[Pkg-rust-maintainers] rust-jemallocator_0.3.2-1_amd64.changes is NEW

Sylvestre Ledru sylvestre at mozilla.com
Thu Jun 11 16:49:41 BST 2020

Le 11/06/2020 à 17:03, kpcyrd a écrit :
> On Sat, May 23, 2020 at 12:05:23PM -0700, Sean Whitton wrote:
>> Hello Sylvestre,
>> On Sat 23 May 2020 at 07:51PM +02, Sylvestre Ledru wrote:
>>> Oh, OK. It would have been nice to have a clear communication on this.
>>> We had some discussions with some ftpmasters but it wasn't clear to me
>>> it became a policy.
>>> Do you have a recommendation of the number of binary packages or long
>>> Provides
>>> (or know what will be accepted or not?)
>> I wouldn't say it's a policy.  It's just that team members don't want to
>> do things which would ignore the concerns of other team members, or they
>> share those concerns directly (I don't know enough to have an opinion on
>> it so I'm in the former group).
>>> Piece of advice: please reject packages instead of leaving them pending
>>> for 6+ months :)
>> We consider REJECT a serious button to press and don't do it unless we
>> know for sure the package can't enter the archive.  In this case, the
>> discussion is unresolved, so we don't know, so we don't press it.
> Hey!
> I'm currently stuck in a situation in which I can't address bugs in
> packages due to dependencies being stuck in NEW.
> Are there any options forward for somebody who doesn't work on the
> tooling, besides pausing maintainership?

We are bit blocked indeed.

We would need to implement this:


(or something similar)

For now, you can also disable features to limit the NEW step.
And when you upload a new package, you should limit the number of features exposed as packages.

Hope this helps!


More information about the Pkg-rust-maintainers mailing list