[Pkg-rust-maintainers] Bug#1013121: rust-winreg: please upgrade to v0.7

[Peter Green]

> Please upgrade to upstream branch v0.7, needed by projects I am
> preparing for Debian.

There are a number of reverse dependencies.

> 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-winreg -spackage
> Package: rust-gpgme-sys
> Package: rust-ipconfig
> Package: rust-reqwest
> Package: rust-winreg
> Package: librust-gpgme-sys-dev
> Package: librust-ipconfig-dev
> Package: librust-reqwest-dev
> Package: librust-winreg+serde-dev
> Package: librust-winreg+serialization-serde-dev
> Package: librust-winreg+transactions-dev
> Package: librust-winreg-dev
> plugwash at coccia:~$
gpgme-sys upstream depends on 0.9 and is currently downpatched to 0.6
in debian.

the version of ipconfig in Debian is not patching the dependency version
but the newest upstream version uses 0.6, ipconfig doesn't seem to
have any reverse dependencies in Debian.

reqwest is currently badly broken in Debian but the latest upstream
version depends on winreg 0.10

The bigger-question though IMO is what should we do about windows-specific
dependencies. Packing n different versions in parallel is not reasonable.
IMO neither is expecting Debian developers to test on Windows. So the question
becomes do we blindly patch the version of said dependency without actually
checking if the result works? or do we just patch away the dependency
completely? currently we seem to be doing a mixture of the two approaches.