Debian Bug report logs - #831914
gui-apt-key: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Lucas Nussbaum <lucas@debian.org>

To: submit@bugs.debian.org

Subject: gui-apt-key: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute

Date: Wed, 20 Jul 2016 21:06:33 +0200

Source: gui-apt-key
Version: 0.4-2.1
Severity: important
Tags: stretch sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20160720 qa-ftbfs qa-indep
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.  This rebuild was done by building only the architecture-independent
packages.  At the same time, a normal build succeeded, which points the
problem specifically to build-indep/binary-indep targets.


The specific error below usually happens there is a binary-indep target in
debian/rules which is either empty or does not do anything useful.

If all the arch-independent packages are dummy transitional packages released
with jessie, the easy fix is to drop them now. If not, debian/rules should be
modified so that the binary-indep target generates the architecture independent
packages (and only those).

After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, this package will be suitable to be uploaded in source-only form if
you wish.

I file this bug as severity: important, but Santiago Vila, who led this
effort (kudos to him), got approval from the release team to consider those
bugs RC for stretch. The severity will be increased to 'serious' shortly.
See #830997 for details.

Relevant part (hopefully):
>  fakeroot debian/rules binary-indep
> make: Nothing to be done for 'binary-indep'.
>  dpkg-genchanges --build=all >../gui-apt-key_0.4-2.1_all.changes
> dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/07/20/gui-apt-key_0.4-2.1_unstable_archallonly.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Message #10 received at 831914@bugs.debian.org (full text, mbox, reply):

From: Santiago Vila <sanvila@unex.es>

To: Lucas Nussbaum <lucas@debian.org>

Cc: 831914@bugs.debian.org, Debian BTS <control@bugs.debian.org>

Subject: Re: gui-apt-key: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute

Date: Thu, 21 Jul 2016 21:29:00 +0200 (CEST)

[Message part 1 (text/plain, inline)]

tags 831914 + patch
thanks

Swapped binary-* targets.

Trivial patch attached.

[gui-apt-key.patch.txt (text/plain, attachment)]

Message #19 received at 831914@bugs.debian.org (full text, mbox, reply):

From: Axel Beckert <abe@debian.org>

To: Martin Schulze <joey@infodrom.org>, 831914@bugs.debian.org

Cc: Lucas Nussbaum <lucas@debian.org>, Santiago Vila <sanvila@unex.es>

Subject: NMU-intent: Re: Bug#831914: gui-apt-key: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute

Date: Wed, 10 Aug 2016 09:33:40 +0200

Hi Joey,

Santiago Vila wrote:
> Swapped binary-* targets.
> 
> Trivial patch attached.
[...]
> --- a/debian/rules
> +++ b/debian/rules
> @@ -40,10 +40,10 @@ debclean:
>  	rm -rf debian/tmp
>  	rm -f debian/{files,substvars}
>  
> -binary-indep:
> +binary-arch:
>  # Nothing to be done here
>  
> -binary-arch: debclean
> +binary-indep: debclean
>  	test -f stamp-build || $(MAKE) -f debian/rules build
>  	$(installbin) -d debian/tmp/DEBIAN
>  	chown -R root.root debian/tmp

I intent to make an NMU with Santiago's patch in the next few days to
fix this issue.

Will post a full debdiff, once I uploaded it to DELAYED/$days (with
$days somewhere between 5 and 15, not sure yet).

(I'm slightly annoyed about myself that I didn't fix this issue with
my previous upload: I noticed the strange usage of these targets, but
didn't fix them to keep the NMU minimal.)

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Message #24 received at 831914@bugs.debian.org (full text, mbox, reply):

From: Axel Beckert <abe@debian.org>

To: 834465@bugs.debian.org

Cc: 831914@bugs.debian.org

Subject: Re: Bug#834465: gui-apt-key: Shows empty owner, probably since the switch of gpg to 2.1

Date: Sat, 27 Aug 2016 13:05:11 +0200

Hi,

Axel Beckert wrote:
> Severity: important
[...]
> either since a recent apt upload or since the switch of GnuPG's default
> version from 1.4 to 2.1, gak only shows blank values in the "owner"
> column as well as in the owner field of the detail view.

Had a look at the GAK::Backend code today. It's the switch to GnuPG
2.x.

> Looks as if the output format of "apt-file list" slightly changed.
                                        ^^^^

Gna, I of course meant "apt-key list" here. Don't know why I always
mix them up.

Actually the output of "gpg --with-colons --list-key" changed. The
UIDs are now provided in separate lines as there can be more than one
UID per key.

I haven't written any code for that yet, but I'm confident, that I'll
come up with a patch for this issue soon.

Expect an NMU which fixes this issue and #831914 (FTBFS with
"dpkg-buildpackage -A") from me, which I'll upload to DELAYED/n (with
n probably being between 5 and 15). I'll post a full debdiff as soon
as I the NMU is ready.

(Actually I haven't NMUed #831914 yet because I ran into #834465 when
preparing that NMU and it didn't seem to make sense to me fix #831914
while knowning about #834465.)

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Message #29 received at 831914@bugs.debian.org (full text, mbox, reply):

From: Axel Beckert <abe@debian.org>

To: 834465@bugs.debian.org

Cc: 831914@bugs.debian.org

Subject: NMU for Bug#834465 (gui-apt-key: Shows empty owner with gpg 2.1) and Bug#831914 (gui-apt-key: FTBFS with dpkg-buildpackage -A)

Date: Sat, 27 Aug 2016 17:15:57 +0200

[Message part 1 (text/plain, inline)]

Control: tag -1 + patch pending

Hi Joey,

Axel Beckert wrote:
> > either since a recent apt upload or since the switch of GnuPG's default
> > version from 1.4 to 2.1, gak only shows blank values in the "owner"
> > column as well as in the owner field of the detail view.
[...]
> Actually the output of "gpg --with-colons --list-key" changed. The
> UIDs are now provided in separate lines as there can be more than one
> UID per key.
> 
> I haven't written any code for that yet, but I'm confident, that I'll
> come up with a patch for this issue soon.
> 
> Expect an NMU which fixes this issue and #831914 (FTBFS with
> "dpkg-buildpackage -A") from me, which I'll upload to DELAYED/n (with
> n probably being between 5 and 15). I'll post a full debdiff as soon
> as I the NMU is ready.

Attached the full source debdiff for the NMU, which I've just
uploaded(*) to DELAYED/7. Feel free to tell me if I should
fast-forward it or delay it longer.

The changelog entry reads as follows:

gui-apt-key (0.4-2.2) unstable; urgency=medium

  * Non-maintainer upload
  * Swap binary-* targets to fix FTBFS with "dpkg-buildpackage -A".
    (closes: #831914)
  * Fix empty owner with GnuPG 2.1 by also parsing "uid:" lines in
    output and assigning them to the right key. (closes: #834465)

 -- Axel Beckert <abe@debian.org>  Tue, 16 Aug 2016 00:56:47 +0200

Since "gpg ... --with-colons" is used in multiple affected places and
the parsing routine got more complex (stateful), I factored out the
output parsing into its own subroutine called "parse_with_colons". The
two functions "keylist" and "keydetails" are now mere wrappers around
"parse_with_colons":

sub keylist
{
    return parse_with_colons('--list-keys', 9, 4,1,6,9);
}

sub keydetails
{
    my $key = shift;
    $key = '0x' . $key if ($key !~ /^0x/);

    return parse_with_colons("--list-keys $key", 9);
}

"parse_with_colons" likely can be used as gpg output parsing routine
in further functions, too, but so far I noticed only the two mentioned
above to be affected, so I changed only those.

(*) I initially uploaded a package build with -A as a proof that the
    fix works. But I didn't notice before the upload that
    gui-apt-key_0.4-2.2_all.changes doesn't include the source package
    in the upload. Sorry for that noise.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

[gui-apt-key_0.4-2.1_0.4-2.2.dsc.debdiff (text/plain, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #36 received at 831914-close@bugs.debian.org (full text, mbox, reply):

From: Axel Beckert <abe@debian.org>

To: 831914-close@bugs.debian.org

Subject: Bug#831914: fixed in gui-apt-key 0.4-2.2

Date: Sat, 03 Sep 2016 18:21:54 +0000

Source: gui-apt-key
Source-Version: 0.4-2.2

We believe that the bug you reported is fixed in the latest version of
gui-apt-key, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 831914@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Axel Beckert <abe@debian.org> (supplier of updated gui-apt-key package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 27 Aug 2016 16:48:34 +0200
Source: gui-apt-key
Binary: gui-apt-key
Architecture: source all
Version: 0.4-2.2
Distribution: unstable
Urgency: medium
Maintainer: Martin Schulze <joey@debian.org>
Changed-By: Axel Beckert <abe@debian.org>
Description:
 gui-apt-key - Graphical Key Manager for APT
Closes: 831914 834465
Changes:
 gui-apt-key (0.4-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Swap binary-* targets to fix FTBFS with "dpkg-buildpackage -A".
     (closes: #831914)
   * Fix empty owner with GnuPG 2.1 by also parsing "uid:" lines in
     output and assigning them to the right key. (closes: #834465)
Checksums-Sha1:
 6e77105e2540c3721b37f20ade3c0c5569cf401e 1617 gui-apt-key_0.4-2.2.dsc
 c923ccfad9fcd48dd27a660e69e5c8d2b01975e6 13106 gui-apt-key_0.4-2.2.diff.gz
 e1d3dd5ae887c856bbf677e15bc9488231d518fd 27622 gui-apt-key_0.4-2.2_all.deb
Checksums-Sha256:
 2ae228e519f43b5465ada55ffee6c6028b310e7f791819787cff606af8b3c6c7 1617 gui-apt-key_0.4-2.2.dsc
 a046473a76ee4fd8f6e9f9de9aca8ed2a163fb41320b7a02848f7098b9bd875e 13106 gui-apt-key_0.4-2.2.diff.gz
 3e1dc12cb25b31af08fc9249d78efbf0633339361b19fff1e7e4f09bc9b6c761 27622 gui-apt-key_0.4-2.2_all.deb
Files:
 ed1e11649385c25e8dcd78e97cdf6fd2 1617 admin optional gui-apt-key_0.4-2.2.dsc
 9f1dac6ce676428d1d4b140a1313a323 13106 admin optional gui-apt-key_0.4-2.2.diff.gz
 bae2d707ff139f8f78d916e87d498197 27622 admin optional gui-apt-key_0.4-2.2_all.deb

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJXwahbAAoJEGvmY8daNcl1VXYQAL3PWJMFPLGIJBcGTmJzIAsh
PZxGX5FPzFcCq2I8ism+YBuvmsjOAyqNrTnzGjwRMECezM8EBXNCxxjIY0EEjAP5
G6g5uwz+NueW6cDWFtVjNPWqC3/aifkZZd7xmNHJTl3fdQBYhYg8JRnXXYVrBDS5
NupVOXpqGubij+TQJnR1CNzr9+akgmfCUsxpADu8CUsABp+0+XTf9laXl/kfG8mM
ZptGklmfhyJt3sTGYaAJYqlXeE+j1iu3zSd9lyKDVbQY3PPqGjkWnGm9fxbrlLsY
KRItgWRrg/76dCGqtPEJlH14vQZlR/jKUjez7pVsZl+AKmMgOrkBBlcm8iHeNDCy
z5YaT3WrDjeybKSo2mc4LljdSwKVY587R3Ms/ziiv+DSAA+/BblhMf/hcMIjDsAj
AvH4csUm9BZKkYAtB9ot6JoNUMHKuQH3pXtuzAlaG1rSGH/+AF2h3yUuzYdcX5lJ
TPBk5sGf2XN1I42caMQ3rrXCq0iN336Bmx1Oog9TnLb1VJOv7GN02RolqExp0wW1
p6TRsjo1OLEQxoRjWuEb/xgpAqNaascb2nmnsxeW8+kKvdgD8vvsfep9vNhHjSqP
VdVPpWXHtZn1uM3b4HH9LoPIVG/RazqCWN3pCt/aJwOJ8hoTL2p9D3WGI6osrnKI
vDrOAiklIszCAZF/Xjvk
=GFA3
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.