05 Dec 2024
Planet Debian
Reproducible Builds: Reproducible Builds in November 2024
Welcome to the November 2024 report from the Reproducible Builds project!
Our monthly reports outline what we've been up to over the past month and highlight items of news from elsewhere in the world of software supply-chain security where relevant. As ever, if you are interested in contributing to the Reproducible Builds project, please visit our Contribute page on our website.
Table of contents:
- Reproducible Builds mourns the passing of Lunar
- Introducing reproduce.debian.net
- New landing page design
- SBOMs for Python packages
- Debian updates
- Reproducible builds by default in Maven 4
- PyPI now supports digital attestations
- "Dependency Challenges in OSS Package Registries"
- Zig programming language demonstrated reproducible
- Website updates
- Upstream patches
- Misc development news
- Reproducibility testing framework
Reproducible Builds mourns the passing of Lunar
The Reproducible Builds community sadly announced it has lost its founding member, Lunar. Jérémy Bobbio aka 'Lunar' passed away on Friday November 8th in palliative care in Rennes, France.
Lunar was instrumental in starting the Reproducible Builds project in 2013 as a loose initiative within the Debian project. He was the author of our earliest status reports and many of our key tools in use today are based on his design. Lunar's creativity, insight and kindness were often noted.
You can view our full tribute elsewhere on our website. He will be greatly missed.
Introducing reproduce.debian.net
In happier news, this month saw the introduction of reproduce.debian.net. Announced at the recent Debian MiniDebConf in Toulouse, reproduce.debian.net is an instance of rebuilderd operated by the Reproducible Builds project.
rebuilderd is our server designed monitor the official package repositories of Linux distributions and attempts to reproduce the observed results there.
In November, reproduce.debian.net began rebuilding Debian unstable on the amd64
architecture, but throughout the MiniDebConf, it had attempted to rebuild 66% of the official archive. From this, it could be determined that it is currently possible to bit-for-bit reproduce and corroborate approximately 78% of the actual binaries distributed by Debian - that is, using the .buildinfo
files hosted by Debian itself.
reproduce.debian.net also contains instructions how to setup one's own rebuilderd instance, and we very much invite everyone with a machine to spare to setup their own version and to share the results. Whilst rebuilderd is still in development, it has been used to reproduce Arch Linux since 2019. We are especially looking for installations targeting Debian architectures other than i386
and amd64
.
New landing page design
As part of a very productive partnership with the Sovereign Tech Fund and Neighbourhoodie, we are pleased to unveil our new homepage/landing page.
We are very happy with our collaboration with both STF and Neighbourhoodie (including many changes not directly related to the website), and look forward to working with them in the future.
SBOMs for Python packages
The Python Software Foundation has announced a new "cross-functional project for SBOMs and Python packages". Seth Michael Larson writes that the project is "specifically looking to solve these issues":
- Enable Python users that require SBOM documents (likely due to regulations like CRA or SSDF) to self-serve using existing SBOM generation tools.
- Solve the "phantom dependency" problem, where non-Python software is bundled in Python packages but not recorded in any metadata. This makes the job of software composition analysis (SCA) tools difficult or impossible.
- Make the adoption work by relevant projects such as build backends, auditwheel-esque tools, as minimal as possible. Empower users who are interested in having better SBOM data for the Python projects they are using to be able to contribute engineering time towards that goal.
A GitHub repository for the initiative is available, and there are a number of queries, comments and remarks on Seth's Discourse forum post.
Debian updates
There was significant development within Debian this month. Firstly, at the recent MiniDebConf in Toulouse, France, Holger Levsen gave a Debian-specific talk on rebuilding packages distributed from ftp.debian.org
- that is to say, how to reproduce the results from the official Debian build servers:
Holger described the talk as follows:
For more than ten years, the Reproducible Builds project has worked towards reproducible builds of many projects, and for ten years now we have build Debian packages twice-with maximal variations applied-to see if they can be build reproducible still.
Since about a month, we've also been rebuilding trying to exactly match the builds being distributed via
ftp.debian.org
. This talk will describe the setup and the lessons learned so far, and why the results currently are what they are (spoiler: they are less than 30% reproducible), and what we can do to fix that.
The Debian Project Leader, Andreas Tille, was present at the talk and remarked later in his Bits from the DPL update that:
It might be unfair to single out a specific talk from Toulouse, but I'd like to highlight the one on reproducible builds. Beyond its technical focus, the talk also addressed the recent loss of Lunar, whom we mourn deeply. It served as a tribute to Lunar's contributions and legacy. Personally, I've encountered packages maintained by Lunar and bugs he had filed. I believe that taking over his packages and addressing the bugs he reported is a meaningful way to honor his memory and acknowledge the value of his work.
Holger's slides and video in .webm
format are available.
Next, rebuilderd is the server to monitor package repositories of Linux distributions and attempt to reproduce the observed results. This month, version 0.21.0 released, most notably with improved support for binNMUs by Jochen Sprickerhof and updating the rebuilderd-debian.sh
integration to the latest debrebuild
version by Holger Levsen. There has also been significant work to get the rebuilderd
package into the Debian archive, in particular, both rust-rebuilderd-common
version 0.20.0-1
and rust-rust-lzma
version 0.6.0-1
were packaged by kpcyrd and uploaded by Holger Levsen.
Related to this, Holger Levsen submitted three additional issues against rebuilderd as well:
rebuildctl
should be more verbose when encountering issues. […]- Please add an option to used randomised queues. […]
- Scheduling and re-scheduling multiple packages at once. […]
… and lastly, Jochen Sprickerhof submitted one an issue requested that rebuilderd downloads the source package in addition to the .buildinfo
file […] and kpcyrd also submitted and fixed an issue surrounding dependencies and clarifying the license […]
Separate to this, back in 2018, Chris Lamb filed a bug report against the sphinx-gallery
package as it generates unreproducible content in various ways. This month, however, Dmitry Shachnev finally closed the bug, listing the multiple sub-issues that were part of the problem and how they were resolved.
Elsewhere, Roland Clobus posted to our mailing list this month, asking for input on a bug in Debian's ca-certificates-java
package. The issue is that the Java key management tools embed timestamps in its output, and this output ends up in the /etc/ssl/certs/java/cacerts
file on the generated ISO images. A discussion resulted from Roland's post suggesting some short- and medium-term solutions to the problem.
Holger Levsen uploaded some packages with reproducibility-related changes:
-
devscripts
versions 2.24.3, 2.24.4 and 2.24.5 were uploaded, including several fixes for thedebrebuild
anddebootsnap
and scripts. -
cdbs
version 0.4.167 uploaded in order to dropdh_buildinfo
support, asdpkg
has generated.buildinfo
files since 2016 and the results ofdh_buildinfo
are typically unreproducible. Related to this a mass bug filing by Helmut Grohne intended to remove the obsolete and deprecateddh-buildinfo
package from the archive. At the time of writing, this still affects 311 packages in Debian unstable.
Lastly, 12 reviews of Debian packages were added, 5 were updated and 21 were removed this month adding to our knowledge about identified issues in Debian.
Reproducible builds by default in Maven 4
On our mailing list this month, Hervé Boutemy reported the latest release of Maven (4.0.0-beta-5
) has reproducible builds enabled by default. In his mailing list post, Hervé mentions that "this story started during our Reproducible Builds summit in Hamburg", where he created the upstream issue that builds on a "multi-year" effort to have Maven builds configured for reproducibility.
PyPI now supports digital attestations
Elsewhere in the Python ecosystem and as reported on LWN and elsewhere, the Python Package Index (PyPI) has announced that it has finalised support for PEP 740 ("Index support for digital attestations").
Trail of Bits, who performed much of the development work, has an in-depth blog post about the work and its adoption, as well as what is left undone:
One thing is notably missing from all of this work: downstream verification. […]
This isn't an acceptable end state (cryptographic attestations have defensive properties only insofar as they're actually verified), so we're looking into ways to bring verification to individual installing clients. In particular, we're currently working on a plugin architecture for
pip
that will enable users to load verification logic directly into theirpip install
flows.
There was an in-depth discussion on LWN's announcement page, as well as on Hacker News.
"Dependency Challenges in OSS Package Registries"
At BENEVOL, the Belgium-Netherlands Software Evolution workshop in Namur, Belgium, Tom Mens and Alexandre Decan presented their paper, "An Overview and Catalogue of Dependency Challenges in Open Source Software Package Registries".
The abstract of their paper is as follows:
While open-source software has enabled significant levels of reuse to speed up software development, it has also given rise to the dreadful dependency hell that all software practitioners face on a regular basis. This article provides a catalogue of dependency-related challenges that come with relying on OSS packages or libraries. The catalogue is based on the scientific literature on empirical research that has been conducted to understand, quantify and overcome these challenges. […]
A PDF of the paper is available online.
Zig programming language demonstrated reproducible
Motiejus Jakšty posted an interesting and practical blog post on his successful attempt to reproduce the Zig programming language without using the pre-compiled binaries checked into the repository, and despite the circular dependency inherent in its bootstrapping process.
As a summary, Motiejus concludes that:
I can now confidently say (and you can also check, you don't need to trust me) that there is nothing hiding in
zig1.wasm
[the checked-in binary] that hasn't been checked-in as a source file.
The full post is full of practical details, and includes a few open questions.
Website updates
Notwithstanding the significant change to the landing page (screenshot above), there were an enormous number of changes made to our website this month. This included:
-
Alex Feyerke and Mariano Giménez:
-
Bernhard M. Wiedemann:
- Update the "System images" page to document the
e2fsprogs
approach. […]
- Update the "System images" page to document the
-
Chris Lamb:
- Cachebust every CSS file per-release. […]
- Replace some inline markdown with HTML. […]
- Use spaces on the "Publications" page. […]
- Add a news article about the passing of Lunar. […][…][…][…]
- Add a black memorial band to the top of the page. […]
-
FC (Fay) Stegerman:
- Replace more inline markdown with HTML on the "Success stories" page. […]
- Add some links, fix some other links and correct some spelling errors on the "Tools" page. […]
-
Holger Levsen:
-
Julia Krüger:
- Add a new "Stripping of unreproducible information page to the documentation. […]
-
Ninette Adhikari & hulkoba:
-
Philip Rinn:
- Import 47 historical weekly reports. […]
-
hulkoba:
- Add
alt
text to almost all images (!). […][…] - Fix a number of links on the "Talks". […][…]
- Avoid so-called 'ghost' buttons by not using
<button>
elements as links, as the affordance of a<button>
implies an action with (potentially) a side effect. […][…] - Center the sponsor logos on the homepage. […]
-
Move publications and generate them instead from a
data.yml
file with an improved layout. […][…] -
Make a large number of small but impactful stylisting changes. […][…][…][…]
- Expand the "Tools" to include a number of missing tools, fix some styling issues and fix a number of stale/broken links. […][…][…][…][…][…]
- Add
Upstream patches
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:
-
Bernhard M. Wiedemann:
clisp
(fix contributed by Bruno Haible)conky
(date-related issue)emacs-auctex
(date-relatedgzip
issue)javadoc
(filesystem ordering issue)jboss-websocket-1.0-api
(embedsuname -r
)lcms2
(CPU issue)LiE
(ASLR-related issue)make_ext4fs
(toolchain-related issue for for VM images)obs-build
(issue when running builds with certain CPU types or core numbers)perl-Time-modules
(fails to build far in the future)python-bson
(fails to build far in the future)python-exiv2
(fails to build far in the future)python-moto
(date-relatedgzip
issue)python-pyhanko-certvalidator
(fails to build far in the future)python-python-gvm
(concurrency-related issue)python310
(fails to build far in the future)python313
(fails to build far in the future)reproducible-faketools
(toolchain for emacs)shadowsocks-rust
(date-related issue)swipl
(fails to build far in the future)
-
Chris Lamb:
- #1087330 filed against
python-pydash
. - #1087485 filed against
fritzconnection
. - #1087486 filed against
tracy
. - #1088238 filed against
rust-broot
. - #1088353 filed against
python-aiovlc
. - #1088742 filed against
python-aiohomekit
.
- #1087330 filed against
-
James Addison:
Misc development news
-
Bernhard M. Wiedemann published another report for the openSUSE distribution.
-
Martin Abente Lahaye updated diffoscope to fix a crash when
objdump
is missing. […] -
On our mailing list, Jan-Benedict Glaw announced the publication of the fifth NetBSD Reproducibility Report
Reproducibility testing framework
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 November, a number of changes were made by Holger Levsen, including:
-
reproduce.debian.net-related changes:
- Create and introduce a new reproduce.debian.net service and subdomain […]
- Make a large number of documentation changes relevant to
rebuilderd
. […][…][…][…][…] - Explain a temporary workaround for a specific issue in
rebuilderd
. […] - Setup another
rebuilderd
instance on theo4
node and update installation documentation to match. […][…] - Make a number of helpful/cosmetic changes to the interface, such as clarifying terms and adding links. […][…][…][…][…]
- Deploy configuration to the
/opt
and/var
directories. […][…] - Add an infancy (or 'alpha') disclaimer. […][…]
- Add more notes to the temporary
rebuilderd
documentation. […] - Commit an nginx configuration file for reproduce.debian.net's "Stats" page. […]
- Commit a
rebuilder-worker.conf
configuration for theo5
node. […]
-
Debian-related changes:
-
Misc changes:
- Adapt the
update_jdn.sh
script for new Debian trixie systems. […] - Stop installing the PostgreSQL database engine on the
o4
ando5
nodes. […] - Prevent accidental reboots of the
o4
node because of a long-running job owned byjosch
. […][…]
- Adapt the
In addition, Mattia Rizzolo addressed a number of issues with reproduce.debian.net […][…][…][…]. And lastly, both Holger Levsen […][…][…][…] and Vagrant Cascadian […][…][…][…] performed node maintenance.
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
onirc.oftc.net
. -
Mastodon: @reproducible_builds@fosstodon.org
-
Mailing list:
rb-general@lists.reproducible-builds.org
-
Twitter: @ReproBuilds
05 Dec 2024 12:47pm GMT
Russ Allbery: Review: Paladin's Hope
Review: Paladin's Hope, by T. Kingfisher
Series: | The Saint of Steel #3 |
Publisher: | Red Wombat Studio |
Copyright: | 2021 |
ISBN: | 1-61450-613-2 |
Format: | Kindle |
Pages: | 303 |
Paladin's Hope is a fantasy romance novel and the third book of The Saint of Steel series. Each book of that series features different protagonists in closer to the romance series style than the fantasy series style and stands alone reasonably well. There are a few spoilers for the previous books here, so you probably want to read the series in order.
Galen is one of the former paladins of the Saint of Steel, left bereft and then adopted by the Temple of the Rat after their god dies. Even more than the paladin protagonists of the previous two books, he reacted very badly to that death and has ongoing problems with nightmares and going into berserker rages when awakened. As the book opens, he's the escort for a lich-doctor named Piper who is examining a corpse found in the river.
The last of the five was the only one who did not share a certain martial quality. He was slim and well-groomed and would be considered handsome, but he was also extraordinarily pale, as if he lived his life underground.
It was this fifth man who nudged the corpse with the toe of his boot and said, "Well, if you want my professional opinion, this great goddamn hole in his chest is probably what killed him."
As it turns out, slim and well-groomed and exceedingly pale is Galen's type.
This is another paladin romance, this time between two men. It's almost all romance; the plot is barely worth mentioning. About half of the book is an exploration of a puzzle dungeon of the sort that might be fun in a video game or tabletop RPG, but that I found rather boring and monotonous in a novel. This creates a lot more room for the yearning and angst.
Kingfisher tends towards slow-burn romances. This romance is a somewhat faster burn than some of her other books, but instead implodes into one of the most egregiously stupid third-act break-ups that I've read in a romance plot. Of all the Kingfisher paladin books, I think this one was hurt the most by my basic difference in taste from the author. Kingfisher finds constant worrying and despair over being good enough for the romantic partner to be an enjoyable element, and I find it incredibly annoying. I think your enjoyment of this book will heavily depend on where you fall on that taste divide.
The saving grace of this book are the gnoles, who are by far the best part of this world. Earstripe, a gnole constable, is the one who found the body that the book opens with and he drives most of the plot, such that it is. He's also the source of the best banter in the book, which is full of pointed and amused gnole observations about humans and their various stupidities. Given that I was also grumbling about human stupidities for most of the book, the gnole viewpoint and I got along rather well.
"God's stripes." Earstripe shook his head in disbelief. "Bone-doctor would save some gnole, yes? If some gnole was hurt."
"Of course," said Piper. "If I could."
"And tomato-man would save some gnole?" He swung his muzzle toward Galen. "If some gnome needed big human with sword?"
"Yes, of course."
Earstripe spread his hands, claws gleaming. "A gnole saves some human. Same thing." He took a deep breath, clearly choosing his words carefully. "A gnole's compassion does not require fur."
We learn a great deal more about gnole culture, all of which I found fascinating, and we get a rather satisfying amount of gnole acerbic commentary. Kingfisher is very good at banter, and dialogue in general, which also smoothes over the paucity of detailed plot. There was no salvaging the romance, at least for me, but I did at least like Piper, and Galen wasn't too bad when he wasn't being annoyingly self-destructive.
I had been wondering a little if gay romance would, like sapphic romance, avoid my dislike of heterosexual gender roles. I think the jury is still out, but it did not work in this book because Galen is so committed to being the self-sacrificing protector who is unable to talk about his feelings that he single-handedly introduced a bunch of annoying pieces of the male gender role anyway. I will have to try that experiment with a book that doesn't involve hard-headed paladins.
I have yet to read a bad T. Kingfisher novel, but I thought this one was on the weaker side. The gnoles are great and kept me reading, but I wish there had been a more robust plot, a lot less of the romance, and no third-act break-up. As is, I recommend the other Saint of Steel books over this one. Ah well.
Followed by Paladin's Faith.
Rating: 6 out of 10
05 Dec 2024 3:56am GMT
04 Dec 2024
Planet Debian
Dirk Eddelbuettel: corels 0.0.5 on CRAN: Maintenance
An updated version of the corels package is now on CRAN! The 'Certifiably Optimal RulE ListS (Corels)' learner provides interpretable decision rules with an optimality guarantee-a nice feature which sets it apart in machine learning. You can learn more about corels at its UBC site.
The changes concern mostly maintenance for both the repository (such as continunous integration setup, badges, documentation links, …) and the package level (such as removing the no-longer-requiring C++ compilation standard setter now emitting a NOTE at CRAN.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
04 Dec 2024 11:13pm GMT
Scarlett Gately Moore: Hacked and tis the season for surgeries
I am still here. Sadly while I battle this insane infection from my broken arm I got back in July, the hackers got my blog. I am slowly building it back up. Further bad news is I have more surgeries, first one tomorrow. Furthering my current struggles I cannot start my job search due to hospitalization and recovery. Please consider a donation. https://gofund.me/6e99345d
On the open source work front, I am still working on stuff, mostly snaps ( Apps 24.08.3 released )
Thank you everyone that voted me into the Ubuntu Community Council!
I am trying to stay positive, but it seems I can't catch a break. I will have my computer in the hospital and will work on what I can. Have a blessed day and see you soon.
Scarlett
04 Dec 2024 5:30pm GMT
Sven Hoexter: Looking at x509 Certificate Chains
Sometimes you've to look at the content of x509 certificate chains. Usually one finds them pem encoded and concatenated in a text file.
Since the openssl x509
subcommand only decodes the first certificate it will find in a file, I did something like this:
csplit -z -f 'cert' fullchain.pem '/-----BEGIN CERTIFICATE-----/' '{*}'
for x in cert*; do openssl x509 -in $x -noout -text; done
Apparently that's the "wrong" way and the more appropriate way is using the openssl crl2pkcs7
subcommand albeit we do not try to parse a revocation list here.
openssl crl2pkcs7 -nocrl -certfile fullchain.pem | \
openssl pkcs7 -print_certs -noout
Learned that one in a webinar presented by Victor Dukhovni. If you're new to the topic worth watching.
04 Dec 2024 5:23pm GMT
Enrico Zini: How to right click
I climbed on top of a mountain with a beautiful view, and when I started readying my new laptop for a work call (as one does on top of mountains), I realised that I couldn't right click and it kind of spoiled the mood.
Clicking on the bottom right corner of my touchpad left-clicked. Clicking with two fingers left-clicked. Alt-clicking, Super-clicking, Control-clicking, left clicked.
Here's there are two ways to simulate mouse buttons with touchpads in Wayland:
- clicking on different areas at the bottom of the touchpad
- double or triple-tapping, as long as the fingers are not too far apart
Skippable digression:
I'm not sure why Gnome insists in following Macs for defaults, which is what people with non-Mac hardware are less likely to be used to.
In my experience, Macs are as arbitrarily awkward to use as anything else, but they managed to build a community where if you don't understand how it works you get told you're stupid. All other systems (including Gnome) have communities where instead you get told (as is generally the case) that the system design is stupid, which at least gives you some amount of validation in your suffering.
Oh well.
How to configure right click
Surprisingly, this is not available in Gnome Shell settings. It can be found in gnome-tweaks: under "Keyboard & Mouse", "Mouse Click Emulation", one can choose between "Fingers" or "Area".
I tried both and went for "Area": I use right-drag a lot to resize windows, and I couldn't find a way, at least with this touchpad, to make it work consistently in "Fingers" mode.
04 Dec 2024 4:51pm GMT
Bits from Debian: "Ceratopsian" will be the default theme for Debian 13
The theme "Ceratopsian" by Elise Couper has been selected as the default theme for Debian 13 "trixie". The theme is inspired by Trixie's (the fictional character from Toy Story) frill and is also influenced by a previously used theme called "futurePrototype" by Alex Makas.
After the Debian Desktop Team made the call for proposing themes, a total of six choices were submitted. The desktop artwork poll was open to the public, and we received 2817 responses ranking the different choices, of which Ceratopsian has been ranked as the winner among them.
We'd like to thank all the designers that have participated and have submitted their excellent work in the form of wallpapers and artwork for Debian 13.
Congratulations, Elise, and thank you very much for your contribution to Debian!
04 Dec 2024 12:30pm GMT
03 Dec 2024
Planet Debian
Russ Allbery: Review: Astrid Parker Doesn't Fail
Review: Astrid Parker Doesn't Fail, by Ashley Herring Blake
Series: | Bright Falls #2 |
Publisher: | Berkley Romance |
Copyright: | November 2022 |
ISBN: | 0-593-33644-5 |
Format: | Kindle |
Pages: | 365 |
Astrid Parker Doesn't Fail is a sapphic romance novel and a sequel to Delilah Green Doesn't Care. This is a romance style of sequel, which means that it spoils the previous book but involves a different set of protagonists, one of whom was a supporting character in the previous novel.
I suppose the title is a minor spoiler for Delilah Green Doesn't Care, but not one that really matters.
Astrid Parker's interior design business is in trouble. The small town of Bright Falls doesn't generate a lot of business, and there are limits to how many dentist office renovations that she's willing to do. The Everwood Inn is her big break: Pru Everwood has finally agreed to remodel and, even better, Innside America wants to feature the project. The show always works with local designers, and that means Astrid. National TV exposure is just what she needs to turn her business around and avoid an unpleasant confrontation with her domineering, perfectionist mother.
Jordan Everwood is an out-of-work carpenter and professional fuck-up. Ever since she lost her wife, nothing has gone right either inside or outside of her head. Now her grandmother is renovating the favorite place of her childhood, and her novelist brother had the bright idea of bringing her to Bright Falls to help with the carpentry work. The remodel and the HGTV show are the last chance for the inn to stay in business and stay in the family, and Jordan is terrified that she's going to fuck that up too. And then she dumps coffee all over the expensive dress of a furious woman in a designer dress because she wasn't watching where she was going, and that woman turns out to be the designer of the Everwood Inn renovation. A design that Jordan absolutely loathes.
The reader met Astrid in Delilah Green Doesn't Care (which you definitely want to read first). She's a bit better than she was there, but she's still uptight and unhappy and determined not to think too hard about why. When Jordan spills coffee down her favorite dress in their first encounter, shattering her fragile professional calm, it's not a meet-cute. Astrid is awful to her. Her subsequent regret, combined with immediately having to work with her and the degree to which she finds Jordan surprisingly attractive (surprising in part because Astrid thinks she's straight), slowly crack open Astrid's too-controlled life.
This book was, once again, just compulsively readable. I read most of it the same day that I started it, staying up much too late, and then finished it the next day. It also once again made me laugh in delight at multiple points. I am a sucker for stories about someone learning how to become a better person, particularly when it involves a release of anxiety, and oh my does Blake ever deliver on that. Jordan's arc is more straightforward than Astrid's - she just needs to get her confidence back - but her backstory is a lot more complex than it first appears, including a morally ambiguous character who I would hate in person but who I admired as a deft and tricky bit of characterization.
The characters from Delilah Green Doesn't Care of course play a significant role. Delilah in particular is just as much of a delight here as she was in the first book, and I enjoyed seeing the development of her relationship with her step-sister. But the new characters, both the HGTV film crew and the Everwoods, are also great. I think Blake has a real knack for memorable, distinct supporting characters that add a lot of depth to the main romance plot.
I thought this book was substantially more sex-forward than Delilah Green Doesn't Care, with some lust at first or second sight, a bit more physical description of bodies, and an extended section in the middle of the book that's mostly about sex. If this is or is not your thing in romance novels, you may have a different reaction to this book than the previous one.
There is, unfortunately, another third-act break-up, and this one annoyed me more than the one in Delilah Green Doesn't Care because it felt more unnecessary and openly self-destructive. The characters felt like they were headed towards a more sensible and less dramatic resolution, and then that plot twist caught me by surprise in an unpleasant way. After two books, I'm getting the sense that Blake has a preferred plot arc, at least in this series, and I wish she'd varied the story structure a bit more. Still, the third-act conflict was somewhat believable and the resolution was satisfying enough to salvage it.
If it weren't for some sour feelings about the shape of that plot climax, I would have said that I liked this book even better than Delilah Green Doesn't Care, and that's a high bar. This series is great, and I will definitely be reading the third one. I'm going to be curious how that goes since it's about Iris, who so far has worked better for me as a supporting character than a protagonist. But Blake has delivered compulsively readable and thoroughly enjoyable books twice now, so I'm definitely here for the duration.
If you like this sort of thing, I highly recommend this whole series.
Followed by Iris Kelly Doesn't Date in the romance series sense, but as before this book is a complete story with a satisfying ending.
Rating: 9 out of 10
03 Dec 2024 3:26am GMT
02 Dec 2024
Planet Debian
Bits from Debian: Bits from the DPL
This is bits from DPL for November.
MiniDebConf Toulouse
I had the pleasure of attending the MiniDebConf in Toulouse, which featured a range of engaging talks, complementing those from the recent MiniDebConf in Cambridge. Both events were preceded by a DebCamp, which provided a valuable opportunity for focused work and collaboration.
DebCamp
During these events, I participated in numerous technical discussions on topics such as maintaining long-neglected packages, team-based maintenance, FTP master policies, Debusine, and strategies for separating maintainer script dependencies from runtime dependencies, among others. I was also fortunate that members of the Publicity Team attended the MiniDebCamp, giving us the opportunity to meet in person and collaborate face-to-face.
Independent of the ongoing lengthy discussion on the Debian Devel mailing list, I encountered the perspective that unifying Git workflows might be more critical than ensuring all packages are managed in Git. While I'm uncertain whether these two questions--adopting Git as a universal development tool and agreeing on a common workflow for its use--can be fully separated, I believe it's worth raising this topic for further consideration.
Attracting newcomers
In my own talk, I regret not leaving enough time for questions--my apologies for this. However, I want to revisit the sole question raised, which essentially asked: Is the documentation for newcomers sufficient to attract new contributors? My immediate response was that this question is best directed to new contributors themselves, as they are in the best position to identify gaps and suggest improvements that could make the documentation more helpful.
That said, I'm personally convinced that our challenges extend beyond just documentation. I don't get the impression that newcomers are lining up to join Debian only to be deterred by inadequate documentation. The issue might be more about fostering interest and engagement in the first place.
My personal impression is that we sometimes fail to convey that Debian is not just a product to download for free but also a technical challenge that warmly invites participation. Everyone who respects our Code of Conduct will find that Debian is a highly diverse community, where joining the project offers not only opportunities for technical contributions but also meaningful social interactions that can make the effort and time truly rewarding.
In several of my previous talks (you can find them on my talks page -just search for "team," and don't be deterred if you see "Debian Med" in the title; it's simply an example), I emphasized that the interaction between a mentor and a mentee often plays a far more significant role than the documentation the mentee has to read. The key to success has always been finding a way to spark the mentee's interest in a specific topic that resonates with their own passions.
Bug of the Day
In my presentation, I provided a brief overview of the Bug of the Day initiative, which was launched with the aim of demonstrating how to fix bugs as an entry point for learning about packaging. While the current level of interest from newcomers seems limited, the initiative has brought several additional benefits.
I must admit that I'm learning quite a bit about Debian myself. I often compare it to exploring a house's cellar with a flashlight -you uncover everything from hidden marvels to things you might prefer to discard. I've also come across traces of incredibly diligent people who have invested their spare time polishing these hidden treasures (what we call NMUs). The janitor, a service in Salsa that automatically updates packages, fits perfectly into this cellar metaphor, symbolizing the ongoing care and maintenance that keep everything in order. I hadn't realized the immense amount of silent work being done behind the scenes--thank you all so much for your invaluable QA efforts.
Reproducible builds
It might be unfair to single out a specific talk from Toulouse, but I'd like to highlight the one on reproducible builds. Beyond its technical focus, the talk also addressed the recent loss of Lunar, whom we mourn deeply. It served as a tribute to Lunar's contributions and legacy. Personally, I've encountered packages maintained by Lunar and bugs he had filed. I believe that taking over his packages and addressing the bugs he reported is a meaningful way to honor his memory and acknowledge the value of his work.
Advent calendar bug squashing
I'd like to promote an idea originally introduced by Thorsten Alteholz, who in 2011 proposed a Bug Squashing Advent Calendar for the Debian Med team. (For those unfamiliar with the concept of an Advent Calendar, you can find an explanation on Wikipedia.) While the original version included a fun graphical element -which we've had to set aside due to time constraints (volunteers, anyone?)- we've kept the tradition alive by tackling one bug per day from December 1st to 24th each year. This initiative helps clean up issues that have accumulated over the year.
Regardless of whether you celebrate the concept of Advent, I warmly recommend this approach as a form of continuous bug-squashing party for every team. Not only does it contribute to the release readiness of your team's packages, but it's also an enjoyable and bonding activity for team members.
Best wishes for a cheerful and productive December
Andreas.
02 Dec 2024 11:00pm GMT
Dirk Eddelbuettel: anytime 0.3.10 on CRAN: Multiple Enhancements
A new release of the anytime package arrived on CRAN today-the first is well over four years. The package is fairly feature-complete, and code and functionality remain mature and stable, of course.
anytime is a very focused package aiming to do just one thing really well: to convert anything in integer, numeric, character, factor, ordered, … input format to either POSIXct (when called as anytime
) or Date objects (when called as anydate
) - and to do so without requiring a format string as well as accomodating different formats in one input vector. See the anytime page, or the GitHub repo for a few examples, and the beautiful documentation site for all documentation.
This release slowly matured over four years. It combines a number of strictly internal repository maintenance such as changes to continuous integration with small enhancements (adding for example some new formats, responding better to an error condition, dealing with logical input as an error) with a relaxation of the C++ compilation standard. While we once needed C++11, it is now a constraint as as R itself is quite proactive (the last two releases defaulted already to C++17, suitable compiler permitting) we can now relax this constraint. The documentation site is new, as some other small changes. See the full list of changes which follows.
Changes in anytime version 0.3.10 (2024-12-02)
A new documentation site was added.
Continuous Integration now uses
run.sh
from r-ci with bspmLogical input vectors are now recognised as an error (#121)
Additional dot-separated format
'%Y.%m.%d'
is supportedOther small updates were made throughout the package
No longer set a C++ compilation standard as the default choices by R are sufficient for the package
Switch Rcpp include file to Rcpp/Lightest
We recommend
~/.R/Makevars
compiler flag options-Wno-ignored-attributes -Wno-nonnull -Wno-parentheses
The tinytest runner was simplified
NA
values from conversion now trigger a warning
Courtesy of my CRANberries, there is also a diffstat report of changes relative to the previous release. The issue tracker tracker off the GitHub repo can be use for questions and comments. More information about the package is at the package page, the GitHub repo and the documentation site. If you like this or other open-source work I do, you can now sponsor me at GitHub.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
02 Dec 2024 10:01pm GMT
Jonathan Dowland: jungle/acid/etc
I thought it had been a full year since I last shared a playlist, but it's been two! I had a plan to produce more, but it seems I haven't. Instead here's a few tracks I've discovered recently which share a common theme.
In August I stumbled across a Sound on Sound video interviewing Pete Cannon, who creates authentically old-school Jungle music using tools and techniques from the time, including AKAI samplers and the Commodore Amiga computer.
Here's three tracks that I found since then. Some 8-bit Amiga-jungle,
some slower-paced acid house from someone ostensibly based on Whitley Bay,
and a darker piece I heard on the radio.
02 Dec 2024 10:00pm GMT
Junichi Uekawa: Graph for my furusato tax.
Graph for my furusato tax. Exceeding 150-man will inevitably exceed 50-man limit for Ichiji-shotoku. So added some rough calculation there. graph.
02 Dec 2024 5:39am GMT
Russ Allbery: Review: Long Live Evil
Review: Long Live Evil, by Sarah Rees Brennan
Series: | Time of Iron #1 |
Publisher: | Orbit |
Copyright: | July 2024 |
ISBN: | 0-316-56872-4 |
Format: | Kindle |
Pages: | 433 |
Long Live Evil is a portal fantasy (or, arguably more precisely, a western take on an isekai villainess fantasy) and the first book of a series. If the author's name sounds familiar, it's possibly because of In Other Lands, which got a bunch of award nominations in 2018, She has also written a lot of other YA fantasy, but this is her first adult epic fantasy novel.
Rae is in the hospital, dying of cancer. Everything about that experience, from the obvious to the collapse of her friendships, absolutely fucking sucks. One of the few bright points is her sister's favorite fantasy series, Time of Iron, which her sister started reading to her during chemo sessions. Rae mostly failed to pay attention until the end of the first book and the rise of the Emperor. She fell in love with the brooding, dangerous anti-hero and devoured the next two books. The first book was still a bit hazy, though, even with the help of a second dramatic reading after she was too sick to read on her own.
This will be important later.
After one of those reading sessions, Rae wakes up to a strange woman in her hospital room who offers her an option. Rather than die a miserable death that bankrupts her family, she can go through a door to Eyam, the world of Time of Iron, and become the character who suits her best. If she can steal the Flower of Life and Death from the imperial greenhouse on the one day a year that it blooms, she will wake up, cured. If not, she will die. Rae of course goes through, and wakes in the body of Lady Rahela, the Beauty Dipped in Blood, the evil stepsister. One of the villains, on the night before she is scheduled to be executed.
Rae's initial panic slowly turns to a desperate glee. She knows all of these characters. She knows how the story will turn out. And she has a healthy body that's not racked with pain. Maybe she's not the heroine, but who cares, the villains are always more interesting anyway. If she's going to be cast as the villain, she's going to play it to the hilt. It's not like any of these characters are real.
Stories in which the protagonists are the villains are not new (Nimona and Hench come to mind just among books I've reviewed), but they are having a moment. Assistant to the Villain by Hannah Nicole Maehrer came out last year, and this book and Django Wexler's How to Become the Dark Lord and Die Trying both came out this year. This batch of villain books all take different angles on the idea, but they lean heavily on humor. In Long Live Evil, that takes the form of Rae's giddy embrace of villainous scheming, flouncing, and blatant plot manipulation, along with her running commentary on the various characters and their in-story fates.
The setup here is great. Rae is not only aware that she's in a story, she knows it's full of cliches and tropes. Some of them she loves, some of them she thinks are ridiculous, and she isn't shy about expressing both of those opinions. Rae is a naturally dramatic person, and it doesn't take her long to lean into the opportunities for making dramatic monologues and villainous quips, most of which involve modern language and pop culture references that the story characters find baffling and disconcerting.
Unfortunately, the base Time of Iron story is, well, bad. It's absurd grimdark epic fantasy with paper-thin characters and angst as a central character trait. This is clearly intentional for both in-story and structural reasons. Rae enjoys it precisely because it's full of blood and battles and over-the-top brooding, malevolent anti-heroes, and Rae's sister likes the impossibly pure heroes who suffer horrible fates while refusing to compromise their ideals. Rae is also about to turn the story on its head and start smashing its structure to try to get herself into position to steal the Flower of Life and Death, and the story has to have a simple enough structure that it doesn't get horribly confusing once smashed. But the original story is such a grimdark parody, and so not my style of fantasy, that I struggled with it at the start of the book.
This does get better eventually, as Rae introduces more and more complications and discovers some surprising things about the other characters. There are several delightful twists concerning the impossibly pure heroine of the original story that I will not spoil but that I thought retroactively made the story far more interesting. But that leads to the other problem: Rae is both not very good at scheming, and is flippant and dismissive of the characters around her. These are both realistic; Rae is a young woman with cancer, not some sort of genius mastermind, and her whole frame for interacting with the story is fandom discussions and arguments with her sister. Early in the book, it's rather funny. But as the characters around her start becoming more fleshed out and complex, Rae's inability to take them seriously starts to grate. The grand revelation to Rae that these people have their own independent existence comes so late in the book that it's arguably a spoiler, but it was painfully obvious to everyone except Rae for hundreds of pages before it got through Rae's skull.
Those are my main complaints, but there was a lot about this book that I liked. The Cobra, who starts off as a minor villain in the story, is by far the best character of the book. He's not only more interesting than Rae, he makes everyone else in the book, including Rae, more interesting characters through their interactions. The twists around the putative heroine, Lady Rahela's stepsister, are a bit too long in coming but are an absolute delight. And Key, the palace guard that Rae befriends at the start of the story, is the one place where Rae's character dynamic unquestionably works. Key anchors a lot of Rae's scenes, giving them a sense of emotional heft that Rae herself would otherwise undermine.
The narrator in this book does not stick with Rae. We also get viewpoint chapters from the Cobra, the Last Hope, and Emer, Lady Rahela's maid. The viewpoints from the Time of Iron characters can be a bit eye-roll-inducing at the start because of how deeply they follow the grimdark aesthetic of the original story, but by the middle of the book I was really enjoying the viewpoint shifts. This story benefited immensely from being seen from more angles than Rae's chaotic manipulation. By the end of the book, I was fully invested in the plot line following Cobra and the Last Hope, to the extent that I was a bit disappointed when the story would switch back to Rae.
I'm not sure this was a great book, but it was fun. It's funny in places, but I ended up preferring the heartfelt parts to the funny parts. It is a fascinating merger of gleeful fandom chaos and rather heavy emotional portrayals of both inequality and the experience of terminal illness. Rees Brennan is a stage four cancer survivor and that really shows; there's a depth, nuance, and internal complexity to Rae's reactions to illness, health, and hope that feels very real. It is the kind of book that can give you emotional whiplash; sometimes it doesn't work, but sometimes it does.
One major warning: this book ends on a ridiculous cliffhanger and does not in any sense resolve its main plot arc. I found this annoying, not so much because of the wait for the second volume, but because I thought this book was about the right length for the amount of time I wanted to spend in this world and wish Rees Brennan had found a way to wrap up the story in one book. Instead, it looks like there will be three books. I'm in for at least one more, since the story was steadily getting better towards the end of Long Live Evil, but I hope the narrative arc survives being stretched out across that many words.
This one's hard to classify, since it's humorous fantasy on the cover and in the marketing, and that element is definitely present, but I thought the best parts of the book were when it finally started taking itself seriously. It's metafictional, trope-subverting portal fantasy full of intentional anachronisms that sometimes fall flat and sometimes work brilliantly. I thought the main appeal of it would be watching Rae embrace being a proper villain, but then the apparent side characters stole the show. Recommended, but you may have to be in just the right mood.
Content notes: Cancer, terminal illness, resurrected corpses, wasting disease, lots of fantasy violence and gore, and a general grimdark aesthetic.
Rating: 7 out of 10
02 Dec 2024 5:26am GMT
Charles: Hello World
Or how it took more than a year for me to set up this website -
As the computer science tradition demands, we must start with a Hello World.
Though I have to say this hello world took quite a long time to reach the internet. I've been thinking about setting up this website for way over a year, but there are always too many things to decide - what Static Site Generator will I use? Where should I get a domain from? Which registrar would be better now? What if I want to set up a mail server, is it good enough? Oh, and what about the theme, which one to choose? Can I get one simple enough to not fetch javascript or css from external sources?
This was taking so long that even my friends were saying "Please, just share your screen and let's do it now!". Well, rejoice friends, now it's done!
02 Dec 2024 2:18am GMT
01 Dec 2024
Planet Debian
Guido Günther: Free Software Activities November 2024
Another short status update of what happened on my side last month. The larger blocks are the Phosh 0.43 release, the initial file chooser portal, phosh-osk-stub now handling digit, number, phone and PIN input purpose via special layouts as well as Phoc mostly catching up with wlroots 0.18 and the current development version targeting 0.19.
phosh
- When taking a screenshot via keybinding or power button long press save screenshots to clipboard and disk (MR)
- Robustify Screenshot CI job (MR)
- Update CI pipeline (MR)
- Fix notifications banners that aren't tall enough not being shown (MR). Another 4y old bug hopefully out of the way.
- Add rfkill mock and docs (MR). Useful for HKS testing.
- Release 0.43~rc1 and 0.43
- Drop libsoup workaround (MR)
- Ensure notification only takes its actual height (MR)
phoc
- Move wlroots 0.18 update forward (MR). Needs a bit more work before we can make it default.
- Catch up with wlroots development branch (MR) allowing us to test current wlroots again.
- Some of the above already applies to main so schedule it for 0.44 (MR)
phosh-mobile-settings
libphosh-rs
phosh-osk-stub
- Add layouts for PIN, number and phone input purpose (MR)
- Release 0.43~rc1
- Ensure translation get picked up, various cleanups and release 0.43.0 (MR)
- Make desktop file match app-id (MR)
phosh-tour
- Fix typo and reduce number of strings to translate (MR)
- Add translator comments (MR). This, the above and additional fixes in p-m-s were prompted by i18n feedback from Alexandre Franke, thanks a lot!
- Release 0.43.0
pfs
- Initial version of the adaptive file chooser dialog using gtk-rs. See demo.
- Allow to activate via double click (for non-touch use) (MR)
xdg-desktop-portal-phosh
- Use pfs to provide a file chooser portal (MR)
meta-phosh
- Slightly improve point release handling (MR)
- Improve string freeze announcements and add phosh-tour (MR)
Debian
- Upload Phosh 0.43.0~rc1 and 0.43.0 (MR, MR, MR, MR, MR, MR, MR, MR, MR, MR, MR)
- meta-phosh: Add
Recommend:
forxdg-desktop-portal-phosh
(MR) - phosh-osk-data got accepted, create repo, brush up packaging and upload to unstable (MR
- phosh-osk-stub: Recommend data packager (MR
- Phosh: drop reverts (MR)
- varnam-schemes: Fix autopkgtest (MR)
- varnam-schemes: Improve packaging (MR)
- Prepare govarnam 1.9.1 (MR)
Calls
- ussd: Set input purpose and switch to
AdwDialog
(MR, Screenshot)
libcall-ui
- Drop libhandy leftover (MR)
git-buildpackage
- Improve docs and cleanup markdown (MR)
- Mention gbp push in intro (MR)
- Use application instead of productname entities to improve reading flow (MR)
wlroots
- Drop mention of
wlr_renderer_begin_with_buffer
(MR)
python-dbusmock
- Add mock for gsd-rfkill (MR)
xdg-spec
- Sync notification categories with the portal spec (MR)
- Add categories for SMS (MR)
- Add a
pubdate
so it's clear the specs aren't stale (MR) (got fixed in a different and better way, thanks Matthias!)
ashpd
- Allow to set filters in file chooser portal demo (MR)
govarnam
- Robustify file generation (MR)
varnam-schemes
- Unbreak tests on non intel/amd architectures (e.g. arm64) (MR)
Reviews
This is not code by me but reviews I did on other peoples code. The list is incomplete, but I hope to improve on this in the upcoming months. Thanks for the contributions!
- flathub: livi runtime and gst update (MR)
- phosh: Split linters into their own test suite (MR)
- phosh; QuickSettings follow-up (MR)
- phosh: Accent color fixes (MR)
- phosh: Notification animation (MR)
- phosh: end-session dialog timeout fix (MR)
- phosh: search daemon (MR)
- phosh-ev: Migrate to newer gtk-rs and async_channel (MR)
- phosh-mobile-settings: Update gmobile (MR)
- phosh-mobile-settings: Make panel-switcher scrollable (MR)
- phosh-mobile-settings: i18n comments (MR)
- gbp doc updates (MR)
- gbp handle suite names with number prefix (MR)
- Debian libvirt dependency changes (MR
- Chatty: misc improvements (MR
- iio-sensor-proxy: buffer driver without trigger (MR)
- gbp doc improvements (MR)
- gbp: More doc improvements (MR)
- gbp: Clean on failure (MR)
- gbp: DEP naming consistency (MR)
Help Development
If you want to support my work see donations. This includes a list of hardware we want to improve support for. Thanks a lot to all current and past donors.
Comments?
Join the Fediverse thread
01 Dec 2024 6:55pm GMT
Colin Watson: Free software activity in November 2024
Most of my Debian contributions this month were sponsored by Freexian.
You can also support my work directly via Liberapay.
Conferences
I attended MiniDebConf Toulouse 2024, and the MiniDebCamp before it. Most of my time was spent with the Freexian folks working on debusine; Stefano gave a talk about its current status with a live demo (frantically fixed up over the previous couple of days, as is traditional) and with me and others helping to answer questions at the end. I also caught up with some people I haven't seen in ages, ate a variety of delicious cheeses, and generally had a good time. Many thanks to the organizers and sponsors!
After the conference, Freexian collaborators spent a day and a half doing some planning for next year, and then went for an afternoon visiting the Cité de l'espace.
Rust team
I upgraded these packages to new upstream versions, as part of upgrading pydantic and rpds-py:
- rust-archery
- rust-jiter (noticing an upstream test bug in the process)
- rust-pyo3 (fixing CVE-2024-9979)
- rust-pyo3-build-config
- rust-pyo3-ffi
- rust-pyo3-macros
- rust-pyo3-macros-backend
- rust-regex
- rust-regex-automata
- rust-regex
- rust-serde
- rust-serde-derive
- rust-serde-json
- rust-speedate
- rust-triomphe
Python team
Last month, I mentioned that we still need to work out what to do about the multipart vs. python-multipart name conflict in Debian (#1085728). We eventually managed to come up with an agreed plan; Sandro has uploaded a renamed binary package to experimental, and I've begun work on converting reverse-dependencies (asgi-csrf, fastapi, python-curies, and starlette done so far). There's a bit more still to do, but I expect we can finish it soon.
I fixed problems related to adding Python 3.13 support in:
- coreapi
- git-repo-updater
- offlineimap3
- ptyprocess
- pytest-testinfra
- python-formencode
- python-iniparse
- python-line-profiler
- python-parameterized
- python-sdjson (contributed upstream)
- python-testfixtures (contributed upstream)
- python-venusian
- sphinx-a4doc (contributed upstream, and I also made a small antlr4 improvement)
- webpy
I fixed some packaging problems that resulted in failures any time we add a new Python version to Debian:
I fixed other build/autopkgtest failures in:
- psycopg3 (contributed upstream)
- python-aiohttp
- python-cotengrust
- python-distutils-extra
- python-formencode
- python-openapi-schema-validator
- python-openapi-spec-validator
- sphinxcontrib-towncrier
I packaged python-quart-trio, needed for a new upstream version of python-urllib3, and contributed a small packaging tweak upstream.
I backported a twisted fix that caused problems in other packages, including breaking debusine's tests.
I disentangled some upstream version confusion in python-catalogue, and upgraded to the current upstream version.
I upgraded these packages to new upstream versions:
- aioftp (fixing a Python 3.13 failure)
- ansible-core
- ansible
- debugpy
- jsonpickle
- manuel
- psycopg2
- pydantic-core
- pydantic
- pydantic-settings
- pymssql (fixing a Python 3.13 failure)
- pyodbc (fixing a Python 3.13 failure)
- python-argh (fixing a Python 3.13 failure)
- python-boltons (fixing a Python 3.13 failure)
- python-channels-redis
- python-colorlog (fixing a Python 3.13 failure)
- python-django-pgtrigger
- python-line-profiler
- python-pathvalidate (fixing a Python 3.13 failure)
- python-plac (fixing a Python 3.13 failure)
- python-precis-i18n
- python-pure-eval (fixing a Python 3.13 failure)
- python-pythonjsonlogger (contributing a small packaging fix upstream, as well as a test fix to jupyter-events)
- python-rdata (fixing a Python 3.13 failure)
- python-semantic-release
- python-telethon (fixing a Python 3.13 failure, and contributing some test fixes upstream)
- python-tornado (fixing CVE-2024-52804)
- python-trio (fixing a Python 3.13 failure)
- python-trustme
- python-typeguard
- python-urllib3 (fixing CVE-2024-37891 and a Python 3.13 failure, and requiring some shenanigans with its hypercorn test-dependency)
- python-zipp
- quart (fixing CVE-2024-49767)
- rpds-py (fixing a build failure)
- sen
- sqlparse
- stravalib
- transaction
- waitress
- zope.interface
Other small fixes
I contributed Incus support to needrestart upstream.
In response to Helmut's Cross building talk at MiniDebConf Toulouse, I fixed libfilter-perl to support cross-building (5b4c2e10, f9788c27).
I applied a patch to move aliased files from /
to /usr
in iprutils (#1087733).
I adjusted debconf to use the new /usr/lib/apt/apt-extracttemplates
path (#1087523).
I upgraded putty to 0.82.
01 Dec 2024 3:00pm GMT