Re: Bugs "fails to migrate to testing for too long" (Was: cluster3 dropped out of testing)

2020-12-09 Thread Diane Trout
On Wed, 2020-12-09 at 19:31 +0100, Mattia Rizzolo wrote: > > Even then, the message says that "cluster3 has no binaries on any > arch" > - from there why can't one try to figure why there are no binaries?  > I'm > positive that dumping the tracker link and that message in > debian-mentors@ would

Re: Bugs "fails to migrate to testing for too long" (Was: cluster3 dropped out of testing)

2020-12-09 Thread Mattia Rizzolo
On Wed, Dec 09, 2020 at 09:44:25AM -0800, Diane Trout wrote: > Could we add a note to tracker or excuses for non-free packages on what > the developer needs to do to get it to migrate? IMHO, that's inappropriate. That would mean artificially adding into britney something that is really a nuance

Re: Bugs "fails to migrate to testing for too long" (Was: cluster3 dropped out of testing)

2020-12-09 Thread Diane Trout
On Wed, 2020-12-09 at 18:27 +0100, Mattia Rizzolo wrote: > Because you seem to not be aware of how non-free works.  Non-free is > not > autobuilt, so when Andreas uploaded 1.59+ds-2 without any binaries > then > "cluster3 has no binaries on any arch".  Since there are no binaries > associated with

Re: Bugs "fails to migrate to testing for too long" (Was: cluster3 dropped out of testing)

2020-12-09 Thread Mattia Rizzolo
On Wed, Dec 09, 2020 at 10:17:56AM +0100, Andreas Tille wrote: > I'd like to point to a discussion on the Debian Med mailing list which > was caused by a "fails to migrate to testing for too long" bug. I > fully agree that these bugs should be filed. However, the bugs are > immediately set to

Bugs "fails to migrate to testing for too long" (Was: cluster3 dropped out of testing)

2020-12-09 Thread Andreas Tille
Hi, I'd like to point to a discussion on the Debian Med mailing list which was caused by a "fails to migrate to testing for too long" bug. I fully agree that these bugs should be filed. However, the bugs are immediately set to "Done" later by the issuer of the bug. I discussed this with Paul