Bug#969493: src:nanook: fails to migrate to testing for too long: maintainer built arch:all binaries

2020-09-10 Thread Andreas Tille
Hi Paul, On Thu, Sep 10, 2020 at 12:02:10PM +0200, Paul Gevers wrote: > On 08-09-2020 22:21, Andreas Tille wrote: > >> I'm back on internet. I have just uploaded to DELAYED/15. Please let me > >> know if I should delay or cancel. > > > > Thanks a lot. There is no point in any delay for Debian Me

Bug#969493: src:nanook: fails to migrate to testing for too long: maintainer built arch:all binaries

2020-09-10 Thread Paul Gevers
Hi Andreas, On 08-09-2020 22:21, Andreas Tille wrote: >> I'm back on internet. I have just uploaded to DELAYED/15. Please let me >> know if I should delay or cancel. > > Thanks a lot. There is no point in any delay for Debian Med packages. Ack, but the NMU is scripted [1]. If I need to change t

Bug#969493: src:nanook: fails to migrate to testing for too long: maintainer built arch:all binaries

2020-09-08 Thread Andreas Tille
Hi Paul, On Mon, Sep 07, 2020 at 08:13:54PM +0200, Paul Gevers wrote: > Control: tags -1 pending > > On 03-09-2020 20:46, Paul Gevers wrote: > > Your package is only blocked because the arch:all binary package(s) > > aren't built on a buildd. Unfortunately the Debian infrastructure > > doesn't al

Bug#969493: src:nanook: fails to migrate to testing for too long: maintainer built arch:all binaries

2020-09-07 Thread Paul Gevers
Control: tags -1 pending Hi, On 03-09-2020 20:46, Paul Gevers wrote: > Your package is only blocked because the arch:all binary package(s) > aren't built on a buildd. Unfortunately the Debian infrastructure > doesn't allow arch:all packages to be properly binNMU'ed. Normally I > would do a no-cha

Bug#969493: src:nanook: fails to migrate to testing for too long: maintainer built arch:all binaries

2020-09-03 Thread Paul Gevers
Source: nanook Version: 1.33+dfsg-1 Severity: serious Control: close -1 1.33+dfsg-2 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between tes