[Pkg-rust-maintainers] Migration of block-padding

[Peter Green]

> 
> It doesn't migrate due to a librust-block-buffer-0.9 depending on the
> old version.

Indeed, personally I was planning to just wait for auto-removals to
remove block-buffer-0.9 and it's rdeps from testing at which point
block-padding should migrate.


> cid-npm depends on ipfs-unixfs but that package have never entered
> testing it seems like: https://tracker.debian.org/pkg/rust-cid-npm

Yes it did enter testing and even stable. It was removed from testing
by auto-removals at the beginning of this month.

It might be nice to investigate if cid-npm can be patched to use the fork
of unixfs.

> 
> ipfs-unixfs seems to be abandoned but someone have forked it and
> published new versions under a new name:

I see the fork no longer depends on multihash. So if cid-npm can be
patched to use unixfs and ipfs-unixfs is removed that gives us a
way forward.

> I ran './dev/list-rdeps.sh sha3-0.9' that didn't list any rdeps

I have found list-rdeps.sh to be untrustworthy.

Personally I use grep-dctrl on mirror.ftp-master.debian.org, but
that does sometimes produce false-positives and I don't think
non-dds can log in there (though you could achive the same by
downloading the correspoding files from a public mirror).

plugwash at coccia:~$ zcat /srv/ftp.debian.org/mirror/dists/sid/main/source/Sources.gz /srv/ftp.debian.org/mirror/dists/sid/main/binary-amd64/Packages.gz | grep -v Testsuite-Triggers | grep-dctrl rust-sha3-0.9 -spackage
Package: rust-multihash
Package: rust-sha3-0.9
Package: ipfs-cid
Package: librust-multihash-dev
Package: librust-sha3-0.9+std-dev
Package: librust-sha3-0.9-dev
plugwash at coccia:~$

> 1: I close that delete request

Lets just leave the moreinfo tag on it for now. When the rdeps are dealt with then
the moreinfo tag can go.

 > and prepare an upload of block-padding-0.2

I'd really rather we did not go further down that road.

There are times when semver-suffix packages are appropriate, for example
if the number of rdeps is very large, or the changes amount to a major
re-write/redesign, but they should not be seen as a substitute for making
a reasonable effort to keep up with new versions of the packages you depend
on.

> I'm happy to help out if you need any help, but don't know with
> exactly what if you are also planning to look at it, maybe I can take
> a stab at upgrading multihash to 0.19 unless someone else is working
> on that.

The main thing appears to be that someone needs to package the
core2 crate.