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 "Done" later by the issuer of the bug. I discussed
> this with Paul before and he said reasons for this - but I think its
> wrong since the issue vanishes from BTS and becomes invisible for the
> maintainers which is not helpful IMHO.
>
> My suggestion is to not set those bugs to Done to keep the red flag
> for the package raised.
I'm instead convinced that closing those bugs directly is right.
The reason the packages are not migrating has nothing to do with the
bug, and keeping it open adds to the confusion as then it's reported as
a "regression" when really it isn't.
> On Tue, Dec 08, 2020 at 08:46:04PM -0800, tony mancill wrote:
> > Hi Diane,
> >
> > On Tue, Dec 08, 2020 at 10:14:24AM -0800, Diane Trout wrote:
> > > My coworker noticed cluster3 dropped out of testing and I'm confused
> > > why.
> > >
> > > https://tracker.debian.org/pkg/cluster3
> > > says that "cluster3 has no binaries on any arch", and there are no logs
> > > at buildd https://buildd.debian.org/status/package.php?p=cluster3 for
> > > it
> > >
> > > However if I grab either the source package for 1.59+ds-2 or the
> > > current main branch from salsa and try building, I get a package with
> > > binaries.
> > >
> > > The only mildly annoying thing is when I build in unstable, it ends up
> > > with a dependency on python3 (<< 3.10), python3 (>= 3.9~) which doesn't
> > > install on testing.
> > >
> > > But the package seems to be fine, so any thoughts why it was held back?
> >
> > Sometimes you can find this information in the PTS [1] in the News
> > section [2]. In this case cluster3 failed to migrate from unstable to
> > testing before a fixed deadline [3]. (Although I don't know exactly why
> > *that* happened.)
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 the source, britney refuses to migrate it. Indeed, one
could just do a binary-only build of it, upload it, and it would migrate
stright the next day.
Or one could ask for an exception to the non-free buildds as docuemnted
on https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#marking-non-free-packages-as-auto-buildable
As you can see, nothing relating to that bug.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Attachment:
signature.asc
Description: PGP signature