Bug#789893: libvolk1.0-bin and libvolk-bin: error when trying to install together
Package: libvolk-bin,libvolk1.0-bin Version: libvolk-bin/3.7.5-5 Version: libvolk1.0-bin/1.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2015-06-25 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package gcc-5-base:amd64. (Reading database ... 10902 files and directories currently installed.) Preparing to unpack .../gcc-5-base_5.1.1-12_amd64.deb ... Unpacking gcc-5-base:amd64 (5.1.1-12) ... Setting up gcc-5-base:amd64 (5.1.1-12) ... (Reading database ... 10909 files and directories currently installed.) Preparing to unpack .../libstdc++6_5.1.1-12_amd64.deb ... Unpacking libstdc++6:amd64 (5.1.1-12) over (4.8.2-19) ... Setting up libstdc++6:amd64 (5.1.1-12) ... Processing triggers for libc-bin (2.19-18) ... Selecting previously unselected package libdb5.3:amd64. (Reading database ... 10923 files and directories currently installed.) Preparing to unpack .../libdb5.3_5.3.28-9_amd64.deb ... Unpacking libdb5.3:amd64 (5.3.28-9) ... Selecting previously unselected package libpython2.7-minimal:amd64. Preparing to unpack .../libpython2.7-minimal_2.7.10-2_amd64.deb ... Unpacking libpython2.7-minimal:amd64 (2.7.10-2) ... Selecting previously unselected package python2.7-minimal. Preparing to unpack .../python2.7-minimal_2.7.10-2_amd64.deb ... Unpacking python2.7-minimal (2.7.10-2) ... Selecting previously unselected package python-minimal. Preparing to unpack .../python-minimal_2.7.9-1_amd64.deb ... Unpacking python-minimal (2.7.9-1) ... Selecting previously unselected package mime-support. Preparing to unpack .../mime-support_3.58_all.deb ... Unpacking mime-support (3.58) ... Selecting previously unselected package libexpat1:amd64. Preparing to unpack .../libexpat1_2.1.0-6+b3_amd64.deb ... Unpacking libexpat1:amd64 (2.1.0-6+b3) ... Selecting previously unselected package libffi6:amd64. Preparing to unpack .../libffi6_3.1-2+b2_amd64.deb ... Unpacking libffi6:amd64 (3.1-2+b2) ... Selecting previously unselected package libpython2.7-stdlib:amd64. Preparing to unpack .../libpython2.7-stdlib_2.7.10-2_amd64.deb ... Unpacking libpython2.7-stdlib:amd64 (2.7.10-2) ... Selecting previously unselected package python2.7. Preparing to unpack .../python2.7_2.7.10-2_amd64.deb ... Unpacking python2.7 (2.7.10-2) ... Selecting previously unselected package libpython-stdlib:amd64. Preparing to unpack .../libpython-stdlib_2.7.9-1_amd64.deb ... Unpacking libpython-stdlib:amd64 (2.7.9-1) ... Processing triggers for man-db (2.7.0.2-5) ... Setting up libpython2.7-minimal:amd64 (2.7.10-2) ... Setting up python2.7-minimal (2.7.10-2) ... Setting up python-minimal (2.7.9-1) ... Selecting previously unselected package python. (Reading database ... 11717 files and directories currently installed.) Preparing to unpack .../python_2.7.9-1_amd64.deb ... Unpacking python (2.7.9-1) ... Selecting previously unselected package libboost-system1.55.0:amd64. Preparing to unpack .../libboost-system1.55.0_1.55.0+dfsg-3_amd64.deb ... Unpacking libboost-system1.55.0:amd64 (1.55.0+dfsg-3) ... Selecting previously unselected package libboost-filesystem1.55.0:amd64. Preparing to unpack .../libboost-filesystem1.55.0_1.55.0+dfsg-3_amd64.deb ... Unpacking libboost-filesystem1.55.0:amd64 (1.55.0+dfsg-3) ... Selecting previously unselected package libboost-program-options1.55.0:amd64. Preparing to unpack .../libboost-program-options1.55.0_1.55.0+dfsg-3_amd64.deb ... Unpacking libboost-program-options1.55.0:amd64 (1.55.0+dfsg-3) ... Selecting previously unselected package libboost-test1.55.0:amd64. Preparing to unpack .../libboost-test1.55.0_1.55.0+dfsg-3_amd64.deb ... Unpacking libboost-test1.55.0:amd64 (1.55.0+dfsg-3) ... Selecting previously unselected package liborc-0.4-0:amd64. Preparing to unpack .../liborc-0.4-0_1%3a0.4.24-1_amd64.deb ... Unpacking liborc-0.4-0:amd64 (1:0.4.24-1) ... Selecting previously unselected package libvolk0.0.0:amd64. Preparing to unpack .../libvolk0.0.0_3.7.5-5_amd64.deb ... Unpacking libvolk0.0.0:amd64 (3.7.5-5) ... Selecting previously unselected package libvolk-bin. Preparing to unpack .../libvolk-bin_3.7.5-5_amd64.deb ... Unpacking libvolk-bin (3.7.5-5) ... Selecting previously unselected package libvolk1.0:amd64. Preparing to unpack .../libvolk1.0_1.0-1_amd64.deb ... Unpacking libvolk1.0:amd64 (1.0-1) ... Selecting previously unselected package libvolk1.0-bin. Preparing to unpack .../libvolk1.0-bin_1.0-1_amd64.deb ... Unpacking libvolk1.0-bin (1.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libvolk1.0-bin_1.0-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/volk-config-info', which is also in package libvolk-bin 3.7.5-5 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for man-db (2.7.0.2-5) ... Errors were encountered while
Bug#789894: libvolk1.0-dev and libvolk-dev: error when trying to install together
Package: libvolk-dev,libvolk1.0-dev Version: libvolk-dev/3.7.5-5 Version: libvolk1.0-dev/1.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2015-06-25 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package gcc-5-base:amd64. (Reading database ... 10902 files and directories currently installed.) Preparing to unpack .../gcc-5-base_5.1.1-12_amd64.deb ... Unpacking gcc-5-base:amd64 (5.1.1-12) ... Setting up gcc-5-base:amd64 (5.1.1-12) ... (Reading database ... 10909 files and directories currently installed.) Preparing to unpack .../libstdc++6_5.1.1-12_amd64.deb ... Unpacking libstdc++6:amd64 (5.1.1-12) over (4.8.2-19) ... Setting up libstdc++6:amd64 (5.1.1-12) ... Processing triggers for libc-bin (2.19-18) ... Selecting previously unselected package libboost-system1.55.0:amd64. (Reading database ... 10923 files and directories currently installed.) Preparing to unpack .../libboost-system1.55.0_1.55.0+dfsg-3_amd64.deb ... Unpacking libboost-system1.55.0:amd64 (1.55.0+dfsg-3) ... Selecting previously unselected package libboost-filesystem1.55.0:amd64. Preparing to unpack .../libboost-filesystem1.55.0_1.55.0+dfsg-3_amd64.deb ... Unpacking libboost-filesystem1.55.0:amd64 (1.55.0+dfsg-3) ... Selecting previously unselected package libboost-program-options1.55.0:amd64. Preparing to unpack .../libboost-program-options1.55.0_1.55.0+dfsg-3_amd64.deb ... Unpacking libboost-program-options1.55.0:amd64 (1.55.0+dfsg-3) ... Selecting previously unselected package libboost-test1.55.0:amd64. Preparing to unpack .../libboost-test1.55.0_1.55.0+dfsg-3_amd64.deb ... Unpacking libboost-test1.55.0:amd64 (1.55.0+dfsg-3) ... Selecting previously unselected package liborc-0.4-0:amd64. Preparing to unpack .../liborc-0.4-0_1%3a0.4.24-1_amd64.deb ... Unpacking liborc-0.4-0:amd64 (1:0.4.24-1) ... Selecting previously unselected package libvolk0.0.0:amd64. Preparing to unpack .../libvolk0.0.0_3.7.5-5_amd64.deb ... Unpacking libvolk0.0.0:amd64 (3.7.5-5) ... Selecting previously unselected package libvolk-bin. Preparing to unpack .../libvolk-bin_3.7.5-5_amd64.deb ... Unpacking libvolk-bin (3.7.5-5) ... Selecting previously unselected package libvolk-dev. Preparing to unpack .../libvolk-dev_3.7.5-5_amd64.deb ... Unpacking libvolk-dev (3.7.5-5) ... Selecting previously unselected package libvolk1.0:amd64. Preparing to unpack .../libvolk1.0_1.0-1_amd64.deb ... Unpacking libvolk1.0:amd64 (1.0-1) ... Selecting previously unselected package libvolk1.0-dev. Preparing to unpack .../libvolk1.0-dev_1.0-1_amd64.deb ... Unpacking libvolk1.0-dev (1.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libvolk1.0-dev_1.0-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/volk.pc', which is also in package libvolk-dev 3.7.5-5 Processing triggers for man-db (2.7.0.2-5) ... Errors were encountered while processing: /var/cache/apt/archives/libvolk1.0-dev_1.0-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/x86_64-linux-gnu/libvolk.so /usr/lib/x86_64-linux-gnu/pkgconfig/volk.pc This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://qa.debian.org/dose/file-overwrites.html. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789897: failure on upgrade, file conflict with ndiff
Package: zenmap Version: 6.47-5 Severity: serious Todays upgrade of zenmap failed: # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: ndiff zenmap 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 898 kB of archives. After this operation, 66.6 kB disk space will be freed. Do you want to continue? [Y/n] Get:1 http://ftp.de.debian.org/debian/ sid/main ndiff all 6.47-5 [257 kB] Get:2 http://ftp.de.debian.org/debian/ sid/main zenmap all 6.47-5 [642 kB] Fetched 898 kB in 0s (906 kB/s) Retrieving bug reports... Done Parsing Found/Fixed information... Done Reading changelogs... Done (Reading database ... 307698 files and directories currently installed.) Preparing to unpack .../archives/ndiff_6.47-5_all.deb ... Unpacking ndiff (6.47-5) over (6.47-3) ... dpkg: error processing archive /var/cache/apt/archives/ndiff_6.47-5_all.deb (--unpack): trying to overwrite '/usr/lib/python2.7/dist-packages/ndiff.py', which is also in package zenmap 6.47-3 Preparing to unpack .../archives/zenmap_6.47-5_all.deb ... Unpacking zenmap (6.47-5) over (6.47-3) ... Processing triggers for man-db (2.7.0.2-5) ... Processing triggers for bamfdaemon (0.2.118-1+b1) ... Rebuilding /usr/share/applications/bamf.index... Processing triggers for gnome-menus (3.13.3-6) ... Processing triggers for mime-support (3.58) ... Processing triggers for desktop-file-utils (0.22-1) ... Errors were encountered while processing: /var/cache/apt/archives/ndiff_6.47-5_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Looks like zenmap is missing a proper versioned Breaks/Replaces: See section 7.6.1: https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces Cheers, Michael -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages zenmap depends on: ii nmap6.47-5 ii python 2.7.9-1 ii python-gobject 3.16.2-1 ii python-gtk2 2.24.0-4 Versions of packages zenmap recommends: ii gksu 2.0.2-9 zenmap suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789827: marked as done (murasaki: FTBFS when not building -common package)
Your message dated Thu, 25 Jun 2015 07:33:48 +
with message-id e1z81fq-0008q9...@franck.debian.org
and subject line Bug#789827: fixed in murasaki 1.68.6-2
has caused the Debian Bug report #789827,
regarding murasaki: FTBFS when not building -common package
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.)
--
789827: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: murasaki
Version: 1.68.6-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Builds of murasaki covering only its architecture-dependent binary
packages (as on the autobuilders) have been failing:
for pscript in debian/murasaki-common/usr/lib/debian-med/bin/* ; do \
pod2man ${pscript} debian/murasaki-common/usr/share/man/man1/`basename
${pscript}`.1 ; \
done
Can't open debian/murasaki-common/usr/lib/debian-med/bin/*: No such file or
directory at /usr/bin/pod2man line 71.
make[1]: *** [override_dh_installman] Error 2
debian/rules:24: recipe for target 'override_dh_installman' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [binary-arch] Error 2
debian/rules:13: recipe for target 'binary-arch' failed
Could you please account for such builds, which you can perform by
running dpkg-buildpackage (or your favorite wrapper) with the -B flag?
Thanks!
---End Message---
---BeginMessage---
Source: murasaki
Source-Version: 1.68.6-2
We believe that the bug you reported is fixed in the latest version of
murasaki, 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 789...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille ti...@debian.org (supplier of updated murasaki 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: SHA256
Format: 1.8
Date: Thu, 25 Jun 2015 08:56:17 +0200
Source: murasaki
Binary: murasaki murasaki-mpi murasaki-common
Architecture: source all amd64
Version: 1.68.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
debian-med-packag...@lists.alioth.debian.org
Changed-By: Andreas Tille ti...@debian.org
Description:
murasaki - homology detection tool across multiple large genomes
murasaki-common - homology detection tool across multiple large genomes
(common fil
murasaki-mpi - homology detection tool across multiple large genomes
(MPI-versio
Closes: 789827 789880
Changes:
murasaki (1.68.6-2) unstable; urgency=medium
.
* Do not try to access dirs from arch all package when doing arch any
only builds
Closes: #789827, #789880
* Small DEP5 format fix
Checksums-Sha1:
54c36d7476d2fc92db6923f520e22708c0c8e394 2244 murasaki_1.68.6-2.dsc
8e2f4f15d9bd1fc859929abbed7fc3f00d8132bc 5780 murasaki_1.68.6-2.debian.tar.xz
9e8bf460f8169ab0d4e526d8b3179ffdbcae2ccb 143216
murasaki-common_1.68.6-2_all.deb
b08df73fd7492be5931e799f32eb80407dcc6518 557220 murasaki-mpi_1.68.6-2_amd64.deb
4987ed584f8c17b816ce3ce8c05f112c854f822c 467902 murasaki_1.68.6-2_amd64.deb
Checksums-Sha256:
adc4640805df024e0ef717901e63f348cc1e6414dd59a4b58da0258de6c9b772 2244
murasaki_1.68.6-2.dsc
355760b145cd8a8c000743642abf41dcb1333ee803cabeb19b58e3415fd8f0cf 5780
murasaki_1.68.6-2.debian.tar.xz
c89bf4b9cee08b2d3be54531c48dd726f198df64651e72d3d2f43eef20af0d68 143216
murasaki-common_1.68.6-2_all.deb
9247dc09cd9cb26fd74cda526daea6a69f9f76c2f25fd2404a7b10f5e59a9904 557220
murasaki-mpi_1.68.6-2_amd64.deb
fe210e0e2d47f5d46d648106bc487e4ca7df0ef4d5f943c5828d0039da977653 467902
murasaki_1.68.6-2_amd64.deb
Files:
54be53e8e66eb3da693c154457e96def 2244 science optional murasaki_1.68.6-2.dsc
70de3f9f2bdc1033edac5e4b77af0f05 5780 science optional
murasaki_1.68.6-2.debian.tar.xz
87def15d923fec818167bdcc750cdd01 143216 science optional
murasaki-common_1.68.6-2_all.deb
098819356b43e8c9fd199700b0a991fb 557220 science optional
murasaki-mpi_1.68.6-2_amd64.deb
3752eb4259903c7aa43dad59aaa600ff 467902 science optional
murasaki_1.68.6-2_amd64.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIbBAEBCAAGBQJVi6qAAAoJEFeKBJTRxkbRxdsP9AptWhoDBWDoMPP6T5j5R2TP
Bug#788321: elinks: FTBFS on arm64
Hi Wookey,
On Thu, Jun 25, 2015 at 01:07:08AM +0100, Wookey wrote:
Moritz Mühlenhoff j...@inutil.org wrote:
I have been holding this back since dh compat level 10 is supposed
to do that by default
This has been mentioned as a possible enhancement of debhelper but is
not scheduled or certain yet:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480576#35
so we get to do it manually for a while longer.
Ah, ok. I thought that was done already.
Edmund Grimley Evans edmund.grimley.ev...@gmail.com wrote:
I was able to build successfully if I replaced
--with autoreconf
with either
--with autotools-dev
or
--with autoreconf,autotools-dev
The latter is correct. See
https://wiki.debian.org/Autoreconf#dh-autoreconf_and_autotools-dev
This package uses autoconf, but not libtool or automake. So
dh_autoreconf will not update config.{sub,guess} on its own.
autotools-dev also needs to be installed and used.
I've just confirmed that doing this does indeed fix matters
(autotools-dev is still in the control file so the above one-line
change is all that's needed). Patch attached anyway, as I've done one.
What I don't understand is why elinks built before on arm64, e.g. in
jessie?
I'm happy to NMU this if you like.
Thanks, but I'll do it this weekend, just haven't come around to it yet
(and want to fold in another fix as well).
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789897: Acknowledgement (failure on upgrade, file conflict with ndiff)
Control: reassign -1 ndiff Control: found -1 6.47-5 Control: retitle -1 failure on upgrade, file conflict with zenmap Actually, the bug is in ndiff. I was mislead by this changelog message: * Moved ndiff.py to zenmap (Closes: #789776) Looks like this was actually the other way around. The ndiff.py file was moved from zenmap to ndiff and ndiff doesn't have a proper Breaks/Replaces against zenmap. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#789897: Acknowledgement (failure on upgrade, file conflict with ndiff)
Processing control commands: reassign -1 ndiff Bug #789897 [zenmap] failure on upgrade, file conflict with ndiff Bug reassigned from package 'zenmap' to 'ndiff'. No longer marked as found in versions nmap/6.47-5. Ignoring request to alter fixed versions of bug #789897 to the same values previously set found -1 6.47-5 Bug #789897 [ndiff] failure on upgrade, file conflict with ndiff Marked as found in versions nmap/6.47-5. retitle -1 failure on upgrade, file conflict with zenmap Bug #789897 [ndiff] failure on upgrade, file conflict with ndiff Changed Bug title to 'failure on upgrade, file conflict with zenmap' from 'failure on upgrade, file conflict with ndiff' -- 789897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789897 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789832: unburden-home-dir: FTBFS: t/unexpected-cases.t fails on amd64
Control: tag -1 - moreinfo unreproducible Control: severity -1 important Hi, solo-debianb...@goeswhere.com wrote: On Thu, Jun 25, 2015 at 12:03:04AM +0200, Axel Beckert wrote: t/undo.t ... ok t/unexpected-cases.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/98 subtests thanks for the report, but I couldn't reproduce this, neither with 0.3.3 nor with the HEAD of the git repository. And https://reproducible.debian.net/rb-pkg/unstable/amd64/unburden-home-dir.html shows different tests failing, but not t/unexpected-cases.t. Can you please explain a little bit more about your setup? pbuilder or sbuild? On which file system where the tests run? (And if the reporting machine was not the same as the machine where the issue happend: Which locale was set? Which init system was used? Which kernel was running?) etc. Hah. After far too much staring, the test which is failing for me is: ok 93 - Make list file t/zo4O_qcnum/list unreadable ok 94 - Call 'perl bin/unburden-home-dir -C t/zo4O_qcnum/config -c /dev/null -L t/zo4O_qcnum/list -l /dev/null' not ok 95 - Check STDERR # Failed test 'Check STDERR' # at t/lib/Test/UBH.pm line 260. # --- Got # +++ Expected # @@ -1 +1,2 @@ # -'' # +'List file t/8mn4dawfHl/list isn\'t readable, skipping at # unburden-home-dir line n. # +' # Looks like you failed 1 test of 98. It's running chmod foo cat foo, and expecting it to fail. It succeeds for me as I have a better simulation of root: I'm running the build as very-nearly root on a VM. (root in an unpriviliged LXC container). Interesting case. The full build log isn't much more useful; sorry for missing some important parts in the initial report: https://paste.debian.net/260610/ Yeah, the above already suffices. Thanks for the details. My specific bug is probably invalid, in this case? Not sure. Will have to investigate. I've allowed myself to at least downgrade it to non-rc. I don't think we expect the builds to pass as root. Well, actually we do expect that. :-) But then again that test should still fail in that case. Weird test, though. Well, it's a test which checks if unburden-home-dir has regressions in error handling. Regards, Axel -- ,''`. | Axel Beckert a...@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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#789832: unburden-home-dir: FTBFS: t/unexpected-cases.t fails on amd64
Processing control commands: tag -1 - moreinfo unreproducible Bug #789832 [unburden-home-dir] unburden-home-dir: FTBFS: t/unexpected-cases.t fails on amd64 Removed tag(s) moreinfo and unreproducible. severity -1 important Bug #789832 [unburden-home-dir] unburden-home-dir: FTBFS: t/unexpected-cases.t fails on amd64 Severity set to 'important' from 'serious' -- 789832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789978: FTBFS: lua5.2: test_discount.lua:49: attempt to index global 'lu' (a nil value)
Source: lua-discount Version: 1.2.10.1-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build, during tests(?): Making target test for debian/lua5.2.dh-lua.conf ** lua dynamic (5.2) * Test: test_discount.lua lua5.2: test_discount.lua:49: attempt to index global 'lu' (a nil value) stack traceback: test_discount.lua:49: in main chunk [C]: in ? /usr/share/dh-lua/make/dh-lua.Makefile.single:288: recipe for target 'test-lua-dynamic-real' failed make[2]: *** [test-lua-dynamic-real] Error 1 /usr/share/dh-lua/make/dh-lua.Makefile.multiple:12: recipe for target 'test' failed Alternative build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/lua-discount.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: limit source to xjadeo, tagging 778184
Processing commands for cont...@bugs.debian.org: limit source xjadeo Limiting to bugs with field 'source' containing at least one of 'xjadeo' Limit currently set to 'source':'xjadeo' tags 778184 + pending Bug #778184 [src:xjadeo] xjadeo: ftbfs with GCC-5 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 778184: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789990: FTBFS: AttributeAlias.java: error: package com.netscape.management.client.util does not exist
Source: 389-ds-console Version: 1.2.7-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: build: [javac] /tmp/buildd/389-ds-console-1.2.7/build.xml:102: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 359 source files to /tmp/buildd/389-ds-console-1.2.7/build/classes [javac] warning: [options] bootstrap class path not set in conjunction with -source 1.5 [javac] /tmp/buildd/389-ds-console-1.2.7/src/com/netscape/admin/dirserv/AttributeAlias.java:23: error: package com.netscape.management.client.util does not exist [javac] import com.netscape.management.client.util.ResourceSet; Full build log: https://reproducible.debian.net/rb-pkg/testing/amd64/389-ds-console.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789991: FTBFS: Test failures including FixtureS.TestPanicOnSetUpSuite, FixtureS.TestPanicOnSetUpTest
Source: golang-gocheck Version: 0.0~bzr20131118+85-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build during its tests: -- FAIL: fixture_test.go:132: FixtureS.TestPanicOnSetUpSuite fixture_test.go:153: c.Check(output.value, Matches, expected) value string = + \n + --\n + PANIC: gocheck_test.go:119: FixtureHelper.SetUpSuite\n + \n + ... Panic: SetUpSuite (PC=0x43A0F5)\n + \n + /usr/lib/go/src/runtime/asm_amd64.s:401\n + in call16\n + /usr/lib/go/src/runtime/panic.go:387\n + in gopanic\n + gocheck_test.go:109\n + in FixtureHelper.trace\n + gocheck_test.go:120\n + in FixtureHelper.SetUpSuite\n + /usr/lib/go/src/runtime/asm_amd64.s:401\n + in call16\n regex string = + ^\n + -+\n + PANIC: gocheck_test\\.go:[0-9]+: FixtureHelper.SetUpSuite\n + \n + \\.\\.\\. Panic: SetUpSuite \\(PC=[xA-F0-9]+\\)\n + \n + .+:[0-9]+\n + in panic\n + .*gocheck_test.go:[0-9]+\n + in FixtureHelper.trace\n + .*gocheck_test.go:[0-9]+\n + in FixtureHelper.SetUpSuite\n + .+:[0-9]+\n + in call[0-9]+\n + $ OOPS: 119 passed, 5 FAILED --- FAIL: Test (0.18s) FAIL exit status 1 FAILlaunchpad.net/gocheck 0.186s I can reproduce these five tests failing locally. Jenkins finds some benchmark tests failing too: https://reproducible.debian.net/rb-pkg/unstable/amd64/golang-gocheck.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778101: marked as forwarded (rcs-blame: ftbfs with GCC-5)
Your message dated Fri, 26 Jun 2015 14:51:47 +1000 with message-id 20150626045147.gb4...@daedalus.andrew.net.au has caused the report #778101, regarding rcs-blame: ftbfs with GCC-5 to be marked as having been forwarded to the upstream software author(s) foo...@users.sourceforge.net (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.) -- 778101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Hi, It looks like rcs-blame has bitrotted a bit with GCC-5. Is this something you could address? If you maintain the Cc on this email, our bug tracking system will be kept in the loop. regards Andrew On Thu, Feb 12, 2015 at 10:36:32AM +, Matthias Klose wrote: Package: src:rcs-blame Version: 1.3.1-4 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/rcs-blame_1.3.1-4_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] ../lib/libmisc.a(argp-parse.o): In function `_option_is_end': /«PKGBUILDDIR»/lib/argp.h:605: multiple definition of `_option_is_end' blame.o:/«PKGBUILDDIR»/src/../lib/argp.h:605: first defined here ../lib/libmisc.a(argp-pvh.o): In function `argp_usage': /«PKGBUILDDIR»/lib/argp.h:587: multiple definition of `argp_usage' blame.o:/«PKGBUILDDIR»/src/../lib/argp.h:587: first defined here ../lib/libmisc.a(argp-pvh.o): In function `_option_is_short': /«PKGBUILDDIR»/lib/argp.h:593: multiple definition of `_option_is_short' blame.o:/«PKGBUILDDIR»/src/../lib/argp.h:593: first defined here ../lib/libmisc.a(argp-pvh.o): In function `_option_is_end': /«PKGBUILDDIR»/lib/argp.h:605: multiple definition of `_option_is_end' blame.o:/«PKGBUILDDIR»/src/../lib/argp.h:605: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_set_lmargin': /«PKGBUILDDIR»/lib/argp-fmtstream.h:243: multiple definition of `argp_fmtstream_set_lmargin' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:243: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_set_rmargin': /«PKGBUILDDIR»/lib/argp-fmtstream.h:255: multiple definition of `argp_fmtstream_set_rmargin' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:255: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_set_wmargin': /«PKGBUILDDIR»/lib/argp-fmtstream.h:267: multiple definition of `argp_fmtstream_set_wmargin' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:267: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_point': /«PKGBUILDDIR»/lib/argp-fmtstream.h:280: multiple definition of `argp_fmtstream_point' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:280: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_write': /«PKGBUILDDIR»/lib/argp-fmtstream.h:207: multiple definition of `argp_fmtstream_write' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:207: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_putc': /«PKGBUILDDIR»/lib/argp-fmtstream.h:233: multiple definition of `argp_fmtstream_putc' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:233: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_puts': /«PKGBUILDDIR»/lib/argp-fmtstream.h:220: multiple definition of `argp_fmtstream_puts' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:220: first defined here collect2: error: ld returned 1 exit status make[4]: *** [blame] Error 1 Makefile:353: recipe for target 'blame' failed make[4]: Leaving directory
Bug#778101: rcs-blame: ftbfs with GCC-5
Hi, It looks like rcs-blame has bitrotted a bit with GCC-5. Is this something you could address? If you maintain the Cc on this email, our bug tracking system will be kept in the loop. regards Andrew On Thu, Feb 12, 2015 at 10:36:32AM +, Matthias Klose wrote: Package: src:rcs-blame Version: 1.3.1-4 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/rcs-blame_1.3.1-4_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] ../lib/libmisc.a(argp-parse.o): In function `_option_is_end': /«PKGBUILDDIR»/lib/argp.h:605: multiple definition of `_option_is_end' blame.o:/«PKGBUILDDIR»/src/../lib/argp.h:605: first defined here ../lib/libmisc.a(argp-pvh.o): In function `argp_usage': /«PKGBUILDDIR»/lib/argp.h:587: multiple definition of `argp_usage' blame.o:/«PKGBUILDDIR»/src/../lib/argp.h:587: first defined here ../lib/libmisc.a(argp-pvh.o): In function `_option_is_short': /«PKGBUILDDIR»/lib/argp.h:593: multiple definition of `_option_is_short' blame.o:/«PKGBUILDDIR»/src/../lib/argp.h:593: first defined here ../lib/libmisc.a(argp-pvh.o): In function `_option_is_end': /«PKGBUILDDIR»/lib/argp.h:605: multiple definition of `_option_is_end' blame.o:/«PKGBUILDDIR»/src/../lib/argp.h:605: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_set_lmargin': /«PKGBUILDDIR»/lib/argp-fmtstream.h:243: multiple definition of `argp_fmtstream_set_lmargin' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:243: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_set_rmargin': /«PKGBUILDDIR»/lib/argp-fmtstream.h:255: multiple definition of `argp_fmtstream_set_rmargin' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:255: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_set_wmargin': /«PKGBUILDDIR»/lib/argp-fmtstream.h:267: multiple definition of `argp_fmtstream_set_wmargin' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:267: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_point': /«PKGBUILDDIR»/lib/argp-fmtstream.h:280: multiple definition of `argp_fmtstream_point' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:280: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_write': /«PKGBUILDDIR»/lib/argp-fmtstream.h:207: multiple definition of `argp_fmtstream_write' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:207: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_putc': /«PKGBUILDDIR»/lib/argp-fmtstream.h:233: multiple definition of `argp_fmtstream_putc' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:233: first defined here ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_puts': /«PKGBUILDDIR»/lib/argp-fmtstream.h:220: multiple definition of `argp_fmtstream_puts' ../lib/libmisc.a(argp-help.o):/«PKGBUILDDIR»/lib/argp-fmtstream.h:220: first defined here collect2: error: ld returned 1 exit status make[4]: *** [blame] Error 1 Makefile:353: recipe for target 'blame' failed make[4]: Leaving directory '/«PKGBUILDDIR»/src' make[3]: *** [all] Error 2 Makefile:275: recipe for target 'all' failed make[3]: Leaving directory '/«PKGBUILDDIR»/src' make[2]: *** [all-recursive] Error 1 Makefile:322: recipe for target 'all-recursive' failed make[2]: Leaving directory '/«PKGBUILDDIR»' make[1]: *** [all] Error 2 Makefile:258: recipe for target 'all' failed make[1]: Leaving directory '/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [build-arch] Error 2 debian/rules:7: recipe for target 'build-arch' failed dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 signature.asc Description: Digital signature
Bug#777994: marked as done (maildir-utils: ftbfs with GCC-5)
Your message dated Fri, 26 Jun 2015 14:23:35 +0900 with message-id 20150626052335.gj13...@auth.logic.tuwien.ac.at and subject line closing this bug has caused the Debian Bug report #777994, regarding maildir-utils: ftbfs with GCC-5 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.) -- 777994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:maildir-utils Version: 0.9.9.6-5 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/maildir-utils_0.9.9.6-5_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] In file included from mu-maildir.c:36:0: mu-maildir.c: In function 'mu_maildir_mkdir': mu-maildir.c:120:35: warning: ISO C does not support '__FUNCTION__' predefined identifier [-Wpedantic] MU_WRITE_LOG (%s (%s, %o, %s), __FUNCTION__, ^ mu-util.h:414:10: note: in definition of macro 'MU_WRITE_LOG' __VA_ARGS__); \ ^ In file included from /usr/include/glib-2.0/glib.h:62:0, from /usr/include/glib-2.0/glib/gprintf.h:21, from mu-maildir.c:34: mu-maildir.c: In function 'process_file': mu-maildir.c:241:7: warning: ISO C does not support '__FUNCTION__' predefined identifier [-Wpedantic] __FUNCTION__, fullpath); ^ mu-maildir.c: In function 'mu_maildir_get_maildir_from_path': mu-maildir.c:738:7: warning: ISO C does not support '__FUNCTION__' predefined identifier [-Wpedantic] __FUNCTION__, path); ^ CC mu-msg-crypto.lo CXX mu-msg-doc.lo In file included from /usr/include/xapian.h:40:0, from mu-msg-doc.cc:24: /usr/include/xapian/version.h:28:2: error: #error The C++ ABI version of compiler you are using does not match #error The C++ ABI version of compiler you are using does not match ^ /usr/include/xapian/version.h:29:2: error: #error that of the compiler used to build the library. The versions #error that of the compiler used to build the library. The versions ^ /usr/include/xapian/version.h:30:2: error: #error must match or your program will not work correctly. #error must match or your program will not work correctly. ^ /usr/include/xapian/version.h:31:2: error: #error The Xapian library was built with g++ 4.9.1 #error The Xapian library was built with g++ 4.9.1 ^ make[4]: *** [mu-msg-doc.lo] Error 1 Makefile:578: recipe for target 'mu-msg-doc.lo' failed make[4]: Leaving directory '/«PKGBUILDDIR»/lib' make[3]: *** [all-recursive] Error 1 Makefile:597: recipe for target 'all-recursive' failed make[3]: Leaving directory '/«PKGBUILDDIR»/lib' make[2]: *** [all-recursive] Error 1 Makefile:427: recipe for target 'all-recursive' failed make[2]: Leaving directory '/«PKGBUILDDIR»' make[1]: *** [all] Error 2 Makefile:357: recipe for target 'all' failed make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [build-stamp] Error 2 debian/rules:32: recipe for target 'build-stamp' failed dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ---End Message--- ---BeginMessage--- THis is a rubbish bug, as clearly indicated in the bug log. The problem is that xapian was build with gcc 4.9.1 and the api version has changed. That means, that the error report has no indication whatsoever whether the package actually build fails with gcc 5 *AFTER* xapian is updated. Closing this bug. I love automatized bug reproting Norbert
Processed: Re: libsocl-contrib-1.2-0, libsocl-1.2-0: missing breaks+replaces against each other
Processing control commands:
found -1 1.2.0~rc2+dfsg-1
Bug #779599 {Done: Samuel Thibault sthiba...@debian.org}
[libsocl-contrib-1.2-0,libsocl-1.2-0] libsocl-contrib-1.2-0, libsocl-1.2-0:
missing breaks+replaces against each other
Marked as found in versions starpu/1.2.0~rc2+dfsg-1 and
starpu-contrib/1.2.0~rc2+dfsg-1; no longer marked as fixed in versions
starpu-contrib/1.2.0~rc2+dfsg-1 and starpu/1.2.0~rc2+dfsg-1 and reopened.
--
779599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: python3-grib: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man1/grib_repack.1.gz
Processing control commands:
found -1 2.0.0-2
Bug #789661 {Done: Alastair McKinstry mckins...@debian.org} [python3-grib]
python3-grib: fails to upgrade from 'testing' - trying to overwrite
/usr/share/man/man1/grib_repack.1.gz
Marked as found in versions pygrib/2.0.0-2; no longer marked as fixed in
versions pygrib/2.0.0-2 and reopened.
--
789661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789661: python3-grib: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man1/grib_repack.1.gz
Followup-For: Bug #789661 Control: found -1 2.0.0-2 problem is still there Selecting previously unselected package python3-grib. Preparing to unpack .../python3-grib_2.0.0-2_amd64.deb ... Unpacking python3-grib (2.0.0-2) ... dpkg: error processing archive /var/cache/apt/archives/python3-grib_2.0.0-2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/grib_repack.1.gz', which is also in package python-grib-doc 1.9.9-2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/python3-grib_2.0.0-2_amd64.deb Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777974: Patch for GCC 5 build issue
Here's a fix for this build issue. Note that there are different ways to solve this, depending on which compilers / C standards you want to support. There's a really good description at https://gcc.gnu.org/onlinedocs/cpp/Variadic-Macros.html Martin -- Martin Michlmayr Linux for HP Helion OpenStack, Hewlett-Packard diff -urN a/libspf2-1.2.10/debian/patches/gcc5-build-fix.patch libspf2-1.2.10/debian/patches/gcc5-build-fix.patch --- libspf2-1.2.10/debian/patches/gcc5-build-fix.patch 1970-01-01 00:00:00.0 + +++ libspf2-1.2.10/debian/patches/gcc5-build-fix.patch 2015-06-25 13:03:52.310239946 + @@ -0,0 +1,12 @@ + +--- a/src/include/spf_log.h 2015-06-25 13:00:51.866236212 + b/src/include/spf_log.h 2015-06-25 13:01:11.838236625 + +@@ -63,7 +63,7 @@ + #define SPF_errorf(format, ... ) SPF_errorx( __FILE__, __LINE__, format, __VA_ARGS__ ) + #define SPF_warningf(format, ... ) SPF_warningx( __FILE__, __LINE__, format, __VA_ARGS__ ) + #define SPF_infof(format, ... ) SPF_infox( __FILE__, __LINE__, format, __VA_ARGS__ ) +-#define SPF_debugf(format, ... ) SPF_debugx( __FILE__, __LINE__, format, __VA_ARGS__ ) ++#define SPF_debugf(format, ... ) SPF_debugx( __FILE__, __LINE__, format, #__VA_ARGS__ ) + + #elif defined( __GNUC__ ) + diff -urN a/libspf2-1.2.10/debian/patches/series libspf2-1.2.10/debian/patches/series --- libspf2-1.2.10/debian/patches/series 2014-10-12 19:15:29.0 + +++ libspf2-1.2.10/debian/patches/series 2015-06-25 13:03:58.486240074 + @@ -1,2 +1,3 @@ spf_dns-include-std-headers.patch abolish-spf-rrtype.patch +gcc5-build-fix.patch
Bug#778124: Patch for GCC 5 build issue
tags 778124 + patch thanks Here's a fix for the GCC 5 build issue. Long term, upstream should consider Different semantics for inline functions at https://gcc.gnu.org/gcc-5/porting_to.html but it seems there's no active upstream... -- Martin Michlmayr Linux for HP Helion OpenStack, Hewlett-Packard --- a/debian/rules 2015-06-25 13:09:35.718247053 + +++ b/debian/rules 2015-06-25 13:09:54.082247433 + @@ -13,7 +13,7 @@ DEB_INSTALL_CHANGELOGS_ALL = ChangeLog #CC= gcc -CFLAGS += $(CPPFLAGS) -I. -DUSE_PPP -DUSE_MS_DNS -fno-strict-aliasing -Wno-unused +CFLAGS += $(CPPFLAGS) -I. -DUSE_PPP -DUSE_MS_DNS -fno-strict-aliasing -Wno-unused -std=gnu89 PPPCFLAGS = $(CFLAGS) LDFLAGS += -Wl,--as-needed
Bug#789936: libnetcdf-cxx-legacy-dev: fails to upgrade from 'sid' - trying to overwrite /usr/include/ncvalues.h
Package: libnetcdf-cxx-legacy-dev Version: 4.2-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package libnetcdf-c++4. Preparing to unpack .../libnetcdf-c++4_4.2-1~exp1_amd64.deb ... Unpacking libnetcdf-c++4 (4.2-1~exp1) ... Selecting previously unselected package libnetcdf-cxx-legacy-dev. Preparing to unpack .../libnetcdf-cxx-legacy-dev_4.2-1~exp1_amd64.deb ... Unpacking libnetcdf-cxx-legacy-dev (4.2-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/libnetcdf-cxx-legacy-dev_4.2-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/include/ncvalues.h', which is also in package libnetcdf-dev 1:4.1.3-7.2 Errors were encountered while processing: /var/cache/apt/archives/libnetcdf-cxx-legacy-dev_4.2-1~exp1_amd64.deb cheers, Andreas libnetcdf-dev=1%4.1.3-7.2_libnetcdf-cxx-legacy-dev=4.2-1~exp1.log.gz Description: application/gzip
Bug#789922: kio-dev: uninstallable on current unstable
Hi Lisandro, Lisandro Damián Nicanor Pérez Meyer perezme...@gmail.com wrote: Qt5 is currently going trough a transition, so this is just OK. You just need to wait until it's sorted out. Actually you will need to wait until the package gets pushed to unstable or rebuilt in experimental. It should happen soon though. OK, thank you for your quick answer. I will wait, then. :) Regards -- Florent -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789935: libnetcdff-dev: fails to upgrade from 'sid' - trying to overwrite /usr/include/typesizes.mod
Package: libnetcdff-dev Version: 4.4.2-1~exp2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package libnetcdff6. Preparing to unpack .../libnetcdff6_4.4.2-1~exp2_amd64.deb ... Unpacking libnetcdff6 (4.4.2-1~exp2) ... Selecting previously unselected package libnetcdff-dev. Preparing to unpack .../libnetcdff-dev_4.4.2-1~exp2_amd64.deb ... Unpacking libnetcdff-dev (4.4.2-1~exp2) ... dpkg: error processing archive /var/cache/apt/archives/libnetcdff-dev_4.4.2-1~exp2_amd64.deb (--unpack): trying to overwrite '/usr/include/typesizes.mod', which is also in package libnetcdf-dev 1:4.1.3-7.2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libnetcdff-dev_4.4.2-1~exp2_amd64.deb cheers, Andreas libnetcdf-dev=1%4.1.3-7.2_libnetcdff-dev=4.4.2-1~exp2.log.gz Description: application/gzip
Processed: tagging 785224, tagging 786332, tagging 784378, tagging 787877, tagging 786659, tagging 787627 ...
Processing commands for cont...@bugs.debian.org:
tags 785224 + stretch sid
Bug #785224 {Done: Mike Gabriel sunwea...@debian.org} [mate-user-share]
mate-user-share: depends on transitional package apache2.2-bin
Added tag(s) sid and stretch.
tags 786332 + stretch sid
Bug #786332 {Done: Jean-Michel Vourgère nir...@debian.org} [openjpip-server]
openjpip-server depends on gone package apache2.2-bin
Added tag(s) stretch and sid.
tags 784378 + sid stretch
Bug #784378 {Done: georg...@debian.org} [src:fritzing] fritzing: Should not
depend on libqt4-webkit
Added tag(s) sid and stretch.
tags 787877 + sid stretch
Bug #787877 [src:clinica] clinica: FTBFS with valac 0.28
Added tag(s) sid and stretch.
tags 786659 + sid stretch
Bug #786659 [src:git-annex] Do not depend on libghc-hamlet-dev
Added tag(s) stretch and sid.
tags 787627 + sid stretch
Bug #787627 [src:gnome-python-extras] gnome-python-extras: stay out of testing
Added tag(s) stretch and sid.
tags 789026 + sid stretch
Bug #789026 [src:gnubiff] gnubiff: Patch to port to libpanel-applet 3.14+
Added tag(s) stretch and sid.
tags 789400 + sid stretch
Bug #789400 [src:gucharmap] gucharmap: needs update for unicode-data 8.0-1 and
Built-Using field
Added tag(s) stretch and sid.
tags 787463 + sid stretch
Bug #787463 {Done: Salvatore Bonaccorso car...@debian.org}
[src:libquota-perl] libquota-perl: FTBFS with Linux 4.x
Added tag(s) stretch and sid.
tags 789830 + sid stretch
Bug #789830 [src:libterm-filter-perl] libterm-filter-perl: FTBFS in sid: test
failures
Added tag(s) stretch and sid.
tags 789833 + sid stretch
Bug #789833 [src:mat] mat: FTBFS in sid: test failures
Added tag(s) stretch and sid.
tags 787486 + sid stretch
Bug #787486 [src:ppl] ppl: FTBFS with current sid
Added tag(s) sid and stretch.
tags 787875 + sid stretch
Bug #787875 [src:steadyflow] steadyflow: FTBFS with valac 0.28
Added tag(s) sid and stretch.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
784378: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784378
785224: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785224
786332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786332
786659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786659
787463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787463
787486: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787486
787627: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787627
787875: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787875
787877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787877
789026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789026
789400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789400
789830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789830
789833: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777788: Patch for GCC 5 build isse
tags 88 + patch thanks Here's a fix for this build issue. Note that there are different ways to solve this, depending on which compilers / C standards you want to support. There's a really good description at https://gcc.gnu.org/onlinedocs/cpp/Variadic-Macros.html Martin -- Martin Michlmayr Linux for HP Helion OpenStack, Hewlett-Packard Here's a fix for this build issue. Note that there are different ways to solve this, depending on which compilers / C standards you want to support. There's a really good description at https://gcc.gnu.org/onlinedocs/cpp/Variadic-Macros.html Martin diff -urN a/autounit-0.20.1/debian/patches/30_gcc5_build_fix.patch autounit-0.20.1/debian/patches/30_gcc5_build_fix.patch --- autounit-0.20.1/debian/patches/30_gcc5_build_fix.patch 1970-01-01 00:00:00.0 + +++ autounit-0.20.1/debian/patches/30_gcc5_build_fix.patch 2015-06-25 12:49:45.118222413 + @@ -0,0 +1,44 @@ +--- a/c-unit/autounit.h 2006-07-13 20:50:07.0 + b/c-unit/autounit.h 2015-06-25 12:48:20.690220665 + +@@ -200,29 +200,29 @@ + + + #if defined (__STDC_VERSION__) __STDC_VERSION__ = 199901L +-#define au_assert(t, expr, err_msg, ...) au_assert_true(t, expr, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_assert(t, expr, err_msg, ...) au_assert_true(t, expr, __FILE__, __LINE__, err_msg, ##__VA_ARGS__) + +-#define au_assert_fail(t, err_msg, ...) au_assert_true(t, 0, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_assert_fail(t, err_msg, ...) au_assert_true(t, 0, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + +-#define au_assert_succeed(t, err_msg, ...) au_assert_true(t, 1, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_assert_succeed(t, err_msg, ...) au_assert_true(t, 1, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + +-#define au_asserteq_str(t, str1, str2, err_msg, ...) au_assert_str_int(t, AU_REL_EQUAL, str1, str2, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_asserteq_str(t, str1, str2, err_msg, ...) au_assert_str_int(t, AU_REL_EQUAL, str1, str2, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + +-#define au_assertrel_str(t, type, str1, str2, err_msg, ...) au_assert_str_int(t, type, str1, str2, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_assertrel_str(t, type, str1, str2, err_msg, ...) au_assert_str_int(t, type, str1, str2, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + +-#define au_asserteq_uint64(t, in1, in2, err_msg, ...) au_assert_guint64_int(t, AU_REL_EQUAL, in1, in2, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_asserteq_uint64(t, in1, in2, err_msg, ...) au_assert_guint64_int(t, AU_REL_EQUAL, in1, in2, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + +-#define au_assertrel_uint64(t, type, in1, in2, err_msg, ...) au_assert_guint64_int(t, type, in1, in2, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_assertrel_uint64(t, type, in1, in2, err_msg, ...) au_assert_guint64_int(t, type, in1, in2, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + +-#define au_asserteq_int(t, in1, in2, err_msg, ...) au_assert_gint64_int(t, AU_REL_EQUAL, in1, in2, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_asserteq_int(t, in1, in2, err_msg, ...) au_assert_gint64_int(t, AU_REL_EQUAL, in1, in2, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + +-#define au_assertrel_int(t, type, in1, in2, err_msg, ...) au_assert_gint64_int(t, type, in1, in2, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_assertrel_int(t, type, in1, in2, err_msg, ...) au_assert_gint64_int(t, type, in1, in2, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + +-#define au_asserteq_char(t, in1, in2, err_msg, ...) au_asserteq_char_int(t, in1, in2, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_asserteq_char(t, in1, in2, err_msg, ...) au_asserteq_char_int(t, in1, in2, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + +-#define au_asserteq_obj(t, ob1, ob2, compare_func, err_msg, ...) au_assert_obj_int(t, AU_REL_EQUAL, (gpointer)ob1, (gpointer)ob2, compare_func, 0, 0, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_asserteq_obj(t, ob1, ob2, compare_func, err_msg, ...) au_assert_obj_int(t, AU_REL_EQUAL, (gpointer)ob1, (gpointer)ob2, compare_func, 0, 0, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + +-#define au_assertrel_obj(t, type, ob1, ob2, compare_func, err_msg, ...) au_assert_obj_int(t, type, (gpointer)ob1, (gpointer)ob2, compare_func, 0, 0, __FILE__, __LINE__, err_msg, __VA_ARGS__) ++#define au_assertrel_obj(t, type, ob1, ob2, compare_func, err_msg, ...) au_assert_obj_int(t, type, (gpointer)ob1, (gpointer)ob2, compare_func, 0, 0, __FILE__, __LINE__, err_msg, #__VA_ARGS__) + + #define au_assert_null(t, ob1, err_msg, ...) au_assert(t, ob1 == 0, __FILE__, __LINE__, err_msg, __VA_ARGS__) + diff -urN a/autounit-0.20.1/debian/patches/series autounit-0.20.1/debian/patches/series --- autounit-0.20.1/debian/patches/series 2012-02-27 10:04:50.0 + +++ autounit-0.20.1/debian/patches/series 2015-06-25 12:44:01.198215295 + @@ -2,3 +2,4 @@ 10_netstring.patch
Bug#777799: marked as done (bird: ftbfs with GCC-5)
Your message dated Thu, 25 Jun 2015 13:40:36 +0200 with message-id 1435232436.3133834.307417833.66a9b...@webmail.messagingengine.com and subject line Fixed in 1.5.0 has caused the Debian Bug report #99, regarding bird: ftbfs with GCC-5 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.) -- 99: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=99 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:bird Version: 1.4.5-1 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/bird_1.4.5-1_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] cf-lex.o: In function `rem2_node': /«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:113: multiple definition of `rem2_node' cf-parse.tab.o:/«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:113: first defined here cf-lex.o: In function `replace_node': /«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:136: multiple definition of `replace_node' cf-parse.tab.o:/«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:136: first defined here cf-lex.o: In function `init_list': /«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:153: multiple definition of `init_list' cf-parse.tab.o:/«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:153: first defined here cf-lex.o: In function `add_tail_list': /«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:169: multiple definition of `add_tail_list' cf-parse.tab.o:/«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:169: first defined here conf.o: In function `add_tail': /«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:42: multiple definition of `add_tail' cf-parse.tab.o:/«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:42: first defined here conf.o: In function `add_head': /«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:60: multiple definition of `add_head' cf-parse.tab.o:/«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:60: first defined here conf.o: In function `insert_node': /«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:79: multiple definition of `insert_node' cf-parse.tab.o:/«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:79: first defined here conf.o: In function `rem_node': /«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:96: multiple definition of `rem_node' cf-parse.tab.o:/«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:96: first defined here conf.o: In function `rem2_node': /«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:113: multiple definition of `rem2_node' cf-parse.tab.o:/«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:113: first defined here conf.o: In function `replace_node': /«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:136: multiple definition of `replace_node' cf-parse.tab.o:/«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:136: first defined here conf.o: In function `init_list': /«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:153: multiple definition of `init_list' cf-parse.tab.o:/«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:153: first defined here conf.o: In function `add_tail_list': /«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:169: multiple definition of `add_tail_list' cf-parse.tab.o:/«PKGBUILDDIR»/build-ipv4/conf/../lib/lists.c:169: first defined here collect2: error: ld returned 1 exit status make[3]: *** [all.o] Error 1 ../Rules:71: recipe for target 'all.o' failed make[3]: Leaving directory '/«PKGBUILDDIR»/build-ipv4/conf' make[2]: *** [subdir] Error 2 Makefile:36: recipe for target 'subdir' failed make[2]: Leaving directory '/«PKGBUILDDIR»/build-ipv4' dh_auto_build: make -j1 returned exit code 2 make[1]: ***
Bug#789922: kio-dev: uninstallable on current unstable
On Thursday 25 June 2015 10:00:35 Lisandro Damián Nicanor Pérez Meyer wrote: On Thursday 25 June 2015 11:31:29 Florent Rougon wrote: Package: kio-dev Version: 5.9.0-1 Severity: serious Justification: Policy 7.2 Hello, Since yesterday's upgrade, kio-dev is not installable anymore on sid: Hi Florent! You are right, but: [snip] libkf5completion5 : Depends: qtbase-abi-5-3-2 which is a virtual package. Qt5 is currently going trough a transition, so this is just OK. You just need to wait until it's sorted out. Actually you will need to wait until the package gets pushed to unstable or rebuilt in experimental. It should happen soon though. -- The generation of random numbers is too important to be left to chance. http://www.devtopics.com/best-programming-jokes/ Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Processed: Patch
Processing commands for cont...@bugs.debian.org: tags 778124 + patch Bug #778124 [src:slirp] slirp: ftbfs with GCC-5 Added tag(s) patch. -- Stopping processing here. Please contact me if you need assistance. -- 778124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Patch
Processing commands for cont...@bugs.debian.org: tags 88 + patch Bug #88 [src:autounit] autounit: ftbfs with GCC-5 Added tag(s) patch. -- Stopping processing here. Please contact me if you need assistance. -- 88: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=88 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 632948 is serious, user debian...@lists.debian.org, usertagging 786786 ...
Processing commands for cont...@bugs.debian.org: severity 632948 serious Bug #632948 [qtemu] qtemu 2.0~alpha1-1 FTBS in experimental Severity set to 'serious' from 'wishlist' user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). usertags 786786 piuparts There were no usertags set. Usertags are now: piuparts. usertags 786368 piuparts Usertags were: piuparts. Usertags are now: piuparts. found 789893 3.7.5-5 Bug #789893 [libvolk-bin,libvolk1.0-bin] libvolk1.0-bin and libvolk-bin: error when trying to install together There is no source info for the package 'libvolk1.0-bin' at version '3.7.5-5' with architecture '' Marked as found in versions gnuradio/3.7.5-5. found 789893 1.0-1 Bug #789893 [libvolk-bin,libvolk1.0-bin] libvolk1.0-bin and libvolk-bin: error when trying to install together There is no source info for the package 'libvolk-bin' at version '1.0-1' with architecture '' Marked as found in versions volk/1.0-1. found 789894 3.7.5-5 Bug #789894 [libvolk-dev,libvolk1.0-dev] libvolk1.0-dev and libvolk-dev: error when trying to install together There is no source info for the package 'libvolk1.0-dev' at version '3.7.5-5' with architecture '' Marked as found in versions gnuradio/3.7.5-5. found 789894 1.0-1 Bug #789894 [libvolk-dev,libvolk1.0-dev] libvolk1.0-dev and libvolk-dev: error when trying to install together There is no source info for the package 'libvolk-dev' at version '1.0-1' with architecture '' Marked as found in versions volk/1.0-1. severity 782817 serious Bug #782817 [pyfits-utils] pyfits-utils: Please consider removing pyfits-utils Severity set to 'serious' from 'wishlist' affects 782817 + astropy-utils Bug #782817 [pyfits-utils] pyfits-utils: Please consider removing pyfits-utils Added indication that 782817 affects astropy-utils notfound 782817 1:3.3-2 Bug #782817 [pyfits-utils] pyfits-utils: Please consider removing pyfits-utils No longer marked as found in versions pyfits/1:3.3-2. found 782817 1:3.3-3 Bug #782817 [pyfits-utils] pyfits-utils: Please consider removing pyfits-utils Marked as found in versions pyfits/1:3.3-3. affects 789894 + gnuradio-dev Bug #789894 [libvolk-dev,libvolk1.0-dev] libvolk1.0-dev and libvolk-dev: error when trying to install together Added indication that 789894 affects gnuradio-dev affects 789897 + zenmap Bug #789897 [ndiff] failure on upgrade, file conflict with zenmap Added indication that 789897 affects zenmap found 789668 1:2.4.0-2 Bug #789668 [python-swiftclient-doc] python-swiftclient-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/man/man1/swift.1.gz Marked as found in versions python-swiftclient/1:2.4.0-2. affects 789925 + gforge-common Bug #789925 [fusionforge-common] fusionforge-common: fails to upgrade from 'testing' - trying to overwrite /usr/share/locale/bg/LC_MESSAGES/fusionforge.mo Added indication that 789925 affects gforge-common thanks Stopping processing here. Please contact me if you need assistance. -- 632948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632948 782817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782817 786368: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786368 789668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789668 789893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789893 789894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789894 789897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789897 789925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789925 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Patch
Processing commands for cont...@bugs.debian.org: tags 777974 + patch Bug #777974 [src:libspf2] libspf2: ftbfs with GCC-5 Added tag(s) patch. -- Stopping processing here. Please contact me if you need assistance. -- 777974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777974 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789940: FTBFS: gtk_widget_override_background_color is deprecated and -Werror
Source: libgrip Version: 0.3.8-1 Severity: serious Tags: sid stretch Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: gesture.c: In function ‘create_window’: gesture.c:219:3: error: ‘gtk_widget_override_background_color’ is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkwidget.h:1157) [-Werror=deprecated-declarations] gtk_widget_override_background_color (app-da, GTK_STATE_NORMAL, white); ^ cc1: all warnings being treated as errors An alternative build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/libgrip.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789930: gofigure2: FTBFS in unstable
Source: gofigure2 Version: 0.9.0-3 Severity: serious You can see the log from the recent build failure on arm64 here: https://buildd.debian.org/status/package.php?p=gofigure2suite=sid I got the same error on amd64. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789894: libvolk1.0-dev and libvolk-dev: error when trying to install together
Followup-For: Bug #789894 Similar problems between libvolk1.0-dev and gnuradio-dev: Selecting previously unselected package libvolk1.0:amd64. Preparing to unpack .../libvolk1.0_1.0-2_amd64.deb ... Unpacking libvolk1.0:amd64 (1.0-2) ... Selecting previously unselected package libvolk1.0-dev. Preparing to unpack .../libvolk1.0-dev_1.0-2_amd64.deb ... Unpacking libvolk1.0-dev (1.0-2) ... dpkg: error processing archive /var/cache/apt/archives/libvolk1.0-dev_1.0-2_amd64.deb (--unpack): trying to overwrite '/usr/include/volk/volk_16i_max_star_horizontal_16i.h', which is also in package gnuradio-dev 3.7.5-5 Errors were encountered while processing: /var/cache/apt/archives/libvolk1.0-dev_1.0-2_amd64.deb Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789932: ginkgocadx: FTBFS in unstable
Source: ginkgocadx Version: 3.7.0.1465.37+dfsg-1 Severity: serious You can see the log from the recent build failure on arm64 here: https://buildd.debian.org/status/package.php?p=ginkgocadxsuite=sid I got the same error on amd64. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789931: itksnap: FTBFS in unstable
Source: itksnap Version: 2.2.0-1.1 Severity: serious You can see the log from the recent build failure on arm64 here: https://buildd.debian.org/status/package.php?p=itksnapsuite=sid I got the same error on amd64. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: raising severity for GCC 5 issues, please fix these now (see https://wiki.debian.org/GCC5)
Processing commands for cont...@bugs.debian.org:
severity 87 serious
Bug #87 [src:autofs] autofs: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 777871 serious
Bug #777871 [src:geis] geis: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 777912 serious
Bug #777912 [src:insighttoolkit] insighttoolkit: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 777914 serious
Bug #777914 [src:insserv] insserv: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 777919 serious
Bug #777919 [src:irda-utils] irda-utils: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 777935 serious
Bug #777935 [src:libapache2-mod-perl2] libapache2-mod-perl2: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 777939 serious
Bug #777939 [src:libbonoboui] libbonoboui: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 777968 serious
Bug #777968 [src:libprelude] libprelude: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 777975 serious
Bug #777975 [src:libssh] libssh: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 777976 serious
Bug #777976 [src:libvpx] libvpx: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 777991 serious
Bug #777991 [src:ltrace] ltrace: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 778000 serious
Bug #778000 [src:memtest86] memtest86: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 778009 serious
Bug #778009 [src:mknbi] mknbi: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 778046 serious
Bug #778046 [src:openmprtl] openmprtl: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 778085 serious
Bug #778085 [src:qt4-x11] qt4-x11: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 778142 serious
Bug #778142 [src:tcsh] tcsh: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 778148 serious
Bug #778148 [src:trafficserver] trafficserver: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 778187 serious
Bug #778187 [src:xorg-server] xorg-server: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 780206 serious
Bug #780206 [src:squashfs-tools] fix ftbfs with GCC 5 on armhf
Severity set to 'serious' from 'important'
severity 777955 serious
Bug #777955 [src:liblas] liblas: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 777993 serious
Bug #777993 [src:lucene++] lucene++: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 64 serious
Bug #64 [src:abook] abook: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 65 serious
Bug #65 [src:activiz.net] activiz.net: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 66 serious
Bug #66 [src:adun.app] adun.app: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 67 serious
Bug #67 [src:afnix] afnix: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 71 serious
Bug #71 [src:ants] ants: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 72 serious
Bug #72 [src:apophenia] apophenia: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 76 serious
Bug #76 [src:apron] apron: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 78 serious
Bug #78 [src:aptitude] aptitude: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 80 serious
Bug #80 [src:asmon] asmon: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 81 serious
Bug #81 [src:aspectc++] aspectc++: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 82 serious
Bug #82 [src:asterisk] asterisk: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 83 serious
Bug #83 [src:atftp] atftp: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 88 serious
Bug #88 [src:autounit] autounit: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 90 serious
Bug #90 [src:avifile] avifile: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 91 serious
Bug #91 [src:ball] ball: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 97 serious
Bug #97 [src:bbrun] bbrun: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 99 serious
Bug #99 [src:bird] bird: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 777801 serious
Bug #777801 [src:blktap] blktap: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 777803 serious
Bug #777803 [src:bomberclone] bomberclone: ftbfs with GCC-5
Severity set to 'serious' from 'important'
severity 777805 serious
Bug #777805 {Done: Dimitri John Ledkov
Bug#789922: marked as done (kio-dev: uninstallable on current unstable)
Your message dated Thu, 25 Jun 2015 10:00:35 -0300
with message-id 287049697.aoLMx3QYC9@luna
and subject line Re: Bug#789922: kio-dev: uninstallable on current unstable
has caused the Debian Bug report #789922,
regarding kio-dev: uninstallable on current unstable
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.)
--
789922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: kio-dev
Version: 5.9.0-1
Severity: serious
Justification: Policy 7.2
Hello,
Since yesterday's upgrade, kio-dev is not installable anymore on sid:
# aptitude install kio-dev
The following NEW packages will be installed:
kio{a} (for kio-dev) kio-dev libdbusmenu-qt5-2{a} (for kio-dev)
libkf5attica5{a} (for kio-dev) libkf5auth-data{a} (for kio-dev)
libkf5auth-dev{a} (for kio-dev) libkf5auth5{a} (for kio-dev)
libkf5bookmarks-data{a} (for kio-dev)
libkf5bookmarks-dev{a} (for kio-dev) libkf5bookmarks5{a} (for kio-dev)
libkf5codecs-data{a} (for kio-dev) libkf5codecs-dev{a} (for kio-dev)
libkf5codecs5{a} (for kio-dev) libkf5completion-data{a} (for kio-dev)
libkf5completion-dev{a} (for kio-dev)
libkf5completion5{ab} (for kio-dev) libkf5config-bin{a} (for kio-dev)
libkf5config-data{a} (for kio-dev) libkf5config-dev{a} (for kio-dev)
libkf5configcore5{a} (for kio-dev) libkf5configgui5{a} (for kio-dev)
libkf5configwidgets-data{a} (for kio-dev)
libkf5configwidgets-dev{a} (for kio-dev)
libkf5configwidgets5{a} (for kio-dev)
libkf5coreaddons-data{a} (for kio-dev)
libkf5coreaddons-dev{a} (for kio-dev)
libkf5coreaddons5{a} (for kio-dev) libkf5crash5{a} (for kio-dev)
libkf5dbusaddons-bin{a} (for kio-dev)
libkf5dbusaddons-data{a} (for kio-dev)
libkf5dbusaddons-dev{a} (for kio-dev)
libkf5dbusaddons5{a} (for kio-dev)
libkf5globalaccel-bin{a} (for kio-dev)
libkf5globalaccel-data{a} (for kio-dev)
libkf5globalaccel-dev{a} (for kio-dev)
libkf5globalaccel5{a} (for kio-dev)
libkf5guiaddons-dev{a} (for kio-dev) libkf5guiaddons5{a} (for kio-dev)
libkf5i18n-data{a} (for kio-dev) libkf5i18n-dev{a} (for kio-dev)
libkf5i18n5{a} (for kio-dev) libkf5iconthemes-bin{a} (for kio-dev)
libkf5iconthemes-data{a} (for kio-dev)
libkf5iconthemes-dev{a} (for kio-dev)
libkf5iconthemes5{a} (for kio-dev)
libkf5itemviews-data{a} (for kio-dev)
libkf5itemviews-dev{a} (for kio-dev) libkf5itemviews5{ab} (for kio-dev)
libkf5jobwidgets-data{a} (for kio-dev)
libkf5jobwidgets-dev{a} (for kio-dev)
libkf5jobwidgets5{a} (for kio-dev) libkf5kiocore5{a} (for kio-dev)
libkf5kiofilewidgets5{ab} (for kio-dev) libkf5kiontlm5{a} (for kio-dev)
libkf5kiowidgets5{a} (for kio-dev)
libkf5notifications-data{a} (for kio-dev)
libkf5notifications5{a} (for kio-dev)
libkf5service-bin{a} (for kio-dev) libkf5service-data{a} (for kio-dev)
libkf5service-dev{a} (for kio-dev) libkf5service5{a} (for kio-dev)
libkf5solid-dev{a} (for kio-dev) libkf5solid5{a} (for kio-dev)
libkf5solid5-data{a} (for kio-dev) libkf5sonnet-dev{a} (for kio-dev)
libkf5sonnet5-data{a} (for kio-dev) libkf5sonnetcore5{a} (for kio-dev)
libkf5sonnetui5{a} (for kio-dev)
libkf5textwidgets-data{a} (for kio-dev)
libkf5textwidgets-dev{a} (for kio-dev)
libkf5textwidgets5{a} (for kio-dev) libkf5wallet-bin{a} (for kio-dev)
libkf5wallet-data{a} (for kio-dev) libkf5wallet5{a} (for kio-dev)
libkf5widgetsaddons-data{a} (for kio-dev)
libkf5widgetsaddons-dev{a} (for kio-dev)
libkf5widgetsaddons5{a} (for kio-dev)
libkf5windowsystem-data{a} (for kio-dev)
libkf5windowsystem-dev{a} (for kio-dev)
libkf5windowsystem5{a} (for kio-dev) libkf5xmlgui-bin{a} (for kio-dev)
libkf5xmlgui-data{a} (for kio-dev) libkf5xmlgui-dev{ab} (for kio-dev)
libkf5xmlgui5{ab} (for kio-dev) libkwalletbackend5-5{a} (for kio-dev)
libphonon4qt5-4{a} (for kio-dev) libpolkit-qt5-1-1{a} (for kio-dev)
libqt5svg5{a} (for kio-dev) sonnet-plugins{a} (for kio-dev)
0 packages upgraded, 89 newly installed, 0 to remove and 0 not upgraded.
Need to get 275 kB/11.8 MB of archives. After unpacking 72.1 MB will be used.
The following packages have unmet dependencies:
libkf5completion5 : Depends: qtbase-abi-5-3-2 which is a virtual package.
libkf5xmlgui-dev : Depends: libkf5attica-dev (= 5.9.0~) but it is not going
to be installed.
libkf5xmlgui5 : Depends: qtbase-abi-5-3-2 which is a virtual package.
libkf5itemviews5 : Depends: qtbase-abi-5-3-2 which is a virtual package.
libkf5kiofilewidgets5 : Depends: qtbase-abi-5-3-2 which is a virtual package.
The following actions will resolve
Bug#789922: kio-dev: uninstallable on current unstable
On Thursday 25 June 2015 11:31:29 Florent Rougon wrote: Package: kio-dev Version: 5.9.0-1 Severity: serious Justification: Policy 7.2 Hello, Since yesterday's upgrade, kio-dev is not installable anymore on sid: Hi Florent! You are right, but: [snip] libkf5completion5 : Depends: qtbase-abi-5-3-2 which is a virtual package. Qt5 is currently going trough a transition, so this is just OK. You just need to wait until it's sorted out. Kinds regards, Lisandro. -- La vida no se mide por la cantidad de veces que respiramos, sino por la cantidad de momentos que nos quitan la respiración. Anónimo Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#779599: libsocl-contrib-1.2-0, libsocl-1.2-0: missing breaks+replaces against each other
Followup-For: Bug #779599 Control: found -1 1.2.0~rc2+dfsg-1 Still reproducible: Selecting previously unselected package libstarpu-contrib-1.2-1. (Reading database ... 7792 files and directories currently installed.) Preparing to unpack .../libstarpu-contrib-1.2-1_1.2.0~rc2+dfsg-1_amd64.deb ... Unpacking libstarpu-contrib-1.2-1 (1.2.0~rc2+dfsg-1) ... Selecting previously unselected package libsocl-contrib-1.2-0. Preparing to unpack .../libsocl-contrib-1.2-0_1.2.0~rc2+dfsg-1_amd64.deb ... Unpacking libsocl-contrib-1.2-0 (1.2.0~rc2+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/libsocl-contrib-1.2-0_1.2.0~rc2+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/libsocl-1.2.so.0.0.0', which is also in package libsocl-1.2-0 1.2.0~rc2+dfsg-1 Errors were encountered while processing: /var/cache/apt/archives/libsocl-contrib-1.2-0_1.2.0~rc2+dfsg-1_amd64.deb Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789934: libanthyinput-dev: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/libanthyinput.a
Package: libanthyinput-dev Version: 1:0.3-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package libanthyinput0:amd64. Preparing to unpack .../libanthyinput0_1%3a0.3-1_amd64.deb ... Unpacking libanthyinput0:amd64 (1:0.3-1) ... dpkg: error processing archive /var/cache/apt/archives/libanthyinput0_1%3a0.3-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libanthyinput.so.0.0.0', which is also in package libanthy0:amd64 9100h-25 Selecting previously unselected package libanthyinput-dev:amd64. Preparing to unpack .../libanthyinput-dev_1%3a0.3-1_amd64.deb ... Unpacking libanthyinput-dev:amd64 (1:0.3-1) ... dpkg: error processing archive /var/cache/apt/archives/libanthyinput-dev_1%3a0.3-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libanthyinput.a', which is also in package libanthy-dev:amd64 9100h-25 Errors were encountered while processing: /var/cache/apt/archives/libanthyinput0_1%3a0.3-1_amd64.deb /var/cache/apt/archives/libanthyinput-dev_1%3a0.3-1_amd64.deb cheers, Andreas libanthy-dev=9100h-25_libanthyinput-dev=1%0.3-1.log.gz Description: application/gzip
Bug#778142: (no subject)
During this years Debconf I will work on this bug. There's a thread about this bug at http://mx.gw.com/pipermail/tcsh-bugs/2015-May/000930.html and also a new upstream version (6.19.00). -- regards Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789932: ginkgocadx: FTBFS in unstable
Right, it fails because it can't find ITKConfig.cmake any more. When I update libinsighttoolkit3-dev -- libinsighttoolkit4-dev in Build-Depends build progresses till 73% when it fails with another error: thumbnailscommand.cpp:54:30: fatal error: itkOrientedImage.h: No such file or directory Any ideas? -- Regards, Dmitry Smirnov. --- Do your duty as you see it, and damn the consequences. -- George S. Patton signature.asc Description: This is a digitally signed message part.
Bug#789942: mapnik-vector-tile: FTBFS with mapnik 3.0(?): mapnik/graphics.hpp: No such file or directory
Package: mapnik-vector-tile Version: 0.5.1+dfsg-1.3 Severity: serious Tags: sid stretch Justification: fails to build from source (but built successfully in the past) User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build in sid: ake[2]: Entering directory '/mapnik-vector-tile-0.5.1+dfsg' echo #define MAPNIK_PLUGINDIR \/usr/lib/mapnik/3.0/input\ test/test-cfg.h In file included from test/vector_tile.cpp:6:0: test/test_utils.hpp:6:31: fatal error: mapnik/graphics.hpp: No such file or directory #include mapnik/graphics.hpp ^ compilation terminated. I believe this is due to libmapnik-dev pulling in mapnik 3.0. See also e.g. http://bugs.debian.org/788767 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/mapnik-vector-tile.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789931: itksnap: FTBFS in unstable
It looks like the ITK-SNAP build does not find the ITK directory. This is a pretty outdated version, we are up to 3.2 now... Paul On Thu, Jun 25, 2015 at 12:38 PM, Edmund Grimley Evans edmund.grimley.ev...@gmail.com wrote: Source: itksnap Version: 2.2.0-1.1 Severity: serious You can see the log from the recent build failure on arm64 here: https://buildd.debian.org/status/package.php?p=itksnapsuite=sid I got the same error on amd64. -- Paul A. Yushkevich, Ph.D. Associate Professor Penn Image Computing and Science Laboratory Department of Radiology University of Pennsylvania
Bug#789828: unreproducible / pbuilder vs. sbuild
I can't reproduce these 2 bugs. Apparently #789828 happens only with sbuild and not with p/cowbuiler, maybe #789830 falls into the same category ... Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Bob Dylan: Sad eyed lady of the lowlands signature.asc Description: Digital Signature
Bug#789985: FTBFS: IRanges_defines.h: fatal error: S4Vectors_defines.h: No such file or directory
Package: r-bioc-shortread Version: 1.22.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: config.status: creating src/Makevars ** libs make[1]: Entering directory '/tmp/buildd/r-bioc-shortread-1.22.0/src' gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -I/usr/lib/R/site-library/IRanges/include -I/usr/lib/R/site-library/XVector/include -I/usr/lib/R/site-library/Biostrings/include -fopenmp -fpic -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -g -c Biostrings_stubs.c -o Biostrings_stubs.o In file included from /usr/lib/R/site-library/Biostrings/include/Biostrings_defines.h:18:0, from /usr/lib/R/site-library/Biostrings/include/Biostrings_interface.h:114, from /usr/lib/R/site-library/Biostrings/include/_Biostrings_stubs.c:1, from Biostrings_stubs.c:1: /usr/lib/R/site-library/IRanges/include/IRanges_defines.h:18:31: fatal error: S4Vectors_defines.h: No such file or directory #include S4Vectors_defines.h ^ compilation terminated. /usr/lib/R/etc/Makeconf:134: recipe for target 'Biostrings_stubs.o' failed Maybe this is a bug in r-bioc-biostrings, or r-bioc-iranges? The same bug affects at least r-bioc-genomicalignments, r-bioc-rtracklayer, and r-bioc-variantannotation. (all same maintainer) Full build log: https://reproducible.debian.net/rb-pkg/testing/amd64/r-bioc-shortread.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789925: fusionforge-common: fails to upgrade from 'testing' - trying to overwrite /usr/share/locale/bg/LC_MESSAGES/fusionforge.mo
Package: fusionforge-common Version: 6.0.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package fusionforge-common. Preparing to unpack .../fusionforge-common_6.0.1-1_all.deb ... Unpacking fusionforge-common (6.0.1-1) ... dpkg: error processing archive /var/cache/apt/archives/fusionforge-common_6.0.1-1_all.deb (--unpack): trying to overwrite '/usr/share/locale/bg/LC_MESSAGES/fusionforge.mo', which is also in package gforge-common 5.3.2+20141104-3+deb8u1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to unpack .../gforge-common_6.0.1-1_all.deb ... Unpacking gforge-common (6.0.1-1) over (5.3.2+20141104-3+deb8u1) ... dpkg: warning: unable to delete old directory '/var/lib/gforge': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/gforge/common/include': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/gforge/common': Directory not empty dpkg: warning: unable to delete old directory '/usr/share/gforge': Directory not empty dpkg: warning: unable to delete old directory '/etc/fusionforge/custom': Directory not empty dpkg: warning: unable to delete old directory '/etc/fusionforge/config.ini.d': Directory not empty dpkg: warning: unable to delete old directory '/etc/fusionforge': Directory not empty Errors were encountered while processing: /var/cache/apt/archives/fusionforge-common_6.0.1-1_all.deb cheers, Andreas gforge-common_6.0.1-1.log.gz Description: application/gzip
Bug#789927: libanthyinput0: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/libanthyinput.so.0.0.0'
Package: libanthyinput0 Version: 1:0.3-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package libanthyinput0:amd64. Preparing to unpack .../libanthyinput0_1%3a0.3-1_amd64.deb ... Unpacking libanthyinput0:amd64 (1:0.3-1) ... dpkg: error processing archive /var/cache/apt/archives/libanthyinput0_1%3a0.3-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libanthyinput.so.0.0.0', which is also in package libanthy0:amd64 9100h-25 Preparing to unpack .../anthy_1%3a0.3-1_amd64.deb ... Unpacking anthy (1:0.3-1) over (9100h-25) ... dpkg: warning: unable to delete old directory '/var/lib/anthy': Directory not empty Errors were encountered while processing: /var/cache/apt/archives/libanthyinput0_1%3a0.3-1_amd64.deb cheers, Andreas anthy_1:0.3-1.log.gz Description: application/gzip
Bug#777767: Partial patch for GCC 5 build issue
I created the attached patch, which fixes the basic issue.
Note that I sent the fix uptream to Amaury Darsch and he said he'd
incorporate it.
Unfortunately, that patch is not enough to make it build in Debian.
Various patches under debian/patches/ modify the gcc-4 define file and
that has to be applied to the new gcc-5 file, too. I didn't have the
energy to look into that...
--
Martin Michlmayr
Linux for HP Helion OpenStack, Hewlett-Packard
--- afnix-2.2.0~/cnf/bin/afnix-vcomp 2015-06-24 18:07:27.704828795 +
+++ afnix-2.2.0/cnf/bin/afnix-vcomp 2015-06-24 18:07:59.068829444 +
@@ -69,6 +69,7 @@
2.*) ccvers=2 ;;
3.*) ccvers=3 ;;
4.*) ccvers=4 ;;
+ 5.*) ccvers=5 ;;
esac
fi
# check for g++
@@ -79,6 +80,7 @@
2.*) ccvers=2 ;;
3.*) ccvers=3 ;;
4.*) ccvers=4 ;;
+ 5.*) ccvers=5 ;;
esac
fi
}
--- /dev/null 2015-01-14 06:03:17.0 +
+++ afnix-2.2.0/cnf/mak/afnix-gcc-5.mak 2015-06-24 18:28:08.364854471 +
@@ -0,0 +1,209 @@
+#
+# - afnix-gcc5 -
+# - afnix compiler configuration - gcc configuration -
+#
+# - This program is free software; you can redistribute it and/or modify -
+# - it provided that this copyright notice is kept intact. -
+# - -
+# - This program is distributed in the hope that it will be useful, but -
+# - without any warranty; without even the impliedwarranty of -
+# - merchantability or fitness for a particular purpose. In not event shall -
+# - the copyright holder be liable for any direct, indirect, incidental or -
+# - special damages arising in any way out of the use of this software. -
+#
+# - author (c) 1999-2015 amaury darsch -
+# - author (c) 2011-2013 pino toscano hurd platform -
+# ---
+
+#
+# - compiler and linker section -
+#
+
+CC = g++
+LD = g++
+LK = g++
+AR = ar
+RANLIB = ranlib
+STDEVFLAGS =
+STDCCFLAGS = -Wall -Werror -fno-builtin
+STACCFLAGS =
+DYNCCFLAGS = -fPIC
+PLTCCFLAGS =
+DEBUGFLAGS = -g
+OPTCCFLAGS = -O2
+PFLCCFLAGS = -g -pg
+COVCCFLAGS = -g -fprofile-arcs -ftest-coverage
+CPPCCFLAGS = -nostdinc -nostdinc++
+CXXCCFLAGS =
+STDDEFINES =
+DBGDEFINES = -DAFNIX_DEBUG
+OPTDEFINES =
+PFLDEFINES = -DAFNIX_DEBUG -DAFNIX_PROFILED
+STDINCLUDE =
+AFXCPPTYPE = GNU
+AFXCPPVERS = 5
+
+#
+# - compiler dependant libraries -
+#
+
+# adjust for linux platform
+ifeq ($(PLATNAME),linux)
+PLTCCFLAGS = -MMD -pthread
+ifeq ($(OPENMP),yes)
+PLTCCFLAGS += -fopenmp
+endif
+endif
+
+# adjust for solaris platform
+ifeq ($(PLATNAME),solaris)
+PLTDEFINES = -MMD -D_REENTRANT
+endif
+
+# adjust for freebsd platform
+ifeq ($(PLATNAME),freebsd)
+PLTDEFINES = -MMD -D_REENTRANT
+endif
+
+# adjust for gnu/freebsd platform
+ifeq ($(PLATNAME),gnukbsd)
+PLTDEFINES = -MMD -D_REENTRANT
+ifeq ($(OPENMP),yes)
+PLTCCFLAGS += -fopenmp
+endif
+endif
+
+# adjust for gnu platform
+ifeq ($(PLATNAME),gnu)
+PLTDEFINES = -MMD -D_REENTRANT
+ifeq ($(OPENMP),yes)
+PLTCCFLAGS += -fopenmp
+endif
+endif
+
+# adjust for darwin platform
+ifeq ($(PLATNAME),darwin)
+PLTDEFINES = -D_REENTRANT
+PLTSDKROOT = $(SDKDIR)
+PLTSDKARCH = -arch ppc -arch ppc64 -arch i686
+PLTCCFLAGS = -isysroot ${PLTSDKROOT} $(PLTSDKARCH)
+PLTLDFLAGS = $(PLTCCFLAGS)
+PLTLKFLAGS = $(PLTCCFLAGS)
+PLTEVFLAGS = MACOSX_DEPLOYMENT_TARGET=10.5
+endif
+
+#
+# - platform dependant linking flags -
+#
+
+# adjust for linux platform
+ifeq ($(PLATNAME),linux)
+ARFLAGS = rc
+LDFLAGS = -shared -pthread
+ifeq ($(LKMODE),soname)
+LDFLAGS += -Wl,-soname,$(SOMAJ)
+endif
+ifeq ($(OPENMP),yes)
+LDFLAGS+= -fopenmp
+endif
+AFXCPPLIBS =
+endif
+
+# adjust for solaris platform
+ifeq ($(PLATNAME),solaris)
+ARFLAGS = rc
+LDFLAGS = -shared
+ifeq ($(LKMODE),soname)
+LDFLAGS += -Wl,-h,$(SOMAJ)
+endif
+AFXCPPLIBS =
+endif
+
+# adjust for
Bug#789838: marked as done (starman: FTBFS with Plack 1.0036)
Your message dated Thu, 25 Jun 2015 19:34:38 + with message-id e1z8cv0-0001n4...@franck.debian.org and subject line Bug#789838: fixed in starman 0.4014-1 has caused the Debian Bug report #789838, regarding starman: FTBFS with Plack 1.0036 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.) -- 789838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: starman Version: 0.4011-1 Severity: serious Tags: sid stretch upstream This package FTBFS due to the new libplack-perl (cf #789669): t/chunked_req.t .. not ok 1 not ok 2 1..2 Dubious, test returned 2 (wstat 512, 0x200) Failed 2/2 subtests Test Summary Report --- t/chunked_req.t(Wstat: 512 Tests: 2 Failed: 2) Failed tests: 1-2 Non-zero exit status: 2 Files=13, Tests=119, 67 wallclock secs ( 0.09 usr 0.11 sys + 3.72 cusr 1.48 csys = 5.40 CPU) Result: FAIL Cheers, Dominic. ---End Message--- ---BeginMessage--- Source: starman Source-Version: 0.4014-1 We believe that the bug you reported is fixed in the latest version of starman, 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 789...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann gre...@debian.org (supplier of updated starman 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: SHA512 Format: 1.8 Date: Thu, 25 Jun 2015 21:21:53 +0200 Source: starman Binary: starman Architecture: source all Version: 0.4014-1 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: gregor herrmann gre...@debian.org Description: starman- high-performance preforking PSGI/Plack web server Closes: 789838 Changes: starman (0.4014-1) unstable; urgency=medium . * Team upload * Import upstream version 0.4014 Fixes FTBFS with Plack 1.0036 (Closes: #789838) Checksums-Sha1: e760947cd2678ad93723b47e6bef3acffa52c90a 2353 starman_0.4014-1.dsc 810d3731c7f67b229dc9a16a5b6b4405896dfdec 29002 starman_0.4014.orig.tar.gz e922b4edd3838e6489e58f4e0b6028f1d2b865b0 3296 starman_0.4014-1.debian.tar.xz 1e8e2c98c4d70b39e975532e2ef70723b54ca135 27862 starman_0.4014-1_all.deb Checksums-Sha256: 95aea1bd8237360d7dfb8940d80cfc13661ed30e1b3642d603d6bcccda5b16f0 2353 starman_0.4014-1.dsc a5772c18aa89ea42208c24eae4c91246de222b9b6f4a1720cd02e93d562e6be9 29002 starman_0.4014.orig.tar.gz 2f147bd4629cff73bc3e028c5666038886f6cf934c38772248e1e587e562a68a 3296 starman_0.4014-1.debian.tar.xz e2003257c20f08b16b610e13b496e35e3bebc8e52d6fc37cd97b9bae8b33f21a 27862 starman_0.4014-1_all.deb Files: d6c088cab7db39883f721aef84a598ab 2353 perl optional starman_0.4014-1.dsc 12e40b068e6f6f5a4993ef5780ab644b 29002 perl optional starman_0.4014.orig.tar.gz f4a0d47f180bce06e167577a0d52b351 3296 perl optional starman_0.4014-1.debian.tar.xz 9b45d6e87a686cc7fb4afcbb7e267be1 27862 perl optional starman_0.4014-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJVjFYhXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGcykP/0u/ZON0///aAkEvw/QmxY/g aMw7BuMuOuJZk93vYNTqnzvzvylnzuDIKK6b4uOso/F2+MrYHWdPHD6Q7E6LkBWc H7U31ck5eBeKw8VHOBqs29LoYDNEgfwC66YiNbuQwyso/m3qPjiRoAKD1sqJQmz4 oqvKUICSTms9R6uZxIJC4G1m+hLUVvsEi37Q//AqcDjFKrlswRDGM2um7N17KLC0 iDfVvIsI+rCXmouqN8SPEg9rP83B9obTYSL+XjJBOW/euN+KjfV53iyQKcAFCs7L IJtkuLNN1KE8+E4YeLJyJyGl4RUtZX2omYEsBBxUr/2VC0HSZWtQv+KyCoA5fyiQ 2yOgRA+L4WZb6OXFwBFnaJDu06JKBqaDVs1eouAk10UXyo+Jjzm5rXn5SH1LDq9P qZNZHj5k/c3jK2NFNMaEJVloUNd8kKzd036LpqHrzVKjrEky82ok9IjkQbCuAYzI m2UvmoHbuTaltn3B0dK78nUkUZLdgvIz6bwv5HXVvwtVge217N+LZUytyfNvG7OV ZXaAM4ZmFv1EAm1iYMhYjPpqunvSXaWWno0/RauO154EFvgxaws++OGqCZx54xZn pBP7vuxxjdFK3Nmm8IJWNI/Bfkj3MCsoDf5AuIUzD29oLSazf+altKD+qrim7clk d1NYrSa4/QkG8SLCkxhU =SDbU -END PGP SIGNATUREEnd Message---
Bug#777778: marked as done (aptitude: ftbfs with GCC-5)
Your message dated Thu, 25 Jun 2015 15:51:25 -0400
with message-id 20150625195125.ga8...@jirafa.cyrius.com
and subject line Re: Bug#78: aptitude: ftbfs with GCC-5
has caused the Debian Bug report #78,
regarding aptitude: ftbfs with GCC-5
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.)
--
78: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=78
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:aptitude
Version: 0.6.11-1
Severity: normal
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The
severity of this report may be raised before the stretch release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc5-20150205/aptitude_0.6.11-1_unstable_gcc5.log
The last lines of the build log are at the end of this report.
To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t experimental install g++
Common build failures are C11 as the default C mode, new warnings
resulting in build failures with -Werror turned on, or new/dropped
symbols in Debian symbols files. For other C/C++ related build failures
see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html
[...]
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... none
checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking whether NLS is requested... yes
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... (cached) none
checking for ranlib... ranlib
checking for po4a... /usr/bin/po4a
checking for xsltproc... /usr/bin/xsltproc
checking for rsvg-convert... /usr/bin/rsvg-convert
checking for fop... no
checking how to run the C++ preprocessor... g++ -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for initscr in -lncursesw... yes
checking for main in -lapt-pkg... yes
checking whether apt includes the automatic dependency removal patch
(required)... yes
checking for struct pkgCache::Version.MultiArch... yes
checking for APT::CacheFilter::PackageArchitectureMatchesSpecification... yes
checking for main in -lpthread... yes
checking for xapian-config... /usr/bin/xapian-config
checking xapian.h usability... no
checking xapian.h presence... no
configure: error: Can't find the xapian headers -- please install libxapian-dev
checking for xapian.h... no
dh_auto_configure: ../configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=${prefix}/include --mandir=${prefix}/share/man
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--libdir=${prefix}/lib/x86_64-linux-gnu
--libexecdir=${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode
--disable-dependency-tracking --htmldir=${docdir}/html
--program-transform=saptitude$aptitude-curses returned exit code 1
make[1]: *** [override_dh_auto_configure] Error 2
debian/rules:30: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [build-arch] Error 2
debian/rules:27: recipe for target 'build-arch' failed
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
---End Message---
---BeginMessage---
* Matthias Klose d...@debian.org [2015-02-12 10:29]:
checking for struct pkgCache::Version.MultiArch... yes
checking for APT::CacheFilter::PackageArchitectureMatchesSpecification... yes
checking for main in -lpthread... yes
checking
Bug#789830: unreproducible / pbuilder vs. sbuild
Hi Dom, hi Gregor, On Thu, Jun 25, 2015 at 09:52:53PM +0200, gregor herrmann wrote: I can't reproduce these 2 bugs. Apparently #789828 happens only with sbuild and not with p/cowbuiler, maybe #789830 falls into the same category ... Can't neither preproduce #789830 FTBFS for libterm-filter-perl (with sbuild). But have not done any further check so far. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789977: FTBFS: missing dependency: network-uri =2.6
Package: git-repair Version: 1.20141027 Severity: serious Tags: sid stretch Justification: fails to build from source (but built successfully in the past) User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: [21 of 21] Compiling Main ( Setup.hs, Setup.o ) Linking Setup ... ../Setup configure checking version... 1.20141027 checking git... yes checking git version... 2.1.4 Configuring git-repair-1.20141027... Setup: At least the following dependencies are missing: network-uri =2.6 Makefile:10: recipe for target 'Build/SysConfig.hs' failed Alternative build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/git-repair.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789975: FTBFS: CMake Error at doc/doxygen .. INSTALL cannot find .. doc/doxygen/deal.tag
Source: deal.ii Version: 8.1.0-4 Severity: serious Tags: sid stretch Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: -- Installing: /tmp/buildd/deal.ii-8.1.0/debian/tmp/usr/share/doc/libdeal.ii-doc/LICENSE CMake Error at doc/doxygen/cmake_install.cmake:36 (file): file INSTALL cannot find /tmp/buildd/deal.ii-8.1.0/obj-x86_64-linux-gnu/doc/doxygen/deal.tag. Call Stack (most recent call first): doc/cmake_install.cmake:52 (include) cmake_install.cmake:39 (include) Makefile:88: recipe for target 'install' failed An example build log can be seen: https://reproducible.debian.net/rb-pkg/unstable/amd64/deal.ii.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785038: marked as done (collectl-utils and collectl: error when trying to install together)
Your message dated Thu, 25 Jun 2015 13:53:08 -0600 with message-id 20150625195308.GH14261@taz.looney and subject line Close: #785038 has caused the Debian Bug report #785038, regarding collectl-utils and collectl: error when trying to install together 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.) -- 785038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785038 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: collectl,collectl-utils Version: collectl/4.0.0-1 Version: collectl-utils/4.8.1-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2015-05-11 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Extracting templates from packages: 41% Extracting templates from packages: 83% Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 10930 files and directories currently installed.) Preparing to unpack .../perl_5.20.2-4_amd64.deb ... Unpacking perl (5.20.2-4) over (5.18.2-2) ... Preparing to unpack .../libtext-charwidth-perl_0.04-7+b3_amd64.deb ... Unpacking libtext-charwidth-perl (0.04-7+b3) over (0.04-7+b2) ... Preparing to unpack .../perl-base_5.20.2-4_amd64.deb ... Unpacking perl-base (5.20.2-4) over (5.18.2-2) ... Processing triggers for man-db (2.7.0.2-5) ... Setting up perl-base (5.20.2-4) ... (Reading database ... 10375 files and directories currently installed.) Preparing to unpack .../liblocale-gettext-perl_1.05-8+b1_amd64.deb ... Unpacking liblocale-gettext-perl (1.05-8+b1) over (1.05-7+b2) ... Preparing to unpack .../libtext-iconv-perl_1.7-5+b2_amd64.deb ... Unpacking libtext-iconv-perl (1.7-5+b2) over (1.7-5+b1) ... Preparing to unpack .../perl-modules_5.20.2-4_all.deb ... Unpacking perl-modules (5.20.2-4) over (5.18.2-7) ... Selecting previously unselected package libdb5.3:amd64. Preparing to unpack .../libdb5.3_5.3.28-9_amd64.deb ... Unpacking libdb5.3:amd64 (5.3.28-9) ... Selecting previously unselected package libbsd0:amd64. Preparing to unpack .../libbsd0_0.7.0-2_amd64.deb ... Unpacking libbsd0:amd64 (0.7.0-2) ... Selecting previously unselected package libedit2:amd64. Preparing to unpack .../libedit2_3.1-20150325-1_amd64.deb ... Unpacking libedit2:amd64 (3.1-20150325-1) ... Selecting previously unselected package libpci3:amd64. Preparing to unpack .../libpci3_1%3a3.2.1-3_amd64.deb ... Unpacking libpci3:amd64 (1:3.2.1-3) ... Selecting previously unselected package libexpat1:amd64. Preparing to unpack .../libexpat1_2.1.0-6+b3_amd64.deb ... Unpacking libexpat1:amd64 (2.1.0-6+b3) ... Selecting previously unselected package libpng12-0:amd64. Preparing to unpack .../libpng12-0_1.2.50-2+b2_amd64.deb ... Unpacking libpng12-0:amd64 (1.2.50-2+b2) ... Selecting previously unselected package libfreetype6:amd64. Preparing to unpack .../libfreetype6_2.5.2-4_amd64.deb ... Unpacking libfreetype6:amd64 (2.5.2-4) ... Selecting previously unselected package ucf. Preparing to unpack .../archives/ucf_3.0030_all.deb ... Moving old data out of the way Unpacking ucf (3.0030) ... Selecting previously unselected package fonts-dejavu-core. Preparing to unpack .../fonts-dejavu-core_2.34-1_all.deb ... Unpacking fonts-dejavu-core (2.34-1) ... Selecting previously unselected package fontconfig-config. Preparing to unpack .../fontconfig-config_2.11.0-6.3_all.deb ... Unpacking fontconfig-config (2.11.0-6.3) ... Selecting previously unselected package libfontconfig1:amd64. Preparing to unpack .../libfontconfig1_2.11.0-6.3_amd64.deb ... Unpacking libfontconfig1:amd64 (2.11.0-6.3) ... Selecting previously unselected package fontconfig. Preparing to unpack .../fontconfig_2.11.0-6.3_amd64.deb ... Unpacking fontconfig (2.11.0-6.3) ... Selecting previously unselected package libxau6:amd64. Preparing to unpack .../libxau6_1%3a1.0.8-1_amd64.deb ... Unpacking libxau6:amd64 (1:1.0.8-1) ... Selecting previously unselected package x11-common. Preparing to unpack .../x11-common_1%3a7.7+8_all.deb ... Unpacking x11-common (1:7.7+8) ... Selecting previously unselected package libice6:amd64. Preparing to unpack .../libice6_2%3a1.0.9-1+b1_amd64.deb ... Unpacking libice6:amd64 (2:1.0.9-1+b1) ... Selecting previously unselected package libsm6:amd64. Preparing to unpack .../libsm6_2%3a1.2.2-1+b1_amd64.deb ... Unpacking libsm6:amd64 (2:1.2.2-1+b1) ... Selecting previously unselected package libxdmcp6:amd64. Preparing to unpack .../libxdmcp6_1%3a1.1.2-1_amd64.deb ... Unpacking
Bug#785038: Close: #785038
I missed the colon on the Closes directive in the 4.0.0-2 changelog. The 4.0.0-2 upload should resolve this issue using a proper B+R. Troy signature.asc Description: Digital signature
Processed: Re: teeworlds: ftbfs with GCC-5
Processing control commands: tags -1 unreproducible Bug #778143 [src:teeworlds] teeworlds: ftbfs with GCC-5 Added tag(s) unreproducible. -- 778143: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778143: teeworlds: ftbfs with GCC-5
Control: tags -1 unreproducible On Thu, 12 Feb 2015 10:37:23 + Matthias Klose d...@debian.org wrote: The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. I can't reproduce this. The package builds fine with gcc 5.1.1-12 (unstable). Felix -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789982: FTBFS: pybuild: AttributeError: 'module' object has no attribute '_vendor'
Package: python-fedora
Version: 0.3.36-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build:
make[1]: Entering directory '/python-fedora-0.3.36'
dh_auto_clean
I: pybuild base:170: python2.7 setup.py clean
Traceback (most recent call last):
File setup.py, line 16, in module
from setuptools import find_packages, setup
File /usr/lib/python2.7/dist-packages/setuptools/__init__.py, line 11, in
module
from setuptools.extension import Extension
File /usr/lib/python2.7/dist-packages/setuptools/extension.py, line 8, in
module
from .dist import _get_unpatched
File /usr/lib/python2.7/dist-packages/setuptools/dist.py, line 19, in
module
import pkg_resources
File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 84,
in module
packaging = pkg_resources._vendor.packaging
AttributeError: 'module' object has no attribute '_vendor'
E: pybuild pybuild:256: clean: plugin distutils failed with: exit code=1:
python2.7 setup.py clean
dh_auto_clean: pybuild --clean -i python{version} -p 2.7 --dir . returned exit
code 13
debian/rules:6: recipe for target 'override_dh_auto_clean' failed
make[1]: *** [override_dh_auto_clean] Error 13
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/python-fedora.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages python-fedora depends on:
ii python-bs4 4.3.2-2
ii python-bunch 1.0.1-1
ii python-kitchen 1.1.1-1
ii python-requests 2.7.0-3
ii python-urllib3 1.10.4-1
pn python:any none
python-fedora recommends no packages.
python-fedora suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789980: FTBFS: from pymongo import ... ImportError: cannot import name Connection
Source: python-mongoengine Version: 0.6.13-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: make[2]: Entering directory '/tmp/buildd/python-mongoengine-0.6.13/docs.debian' sphinx-build -b html -d _build/doctrees . _build/html Making output directory... Running Sphinx v1.2.3 Exception occurred: File /tmp/buildd/python-mongoengine-0.6.13/mongoengine/connection.py, line 2, in module from pymongo import Connection, ReplicaSetConnection, uri_parser ImportError: cannot import name Connection The full traceback has been saved in /tmp/sphinx-err-ty4S2z.log, if you want to report the issue to the developers. Alternative build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/python-mongoengine.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784903: [Pkg-fglrx-devel] Bug#784903: fglrx-driver: broken depends on xorg-video-abi-18
On Fri, 15 May 2015 14:50:22 +0200 Michael Tatge michael.ta...@web.de wrote: * On Tue, May 12, 2015 07:51PM +0200 Patrick Matthäi (pmatth...@debian.org) wrote: I will check in the next days if the experimental 14.12 version is compatible with it, but I do not think so. It seems it is not. Even amd say it's only compatible with Xorg up to 1.16. around the beginning of the July newer version of fglrx showed up - 15.5. i hope it solves X's ABI compatibility issue (this blocks far too many updates already...). even if it does not, it would be worth packaging any way - just to have an up to date driver installed. -- pozdrawiam serdecznie / best regards, bartek 'basz' szurgot /* http://www.baszerr.eu */ /* http://www.baszerr.eu/lib/exe/fetch.php/about_me/basz_pub_key.txt */ signature.asc Description: OpenPGP digital signature
Bug#789943: [pkg-php-pear] Bug#789943: FTBFS: Unable to parse version '=0.90 3.0' with dependency ruflin/elastica
2015-06-25 17:20 GMT+02:00 David Prévot taf...@debian.org: [...] FWIW, I do use this version for a month already without any issue so far, except maybe not noticing FTBFSes like this one any more. The range specification was updated recently (in Composer 1.0.0~alpha10) [3]. Hypen range is a bit trickier to handle as far as I’ve tried, but is not yet used in what is currently packaged in Debian AFAIK. I've uploaded it you can do future upload as a team upload. -- Mathieu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789987: FTBFS: raft/protobuf/append_entries_request.pb.go:113: undefined: proto.ErrWrongType
Source: golang-raft Version: 0.0~git20140427-4 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: code.google.com/p/gogoprotobuf/proto github.com/coreos/raft/protobuf # github.com/coreos/raft/protobuf src/github.com/coreos/raft/protobuf/append_entries_request.pb.go:113: undefined: proto.ErrWrongType src/github.com/coreos/raft/protobuf/append_entries_request.pb.go:130: undefined: proto.ErrWrongType [...] src/github.com/coreos/raft/protobuf/append_entries_responses.pb.go:148: undefined: proto.ErrWrongType src/github.com/coreos/raft/protobuf/append_entries_responses.pb.go:148: too many errors dh_auto_build: go install -v github.com/coreos/raft github.com/coreos/raft/protobuf returned exit code 2 debian/rules:6: recipe for target 'build' failed Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/golang-raft.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789989: FTBFS: The type TranslationUnit must implement [...] ITranslationUnit.getFile()
Source: eclipse-ptp
Version: 8.0.0-1
Severity: serious
Tags: sid stretch
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build:
@dot:
[mkdir] Created dir:
/tmp/buildd/eclipse-ptp-8.0.0/debian/.eclipse-build/org.eclipse.ptp.rdt.core/@dot
[javac] Compiling 191 source files to
/tmp/buildd/eclipse-ptp-8.0.0/debian/.eclipse-build/org.eclipse.ptp.rdt.core/@dot
[javac] 470. ERROR in
/eclipse-ptp-8.0.0/debian/.eclipse-build/org.eclipse.ptp.rdt.core/src/org/eclipse/ptp/internal/rdt/core/model/TranslationUnit.java
(at line 62)
[javac] public class TranslationUnit extends Parent implements
ITranslationUnit {
[javac] ^^^
[javac] The type TranslationUnit must implement the inherited abstract
method ITranslationUnit.getFile()
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/eclipse-ptp.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789988: FTBFS: The import org.eclipse.egit.ui.internal.FilteredCheckboxTree cannot be resolved
Package: eclipse-mylyn-tasks-github Version: 3.3.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, The package fails to build, probably because egit has changed: @dot: [mkdir] Created dir: /tmp/buildd/eclipse-mylyn-tasks-github-3.3.0/debian/.eclipse-build/org.eclipse.mylyn.github.ui/@dot [javac] Compiling 50 source files to /tmp/buildd/eclipse-mylyn-tasks-github-3.3.0/debian/.eclipse-build/org.eclipse.mylyn.github.ui/@dot [javac] 29. ERROR in /tmp/buildd/eclipse-mylyn-tasks-github-3.3.0/debian/.eclipse-build/org.eclipse.mylyn.github.ui/src/org/eclipse/mylyn/internal/github/ui/RepositorySelectionWizardPage.java (at line 27) [javac] import org.eclipse.egit.ui.internal.FilteredCheckboxTree; [javac]^ [javac] The import org.eclipse.egit.ui.internal.FilteredCheckboxTree cannot be resolved [javac] -- [javac] 30. ERROR in /tmp/buildd/eclipse-mylyn-tasks-github-3.3.0/debian/.eclipse-build/org.eclipse.mylyn.github.ui/src/org/eclipse/mylyn/internal/github/ui/RepositorySelectionWizardPage.java (at line 184) [javac] private FilteredCheckboxTree tree; [javac] [javac] FilteredCheckboxTree cannot be resolved to a type etc. Full build log: https://reproducible.debian.net/rb-pkg/testing/amd64/eclipse-mylyn-tasks-github.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fixed 778150 in 4.7.0-1
Processing commands for cont...@bugs.debian.org: fixed 778150 4.7.0-1 Bug #778150 [src:tulip] tulip: ftbfs with GCC-5 The source 'tulip' and version '4.7.0-1' do not appear to match any binary packages Marked as fixed in versions tulip/4.7.0-1. thanks Stopping processing here. Please contact me if you need assistance. -- 778150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778150 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777974: marked as done (libspf2: ftbfs with GCC-5)
Your message dated Thu, 25 Jun 2015 21:20:39 +
with message-id e1z8ezb-0004fp...@franck.debian.org
and subject line Bug#777974: fixed in libspf2 1.2.10-6
has caused the Debian Bug report #777974,
regarding libspf2: ftbfs with GCC-5
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.)
--
777974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:libspf2
Version: 1.2.10-5
Severity: normal
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The
severity of this report may be raised before the stretch release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc5-20150205/libspf2_1.2.10-5_unstable_gcc5.log
The last lines of the build log are at the end of this report.
To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t experimental install g++
Common build failures are C11 as the default C mode, new warnings
resulting in build failures with -Werror turned on, or new/dropped
symbols in Debian symbols files. For other C/C++ related build failures
see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html
[...]
/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
-I../.. -I../../src/include -I../../src -D_FORTIFY_SOURCE=2 -g -O2
-fstack-protector-strong -Wformat -Werror=format-security -Wall -MT
spf_compile.lo -MD -MP -MF .deps/spf_compile.Tpo -c -o spf_compile.lo
spf_compile.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include
-I../../src -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wall -MT spf_compile.lo -MD -MP -MF
.deps/spf_compile.Tpo -c spf_compile.c -fPIC -DPIC -o .libs/spf_compile.o
In file included from ../../src/include/spf.h:31:0,
from ../../src/include/spf_response.h:166,
from ../../src/include/spf_record.h:25,
from ../../src/include/spf_internal.h:83,
from spf_compile.c:17:
spf_compile.c: In function 'SPF_c_parse_macro':
../../src/include/spf_log.h:66:86: error: expected expression before ')' token
#define SPF_debugf(format, ... ) SPF_debugx( __FILE__, __LINE__, format,
__VA_ARGS__ )
^
spf_compile.c:580:5: note: in expansion of macro 'SPF_debugf'
SPF_debugf(Adding literal %%);
^
../../src/include/spf_log.h:66:86: error: expected expression before ')' token
#define SPF_debugf(format, ... ) SPF_debugx( __FILE__, __LINE__, format,
__VA_ARGS__ )
^
spf_compile.c:589:5: note: in expansion of macro 'SPF_debugf'
SPF_debugf(Adding literal space);
^
../../src/include/spf_log.h:66:86: error: expected expression before ')' token
#define SPF_debugf(format, ... ) SPF_debugx( __FILE__, __LINE__, format,
__VA_ARGS__ )
^
spf_compile.c:598:5: note: in expansion of macro 'SPF_debugf'
SPF_debugf(Adding escaped space);
^
spf_compile.c:607:16: warning: format '%d' expects argument of type 'int', but
argument 5 has type 'size_t {aka long unsigned int}' [-Wformat=]
SPF_debugf(Adding illegal %%-follower '%c' at %d,
^
../../src/include/spf_log.h:66:66: note: in definition of macro 'SPF_debugf'
#define SPF_debugf(format, ... ) SPF_debugx( __FILE__, __LINE__, format,
__VA_ARGS__ )
^
make[5]: *** [spf_compile.lo] Error 1
Makefile:518: recipe for target 'spf_compile.lo' failed
make[5]: Leaving directory '/«PKGBUILDDIR»/src/libspf2'
make[4]: *** [all-recursive] Error 1
Makefile:537: recipe for target 'all-recursive' failed
make[4]: Leaving directory '/«PKGBUILDDIR»/src/libspf2'
make[3]: *** [all-recursive] Error 1
Makefile:340: recipe for target 'all-recursive' failed
make[3]: Leaving directory '/«PKGBUILDDIR»/src'
make[2]: *** [all-recursive]
Bug#789772: marked as done (fusionforge-mta-exim4: modifies conffiles (policy 10.7.3): /etc/exim4/exim4.conf.template /etc/exim4/conf.d/main/01_exim4-config_listmacrosdefs)
Your message dated Thu, 25 Jun 2015 15:59:06 +0200 with message-id 20150625135906.ga28...@mail.beuc.net and subject line Re: fusionforge-mta-exim4: modifies conffiles (policy 10.7.3): /etc/exim4/exim4.conf.template /etc/exim4/conf.d/main/01_exim4-config_listmacrosdefs has caused the Debian Bug report #789772, regarding fusionforge-mta-exim4: modifies conffiles (policy 10.7.3): /etc/exim4/exim4.conf.template /etc/exim4/conf.d/main/01_exim4-config_listmacrosdefs 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.) -- 789772: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789772 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fusionforge-mta-exim4 Version: 6.0.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. And these are not even conffiles shipped by your package. This is forbidden by the policy, see https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: [...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time). Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: [...] must not ask unnecessary questions (particularly during upgrades) [...] If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also https://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): 0m52.1s ERROR: FAIL: debsums reports modifications inside the chroot: /etc/exim4/exim4.conf.template /etc/exim4/conf.d/main/01_exim4-config_listmacrosdefs cheers, Andreas fusionforge-mta-exim4_6.0.1-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Hi, during a test with piuparts I noticed your package modifies conffiles. That's indeed the point of fusionforge-mta-exim4, which is meant to configure exim4 for fusionforge integration. And these are not even conffiles shipped by your package. This is forbidden by the policy, see https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files Your excerpts mentions generalities about [generated] conffiles; they do not explain why this would be forbidden by policy. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). That's what we do: changing the conffile while preserving user customizations. And removing that change on uninstall. It looks like you're reporting a bug through automated means, without actually using the package, so please only send bugs that are relevant (as checking this is quite time-consuming, plus we didn't volunteer to beta-test piuparts) and preferrably with a patch. Alternatively leave the FusionForge packages alone. Closing. Sylvain---End Message---
Bug#789940: marked as forwarded (FTBFS: gtk_widget_override_background_color is deprecated and -Werror)
Your message dated Thu, 25 Jun 2015 10:53:27 -0400 with message-id 558c15e7.3040...@bregmasoft.ca has caused the report #789940, regarding FTBFS: gtk_widget_override_background_color is deprecated and -Werror to be marked as having been forwarded to the upstream software author(s) n...@bugs.launchpad.net (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.) -- 789940: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- The package fails to build: gesture.c: In function ‘create_window’: gesture.c:219:3: error: ‘gtk_widget_override_background_color’ is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkwidget.h:1157) [-Werror=deprecated-declarations] gtk_widget_override_background_color (app-da, GTK_STATE_NORMAL, white); ^ cc1: all warnings being treated as errors An alternative build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/libgrip.html affects libgrip assignee bregma status inprogress importance medium signature.asc Description: OpenPGP digital signature ---End Message---
Bug#789946: FTBFS: Failed to resolve artifact. Missing: org.jruby.extras:jffi:jar:debian
owner 789946 ! thanks I'll take care of this. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Processed: tagging 777871, tagging 788012, tagging 751539
Processing commands for cont...@bugs.debian.org: tags 777871 + fixed pending Bug #777871 [src:geis] geis: ftbfs with GCC-5 Added tag(s) fixed and pending. tags 788012 + fixed pending Bug #788012 [src:geis] geis: please make the build reproducible Added tag(s) pending and fixed. tags 751539 + fixed pending Bug #751539 [src:geis] geis: FTBFS with clang instead of gcc Added tag(s) fixed and pending. thanks Stopping processing here. Please contact me if you need assistance. -- 751539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751539 777871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777871 788012: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789946: FTBFS: Failed to resolve artifact. Missing: org.jruby.extras:jffi:jar:debian
Package: jenkins-instance-identity Version: 1.4-1 Severity: serious Tags: sid stretch Justification: fails to build from source (but built successfully in the past) User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build due to some unresolvable maven dependencies while maven is in offline mode: [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.jruby.extras:jffi:jar:debian [..] Path to dependency: 1) org.jenkins-ci.modules:instance-identity:jenkins-module:1.4 2) org.jenkins-ci.main:jenkins-core:jar:1.565.3 3) org.jruby.extras:jffi:jar:debian 2) org.jruby.ext.posix:jnr-posix:jar:debian [..] Path to dependency: 1) org.jenkins-ci.modules:instance-identity:jenkins-module:1.4 2) org.jenkins-ci.main:jenkins-core:jar:1.565.3 3) org.jruby.ext.posix:jnr-posix:jar:debian I remember something about there being a different named jruby dependency which provides these, but I'm /totally failing/ to find it anywhere. Alternative build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/jenkins-instance-identity.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#777831: deborphan: ftbfs with GCC-5
Processing control commands: tags -1 + patch Bug #777831 [src:deborphan] deborphan: ftbfs with GCC-5 Added tag(s) patch. -- 777831: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777831: deborphan: ftbfs with GCC-5
Control: tags -1 + patch * Matthias Klose d...@debian.org, 2015-02-12, 10:30: src/set.c:64: undefined reference to `xstrdup' This is due to the change in semantics of the inline keyword[0]. The attached patch seems to do the trick. [0] https://gcc.gnu.org/gcc-5/porting_to.html, search for Different semantics for inline functions. -- Jakub Wilk diff -Nru deborphan-1.7.28.8/include/deborphan.h deborphan-1.7.28.8/include/deborphan.h --- deborphan-1.7.28.8/include/deborphan.h 2012-06-30 20:47:50.0 +0200 +++ deborphan-1.7.28.8/include/deborphan.h 2015-06-25 17:39:18.0 +0200 @@ -172,8 +172,8 @@ int string_to_priority(const char *priority); const char *priority_to_string(int priority); char *sstrsep(char **str, int c); -inline void strstripchr(char *s, int c); -inline unsigned int strhash(const char *line); +extern inline void strstripchr(char *s, int c); +extern inline unsigned int strhash(const char *line); /* keep.c */ dep *readkeep(const char *kfile); diff -Nru deborphan-1.7.28.8/include/xalloc.h deborphan-1.7.28.8/include/xalloc.h --- deborphan-1.7.28.8/include/xalloc.h 2012-06-30 20:47:50.0 +0200 +++ deborphan-1.7.28.8/include/xalloc.h 2015-06-25 17:38:29.0 +0200 @@ -7,7 +7,7 @@ Distributed under the terms of the Artistic License. */ -inline void *xcalloc(size_t nmemb, size_t size); -inline void *xmalloc(size_t size); -inline void *xrealloc(void *ptr, size_t size); -inline char *xstrdup(const char *s); +extern inline void *xcalloc(size_t nmemb, size_t size); +extern inline void *xmalloc(size_t size); +extern inline void *xrealloc(void *ptr, size_t size); +extern inline char *xstrdup(const char *s);
Bug#789773: marked as done (fusionforge-shell: modifies conffiles (policy 10.7.3): /etc/pam.d/sshd)
Your message dated Thu, 25 Jun 2015 16:02:10 +0200 with message-id 20150625140210.gb28...@mail.beuc.net and subject line Re: fusionforge-shell: modifies conffiles (policy 10.7.3): /etc/pam.d/sshd has caused the Debian Bug report #789773, regarding fusionforge-shell: modifies conffiles (policy 10.7.3): /etc/pam.d/sshd 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.) -- 789773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789773 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fusionforge-shell Version: 6.0.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. And this is not even a conffile shipped by your package. This is forbidden by the policy, see https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: [...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time). Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: [...] must not ask unnecessary questions (particularly during upgrades) [...] If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also https://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): 2m49.1s ERROR: FAIL: debsums reports modifications inside the chroot: /etc/pam.d/sshd cheers, Andreas fusionforge-shell_6.0.1-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- See #789772---End Message---
Bug#789772: Re: fusionforge-mta-exim4: modifies conffiles (policy 10.7.3): /etc/exim4/exim4.conf.template /etc/exim4/conf.d/main/01_exim4-config_listmacrosdefs
On 2015-06-25 15:59, b...@debian.org wrote: during a test with piuparts I noticed your package modifies conffiles. Please note the distiction between configuration files and conffiles in the policy. That's indeed the point of fusionforge-mta-exim4, which is meant to configure exim4 for fusionforge integration. Having to modify conffiles for this task indicates lack of an abstraction layer to allow such automated customization. And these are not even conffiles shipped by your package. This is forbidden by the policy, see https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files Your excerpts mentions generalities about [generated] conffiles; they do not explain why this would be forbidden by policy. You are right, the bug template was not well suited for your case of policy violation (which is a rather uncommon case). Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). That's what we do: changing the conffile while preserving user customizations. And that's forbidden on conffiles (see the definition in the policy): [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time). What happens on the next update of exim that ships a modified version of that conffile? dpkg will prompt about a modified conffile even if the admin did not modify anything. And removing that change on uninstall. It looks like you're reporting a bug through automated means, without No, bug filing is an entirely manual process. actually using the package, That's right, but the piuparts logfile is usually informative enough. so please only send bugs that are relevant This one is. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: forcemerge 781567 779286 Bug #781567 [libgps22] libgps22: upgrade failure Bug #779286 [libgps22] libgps22: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/libgpsd.so.22.0.0 Bug #779286 [libgps22] libgps22: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/libgpsd.so.22.0.0 Merged 779286 781567 thanks Stopping processing here. Please contact me if you need assistance. -- 779286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779286 781567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789944: FTBFS: [..]code.google.com/p/go.net/html expects import golang.org/x/net/html
Source: golang-blackfriday Version: 1.2-1 Severity: serious Justification: fails to build from source Dear Maintainer, The package fails to build in unstable, but not in testing: dh_auto_build -O--buildsystem=golang go install -v github.com/russross/blackfriday src/github.com/russross/blackfriday/sanitize.go:6:2: code in directory /golang-blackfriday-1.2/obj-x86_64-linux-gnu/src/code.google.com/p/go.net/html expects import golang.org/x/net/html dh_auto_build: go install -v github.com/russross/blackfriday returned exit code 1 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/golang-blackfriday.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789943: FTBFS: Unable to parse version '=0.90 3.0' with dependency ruflin/elastica
Package: php-monolog
Version: 1.14.0-1
Severity: serious
Tags: sid stretch
Justification: fails to build from source (but built successfully in the past)
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build in sid, but seems fine in testing (for now):
dh_phpcomposer
exception 'InvalidArgumentException' with message 'Unable to parse version
'=0.90 3.0' with dependency ruflin/elastica (=0.90 3.0)' in
/usr/share/php/pkgtools/phpcomposer/source.php:192
Stack trace:
#0 /usr/share/php/pkgtools/phpcomposer/command.php(73):
Pkgtools\Phpcomposer\Source-getDependencies()
#1 [internal function]: Pkgtools\Phpcomposer\Command-runSubstvars()
#2 /usr/share/php/pkgtools/base/command.php(180): call_user_func_array(Array,
Array)
#3 /usr/share/php/pkgtools/base/command.php(168):
Pkgtools\Base\Command-parseArgs(Array)
#4 /usr/bin/pkgtools(32): Pkgtools\Base\Command-parseArgs()
#5 {main}
Fuller log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/php-monolog.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 5 errors): Re: raising severity for GCC 5 issues, please fix these now (see https://wiki.debian.org/GCC5)
Processing commands for cont...@bugs.debian.org: severity 777909 important Bug #777909 [src:iceweasel] iceweasel: ftbfs with GCC-5 Severity set to 'important' from 'serious' AFAICS, GCC 5 is not the default yet, so bumping the severity seems Unknown command or malformed arguments to command. premature. Moreover the iceweasel version that is in now both testing Unknown command or malformed arguments to command. and unstable is likely not affected (and it's not like I didn't ask for Unknown command or malformed arguments to command. a respin for the version in experimental at the time) Unknown command or malformed arguments to command. Mike Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. -- 777909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777909: raising severity for GCC 5 issues, please fix these now (see https://wiki.debian.org/GCC5)
severity 777909 important AFAICS, GCC 5 is not the default yet, so bumping the severity seems premature. Moreover the iceweasel version that is in now both testing and unstable is likely not affected (and it's not like I didn't ask for a respin for the version in experimental at the time) Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#789943: FTBFS: Unable to parse version '=0.90 3.0' with dependency ruflin/elastica
Processing control commands: reassign -1 pkg-php-tools,php-monolog Bug #789943 [php-monolog] FTBFS: Unable to parse version '=0.90 3.0' with dependency ruflin/elastica Bug reassigned from package 'php-monolog' to 'pkg-php-tools,php-monolog'. No longer marked as found in versions php-monolog/1.14.0-1. Ignoring request to alter fixed versions of bug #789943 to the same values previously set retitle -1 dh_phpcomposer should handle ranges separated by a space (causes FTBFS in packages using them) Bug #789943 [pkg-php-tools,php-monolog] FTBFS: Unable to parse version '=0.90 3.0' with dependency ruflin/elastica Changed Bug title to 'dh_phpcomposer should handle ranges separated by a space (causes FTBFS in packages using them)' from 'FTBFS: Unable to parse version '=0.90 3.0' with dependency ruflin/elastica' found -1 pkg-php-tools/1.29 Bug #789943 [pkg-php-tools,php-monolog] dh_phpcomposer should handle ranges separated by a space (causes FTBFS in packages using them) Marked as found in versions pkg-php-tools/1.29. found -1 pkg-php-tools/1.14.0-1 Bug #789943 [pkg-php-tools,php-monolog] dh_phpcomposer should handle ranges separated by a space (causes FTBFS in packages using them) The source pkg-php-tools and version 1.14.0-1 do not appear to match any binary packages Marked as found in versions pkg-php-tools/1.14.0-1. tags -1 = pending Bug #789943 [pkg-php-tools,php-monolog] dh_phpcomposer should handle ranges separated by a space (causes FTBFS in packages using them) Added tag(s) pending; removed tag(s) stretch and sid. -- 789943: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788321: elinks: FTBFS on arm64
+++ Moritz Muehlenhoff [2015-06-25 08:30 +0200]:
What I don't understand is why elinks built before on arm64, e.g. in
jessie?
The jessie version (pre6-5) already had a build-dep on autotools-dev
(which makes the current config.{sub,guess} available, and then its own
manual machinery for updating them.
That version built (and still builds) fine in jessie and unstable.
pre6-6 was the first one to break:
https://buildd.debian.org/status/logs.php?pkg=elinksarch=arm64
and it dies with: machine aarch64' not recognized
That version was the firs to use a simple 'dh' rules file (according
to https://tracker.debian.org/news/681779) . But
presumably forgot to explicitly say --with autotools-dev? so the
shipped config.{sub,guess} was used, not the uptodate ones in
autotools-dev.
adding --with dh-autoreconf didn't fix that because this is a
non-automake/non-libtool package.
So it does all make sense.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778042: marked as done (open-vm-tools: ftbfs with GCC-5)
Your message dated Thu, 25 Jun 2015 15:58:21 +0200 with message-id 558c08fd.9020...@conova.com and subject line long fixed has caused the Debian Bug report #778042, regarding open-vm-tools: ftbfs with GCC-5 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.) -- 778042: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:open-vm-tools Version: 2:9.4.6-1770165-7 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/open-vm-tools_9.4.6-1770165-7_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] /bin/bash ../../../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\open-vm-tools\ -DPACKAGE_TARNAME=\open-vm-tools\ -DPACKAGE_VERSION=\9.4.6\ -DPACKAGE_STRING=\open-vm-tools\ 9.4.6\ -DPACKAGE_BUGREPORT=\open-vm-tools-de...@lists.sourceforge.net\ -DPACKAGE_URL=\\ -DPACKAGE=\open-vm-tools\ -DVERSION=\9.4.6\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\.libs/\ -DHAVE_X11_SM_SMLIB_H=1 -DHAVE_X11_ICE_ICELIB_H=1 -DHAVE_X11_EXTENSIONS_XCOMPOSITE_H=1 -DHAVE_ECVT=1 -DHAVE_FCVT=1 -DDNET_IS_DUMBNET=1 -DHAVE_CRYPT_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_WCHAR_H=1 -DHAVE_SYS_IO_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_SYSINFO_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_USER_H=1 -DHAVE_SYS_VFS_H=1 -DHAVE_UNWIND_H=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -DHAVE_STRUCT_STAT_ST_RDEV=1 -DTIME_WITH_S YS_TIME=1 -I. -DVMTOOLS_USE_GLIB -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -fvisibility=hidden -DGCC_EXPLICIT_EXPORT -I/«PKGBUILDDIR»/lib/include -I/«PKGBUILDDIR»/lib/include -D_FORTIFY_SOURCE=2 -DUSING_AUTOCONF=1 -DOPEN_VM_TOOLS -I/usr/include -DUSE_ICU -DHAVE_ICU_38 -DVMX86_TOOLS -DHAVE_GLIB_REGEX -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -fPIC -Wno-deprecated-declarations -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -Wno-pointer-sign -Wno-unused-value -fno-strict-aliasing -Wno-unknown-pragmas -Wno-uninitialized -Wno-unused-but-set-variable -c -o libvmbackup_la-nullProvider.lo `test -f 'nullProvider.c' || echo './'`nullProvider.c libtool: compile: gcc -DPACKAGE_NAME=\open-vm-tools\ -DPACKAGE_TARNAME=\open-vm-tools\ -DPACKAGE_VERSION=\9.4.6\ -DPACKAGE_STRING=\open-vm-tools 9.4.6\ -DPACKAGE_BUGREPORT=\open-vm-tools-de...@lists.sourceforge.net\ -DPACKAGE_URL=\\ -DPACKAGE=\open-vm-tools\ -DVERSION=\9.4.6\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\.libs/\ -DHAVE_X11_SM_SMLIB_H=1 -DHAVE_X11_ICE_ICELIB_H=1 -DHAVE_X11_EXTENSIONS_XCOMPOSITE_H=1 -DHAVE_ECVT=1 -DHAVE_FCVT=1 -DDNET_IS_DUMBNET=1 -DHAVE_CRYPT_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_WCHAR_H=1 -DHAVE_SYS_IO_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_SYSINFO_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_USER_H=1 -DHAVE_SYS_VFS_H=1 -DHAVE_UNWIND_H=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -DHAVE_STRUCT_STAT_ST_RDEV=1 -DTIME_WITH_SYS_TIME=1 -I. -DVMTOOLS_USE_GLIB - I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -fvisibility=hidden -DGCC_EXPLICIT_EXPORT -I/«PKGBUILDDIR»/lib/include
Processed: Re: FTBFS: Failed to resolve artifact. Missing: org.jruby.extras:jffi:jar:debian
Processing commands for cont...@bugs.debian.org: owner 789946 ! Bug #789946 [jenkins-instance-identity] FTBFS: Failed to resolve artifact. Missing: org.jruby.extras:jffi:jar:debian Owner recorded as Miguel Landaeta nomad...@debian.org. thanks Stopping processing here. Please contact me if you need assistance. -- 789946: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789946 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789943: FTBFS: Unable to parse version '=0.90 3.0' with dependency ruflin/elastica
Control: reassign -1 pkg-php-tools,php-monolog Control: retitle -1 dh_phpcomposer should handle ranges separated by a space (causes FTBFS in packages using them) Control: found -1 pkg-php-tools/1.29 Control: found -1 pkg-php-tools/1.14.0-1 Control: tags -1 = pending On Thu, Jun 25, 2015 at 01:57:40PM +, Chris West (Faux) wrote: Package: php-monolog Version: 1.14.0-1 Severity: serious Tags: sid stretch Justification: fails to build from source (but built successfully in the past) User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs The package fails to build in sid, but seems fine in testing Well, the version is testing is not the same 1.13.1-2 (nor is the version in stable (1.11.0-2), so the tags might have been an abuse. exception 'InvalidArgumentException' with message 'Unable to parse version '=0.90 3.0' with dependency ruflin/elastica (=0.90 3.0)' in /usr/share/php/pkgtools/phpcomposer/source.php:192 I noticed it one day after the upload (thanks to the reproducible effort showing up in the DDPO), and documented it four days ago [1]. 1: http://anonscm.debian.org/cgit/pkg-php/php-monolog.git/commit/?id=6768cb5d271b6b72e1843115a2182bd5fe2da8e6 The root issue has been fixed in pkg-php-tools a month ago [2], Mathieu, are you willing to upload it soon, or do you mind me doing a team upload of pkg-php-tools as of its current status? FWIW, I do use this version for a month already without any issue so far, except maybe not noticing FTBFSes like this one any more. The range specification was updated recently (in Composer 1.0.0~alpha10) [3]. Hypen range is a bit trickier to handle as far as I’ve tried, but is not yet used in what is currently packaged in Debian AFAIK. 2: http://anonscm.debian.org/cgit/pkg-php/pkg-php-tools.git/commit/?id=0077d22e352cdfe0351f53b396ef83f30c63e08d 3: https://getcomposer.org/doc/01-basic-usage.md#package-versions Regards David signature.asc Description: Digital signature
Bug#778045: [Pkg-openldap-devel] Processed: raising severity for GCC 5 issues, please fix these now (see https://wiki.debian.org/GCC5)
On Thu, Jun 25, 2015 at 11:27:47AM +, Debian Bug Tracking System wrote: severity 778045 serious Bug #778045 [src:openldap] openldap: ftbfs with GCC-5 Severity set to 'serious' from 'important' Sorry for not getting to this sooner. I'll prepare the fix this weekend, new upstream if it's available by then, otherwise just the patch. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789541: abtransfers: Crash after successful money transfer
Hello Paul, I'm the upstream author of AB-Transfers. Thank you for your detailed explanations. A little background for the history functionality of abtransfers: I'm using the import and export functions from aqbanking to store all relevant data at a 'ctx-file' (aqbanking main file format). I'm using this to store all needed information, regardless of if it is an account, transfer, standing order (Dauerauftrag) or whatever else aqbanking supports. Another benefit of this is that I can use the same parser for the data, regardless of if it was send by the bank or read from a file. [...] Looking at the “bad” `history.ctx` it’s size is 41 MB (42626560 Bytes) and I think it contains strange characters due to umlauts I put into the “Verwendungszweck” with the middle click as it’s not allowed (for some reason) entering it with the keyboard. During development I had some issues with the German umlauts. Some banks supported it some don't. And also the aqbanking backend sometimes replaced some umlauts with spaces or not readable characters (but a crash did not happened). Therefore I decided to be on the save side and disabled the input of umlauts at abtransfers (didn't blocked/checked copypaste input, my fault). Also a size of 41 MB is pretty big, either you using the program for a long time with a lot of transfers or something else is wrong. A normal transfer should occupy around 1.2 KB at the history (34000 transfers needed to reach 41MB). Also looking at `history.ctx` after the crash yesterday, the format seems to be incorrect. The following is missing at the end of the file compared to the file written today. int cycle=0 int executionDay=0 char type=transaction char subType=none char status=none char charge=Nobody char sequenceType=once } #transfer } #transferList } #accountInfo } #accountInfoList A few lines above this missing entries (or directly at the end) of your bad history.ctx file should be a line starting with char purpose=. Could you remember which purpose (with umlauts) do you used? Which is the character that could not be written at the bad history.txt and maybe caused the crash? If I know this I could try to reproduce it here and maybe could fix it. Kind regards Patrick Wacker -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789897: marked as done (failure on upgrade, file conflict with zenmap)
Your message dated Thu, 25 Jun 2015 16:22:32 + with message-id e1z89v6-0001o9...@franck.debian.org and subject line Bug#789897: fixed in nmap 6.47-6 has caused the Debian Bug report #789897, regarding failure on upgrade, file conflict with zenmap 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.) -- 789897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789897 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: zenmap Version: 6.47-5 Severity: serious Todays upgrade of zenmap failed: # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: ndiff zenmap 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 898 kB of archives. After this operation, 66.6 kB disk space will be freed. Do you want to continue? [Y/n] Get:1 http://ftp.de.debian.org/debian/ sid/main ndiff all 6.47-5 [257 kB] Get:2 http://ftp.de.debian.org/debian/ sid/main zenmap all 6.47-5 [642 kB] Fetched 898 kB in 0s (906 kB/s) Retrieving bug reports... Done Parsing Found/Fixed information... Done Reading changelogs... Done (Reading database ... 307698 files and directories currently installed.) Preparing to unpack .../archives/ndiff_6.47-5_all.deb ... Unpacking ndiff (6.47-5) over (6.47-3) ... dpkg: error processing archive /var/cache/apt/archives/ndiff_6.47-5_all.deb (--unpack): trying to overwrite '/usr/lib/python2.7/dist-packages/ndiff.py', which is also in package zenmap 6.47-3 Preparing to unpack .../archives/zenmap_6.47-5_all.deb ... Unpacking zenmap (6.47-5) over (6.47-3) ... Processing triggers for man-db (2.7.0.2-5) ... Processing triggers for bamfdaemon (0.2.118-1+b1) ... Rebuilding /usr/share/applications/bamf.index... Processing triggers for gnome-menus (3.13.3-6) ... Processing triggers for mime-support (3.58) ... Processing triggers for desktop-file-utils (0.22-1) ... Errors were encountered while processing: /var/cache/apt/archives/ndiff_6.47-5_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Looks like zenmap is missing a proper versioned Breaks/Replaces: See section 7.6.1: https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces Cheers, Michael -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages zenmap depends on: ii nmap6.47-5 ii python 2.7.9-1 ii python-gobject 3.16.2-1 ii python-gtk2 2.24.0-4 Versions of packages zenmap recommends: ii gksu 2.0.2-9 zenmap suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: nmap Source-Version: 6.47-6 We believe that the bug you reported is fixed in the latest version of nmap, 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 789...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen ben...@debian.org (supplier of updated nmap 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: SHA256 Format: 1.8 Date: Thu, 25 Jun 2015 18:03:40 +0200 Source: nmap Binary: nmap zenmap ndiff Architecture: source all amd64 Version: 6.47-6 Distribution: unstable Urgency: medium Maintainer: Hilko Bengen ben...@debian.org Changed-By: Hilko Bengen ben...@debian.org Description: ndiff - The Network Mapper - result compare utility nmap - The Network Mapper zenmap - The Network Mapper Front End Closes: 789897 Changes: nmap (6.47-6) unstable; urgency=medium . * ndiff: Added versioned Conflicts (Closes: #789897) Checksums-Sha1: 1cca5a03e1f8c50c64faee87a36f630b2ee42f4e 2038 nmap_6.47-6.dsc 656ca2567efc59c41d248a0471b6f60ab0089483 28956 nmap_6.47-6.debian.tar.xz e1ebcb64fcde6d8062ee924838159df04b1d21b8 256624 ndiff_6.47-6_all.deb 59ed20164deb21c999bf0a3cf91962d77093c815 3972328
Bug#777838: ekiga: ftbfs with GCC-5
blocked 777838 by 778074 severity 777838 important thanks * Matthias Klose d...@debian.org [2015-02-12 10:31]: In file included from /usr/include/ptlib/contain.h:42:0, from /usr/include/ptlib.h:56, from ../lib/gui/xwindow.h:44, from ../lib/gui/xvwindow.h:54, from ../lib/gui/xvwindow.cpp:39: /usr/include/ptlib/critsec.h:46:33: fatal error: bits/atomicity.h: No such file or directory The problem is in ptlib (#778074). I tested with a modified /usr/include/ptlib/critsec.h and ekiga built fine. I suggest this bug be closed when ptlib is fixed. -- Martin Michlmayr Linux for HP Helion OpenStack, Hewlett-Packard -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Patch for GCC 5 build issue
Processing commands for cont...@bugs.debian.org: tags 80 + patch Bug #80 [src:asmon] asmon: ftbfs with GCC-5 Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 80: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=80 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: block
Processing commands for cont...@bugs.debian.org: block 777838 by 778074 Bug #777838 [src:ekiga] ekiga: ftbfs with GCC-5 777838 was not blocked by any bugs. 777838 was not blocking any bugs. Added blocking bug(s) of 777838: 778074 -- Stopping processing here. Please contact me if you need assistance. -- 777838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789893: marked as done (libvolk1.0-bin and libvolk-bin: error when trying to install together)
Your message dated Thu, 25 Jun 2015 17:19:03 + with message-id e1z8ann-0002ym...@franck.debian.org and subject line Bug#789893: fixed in volk 1.0-3 has caused the Debian Bug report #789893, regarding libvolk1.0-bin and libvolk-bin: error when trying to install together 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.) -- 789893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789893 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libvolk-bin,libvolk1.0-bin Version: libvolk-bin/3.7.5-5 Version: libvolk1.0-bin/1.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2015-06-25 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package gcc-5-base:amd64. (Reading database ... 10902 files and directories currently installed.) Preparing to unpack .../gcc-5-base_5.1.1-12_amd64.deb ... Unpacking gcc-5-base:amd64 (5.1.1-12) ... Setting up gcc-5-base:amd64 (5.1.1-12) ... (Reading database ... 10909 files and directories currently installed.) Preparing to unpack .../libstdc++6_5.1.1-12_amd64.deb ... Unpacking libstdc++6:amd64 (5.1.1-12) over (4.8.2-19) ... Setting up libstdc++6:amd64 (5.1.1-12) ... Processing triggers for libc-bin (2.19-18) ... Selecting previously unselected package libdb5.3:amd64. (Reading database ... 10923 files and directories currently installed.) Preparing to unpack .../libdb5.3_5.3.28-9_amd64.deb ... Unpacking libdb5.3:amd64 (5.3.28-9) ... Selecting previously unselected package libpython2.7-minimal:amd64. Preparing to unpack .../libpython2.7-minimal_2.7.10-2_amd64.deb ... Unpacking libpython2.7-minimal:amd64 (2.7.10-2) ... Selecting previously unselected package python2.7-minimal. Preparing to unpack .../python2.7-minimal_2.7.10-2_amd64.deb ... Unpacking python2.7-minimal (2.7.10-2) ... Selecting previously unselected package python-minimal. Preparing to unpack .../python-minimal_2.7.9-1_amd64.deb ... Unpacking python-minimal (2.7.9-1) ... Selecting previously unselected package mime-support. Preparing to unpack .../mime-support_3.58_all.deb ... Unpacking mime-support (3.58) ... Selecting previously unselected package libexpat1:amd64. Preparing to unpack .../libexpat1_2.1.0-6+b3_amd64.deb ... Unpacking libexpat1:amd64 (2.1.0-6+b3) ... Selecting previously unselected package libffi6:amd64. Preparing to unpack .../libffi6_3.1-2+b2_amd64.deb ... Unpacking libffi6:amd64 (3.1-2+b2) ... Selecting previously unselected package libpython2.7-stdlib:amd64. Preparing to unpack .../libpython2.7-stdlib_2.7.10-2_amd64.deb ... Unpacking libpython2.7-stdlib:amd64 (2.7.10-2) ... Selecting previously unselected package python2.7. Preparing to unpack .../python2.7_2.7.10-2_amd64.deb ... Unpacking python2.7 (2.7.10-2) ... Selecting previously unselected package libpython-stdlib:amd64. Preparing to unpack .../libpython-stdlib_2.7.9-1_amd64.deb ... Unpacking libpython-stdlib:amd64 (2.7.9-1) ... Processing triggers for man-db (2.7.0.2-5) ... Setting up libpython2.7-minimal:amd64 (2.7.10-2) ... Setting up python2.7-minimal (2.7.10-2) ... Setting up python-minimal (2.7.9-1) ... Selecting previously unselected package python. (Reading database ... 11717 files and directories currently installed.) Preparing to unpack .../python_2.7.9-1_amd64.deb ... Unpacking python (2.7.9-1) ... Selecting previously unselected package libboost-system1.55.0:amd64. Preparing to unpack .../libboost-system1.55.0_1.55.0+dfsg-3_amd64.deb ... Unpacking libboost-system1.55.0:amd64 (1.55.0+dfsg-3) ... Selecting previously unselected package libboost-filesystem1.55.0:amd64. Preparing to unpack .../libboost-filesystem1.55.0_1.55.0+dfsg-3_amd64.deb ... Unpacking libboost-filesystem1.55.0:amd64 (1.55.0+dfsg-3) ... Selecting previously unselected package libboost-program-options1.55.0:amd64. Preparing to unpack .../libboost-program-options1.55.0_1.55.0+dfsg-3_amd64.deb ... Unpacking libboost-program-options1.55.0:amd64 (1.55.0+dfsg-3) ... Selecting previously unselected package libboost-test1.55.0:amd64. Preparing to unpack .../libboost-test1.55.0_1.55.0+dfsg-3_amd64.deb ... Unpacking libboost-test1.55.0:amd64 (1.55.0+dfsg-3) ... Selecting previously unselected package liborc-0.4-0:amd64. Preparing to unpack .../liborc-0.4-0_1%3a0.4.24-1_amd64.deb ... Unpacking liborc-0.4-0:amd64 (1:0.4.24-1) ... Selecting previously unselected package libvolk0.0.0:amd64. Preparing to unpack
Processed: Patch
Processing commands for cont...@bugs.debian.org: tags 90 + patch Bug #90 [src:avifile] avifile: ftbfs with GCC-5 Added tag(s) patch. -- Stopping processing here. Please contact me if you need assistance. -- 90: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=90 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777810: GCC 5 build issue
* Tom Lee m...@tomlee.co [2015-05-03 02:34]: Not sure if you're actively attempting test rebuilds every so often, but feel free to try for yourself when 0.5.2-1 hits unstable. I can confirm that the package in unstable builds fine with GCC 5. Tom, as the maintainer, I suggest you close this bug. -- Martin Michlmayr Linux for HP Helion OpenStack, Hewlett-Packard -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Patch for GCC 5 build issue
Processing commands for cont...@bugs.debian.org: tags 778074 + patch Bug #778074 [src:ptlib] ptlib: ftbfs with GCC-5 Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 778074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778074 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778001: marked as done (memtest86+: ftbfs with GCC-5)
Your message dated Thu, 25 Jun 2015 17:33:45 +
with message-id e1z8b21-0005hi...@franck.debian.org
and subject line Bug#778001: fixed in memtest86+ 5.01-3
has caused the Debian Bug report #778001,
regarding memtest86+: ftbfs with GCC-5
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.)
--
778001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:memtest86+
Version: 5.01-2
Severity: normal
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The
severity of this report may be raised before the stretch release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc5-20150205/memtest86+_5.01-2_unstable_gcc5.log
The last lines of the build log are at the end of this report.
To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t experimental install g++
Common build failures are C11 as the default C mode, new warnings
resulting in build failures with -Werror turned on, or new/dropped
symbols in Debian symbols files. For other C/C++ related build failures
see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html
[...]
smp.c: In function 'smp_find_cpus':
smp.c:513:11: warning: passing argument 1 of 'memset' discards 'volatile'
qualifier from pointer target type [-Wdiscarded-array-qualifiers]
memset(AP, 0, sizeof AP);
^
smp.c:170:1: note: expected 'void *' but argument is of type 'volatile
ap_info_t (*)[32] {aka volatile struct anonymous (*)[32]}'
memset (void *dst,
^
gcc -Wall -march=i486 -m32 -O0 -fomit-frame-pointer -fno-builtin -ffreestanding
-fPIC -fno-stack-protector-c -o vmem.o vmem.c
gcc -c -Wall -march=i486 -m32 -O3 -fomit-frame-pointer -fno-builtin
-ffreestanding random.c
gcc -Wall -march=i486 -m32 -O0 -fomit-frame-pointer -fno-builtin -ffreestanding
-fPIC -fno-stack-protector-c -o multiboot.o multiboot.c
ld -z max-page-size=0x1000 --warn-constructors --warn-common -static -T
memtest_shared.lds \
-o memtest_shared head.o reloc.o main.o test.o init.o lib.o patn.o
screen_buffer.o config.o cpuid.o linuxbios.o pci.o memsize.o spd.o error.o
dmi.o controller.o smp.o vmem.o random.o multiboot.o \
ld -z max-page-size=0x1000 -shared -Bsymbolic -T memtest_shared.lds -o
memtest_shared head.o reloc.o main.o test.o init.o lib.o patn.o screen_buffer.o
config.o cpuid.o linuxbios.o pci.o memsize.o spd.o error.o dmi.o controller.o
smp.o vmem.o random.o multiboot.o
lib.o: In function `outsb':
lib.c:(.text+0x78): multiple definition of `outsb'
init.o:init.c:(.text+0x12d): first defined here
lib.o: In function `outsw':
lib.c:(.text+0xb6): multiple definition of `outsw'
init.o:init.c:(.text+0x16b): first defined here
lib.o: In function `outsl':
lib.c:(.text+0xf5): multiple definition of `outsl'
init.o:init.c:(.text+0x1aa): first defined here
pci.o: In function `outsb':
pci.c:(.text+0xf0): multiple definition of `outsb'
init.o:init.c:(.text+0x12d): first defined here
pci.o: In function `outsw':
pci.c:(.text+0x12e): multiple definition of `outsw'
init.o:init.c:(.text+0x16b): first defined here
pci.o: In function `outsl':
pci.c:(.text+0x16d): multiple definition of `outsl'
init.o:init.c:(.text+0x1aa): first defined here
spd.o: In function `outsb':
spd.c:(.text+0x51): multiple definition of `outsb'
init.o:init.c:(.text+0x12d): first defined here
spd.o: In function `outsw':
spd.c:(.text+0x8f): multiple definition of `outsw'
init.o:init.c:(.text+0x16b): first defined here
spd.o: In function `outsl':
spd.c:(.text+0xce): multiple definition of `outsl'
init.o:init.c:(.text+0x1aa): first defined here
main.o: In function `test_start':
main.c:(.text+0x193c): undefined reference to `reboot'
lib.o: In function `check_input':
lib.c:(.text+0x17be): undefined reference to `reboot'
make[1]: *** [memtest_shared] Error 1
Makefile:34: recipe for target 'memtest_shared' failed
make[1]: Leaving directory '/build/memtest86+-WjIgKJ/memtest86+-5.01'
make: *** [build-stamp] Error 2
debian/rules:9: recipe for target 'build-stamp' failed
dpkg-buildpackage: error: debian/rules
Bug#778074: Patch for GCC 5 build issue
tags 778074 + patch thanks Here's a patch for the GCC 5 build issue. Sorry, I'm not sure how best to send patches for packages using quilt. BTW, it seems this issue is no longer present upstream: svn ls svn://svn.code.sf.net/p/opalvoip/code/ptlib/trunk/include/ptlib/ | grep crit It seems this is properly handled in configure now. -- Martin Michlmayr Linux for HP Helion OpenStack, Hewlett-Packard diff -urN a/debian/patches/gcc-5_support b/debian/patches/gcc-5_support --- a/debian/patches/gcc-5_support 1970-01-01 00:00:00.0 + +++ b/debian/patches/gcc-5_support 2015-06-25 17:20:02.0 + @@ -0,0 +1,13 @@ +Index: ptlib-2.10.10~dfsg/include/ptlib/critsec.h +=== +--- ptlib-2.10.10~dfsg.orig/include/ptlib/critsec.h ptlib-2.10.10~dfsg/include/ptlib/critsec.h +@@ -40,7 +40,7 @@ + #if P_HAS_ATOMIC_INT + + #if defined(__GNUC__) +-# if __GNUC__ = 4 __GNUC_MINOR__ = 2 ++# if (__GNUC__ = 4 __GNUC_MINOR__ = 2) || __GNUC__ = 5 + # include ext/atomicity.h + # else + # include bits/atomicity.h diff -urN a/debian/patches/series b/debian/patches/series --- a/debian/patches/series 2014-10-08 02:18:13.0 + +++ b/debian/patches/series 2015-06-25 17:19:36.0 + @@ -1,3 +1,4 @@ hurd-fix bison-fix ppc64el-arm64-mips64.diff +gcc-5_support
