Please upgrade crate petgraph to v0.8.
-----BEGIN PGP SIGNATURE-----

wsG7BAEBCgBvBYJoos15CRAsfDFGwaABIUcUAAAAAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmenLu2fzlNx9Ksh8rJMFDph5kBqnTfyXNl9taBr9JN/
fhYhBJ/j6cNmkaaf9TzGhCx8MUbBoAEhAADWWw/8CSVcyy22LzC56FItqlmj2T/I
4Vo15w1Am6tFDSu54Wqtc+1FNkhrgeljCoLsgy3hEJUsSBT03Az5+zieXLhqQPBp
UXr9NTQEaqTSCcCLNS6yhcW/W7gJ7ifh4jmal+kawGv26IUQNbgFdZ8834qlAaJp
Q/iq4A5jGjKA6v5m2KvBCTn6aaSctxzJisph68pv7eF6S05mm8z8Uc1PfP7r3JuT
JoQUPnwPsvHiedHJlCXlY+xcfuKf3VLqC35m+bLNXeKgE5XrNqbMmysYrgNwM9wZ
mAJxltgxAHxc/94o5vp/tAvNlZJuBJGVn7hZ2jqTyTwYX7J9/vx3Rh2ElTNBzDGS
SdnVi6f6sEc/ZV6GP+PKVshbo+VKn2tMF4HX5ZasjU/ox5LNrqN/y2JV5Mx2tyYx
y6EbbDTlymyhAZFXjibIrhavbXM+YV8CZp1FixOJ1vCdcjaXnPZETEoq2OSIxMtQ
OFEt1XPcALB2REn/QMHDHs5OvIN8OmEZ52LHwNWAqviLWcczakbGhPM9lMWrnD0S
+ndiaWQXC61DZFRTCjkqDg6NrekoFLo+eghWeHIllHanRUkjJfNeRd7SyWkL9fF/
BaO9cxUEfa371aP7+GV8R35g43JITwTiTpPvdLO6E6iEPe8x6EUjYosrheHgxVHx
p0l3OgiyXnv4TyYvGXk=
=liWu
-----END PGP SIGNATURE-----

Quoting Jonas Smedegaard (2025-08-18 08:51:40)

Ping...

but slapping them on every bug is not going to get them actioned
faster and indeed may get the opposite response.

Quoting Peter Green (2025-09-24 01:33:20)

I was told¹ that if a Rust team bugreport had no response for a few
days then it's lost, and you need a ping.

 - Jonas

¹ lists.debian.org/3cb4ac0f-31e1-49e6-9901-73f66e5846b3@disroot.org

On the bug itself, as one would usually do for every bug, not debian-rust:

And I stress:

I also said

So no, it's not automatically lost. But it can become due to high
traffic, if no one does the things I listed.

Quoting NoisyCoil (2025-09-24 02:05:17)

I check the bugreport and see no activity there.

Do you mean to say that I am expected to hunt down notes scribbled
elsewhere?

 - Jonas

I can't speak for how others decide which bugs to work on. I tend to work from a mixture of sources including recent posts to the pkg-rust-maintainers mailing list (which receives all posts to rust team bug reports) and the udd bugs list for the team, I do look at older bugs but I can only action so many. Clogging up my personal inbox and the debian-rust list isn't going to change that.

It might be useful if you could somehow document which update requests are most important to you and/or which ones are most important to particular packaging efforts.

Jonas,

Could you be more patient? The Debian Rust team has been extremely
busy since Debian 13 was released. A quick search of
https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/ for
"accepted" in August and September shows approximately 1000 uploads,
which I think is impressive throughput. But with over 3000 Rust
packages in Debian, it's going to take time to catch up after the
Debian archive was frozen for most of the year.

Because of how versioning [1] works in Rust, an update of
rust-petgraph from 0.6.4-1 to 0.8 is basically a transition and
requires careful work to ensure that all reverse dependencies are
still buildable. This takes careful work and it takes time.

You are welcome to contribute packaging directly if you want to see
various Rust packages updated sooner. That of course requires
contributing using the established workflow for those packages.

By the way, larger Rust transitions have been scheduled at
https://salsa.debian.org/rust-team/debcargo-conf/-/issues/130

[1] https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#default-requirements

Thank you,
Jeremy Bícha

Hi Jeremy,

Quoting Jeremy Bícha (2025-09-24 17:11:19)

How patient? Days, weeks, months, years?

I already elaborated, that my ping - in this case after more than a
month of silence since my initial reporting - was done because it was
my understanding that bugreports not responded to within few days were
likely to have been missed. It was then clarified that getting missed
is not likely only possibly (or some such - please do correct me if I
still haven't understood it properly).

So please tell me, how patient do you ask me to be?

Should I give it 10 months of total silence before bothering anyone?
https://bugs.debian.org/1085170

Or is 11 months a nice timeframe, perhaps?
https://bugs.debian.org/1085170

I guess 7 months is too soon, with the freeze and all, right?
https://bugs.debian.org/1095580

Kind regards,

 - Jonas

You've reported a large number of "please update" bugs for Debian Rust
Maintainers packages since yesterday. The team is aware that many Rust
packages are outdated because all these packages have working
debian/watch integration and there are trackers that show when
packages are out of date.

I pointed out that the team has been very busy since the freeze was
lifted; we are working hard to catch up. Filing bugs isn't necessarily
helping since it takes extra time and work to handle all these extra
bug reports.

Although you used the word "please", asking for too many things too
quickly can be seen as demanding.

Thank you,
Jeremy Bícha

Quoting Peter Green (2025-09-24 02:42:51)

It might be helpful to be able to see which bugreports have not been
lost, e.g. by tagging as confirmed or pending.

I have now trawled through all Rust packages that I maintain, and
annotated the bugreports affecting them. I will try consistently do
that from now on.

I don't see how it is sensible to rank those bugreports - every
bugreport requires maintenance of at least one patch, regardless of how
"important" the change is from a user standpoint. With the "affects"
annotation you get a glimpse of the burden the issue is causing, but
only the tip of the iceberg: I also work on ~40 packages with binaries
which are not yet in Debian, and the annotation does not show how often
the patches need maintenance.

 - Jonas

Hi Jeremy,

I generally agree, but please also put Jonas' emails in the context of
recent discussion (2 days ago, see d-rust@l.d.o) where I explained due
to high traffic of the alioth mailing list some of the older bugs may
have been forgotten, and he could try pinging us. Of course a dozen +
pings may seem annoying, but I hope knowing the context in which they
were sent may make them feel less so.

Jonas, please understand that taking care of all the semver-breaking
updates you pinged us about during the last ~ 24hrs may well require
hundreds of uploads in multiple batches, so it will definitely take a
good while. If you need some updates earlier than others, let us know,
we will try prioritizing those.

Cheers!

Quoting NoisyCoil (2025-09-24 21:45:25)

I did not mean to imply "do all of this RIGHT NOW..." by my slew of new
bugreports, nor by the smaller amount of pinging old (and arguably not
old but just "maturing") bugreports.

 - Jonas

No problem, I understand, I didn't think you were :-)

Quoting Jeremy Bicha (2025-09-24 20:48:34)

Thanks for clarifying where you are coming from.

What I have filed bugreports for is packages carrying patches, which I
doubt is showing on any trackers.

If it feels offending that I wrote "please", then I can gladly save
those few key strokes when filing these bugreports.  Please state so
explicitly if that is preferred, as I have a tendency to misinterpret.

 - Jonas

Feel free to use "please" in your bug reports. I think we all have a
better understanding now that we have communicated more on Wednesday.

Thank you,
Jeremy Bícha

Based on reading the upstream changelog, I think fixedbitset and
petgraph should go in together.

The main blocker seems to be termwiz, it has a test failure with
the new fixedbitset that I'm not comfortable ignoring without input
from upstream.

rudof - no changes needed
rust-cargo-debstatus - fix uploaded to unstable
rust-cargo-lock - fix uploaded to unstable
rust-ena - fix uploaded to unstable
rust-lalrpop - no changes needed
rust-prost-build - no changes needed
rust-termwiz - new version of fixedbitset breaks tests, issue filed upstream
rust-tree-magic-mini - fix uploaded to unstable
settle - no changes needed
sourmash - broken and not in testing
thin-provisioning-tools - patch sent to existing bug report
trippy - bug report filed with patch