[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [jdg@debian.org: Your Debian package(s) will not migrate to testing]

On Thu, Sep 05, 2019 at 10:10:00AM +0200, Andre Noll wrote:
> Hi Adam,
> looks like tfortune needs a new source-only upload to migrate to
> testing. Could you please do this for me?  Here's the commands to
> build the source package:
> 	git archive --prefix tfortune-1.0.0/ origin/master > ../tfortune_1.0.0.orig.tar.xz
> 	dpkg-buildpackage -S
> There have been no changes since June, so your existing repo should
> still be uptodate.
> Thanks
> Andre

Hi Adam and Andre,

You will need to upload a new version, though; the system will not
accept a package with the same version number.

Best wishes,


> ----- Forwarded message from Julian Gilbey <jdg@debian.org> -----
> Subject: Your Debian package(s) will not migrate to testing
> From: Julian Gilbey <jdg@debian.org>
> To: Andre Noll <maan@tuebingen.mpg.de>
> Message-Id: <E1i5ce8-0002mU-On@erdos.d-and-j.net>
> Date: Wed, 04 Sep 2019 22:16:56 +0100
> Dear Andre Noll,
> This is a courtesy message about your package(s) which is/are
> stuck in sid, and will not migrate to testing, in case you
> are unaware; they are listed below.
> The release managers announced on 7th July 2019 in their email
> to debian-devel-announce and debian-release
> (Message-ID: <20190707014700.GF15255@powdarrmonkey.net>)
> that only source-only uploads would transition to testing.
> Here is the relevant part of what they wrote:
> ~~~~~
> No binary maintainer uploads for bullseye
> =========================================
> The release of buster also means the bullseye release cycle is about to begin.
> >From now on, we will no longer allow binaries uploaded by maintainers to
> migrate to testing. This means that you will need to do source-only uploads if
> you want them to reach bullseye.
>   Q: I already did a binary upload, do I need to do a new (source-only) upload?
>   A: Yes (preferably with other changes, not just a version bump).
>   Q: I needed to do a binary upload because my upload went to the NEW queue,
>      do I need to do a new (source-only) upload for it to reach bullseye?
>   A: Yes. We also suggest going through NEW in experimental instead of unstable
>      where possible, to avoid disruption in unstable.
>   Q: Does this also apply to contrib and non-free?
>   A: No. Not all packages in contrib and non-free can be built on the buildds,
>      so maintainer uploads will still be allowed to migrate for packages
>      outside main.
> ~~~~~
> To perform a source-only build and upload, run dpkg-buildpackage -S
> and then upload the relevant files in the normal way (for example,
> using dupload or dput).
> Your package(s) involved is/are as follows:
> Source package: tfortune
> Version: 1.0.0-2
> One relevant line of the excuse file (including the uploader):
>   Not built on buildd: arch amd64 binaries uploaded by kilobyte
> Transition verdict: REJECTED_PERMANENTLY
> I hope this is of help to you!
> Best wishes,
>    Julian
> ----- End forwarded message -----

Reply to: