Bug#750298: marked as done (xenwatch: FTBFS: Make.config:1: *** empty variable name.)
Your message dated Sun, 19 Jul 2015 17:05:58 +0000
with message-id <E1ZGs2I-0004d7-65@franck.debian.org>
and subject line Bug#750298: fixed in xenwatch 0.5.4-4
has caused the Debian Bug report #750298,
regarding xenwatch: FTBFS: Make.config:1: *** empty variable name.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
750298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750298
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: xenwatch
Version: 0.5.4-3
Severity: serious
Tags: jessie sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20140601 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean
> dh_testdir
> dh_auto_clean
> make[1]: Entering directory '/«PKGBUILDDIR»'
> Make.config:1: *** empty variable name. Stop.
> make[1]: Leaving directory '/«PKGBUILDDIR»'
> dh_auto_clean: make -j1 distclean returned exit code 2
> make: *** [clean] Error 2
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/06/01/xenwatch_0.5.4-3_unstable.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.
--- End Message ---
--- Begin Message ---
Source: xenwatch
Source-Version: 0.5.4-4
We believe that the bug you reported is fixed in the latest version of
xenwatch, 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 750298@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann <anbe@debian.org> (supplier of updated xenwatch 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: Sun, 19 Jul 2015 17:11:02 +0200
Source: xenwatch
Binary: xenwatch
Architecture: source
Version: 0.5.4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Andreas Beckmann <anbe@debian.org>
Description:
xenwatch - Virtualization utilities, mostly for Xen
Closes: 750298
Changes:
xenwatch (0.5.4-4) unstable; urgency=medium
.
* QA upload.
* Use /bin/echo if the -e flag is needed. Fixes FTBFS if the shell builtin
does not implement this. (Closes: 750298)
Checksums-Sha1:
8a908ac55c911152c2540996661947d8ab5c3240 1785 xenwatch_0.5.4-4.dsc
5d16229548fda13bdede5114fdb956adf6b98492 3304 xenwatch_0.5.4-4.debian.tar.xz
Checksums-Sha256:
685a00dccc8abfed2f1c925bddf9f698de1260dcb44914f3493a7a9989b4e497 1785 xenwatch_0.5.4-4.dsc
3619c0fb1e8d8fb54e09053746e8a00080dc042503f4459b2f5c2e9dc0453418 3304 xenwatch_0.5.4-4.debian.tar.xz
Files:
c8aa8fb5f8115f6be23c23f9c2c3f7b2 1785 admin optional xenwatch_0.5.4-4.dsc
aee8342b7dfe9cff315133a690095d0c 3304 admin optional xenwatch_0.5.4-4.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJVq9doAAoJEF+zP5NZ6e0I+0UP/AiI7QPfNG+towk1vvXclbtI
wG6oLZDsptWY7KFr4wmk7W17d6DoRXODygZi/UPO8YQltfGuHdGoHfbmmipx3rc5
+C8Ad28n0B1rX1xnWO6sZYVcvQMw0NY+eDnxuCShMK3j7N65HtO2nPCOnRcsSmNk
XB3zV7wn5IprMjKumsLpTE4cAEsvbTKEdb8+Ql+6uanKSoX6GXkj5y/x/P4Cipgq
j5mavRnC4GO8dnkvOU22ytLJnZJmFSg6dHdmFeWBz9eEnOhjdLlmAp9y155sHYvp
0xPLzJxhu4L5Go6RxLA+4OQEhHUhA6agefqnkyDDqvMXKulJ7FDqXJRsBiSlzQM0
Qp8FJEs5/UlxrTVKuat3tZD/koWDzdLvsnl+bkHGMY6LasuRtaNf/Azjg0RbLLA9
zfuMdvKJJZ/99NmFwCPvTZDlp0BEckXjRQgcNW7KMbNHaM4PGK2xY4viKCfIcdE0
GqTUqt4EbkfN+QcSqEAcr/b4DeqbWmH52ERKnyM5MBx/+61S05j2aFcgXwr2QKUe
N3sM/BZjmvFCgwJ0LvSEHm34ORIeVp0FrjkC4BORw0IzcmQfNblR+BQccemNoWAR
Uyzntk1LRzefpCgEd6c7Y5iDClueANDcYSWCmiGycROuzWwy9CrgsAv7xxqI+tWv
Vojknk2PeE0YSd0sCxaU
=DFUu
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: