[Pkg-rust-maintainers] Bug#931003: Fixing rust package FTBFS in buster (was: Bug#931003: Removed package(s) from unstable )

[peter green]

On 04/05/2021 12:28, Santiago Vila wrote:
> On Tue, May 04, 2021 at 11:48:09AM +0100, peter green wrote:
>>> This was automatically closed by ftpmaster because the package was
>>> removed from unstable, but this still does not fix the FTBFS problem
>>> in stable.
>>
>> Unfortunately I don't think a proper fix will be forthcoming, upstream
>> has abandoned the crate in question.
> 
> It does not need to be a perfect fix. It is enough that dpkg-buildpackage
> exits with status 0. If the tests are no longer valid, disabling them
> should be much better than nothing, because packages in stable must
> build in stable.

I'm prepared prepare such uploads if the stable release managers
are prepared to accept them.

> 
>>> There are already 74 packages which FTBFS in stable (by my count),
>>
>> Do you have a list?
> 
> Last time I tried this is what I found:
> 
> https://people.debian.org/~sanvila/ftbfs-in-buster/

Thanks, looks like I misinterpreted your number as referring to rust packages
specifically rather than to all packages. Looks like there are four rust
packages in your FTBFS lists. The good news is that none of them seem to
be applications.

Of the four

rust-simd: abandoned upstream, not in testing/unstable probably not properly fixible, could disable test build during package build to fix FTBFS.
rust-coresimd: abandoned upstream, not in testing/unstable probably not properly fixible, could disable test build during package build to fix FTBFS.
rust-nodrop-union: abandoned upstream, not in testing, broken in unstable probably not properly fixible, could disable test build during package build to fix FTBFS.
rust-rustyline: fixed upstream and in testing/unstable, I was able to bisect and backport the fix (see bug 988025 )