[pkg-lxqt-devel] Your Debian package(s) will not migrate to testing
agaida at siduction.org
Wed Sep 4 23:32:18 BST 2019
On Wed, 04 Sep 2019 22:02:50 +0100
Julian Gilbey <jdg at debian.org> wrote:
> Dear LXQt Packaging Team,
> 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 at powdarrmonkey.net>)
> that only source-only uploads would transition to testing.
> Here is the relevant part of what they wrote:
> 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).
Will do so soon
> Source package: featherpad
> Version: 0.11.1-1
> One relevant line of the excuse file (including the uploader):
> Not built on buildd: arch amd64 binaries uploaded by
> mattia at mapreri.org Transition verdict: REJECTED_PERMANENTLY
I understand the reasons and highly appreciate them - but there is a
design fault in the workflow. Featherpad was uploaded to NEW because
splitted out languages (now featherpad-l10n) - and upload to NEW is
impossible without binaries right now. In a perfect world it should be
possible to do source only uploads to NEW.
I'm not complaining, but it looks like wasted maintainer and builder
time esp. with bigger packages - it just makes no sense to waste time
with a local (ideally sbuild or pbuilder) build and do the same thing
again with no changes on the build server again because the NEW package
will never ever have a chance to migrate :D
Ok, i also understand that a clean local build in a chroot shows that
the new package will build at least for one or maybe two architectures.
BDBF C688 EFAD BA89 5A9F 464B CD28 0A0B 4D72 827C
More information about the pkg-lxqt-devel