In other words, I don't see what value these bug reports are adding.
As long as the package is not in Debian Testing, there are very excellent
status pages developed by the Debian Release team to make us aware of the
problem. Additional bug reports informing us of what we already know
(uninstallable, bd-uninstallable, blah blah blah) do not add extra value, in
fact they reduce value by forcing us to close bug reports.
Best,
Ximin
Ximin Luo:
> Due to the nature of the Rust upstream ecosystem, bugs like this are expected
> from time to time as we update dependent crates.
>
> A reversion in terms of downgrading the version using +really-like schemes is
> not feasible at the current time, see
> https://salsa.debian.org/rust-team/debcargo/-/issues/31.
>
> rust-cargo is blocked on various crates in NEW. rust-debcargo is likewise
> blocked on rust-cargo.
>
> In the meantime I am happy for these packages to be kept out of Debian
> Testing as per britney's automated process; I performed the uploads of the
> dependency packages well aware that this sort of breakage would result. It is
> not against Debian Policy to have broken packages in Debian Unstable, that is
> exactly what it is for.
>
> Paul Gevers:
>> Control: reassign 998415 rust-cargo
>> Control: close 998415 0.57.0-1
>> Control: affects 998415 src:rust-serde src:rust-debcargo
>>
>> Hi Peter,
>>
>> On 04-11-2021 01:19, Peter Green wrote:
>>> Reassign 998415 rust-cargo
>>> Close 998415 0.57.0-1
>>> Thanks
>>
>> ^ Fixing this, the message wasn't sent to control@b.d.o
>>
>>> I can prepare a TPU upload if you would like. Or we can just wait it out
>>> and see what
>>> happens after the Packages pass new and Debcargo is updated.
>>
>> Depends on how long that's going to take and how the TPU would look
>> like. If this is taking long (the RC limit is 60 days), then please
>> contact the Release Team via an unblock request to discuss the potential
>> upload before uploading. An alternative (better from my RT perspective)
>> is to revert the new upstream version of rust-cargo, fix the issue in
>> unstable, have that migrate and then reupload the new upstream version
>> to unstable. That way the RT doesn't need to be further involved.
>>
>> Paul
>>
>>
>> ___
>> Pkg-rust-maintainers mailing list
>> pkg-rust-maintain...@alioth-lists.debian.net
>> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers
>>
>
>
--
GPG: ed25519/56034877E1F87C35
https://github.com/infinity0/pubkeys.git
