Your message dated Sat, 18 Jan 2014 12:33:50 +0000
with message-id <e1w4v5y-0004z6...@franck.debian.org>
and subject line Bug#733771: fixed in trinity 1.3-1
has caused the Debian Bug report #733771,
regarding trinity: FTBFS on most architectures: wants linux-headers(-amd64)
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 ow...@bugs.debian.org
immediately.)
--
733771: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733771
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trinity
Version: 1.2-1
Severity: serious
Justification: fails to build from source
Trinity's build dependencies are unsatisfiable on most architectures
because they include
linux-headers-amd64 | linux-headers-generic | linux-headers
but linux-headers-amd64 is naturally amd64-specific and the
alternatives don't exist at all these days, per #724569. (Even if
they did, the autobuilders would still ignore them in the absence of
explicit architecture restrictions, for the sake of reproducibility.)
That said, it's not clear what good this build dependency does anyway
-- the only kernel headers that wind up in the default include path
are from linux-libc-dev, which is already an explicit build
dependency (not to mention transitively build-essential on Linux).
Could you please try removing it altogether?
Thanks!
--- End Message ---
--- Begin Message ---
Source: trinity
Source-Version: 1.3-1
We believe that the bug you reported is fixed in the latest version of
trinity, 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 733...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gustavo panizzo <g...@zumbi.com.ar> (supplier of updated trinity 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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Fri, 17 Jan 2014 21:10:15 -0300
Source: trinity
Binary: trinity
Architecture: source amd64
Version: 1.3-1
Distribution: unstable
Urgency: medium
Maintainer: gustavo panizzo <g...@zumbi.com.ar>
Changed-By: gustavo panizzo <g...@zumbi.com.ar>
Description:
trinity - system call fuzz tester
Closes: 733771
Changes:
trinity (1.3-1) unstable; urgency=medium
.
* New upstream version 1.3.
* Removed wrong dependency on linux-headers. (Closes: #733771).
Checksums-Sha1:
ddc556e8ef24b8ab1e12e26957071afbb2772b5b 1305 trinity_1.3-1.dsc
f93f5269772e7ebfbe086c882c39f71bca40d3ff 148744 trinity_1.3.orig.tar.xz
3f1f14802f02dfb976ad2806a35f67afc4862017 175130 trinity_1.3-1.debian.tar.gz
322ea977df0934d85fd06ba2f3869014de5fb090 255946 trinity_1.3-1_amd64.deb
Checksums-Sha256:
74eb8ea5f9662d52cb9c2f12f8d72c2d5ea4b7df31ba88fea005813e901b2d99 1305
trinity_1.3-1.dsc
85f355de52fe5829fa3f011f090b58e76d39cba6d8233df88be24d91c5436ec5 148744
trinity_1.3.orig.tar.xz
e22e7a609ba4eef4888121184fb3a3f1e823a5d49a263cd3f7f472e55eb90252 175130
trinity_1.3-1.debian.tar.gz
06e6c5519988b416b223093b463e3e140079a05cdba27e6bb477e9dc0fe1f677 255946
trinity_1.3-1_amd64.deb
Files:
c19e2004caaaa7dcd122cf53dfb2c45c 1305 utils optional trinity_1.3-1.dsc
5699a72ad30bd6207a8dabf848e6acb0 148744 utils optional trinity_1.3.orig.tar.xz
00f9d34d6e8e00708c8f107b511f0d04 175130 utils optional
trinity_1.3-1.debian.tar.gz
fc4e9003dc0a5de34ed45b73bff010d5 255946 utils optional trinity_1.3-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
iEYEARECAAYFAlLacHcACgkQStlRaw+TLJyHigCgxN2ukx429cs1P6wlpm8UOP+k
HfsAoKE7GjCQsWBWyVe2KlJ0yxyCxZa5
=VcqL
-----END PGP SIGNATURE-----
--- End Message ---
