[Pkg-rust-maintainers] Getting rid of the NEW step for binaries ?

[Sylvestre Ledru]

Le 17/10/2019 à 19:53, Thorsten Alteholz a écrit :
> Hi Sylvestre,
> 
> 
>> But this isn't an issue specific to Rust. Having to go through NEW when it is the same source (...)
> 
> I have no numbers at hand, but I got the impression that most rust packages still have a changelog entry like "new upstream release" when they enter NEW.
Yeah, i meant source in the "Source:" in the debian/control ;)
This is indeed what triggers the NEW.


> 
>>>  From looking at the package with the insane large Provides field, it
>>> seems like it creates empty binary packages to avoid some dependencies
>>> on other development packages to safe ~50k of downloads?  I would
>>> suggest to just accept the 50k extra downloads for packages for people
>>> using the rust development packages rather than creating extra binary
>>> packages.
>>
>> Sure but this isn't directly related to this discussion. I also do agree that we should address this issue.
> 
> NEW existed before rust and you created a tooling that sends packages frequently through NEW. From my point of view there is a relation.
Well, even if the ftp team fast tracked my llvm packages when I asked (thanks again), sometimes, I had to wait a month to get llvm-toolchain-* approved.


> But I am not really convinced that rust packages should be on it as well.
Why?

Sylvestre