Feeds
Bounteous.com: Acquia Site Studio: Introducing Visual Page Builder, New Features, and Bug Fixes
Bounteous.com: How to Build a Great Drupal Team
Bounteous.com: Mini Case Study: An Iterative Approach to Decoupling Drupal
Bounteous.com: A Mini Case Study: How to Rescue an Abandoned/Neglected Drupal Module
Bounteous.com: Acquia Site Studio: Why You May Need It for Your Next Drupal Project
Bounteous.com: Deploying Acquia Cloud Platform CDN With Confidence
Bounteous.com: Connecting PHPStorm and Lando Databases for Highly Productive Drupal Development
Bounteous.com: Migrating Your Drupal 8 Site to Acquia Cloud Platform Hosting
Bounteous.com: How We Built and Launched a Website in Ten Days Using Acquia Site Studio
Bounteous.com: How to Manage Drupal Entities Through Webhook Notifications
Bounteous.com: Drupal Hosting Solutions: Acquia vs On-Premise
Mike Driscoll: One Week Left for Python Logging Book / Course Kickstarter
My latest Python book campaign is ending in less than a week. This book is about Python’s logging module. I also include two chapters that discuss structlog and loguru.
Why Back A Kickstarter?The reason to back the Kickstarter is that I have exclusive perks there that you cannot get outside of it. Here are some examples:
- Signed paperback copy of the book
- Early access to the video course lessons
- T-shirt with the cover art
- Exclusive price for Teach Me Python, which includes ALL my self-published books and courses
- Exclusive price for all my self-published books
In this book, you will learn how about the following:
- Logger objects
- Log levels
- Log handlers
- Formatting your logs
- Log configuration
- Logging decorators
- Rotating logs
- Logging and concurrency
- and more!
The finished book will be made available in the following formats:
- paperback (at the appropriate reward level)
- epub
The paperback is a 6″ x 9″ book and is approximately 150 pages long.
The post One Week Left for Python Logging Book / Course Kickstarter appeared first on Mouse Vs Python.
Real Python: The Real Python Podcast – Episode #204: Querying OpenStreetMaps via API & Lazy Evaluation in Python
Would you like to get more practice working with APIs in Python? How about exploring the globe using the data from OpenStreetMap? Christopher Trudeau is back on the show this week, bringing another batch of PyCoder's Weekly articles and projects.
[ Improve Your Python With 🐍 Python Tricks 💌 – Get a short & sweet Python Trick delivered to your inbox every couple of days. >> Click here to learn more and see examples ]
Using the QML Language Server for KDE Development (update)
In a previous post I talked about using the QML Language Server for KDE development. Since writing that post a few things happened, so it’s time for an update.
I mentioned that when using Kate qmlls should work out of the box when opening a QML file. That’s mostly true, there is one problem though. Depending on your distribution the binary for qmlls has a different name. Sometimes it’s qmlls, sometimes qmlls6 or qmlls-qt6. You may need to adjust the LSP Server settings in Kate to match the name on your system.
In order for qmlls to find types that are defined in your application’s C++ code those must not only be declaratively registered, qmlls also needs to be told where to find the type information. Fortunately Qt 6.7 comes with a handy way to do that. By passing -DQT_QML_GENERATE_QMLLS_INI=ON to CMake you get an appropriate config file generated. This will be placed into the project’s source directory but is specific to your setup, so add that to your gitignore file (PS: You can set up a global gitignore file for your system, so you don’t need to add this to all your projects). Unfortunately the initial implementation produced wrong configurations for some modules, but this is fixed in Qt 6.7.2.
A problem I mentioned is that qmlls doesn’t find modules that are not installed into the same path as Qt. With Qt 6.8 there will be two new options. The -I parameter allows to add custom import paths to qmlls’ search paths. The -E parameter makes qmlls consider the value of the QML_IMPORT_PATH environment variable for its search paths.
In order for qmlls to work properly modules need to be created using the CMake API and use declarative type registration. Since writing the last post some KDE modules have been converted to those, but there’s still more to do.
Thanks to the QML team for those swift improvements!
Reproducible Builds: Reproducible Builds in April 2024
Welcome to the April 2024 report from the Reproducible Builds project! In our reports, we attempt to outline what we have been up to over the past month, as well as mentioning some of the important things happening more generally in software supply-chain security. As ever, if you are interested in contributing to the project, please visit our Contribute page on our website.
Table of contents:
- New backseat-signed tool to validate distributions’ source inputs
- ‘NixOS is not reproducible’
- Certificate vulnerabilities in F-Droid’s fdroidserver
- Website updates
- ‘Reproducible Builds and Insights from an Independent Verifier for Arch Linux’
- libntlm now releasing ‘minimal source-only tarballs’
- Distribution work
- Mailing list news
- diffoscope
- Upstream patches
- reprotest
- Reproducibility testing framework
kpcyrd announced a new tool called backseat-signed, after:
I figured out a somewhat straight-forward way to check if a given git archive output is cryptographically claimed to be the source input of a given binary package in either Arch Linux or Debian (or both).
Elaborating more in their announcement post, kpcyrd writes:
I believe this to be the “reproducible source tarball” thing some people have been asking about. As explained in the README, I believe reproducing autotools-generated tarballs isn’t worth everybody’s time and instead a distribution that claims to build from source should operate on VCS snapshots instead of tarballs with 25k lines of pre-generated shell-script.
Indeed, many distributions’ packages already build from VCS snapshots, and this trend is likely to accelerate in response to the xz incident. The announcement led to a lengthy discussion on our mailing list, as well as shorter followup thread from kpcyrd about bootstrapping Autotools projects.
Morten Linderud posted an post on his blog this month, provocatively titled, “NixOS is not reproducible”. Although quickly admitting that his title is indeed “clickbait”, Morten goes on to clarify the precise guarantees and promises that NixOS provides its users.
Later in the most, Morten mentions that he was motivated to write the post because:
I have heavily invested my free-time on this topic since 2017, and met some of the accomplishments we have had with “Doesn’t NixOS solve this?” for just as long… and I thought it would be of peoples interest to clarify[.]
In early April, Fay Stegerman announced a certificate pinning bypass vulnerability and Proof of Concept (PoC) in the F-Droid fdroidserver tools for “managing builds, indexes, updates, and deployments for F-Droid repositories” to the oss-security mailing list.
We observed that embedding a v1 (JAR) signature file in an APK with minSdk >= 24 will be ignored by Android/apksigner, which only checks v2/v3 in that case. However, since fdroidserver checks v1 first, regardless of minSdk, and does not verify the signature, it will accept a “fake” certificate and see an incorrect certificate fingerprint. […] We also realised that the above mentioned discrepancy between apksigner and androguard (which fdroidserver uses to extract the v2/v3 certificates) can be abused here as well. […]
Later on in the month, Fay followed up with a second post detailing a third vulnerability and a script that could be used to scan for potentially affected .apk files and mentioned that, whilst upstream had acknowledged the vulnerability, they had not yet applied any ameliorating fixes.
There were a number of improvements made to our website this month, including Chris Lamb updating the archive page to recommend -X and unzipping with TZ=UTC […] and adding Maven, Gradle, JDK and Groovy examples to the SOURCE_DATE_EPOCH page […]. In addition Jan Zerebecki added a new /contribute/opensuse/ page […] and Sertonix fixed the automatic RSS feed detection […][…].
Joshua Drexel, Esther Hänggi and Iyán Méndez Veiga of the School of Computer Science and Information Technology, Hochschule Luzern (HSLU) in Switzerland published a paper this month entitled Reproducible Builds and Insights from an Independent Verifier for Arch Linux. The paper establishes the context as follows:
Supply chain attacks have emerged as a prominent cybersecurity threat in recent years. Reproducible and bootstrappable builds have the potential to reduce such attacks significantly. In combination with independent, exhaustive and periodic source code audits, these measures can effectively eradicate compromises in the building process. In this paper we introduce both concepts, we analyze the achievements over the last ten years and explain the remaining challenges.
What is more, the paper aims to:
… contribute to the reproducible builds effort by setting up a rebuilder and verifier instance to test the reproducibility of Arch Linux packages. Using the results from this instance, we uncover an unnoticed and security-relevant packaging issue affecting 16 packages related to Certbot […].
A PDF of the paper is available.
Simon Josefsson wrote on his blog this month that, going forward, the libntlm project will now be releasing what they call “minimal source-only tarballs”:
The XZUtils incident illustrate that tarballs with files that are not included in the git archive offer an opportunity to disguise malicious backdoors. [The] risk of hiding malware is not the only motivation to publish signed minimal source-only tarballs. With pre-generated content in tarballs, there is a risk that GNU/Linux distributions [ship] generated files coming from the tarball into the binary *.deb or *.rpm package file. Typically the person packaging the upstream project never realized that some installed artifacts was not re-built[.]
Simon’s post goes into further details how this was achieved, and describes some potential caveats and counters some expected responses as well. A shorter version can be found in the announcement for the 1.8 release of libntlm.
In Debian this month, Helmut Grohne filed a bug suggesting the removal of dh-buildinfo, a tool to generate and distribute .buildinfo-like files within binary packages. Note that this is distinct from the .buildinfo generation performed by dpkg-genbuildinfo. By contrast, the entirely optional dh-buildinfo generated a debian/buildinfo file that would be shipped within binary packages as /usr/share/doc/package/buildinfo_$arch.gz.
Adrian Bunk recently asked about including source hashes in Debian’s .buildinfo files, which prompted Guillem Jover to refresh some old patches to dpkg to make this possible, which revealed some quirks Vagrant Cascadian discovered when testing.
In addition, 21 reviews of Debian packages were added, 22 were updated and 16 were removed this month adding to our knowledge about identified issues. A number issue types have been added, such as new random_temporary_filenames_embedded_by_mesonpy and timestamps_added_by_librime toolchain issues.
In openSUSE, it was announced that their Factory distribution enabled bit-by-bit reproducible builds for almost all parts of the package. Previously, more parts needed to be ignored when comparing package files, but now only the signature needs to be deleted.
In addition, Bernhard M. Wiedemann published theunreproduciblepackage as a proper .rpm package which it allows to better test tools intended to debug reproducibility. Furthermore, it was announced that Bernhard’s work on a 100% reproducible openSUSE-based distribution will be funded by NLnet. He also posted another monthly report for his reproducibility work in openSUSE.
In GNU Guix, Janneke Nieuwenhuizen submitted a patch set for creating a reproducible source tarball for Guix. That is to say, ensuring that make dist is reproducible when run from Git. […]
Lastly, in Fedora, a new wiki page was created to propose a change to the distribution. Titled “Changes/ReproduciblePackageBuilds”, the page summarises itself as a proposal whereby “A post-build cleanup is integrated into the RPM build process so that common causes of build irreproducibility in packages are removed, making most of Fedora packages reproducible.”
On our mailing list this month:
-
Continuing a thread started in March 2024 about the Arch Linux minimal container now being 100% reproducible, John Gilmore followed up with a post about the practical and philosophical distinctions of local vs. remote storage of the various artifacts needed to build packages.
-
Chris Lamb asked the list which conferences readers are attending these days: “After peak Covid and other industry-wide changes, conferences are no longer the ‘must attend’ events they previously were… especially in the area of software supply-chain security. In rough, practical terms, it seems harder to justify conference travel today than it did in mid-2019.” The thread generated a number of responses which would be of interest to anyone planning travel in Q3 and Q4 of 2024.
-
James Addison wrote to the list about a “quirk” in Git related to its core.autocrlf functionality, thus helpfully passing on a “slightly off-topic and perhaps not of direct relevance to anyone on the list today” note that might still be “the kind of issue that is useful to be aware of if-and-when puzzling over unexpected git content / checksum issues (situations that I do expect people on this list encounter from time-to-time)”.
diffoscope is our in-depth and content-aware diff utility that can locate and diagnose reproducibility issues. This month, Chris Lamb made a number of changes such as uploading versions 263, 264 and 265 to Debian and made the following additional changes:
- Don’t crash on invalid .zip files, even if we encounter their ‘badness’ halfway through the file and not at the time of their initial opening. […]
- Prevent odt2txt tests from always being skipped due to an (impossibly) new version requirement. […]
- Avoid parens-in-parens in test ‘skipping’ messages. […]
- Ensure that tests with >=-style version constraints actually print the tool name. […]
In addition, Fay Stegerman fixed a crash when there are (invalid) duplicate entries in .zip which was originally reported in Debian bug #1068705). […] Fay also added a user-visible ‘note’ to a diff when there are duplicate entries in ZIP files […]. Lastly, Vagrant Cascadian added an external tool pointer for the zipdetails tool under GNU Guix […] and proposed updates to diffoscope in Guix as well […] which were merged as [264] [265], fixed a regression in test coverage and increased verbosity of the test suite[…].
The Reproducible Builds project detects, dissects and attempts to fix as many currently-unreproducible packages as possible. We endeavour to send all of our patches upstream where appropriate. This month, we wrote a large number of such patches, including:
-
Chris Lamb:
- #1068173 filed against pg-gvm.
- #1068176 filed against goldendict-ng.
- #1068372 filed against grokevt.
- #1068374 filed against ttconv.
- #1068375 filed against ludevit.
- #1068795 filed against pympress.
- #1069168 filed against sagemath-database-conway-polynomials.
- #1069169 filed against gap-polymaking.
- #1069663 filed against dub.
- #1069709 filed against dpb.
- #1069784 filed against python-itemloaders.
- #1069822 filed against python-gvm.
-
Bernhard M. Wiedemann:
- metis (fix build with –nocheck)
- musique (fix a date-related issue)
- orthanc-volview (fix an issue with mtimes and sorting)
- go1.13[go1.14], (https://build.opensuse.org/request/show/1167936), go1.15 (fix a parallelism-related issue)
- postfish (disable compile-time benchmarking)
- geany/glfw (toolchain, random)
- edk2/ovmf/tianocore (with Joey Li: fix a date-related issue)
- dlib (report an issue with compile-time-CPU-detection)
- lua-lmod (fix a date-related issue)
- gitui (fix a date-related issue)
- openssl-3 (report an issue with random output)
- gcc14 (FTBFS-2038)
- nebula (FTBFS-2027-11-11)
-
Jan Zerebecki:
- rpm (Support reproducible automatic rebuilds, etc.)
- openSUSE-release-tools (Create changelog for generated package sources for SOURCE_DATE_EPOCH)
- pesign-obs-integration (Create changelog for generated package sources for SOURCE_DATE_EPOCH)
- openSUSE post-build-checks (Set SOURCE_DATE_EPOCH)
- obs-build (Fix changelog timezone handling)
- obs-service-tar_scm (When generating changelog from Git, create the file if it does not exist.)
-
Thomas Goirand:
- oslo.messaging (fix a hostname-related issue)
reprotest is our tool for building the same source code twice in different environments and then checking the binaries produced by each build for any differences. This month, reprotest version 0.7.27 was uploaded to Debian unstable) by Vagrant Cascadian who made the following additional changes:
- Enable specific number of CPUs using --vary=num_cpus.cpus=X. […]
- Consistently use 398 days for time variation, rather than choosing randomly each time. […]
- Disable builds of arch:any packages. […]
- Update the description for the build_path.path option in README.rst. […]
- Update escape sequences for compatibility with Python 3.12. (#1068853). […]
- Remove the generic ‘upstream’ signing-key […] and update the packages’ signing key with the currently active team members […].
- Update the packaging Standards-Version to 4.7.0. […]
In addition, Holger Levsen fixed some spelling errors detected by the spellintian tool […] and Vagrant Cascadian updated reprotest in GNU Guix to 0.7.27.
The Reproducible Builds project operates a comprehensive testing framework running primarily at tests.reproducible-builds.org in order to check packages and other artifacts for reproducibility.
In April, an enormous number of changes were made by Holger Levsen:
-
Debian-related changes:
-
Breakage detection:
- Exclude currently building packages from breakage detection. […]
- Be more noisy if diffoscope crashes. […]
- Health check: provide clickable URLs in jenkins job log for failed pkg builds due to diffoscope crashes. […]
- Limit graph to about the last 100 days of breakages only. […]
- Fix all found files with bad permissions. […]
- Prepare dealing with diffoscope timeouts. […]
- Detect more cases of failure to debootstrap base system. […]
- Include timestamps of failed job runs. […]
-
Documentation updates:
- Document how to access arm64 nodes at Codethink. […]
- Document how to use infomaniak.cloud. […]
- Drop notes about long stalled LeMaker HiKey960 boards sponsored by HPE and hosted at ETH. […]
- Mention osuosl4 and osuosl5 and explain their usage. […]
- Mention that some packages are built differently. […][…]
- Improve language in a comment. […]
- Add more notes how to query resource usage from infomaniak.cloud. […]
-
Node maintenance:
-
Misc changes:
In addition, Mattia Rizzolo added some new host details. […]
If you are interested in contributing to the Reproducible Builds project, please visit our Contribute page on our website. However, you can get in touch with us via:
-
IRC: #reproducible-builds on irc.oftc.net.
-
Twitter: @ReproBuilds
-
Mastodon: @reproducible_builds@fosstodon.org
-
Mailing list: rb-general@lists.reproducible-builds.org
Web Review, Week 2024-19
Let’s go for my web review for the week 2024-19.
Heat Death of the Internet - takahēTags: tech, internet, web, satire, criticism
Obviously a satire, some of it feels eerily real though.
https://www.takahe.org.nz/heat-death-of-the-internet/
Tags: tech, ai, machine-learning, gpt, research, benchmarking, criticism
Nice article. It’s a good reminder that the benchmarks used to evaluate generative AI systems have many caveats.
https://aiguide.substack.com/p/ai-now-beats-humans-at-basic-tasks
Tags: tech, ai, copilot, productivity
Interesting data point. This is a very specialized experience but the fact that those systems are kind of random and slow clearly play a good part in limiting the productivity you could get from them.
https://trace.yshui.dev/2024-05-copilot.html
Tags: tech, ai, copilot, ethics, programming, teaching, learning
Well, maybe our profession will make a leap forward. If instead of drinking the generative AI cool aid, if we really get a whole cohort of programmers better at critical skills (ethical issues, being skeptical of their tools, testing, software design and debugging) it’ll clearly be some progress. Let’s hope we don’t fall in the obvious pitfalls.
https://spectrum.ieee.org/ai-coding
Tags: tech, ai, machine-learning, gpt, copyright, gdpr
Interesting questions and state of the art around model “unlearning”. This became important due to the opacity of data sets used to train some models. It’ll also be important in any case for managing models over time.
https://ai.stanford.edu/~kzliu/blog/unlearning
Tags: tech, linux, systemd
Indeed the next systemd release feels feature packed. Definitely to keep an eye on.
https://lwn.net/SubscriberLink/971866/f244aee59d4d6a66/
Tags: tech, bios, uefi, hardware
Confused? Well, not surprising we mostly use those terms with very lax definitions.
https://utcc.utoronto.ca/~cks/space/blog/tech/UEFIAndBIOSAndOtherPCTerms
Tags: tech, tcp, networking
Getting network protocols right is definitely difficult.
https://brooker.co.za/blog/2024/05/09/nagle.html
Tags: tech, language, search
If you wonder why information retrieval from natural language texts is a tough domain, here is a short article listing the important things to keep in mind.
https://transactional.blog/blog/2023-why-full-text-search-is-hard
Tags: tech, failure, ux
Not a reason to make no effort into having as proper error messages as possible. Still there’s some truth there that trying to have a really useful error message is a fool’s errand.
https://www.haskellforall.com/2024/05/all-error-messages-are-necessarily-bad.html?m=1
Tags: tech, python, qt, spreadsheets, tools
Looks like a fun spreadsheet tool where you can use Python in any cell.
Tags: tech, uuid, encodings
Interesting set of tricks around UUIDs to make them easier to manipulate.
https://www.unkey.com/blog/uuid-ux
Tags: tech, web, frontend, htmx
Excellent exercise in understanding how HTMX works under the hood.
https://joshi.monster/posts/build-your-own-htmx/
Tags: tech, web, email
Good exploration of the many ways contact forms fail us regularly. Also shows a few cases where you might still want to us them… in most cases you shouldn’t.
https://adamjones.me/blog/dont-use-contact-forms/
Tags: tech, web, frontend, css
Looks like a good reference about everything which can be done with the latest CSS evolutions.
https://frontendmasters.com/blog/what-you-need-to-know-about-modern-css-spring-2024-edition/
Tags: tech, tests
Good advice indeed. Having asserts using appropriate matchers can go a long way understanding what went wrong.
https://testing.googleblog.com/2024/05/test-failures-should-be-actionable.html?m=1
Tags: tech, complexity
Definitely this. We tend to like complexity too much as a profession and field. It’s also a good reminder that the complexity of the problem and the complexity of the solution shouldn’t be conflated.
https://eugeneyan.com/writing/simplicity/
Tags: tech, programming, culture, craftsmanship
Interesting take about the mantras often used in our profession. They shouldn’t be treated as laws, but as proverbs carrying a piece of contextual wisdom. It’s thus unsurprising that they tend to contradict each other. This contradiction should make us pause and think.
https://lukeplant.me.uk/blog/posts/programming-mantras-are-proverbs/
Tags: tech, programming, refactoring
Since there’s a clear tendency in the developers I meet to “extract at all costs”, this is a good reminder that sometimes you need to inline the code first. This very often brings better clarity in the context of use. In turns this leads to a better final extraction.
https://xp123.com/refactor-inline-adjust-extract/
Bye for now!
Django Weblog: Django Developers Survey 2023 results
In October-November 2023, the Django Software Foundation, in partnership with PyCharm, carried out a survey to capture the preferences and contributions of Django developers worldwide. Today, we’re excited to share the results through detailed infographics highlighting how our community influences the future of web development.
View the Django Developers Survey 2023 report
Why should you check out the infographics?
- Discover the latest trends in Django development.
- Learn about the tools and technologies preferred by leading developers.
- Understand the challenges and opportunities within the Django ecosystem.
Visit the landing page to explore the full report and gain insights that can help shape your projects and strategies in the Django landscape.
Seth Michael Larson: Bringing supply chain security to PyCon US 2024
Published 2024-05-10 by Seth Larson
Reading time: minutes
Next week is PyCon US 2024, one of my favorite times of year. If you'll also be in Pittsburgh, reach out to me on Signal (sethmlarson.99) and we'll meet up sometime during the conference.
Here's where you'll find me during the week:
Secure snek 🐍🛡️
- Talk on "State of Supply Chain Security" with Michael Winser of Alpha-Omega.
- Open space on Vulnerability Disclosure and Management with Madison Oliver of GitHub Security.
- Blogger for the Python Language Summit.
- Spreading security knowledge along with Mike Fiedler, the PyPI Safety and Security Engineer.
- Working in-person with Python core developers during sprints.
I'll also be bringing along some exclusive "secure snek" stickers, so if you see me at the conference ask about those while supplies last!
If you're interested in security, I recommend considering these other tutorials and talks:
- Tutorial: PyO3 101: Writing Python modules in Rust by Cheuk Ting Ho
- Tutorial: Fundamentals of API security in Python by Jose Haro Peralta
- Talk: Making Python safer than ever by Cheuk Ting Ho
- Talk: Building a Rusty path validation library for PyCA Cryptography by William Woodruff
- Talk: How Python harnesses Rust through PyO3 by David Hewitt
That's all for this week! 👋 If you're interested in more you can read last week's report.
Thanks for reading! ♡ Did you find this article helpful and want more content like it?
Get notified of new posts by subscribing to the RSS feed or the email newsletter.
This work is licensed under CC BY-SA 4.0
KDE Ships Frameworks 6.2.0
Friday, 10 May 2024
KDE today announces the release of KDE Frameworks 6.2.0.
KDE Frameworks are 72 addon libraries to Qt which provide a wide variety of commonly needed functionality in mature, peer reviewed and well tested libraries with friendly licensing terms. For an introduction see the KDE Frameworks release announcement.
This release is part of a series of planned monthly releases making improvements available to developers in a quick and predictable manner.
New in this version Attica- Modernize: don't else after return. Commit.
- Provider: document default ctor. Commit.
- Providermanager: remove unused function with typo. Commit.
- Postfiledata: simplify private. Commit.
- Modernize: use unique_ptr for privates. Commit.
- Basejob: don't leave dangly pointers. Commit.
- Platformdependent: v3. Commit.
- Fixed min_bitpool and max_bitpool from capabilities where ignored. Commit.
- Port QML module to declarative type registration. Commit.
- Add support for media-playlist-no-shuffle icon name. Commit.
- Add audio/ogg and audio/x-vorbis+ogg icons. Commit.
- Add audio/vnd.wave MIME type. Commit.
- Remove generic non-symbolic audio and video icons. Commit.
- Add 16 and 22px symbolic versions of some Places icons that were missing. Commit. Fixes bug #486316
- Add zoom-in-map and zoom-out-map icons along with -symbolic versions. Commit.
- Longer description for the ICONS_LIBRARY option. Commit.
- Add symbolic versions for more USB device style icons. Commit.
- Fix some scale errors. Commit. Fixes bug #485479
- Fixed input-combo-on.svg colour issue. Commit.
- Add -symbolic symlinks for notification-* icons. Commit.
- Use new dev.suyu_emu.suyu id, add symlink for old id. Commit.
- Add accessories-screenshot-tool icon/symlink. Commit.
- [webfont] enable ligatures. Commit.
- Gitignore: add VS Code dir. Commit.
- Add input-keyboard-color 22px, 32 px. Commit.
- API dox: KDEInstallDirs6: refer to qtpaths now as source of Qt paths. Commit.
- API dox: KDEInstallDirs6: drop outdated note about being in ALPHA state. Commit.
- Test: Increase minimum cmake version so that it works with Qt 6.7. Commit.
- ECMQmlModule6: group qml and resource file calls. Commit.
- Modules/ECMAddTests.cmake - handle unset or empty QT_PLUGIN_PATH. Commit.
- Gitignore: add VS Code dir. Commit.
- KQuickConfigModule: Don't crash on null object. Commit.
- SimpleKCM: Remove remnants of footerParent. Commit.
- Use ellipsis character instead of three dots. Commit.
- GridDelegate: Port to ComponentBehavior: Bound. Commit.
- GridDelegate: Consolidate code paths for opening a menu. Commit.
- GridDelegate: Don't use qualified property access as appropriate. Commit.
- GridDelegate: Use concrete type for the popup menu. Commit.
- GridDelegate: Use somewhat more consistent ToolTip bindings, remove timeout. Commit.
- Components: Drop QML import versions, unify import aliases. Commit.
- Components: Guard nullable property access. Commit.
- Components: Explicitly specify signal handler arguments. Commit.
- KCModuleQml: Provide a fallback in case a pushed page is not one of magical KCMUtils types. Commit.
- Add API to make header and footer paddings optional. Commit.
- Round all the things consistently. Commit.
- Pluginselector: cache delegates. Commit.
- Gitignore: add VS Code dir. Commit.
- Gitignore: add VS Code dir. Commit.
- Avoid allocations while parsing int/float lists. Commit.
- Adapt kdesktopfiletest to QTemporaryFile behavior change. Commit.
- Guard header with an ifndef and include moc generates sources in the cpp file. Commit.
- Autotests: Don't use a timeout in testLocalDeletion. Commit.
- Adjust kconfig_compiler autotests to include a version without kcfgc. Commit.
- Add a CMake function to add a kcfg file without kcfgc. Commit.
- Gitignore: add VS Code dir. Commit.
- KRecentFilesAction: Load mimeType and action lazily. Commit.
- Remove forward declaration of KToggleAction. Commit.
- Test that an invalid language gives the empty string. Commit.
- Gitignore: add VS Code dir. Commit.
- Restore country detection tests on FreeBSD. Commit.
- Disable FreeBSD tests that recently started to fail in the CI. Commit.
- Gitignore: add VS Code dir. Commit.
- Gitignore: add VS Code dir. Commit.
- API dox: use "MIME type" and "URL" spellings consistently. Commit.
- API dox: add some minimal info to undocumented classes. Commit.
- API dox: add empty line between @brief (ends by first period) and rest. Commit.
- API dox: add some dummy info to namespaces for doxygen to cover them also. Commit.
- API dox: escape space after e.g. to work-around doxygen sentence end magic. Commit.
- UserMetadata: return errors when xattr ops fails. Commit.
- Value is already default timeout value in QT6 framework. Commit.
- [XmlExtractor] Add support for compressed SVGs. Commit.
- [XmlExtractorTest] Move Test class declaration to source file. Commit.
- [Office2007Extractor] Reuse DublinCoreExtractor, fix namespace handling. Commit.
- [DublinCoreExtractor] Add CreationDate (dc::created) support. Commit.
- [DublinCoreExtractor] Skip properties from empty elements, cleanup. Commit.
- Move date parser helper out of ExtractorPlugin, clean it up. Commit.
- [TaglibExtractor] Include vnd.audible.aaxc audio books in supported types. Commit.
- [Test] Include vnd.audible.aax audio books in coverage tests. Commit.
- [TaglibWriterTest] Move test class declaration to source file, cleanup. Commit.
- [TaglibExtractor|Writer] Fix mimetypes. Commit.
- Port q->connect to QObject::connect. Commit.
- Fix connection lifetime issue. Commit. See bug #454854. See bug #485386
- Recorder/kkeysequencerecorder: conform to KKeyServer changes. Commit.
- Gitignore: add VS Code dir. Commit.
- Update holiday_bd_en. Commit.
- Gitignore: add VS Code dir. Commit.
- Allow to configure if we register our icon plugin for SVGs. Commit.
- Port QML module to declarative type registration. Commit.
- Fix typo in BreezeIcons::initIcons loading. Commit.
- Gitignore: add VS Code dir. Commit.
- Fix build with Qt 6.7 on 32 bits. Commit.
- [kfilefilter] Consider mime globs valid. Commit.
- Kfileitemtest: add basic tests for dir. Commit.
- File_unix: don't call QMimeDatabase::mimeTypeForFile for directories. Commit.
- Widgetsaskuseractionhandler prevent crash when job had no parent widget. Commit.
- PreviewJob: Add file extension to thumbnail temp files. Commit. Fixes bug #463989
- KFileItem: handle the case parent url path is empty. Commit.
- KFileItemActions: Add logic to order actions between separators. Commit. Fixes bug #466115
- KFileItem: fix getStatusBarInfo() displaying symlink target as "http:". Commit. Fixes bug #475422
- ScopedProcessRunner: support waitForStarted. Commit.
- ScopedProcessRunner: fix use of undeclared identifier 'close'. Commit.
- [ftp] Always use default timeout values. Commit.
- [http] Set error string for ERR_DOES_NOT_EXIST. Commit.
- Force test language to en. Commit.
- Knewfilemenu: Add @since 6.2 to the new signals and methods. Commit.
- Kfilefilter.h: update API docs. Commit.
- Kencodingfiledialog dox: rewrite API dox that refer to removed functions. Commit.
- Kfilewidget dox: replace references to setFilter() with setFilters(). Commit.
- Fix a few warnings. Commit.
- Add EnableRemoteFolderThumbnail option checking. Commit.
- PreviewJob: Display preview for locally mounted remote directories. Commit.
- Knewfilemenu: add isNewDirNameJobRunning. Commit.
- KFilePlacesItem: Show teardown busy indicator during optical media eject. Commit.
- KDirModelTest.testDeleteFiles: lower debug output. Commit.
- KUrlNavigator: allow adding a badge widget after the breadcrumb. Commit.
- Set ideal case for TwoVectors. Commit.
- Udsentry_api_comparison_benchmark: update. Commit.
- Kurlnavigatorbutton: prevent. Commit.
- Add more explicit moc includes to sources for moc-covered headers. Commit.
- Connection: don't queue tasks until OOM. Commit.
- Http: Fix parsing DAV:getlastmodified. Commit. Fixes bug #484671
- Kfileitem: Linux, use statx to refresh files. Commit. Fixes bug #446858
- Fixed wrong navigation and dialog header button colors. Commit. Fixes bug #486163
- Card: Remove the unnecessary "reality check" binding on footer, add test. Commit.
- Card: Restrict actions type from arbitrary QObject to T.Action. Commit.
- Card: Shuffle things around a bit to make them look nicer. Commit.
- Remove linkActivated/linkHovered from Delegate types. Commit.
- InlineMessage: Improve examples in documentation, clean up QML. Commit.
- OverlayDrawer: Rework separator's code, animate transitions. Commit.
- OverlayDrawer: Hide segmented separator when the drawer is collapsed. Commit.
- OverlayDrawer: Rewrite visibility condition for segmented separator. Commit.
- OverlayDrawer: Rewrite segmented separator positioning expression. Commit.
- OverlayDrawer: Bind segmented separator's width to the real separator's width. Commit.
- GlobalDrawer: Set spacing on the default header. Commit.
- Fix null deref in OverlaySheet. Commit.
- OverlaySheet: Port layout hacks to a simple Padding with its contentItem. Commit.
- Tst_pagepool: Port testing code from verify(==) to compare. Commit.
- Tst_pagepool: Fix test properly. Commit.
- Revert "tst_pagepool: Fix test". Commit.
- CardsGridView and CheckableListItem are not a thing anymore. Commit.
- Actions.main is not a thing anymore. Commit.
- Tst_pagepool: Fix test. Commit.
- Revert "PageRow: Fix parent of Component-based pages". Commit.
- PageRow: Fix parent of Component-based pages. Commit. Fixes bug #482753
- MnemonicAttached: Fix logic when pressing Alt. Commit.
- Dialog: Always use an overlay as visual parent. Commit.
- Link Activation TitleSubtitle. Commit.
- ContextualHelpButton: remove excess space from tooltip. Commit. Fixes bug #481817
- Fix crash on teardown when QML engine is already unset. Commit.
- ListSectionHeader: Deprecate label property. Commit.
- PageRow: Remove superfluous trailing semicolon from a property alias. Commit.
- PromptDialog: Create default contentItem dynamically on demand. Commit.
- Padding: Remove old overridden contentItem from the visual hierarchy. Commit.
- Gitignore: add VS Code dir. Commit.
- Add a explicit page type check in AbstractApplictionHeader. Commit.
- Add radius unit for rounded rectangles. Commit.
- Add more explicit moc includes to sources for moc-covered headers. Commit.
- Show header warning message framelessly. Commit. Fixes bug #485464
- DownloadItemsSheet: use alternating background colors for legibility. Commit. Fixes bug #483724
- Document ContentWarning. Commit.
- Page: conditionalize warning message based on riskiness. Commit.
- Enforce passing tests on Windows. Commit.
- Enforce passing tests on Windows. Commit.
- Action: Make bool operator explicit. Commit.
- Fix matchInternalFinished not being emitted in case of dbus errors. Commit.
- Fix caret painting for inline notes at the end of line. Commit.
- KateCompletionWidget: Mark function static. Commit.
- KateCompletionModel: remove useless std::as_const. Commit.
- Run more tests offscreen. Commit.
- Fix performance with many cursors in a large line. Commit.
- Fix test expectations. Commit.
- Fix crashs and OOM on load with encoding failures. Commit. Fixes bug #486195. Fixes bug #486134
- A11y: Improve tab order for "Appeareance" -> "Borders". Commit.
- A11y: Set "Line Height Multiplier" buddy. Commit.
- Fix broken navigation in completion widget with multiple views. Commit.
- Fix clicking in completion. Commit.
- Fix textInsertedRange signal for insertText behind last line. Commit. Fixes bug #483363
- Enforce passing tests on all platforms. Commit.
- Fix logging category. Commit.
- Fix reply type in portal implementation. Commit.
- Kwalletportalsecrets.h: Add missing include. Commit.
- Implement XDG Secrets Portal. Commit. Fixes bug #466197
- Introduce KContextualHelpButton. Commit.
- KMessageWidget: Fix handling of palette changes. Commit.
- KMessageWidget: Make sure icon label is always vertically centered. Commit.
- Gitignore: add VS Code dir. Commit.
- Port to QNativeInterface::Private::QWaylandWindow. Commit.
- Remove an unused explicit moc include. Commit.
- Add more explicit moc includes to sources for moc-covered headers. Commit.
- Introduce KXcbEvent to initialize the memory of sent XCB events. Commit.
- Improve dbus disabling. Commit.
- TreeViewDelegate: Fix non-observable modelIndex property getting stuck. Commit.
- [CheckIndicator] Use control as AbstractButton. Commit.
- Add missing dependency to private module. Commit.
- Add QTBUG to comment. Commit.
- Make SwitchIndicator more compiler-friendly. Commit.
- ItemBranchIndicators: Fix uninitialized member variable m_selected. Commit.
- StyleSingleton: Check whether object is qGuiApp. Commit.
- [RadioButton] Use id instead of parent lookup. Commit.
- [TabButton] Fix property type. Commit.
- Apply Kirigami.Units.cornerRadius to default list item background too. Commit.
- Gitignore: add VS Code dir. Commit.
- Use consistent radius value from Kirigami.Units.radius. Commit.
- Remove too aggressive assert. Commit. Fixes bug #464149
- [StorageAccess] Fix storageAccessFromPath returning unmounted filesystems. Commit.
- [SolidHwTest] Extend FakeHW description with encrypted volume, add tests. Commit.
- [SolidHwTest] Test Device::storageAccessFromPath. Commit.
- [DeviceManager] Remove exists() check from storageAccessFromPath. Commit.
- Udisks: Return empty string for "root" clearTextPath. Commit. Fixes bug #485507
- [SolidHwTest] Remove unnecessary slotPropertyChanged helper, fix bug. Commit.
- [SolidHwTest] Remove setenv wrapper, unnecessary qt_windows.h include. Commit.
- [SolidHwTest] Move test class declaration to source file. Commit.
- Udisks2: Add support CanCheck/Check/CanRepair/Repair. Commit.
Reproducible Builds (diffoscope): diffoscope 266 released
The diffoscope maintainers are pleased to announce the release of diffoscope version 266. This version includes the following changes:
[ Chris Lamb ] * Use "xz --list" to supplement the output when comparing .xz archives; essential when some underlying metadata differs. (Closes: #1069329) * Actually append the xz --list after the container differences, as it simplifies tests and the output. * Add 7zip to <!nocheck> Build-Depends in debian/control. * Update copyright years. [ James Addison ] * Maintain an in-header boolean state to determine whether to drop from-file/to-file lines. This fixes an issue where HTML differences were being inadvertendly neglected. (Closes: reproducible-builds/diffoscope#372)You find out more by visiting the project homepage.