Hi,
there is https://rustsec.org/advisories/RUSTSEC-2023-0020.html which flags
that rust-const-cstr is unmaintained. Since there are no reverse deps in the
archive, let's exclude it from bookworm (or rather remove rightaway)?

Cheers,
        Moritz

Hi

The list-rdeps.sh script in
https://salsa.debian.org/rust-team/debcargo-conf/ shows that it's in
use:

$ ./dev/list-rdeps.sh const-cstr
Versions of rust-const-cstr in unstable:
  librust-const-cstr-dev                           0.3.0-1+b1

Versions of rdeps of rust-const-cstr in unstable, that also exist in testing:
  librust-yeslogic-fontconfig-sys-dev              3.0.1-1+b1
depends on     librust-const-cstr-0.3+default-dev,

And since unmaintained is just a notification about how fast the
maintainer responds, and not really a security problem in itself I
would rather not remove it as it might set of further deletions.

//Alex

severity 1033333 normal
retitle 1033333 rust-encoding is unmaintained upstream
severity 1033334 normal
retitle 1033334 rust-boxfnonce is unmaintained upstream
severity 1033335 normal
retitle 1033335 rust-const-cstr is unmaintained upstream

(summarising several bugs)

I don't know what tool you are using to check for reverse dependencies but
whatever it is does not seem to take account of virtual packages correctly.
(unfortunately I don't know of one that does, I personally resort to
grepping the packages/sources files which works but does produce some
false positives). Some other rust team members use list-rdeps.sh in the
debcargo-conf repository but that only seems to take account of packages
packaged through debcargo.

While I agree it's good to move away from crates that are abandoned upstream,
I think it's too late to do so for bookworm and I don't think any of these
crates are sensitive enough to consider such maintenance issues as rc.

daemonize has already moved away from boxfnonce upstream, and the latest
upstream git source for sccache has moved to the new version of daemonize
so this should be a fairly easy fix, but still probablly too instrusive
for the current stage in the release process.

I've filed upstream issies for the other two

https://github.com/yeslogic/fontconfig-rs/issues/35

https://github.com/sharkdp/bat/issues/2512