[Pkg-rust-maintainers] Bug#1072909: rust-loom: please upgrade to v0.7

Jonas Smedegaard dr at jones.dk
Fri Aug 15 10:00:44 BST 2025


Quoting Fab Stz (2025-08-15 10:25:21)
> Hi,
> 
> Le vendredi 15 ao�t 2025 09:29:18 CEST, vous avez �crit :
> > Quoting Fab Stz (2025-08-14 18:44:19)
> > > Dear Jonas,
> > > 
> > > On Mon, 10 Jun 2024 09:19:11 +0200 Jonas Smedegaard <dr at jones.dk> wrote:
> > > > Source: rust-loom
> > > > Version: 0.5.6-2
> > > > Severity: normal
> > > > Tags: upstream
> > > > 
> > > > Please upgrade to, or separately provide, branch v0.7.
> > > > 
> > > 
> > > Do you still need this update? For which package(s)?
> > 
> > Yes, I need this for a few packages, and the Rust team for some more:
> > It is used for tests which in Debian are patched out:
> > 
> >   * async-lock
> >   * bytes
> >   * concurrent-queue
> >   * crossbeam-epoch
> >   * crossbeam-utils
> >   * event-listener
> >   * event-listener-strategy
> >   * oneshot
> >   * parking
> >   * sharded-slab
> >   * state
> >   * tokio
> > 
> > This future package needs it as well:
> > 
> >   * fractal (bug#900928), transitively via async_cell
> > 
> > > I used to need it for "state" 0.6 but dependency on loom 0.5 was patched
> > > out.
> > 
> > So in other words, you still need it, but have chosen to suppress that
> > need.
> 
> I think there is some misunderstanding. Given that loom doesn't build on all 
> supported debian arch but only amd64 and arm64, it was somehow decided that 
> this was not ideal for czkawka which is the final binay crate that depends on 
> "state" (which depends on loom).

Thank you for sharing. That sounds like something decided internally in
the Rust team, and sadly not communicated to Debian at large.

I can recommend such reasons for applying patches as DEP-3 headers to
patch themselves, and/or add a README.Debian or TODO notice about such
reasons for deviating from upstream.

Bonus points for such notes being very brief with a link to a more
elaborate explanation on the Debian wiki or some other public place,
but minus points for assuming that anyone interested is a Rust team
member and therefore already knew without stating anything in each
affected package.

> > > So you could adopt the package if you want.
> > 
> > Thank you (finally!).
> >
> > 
> > In future, please consider pouring a bit more effort into package
> > maintenance: I filed this bugreport a year ago, and have received only
> > silence and then you giving up.
> 
> As a team member, I thought you could update any package, anyway.

I am a Debian developer, but not a Rust team member.

> Please understand that I've started working on czkawka during the freeze of 
> bookworm. This required to have approx >80 packages sponsored by a DD and it 
> took almost 2 years to have sponsors (mostly werdahias, sylvestre and capitol 
> (not sure of the nick)) uploading all of them to the archive. I was granted DM 
> rights on rust packages on 2025-06-28, so less than 2 months ago. I think you 
> understand what all that means.

My criticism is targeted the plural "you": The Rust team, collectively,
who is listed as maintainer for the loom package where my bugreport has
seen no response for a year.

Sounds like you are doing a lot of exciting work on Rust packaging - I
wish you all the best with that. I don't see how any of that work is a
blocker for you or anyone else in the Rust team responding to my
bugreport much, much sooner, however.

> I prepared multiple NEW packages that are required to update czkawka to 9.0. I 
> haven't uploaded them all to master yet. Right now there are at least 7, and 
> more will come. But if you feel like willing to sponsor/upload them, please 
> do. See ./dev/list-rfs.sh. You could then give me DM upload rights for these 
> packages.

I am happy to team up with you, if you are interested in that. Our
collaboration would not be reduced to me granting you upload rights or
me rubber-stamping packaging solely done by you, however. It would also
not be done in a giant efficient-for-the-team git repo, but in
efficient-for-Debian-developers-in-general project-specific git repos.
I might sound like a stubborn narrowminded old fart - I sure hope that
is not the case, but perhaps I really am - if curious but want a second
opinion then perhaps ask Blair Noctis, whom I collaborate with for some
Rust packages.

Happy hacking,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 931 bytes
Desc: signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/attachments/20250815/56f0b1f7/attachment.sig>


More information about the Pkg-rust-maintainers mailing list