Processed: Re: log4cxx: library transition may be needed when GCC 5 is the default
Processing control commands: severity -1 important Bug #791192 [src:log4cxx] log4cxx: library transition may be needed when GCC 5 is the default Severity set to 'important' from 'serious' -- 791192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791192 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#791192: log4cxx: library transition may be needed when GCC 5 is the default
Package: src:log4cxx Followup-For: Bug #791192 Control: severity -1 important Just uploaded a new version to experimental, setting the soname to v5. (This will need to go through NEW) -- tobi -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-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) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777787: marked as done (autofs: ftbfs with GCC-5)
Your message dated Fri, 10 Jul 2015 17:55:11 +1000 with message-id 2116941.HqOgck8B9y@debstor and subject line Done: autofs: ftbfs with GCC-5 has caused the Debian Bug report #87, regarding autofs: 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.) -- 87: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=87 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:autofs Version: 5.0.8-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/autofs_5.0.8-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 [...] ^ In file included from ../include/automount.h:29:0, from lookup.c:25: ../include/master.h:117:28: warning: inline function 'master_get_logopt' declared but never defined extern inline unsigned int master_get_logopt(void); ^ gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -D_REENTRANT -D_FILE_OFFSET_BITS=64 -D_REENTRANT -D_FILE_OFFSET_BITS=64 -rdynamic -fPIE -D_GNU_SOURCE -I../include -DAUTOFS_LIB_DIR=\/usr/lib/x86_64-linux-gnu/autofs\ -DAUTOFS_MAP_DIR=\/etc\ -DAUTOFS_CONF_DIR=\/etc/default\ -DAUTOFS_FIFO_DIR=\/var/run\ -DAUTOFS_FLAG_DIR=\/var/run\ -DVERSION_STRING=\5.0.8\ -I/usr/include/libxml2 -c state.c In file included from state.c:17:0: ../include/automount.h:215:13: warning: inline function 'dump_core' declared but never defined inline void dump_core(void); ^ In file included from ../include/automount.h:29:0, from state.c:17: ../include/master.h:117:28: warning: inline function 'master_get_logopt' declared but never defined extern inline unsigned int master_get_logopt(void); ^ gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -D_REENTRANT -D_FILE_OFFSET_BITS=64 -D_REENTRANT -D_FILE_OFFSET_BITS=64 -rdynamic -fPIE -D_GNU_SOURCE -I../include -DAUTOFS_LIB_DIR=\/usr/lib/x86_64-linux-gnu/autofs\ -DAUTOFS_MAP_DIR=\/etc\ -DAUTOFS_CONF_DIR=\/etc/default\ -DAUTOFS_FIFO_DIR=\/var/run\ -DAUTOFS_FLAG_DIR=\/var/run\ -DVERSION_STRING=\5.0.8\ -I/usr/include/libxml2 -c flag.c In file included from flag.c:31:0: ../include/automount.h:215:13: warning: inline function 'dump_core' declared but never defined inline void dump_core(void); ^ In file included from ../include/automount.h:29:0, from flag.c:31: ../include/master.h:117:28: warning: inline function 'master_get_logopt' declared but never defined extern inline unsigned int master_get_logopt(void); ^ gcc -Wl,-z,relro -rdynamic -pie -o automount automount.o indirect.o direct.o spawn.o module.o mount.o lookup.o state.o flag.o ../lib/autofs.a -lpthread -lnsl -ldl -lpthread -lxml2 automount.o: In function `do_master_cleanup_unlock': /«PKGBUILDDIR»/daemon/automount.c:1154: undefined reference to `dump_core' automount.o: In function `return_start_status': /«PKGBUILDDIR»/daemon/automount.c:1389: undefined reference to `dump_core' /«PKGBUILDDIR»/daemon/automount.c:1393: undefined reference to `dump_core' automount.o: In function `do_read_master': /«PKGBUILDDIR»/daemon/automount.c:1256: undefined reference to `dump_core' /«PKGBUILDDIR»/daemon/automount.c:1242: undefined reference to `dump_core' automount.o:/«PKGBUILDDIR»/daemon/automount.c:1262: more undefined references to `dump_core' follow collect2: error: ld returned 1 exit status make[3]: *** [automount] Error 1
Bug#791984: dicomscope: must depend on libdicomscope-jni
Am 10.07.2015 um 09:09 schrieb Andreas Tille: Hi Markus, thanks for the bug report including patch. It seems you missed some upload in between that has dealt with the upgrade issue - so the Breaks is included (I'm not sure about the Replaces since the library does not actually replace dicomscope). I commited the following patch to SVN to enable you a review before I'll upload. Please let me know what you think about it. Hi Andreas, sorry, I missed your last upload. I think the patch looks good but I would readd the Replaces to libdicomscope-jni. I usually follow the advice to add both, Breaks and Replaces, while doing a package transition. https://wiki.debian.org/PackageTransition dicomscope would be case #8 Replaces just means that package B, libdicomscope-jni, replaces some files in package A but not the whole package. More info here: https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces Regards, Markus signature.asc Description: OpenPGP digital signature
Processed: Re: [cuneiform] Buffer overflow triggered by user supplied image
Processing control commands: tags -1 + security Bug #781354 [cuneiform] [cuneiform] Buffer overflow triggered by user supplied image Added tag(s) security. severity -1 grave Bug #781354 [cuneiform] [cuneiform] Buffer overflow triggered by user supplied image Severity set to 'grave' from 'normal' -- 781354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781354 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#791984: dicomscope: must depend on libdicomscope-jni
Hi Markus,
thanks for the bug report including patch. It seems you missed some
upload in between that has dealt with the upgrade issue - so the
Breaks is included (I'm not sure about the Replaces since the
library does not actually replace dicomscope).
I commited the following patch to SVN to enable you a review before
I'll upload. Please let me know what you think about it.
Kind regards
Andreas.
--
http://fam-tille.de
$ svn diff
Index: changelog
===
--- changelog (Revision 19581)
+++ changelog (Arbeitskopie)
@@ -1,3 +1,12 @@
+dicomscope (3.6.0-14) UNRELEASED; urgency=medium
+
+ * dicomscope: Depend on libdicomscope-jni (thanks for the patch to
+Markus Koschany a...@gambaru.de)
+Closes: #791984
+ * remove superfluous ${shlibs:Depends} substvar.
+
+ -- Andreas Tille ti...@debian.org Fri, 10 Jul 2015 08:57:31 +0200
+
dicomscope (3.6.0-13) unstable; urgency=medium
* Enable smooth upgrades by adding Breaks: dicomscope (= 3.6.0-11)
Index: control
===
--- control (Revision 19581)
+++ control (Arbeitskopie)
@@ -19,11 +19,11 @@
Architecture: all
Multi-Arch: foreign
Depends: ${java:Depends},
- ${shlibs:Depends},
${misc:Depends},
tk8.6 | tk8.5 | tk8.4 | wish,
default-jre,
- jarwrapper
+ jarwrapper,
+ libdicomscope-jni
Description: OFFIS DICOM Viewer
DICOMscope is a free DICOM viewer which can display uncompressed, monochrome
DICOM images from all modalities and which supports monitor calibration
@@ -44,11 +44,9 @@
Package: libdicomscope-jni
Architecture: any
Multi-Arch: same
-Depends: ${java:Depends},
- ${shlibs:Depends},
- ${misc:Depends},
- default-jre
-Breaks: dicomscope (= 3.6.0-11)
+Depends: ${shlibs:Depends},
+ ${misc:Depends}
+Breaks: dicomscope ( 3.6.0-12)
Description: OFFIS DICOM Viewer (JNI files)
DICOMscope is a free DICOM viewer which can display uncompressed, monochrome
DICOM images from all modalities and which supports monitor calibration
Processed: Re: Bug#790819: FTBFS: cannot stat 'debian/tmp//usr/lib/ocaml/netcamlbox': No such file or directory
Processing commands for cont...@bugs.debian.org: severity 790819 normal Bug #790819 [ocamlnet] FTBFS: cannot stat 'debian/tmp//usr/lib/ocaml/netcamlbox': No such file or directory Severity set to 'normal' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 790819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790819 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#792002: lvm2-monitor service causes long delay at boot (encrypted root/swap)
On 07/10/2015 01:48 AM, Josh Triplett wrote: Package: lvm2 Version: 2.02.122-1 Severity: grave File: /lib/systemd/system/lvm2-monitor.service On a laptop with encrypted root and swap, I now get a minutes-long delay at boot time, due to lvm2-monitor. Here's the complete set of messages at boot (transcribed from a photo of the screen): Loading, please wait... /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. Volume group data not found Cannot process volume group data Unable to find LVM volume data/root /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. Volume group data not found Cannot process volume group data Unable to find LVM volume data/swap Please unlock disk sda2_crypt: /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. Reading all physical volumes. This may take a while... Found volume group data using metadata type lvm2 /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. 2 logical volume(s) in volume group data now active cryptsetup: sda2_crypt set up successfully fsck from util-linux 2.26.2 /dev/mapper/data-root: clean, [...] [ ] A start job is running for Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling (59s / no limit) That last line matches the description in lvm2-monitor.service. (The preceeding lvm2 errors may or may not be related. The recurring two lines of lvmetad errors are new, as is the long delay on lvm2-monitor.service; the errors before unlocking the disk about not finding data/root and data/swap occurred with previous versions of lvm2.) If initrd is generated, the existing lvm.conf needs to be modified so the configuration is suitable for initrd environment (where I suppose lvmetad daemon is not running). So the script generating initrd needs to modify lvm.conf so that use_lvmetad=0 is used. In case lvmetad daemon is not running in initrd, which is, I suppose, exactly the case here - running lvmetad (the LVM metadata caching daemon) is not quite useful in initrd anyway as lvmetad would need to be started again after switching to root fs. So that's probably the first problem here. If those falling back to internal scanning messages appear even after switching to root fs, please check if lvm2-lvmetad.socket is enabled (so it can instantiate lvm2-lvmetad.service on first socket access): systemctl status lvm2-lvmetad.socket If it's disabled then the distro needs to make sure it's always enabled so whenever use_lvmetad=1 is used, the lvm2-lvmetad.service can be instantiated automatically. Let's check these things first before debugging the lvm2-monitor.service delay... -- Peter -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790819: FTBFS: cannot stat 'debian/tmp//usr/lib/ocaml/netcamlbox': No such file or directory
severity 790819 normal thanks Le 02/07/2015 13:24, Martin Michlmayr a écrit : dh_install --fail-missing -X.so.owner -Xmod_netcgi_apache.so cp: cannot stat 'debian/tmp//usr/lib/ocaml/netcamlbox': No such file or directory dh_install: cp --reflink=auto -a debian/tmp//usr/lib/ocaml/netcamlbox debian/libocamlnet-ocaml-dev//usr/lib/ocaml/ returned exit code 1 make[1]: *** [override_dh_install] Error 2 This happened in the past on kfreebsd, which lacked named semaphores. What architecture is this? This was on arm64, but I get the same on amd64. It built successfully on all architectures 66 days ago [1]. [1] https://buildd.debian.org/status/package.php?p=ocamlnetsuite=unstable Can you reproduce the failure on a porterbox? I just tried on asachi (arm64 porterbox), the package builds successfully. Would the complete build log help? Yes. Might it be the way the chroot was setup? Maybe. Are all virtual filesystems (in particular /dev/shm) mounted in your chroot? Cheers, -- Stéphane -- 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 783202 is normal
Processing commands for cont...@bugs.debian.org: severity 783202 normal Bug #783202 [autopkgtest] [adt-buildvm-ubuntu-cloud] timeout nearly after display Net device info Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 783202: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783202 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: fixed 781640 in 1.3.0-1
Processing commands for cont...@bugs.debian.org:
fixed 781640 1.3.0-1
Bug #781640 {Done: Daniele Tricoli er...@mornie.org} [pyjwt] Asymmetric keys
and x509 certificates should not be used as HMAC keys
There is no source info for the package 'pyjwt' at version '1.3.0-1' with
architecture ''
Unable to make a source version for version '1.3.0-1'
Marked as fixed in versions 1.3.0-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
781640: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781640
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#777812: marked as done (cclive: ftbfs with GCC-5)
Your message dated Fri, 10 Jul 2015 09:34:55 + with message-id e1zduhr-0005fk...@franck.debian.org and subject line Bug#777812: fixed in cclive 0.7.16-2.1 has caused the Debian Bug report #777812, regarding cclive: 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.) -- 777812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777812 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:cclive Version: 0.7.16-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/cclive_0.7.16-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 [...] | /* end confdefs.h. */ | #include ac_nonexistent.h configure:16632: checking whether ln -s works configure:16636: result: yes configure:16646: checking for a2x configure:16664: found /usr/bin/a2x configure:16677: result: /usr/bin/a2x configure:16755: checking for pkg-config configure:16773: found /usr/bin/pkg-config configure:16785: result: /usr/bin/pkg-config configure:16810: checking pkg-config is at least version 0.9.0 configure:16813: result: yes configure:16823: checking for libquvi configure:16830: $PKG_CONFIG --exists --print-errors libquvi = 0.4.0 configure:16833: $? = 0 configure:16847: $PKG_CONFIG --exists --print-errors libquvi = 0.4.0 configure:16850: $? = 0 configure:17068: result: yes configure:17076: checking for libcurl configure:17083: $PKG_CONFIG --exists --print-errors libcurl = 7.18.0 configure:17086: $? = 0 configure:17100: $PKG_CONFIG --exists --print-errors libcurl = 7.18.0 configure:17103: $? = 0 configure:17161: result: yes configure:17167: checking for libpcre configure:17174: $PKG_CONFIG --exists --print-errors libpcre = 8.02 configure:17177: $? = 0 configure:17191: $PKG_CONFIG --exists --print-errors libpcre = 8.02 configure:17194: $? = 0 configure:17252: result: yes configure:17258: checking for libpcrecpp configure:17265: $PKG_CONFIG --exists --print-errors libpcrecpp = 8.02 configure:17268: $? = 0 configure:17282: $PKG_CONFIG --exists --print-errors libpcrecpp = 8.02 configure:17285: $? = 0 configure:17343: result: yes configure: this is boost.m4 serial 18 configure:17376: checking for Boost headers version = 1.42.0 configure:17447: g++ -c -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 conftest.cpp 5 configure:17447: $? = 0 configure:17468: result: yes configure:17487: checking for Boost's header version configure:17505: result: configure:17511: error: invalid value: boost_major_version= ## ## ## Cache variables. ## ## ## make: *** [build-arch] Error 255 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ---End Message--- ---BeginMessage--- Source: cclive Source-Version: 0.7.16-2.1 We believe that the bug you reported is fixed in the latest version of cclive, 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 777...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose d...@debian.org (supplier of updated cclive 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:
Bug#791513: marked as done (golang-ed25519-dev: FTBFS during tests: go.crypto/curve25519 expects import golang.org/x/crypto/curve25519)
Your message dated Fri, 10 Jul 2015 09:50:19 + with message-id e1zduwl-0004fq...@franck.debian.org and subject line Bug#791513: fixed in golang-ed25519-dev 0~20140907.d2b94fd-2 has caused the Debian Bug report #791513, regarding golang-ed25519-dev: FTBFS during tests: go.crypto/curve25519 expects import golang.org/x/crypto/curve25519 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.) -- 791513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791513 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: golang-ed25519-dev Version: 0~20140907.d2b94fd-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: dh_auto_build -O--buildsystem=golang go install -v github.com/agl/ed25519 github.com/agl/ed25519/edwards25519 github.com/agl/ed25519/extra25519 github.com/agl/ed25519/edwards25519 github.com/agl/ed25519 github.com/agl/ed25519/extra25519 dh_auto_test -O--buildsystem=golang go test -v github.com/agl/ed25519 github.com/agl/ed25519/edwards25519 github.com/agl/ed25519/extra25519 # github.com/agl/ed25519/extra25519 src/github.com/agl/ed25519/extra25519/extra25519_test.go:12:2: code in directory /tmp/buildd/golang-ed25519-dev-0~20140907.d2b94fd/obj-x86_64-linux-gnu/src/code.google.com/p/go.crypto/curve25519 expects import golang.org/x/crypto/curve25519 FAILgithub.com/agl/ed25519/extra25519 [setup failed] Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/golang-ed25519-dev.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) ---End Message--- ---BeginMessage--- Source: golang-ed25519-dev Source-Version: 0~20140907.d2b94fd-2 We believe that the bug you reported is fixed in the latest version of golang-ed25519-dev, 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 791...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Bobbio lu...@debian.org (supplier of updated golang-ed25519-dev 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, 09 Jul 2015 23:41:36 +0200 Source: golang-ed25519-dev Binary: golang-ed25519-dev Architecture: source all Version: 0~20140907.d2b94fd-2 Distribution: unstable Urgency: medium Maintainer: Anonymity Tools Debian Maintainers pkg-anonymity-to...@lists.alioth.debian.org Changed-By: Jérémy Bobbio lu...@debian.org Description: golang-ed25519-dev - Go implementation of the Ed25519 signature algorithm Closes: 791513 Changes: golang-ed25519-dev (0~20140907.d2b94fd-2) unstable; urgency=medium . * Add a patch to fix go.crypto import path. (Closes: #791513) * Bump Standards-Version, no changes required. Checksums-Sha1: bee1c89f99f694d1813b6f9b8bb6667d66475355 2167 golang-ed25519-dev_0~20140907.d2b94fd-2.dsc e8ed11164a6f1ac407641b221e2a9c7d92fa9bcf 2529 golang-ed25519-dev_0~20140907.d2b94fd-2.debian.tar.gz 1c73231099267fad6a8fa98c8a314612cea628b3 98766 golang-ed25519-dev_0~20140907.d2b94fd-2_all.deb Checksums-Sha256: 74ab357ab60690b54cbc053c8588ea7c1fbb912cdc3a01be56bb0cab77548668 2167 golang-ed25519-dev_0~20140907.d2b94fd-2.dsc cfb325eb7f59787ab1825d662ed7912fc559668b33618a536a0a40b2a604720a 2529 golang-ed25519-dev_0~20140907.d2b94fd-2.debian.tar.gz 5acb6157c6be1a3b580b6baffb2e36658d80f9f30a7e0aaaf1743c59658dd7d0 98766 golang-ed25519-dev_0~20140907.d2b94fd-2_all.deb Files: f858635ec8626eaac78654c36aea35c7 2167 devel extra golang-ed25519-dev_0~20140907.d2b94fd-2.dsc aeafba3aeb90617703a4aceb762ac669 2529 devel extra golang-ed25519-dev_0~20140907.d2b94fd-2.debian.tar.gz 0c87a233d2727dd0a934024dc69f23a6 98766 devel extra golang-ed25519-dev_0~20140907.d2b94fd-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux)
Bug#778188: marked as done (xorp: ftbfs with GCC-5)
Your message dated Fri, 10 Jul 2015 09:51:06 + with message-id e1zduxw-0004yz...@franck.debian.org and subject line Bug#778188: fixed in xorp 1.8.5-4.1 has caused the Debian Bug report #778188, regarding xorp: 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.) -- 778188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:xorp Version: 1.8.5-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/xorp_1.8.5-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 [...] g++ -o obj/x86_64-unknown-linux-gnu/libxipc/permits.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. libxipc/permits.cc g++ -o obj/x86_64-unknown-linux-gnu/libxipc/sockutil.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. libxipc/sockutil.cc g++ -o obj/x86_64-unknown-linux-gnu/libxipc/xrl.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. libxipc/xrl.cc g++ -o obj/x86_64-unknown-linux-gnu/libxipc/xrl_args.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. libxipc/xrl_args.cc g++ -o obj/x86_64-unknown-linux-gnu/libxipc/xrl_atom.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. libxipc/xrl_atom.cc g++ -o obj/x86_64-unknown-linux-gnu/libxipc/xrl_atom_encoding.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. libxipc/xrl_atom_encoding.cc g++ -o obj/x86_64-unknown-linux-gnu/libxipc/xrl_atom_list.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. libxipc/xrl_atom_list.cc g++ -o obj/x86_64-unknown-linux-gnu/libxipc/xrl_cmd_map.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. libxipc/xrl_cmd_map.cc g++ -o obj/x86_64-unknown-linux-gnu/libxipc/xrl_dispatcher.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5 -Iobj/x86_64-unknown-linux-gnu -I. -I. libxipc/xrl_dispatcher.cc g++ -o obj/x86_64-unknown-linux-gnu/libxipc/xrl_error.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual
Bug#791984: marked as done (dicomscope: must depend on libdicomscope-jni)
Your message dated Fri, 10 Jul 2015 10:05:14 +
with message-id e1zdvbd-0002sa...@franck.debian.org
and subject line Bug#791984: fixed in dicomscope 3.6.0-14
has caused the Debian Bug report #791984,
regarding dicomscope: must depend on libdicomscope-jni
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.)
--
791984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: dicomscope
Version: 3.6.0-12
Severity: grave
Tags: patch
Hi,
The new version of dicomscope is unusable because dicomscope must
depend on libdicomscope-jni. Otherwise the program won't start at all.
It is also necessary to add a Breaks and Replaces relation against
dicomscope to libdicomscope-jni to ensure that the upgrade won't fail.
Please find attached a patch, that resolves this issue.
Regards,
Markus
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 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: unable to detect
diff -Nru dicomscope-3.6.0/debian/changelog dicomscope-3.6.0/debian/changelog
--- dicomscope-3.6.0/debian/changelog 2015-07-04 23:02:05.0 +0200
+++ dicomscope-3.6.0/debian/changelog 2015-07-09 21:04:20.0 +0200
@@ -1,3 +1,11 @@
+dicomscope (3.6.0-13) unstable; urgency=medium
+
+ * Add Breaks and Replaces fields to libdicomscope-jni.
+dicomscope: Depend on libdicomscope-jni. Remove superfluous
+${shlibs:Depends} substvar.
+
+ -- Markus Koschany a...@gambaru.de Thu, 09 Jul 2015 20:42:57 +0200
+
dicomscope (3.6.0-12) unstable; urgency=medium
* Moved debian/upstream to debian/upstream/metapackages
diff -Nru dicomscope-3.6.0/debian/control dicomscope-3.6.0/debian/control
--- dicomscope-3.6.0/debian/control 2015-07-04 22:57:37.0 +0200
+++ dicomscope-3.6.0/debian/control 2015-07-09 21:04:20.0 +0200
@@ -18,11 +18,11 @@
Package: dicomscope
Architecture: all
Depends: ${java:Depends},
- ${shlibs:Depends},
${misc:Depends},
tk8.6 | tk8.5 | tk8.4 | wish,
default-jre,
- jarwrapper
+ jarwrapper,
+ libdicomscope-jni
Description: OFFIS DICOM Viewer
DICOMscope is a free DICOM viewer which can display uncompressed, monochrome
DICOM images from all modalities and which supports monitor calibration
@@ -42,10 +42,13 @@
Package: libdicomscope-jni
Architecture: any
-Depends: ${java:Depends},
- ${shlibs:Depends},
- ${misc:Depends},
- default-jre
+Depends:
+ ${shlibs:Depends},
+ ${misc:Depends}
+Replaces:
+ dicomscope ( 3.6.0-13)
+Breaks:
+ dicomscope ( 3.6.0-13)
Description: OFFIS DICOM Viewer (JNI files)
DICOMscope is a free DICOM viewer which can display uncompressed, monochrome
DICOM images from all modalities and which supports monitor calibration
---End Message---
---BeginMessage---
Source: dicomscope
Source-Version: 3.6.0-14
We believe that the bug you reported is fixed in the latest version of
dicomscope, 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 791...@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 dicomscope 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: Fri, 10 Jul 2015 08:57:31 +0200
Source: dicomscope
Binary: dicomscope libdicomscope-jni dicomscope-doc
Architecture: source all amd64
Version: 3.6.0-14
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
debian-med-packag...@lists.alioth.debian.org
Changed-By: Andreas Tille ti...@debian.org
Description:
dicomscope - OFFIS DICOM Viewer
dicomscope-doc - OFFIS DICOM Viewer - documentation
libdicomscope-jni - OFFIS DICOM Viewer (JNI files)
Closes: 791984
Changes:
dicomscope (3.6.0-14) unstable; urgency=medium
.
* dicomscope: Depend on libdicomscope-jni (thanks for the patch to
Markus Koschany a...@gambaru.de)
Closes: #791984
* dicomscope: remove superfluous
Bug#777782: fix build using GCC 5
Control: tags -1 + patch pending
attaching a patch for three issues, and uploading to delayed.
diff -Nru asterisk-13.1.0~dfsg/debian/changelog
asterisk-13.1.0~dfsg/debian/changelog
--- asterisk-13.1.0~dfsg/debian/changelog 2014-12-31 22:11:17.0
+0100
+++ asterisk-13.1.0~dfsg/debian/changelog 2015-07-10 13:21:18.0
+0200
@@ -1,3 +1,17 @@
+asterisk (1:13.1.0~dfsg-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Matthias Klose ]
+ * Build with -fgnu89-inline. Closes: #82.
+ * CVE-2015-1558: File descriptor leak when incompatible codecs are offered.
+Closes: #780601.
+
+ [ James Cowgill ]
+ * Fix OSARCH detection on all linux architectures. Closes: #780287.
+
+ -- Matthias Klose d...@debian.org Fri, 10 Jul 2015 12:56:51 +0200
+
asterisk (1:13.1.0~dfsg-1) unstable; urgency=high
[ Tzafrir Cohen ]
diff -Nru asterisk-13.1.0~dfsg/debian/patches/AST-2015-001-13.diff
asterisk-13.1.0~dfsg/debian/patches/AST-2015-001-13.diff
--- asterisk-13.1.0~dfsg/debian/patches/AST-2015-001-13.diff1970-01-01
01:00:00.0 +0100
+++ asterisk-13.1.0~dfsg/debian/patches/AST-2015-001-13.diff2015-07-10
13:19:19.0 +0200
@@ -0,0 +1,165 @@
+Index: res/res_pjsip_sdp_rtp.c
+===
+--- ./res/res_pjsip_sdp_rtp.c (revision 431302)
./res/res_pjsip_sdp_rtp.c (revision 431303)
+@@ -1242,6 +1242,7 @@
+ ast_rtp_instance_stop(session_media-rtp);
+ ast_rtp_instance_destroy(session_media-rtp);
+ }
++ session_media-rtp = NULL;
+ }
+
+ /*! \brief SDP handler for 'audio' media stream */
+Index: res/res_pjsip_t38.c
+===
+--- ./res/res_pjsip_t38.c (revision 431302)
./res/res_pjsip_t38.c (revision 431303)
+@@ -818,6 +818,7 @@
+ if (session_media-udptl) {
+ ast_udptl_destroy(session_media-udptl);
+ }
++ session_media-udptl = NULL;
+ }
+
+ /*! \brief SDP handler for 'image' media stream */
+Index: res/res_pjsip_session.c
+===
+--- ./res/res_pjsip_session.c (revision 431302)
./res/res_pjsip_session.c (revision 431303)
+@@ -186,6 +186,26 @@
+ ao2_callback_data(sdp_handlers, OBJ_KEY | OBJ_UNLINK | OBJ_NODATA,
remove_handler, (void *)stream_type, handler);
+ }
+
++/*!
++ * \brief Set an SDP stream handler for a corresponding session media.
++ *
++ * \note Always use this function to set the SDP handler for a session media.
++ *
++ * This function will properly free resources on the SDP handler currently
being
++ * used by the session media, then set the session media to use the new SDP
++ * handler.
++ */
++static void session_media_set_handler(struct ast_sip_session_media
*session_media,
++ struct ast_sip_session_sdp_handler *handler)
++{
++ ast_assert(session_media-handler != handler);
++
++ if (session_media-handler) {
++ session_media-handler-stream_destroy(session_media);
++ }
++ session_media-handler = handler;
++}
++
+ static int handle_incoming_sdp(struct ast_sip_session *session, const
pjmedia_sdp_session *sdp)
+ {
+ int i;
+@@ -235,6 +255,9 @@
+ continue;
+ }
+ AST_LIST_TRAVERSE(handler_list-list, handler, next) {
++ if (handler == session_media-handler) {
++ continue;
++ }
+ ast_debug(1, Negotiating incoming SDP media stream
'%s' using %s SDP handler\n,
+ session_media-stream_type,
+ handler-id);
+@@ -249,7 +272,7 @@
+ session_media-stream_type,
+ handler-id);
+ /* Handled by this handler. Move to the next
stream */
+- session_media-handler = handler;
++ session_media_set_handler(session_media,
handler);
+ handled = 1;
+ break;
+ }
+@@ -317,6 +340,9 @@
+ continue;
+ }
+ AST_LIST_TRAVERSE(handler_list-list, handler, next) {
++ if (handler == session_media-handler) {
++ continue;
++ }
+ ast_debug(1, Applying negotiated SDP media stream '%s'
using %s SDP handler\n,
+ session_media-stream_type,
+ handler-id);
+@@ -331,7 +357,7 @@
+ session_media-stream_type,
+ handler-id);
+ /* Handled by this handler. Move to the next
stream */
+-
Bug#791884: marked as done (libkcddb: FTBFS against libmusicbrainz5 from experimental)
Your message dated Fri, 10 Jul 2015 10:35:08 + with message-id e1zdve8-jn...@franck.debian.org and subject line Bug#791884: fixed in libkcddb 4:15.04.1-1 has caused the Debian Bug report #791884, regarding libkcddb: FTBFS against libmusicbrainz5 from experimental 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.) -- 791884: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791884 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libkcddb Version: 4.14.2-1 Severity: important Tags: patch sid stretch libkcddb fails to build against libmusicbrainz5 from experimental which split the C and C++ interface into different shared libraries. Since libkcddb uses the C++ interface it needs to link against libmusicbrainz5cc now. The attached patch fixes this issue. Cheers -- Sebastian Ramacher diff -Nru libkcddb-4.14.2/debian/changelog libkcddb-4.14.2/debian/changelog --- libkcddb-4.14.2/debian/changelog2014-10-20 17:13:14.0 +0200 +++ libkcddb-4.14.2/debian/changelog2015-07-09 11:10:05.0 +0200 @@ -1,3 +1,10 @@ +libkcddb (4:4.14.2-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Look for libmusicbrainz5cc instead of libmusicbrainz5. + + -- Sebastian Ramacher sramac...@debian.org Thu, 09 Jul 2015 11:08:06 +0200 + libkcddb (4:4.14.2-1) unstable; urgency=medium * New upstream release (4.14.2). diff -Nru libkcddb-4.14.2/debian/control libkcddb-4.14.2/debian/control --- libkcddb-4.14.2/debian/control 2014-10-20 17:13:14.0 +0200 +++ libkcddb-4.14.2/debian/control 2015-07-09 11:08:55.0 +0200 @@ -9,7 +9,7 @@ debhelper (= 9), kde-sc-dev-latest (= 4:4.12), kdelibs5-dev (= 4:4.11), - libmusicbrainz5-dev, + libmusicbrainz5-dev (= 5.1.0+git20150707), pkg-kde-tools (= 0.12) Standards-Version: 3.9.5 XS-Testsuite: autopkgtest diff -Nru libkcddb-4.14.2/debian/patches/libmusicbrainz5cc.patch libkcddb-4.14.2/debian/patches/libmusicbrainz5cc.patch --- libkcddb-4.14.2/debian/patches/libmusicbrainz5cc.patch 1970-01-01 01:00:00.0 +0100 +++ libkcddb-4.14.2/debian/patches/libmusicbrainz5cc.patch 2015-07-09 11:09:22.0 +0200 @@ -0,0 +1,15 @@ +Description: Look for libmusicbrainz5cc instead of libmusicbrainz5. +Author: Sebastian Ramacher sramac...@debian.org +Last-Update: 2015-07-09 + +--- libkcddb-4.14.2.orig/cmake/FindMusicBrainz5.cmake libkcddb-4.14.2/cmake/FindMusicBrainz5.cmake +@@ -16,7 +16,7 @@ endif(MUSICBRAINZ5_INCLUDE_DIR AND MUSIC + + FIND_PATH(MUSICBRAINZ5_INCLUDE_DIR musicbrainz5/Disc.h) + +-FIND_LIBRARY( MUSICBRAINZ5_LIBRARIES NAMES musicbrainz5) ++FIND_LIBRARY( MUSICBRAINZ5_LIBRARIES NAMES musicbrainz5cc) + + include(FindPackageHandleStandardArgs) + find_package_handle_standard_args( MusicBrainz5 DEFAULT_MSG diff -Nru libkcddb-4.14.2/debian/patches/series libkcddb-4.14.2/debian/patches/series --- libkcddb-4.14.2/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ libkcddb-4.14.2/debian/patches/series 2015-07-09 11:09:03.0 +0200 @@ -0,0 +1 @@ +libmusicbrainz5cc.patch signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: libkcddb Source-Version: 4:15.04.1-1 We believe that the bug you reported is fixed in the latest version of libkcddb, 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 791...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Maximiliano Curia m...@debian.org (supplier of updated libkcddb 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: Fri, 10 Jul 2015 11:57:03 +0200 Source: libkcddb Binary: libkcddb4 libkcddb-dev kde-config-cddb libkcddb-dbg Architecture: source amd64 Version: 4:15.04.1-1 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers debian-qt-...@lists.debian.org Changed-By: Maximiliano Curia m...@debian.org Description: kde-config-cddb - CDDB retrieval configuration libkcddb-dbg - debugging symbols for libkcddb libkcddb-dev - CDDB library for KDE Platform (development) libkcddb4 -
Bug#792021: libmaven3-core-java: not installable in sid - libeclipse-aether-java (= 1.0) does not exist
Package: libmaven3-core-java
Version: 3.3.3-1
Severity: grave
Hi,
maven and libmaven3-core-java can no longer be installed in sid because
the dependency on libeclipse-aether-java cannot be satisfied.
$ sudo aptitude install maven
The following NEW packages will be installed:
libguice-java{a} libmaven3-core-java{ab} libsisu-inject-java{a}
libsisu-plexus-java{a}
The following packages will be upgraded:
maven
1 packages upgraded, 4 newly installed, 0 to remove and 1 not upgraded.
Need to get 2,541 kB of archives. After unpacking 1,734 kB will be used.
The following packages have unmet dependencies:
libmaven3-core-java : Depends: libeclipse-aether-java (= 1.0) but it is not
going to be installed.
$ rmadison -sunstable libeclipse-aether-java
libeclipse-aether-java | 0.9.0.M2-1| unstable | all
Thanks,
James
signature.asc
Description: This is a digitally signed message part
Bug#782108: marked as done (libkf5people-data: fails to upgrade from 'sid' - trying to overwrite /usr/share/locale/*/LC_MESSAGES/libkpeople.mo)
Your message dated Fri, 10 Jul 2015 10:51:44 + with message-id e1zdvuc-0001sy...@franck.debian.org and subject line Bug#782108: fixed in kpeople 5.12.0-1 has caused the Debian Bug report #782108, regarding libkf5people-data: fails to upgrade from 'sid' - trying to overwrite /usr/share/locale/*/LC_MESSAGES/libkpeople.mo 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.) -- 782108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libkf5people-data Version: 5.8.0-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 libkf5people-data. Preparing to unpack .../libkf5people-data_5.8.0-1_all.deb ... Unpacking libkf5people-data (5.8.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libkf5people-data_5.8.0-1_all.deb (--unpack): trying to overwrite '/usr/share/locale/bs/LC_MESSAGES/libkpeople.mo', which is also in package libkpeople3 0.2.2-2 cheers, Andreas libkpeople3=0.2.2-2_libkf5people-data=5.8.0-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: kpeople Source-Version: 5.12.0-1 We believe that the bug you reported is fixed in the latest version of kpeople, 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 782...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Maximiliano Curia m...@debian.org (supplier of updated kpeople 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, 09 Jul 2015 12:43:43 +0200 Source: kpeople Binary: libkf5people-dev libkf5people-data libkf5peoplebackend5 libkf5peoplewidgets5 qml-module-org-kde-people libkf5people5 libkf5people-dbg Architecture: source all amd64 Version: 5.12.0-1 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers debian-qt-...@lists.debian.org Changed-By: Maximiliano Curia m...@debian.org Description: libkf5people-data - data files for kpeople libkf5people-dbg - debug symbols for kpeople libkf5people-dev - development files for kpeople libkf5people5 - framework providing unified access to contacts aggregated by pers libkf5peoplebackend5 - framework providing unified access to contacts aggregated by pers libkf5peoplewidgets5 - framework providing unified access to contacts aggregated by pers qml-module-org-kde-people - framework providing unified access to contacts aggregated by pers Closes: 782108 Changes: kpeople (5.12.0-1) unstable; urgency=medium . * New upstream release (5.12.0). * Really add the kpeople2 breaks/replaces (Closes: #782108) Checksums-Sha1: 376e8c285b8f2d2d9a448814177ae1de5509e185 2710 kpeople_5.12.0-1.dsc 3572d7d08b37411133f3e7ce2b504181b6e303ad 57324 kpeople_5.12.0.orig.tar.xz 5e31401735a51670766ce2fbf8d1c520e1047792 3564 kpeople_5.12.0-1.debian.tar.xz e1afa886dac18becd79bd210f0b8ece5f995d71c 13980 libkf5people-data_5.12.0-1_all.deb d15bb3c1f645be0ef7b69bc75a5d6da025627cbc 2560832 libkf5people-dbg_5.12.0-1_amd64.deb 558a1dd5ffe254fba314a88f3509f93c3308aaf7 13130 libkf5people-dev_5.12.0-1_amd64.deb 9c06223383fdee7bf8b3d6ed405cb9cb278d0e5f 52128 libkf5people5_5.12.0-1_amd64.deb ebda74e6a2e79a4e61e75ccdefc4389b7ad30c57 12418 libkf5peoplebackend5_5.12.0-1_amd64.deb 454b4b9d17bc99a91789e86045b159e3acdbd14d 31334 libkf5peoplewidgets5_5.12.0-1_amd64.deb 36512223ae277eccdcbb1f2a44163bca960571ff 14450 qml-module-org-kde-people_5.12.0-1_amd64.deb Checksums-Sha256: 8e8e3ac858cd1ba3ee3747638a3998aba9282a4c22f2cb18d378dbcd488b2f7d 2710 kpeople_5.12.0-1.dsc 2813e2047ffc3abae42acbc01b45ab1045b8cb0c5666ed8e03ab3bd67355185d 57324 kpeople_5.12.0.orig.tar.xz
Bug#777869: marked as done (gearmand: ftbfs with GCC-5)
Your message dated Fri, 10 Jul 2015 11:34:30 +
with message-id e1zdwza-000498...@franck.debian.org
and subject line Bug#777869: fixed in gearmand 1.0.6-5.1
has caused the Debian Bug report #777869,
regarding gearmand: 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.)
--
777869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:gearmand
Version: 1.0.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/gearmand_1.0.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
[...]
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define __EXTENSIONS__ 1
| #define _ALL_SOURCE 1
| #define _GNU_SOURCE 1
| #define _POSIX_PTHREAD_SEMANTICS 1
| #define _TANDEM_SOURCE 1
| #define PACKAGE gearmand
| #define VERSION 1.0.6
| #define HAVE_DLFCN_H 1
| #define LT_OBJDIR .libs/
| #define HOST_VENDOR pc
| #define HOST_OS linux-gnu
| #define HOST_CPU x86_64
| #define TARGET_VENDOR pc
| #define TARGET_OS linux-gnu
| #define TARGET_CPU x86_64
| #define TARGET_OS_LINUX 1
| #define DEBUG 0
| #define VCS_SYSTEM none
| #define VCS_CHECKOUT 0
| #define NDEBUG 1
| /* end confdefs.h. */
|
| #if defined __ICC (defined __unix || defined )
| /* OK */
| #else
| # error defined __ICC (defined __unix || defined )
| #endif
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:16802: g++ -c -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -D_FORTIFY_SOURCE=2 conftest.cpp 5
conftest.cpp:43:3: error: #error defined __ICL
# error defined __ICL
^
configure:16802: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME gearmand
| #define PACKAGE_TARNAME gearmand
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
---End Message---
---BeginMessage---
Source: gearmand
Source-Version: 1.0.6-5.1
We believe that the bug you reported is fixed in the latest version of
gearmand, 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 777...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose d...@debian.org (supplier of updated gearmand 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, 09 Jul 2015 12:44:56 +0200
Source: gearmand
Binary: libgearman7 libgearman-dev libgearman-dbg libgearman7-dbg
libgearman-doc gearman-job-server gearman-tools gearman
Architecture: source amd64 all
Version: 1.0.6-5.1
Distribution: unstable
Urgency: medium
Maintainer: Stig Sandbeck Mathisen s...@debian.org
Changed-By: Matthias Klose d...@debian.org
Description:
gearman- Distributed job queue
gearman-job-server - Job server for the Gearman distributed job queue
gearman-tools - Tools for the Gearman distributed job queue
libgearman-dbg - transitional dummy package
libgearman-dev - Development files for the Gearman Library
libgearman-doc - API Documentation for the Gearman Library
libgearman7 - Library providing Gearman client and
Bug#777961: marked as done (libomxil-bellagio: ftbfs with GCC-5)
Your message dated Fri, 10 Jul 2015 11:49:34 + with message-id e1zdwoa-0003ax...@franck.debian.org and subject line Bug#777961: fixed in libomxil-bellagio 0.9.3-3 has caused the Debian Bug report #777961, regarding libomxil-bellagio: 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.) -- 777961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:libomxil-bellagio Version: 0.9.3-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/libomxil-bellagio_0.9.3-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 [...] libtool: link: (cd .libs rm -f libomxaudio_effects.so.0 ln -s libomxaudio_effects.so.0.0.0 libomxaudio_effects.so.0) libtool: link: (cd .libs rm -f libomxaudio_effects.so ln -s libomxaudio_effects.so.0.0.0 libomxaudio_effects.so) libtool: link: ar cru .libs/libomxaudio_effects.a libomxaudio_effects_la-omx_volume_component.o libomxaudio_effects_la-omx_audiomixer_component.o libomxaudio_effects_la-library_entry_point.o libtool: link: ranlib .libs/libomxaudio_effects.a libtool: link: ( cd .libs rm -f libomxaudio_effects.la ln -s ../libomxaudio_effects.la libomxaudio_effects.la ) make[5]: Leaving directory '/«PKGBUILDDIR»/src/components/audio_effects' Making all in clocksrc make[5]: Entering directory '/«PKGBUILDDIR»/src/components/clocksrc' /bin/bash ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../include -I../../../src -I../../../src/base -Wall -Werror -Wno-error=unused-but-set-variable -Wno-error=unused-but-set-parameter -DCONFIG_DEBUG_LEVEL=0 -c -o libomxclocksrc_la-omx_clocksrc_component.lo `test -f 'omx_clocksrc_component.c' || echo './'`omx_clocksrc_component.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../include -I../../../src -I../../../src/base -Wall -Werror -Wno-error=unused-but-set-variable -Wno-error=unused-but-set-parameter -DCONFIG_DEBUG_LEVEL=0 -c omx_clocksrc_component.c -fPIC -DPIC -o .libs/libomxclocksrc_la-omx_clocksrc_component.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../include -I../../../src -I../../../src/base -Wall -Werror -Wno-error=unused-but-set-variable -Wno-error=unused-but-set-parameter -DCONFIG_DEBUG_LEVEL=0 -c omx_clocksrc_component.c -o libomxclocksrc_la-omx_clocksrc_component.o /dev/null 21 /bin/bash ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../include -I../../../src -I../../../src/base -Wall -Werror -Wno-error=unused-but-set-variable -Wno-error=unused-but-set-parameter -DCONFIG_DEBUG_LEVEL=0 -c -o libomxclocksrc_la-library_entry_point.lo `test -f 'library_entry_point.c' || echo './'`library_entry_point.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../include -I../../../src -I../../../src/base -Wall -Werror -Wno-error=unused-but-set-variable -Wno-error=unused-but-set-parameter -DCONFIG_DEBUG_LEVEL=0 -c library_entry_point.c -fPIC -DPIC -o .libs/libomxclocksrc_la-library_entry_point.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../include -I../../../src -I../../../src/base -Wall -Werror -Wno-error=unused-but-set-variable -Wno-error=unused-but-set-parameter -DCONFIG_DEBUG_LEVEL=0 -c library_entry_point.c -o libomxclocksrc_la-library_entry_point.o /dev/null 21 /bin/bash ../../../libtool --tag=CC --mode=link gcc -I../../../include -I../../../src -I../../../src/base -Wall -Werror
Bug#791445: [Ceph-maintainers] Bug#791445: : Bug#791445: ceph: uses bundled libjerasure library again
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/07/15 22:27, Thomas Goirand wrote: One of the reasons why I like standalone library is that it can run its own tests as well -- a something rarely seen in bundled (statically linked) libraries. Unfortunately at the moment libjerasure package do not run any tests... :( There's no question asked here. Embedding a library which is at the same time available standalone is a RC bug (severity: serious, because of a strong policy violation) which shall be fixed asap (so the severity of the bug is correct). Actually I don't think this is a RC bug - policy says 'should' not 'must '. I agree that having a single libjerasure etc... is preferably, but at the same time, the way the build works (multiple, cpu optimized plugins including jerasure and gf-complete) in Ceph and how it *does* do runtime detection of CPU features means that if we switch now to using libjerasure, we cripple Ceph performance on any reasonably specified server for users who want to use erasure coding. I'd actually feel compelled to raise an RC bug against Ceph being fundamentally broken in this area if this where the case. Switch to libjerasure/gf-complete? - yes - when? when its possible todo the correct runtime determination of CPU features in these codebases, and we're able to make Ceph build and use this effectively. So not yet... - -- James Page Ubuntu and Debian Developer james.p...@ubuntu.com jamesp...@debian.org -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVn7hlAAoJEL/srsug59jDMYYP/ivUsNw2RBPlvJkPDgvfcPke h2dE6xrETy4me2+9V2dVkSnQhxNpOJjNUezagfZJ1aD9D0c5DpW2qZqlDlhJI6Cp dk4VxMD3NCBMRaBO0TmhfO4t21L5FAyjRS5DZ8VHrUvXVMfxZFZ6DbD1uXhowega 1pE67bXWSsXEu1yOhZTqLbdx26mBtOSPyS4VXfHofY5xlDnneJBbD85nEKi37VT9 Sbbiy3CPWzGf6mIFlQbxDUSDoaQuXY8ZMkMX+RdkCloLmy1QSDJzU6Folhe8Aba7 2yjOHzHrgykm6x2YB/HaLgBctgcz21US2SuX4Y3IXHHXqnKL8dZpkWQLFawwpWTf npSmya/P/ThxAQ3Ra/9FwJMGhvzRjdftsmoIq0jwGV7Xl41CqgAlSIll5u+wWlr0 mVKY3tFanAH0WdXx9qOfO2eLCx9bOuhm9D6xrQufeFTipVeeARZwPCQdWpbCWN94 kHxrZz6MUb8+CW86CtKRhiVR4xCDK1NJzgAkrMMnRD+Z/BW5FqPQB7dJFoD4dX0s xiHlFTGXdweorsus7MHiw0Ylhp7/AFwshn0DjsXI0fXv9hMvWigSUCjIH1hK8GKD tyK0TlYu3JtGKL33NczN5mGQe5Hg76ejGpHGSqp8EthZCDeNZhHy1dq6wFUrYQ6M 3LKDAuwK4/PlpVVXkj6r =1/Bp -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: autoconf-archive: diff for NMU version 20150224-2.1
Processing control commands: tags 790937 + patch Bug #790937 [autoconf-archive] autoconf-archive: contains ax_check_enable_debug.m4, ax_code_coverage.m4 which are also in gnome-common Added tag(s) patch. tags 790937 + pending Bug #790937 [autoconf-archive] autoconf-archive: contains ax_check_enable_debug.m4, ax_code_coverage.m4 which are also in gnome-common Added tag(s) pending. -- 790937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790937 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#790937: autoconf-archive: diff for NMU version 20150224-2.1
Control: tags 790937 + patch
Control: tags 790937 + pending
Hi maintainers,
This breaks upgrades and is quite annoying, so I've prepared an NMU and
uploaded it to DELAYED/2. Feel free to (ask me to or do it yourself)
cancel, reschedule, supersede with your own upload, etc.
Cheers,
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.com ]
diff -Nru autoconf-archive-20150224/debian/changelog autoconf-archive-20150224/debian/changelog
--- autoconf-archive-20150224/debian/changelog 2015-07-06 22:54:30.0 +0100
+++ autoconf-archive-20150224/debian/changelog 2015-07-10 13:04:49.0 +0100
@@ -1,3 +1,12 @@
+autoconf-archive (20150224-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add Breaks and Replaces on gnome-common ( 3.14.0-2~) due to
+autoconf-archive and gnome-common both shipping the same .m4 files.
+(Closes: #790937)
+
+ -- Iain Lane i...@orangesquash.org.uk Fri, 10 Jul 2015 13:04:49 +0100
+
autoconf-archive (20150224-2) unstable; urgency=medium
* Acknowledge NMU.
diff -Nru autoconf-archive-20150224/debian/control autoconf-archive-20150224/debian/control
--- autoconf-archive-20150224/debian/control 2015-07-03 17:50:40.0 +0100
+++ autoconf-archive-20150224/debian/control 2015-07-10 13:04:45.0 +0100
@@ -14,9 +14,9 @@
Pre-Depends: dpkg (= 1.17.5)
Depends: ${misc:Depends}
Recommends: autoconf
-Replaces: autoconf-gl-macros ( 20130609-1~)
+Replaces: autoconf-gl-macros ( 20130609-1~), gnome-common ( 3.14.0-2~)
Enhances: autoconf
-Breaks: autoconf-gl-macros ( 20130609-1~)
+Breaks: autoconf-gl-macros ( 20130609-1~), gnome-common ( 3.14.0-2~)
Description: Autoconf Macro Archive
Autoconf Macro Archive aims to provide a central repository of
useful and tested Autoconf macros for software developers around the
@@ -29,4 +29,4 @@
Depends: ${misc:Depends}, autoconf-archive
Section: oldlibs
Description: Autoconf OpenGL Macro Archive -- transitional dummy package
- This is a transitional dummy package. It can safely be removed.
\ No newline at end of file
+ This is a transitional dummy package. It can safely be removed.
signature.asc
Description: Digital signature
Bug#755202: network-manager: keeps creating and using new connection eth0
Hello Michael, to reproduce this behaviour is quite easy. During Debian installation create an encrypted root fs, then additionally install dropbear. Due to Dropbear the network will be configured in initramfs with the current ip data. This will cause an already configured eth0 at the time when Network Manager gets started. Kind regards Maddese -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777971: librcsb-core-wrapper: ftbfs with GCC-5
Control: tags -1 + patch pending attaching patch, and uploading to delayed. diff -Nru librcsb-core-wrapper-1.005/debian/changelog librcsb-core-wrapper-1.005/debian/changelog --- librcsb-core-wrapper-1.005/debian/changelog 2015-02-14 18:08:44.0 +0100 +++ librcsb-core-wrapper-1.005/debian/changelog 2015-07-10 13:47:21.0 +0200 @@ -1,3 +1,9 @@ +librcsb-core-wrapper (1.005-3.1) unstable; urgency=medium + + * Fix GCC version detection. Closes: #777971. + + -- Matthias Klose d...@debian.org Fri, 10 Jul 2015 13:46:42 +0200 + librcsb-core-wrapper (1.005-3) unstable; urgency=medium * Patch for Henry Spencer regular expressions (regex) library contains diff -Nru librcsb-core-wrapper-1.005/debian/patches/gcc5.diff librcsb-core-wrapper-1.005/debian/patches/gcc5.diff --- librcsb-core-wrapper-1.005/debian/patches/gcc5.diff 1970-01-01 01:00:00.0 +0100 +++ librcsb-core-wrapper-1.005/debian/patches/gcc5.diff 2015-07-10 13:52:00.0 +0200 @@ -0,0 +1,13 @@ +Index: b/etc/platform.sh +=== +--- a/etc/platform.sh b/etc/platform.sh +@@ -67,7 +67,7 @@ case `uname -s` in + # Check if it is a Linux platform + Linux) + # Check if it is GCC version 4.x +- gcc_ver=`gcc --version | grep -e 4\.` ++ gcc_ver=`gcc --version | grep -e [456789]\.` + if [[ -z $gcc_ver ]] + then + # It is not GCC version 4.x. Check if it is GCC version 3.x diff -Nru librcsb-core-wrapper-1.005/debian/patches/series librcsb-core-wrapper-1.005/debian/patches/series --- librcsb-core-wrapper-1.005/debian/patches/series2015-02-14 17:44:47.0 +0100 +++ librcsb-core-wrapper-1.005/debian/patches/series2015-07-10 13:45:51.0 +0200 @@ -12,3 +12,4 @@ exit-in-shlib make_test_target regcomp_cert_fix.patch +gcc5.diff
Bug#777964: marked as done (libosl: ftbfs with GCC-5)
Your message dated Fri, 10 Jul 2015 12:07:16 + with message-id e1zdx5i-0002fk...@franck.debian.org and subject line Bug#777964: fixed in libosl 0.6.0-3.2 has caused the Debian Bug report #777964, regarding libosl: 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.) -- 777964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777964 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:libosl Version: 0.6.0-3.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/libosl_0.6.0-3.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 [...] grep ../lib/move_generator/legalMoves.cc .deps/move_generator/legalMoves.cc.d /dev/null 21 || (rm -f .deps/move_generator/legalMoves.cc.d; false) if [ ! -d `dirname .deps/move_generator/promote_.cc.d` ]; then mkdir -p `dirname .deps/move_generator/promote_.cc.d`; fi; g++ -MM -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -DOSL_HOME=\/«PKGBUILDDIR»\ -O3 -funroll-loops -funswitch-loops -fpeel-loops --param large-function-growth=48000 --param inline-unit-growth=8000 --param max-inline-insns-single=8000 -DNDEBUG -fomit-frame-pointer -pipe -march=k8 -DOSL_SMP -fPIC -Wall -Wwrite-strings -Wextra -Wstrict-aliasing=2 -Woverloaded-virtual -Wcast-align -Wwrite-strings -Wpointer-arith -Wno-unused-parameter -Wno-missing-field-initializers -Werror -I../include -D_REENTRANT ../lib/move_generator/promote_.cc \ | sed 's/\(.*\.o\)[ :]*/move_generator\/promote_.o .deps\/move_generator\/promote_.cc.d : /g' .deps/move_generator/promote_.cc.d grep ../lib/move_generator/promote_.cc .deps/move_generator/promote_.cc.d /dev/null 21 || (rm -f .deps/move_generator/promote_.cc.d; false) if [ ! -d `dirname .deps/move_generator/capture_.cc.d` ]; then mkdir -p `dirname .deps/move_generator/capture_.cc.d`; fi; g++ -MM -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -DOSL_HOME=\/«PKGBUILDDIR»\ -O3 -funroll-loops -funswitch-loops -fpeel-loops --param large-function-growth=48000 --param inline-unit-growth=8000 --param max-inline-insns-single=8000 -DNDEBUG -fomit-frame-pointer -pipe -march=k8 -DOSL_SMP -fPIC -Wall -Wwrite-strings -Wextra -Wstrict-aliasing=2 -Woverloaded-virtual -Wcast-align -Wwrite-strings -Wpointer-arith -Wno-unused-parameter -Wno-missing-field-initializers -Werror -I../include -D_REENTRANT ../lib/move_generator/capture_.cc \ | sed 's/\(.*\.o\)[ :]*/move_generator\/capture_.o .deps\/move_generator\/capture_.cc.d : /g' .deps/move_generator/capture_.cc.d grep ../lib/move_generator/capture_.cc .deps/move_generator/capture_.cc.d /dev/null 21 || (rm -f .deps/move_generator/capture_.cc.d; false) if [ ! -d `dirname .deps/move_generator/pieceOnBoard.cc.d` ]; then mkdir -p `dirname .deps/move_generator/pieceOnBoard.cc.d`; fi; g++ -MM -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -DOSL_HOME=\/«PKGBUILDDIR»\ -O3 -funroll-loops -funswitch-loops -fpeel-loops --param large-function-growth=48000 --param inline-unit-growth=8000 --param max-inline-insns-single=8000 -DNDEBUG -fomit-frame-pointer -pipe -march=k8 -DOSL_SMP -fPIC -Wall -Wwrite-strings -Wextra -Wstrict-aliasing=2 -Woverloaded-virtual -Wcast-align -Wwrite-strings -Wpointer-arith -Wno-unused-parameter -Wno-missing-field-initializers -Werror -I../include -D_REENTRANT ../lib/move_generator/pieceOnBoard.cc \ | sed 's/\(.*\.o\)[ :]*/move_generator\/pieceOnBoard.o .deps\/move_generator\/pieceOnBoard.cc.d : /g'
Processed: fix build using GCC 5
Processing control commands: tags -1 + patch pending Bug #82 [src:asterisk] asterisk: ftbfs with GCC-5 Added tag(s) patch and pending. -- 82: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=82 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#789088: marked as done (FTBFS: `require': cannot load such file -- minitest/autorun (LoadError))
Your message dated Fri, 10 Jul 2015 12:38:46 + with message-id e1zdxzm-u6...@franck.debian.org and subject line Bug#789088: fixed in ruby-beaneater 1.0.0-1 has caused the Debian Bug report #789088, regarding FTBFS: `require': cannot load such file -- minitest/autorun (LoadError) 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.) -- 789088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ruby-beaneater Version: 0.3.3 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, The package fails to run the tests: Coveralls] Using SimpleCov's default settings. SimpleCov failed to recognize the test framework and/or suite used. Please specify manually using SimpleCov.command_name 'Unit Tests'. [Coveralls] Outside the Travis environment, not sending data. /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- minitest/autorun (LoadError) from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require' from /home/faux/ruby-beaneater-0.3.3/test/test_helper.rb:5:in `top (required)' [..] The full build log can be seen on the Reproducible Builds builder: https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-beaneater.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-20-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) ---End Message--- ---BeginMessage--- Source: ruby-beaneater Source-Version: 1.0.0-1 We believe that the bug you reported is fixed in the latest version of ruby-beaneater, 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. Apollon Oikonomopoulos apoi...@debian.org (supplier of updated ruby-beaneater 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: Fri, 10 Jul 2015 14:38:15 +0300 Source: ruby-beaneater Binary: ruby-beaneater Architecture: source all Version: 1.0.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Apollon Oikonomopoulos apoi...@debian.org Description: ruby-beaneater - simple beanstalkd client for Ruby Closes: 789088 Changes: ruby-beaneater (1.0.0-1) unstable; urgency=medium . * New upstream release. * Remove test/pool_test.rb and test/pool_command_test.rb from the ruby test lists: pool support dropped upstream. * Build-Depend on ruby-minitest. Fixes FTBFS due to test suite failure (Closes: #789088). Checksums-Sha1: 68f8f5e985c7e55a86c96150bcf15749bc2aaf60 2129 ruby-beaneater_1.0.0-1.dsc c763e500eb2c00823b1b73d988cc05000dfedf44 27972 ruby-beaneater_1.0.0.orig.tar.gz f3a57f901d437dd554b85ca5a7fdaf843a9d38d9 2660 ruby-beaneater_1.0.0-1.debian.tar.xz ea8a6745bdbf5f94f48cf32c19dd689983e749e7 22098 ruby-beaneater_1.0.0-1_all.deb Checksums-Sha256: ddb7ef8189339f9de41e8be414e36ce146c9ad4e10c49187474ed667b86e0d7d 2129 ruby-beaneater_1.0.0-1.dsc 817f5ceb88d3a419c7a50dc4a3e83c8dbaf404b268d619953b32dd49e87e69ae 27972 ruby-beaneater_1.0.0.orig.tar.gz 381d8f41564956b22df4a45f3a40d4953d55459da770cbdb6cd10d4e3f53b020 2660 ruby-beaneater_1.0.0-1.debian.tar.xz 0bfc19f945c1e57e5248d843e9a67e85f8d3aaf8a1530b3852ced9130a21e991 22098 ruby-beaneater_1.0.0-1_all.deb Files: 24bdb5fd344d716ce837dcff56d27665 2129 ruby optional ruby-beaneater_1.0.0-1.dsc e4ec7a76199cd306707c0a5f5c4cb8b3 27972 ruby optional ruby-beaneater_1.0.0.orig.tar.gz 8c5bc9ba9523b08e88c1fd484acb3f73 2660 ruby optional ruby-beaneater_1.0.0-1.debian.tar.xz 6b9d32b9832cb46948f2519b5c748005 22098 ruby optional ruby-beaneater_1.0.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVn7E7AAoJEHLTQsHpUUMGRNAQAKL7U6z7M72aHyifHgxzc4yy
Bug#777877: marked as done (gltron: ftbfs with GCC-5)
Your message dated Fri, 10 Jul 2015 12:35:38 + with message-id e1zdxwk-0007ll...@franck.debian.org and subject line Bug#777877: fixed in gltron 0.70final-12.1 has caused the Debian Bug report #777877, regarding gltron: 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.) -- 777877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:gltron Version: 0.70final-12 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/gltron_0.70final-12_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 [...] Making all in configuration make[3]: Entering directory '/«PKGBUILDDIR»/src/configuration' x86_64-linux-gnu-gcc -DPACKAGE_NAME=\gltron\ -DPACKAGE_TARNAME=\gltron\ -DPACKAGE_VERSION=\0.70\ -DPACKAGE_STRING=\gltron\ 0.70\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\gltron\ -DVERSION=\0.70\ -DHAVE_LIBGL=1 -DHAVE_LIBZ=1 -DHAVE_LIBPNG=1 -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_UNISTD_H=1 -DHAVE_GL_GL_H=1 -DHAVE_MKSTEMP=1 -I. -DDATA_DIR=\/usr/share/games/gltron\ -DSNAP_DIR=\~\ -DPREF_DIR=\~\ -I../../lua/include -I../../nebu/include -I../../src/include -Wall -g -O2 -DSEPARATOR='/' -Wall -Werror -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -MT settings.o -MD -MP -MF .deps/settings.Tpo -c -o settings.o settings.c mv -f .deps/settings.Tpo .deps/settings.Po rm -f libconfiguration.a ar cru libconfiguration.a settings.o x86_64-linux-gnu-ranlib libconfiguration.a make[3]: Leaving directory '/«PKGBUILDDIR»/src/configuration' Making all in audio make[3]: Entering directory '/«PKGBUILDDIR»/src/audio' x86_64-linux-gnu-gcc -DPACKAGE_NAME=\gltron\ -DPACKAGE_TARNAME=\gltron\ -DPACKAGE_VERSION=\0.70\ -DPACKAGE_STRING=\gltron\ 0.70\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\gltron\ -DVERSION=\0.70\ -DHAVE_LIBGL=1 -DHAVE_LIBZ=1 -DHAVE_LIBPNG=1 -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_UNISTD_H=1 -DHAVE_GL_GL_H=1 -DHAVE_MKSTEMP=1 -I. -DDATA_DIR=\/usr/share/games/gltron\ -DSNAP_DIR=\~\ -DPREF_DIR=\~\ -I../../lua/include -I../../nebu/include -I../../src/include -Wall -g -O2 -DSEPARATOR='/' -Wall -Werror -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -MT sound.o -MD -MP -MF .deps/sound.Tpo -c -o sound.o sound.c mv -f .deps/sound.Tpo .deps/sound.Po x86_64-linux-gnu-g++ -DPACKAGE_NAME=\gltron\ -DPACKAGE_TARNAME=\gltron\ -DPACKAGE_VERSION=\0.70\ -DPACKAGE_STRING=\gltron\ 0.70\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\gltron\ -DVERSION=\0.70\ -DHAVE_LIBGL=1 -DHAVE_LIBZ=1 -DHAVE_LIBPNG=1 -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_UNISTD_H=1 -DHAVE_GL_GL_H=1 -DHAVE_MKSTEMP=1 -I. -DDATA_DIR=\/usr/share/games/gltron\ -DSNAP_DIR=\~\ -DPREF_DIR=\~\ -I../../lua/include -I../../nebu/include -I../../src/include -Wall -g -O2 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -MT sound_glue.o -MD -MP -MF .deps/sound_glue.Tpo -c -o sound_glue.o sound_glue.cpp sound_glue.cpp:23:13: warning: 'void output_decoders()' defined but not used [-Wunused-function] static void
Processed: Re: Bug#791964: gdm3: upgrade causes X session to be terminated
Processing control commands: severity -1 serious Bug #791964 [gdm3] gdm3: upgrade causes X session to be terminated Severity set to 'serious' from 'normal' -- 791964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791964 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#778076: marked as done (python-enable: ftbfs with GCC-5)
Your message dated Fri, 10 Jul 2015 11:05:56 +
with message-id e1zdw7w-0007ri...@franck.debian.org
and subject line Bug#778076: fixed in python-enable 4.3.0-2.1
has caused the Debian Bug report #778076,
regarding python-enable: 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.)
--
778076: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:python-enable
Version: 4.3.0-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/python-enable_4.3.0-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
[...]
File /usr/lib/python2.7/dist-packages/numpy/distutils/misc_util.py, line
935, in get_subpackage
caller_level = caller_level + 1)
File /usr/lib/python2.7/dist-packages/numpy/distutils/misc_util.py, line
872, in _get_configuration_from_setup_py
config = setup_module.configuration(*args)
File kiva/agg/setup.py, line 88, in configuration
if int(m.group(1)) 4:
AttributeError: 'NoneType' object has no attribute 'group'
make: [python-module-clean/python-enable] Error 1 (ignored)
/usr/share/cdbs/1/class/python-distutils.mk:158: recipe for target
'python-module-clean/python-enable' failed
rm -rf debian/python-module-stampdir
find /«PKGBUILDDIR» -name '*.py[co]' -delete
find /«PKGBUILDDIR» -name __pycache__ -type d -empty -delete
find /«PKGBUILDDIR» -prune -name '*.egg-info' -exec rm -rf '{}' ';'
debian/rules build-arch
test -x debian/rules
mkdir -p .
/usr/share/cdbs/1/rules/buildcore.mk:110: CDBS WARNING:DEB_COMPRESS_EXCLUDE
is deprecated since 0.4.85
mkdir -p debian/python-module-stampdir
set -e; \
cd . \
python setup.py build --build-base=/«PKGBUILDDIR»/./build;
/usr/lib/python2.7/dist-packages/numpy/distutils/system_info.py:576:
UserWarning: Specified path /usr/local/include/python2.7 is invalid.
warnings.warn('Specified path %s is invalid.' % d)
/usr/lib/python2.7/dist-packages/numpy/distutils/system_info.py:576:
UserWarning: Specified path is invalid.
warnings.warn('Specified path %s is invalid.' % d)
Traceback (most recent call last):
File setup.py, line 56, in module
config = configuration().todict()
File setup.py, line 48, in configuration
config.add_subpackage('kiva')
File /usr/lib/python2.7/dist-packages/numpy/distutils/misc_util.py, line
966, in add_subpackage
caller_level = 2)
File /usr/lib/python2.7/dist-packages/numpy/distutils/misc_util.py, line
935, in get_subpackage
caller_level = caller_level + 1)
File /usr/lib/python2.7/dist-packages/numpy/distutils/misc_util.py, line
872, in _get_configuration_from_setup_py
config = setup_module.configuration(*args)
File kiva/setup.py, line 27, in configuration
config.add_subpackage('agg')
File /usr/lib/python2.7/dist-packages/numpy/distutils/misc_util.py, line
966, in add_subpackage
caller_level = 2)
File /usr/lib/python2.7/dist-packages/numpy/distutils/misc_util.py, line
935, in get_subpackage
caller_level = caller_level + 1)
File /usr/lib/python2.7/dist-packages/numpy/distutils/misc_util.py, line
872, in _get_configuration_from_setup_py
config = setup_module.configuration(*args)
File kiva/agg/setup.py, line 88, in configuration
if int(m.group(1)) 4:
AttributeError: 'NoneType' object has no attribute 'group'
make: *** [debian/python-module-stampdir/python-enable] Error 1
/usr/share/cdbs/1/class/python-distutils.mk:116: recipe for target
Bug#734385: cardstories: Package installation fails if /etc/apache2/conf.d does not exist
Package: cardstories Version: 1.0.6-1.3 Followup-For: Bug #734385 tags 734385 + patch Here is a patch fixing this issue for apache2.4. diff -r old/cardstories-1.0.6/debian/cardstories.postinst cardstories-1.0.6/debian/cardstories.postinst 31c31 conf=/etc/apache2/conf.d/cardstories.conf --- conf=/etc/apache2/conf-available/cardstories.conf 35a36 a2enconf cardstories diff -r old/cardstories-1.0.6/debian/cardstories.postrm cardstories-1.0.6/debian/cardstories.postrm 30c30,33 conf=/etc/apache2/config.d/cardstories.conf --- if [ -f conf=/etc/apache2/conf-enabled/cardstories.conf ]; then a2disconf cardstories fi conf=/etc/apache2/conf-available/cardstories.conf
Bug#753195: cardstories: FTBFS: make[3]: virtualenv: Command not found
Package: cardstories Version: 1.0.6-1.3 Followup-For: Bug #753195 tags 753195 patch thanks virtualenv is no longer installed with python-virtualenv. Here is a patch adding it to Depends. diff -r old/cardstories-1.0.6/debian/control cardstories-1.0.6/debian/control 14c14,15 python-virtualenv --- python-virtualenv, virtualenv
Bug#792078: cantor-backend-qalculate: GPL3 not documented/incompatible mixing of GPL2/3 code
Package: cantor-backend-qalculate Version: 4:4.8.4-2 Severity: serious Tags: upstream Justification: Policy 2.3 I am going to accept this package, despite some issues with licensing. The major issue is the combination of GPL 2+ and GPL 3+ code in src/backends/ qalculate/ that does not appear to be mere aggregation plus the lack of a copying file for GPL 3. Either the two GPL v3 files should be relicensed by the copyright holders as GPL v2+ or a COPYING.GPL3 should be added (in which case the combination is allowed by upgrading thing to be effectively GPL3. I checked, and this problem goes back to wheezy, so since it's not new, I won't reject for it, but will file a bug instead. Please work with upstream to get this resolved. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792084: FTBFS: Fails to build from source
Package: yaboot Version: 1.3.16-4 Severity: serious Tags: sid stretch help Yaboot 1.3.16 and yaboot 1.3.17 fail to build with current version of e2fslibs. Last upload was built against e2fslibs 1.42.2 with some non trivial patching but it won't work with any later version. Introducing back legacy static e2fslibs version 1.41.x for the sole purpose of building yaboot against it would be one way to get around this problem. signature.asc Description: OpenPGP digital signature
Bug#792083: gaupol: Missing dependency python3-gi-cairo
Package: gaupol Version: 0.28.2-1 Severity: grave Justification: renders package unusable Hi, Without installing of python3-gi-cairo package, every time when I want to edit a entry I got Traceback (most recent call last): File /usr/share/gaupol/gaupol/view.py, line 143, in set_number renderer.props.text = str(row + 1) TypeError: Couldn't find foreign struct converter for 'cairo.Context' This renders the package almost unusable and may cause loss of in-memory modification because the program has to be force closed. Hmm, I found python3-gi-cairo is listed as Recommends. I think it should be promoted to Depends. Kanru -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gaupol depends on: ii gir1.2-gst-plugins-base-1.0 1.4.5-2 ii gir1.2-gstreamer-1.0 1.4.5-2 ii gir1.2-gtk-3.0 3.16.4-2 ii gstreamer1.0-plugins-good1.4.5-2+b1 ii python3 3.4.3-4 ii python3-aeidon 0.28.2-1 ii python3-gi 3.16.2-1 pn python3:any none Versions of packages gaupol recommends: pn gir1.2-gtkspell3-3.0 none pn gstreamer1.0-libav none pn gstreamer1.0-plugins-bad none pn gstreamer1.0-plugins-ugly none ii python3-chardet2.3.0-1 pn python3-enchantnone ii python3-gi-cairo 3.16.2-1 Versions of packages gaupol suggests: pn vlc | mplayer none -- 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#791521: marked as done (FTBFS: common.h: RFLOAT undefined: invalid type argument of.. RFLOAT(val)-float_value)
Your message dated Sat, 11 Jul 2015 00:15:52 + with message-id e1zdiso-0007az...@franck.debian.org and subject line Bug#791861: Removed package(s) from unstable has caused the Debian Bug report #791521, regarding FTBFS: common.h: RFLOAT undefined: invalid type argument of.. RFLOAT(val)-float_value 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.) -- 791521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-opengl Version: 0.60.1+dfsg2-3 Severity: serious Tags: sid 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 file included from ../common/common.h:54:0, from gl-1.0-1.1.c:18: .../common/conv.h: In function ‘num2double’: .../common/conv.h:55:1: warning: implicit declaration of function ‘RFLOAT’ [-Wimplicit-function-declaration] FASTCONV(num2double,double,FIX2LONG,rb_num2dbl) ^ .../common/conv.h:33:42: error: invalid type argument of ‘-’ (have ‘int’) #define FLOAT_VAL_ACCESS(val) RFLOAT(val)-float_value ^ .../common/conv.h:44:18: note: in expansion of macro ‘FLOAT_VAL_ACCESS’ return (_type_)FLOAT_VAL_ACCESS(val); \ ^ .../common/conv.h:55:1: note: in expansion of macro ‘FASTCONV’ FASTCONV(num2double,double,FIX2LONG,rb_num2dbl) ^ Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-opengl.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) ---End Message--- ---BeginMessage--- Version: 0.60.1+dfsg2-3+rm Dear submitter, as the package ruby-opengl has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/791861 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Processed: Re: Bug#787864: mysql-server-5.5: fails to start in piuparts test environment
Processing control commands: severity -1 important Bug #787864 [mysql-server-5.5,mysql-server-5.6] mysql-server-5.5: fails to start in piuparts test environment Severity set to 'important' from 'serious' -- 787864: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787864 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#787864: mysql-server-5.5: fails to start in piuparts test environment
Control: severity -1 important Hi Robie, On 2015-07-02 16:53, Robie Basak wrote: On Fri, Jun 05, 2015 at 09:54:04PM +0200, Andreas Beckmann wrote: during a test with piuparts I noticed your package now fails to start the server in a piuparts test environment, i.e. a a minimal sid or stretch chroot (while jessie works fine). This is most likely a regression introduced by another package since the versions in jessie and sid are the same ... I've pinned this down to a change in the behaviour of logger(1) as used by the postinst and filed bug 790875 against bsdutils. Thanks for digging into this. I've now applied a crude hack in my piuparts instance and use the logger binary from jessie for stretch and sid. That works for stretch, but not for sid, so there seems to be something different in 5.6 ... oh wait, there is a pending commit about exit 0 in the initscript ... I'll wait for that to be uploaded before digging further ... We can always stop using logger or wrap calls to it somehow as a workaround. This bug does not affect anyone running a syslog daemon or systemd, so I think it only affects piuparts testing and the non-default case. On this basis would it be reasonable to drop the severity and stop blocking this package from entering stretch? Yes, but not before I filed another RC bug regarding the my.cnf migration that needs to handle the mess created by mariadb-common: #792080 :-) Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792058: [Debian-med-packaging] Bug#792058: python3-cobra: SyntaxError: invalid syntax (2.x-isms)
Hi, and thanks for the bug report. On الجمعـة 10 تـمـوز 2015 12:07, Aaron M. Ucko wrote: Package: python3-cobra Version: 0.4.0b1-1 Severity: grave Justification: renders package unusable (uninstallable) Byte compilation of python3-cobra is failing due to the presence of syntax that was only valid in Python 2.x: Setting up python3-cobra (0.4.0b1-1) ... File /usr/lib/python3/dist-packages/cobra/solvers/glpk_solver_java.py, line 86 except Exception, e1: ^ SyntaxError: invalid syntax File /usr/lib/python3/dist-packages/cobra/solvers/cplex_solver_java.py, line 318 print '%s failed: %s'%(solver_name, status) ^ SyntaxError: invalid syntax File /usr/lib/python3/dist-packages/cobra/solvers/gurobi_solver_java.py, line 73 except Exception, e: ^ SyntaxError: invalid syntax dpkg: error processing package python3-cobra (--configure): subprocess installed post-installation script returned error exit status 1 Could you please take a look? I had code in my packaging that was supposed to remove those files for the python3-package. The *_java.py files are intended to provide jython support according to upstream, and jython is not available for python3. These files aren't relevant for this package, so I will make sure that they are removed from python3-cobra. Thanks and regards Afif -- Afif Elghraoui | عفيف الغراوي http://afif.ghraoui.name -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791449: fpm ini
Thank you for the advice, I have done this already. Ich war eine Zeitlang echt am verzweifeln! mfg, mike On 7/10/15, Dr. Tobias Quathamer to...@debian.org wrote: Am 05.07.2015 um 03:08 schrieb Mike Dupont: I found the problem the fpm ini was broken. [...] the solution was to just copy the ini file from a default. Hi Mike, thanks for the bug report. However, the package fpm has been removed from unstable and testing, so it won't be part of the next stable release. Upstream has been inactive for a long time, and I don't intend to take over the upstream maintenance of the program myself. Therefore, I suggest that you extract your passwords from fpm and import them into another password manager. There are a few alternatives available in Debian. Regards, Tobias -- James Michael DuPont Kansas Linux Fest http://kansaslinuxfest.us Free/Libre Open Source and Open Knowledge Association of Kansas http://openkansas.us Member of Free Libre Open Source Software Kosova http://www.flossk.org Saving Wikipedia(tm) articles from deletion http://SpeedyDeletion.wikia.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792063: marked as done (FTBFS: lngamma_bug.t and test1.t fail)
Your message dated Sat, 11 Jul 2015 01:04:04 + with message-id e1zdjd2-0006r2...@franck.debian.org and subject line Bug#792063: fixed in libmath-mpfr-perl 3.25-1 has caused the Debian Bug report #792063, regarding FTBFS: lngamma_bug.t and test1.t fail 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.) -- 792063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libmath-mpfr-perl Version: 3.24-1 Severity: serious Tags: sid Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: Test Summary Report --- t/lngamma_bug.t (Wstat: 0 Tests: 4 Failed: 2) Failed tests: 2-3 t/test1.t (Wstat: 0 Tests: 85 Failed: 1) Failed test: 69 Files=48, Tests=732, 13 wallclock secs ( 0.34 usr 0.13 sys + 3.05 cusr 0.45 csys = 3.97 CPU) Result: FAIL Failed 2/48 test programs. 3/732 subtests failed. Makefile:1007: recipe for target 'test_dynamic' failed Additionally, a number of tests seem to fail to run due to missing dependencies. Maybe they should be added at the right scope? Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/libmath-mpfr-perl.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-22-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) ---End Message--- ---BeginMessage--- Source: libmath-mpfr-perl Source-Version: 3.25-1 We believe that the bug you reported is fixed in the latest version of libmath-mpfr-perl, 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 792...@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 libmath-mpfr-perl 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: Sat, 11 Jul 2015 02:44:28 +0200 Source: libmath-mpfr-perl Binary: libmath-mpfr-perl Architecture: source Version: 3.25-1 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: gregor herrmann gre...@debian.org Description: libmath-mpfr-perl - perl interface to the MPFR (floating point) library Closes: 792063 Changes: libmath-mpfr-perl (3.25-1) unstable; urgency=medium . * Team upload. . [ Axel Beckert ] * debian/copyright: Deobfuscate e-mail address of copyright holder. Issue reported by DUCK. . [ gregor herrmann ] * Import upstream version 3.25 Fixes FTBFS: lngamma_bug.t and test1.t fail (Closes: #792063) Checksums-Sha1: c36aeb6ad4f728a4d58c303e430071ff134f878c 2236 libmath-mpfr-perl_3.25-1.dsc d3c91fe5250ff57c22c5d76e23c745621d8a5747 104028 libmath-mpfr-perl_3.25.orig.tar.gz 2b4c821f9b841c54eac758000afded3f9eac6b5b 3148 libmath-mpfr-perl_3.25-1.debian.tar.xz Checksums-Sha256: 1b41661e94d3f009dea6d0dd9817a8032267c7e7eeb16a50f91b80bae8f555e9 2236 libmath-mpfr-perl_3.25-1.dsc 5f5df3c14ff533de2b763d327b0821a5c6b6cf331deaa930db90a2e031aa755c 104028 libmath-mpfr-perl_3.25.orig.tar.gz ffa862924b2ce963068bccf80a68d58089c381a199a68fb3f95ded002d5557d1 3148 libmath-mpfr-perl_3.25-1.debian.tar.xz Files: d36a9c492803de630d3d6e66d0e63649 2236 perl optional libmath-mpfr-perl_3.25-1.dsc e62c05d6d54624bd800196954b982463 104028 perl optional libmath-mpfr-perl_3.25.orig.tar.gz 57449644778b8e09068bc03030a84b14 3148 perl optional libmath-mpfr-perl_3.25-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJVoGdEXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGM+MQAIrsgVzKtTexV5tM00K0kK+7 1e4H1pG44MR53lUV63xNaMF+v7XIpzPVzUi+EsZdy2mZhOgmadaqmLU4Umt57IpY 4pHBx5/pAMRAe/9oNVfghSppzdZZ4bh1ZEbg0aNS040n7bbIk8fxnLOALOmhswfo QPMf8RZjT3AhJGCYF0AdCUCaWJzUSUNCgDg1Q2L8lQ08HV358sZc5hhJApbbxkZb
Bug#792080: mysql-common: needs to handle upgrades from mariadb-common that creates my.cnf - mariadb.cnf symlink
Package: mysql-common
Version: 5.6.25-2
Severity: serious
Tags: patch
mariadb-common introduced some fallback mode to create a
my.cnf - mariadb.cnf symlink (and renames the original my.cnf to
my.cnf.old) in case the update-links script is not available.
This needs to be handled in mysql-common, because currently
upgrading mysql-common over mariadb-common in in stretch/sid results in
my.cnf.migrated being created that is actually mariadb.cnf instead of
my.conf.old
Since the issue is hard to describe in detail and with all pitfalls
without digging into it and testing it, I rather developed patches
that I tested in sid and stretch, to ensure sane upgrade paths.
The commit messages should explain all the problems involved ...
if you have more questions, just ask.
This cleanup code needs to go into mysql-common since it cannot be
enforced that mariadb-common is upgraded first (that package may be
deconfigured or in config-files-remaining state, leaving a messed up
my.cnf)
git://git.debian.org/users/anbe/tmp/mysql-5.6.git
Andreas Beckmann (6):
mysql-common.postinst: install my.cnf.fallback alternative after
rm_conffile my.cnf
mysql-common.preinst: revert mariadb-common my.cnf fallback symlink
mysql-common.preinst: recover from unmodfied mariadb.cnf as
my.cnf.migrated
mysql-common.postrm: delete my.cnf.{migrated,old} on purge
mysql-common.postrm: only remove alternatives created by our postinst
mysql-common: add Breaks: mariadb-common ( 10.0.20-3~)
Andreas
PS: this should go along with mariadb-common dropping that piece of code
and adding a Depends: mysql-common (= 5.6.25-3), I'm working on patches
for this, too.
PPS: The migration of my.cnf from conffile to alternatives otherwise
looks well thought and implemented. The lack of mariadb-common handling is
understandable since that fallback mode was implemented only recently
and after the my.cnf migration was designed.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: unarchiving 711619
Processing commands for cont...@bugs.debian.org:
# Fixed by version soon to be uploaded to the NEW queue
unarchive 711619
Bug #711619 {Done: Debian FTP Masters ftpmas...@ftp-master.debian.org}
[src:libtext-mediawikiformat-perl] libtext-mediawikiformat-perl: FTBFS with
perl 5.18: test failures
Warning: Unknown package 'src:libtext-mediawikiformat-perl'
Unarchived Bug 711619
Warning: Unknown package 'src:libtext-mediawikiformat-perl'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
711619: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711619
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#778183: xiphos: ftbfs with GCC-5
tags 778183 +patch thanks gcc5 makes exceeding the max template instantiation depth a fatal error, rather than a warning, and the previous max depth of 25 was insufficient. Simply increasing the debug maximum to 250 fixes the problem. --- xiphos-3.2.2+dfsg1.orig/wscript +++ xiphos-3.2.2+dfsg1/wscript @@ -199,8 +199,8 @@ def configure(conf): env['CXXFLAGS']= [] env['CXXFLAGS_OPTIMIZED'] = ['-O2'] env['CXXFLAGS_RELEASE']= ['-O2'] -env['CXXFLAGS_DEBUG'] = ['-g', '-DDEBUG', '-ftemplate-depth-25'] -env['CXXFLAGS_ULTRADEBUG'] = ['-g3', '-O0', '-DDEBUG', '-ftemplate-depth-25'] +env['CXXFLAGS_DEBUG'] = ['-g', '-DDEBUG', '-ftemplate-depth=250'] +env['CXXFLAGS_ULTRADEBUG'] = ['-g3', '-O0', '-DDEBUG', '-ftemplate-depth=250'] if env['IS_WIN32']: ## setup for Winsock on Windows (required for read-aloud) -- Brett Johnson br...@hp.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards
Control: severity -1 important (downgrading severity as per your explanations) Am 10.07.2015 um 16:41 schrieb Klaus Ethgen: Hello, Am Mo den 6. Jul 2015 um 20:26 schrieb Martin Pitt: Klaus Ethgen [2015-07-05 1:34 +0100]: Well, it clearly shows that it probes some unexisting USB stuff. It's a shot into the dark, but this makes me wonder if this is another fallout of enabling USB auto-suspend? Can you please try and move away /lib/udev/rules.d/42-usb-hid-pm.rules (rename it to *.rules.disabled or so), reboot, and see if that improves things? With version 222-1 there is no /lib/udev/rules.d/42-usb-hid-pm.rules anymore. However, I gave it a try but the bug is not gone. After SCSI detection it takes ~100 seconds to finish USB HID detection. That is ten times more than with udev 215-18. So the system is not unbootable anymore but painful slow booting. If the system if fully booted (with v222), is the problem reproducible if you run $ udevadm trigger $ udevadm settle Does the settle call block as well for such a long time? Have you seen my earlier reply regarding a verbose udev debug log? Would be great if you can gather this information. Michael -- 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#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards
Processing control commands: severity -1 important Bug #790561 [udev] After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards Severity set to 'important' from 'critical' -- 790561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790561 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#778107: marked as done (rlvm: ftbfs with GCC-5)
Your message dated Fri, 10 Jul 2015 16:55:59 +0200
with message-id 559fdcff.5000...@debian.org
and subject line Re: rlvm: ftbfs with GCC-5
has caused the Debian Bug report #778107,
regarding rlvm: 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.)
--
778107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:rlvm
Version: 0.14-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/rlvm_0.14-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
[...]
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'169' from 'int' to 'int8_t {aka signed char}' inside { }
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'168' from 'int' to 'int8_t {aka signed char}' inside { }
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'167' from 'int' to 'int8_t {aka signed char}' inside { }
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'166' from 'int' to 'int8_t {aka signed char}' inside { }
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'165' from 'int' to 'int8_t {aka signed char}' inside { }
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'164' from 'int' to 'int8_t {aka signed char}' inside { }
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'163' from 'int' to 'int8_t {aka signed char}' inside { }
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'162' from 'int' to 'int8_t {aka signed char}' inside { }
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'161' from 'int' to 'int8_t {aka signed char}' inside { }
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'160' from 'int' to 'int8_t {aka signed char}' inside { }
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'159' from 'int' to 'int8_t {aka signed char}' inside { }
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'158' from 'int' to 'int8_t {aka signed char}' inside { }
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'157' from 'int' to 'int8_t {aka signed char}' inside { }
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'156' from 'int' to 'int8_t {aka signed char}' inside { }
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'155' from 'int' to 'int8_t {aka signed char}' inside { }
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'154' from 'int' to 'int8_t {aka signed char}' inside { }
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'153' from 'int' to 'int8_t {aka signed char}' inside { }
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'152' from 'int' to 'int8_t {aka signed char}' inside { }
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'151' from 'int' to 'int8_t {aka signed char}' inside { }
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'150' from 'int' to 'int8_t {aka signed char}' inside { }
src/systems/base/koepac_voice_archive.cc:142:27: error: narrowing conversion of
'149' from 'int' to 'int8_t {aka signed char}' inside { }
Processed: Re: python-demgengeo: ftbfs with GCC-5
Processing control commands: tags -1 + patch pending Bug #778075 [src:python-demgengeo] python-demgengeo: ftbfs with GCC-5 Added tag(s) patch and pending. -- 778075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778075 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#778075: python-demgengeo: ftbfs with GCC-5
Control: tags -1 + patch pending attaching a patch, uploading to delayed. diff -Nru python-demgengeo-1.0/debian/changelog python-demgengeo-1.0/debian/changelog --- python-demgengeo-1.0/debian/changelog 2014-05-14 18:38:03.0 + +++ python-demgengeo-1.0/debian/changelog 2015-07-10 12:59:23.0 + @@ -1,3 +1,10 @@ +python-demgengeo (1.0-2.1) unstable; urgency=medium + + * Non maintainer upload. + * Call cpp with -P. Closes: #778075. + + -- Matthias Klose d...@debian.org Fri, 10 Jul 2015 14:58:40 +0200 + python-demgengeo (1.0-2) unstable; urgency=medium * [25149fb] Add autopkgtest. diff -Nru python-demgengeo-1.0/debian/patches/gcc5.diff python-demgengeo-1.0/debian/patches/gcc5.diff --- python-demgengeo-1.0/debian/patches/gcc5.diff 1970-01-01 00:00:00.0 + +++ python-demgengeo-1.0/debian/patches/gcc5.diff 2015-07-10 13:00:02.0 + @@ -0,0 +1,13 @@ +Index: b/build/m4/boost.m4 +=== +--- a/build/m4/boost.m4 b/build/m4/boost.m4 +@@ -76,7 +76,7 @@ dnl strip `\n' with backquotes, not the + dnl boost_cv_lib_version='1_37\r' for instance, which breaks + dnl everything else. + dnl Cannot use 'dnl' after [$4] because a trailing dnl may break AC_CACHE_CHECK +-(eval $ac_cpp conftest.$ac_ext) 2AS_MESSAGE_LOG_FD | ++(eval $ac_cpp -P conftest.$ac_ext) 2AS_MESSAGE_LOG_FD | + tr -d '\r' | + $SED -n -e $1 conftest.i 21], + [$3], diff -Nru python-demgengeo-1.0/debian/patches/series python-demgengeo-1.0/debian/patches/series --- python-demgengeo-1.0/debian/patches/series 2014-05-14 18:26:10.0 + +++ python-demgengeo-1.0/debian/patches/series 2015-07-10 12:59:32.0 + @@ -1,2 +1,3 @@ fix-rpath.patch replace_cerr_by_cout.patch +gcc5.diff
Bug#778075: python-demgengeo: ftbfs with GCC-5
Thanks a lot, Matthias, for the patch! Could you please remove the upload from delayed? I have prepared the newer version and I will apply your patch as well tonight. Thank you Anton 2015-07-10 15:19 GMT+02:00 Matthias Klose d...@debian.org: Control: tags -1 + patch pending attaching a patch, uploading to delayed. -- debian-science-maintainers mailing list debian-science-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792034: designate: Package is missing designate services
Package: designate Version: 2015.1.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? apt-get install designate * What was the outcome of this action? 2 services introduced in Kilo (designate-mdns designate-pool-manager) are not included in an install These are critical to designate functioning. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages designate depends on: ii designate-agent2015.1.0-1 ii designate-api 2015.1.0-1 ii designate-central 2015.1.0-1 ii designate-common 2015.1.0-1 ii dpkg 1.18.1 designate recommends no packages. designate suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790524: src:gmt: takes over files from several unrelated packages
On 2015-07-09 23:25, Sebastiaan Couwenberg wrote: The GMT 4 packaging also appended 'gmt' to the man page sections, I've reintroduced this in the ~exp7 revision that was just uploaded. ACK. I think that should do. If you add some more B+R: Selecting previously unselected package gmt-common. Preparing to unpack .../gmt-common_5.1.2+dfsg1-1~exp7_all.deb ... Unpacking gmt-common (5.1.2+dfsg1-1~exp7) ... dpkg: error processing archive /var/cache/apt/archives/gmt-common_5.1.2+dfsg1-1~exp7_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/psimage.1gmt.gz', which is also in package gmt-manpages 3.4.4-1 Errors were encountered while processing: /var/cache/apt/archives/gmt-common_5.1.2+dfsg1-1~exp7_all.deb gmt-manpages can probably be RM'ed from unstable. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790524: marked as done (src:gmt: takes over files from several unrelated packages)
Your message dated Fri, 10 Jul 2015 15:35:51 + with message-id e1zdal9-0003ni...@franck.debian.org and subject line Bug#790524: fixed in gmt 5.1.2+dfsg1-1~exp8 has caused the Debian Bug report #790524, regarding src:gmt: takes over files from several unrelated packages 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.) -- 790524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790524 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gmt Version: 5.1.2+dfsg1-1~exp4 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 ... which may not be appropriate in this case since the packages probably provide different functionality. So one must rename the binary it ships. From the attached log (scroll to the bottom...): Selecting previously unselected package gmt-common. Preparing to unpack .../gmt-common_5.1.2+dfsg1-1~exp4_all.deb ... Unpacking gmt-common (5.1.2+dfsg1-1~exp4) ... dpkg: error processing archive /var/cache/apt/archives/gmt-common_5.1.2+dfsg1-1~exp4_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/gmt.1.gz', which is also in package libgenome-perl 0.06-2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Selecting previously unselected package gmt. Preparing to unpack .../gmt_5.1.2+dfsg1-1~exp4_amd64.deb ... Unpacking gmt (5.1.2+dfsg1-1~exp4) ... dpkg: error processing archive /var/cache/apt/archives/gmt_5.1.2+dfsg1-1~exp4_amd64.deb (--unpack): trying to overwrite '/usr/bin/gmt', which is also in package libgenome-perl 0.06-2 Errors were encountered while processing: /var/cache/apt/archives/gmt-common_5.1.2+dfsg1-1~exp4_all.deb /var/cache/apt/archives/gmt_5.1.2+dfsg1-1~exp4_amd64.deb cheers, Andreas libgenome-perl=0.06-2_gmt=5.1.2+dfsg1-1~exp4.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: gmt Source-Version: 5.1.2+dfsg1-1~exp8 We believe that the bug you reported is fixed in the latest version of gmt, 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 790...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bas Couwenberg sebas...@debian.org (supplier of updated gmt 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: Fri, 10 Jul 2015 16:33:55 +0200 Source: gmt Binary: gmt gmt-common libgmt5 libgmt-dev gmt-dbg gmt-doc-pdf gmt-doc gmt-examples Architecture: source all amd64 Version: 5.1.2+dfsg1-1~exp8 Distribution: experimental Urgency: medium Maintainer: Debian GIS Project pkg-grass-de...@lists.alioth.debian.org Changed-By: Bas Couwenberg sebas...@debian.org Description: gmt- Generic Mapping Tools gmt-common - Generic Mapping Tools - Architecture-independent files gmt-dbg- Generic Mapping Tools Library - Debugging symbols gmt-doc- HTML documentation for GMT, the Generic Mapping Tools gmt-doc-pdf - PDF docs for GMT, the Generic Mapping Tools gmt-examples - Example scripts illustrating the use of GMT libgmt-dev - Generic Mapping Tools Library - Development files libgmt5- Generic Mapping Tools Library Closes: 790524 Changes: gmt (5.1.2+dfsg1-1~exp8) experimental; urgency=medium . * Drop Conflicts on turnin-ng pslib-dev, gmt man pages use 'gmt' suffix now. * Add Breaks/Replaces on old gmt-manpages to gmt-common. (closes: #790524) * Drop obsolete README.Debian file. Checksums-Sha1: 5861e66db10f5d039a1c6893a998736925334dc5 2536 gmt_5.1.2+dfsg1-1~exp8.dsc dea3cb8be9b2f4c0f8c446f106b53655c7baa673 39140 gmt_5.1.2+dfsg1-1~exp8.debian.tar.xz 1e335debc529ae335ee7b25d8756f69ed5d2da6a 4438902 gmt-common_5.1.2+dfsg1-1~exp8_all.deb f593ba45fee0b158c7d7877080662ed3dfd515d2 4484666 gmt-dbg_5.1.2+dfsg1-1~exp8_amd64.deb cbe20f381d2563c4bca7dd1bcde94167be7da588 22693946 gmt-doc-pdf_5.1.2+dfsg1-1~exp8_all.deb 72623693bc53131d00c8fc40953d6f8faf1080e0 31550494
Bug#791865: marked as done (kactivities-kf5 FTBFS on armel, symbols files issues.)
Your message dated Fri, 10 Jul 2015 12:04:59 + with message-id e1zdx35-i3...@franck.debian.org and subject line Bug#791865: fixed in kactivities-kf5 5.12.0-1 has caused the Debian Bug report #791865, regarding kactivities-kf5 FTBFS on armel, symbols files issues. 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.) -- 791865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kactivities-kf5 Version: 5.11.0-1 Severity: serious Your package fails to build on armel with a symbols file error. dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libkf5activities5/DEBIAN/symbols doesn't match completely debian/libkf5activities5.symbols --- debian/libkf5activities5.symbols (libkf5activities5_5.11.0-1_armel) +++ dpkg-gensymbols53zPO5 2015-07-07 04:58:25.351194353 + @@ -88,21 +88,29 @@ _ZNK11KActivities8Consumer10metaObjectEv@Base 4.96.0 _ZNK11KActivities8Consumer15currentActivityEv@Base 4.96.0 (optional=templinst)_ZNKSt8functionIFvvEEclEv@Base 4.97.0 - (optional=templinst)_ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE10_M_destroyEv@Base 4.98.0 + _ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE10_M_destroyEv@Base 5.11.0-1 +#MISSING: 5.11.0-1# (optional=templinst)_ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE10_M_destroyEv@Base 4.98.0 _ZTIN11KActivities10ControllerE@Base 4.96.0 _ZTIN11KActivities16ResourceInstanceE@Base 4.96.0 _ZTIN11KActivities4InfoE@Base 4.96.0 _ZTIN11KActivities8ConsumerE@Base 4.96.0 - _ZTISt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 4.98.0 - _ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 4.98.0 + _ZTIN9__gnu_cxx7__mutexE@Base 5.11.0-1 + _ZTISt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 5.11.0-1 +#MISSING: 5.11.0-1# _ZTISt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 4.98.0 + _ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 5.11.0-1 +#MISSING: 5.11.0-1# _ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 4.98.0 _ZTSN11KActivities10ControllerE@Base 4.96.0 _ZTSN11KActivities16ResourceInstanceE@Base 4.96.0 _ZTSN11KActivities4InfoE@Base 4.96.0 _ZTSN11KActivities8ConsumerE@Base 4.96.0 - _ZTSSt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 4.98.0 - _ZTSSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 4.98.0 + _ZTSN9__gnu_cxx7__mutexE@Base 5.11.0-1 + _ZTSSt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 5.11.0-1 +#MISSING: 5.11.0-1# _ZTSSt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 4.98.0 + _ZTSSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 5.11.0-1 +#MISSING: 5.11.0-1# _ZTSSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 4.98.0 _ZTVN11KActivities10ControllerE@Base 4.96.0 _ZTVN11KActivities16ResourceInstanceE@Base 4.96.0 _ZTVN11KActivities4InfoE@Base 4.96.0 _ZTVN11KActivities8ConsumerE@Base 4.96.0 - _ZTVSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 4.98.0 + _ZTVSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 5.11.0-1 +#MISSING: 5.11.0-1# _ZTVSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 4.98.0 dh_makeshlibs: failing due to earlier errors I imagine this should be a fairly easy fix. While kactivities-kf5 has never been built on armel kdeplasma-addons has and now build-depends (indirectly) on this package. ---End Message--- ---BeginMessage--- Source: kactivities-kf5 Source-Version: 5.12.0-1 We believe that the bug you reported is fixed in the latest version of kactivities-kf5, 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 791...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Maximiliano Curia m...@debian.org (supplier of updated kactivities-kf5 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, 09 Jul 2015 12:44:12 +0200 Source: kactivities-kf5 Binary: libkf5activities-dev libkf5activities5 kactivities libkf5activities5-dbg qml-module-org-kde-extensionplugin Architecture: source amd64 Version: 5.12.0-1 Distribution: unstable Urgency: medium
Processed: Re: librcsb-core-wrapper: ftbfs with GCC-5
Processing control commands: tags -1 + patch pending Bug #777971 [src:librcsb-core-wrapper] librcsb-core-wrapper: ftbfs with GCC-5 Added tag(s) patch and pending. -- 777971: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777971 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: fix GCC version detection
Processing control commands: tags -1 + patch pending Bug #778033 [src:ocp] ocp: ftbfs with GCC-5 Added tag(s) pending and patch. -- 778033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778033 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#778033: fix GCC version detection
Control: tags -1 + patch pending attaching patch, and uploading to delayed. diff -Nru ocp-0.1.21/debian/changelog ocp-0.1.21/debian/changelog --- ocp-0.1.21/debian/changelog 2012-09-16 17:21:01.0 +0200 +++ ocp-0.1.21/debian/changelog 2015-07-10 14:20:39.0 +0200 @@ -1,3 +1,11 @@ +ocp (1:0.1.21-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fix GCC version detection. Closes: #778033. + * Build using dh-autoreconf. Closes: #744480. + + -- Matthias Klose d...@debian.org Fri, 10 Jul 2015 14:07:58 +0200 + ocp (1:0.1.21-1.1) unstable; urgency=low * Non-maintainer upload. diff -Nru ocp-0.1.21/debian/control ocp-0.1.21/debian/control --- ocp-0.1.21/debian/control 2011-12-01 09:52:43.0 +0100 +++ ocp-0.1.21/debian/control 2015-07-10 14:14:25.0 +0200 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Gürkan Sengün gur...@phys.ethz.ch Uploaders: Debian Multimedia Team debian-multime...@lists.debian.org -Build-Depends: debhelper (= 8), libmad0-dev, libid3tag0-dev, zlib1g-dev, libncurses5-dev, libogg-dev, libvorbis-dev, libsidplay1-dev, libx11-dev, libxext-dev, texi2html, libxxf86dga-dev, libxxf86vm-dev, texinfo, libbinio-dev, libadplug-dev (= 2.0.1-2), libflac-dev, libxpm-dev, libasound2-dev, desktop-file-utils, dpkg (= 1.15.4) | install-info +Build-Depends: debhelper (= 8), dh-autoreconf, libmad0-dev, libid3tag0-dev, zlib1g-dev, libncurses5-dev, libogg-dev, libvorbis-dev, libsidplay1-dev, libx11-dev, libxext-dev, texi2html, libxxf86dga-dev, libxxf86vm-dev, texinfo, libbinio-dev, libadplug-dev (= 2.0.1-2), libflac-dev, libxpm-dev, libasound2-dev, desktop-file-utils, dpkg (= 1.15.4) | install-info Standards-Version: 3.9.2 Homepage: http://stian.cubic.org/project-ocp.php diff -Nru ocp-0.1.21/debian/patches/gccver.diff ocp-0.1.21/debian/patches/gccver.diff --- ocp-0.1.21/debian/patches/gccver.diff 1970-01-01 01:00:00.0 +0100 +++ ocp-0.1.21/debian/patches/gccver.diff 2015-07-10 14:25:25.0 +0200 @@ -0,0 +1,13 @@ +Index: b/configure.ac +=== +--- a/configure.ac b/configure.ac +@@ -117,7 +117,7 @@ else + '') + AC_MSG_ERROR([not found]); + ;; +- 2.95.[[2-9]]|2.95.[[2-9]][[-.]]*|3.[[0-9]]|3.[[0-9]].[[0-9]]|3.[[0-9]]|3.[[0-9]].[[0-9]]-*|4.*) ++ 2.95.[[2-9]]|2.95.[[2-9]][[-.]]*|3.[[0-9]]|3.[[0-9]].[[0-9]]|3.[[0-9]]|3.[[0-9]].[[0-9]]-*|[[4-9]].*) + _cc_major=`echo $cc_version | cut -d '.' -f 1` + _cc_minor=`echo $cc_version | cut -d '.' -f 2` + _cc_mini=`echo $cc_version | cut -d '.' -f 3` diff -Nru ocp-0.1.21/debian/patches/series ocp-0.1.21/debian/patches/series --- ocp-0.1.21/debian/patches/series2012-09-16 17:15:01.0 +0200 +++ ocp-0.1.21/debian/patches/series2015-07-10 14:20:09.0 +0200 @@ -1,3 +1,4 @@ info-compression fix-desktop-file fix-gcc47-pcthunk +gccver.diff diff -Nru ocp-0.1.21/debian/rules ocp-0.1.21/debian/rules --- ocp-0.1.21/debian/rules 2011-12-01 10:07:16.0 +0100 +++ ocp-0.1.21/debian/rules 2015-07-10 14:23:46.0 +0200 @@ -11,9 +11,9 @@ CFLAGS += -O2 endif -configure: configure-stamp configure-stamp: dh_testdir + AUTOMAKE=true LIBTOOLIZE=true AUTOHEADER=true dh_autoreconf CFLAGS=$(CFLAGS) CXXFLAGS=$(CXXFLAGS) ./configure --host=$(DEB_HOST_GNU_TYPE) \ --build=$(DEB_BUILD_GNU_TYPE) \ --prefix=/usr \ @@ -43,6 +43,7 @@ rm -f build-stamp configure-stamp [ ! -f Makefile ] || $(MAKE) clean distclean rm -f config.log config.status + dh_autoreconf_clean dh_clean install: build
Processed: Adding tag patch
Processing commands for cont...@bugs.debian.org: tags 734385 patch Bug #734385 [cardstories] cardstories: Package installation fails if /etc/apache2/conf.d does not exist Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 734385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734385 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#790561: After upgrading udev from 215-18 to 220-7 or 221-1, the system is unbootable afterwards
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, Am Mo den 6. Jul 2015 um 20:26 schrieb Martin Pitt: Klaus Ethgen [2015-07-05 1:34 +0100]: Well, it clearly shows that it probes some unexisting USB stuff. It's a shot into the dark, but this makes me wonder if this is another fallout of enabling USB auto-suspend? Can you please try and move away /lib/udev/rules.d/42-usb-hid-pm.rules (rename it to *.rules.disabled or so), reboot, and see if that improves things? With version 222-1 there is no /lib/udev/rules.d/42-usb-hid-pm.rules anymore. However, I gave it a try but the bug is not gone. After SCSI detection it takes ~100 seconds to finish USB HID detection. That is ten times more than with udev 215-18. So the system is not unbootable anymore but painful slow booting. I went back to 215-18 again and the system boots as usually. Gruß Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen kl...@ethgen.de Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQGcBAEBCgAGBQJVn9mYAAoJEKZ8CrGAGfas3mIL/jXZCXxdYJaodpCDTIcltvt3 s0CKxocUJ856SJcsDPVL0UO+4jHkyPJw+IQt5b13tuwTD35K0O03Xyk5BgjNMYVh sUhXhPSVjVd0YIwhHuKYLpDY7ldN7Vyi1lrBJtKz90mO+yfemtUFuZKv0IItfR3k S7TnzEzhItjY4Md1be7enkvWe38e6YXxyWDDiMTwGifpW3lmJSrGk6EU/JsKlG3g 8rWmp41mb/eWKe4PntfLIHgWb8E71P9EdmM2DOYhU2e+Ci6nHWPVsUm3d4qS3t0W M/EMtlpD8TG3EmtNva3rPLiWrxpABaZVKd99zEnxezSxHIQXCAUqDwYo/jzp6lem j/vkXPJuoxniU8GbF9dW1MeuaAsx2troxTa2IbAzkI8G/kb++nvB2waceyM9SfOZ fIGRH2snMCx0ZHOc7n0D8QSk68rC8vTMi7u+Kc2l3pi5UdDzqVjQSA9mwtOMdu8f kaU+4z9j4RLUz9SmEPm6Q8wsjP3qRR06J9a/rblS5Q== =J0QZ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790524: src:gmt: takes over files from several unrelated packages
On 07/10/2015 04:20 PM, Andreas Beckmann wrote: On 2015-07-09 23:25, Sebastiaan Couwenberg wrote: The GMT 4 packaging also appended 'gmt' to the man page sections, I've reintroduced this in the ~exp7 revision that was just uploaded. ACK. I think that should do. If you add some more B+R: Selecting previously unselected package gmt-common. Preparing to unpack .../gmt-common_5.1.2+dfsg1-1~exp7_all.deb ... Unpacking gmt-common (5.1.2+dfsg1-1~exp7) ... dpkg: error processing archive /var/cache/apt/archives/gmt-common_5.1.2+dfsg1-1~exp7_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/psimage.1gmt.gz', which is also in package gmt-manpages 3.4.4-1 Errors were encountered while processing: /var/cache/apt/archives/gmt-common_5.1.2+dfsg1-1~exp7_all.deb gmt-manpages can probably be RM'ed from unstable. The auto decruft should take of that when the gmt packages are uploaded to unstable IIRC. I've just uploaded ~exp8 that fixes the conflict with the gmt suffixed man pages. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778133: sword: ftbfs with GCC-5
Control: tags -1 + pending patch attaching a patch, uploading to delayed diff -Nru sword-1.7.3+dfsg/debian/changelog sword-1.7.3+dfsg/debian/changelog --- sword-1.7.3+dfsg/debian/changelog 2014-07-16 02:27:30.0 +0200 +++ sword-1.7.3+dfsg/debian/changelog 2015-07-10 16:23:52.0 +0200 @@ -1,3 +1,10 @@ +sword (1.7.3+dfsg-2.1) unstable; urgency=medium + + * Non maintainer upload. + * Fix build with GCC 5 (-Wno-error=deprecated-declarations). Closes: #778133. + + -- Matthias Klose d...@debian.org Fri, 10 Jul 2015 16:18:02 +0200 + sword (1.7.3+dfsg-2) unstable; urgency=medium * Add missing license in debian/copyright. (Closes: 754869) diff -Nru sword-1.7.3+dfsg/debian/rules sword-1.7.3+dfsg/debian/rules --- sword-1.7.3+dfsg/debian/rules 2014-07-15 20:01:30.0 +0200 +++ sword-1.7.3+dfsg/debian/rules 2015-07-10 16:19:30.0 +0200 @@ -4,7 +4,7 @@ ver:=$(shell dpkg-parsechangelog | sed -nr 2s/Version: (.*)-.*/\1/p) bd :=$(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) -WFLAGS := -Wall -Werror +WFLAGS := -Wall -Werror -Wno-error=deprecated-declarations CFLAGS= $(shell dpkg-buildflags --get CFLAGS) $(WFLAGS) CXXFLAGS = $(shell dpkg-buildflags --get CXXFLAGS) $(WFLAGS)
Bug#778155: undertaker: ftbfs with GCC-5
Control: tags -1 + patch pending Build with -fpermissive as a work around, uploading to delayed. diff -Nru undertaker-1.6/debian/changelog undertaker-1.6/debian/changelog --- undertaker-1.6/debian/changelog 2014-11-12 05:07:57.0 +0100 +++ undertaker-1.6/debian/changelog 2015-07-10 16:31:38.0 +0200 @@ -1,3 +1,11 @@ +undertaker (1.6-2.1) unstable; urgency=medium + + * Non maintainer upload. + * Build with -fpermissive to work around build failure with GCC 5. +Closes: #778155. + + -- Matthias Klose d...@debian.org Fri, 10 Jul 2015 16:30:53 +0200 + undertaker (1.6-2) unstable; urgency=medium * Use system picsoat = 960 (Closes: #766273) diff -Nru undertaker-1.6/debian/patches/gcc5.diff undertaker-1.6/debian/patches/gcc5.diff --- undertaker-1.6/debian/patches/gcc5.diff 1970-01-01 01:00:00.0 +0100 +++ undertaker-1.6/debian/patches/gcc5.diff 2015-07-10 16:39:19.0 +0200 @@ -0,0 +1,13 @@ +Index: b/undertaker/Makefile +=== +--- a/undertaker/Makefile b/undertaker/Makefile +@@ -6,7 +6,7 @@ NODEPS:=clean clean-check clean-parsers + + CFLAGS = -Wall -Wextra -O2 + CPPFLAGS = -I $(CURDIR)/../scripts/kconfig -I $(CURDIR)/../picosat +-CXXFLAGS = $(CFLAGS) -std=gnu++11 ++CXXFLAGS = $(CFLAGS) -std=gnu++11 -fpermissive + + # use g++ for linking, will automaticly use -lstdc++ -lm libraries + CC = g++ diff -Nru undertaker-1.6/debian/patches/series undertaker-1.6/debian/patches/series --- undertaker-1.6/debian/patches/series2014-11-12 05:04:47.0 +0100 +++ undertaker-1.6/debian/patches/series2015-07-10 16:34:16.0 +0200 @@ -1,2 +1,3 @@ update_picomus.patch undertaker-checkpatch-fix-Kconfig-parsing.patch +gcc5.diff
Processed: Re: undertaker: ftbfs with GCC-5
Processing control commands: tags -1 + patch pending Bug #778155 [src:undertaker] undertaker: ftbfs with GCC-5 Added tag(s) pending and patch. -- 778155: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778155 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#792033: qtbase-opensource-src: Gold linker breaks build on sparc
Source: qtbase-opensource-src Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, The qtbase-opensource-src build is currently broken on sparc. While investigating the bug describing this breakage, #773590, I found that the actual code generated by gcc-4.9 is fine but the linker is incorrectly arranging sting literal function arguments resulting in garbage values being passed to functions. The result is that moc doesn't produce any output files and doesn't print correct diagnostic messages. It appears to be specifically the gold linker that the ./configure script selects by default that has the problem. If the bfd linker is selected instead the build completes normally and the packages generated work in my testing. I'm working on a minimal testcase to report the gold bug but until this is fixed it can be worked around by disabling gold on sparc at configure time. This patch is one way this could be done, it fixes the build on my sparc system. --- qtbase-opensource-src-5.4.2+dfsg/debian/rules +++ qtbase-opensource-src-5.4.2+dfsg/debian/rules @@ -55,6 +55,11 @@ extra_configure_opts += -opengl desktop endif +no_gold_architectures := sparc +ifeq ($(DEB_HOST_ARCH),$(findstring $(DEB_HOST_ARCH), $(no_gold_architectures))) +extra_configure_opts += -no-use-gold-linker +endif + ifneq ($(DEB_HOST_ARCH_OS),linux) extra_configure_opts += -no-eglfs endif -- System Information: Debian Release: stretch/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: sparc (sparc64) Foreign Architectures: sparc64 Kernel: Linux 4.1.0-201506221440 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791964: gdm3: upgrade causes X session to be terminated
[keeping pkg-systemd into the loop here] Am 10.07.2015 um 14:37 schrieb Michael Biebl: I suggest we follow up on this bug report. I'm not yet quite sure, if this is a gdm or systemd bug and whether the best course of action is to simply re-introduce the workaround patch and drop that in stretch+1 or if we drop the reload from gdm3.postinst or if this indeed another corner case which is not handled properly in systemd. Joss, bigon: looking at gdm3.postinst, I wonder why we do run invoke-rc.d gdm3 reload. Isn't that potentially dangerous, say we have a major new gdm3 upgrade with incompatible configuration and we tell the old, running gdm3 to reload this new configuration? Wouldn't we rather want a full-restart once all user sessions are closed? I'm not sure if gdm3 (still) supports that. As for the systemd specific part, I made an interesting observation, which might be related to the problem. Say you have gdm-3.14-7 runnig which has BusName *not* set. systemctl show gdm3.service -p BusName -p Type will return Type=simple (as expected). Merely changing the gdm3.service file on disk, and running systemctl daemon-reload *without* actually restarting gdm3, will now yield Type=dbus BusName=org.gnome.DisplayManager I find this behaviour unexpected and strange, i.e. changing the Type of a running job. -- 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: sword: ftbfs with GCC-5
Processing control commands: tags -1 + pending patch Bug #778133 [src:sword] sword: ftbfs with GCC-5 Added tag(s) patch and pending. -- 778133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778133 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: nsis: ftbfs with GCC-5
Processing control commands: tags -1 + patch pending Bug #778029 [src:nsis] nsis: ftbfs with GCC-5 Added tag(s) patch and pending. -- 778029: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778029 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#778029: nsis: ftbfs with GCC-5
Control: tags -1 + patch pending still failed to build for me. patch attached, uplodaing to delayed diff -Nru nsis-2.46/debian/changelog nsis-2.46/debian/changelog --- nsis-2.46/debian/changelog 2014-12-15 22:58:07.0 +0100 +++ nsis-2.46/debian/changelog 2015-07-10 14:00:30.0 +0200 @@ -1,3 +1,10 @@ +nsis (2.46-10.1) unstable; urgency=medium + + * Non-maintainer upload. + * Build with -fgnu89-inline. Closes: #778029. + + -- Matthias Klose d...@debian.org Fri, 10 Jul 2015 13:59:55 +0200 + nsis (2.46-10) unstable; urgency=medium * Fail the build if libwinpthread is needed at runtime (see #722898) diff -Nru nsis-2.46/debian/rules nsis-2.46/debian/rules --- nsis-2.46/debian/rules 2014-12-16 09:02:54.0 +0100 +++ nsis-2.46/debian/rules 2015-07-10 13:59:46.0 +0200 @@ -31,7 +31,7 @@ # Honor hardening flags DPKG_EXPORT_BUILDFLAGS = 1 include /usr/share/dpkg/buildflags.mk -SCONSHOSTFLAGS = APPEND_CCFLAGS=$(CFLAGS) $(CPPFLAGS) \ +SCONSHOSTFLAGS = APPEND_CCFLAGS=-fgnu89-inline $(CFLAGS) $(CPPFLAGS) \ APPEND_LINKFLAGS=$(LDFLAGS) SCONSOPTS = $(SCONSFLAGS) VERSION=$(VERSION) \
Bug#792021: marked as done (libmaven3-core-java: not installable in sid - libeclipse-aether-java (= 1.0) does not exist)
Your message dated Fri, 10 Jul 2015 11:38:48 -0300
with message-id 20150710143848.ga19...@alice.nomadium.lan
and subject line Re: libmaven3-core-java: not installable in sid -
libeclipse-aether-java (= 1.0) does not exist
has caused the Debian Bug report #792021,
regarding libmaven3-core-java: not installable in sid - libeclipse-aether-java
(= 1.0) does not exist
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.)
--
792021: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libmaven3-core-java
Version: 3.3.3-1
Severity: grave
Hi,
maven and libmaven3-core-java can no longer be installed in sid because
the dependency on libeclipse-aether-java cannot be satisfied.
$ sudo aptitude install maven
The following NEW packages will be installed:
libguice-java{a} libmaven3-core-java{ab} libsisu-inject-java{a}
libsisu-plexus-java{a}
The following packages will be upgraded:
maven
1 packages upgraded, 4 newly installed, 0 to remove and 1 not upgraded.
Need to get 2,541 kB of archives. After unpacking 1,734 kB will be used.
The following packages have unmet dependencies:
libmaven3-core-java : Depends: libeclipse-aether-java (= 1.0) but it is not
going to be installed.
$ rmadison -sunstable libeclipse-aether-java
libeclipse-aether-java | 0.9.0.M2-1| unstable | all
Thanks,
James
signature.asc
Description: This is a digitally signed message part
---End Message---
---BeginMessage---
On Fri, Jul 10, 2015 at 11:38:31AM +0100, James Cowgill wrote:
Package: libmaven3-core-java
Version: 3.3.3-1
Severity: grave
Hi,
maven and libmaven3-core-java can no longer be installed in sid because
the dependency on libeclipse-aether-java cannot be satisfied.
eclipse-aether 1.0.2-1 was accepted in sid two hours ago, so this bug
should be fixed today when it reaches the mirrors.
--
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
---End Message---
Processed: Re: xracer: ftbfs with GCC-5
Processing commands for cont...@bugs.debian.org: tags 778189 + patch Bug #778189 [src:xracer] xracer: ftbfs with GCC-5 Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 778189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778189 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#778189: xracer: ftbfs with GCC-5
tags 778189 + patch
thanks
I made a patch to fix this.
Might not be good but just fix it in experimental.
As attachment.
--
PaulLiu (劉穎駿)
E-mail: Ying-Chun Liu (PaulLiu) paul...@debian.org
Description: Fix FTBFS on gcc-5
The gcc-5 (C99) has different definition of extern inline.
This patch keep the inline function in header file.
And then export it in exactly one compilation unit (.c file).
Author: Ying-Chun Liu (PaulLiu) paul...@debian.org
Bug-Debian: http://bugs.debian.org/778189
Last-Update: 2015-07-10
Index: xracer-0.96.9.1/xracer-0.96.9/include/xracer-player.h
===
--- xracer-0.96.9.1.orig/xracer-0.96.9/include/xracer-player.h
+++ xracer-0.96.9.1/xracer-0.96.9/include/xracer-player.h
@@ -130,79 +130,64 @@ extern void xrPlayerEndGame (void);
extern void xrPlayerUpdate (const struct xrGameControls *controls);
/* Inline structure accessors. */
-extern int xrPlayerHasExternalShield (const struct xrPlayer *player);
-extern inline int
+inline int
xrPlayerHasExternalShield (const struct xrPlayer *player)
{
return player-has_external_shield;
}
-extern int xrPlayerHasAutoPilot (const struct xrPlayer *player);
-
-extern inline int
+inline int
xrPlayerHasAutoPilot (const struct xrPlayer *player)
{
return player-has_autopilot;
}
/* This always returns the position of the midpoint of the back line. */
-extern const GLfloat *xrPlayerGetPosition (const struct xrPlayer *player);
-extern inline const GLfloat *
+inline const GLfloat *
xrPlayerGetPosition (const struct xrPlayer *player)
{
return player-backline_midpoint;
}
-extern int xrPlayerGetSegment (const struct xrPlayer *player);
-
-extern inline int
+inline int
xrPlayerGetSegment (const struct xrPlayer *player)
{
return player-seg[0];
}
/* Return the eye position, accounting for OOBE, if necessary. */
-extern const GLfloat *xrPlayerGetCameraEye (const struct xrPlayer *player,
- int oobe);
-extern inline const GLfloat *
+inline const GLfloat *
xrPlayerGetCameraEye (const struct xrPlayer *player, int oobe)
{
return oobe ? player-eye_oobe : player-backline_midpoint;
}
/* Return the camera centre point, accounting for OOBE, if necessary. */
-extern const GLfloat *xrPlayerGetCameraCentre (const struct xrPlayer *player,
- int oobe);
-extern inline const GLfloat *
+inline const GLfloat *
xrPlayerGetCameraCentre (const struct xrPlayer *player, int oobe)
{
return oobe ? player-centre_oobe : player-posn[0];
}
/* Return the camera up vector (this is unaffected by OOBE). */
-extern const GLfloat *xrPlayerGetCameraUp (const struct xrPlayer *player);
-extern inline const GLfloat *
+inline const GLfloat *
xrPlayerGetCameraUp (const struct xrPlayer *player)
{
return player-up;
}
-extern int xrPlayerGetSpeed (const struct xrPlayer *player);
-
-extern inline int
+inline int
xrPlayerGetSpeed (const struct xrPlayer *player)
{
return xrMagnitude (player-momentum[0]) * 500.;
}
-extern int xrPlayerGetPowerup (const struct xrPlayer *player);
-
-extern inline int
+inline int
xrPlayerGetPowerup (const struct xrPlayer *player)
{
return player-powerup;
@@ -211,18 +196,16 @@ xrPlayerGetPowerup (const struct xrPlaye
/* Return the player's current lap, counting from 1. After the player has
* completed the game, this can return NR_LAPS + 1, so beware.
*/
-extern int xrPlayerGetCurrentLap (const struct xrPlayer *player);
-extern inline int
+inline int
xrPlayerGetCurrentLap (const struct xrPlayer *player)
{
return player-displayed_current_lap + 1;
}
/* Return the player's current lap time. */
-extern double xrPlayerGetCurrentLapTime (const struct xrPlayer *player);
-extern inline double
+inline double
xrPlayerGetCurrentLapTime (const struct xrPlayer *player)
{
return xrCurrentTime - player-start_of_lap_time;
@@ -232,9 +215,8 @@ xrPlayerGetCurrentLapTime (const struct
* Note: the LAP argument starts counting from 1, and must be = NR_LAPS.
* This function does not return the current lap time.
*/
-extern double xrPlayerGetLapTime (const struct xrPlayer *player, int lap);
-extern inline double
+inline double
xrPlayerGetLapTime (const struct xrPlayer *player, int lap)
{
lap--;
Index: xracer-0.96.9.1/xracer-0.96.9/include/xracer-player-external.h
===
--- /dev/null
+++ xracer-0.96.9.1/xracer-0.96.9/include/xracer-player-external.h
@@ -0,0 +1,19 @@
+#ifndef __xracer_player_external_001_h__
+#define __xracer_player_external_001_h__
+
+extern inline int xrPlayerHasExternalShield (const struct xrPlayer *player);
+extern inline int xrPlayerHasAutoPilot (const struct xrPlayer *player);
+extern inline const GLfloat *xrPlayerGetPosition (const struct xrPlayer *player);
+extern inline int xrPlayerGetSegment (const struct xrPlayer *player);
+extern inline const GLfloat *xrPlayerGetCameraEye (const struct
Bug#792052: gcc-python-plugin: FTBFS: python3-dbg: not found
Source: gcc-python-plugin Version: 0.14-1 Severity: serious Justification: fails to build from source Builds of gcc-python-plugin in minimal environments (notably, on the autobuilders) have been failing: make[1]: Entering directory '/«PKGBUILDDIR»/build-python3-dbg' Makefile:193: warning: overriding recipe for target 'autogenerated-casts.c' Makefile:190: warning: ignoring old recipe for target 'autogenerated-casts.c' python3-dbg generate-config-h.py -o autogenerated-config.h --gcc=gcc-5 --plugindir=/usr/lib/gcc/aarch64-linux-gnu/5/plugin /bin/sh: 1: python3-dbg: not found make[1]: *** [autogenerated-config.h] Error 127 Makefile:177: recipe for target 'autogenerated-config.h' failed make[1]: Leaving directory '/«PKGBUILDDIR»/build-python3-dbg' make: *** [build-stamp-python3-dbg] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 Please declare a build dependency on python3-dbg. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778040: marked as done (opal: ftbfs with GCC-5)
Your message dated Fri, 10 Jul 2015 19:41:33 +0200
with message-id 55a003cd.9050...@debian.org
and subject line builds with a ptlib built using GCC 5
has caused the Debian Bug report #778040,
regarding opal: 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.)
--
778040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:opal
Version: 3.10.10~dfsg2-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/opal_3.10.10~dfsg2-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
[...]
bindir='${exec_prefix}/bin'
build_alias='x86_64-linux-gnu'
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE}'
dvidir='${docdir}'
exec_prefix='NONE'
host_alias=''
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${prefix}/share/info'
libdir='${exec_prefix}/lib'
libexecdir='${prefix}/lib/opal'
localedir='${datarootdir}/locale'
localstatedir='/var'
mandir='${prefix}/share/man'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
subdirs=''
sysconfdir='/etc'
target_alias=''
## --- ##
## confdefs.h. ##
## --- ##
/* confdefs.h */
#define PACKAGE_NAME
#define PACKAGE_TARNAME
#define PACKAGE_VERSION
#define PACKAGE_STRING
#define PACKAGE_BUGREPORT
#define PACKAGE_URL
#define STDC_HEADERS 1
#define OPAL_MAJOR 3
#define OPAL_MINOR 10
#define OPAL_BUILD 10
#define OPAL_VERSION 3.10.10
configure: exit 255
debian/rules:22: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [build-arch] Error 2
debian/rules:18: recipe for target 'build-arch' failed
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
---End Message---
---BeginMessage---
builds with a ptlib built using GCC 5, closing the issue.---End Message---
Bug#792053: [pkg-go] Bug#792053: prometheus: FTBFS w/ test suite errors
Martín Ferrari tin...@tincho.org writes: This is pretty weird.. There are a few precision mismatches, but many instances of expected 1, got 0. I will get some 32 bit machine and take a look. Great, thanks. As I said, I suspect at least some of the errors are due to buildd quirks rather than architectural differences, so you might need to install sbuild and perhaps also adjust its configuration to match the autobuilders more closely. (I'm not familiar with the setup details myself, so I can't offer any specifics here, sorry.) Thanks for reporting! Thanks for following up right away! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fix ftbfs
Processing control commands: tags -1 + patch Bug #777888 [src:goplay] goplay: ftbfs with GCC-5 Ignoring request to alter tags of bug #777888 to the same tags previously set -- 777888: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777888 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#778067: marked as done (plee-the-bear: ftbfs with GCC-5)
Your message dated Fri, 10 Jul 2015 20:22:50 +0200
with message-id 55a00d7a.20...@debian.org
and subject line builds
has caused the Debian Bug report #778067,
regarding plee-the-bear: 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.)
--
778067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:plee-the-bear
Version: 0.6.0-3.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/plee-the-bear_0.6.0-3.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
[...]
from
/«PKGBUILDDIR»/plee-the-bear/src/ptb/throwable_item/code/throwable_items_container.cpp:29:
/usr/include/boost/signals2/detail/variadic_slot_invoker.hpp: In instantiation
of 'class
boost::signals2::detail::variadic_slot_invokerboost::signals2::detail::void_type,
const std::basic_stringchar, std::char_traitschar, std::allocatorchar
':
/usr/include/boost/signals2/detail/signal_template.hpp:238:24: required from
'boost::signals2::detail::signal_implR(Args ...), Combiner, Group,
GroupCompare, SlotFunction, ExtendedSlotFunction, Mutex::result_type
boost::signals2::detail::signal_implR(Args ...), Combiner, Group,
GroupCompare, SlotFunction, ExtendedSlotFunction, Mutex::operator()(Args ...)
[with Combiner = boost::signals2::optional_last_valuevoid; Group = int;
GroupCompare = std::lessint; SlotFunction = boost::functionvoid(const
std::basic_stringchar); ExtendedSlotFunction = boost::functionvoid(const
boost::signals2::connection, const std::basic_stringchar); Mutex =
boost::signals2::mutex; R = void; Args = {const std::basic_stringchar,
std::char_traitschar, std::allocatorchar };
boost::signals2::detail::signal_implR(Args ...), Combiner, Group,
GroupCompare, SlotFunction, ExtendedSlotFunction, Mutex::result_type = void]'
/usr/include/boost/signals2/detail/signal_template.hpp:695:25: required from
'boost::signals2::signalR(Args ...), Combiner, Group, GroupCompare,
SlotFunction, ExtendedSlotFunction, Mutex::result_type
boost::signals2::signalR(Args ...), Combiner, Group, GroupCompare,
SlotFunction, ExtendedSlotFunction, Mutex::operator()(Args ...) [with Combiner
= boost::signals2::optional_last_valuevoid; Group = int; GroupCompare =
std::lessint; SlotFunction = boost::functionvoid(const
std::basic_stringchar); ExtendedSlotFunction = boost::functionvoid(const
boost::signals2::connection, const std::basic_stringchar); Mutex =
boost::signals2::mutex; R = void; Args = {const std::basic_stringchar,
std::char_traitschar, std::allocatorchar };
boost::signals2::signalR(Args ...), Combiner, Group, GroupCompare,
SlotFunction, ExtendedSlotFunction, Mutex::result_type = void]'
/«PKGBUILDDIR»/plee-the-bear/src/ptb/throwable_item/code/throwable_items_container.cpp:72:45:
required from here
/usr/include/boost/signals2/detail/variadic_slot_invoker.hpp:103:9: error:
forming reference to reference type 'const std::basic_stringchar'
variadic_slot_invoker(Args ... args): _args(args...)
^
In file included from /usr/include/boost/signals2/variadic_signal.hpp:21:0,
from /usr/include/boost/signals2/signal.hpp:38,
from /usr/include/boost/signals2.hpp:19,
from
/«PKGBUILDDIR»/plee-the-bear/src/ptb/../ptb/throwable_item/throwable_items_container.hpp:35,
from
/«PKGBUILDDIR»/plee-the-bear/src/ptb/throwable_item/code/throwable_items_container.cpp:29:
Bug#792053: [pkg-go] Bug#792053: prometheus: FTBFS w/ test suite errors
Hi Aaron, On 10/07/15 19:26, Aaron M. Ucko wrote: Builds of prometheus on those architectures on which its build dependencies are available (so far just armel, armhf, and i386, aside from amd64) have been failing with assorted test suite errors: https://buildd.debian.org/status/logs.php?pkg=prometheusver=0.14.0%2Bds-1 Architectural differences might play a part here (all attempted builds were 32-bit), but I suspect buildd configuration quirks may also be relevant, so I've gone with a severity of serious. This is pretty weird.. There are a few precision mismatches, but many instances of expected 1, got 0. I will get some 32 bit machine and take a look. Thanks for reporting! -- Martín Ferrari (Tincho) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777894: marked as done (h323plus: ftbfs with GCC-5)
Your message dated Fri, 10 Jul 2015 19:23:53 +0200 with message-id 559fffa9.5010...@debian.org and subject line builds once ptlib is built using GCC 5 has caused the Debian Bug report #777894, regarding h323plus: 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.) -- 777894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:h323plus Version: 1.24.0~dfsg2-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/h323plus_1.24.0~dfsg2-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 [...] /usr/share/ptlib//make/common.mak:96: recipe for target '/«PKGBUILDDIR»/lib/obj/h225_2.o' failed In file included from /usr/include/ptlib/contain.h:42:0, from /usr/include/ptlib.h:56, from h245_3.cxx:7: /usr/include/ptlib/critsec.h:46:33: fatal error: bits/atomicity.h: No such file or directory compilation terminated. make[3]: *** [/«PKGBUILDDIR»/lib/obj/h245_1.o] Error 1 /usr/share/ptlib//make/common.mak:96: recipe for target '/«PKGBUILDDIR»/lib/obj/h245_1.o' failed compilation terminated. make[3]: *** [/«PKGBUILDDIR»/lib/obj/h225_1.o] Error 1 /usr/share/ptlib//make/common.mak:96: recipe for target '/«PKGBUILDDIR»/lib/obj/h225_1.o' failed In file included from /usr/include/ptlib/contain.h:42:0, from /usr/include/ptlib.h:56, from /«PKGBUILDDIR»/src/h350/h350_service.cxx:11: /usr/include/ptlib/critsec.h:46:33: fatal error: bits/atomicity.h: No such file or directory make[3]: *** [/«PKGBUILDDIR»/lib/obj/h248.o] Error 1 /usr/share/ptlib//make/common.mak:96: recipe for target '/«PKGBUILDDIR»/lib/obj/h248.o' failed compilation terminated. make[3]: *** [/«PKGBUILDDIR»/lib/obj/OID2.o] Error 1 /usr/share/ptlib//make/common.mak:96: recipe for target '/«PKGBUILDDIR»/lib/obj/OID2.o' failed compilation terminated. make[3]: *** [/«PKGBUILDDIR»/lib/obj/h350_service.o] Error 1 /usr/share/ptlib//make/common.mak:96: recipe for target '/«PKGBUILDDIR»/lib/obj/h350_service.o' failed In file included from /usr/include/ptlib/contain.h:42:0, from /usr/include/ptlib.h:56, from h245_2.cxx:7: /usr/include/ptlib/critsec.h:46:33: fatal error: bits/atomicity.h: No such file or directory compilation terminated. make[3]: *** [/«PKGBUILDDIR»/lib/obj/h245_3.o] Error 1 /usr/share/ptlib//make/common.mak:96: recipe for target '/«PKGBUILDDIR»/lib/obj/h245_3.o' failed In file included from /usr/include/ptlib/contain.h:42:0, from /usr/include/ptlib.h:56, from h235.cxx:11: /usr/include/ptlib/critsec.h:46:33: fatal error: bits/atomicity.h: No such file or directory make[3]: *** [/«PKGBUILDDIR»/lib/obj/h245_2.o] Error 1 /usr/share/ptlib//make/common.mak:96: recipe for target '/«PKGBUILDDIR»/lib/obj/h245_2.o' failed compilation terminated. make[3]: *** [/«PKGBUILDDIR»/lib/obj/h235.o] Error 1 /usr/share/ptlib//make/common.mak:96: recipe for target '/«PKGBUILDDIR»/lib/obj/h235.o' failed make[3]: Leaving directory '/«PKGBUILDDIR»/src' make[2]: *** [optshared] Error 2 /usr/share/ptlib//make/common.mak:292: recipe for target 'optshared' failed make[2]: Leaving directory '/«PKGBUILDDIR»/src' make[1]: *** [optshared] Error 2 Makefile:78: recipe for target 'optshared' failed make[1]: Leaving directory '/«PKGBUILDDIR»' dh_auto_build: make -j10 returned exit code 2 make: *** [build-arch] Error 2 debian/rules:15: recipe for
Bug#792053: prometheus: FTBFS w/ test suite errors
Source: prometheus Version: 0.14.0+ds-1 Severity: serious Justification: fails to build from source Builds of prometheus on those architectures on which its build dependencies are available (so far just armel, armhf, and i386, aside from amd64) have been failing with assorted test suite errors: https://buildd.debian.org/status/logs.php?pkg=prometheusver=0.14.0%2Bds-1 Architectural differences might play a part here (all attempted builds were 32-bit), but I suspect buildd configuration quirks may also be relevant, so I've gone with a severity of serious. Could you please take a look? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: openbabel ftbfs with GCC 5
Processing control commands: tags -1 + pending patch Bug #778044 [src:openbabel] openbabel: ftbfs with GCC-5 Added tag(s) pending and patch. -- 778044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778044 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#778044: openbabel ftbfs with GCC 5
Control: tags -1 + pending patch attaching a patch, and uploading to delayed. diff -Nru openbabel-2.3.2+dfsg/debian/changelog openbabel-2.3.2+dfsg/debian/changelog --- openbabel-2.3.2+dfsg/debian/changelog 2014-09-20 14:43:39.0 +0200 +++ openbabel-2.3.2+dfsg/debian/changelog 2015-07-10 17:36:25.0 +0200 @@ -1,3 +1,10 @@ +openbabel (2.3.2+dfsg-2.1) unstable; urgency=medium + + * Non maintainer upload. + * Fix building with GCC 5. Closes: #778044. + + -- Matthias Klose d...@debian.org Fri, 10 Jul 2015 17:35:33 +0200 + openbabel (2.3.2+dfsg-2) unstable; urgency=medium [ Daniel Leidert ] diff -Nru openbabel-2.3.2+dfsg/debian/patches/gcc5.diff openbabel-2.3.2+dfsg/debian/patches/gcc5.diff --- openbabel-2.3.2+dfsg/debian/patches/gcc5.diff 1970-01-01 01:00:00.0 +0100 +++ openbabel-2.3.2+dfsg/debian/patches/gcc5.diff 2015-07-10 17:35:04.0 +0200 @@ -0,0 +1,13 @@ +Index: b/include/openbabel/shared_ptr.h +=== +--- a/include/openbabel/shared_ptr.h b/include/openbabel/shared_ptr.h +@@ -21,7 +21,7 @@ GNU General Public License for more deta + #define shared_ptr boost::shared_ptr + #else + #include memory +- #if __GNUC__ == 4 // __GNUC_MINOR__ 3 removed at the suggestion of Konstantin Tokarev ++ #if __GNUC__ = 4 // __GNUC_MINOR__ 3 removed at the suggestion of Konstantin Tokarev + #include tr1/memory + #endif + using std::tr1::shared_ptr; diff -Nru openbabel-2.3.2+dfsg/debian/patches/series openbabel-2.3.2+dfsg/debian/patches/series --- openbabel-2.3.2+dfsg/debian/patches/series 2014-09-20 14:29:34.0 +0200 +++ openbabel-2.3.2+dfsg/debian/patches/series 2015-07-10 17:34:33.0 +0200 @@ -2,3 +2,4 @@ libinchi_static.patch fix_ftbfs.patch 715668_fix_babel_segfault.patch +gcc5.diff
Bug#791964: gdm3: upgrade causes X session to be terminated
On 2015-07-10 10:46, Michael Biebl wrote: Am 10.07.2015 um 18:38 schrieb Josh Triplett: On Fri, Jul 10, 2015 at 02:37:49PM +0200, Michael Biebl wrote: * Systemd has been fixed in v222 to no longer kill services on reload if BusName is set, so drop that part from 92_systemd_unit.patch. but that is EXACTLY what happened to me right now, in the middle of Right. Subsequent reloads of gdm3.service should no longer kill gdm3.service though. So this was indeed fixed in v222 but there seems to be a specific issue for the upgrade path. Once gdm3 has been restarted, a reload no longer causes it to be killed. Note, though, that it doesn't help for systemd to be upgraded first. Even if running the new systemd 222, upgrading gdm3 kills the active session. Well, that's exactly what I said, right? apt used this order on my system: 2015-07-09 12:05:33 status installed systemd:amd64 222-1 [...] 2015-07-09 12:05:46 status installed gdm3:amd64 3.14.2-1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769805: marked as done (ming: FTBFS on current sid: swf4compiler.tab.c:3535:7: error: lvalue required as left operand of assignment)
Your message dated Fri, 10 Jul 2015 17:54:22 +
with message-id 20150710175422.ga23...@chase.mapreri.org
and subject line Re: Bug#769805: ming: FTBFS on current sid:
swf4compiler.tab.c:3535:7: error: lvalue required as left operand of assignment
has caused the Debian Bug report #769805,
regarding ming: FTBFS on current sid: swf4compiler.tab.c:3535:7: error: lvalue
required as left operand of assignment
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.)
--
769805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: ming
Severity: serious
Hi,
I tried to test my fix for #752629, but couldn't build the package
with pbuilder in a sid chroot:
Making all in actioncompiler
make[4]: Entering directory '/tmp/buildd/ming-0.4.5/src/actioncompiler'
bison -y -p swf4 -b swf4compiler ./swf4compiler.y
bison -y --defines --debug -p swf4 -b swf4compiler ./swf4compiler.y
bison -y -p swf5 -b swf5compiler ./swf5compiler.y
bison -y --defines --debug -p swf5 -b swf5compiler ./swf5compiler.y
./swf4compiler.y: warning: 52 shift/reduce conflicts [-Wconflicts-sr]
./swf4compiler.y: warning: 42 reduce/reduce conflicts [-Wconflicts-rr]
./swf4compiler.y: warning: 52 shift/reduce conflicts [-Wconflicts-sr]
./swf4compiler.y: warning: 42 reduce/reduce conflicts [-Wconflicts-rr]
./swf4compiler.y:197.25-38: warning: rule useless in parser due to conflicts
[-Wother]
: /* empty */ { $$ = NULL; }
^^
./swf4compiler.y:701.11-705.29: warning: rule useless in parser due to
conflicts [-Wother]
| '-' NUMBER %prec NEGATE
./swf4compiler.y:197.25-38: warning: rule useless in parser due to conflicts
[-Wother]
: /* empty */ { $$ = NULL; }
^^
./swf4compiler.y:701.11-705.29: warning: rule useless in parser due to
conflicts [-Wother]
| '-' NUMBER %prec NEGATE
flex -Pswf4 ./swf4compiler.flex
flex -Pswf5 ./swf5compiler.flex
/usr/bin/make all-am
make[5]: Entering directory '/tmp/buildd/ming-0.4.5/src/actioncompiler'
CC assembler.lo
CC compile.lo
CC listaction.lo
CC compileaction.lo
CC swf4compiler.tab.lo
swf4compiler.tab.c: In function 'swf4parse':
swf4compiler.tab.c:3535:7: error: lvalue required as left operand of assignment
yyn = yyr1[yyn];
^
swf4compiler.tab.c:3535:18: error: expected ')' before ';' token
yyn = yyr1[yyn];
^
swf4compiler.tab.c:3736:1: error: expected expression before '}' token
}
^
swf4compiler.tab.c:1978:5: error: label 'yyerrlab' used but not defined
goto yyerrlab;
^
swf4compiler.tab.c:1902:5: error: label 'yyacceptlab' used but not defined
YYACCEPT;
^
swf4compiler.tab.c:1896:9: error: label 'yyabortlab' used but not defined
YYABORT;
^
swf4compiler.tab.c:1879:11: error: label 'yyexhaustedlab' used but not defined
goto yyexhaustedlab;
^
swf4compiler.tab.c:1806:12: warning: unused variable 'yymsg_alloc'
[-Wunused-variable]
YYSIZE_T yymsg_alloc = sizeof yymsgbuf;
^
swf4compiler.tab.c:1805:9: warning: unused variable 'yymsg' [-Wunused-variable]
char *yymsg = yymsgbuf;
^
swf4compiler.tab.c:1795:7: warning: unused variable 'yyresult'
[-Wunused-variable]
int yyresult;
^
./swf4compiler.y: At top level:
swf4compiler.tab.c:1607:1: warning: 'yysyntax_error' defined but not used
[-Wunused-function]
yysyntax_error (YYSIZE_T *yymsg_alloc, char **yymsg,
^
swf4compiler.tab.c:1739:1: warning: 'yydestruct' defined but not used
[-Wunused-function]
yydestruct (const char *yymsg, int yytype, YYSTYPE *yyvaluep, void *buffer)
^
swf4compiler.tab.c: In function 'swf4parse':
swf4compiler.tab.c:3736:1: warning: control reaches end of non-void function
[-Wreturn-type]
}
^
Makefile:444: recipe for target 'swf4compiler.tab.lo' failed
make[5]: *** [swf4compiler.tab.lo] Error 1
make[5]: *** Waiting for unfinished jobs
make[5]: Leaving directory '/tmp/buildd/ming-0.4.5/src/actioncompiler'
Makefile:365: recipe for target 'all' failed
make[4]: *** [all] Error 2
make[4]: Leaving directory '/tmp/buildd/ming-0.4.5/src/actioncompiler'
Makefile:709: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/tmp/buildd/ming-0.4.5/src'
Makefile:521: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/tmp/buildd/ming-0.4.5/src'
Makefile:503: recipe for target
Bug#791964: gdm3: upgrade causes X session to be terminated
Am 10.07.2015 um 19:11 schrieb Josh Triplett: On Fri, Jul 10, 2015 at 06:46:18PM +0200, Michael Biebl wrote: Am 10.07.2015 um 18:38 schrieb Josh Triplett: Note, though, that it doesn't help for systemd to be upgraded first. Even if running the new systemd 222, upgrading gdm3 kills the active session. Well, that's exactly what I said, right? You said seems to be a specific issue for the upgrade path, and I didn't know whether you meant the upgrade path for gdm3, systemd, or both. Just wanted to make sure. Ah, ok, I meant the gdm upgrade indeed. Yeah, probably a bit misleading when you get this email out-of-context. This was filed against gdm3 after all, specifically for gdm being upgraded. Michael -- 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
Bug#790524: src:gmt: takes over files from several unrelated packages
On 2015-07-10 16:40, Sebastiaan Couwenberg wrote: gmt-manpages can probably be RM'ed from unstable. The auto decruft should take of that when the gmt packages are uploaded to unstable IIRC. No, since gmt-manpages is a separate source package and you are not taking over the gmt-manpages binary package with src:gmt. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791964: gdm3: upgrade causes X session to be terminated
On Fri, Jul 10, 2015 at 06:46:18PM +0200, Michael Biebl wrote: Am 10.07.2015 um 18:38 schrieb Josh Triplett: On Fri, Jul 10, 2015 at 02:37:49PM +0200, Michael Biebl wrote: Control: severity -1 serious Am 09.07.2015 um 20:14 schrieb David Mohr: Package: gdm3 Version: 3.14.2-1 Severity: normal Dear Maintainer, the changelog reads: * Systemd has been fixed in v222 to no longer kill services on reload if BusName is set, so drop that part from 92_systemd_unit.patch. but that is EXACTLY what happened to me right now, in the middle of Right. Subsequent reloads of gdm3.service should no longer kill gdm3.service though. So this was indeed fixed in v222 but there seems to be a specific issue for the upgrade path. Once gdm3 has been restarted, a reload no longer causes it to be killed. Note, though, that it doesn't help for systemd to be upgraded first. Even if running the new systemd 222, upgrading gdm3 kills the active session. Well, that's exactly what I said, right? You said seems to be a specific issue for the upgrade path, and I didn't know whether you meant the upgrade path for gdm3, systemd, or both. Just wanted to make sure. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792048: xdemorse: FTBFS: ***Error***: You must have automake = 1.9 installed
Package: xdemorse
Version: 2.9-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
The package depends on automake, but it checks up to automake 1.14, while now
the default is 1.15.
Please either expand the check or build-depend on a fixed automake version (the
former is slightly preferred).
Build log tail:
dh_autoreconf /tmp/buildd/xdemorse-2.9/autogen.sh
find ! -ipath ./debian/* -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f -exec
md5sum {} \; debian/autoreconf.before
/tmp/buildd/xdemorse-2.9/autogen.sh
checking for autoconf = 2.53...
testing autoconf2.50... not found.
testing autoconf... found 2.69
checking for automake = 1.9...
testing automake-1.14... not found.
testing automake-1.13... not found.
testing automake-1.12... not found.
testing automake-1.11... not found.
testing automake-1.10... not found.
testing automake-1.9... not found.
***Error***: You must have automake = 1.9 installed
to build Package. Download the appropriate package for
from your distribution or get the source tarball at
http://ftp.gnu.org/pub/gnu/automake/automake-1.9.tar.gz
find ! -ipath ./debian/* -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f -exec
md5sum {} \; debian/autoreconf.after
dh_autoreconf: /tmp/buildd/xdemorse-2.9/autogen.sh returned exit code 1
debian/rules:10: recipe for target 'override_dh_autoreconf' failed
make[1]: *** [override_dh_autoreconf] Error 2
make[1]: Leaving directory '/tmp/buildd/xdemorse-2.9'
debian/rules:7: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
E: Failed autobuilding of package
You can see a full build log at
https://reproducible.debian.net/rb-pkg/unstable/amd64/xdemorse.html
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: Digital signature
Processed: severity of 792033 is important
Processing commands for cont...@bugs.debian.org: severity 792033 important Bug #792033 [src:qtbase-opensource-src] qtbase-opensource-src: Gold linker breaks build on sparc Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 792033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792033 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#791964: gdm3: upgrade causes X session to be terminated
On Fri, Jul 10, 2015 at 02:37:49PM +0200, Michael Biebl wrote: Control: severity -1 serious Am 09.07.2015 um 20:14 schrieb David Mohr: Package: gdm3 Version: 3.14.2-1 Severity: normal Dear Maintainer, the changelog reads: * Systemd has been fixed in v222 to no longer kill services on reload if BusName is set, so drop that part from 92_systemd_unit.patch. but that is EXACTLY what happened to me right now, in the middle of Right. Subsequent reloads of gdm3.service should no longer kill gdm3.service though. So this was indeed fixed in v222 but there seems to be a specific issue for the upgrade path. Once gdm3 has been restarted, a reload no longer causes it to be killed. Note, though, that it doesn't help for systemd to be upgraded first. Even if running the new systemd 222, upgrading gdm3 kills the active session. I'm not yet quite sure, if this is a gdm or systemd bug and whether the best course of action is to simply re-introduce the workaround patch and drop that in stretch+1 or if we drop the reload from gdm3.postinst or if this indeed another corner case which is not handled properly in systemd. For a short-term fix, how about quickly re-introducing the gdm3 workaround? Then, we can experiment with possible ways to drop it and (more) carefully test the upgrade paths with packages that haven't been uploaded yet, and subsequently with experimental. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790524: src:gmt: takes over files from several unrelated packages
On 07/10/2015 06:30 PM, Andreas Beckmann wrote: On 2015-07-10 16:40, Sebastiaan Couwenberg wrote: gmt-manpages can probably be RM'ed from unstable. The auto decruft should take of that when the gmt packages are uploaded to unstable IIRC. No, since gmt-manpages is a separate source package and you are not taking over the gmt-manpages binary package with src:gmt. Right, I hadn't noticed that. Since GMT 4 the man pages are built from the gmt source package, so we could have removed the gmt-manpages package much sooner. I've requested its removal in #792043. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791964: gdm3: upgrade causes X session to be terminated
Am 10.07.2015 um 18:38 schrieb Josh Triplett: On Fri, Jul 10, 2015 at 02:37:49PM +0200, Michael Biebl wrote: Control: severity -1 serious Am 09.07.2015 um 20:14 schrieb David Mohr: Package: gdm3 Version: 3.14.2-1 Severity: normal Dear Maintainer, the changelog reads: * Systemd has been fixed in v222 to no longer kill services on reload if BusName is set, so drop that part from 92_systemd_unit.patch. but that is EXACTLY what happened to me right now, in the middle of Right. Subsequent reloads of gdm3.service should no longer kill gdm3.service though. So this was indeed fixed in v222 but there seems to be a specific issue for the upgrade path. Once gdm3 has been restarted, a reload no longer causes it to be killed. Note, though, that it doesn't help for systemd to be upgraded first. Even if running the new systemd 222, upgrading gdm3 kills the active session. Well, that's exactly what I said, right? -- 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
Bug#792002: lvm2-monitor service causes long delay at boot (encrypted root/swap)
On Fri, Jul 10, 2015 at 09:53:01AM +0200, Peter Rajnoha wrote: On 07/10/2015 01:48 AM, Josh Triplett wrote: Package: lvm2 Version: 2.02.122-1 Severity: grave File: /lib/systemd/system/lvm2-monitor.service On a laptop with encrypted root and swap, I now get a minutes-long delay at boot time, due to lvm2-monitor. Here's the complete set of messages at boot (transcribed from a photo of the screen): Loading, please wait... /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. Volume group data not found Cannot process volume group data Unable to find LVM volume data/root /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. Volume group data not found Cannot process volume group data Unable to find LVM volume data/swap Please unlock disk sda2_crypt: /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. Reading all physical volumes. This may take a while... Found volume group data using metadata type lvm2 /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. 2 logical volume(s) in volume group data now active cryptsetup: sda2_crypt set up successfully fsck from util-linux 2.26.2 /dev/mapper/data-root: clean, [...] [ ] A start job is running for Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling (59s / no limit) That last line matches the description in lvm2-monitor.service. (The preceeding lvm2 errors may or may not be related. The recurring two lines of lvmetad errors are new, as is the long delay on lvm2-monitor.service; the errors before unlocking the disk about not finding data/root and data/swap occurred with previous versions of lvm2.) If initrd is generated, the existing lvm.conf needs to be modified so the configuration is suitable for initrd environment (where I suppose lvmetad daemon is not running). So the script generating initrd needs to modify lvm.conf so that use_lvmetad=0 is used. In case lvmetad daemon is not running in initrd, which is, I suppose, exactly the case here - running lvmetad (the LVM metadata caching daemon) is not quite useful in initrd anyway as lvmetad would need to be started again after switching to root fs. So that's probably the first problem here. If those falling back to internal scanning messages appear even after switching to root fs, The above are the only such messages I see on each boot. please check if lvm2-lvmetad.socket is enabled (so it can instantiate lvm2-lvmetad.service on first socket access): systemctl status lvm2-lvmetad.socket It's active (running) on the booted system. If it's disabled then the distro needs to make sure it's always enabled so whenever use_lvmetad=1 is used, the lvm2-lvmetad.service can be instantiated automatically. Let's check these things first before debugging the lvm2-monitor.service delay... I just booted the system again, and the delay seems to have gone away. I don't know if that means it's non-deterministic, or if it only happens on the first boot after upgrade. If it's the latter, this is still a bug, but not an RC one. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777971: marked as done (librcsb-core-wrapper: ftbfs with GCC-5)
Your message dated Fri, 10 Jul 2015 17:04:11 + with message-id e1zdbid-0002xg...@franck.debian.org and subject line Bug#777971: fixed in librcsb-core-wrapper 1.005-4 has caused the Debian Bug report #777971, regarding librcsb-core-wrapper: 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.) -- 777971: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:librcsb-core-wrapper Version: 1.005-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/librcsb-core-wrapper_1.005-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 [...] make[3]: *** Waiting for unfinished jobs Makefile:156: recipe for target 'RcsbPlatform.o' failed libtool: compile: unrecognized option `-D_FORTIFY_SOURCE=2' libtool: compile: Try `libtool --help' for more information. make[3]: *** [CifString.o] Error 1 Makefile:156: recipe for target 'CifString.o' failed libtool: compile: unrecognized option `-D_FORTIFY_SOURCE=2' libtool: compile: unrecognized option `-D_FORTIFY_SOURCE=2' libtool: compile: unrecognized option `-D_FORTIFY_SOURCE=2' libtool: compile: Try `libtool --help' for more information. libtool: compile: unrecognized option `-D_FORTIFY_SOURCE=2' libtool: compile: Try `libtool --help' for more information. make[3]: *** [Serializer.o] Error 1 Makefile:156: recipe for target 'Serializer.o' failed libtool: compile: unrecognized option `-D_FORTIFY_SOURCE=2' libtool: compile: Try `libtool --help' for more information. make[3]: *** [DataInfo.o] Error 1 Makefile:156: recipe for target 'DataInfo.o' failed make[3]: *** [GenString.o] Error 1 Makefile:156: recipe for target 'GenString.o' failed libtool: compile: unrecognized option `-D_FORTIFY_SOURCE=2' libtool: compile: Try `libtool --help' for more information. make[3]: *** [Exceptions.o] Error 1 Makefile:156: recipe for target 'Exceptions.o' failed libtool: compile: unrecognized option `-D_FORTIFY_SOURCE=2' libtool: compile: Try `libtool --help' for more information. libtool: compile: Try `libtool --help' for more information. make[3]: *** [BlockIO.o] Error 1 make[3]: *** [mapped_vector.o] Error 1 libtool: compile: Try `libtool --help' for more information. Makefile:156: recipe for target 'BlockIO.o' failed Makefile:156: recipe for target 'mapped_vector.o' failed make[3]: *** [RcsbFile.o] Error 1 Makefile:156: recipe for target 'RcsbFile.o' failed libtool: compile: unrecognized option `-D_FORTIFY_SOURCE=2' libtool: compile: Try `libtool --help' for more information. make[3]: *** [GenCont.o] Error 1 Makefile:156: recipe for target 'GenCont.o' failed make[3]: Leaving directory '/«PKGBUILDDIR»/common' libtool: link: `lib/*.lo' is not a valid libtool object make[2]: *** [lib/librcsb-core-wrapper.la] Error 1 Makefile:107: recipe for target 'lib/librcsb-core-wrapper.la' failed make[2]: Leaving directory '/«PKGBUILDDIR»' dh_auto_build: make -j10 returned exit code 2 make[1]: *** [override_dh_auto_build-nopy] Error 2 debian/rules:19: recipe for target 'override_dh_auto_build-nopy' failed make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [build-arch] Error 2 debian/rules:14: recipe for target 'build-arch' failed dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ---End Message--- ---BeginMessage--- Source: librcsb-core-wrapper Source-Version: 1.005-4 We believe that the bug you reported is fixed in the latest version of librcsb-core-wrapper, which is due to be installed in the Debian FTP
Bug#789773: fusionforge-shell: modifies conffiles (policy 10.7.3): /etc/pam.d/sshd
Version: 6.0.2+20150708-1 Followup-For: Bug #789773 Hi Sylvain, attached is a piuparts logfile that demonstrates what will happen if fusionforge-shell is installed and the user upgrades openssh-server to a version that comes with an updated version of /etc/pam.d/sshd: 1m9.3s ERROR: Command failed (status=100): ['chroot', '/tmp/piupartss/tmpJ9G9Hg', 'apt-get', '-yf', 'dist-upgrade'] Reading package lists... Building dependency tree... Reading state information... The following packages will be upgraded: openssh-client openssh-server openssh-sftp-server debconf: delaying package configuration, since apt-utils is not installed 3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/1057 kB of archives. After this operation, 136 kB disk space will be freed. (Reading database ... 10209 files and directories currently installed.) Preparing to unpack .../openssh-sftp-server_6.7p1-6+foobar_amd64.deb ... Unpacking openssh-sftp-server (1:6.7p1-6+foobar) over (1:6.7p1-6) ... Preparing to unpack .../openssh-server_6.7p1-6+foobar_amd64.deb ... Unpacking openssh-server (1:6.7p1-6+foobar) over (1:6.7p1-6) ... Preparing to unpack .../openssh-client_6.7p1-6+foobar_amd64.deb ... Unpacking openssh-client (1:6.7p1-6+foobar) over (1:6.7p1-6) ... Processing triggers for systemd (222-1) ... Setting up openssh-client (1:6.7p1-6+foobar) ... Setting up openssh-sftp-server (1:6.7p1-6+foobar) ... Setting up openssh-server (1:6.7p1-6+foobar) ... Configuration file '/etc/pam.d/sshd' == Modified (by you or by a script) since installation. == Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** sshd (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package openssh-server (--configure): end of file on stdin at conffile prompt Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) That is exactly the prompting that must not happen if the conffile was not modified by the user. BTW, there is pam-auth-update. Could this be used to achieve the desired result? Andreas fusionforge-shell.log.gz Description: application/gzip
Bug#792058: python3-cobra: SyntaxError: invalid syntax (2.x-isms)
Package: python3-cobra Version: 0.4.0b1-1 Severity: grave Justification: renders package unusable (uninstallable) Byte compilation of python3-cobra is failing due to the presence of syntax that was only valid in Python 2.x: Setting up python3-cobra (0.4.0b1-1) ... File /usr/lib/python3/dist-packages/cobra/solvers/glpk_solver_java.py, line 86 except Exception, e1: ^ SyntaxError: invalid syntax File /usr/lib/python3/dist-packages/cobra/solvers/cplex_solver_java.py, line 318 print '%s failed: %s'%(solver_name, status) ^ SyntaxError: invalid syntax File /usr/lib/python3/dist-packages/cobra/solvers/gurobi_solver_java.py, line 73 except Exception, e: ^ SyntaxError: invalid syntax dpkg: error processing package python3-cobra (--configure): subprocess installed post-installation script returned error exit status 1 Could you please take a look? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778075: marked as done (python-demgengeo: ftbfs with GCC-5)
Your message dated Fri, 10 Jul 2015 19:33:52 + with message-id e1zde3u-00020z...@franck.debian.org and subject line Bug#778075: fixed in python-demgengeo 1.0-3 has caused the Debian Bug report #778075, regarding python-demgengeo: 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.) -- 778075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778075 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:python-demgengeo Version: 1.0-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/python-demgengeo_1.0-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 [...] checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking for shl_load... no checking for shl_load in -ldld... no checking for dlopen... no checking for dlopen in -ldl... yes checking whether a program can dlopen itself... yes checking whether a statically linked program can dlopen itself... no checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking how to run the C++ preprocessor... g++ -E checking for ld used by g++... /usr/bin/ld -m elf_x86_64 checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC -DPIC checking if g++ PIC flag -fPIC -DPIC works... yes checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking if g++ supports -c -o file.o... (cached) yes checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... (cached) GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking for epydoc... /usr/bin/epydoc configure: epydoc found. HTML documentation enabled. checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking whether gcc understands -c and -o together... (cached) yes checking dependency style of gcc... (cached) gcc3 checking whether we are using the GNU C++ compiler... (cached) yes checking whether g++ accepts -g... (cached) yes checking dependency style of g++... (cached) gcc3 checking for find... find checking for Py_Main in -lpython2.7... yes checking for Boost headers version = 1.34.1... yes checking for Boost's header version... configure: error: invalid value: boost_major_version= make[1]: *** [override_dh_auto_configure] Error 1 debian/rules:11: recipe for target 'override_dh_auto_configure' failed make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [build-arch] Error 2 debian/rules:8: recipe for target 'build-arch' failed dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ---End Message--- ---BeginMessage--- Source: python-demgengeo Source-Version: 1.0-3 We believe that the bug you reported is fixed in the latest version of
Bug#792071: FTBFS: most tests fail: from tuskarclient.v1 import overcloud_roles: ImportError: No module named v1
Source: tuskar-ui Version: 0.1.0-2 Severity: serious Justification: fails to build from source Dear Maintainer, The package's tests fail, mostly with the same error: + /usr/bin/python-coverage run -p /tmp/buildd/tuskar-ui-0.1.0/manage.py test tuskar_ui --settings=tuskar_ui.test.settings == ERROR: Create a FormsetDataTable and populate it with data. -- Traceback (most recent call last): File /tmp/buildd/tuskar-ui-0.1.0/tuskar_ui/test/helpers.py, line 53, in setUp test_data_utils.load_test_data(self) File /tmp/buildd/tuskar-ui-0.1.0/tuskar_ui/test/test_data/utils.py, line 26, in load_test_data from tuskar_ui.test.test_data import tuskar_data File /tmp/buildd/tuskar-ui-0.1.0/tuskar_ui/test/test_data/tuskar_data.py, line 23, in module from tuskarclient.v1 import overcloud_roles ImportError: No module named v1 == ERROR: Failure: ImportError (No module named v1) -- Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/nose/loader.py, line 420, in loadTestsFromName addr.filename, addr.module) File /usr/lib/python2.7/dist-packages/nose/importer.py, line 47, in importFromPath return self.importFromDir(dir_path, fqname) File /usr/lib/python2.7/dist-packages/nose/importer.py, line 94, in importFromDir mod = load_module(part_fqname, fh, filename, desc) File /tmp/buildd/tuskar-ui-0.1.0/tuskar_ui/api.py, line 26, in module from tuskarclient.v1 import client as tuskar_client ImportError: No module named v1 -- Ran 28 tests in 0.060s FAILED (errors=28) Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/tuskar-ui.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-22-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#791964: gdm3: upgrade causes X session to be terminated
Am 10.07.2015 um 18:38 schrieb Josh Triplett: On Fri, Jul 10, 2015 at 02:37:49PM +0200, Michael Biebl wrote: I'm not yet quite sure, if this is a gdm or systemd bug and whether the best course of action is to simply re-introduce the workaround patch and drop that in stretch+1 or if we drop the reload from gdm3.postinst or if this indeed another corner case which is not handled properly in systemd. For a short-term fix, how about quickly re-introducing the gdm3 workaround? Then, we can experiment with possible ways to drop it and (more) carefully test the upgrade paths with packages that haven't been uploaded yet, and subsequently with experimental. I won't be around till monday. If someone fills like this needs immediate action, please use your best judgement and proceed. Michael -- 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
