Bug#789661: marked as done (python3-grib: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man1/grib_repack.1.gz)
Your message dated Fri, 26 Jun 2015 06:18:50 + with message-id e1z8myq-0004js...@franck.debian.org and subject line Bug#789661: fixed in pygrib 2.0.0-3 has caused the Debian Bug report #789661, regarding python3-grib: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man1/grib_repack.1.gz 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.) -- 789661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789661 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python3-grib Version: 2.0.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 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package python3-grib. Preparing to unpack .../python3-grib_2.0.0-1_amd64.deb ... Unpacking python3-grib (2.0.0-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-grib_2.0.0-1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/grib_repack.1.gz', which is also in package python-grib-doc 1.9.9-2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/python3-grib_2.0.0-1_amd64.deb cheers, Andreas python-grib-doc=1.9.9-2_python3-grib=2.0.0-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: pygrib Source-Version: 2.0.0-3 We believe that the bug you reported is fixed in the latest version of pygrib, 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. Alastair McKinstry mckins...@debian.org (supplier of updated pygrib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 25 Jun 2015 16:53:32 +0100 Source: pygrib Binary: python-grib python3-grib python-grib-doc Architecture: source all amd64 Version: 2.0.0-3 Distribution: sid Urgency: medium Maintainer: Alastair McKinstry mckins...@debian.org Changed-By: Alastair McKinstry mckins...@debian.org Description: python-grib - Python module for reading and writing GRIB files python-grib-doc - Documentation and examples for Python GRIB python3-grib - Python 3 module for reading and writing GRIB files Closes: 789661 Changes: pygrib (2.0.0-3) unstable; urgency=medium . * Remember to move the man pages, too. Closes: #789661. * Put Vcs-Git into canonical anonscm.debian.org form. Checksums-Sha1: 65e5e9ed793cec2aaf0419bdf1992f318b8b8226 2050 pygrib_2.0.0-3.dsc 2859a10edaf4e375f3a73bef0ce11fcbe3d0fef5 10020 pygrib_2.0.0-3.debian.tar.xz 94cd6ba9541779735a79a85ee7a2c86b11af644a 19111732 python-grib-doc_2.0.0-3_all.deb 03152037f485b1b549992880b4d1455750c63074 209810 python-grib_2.0.0-3_amd64.deb dac3e11b6efeb9416e54d76f27c9f666cce82907 213724 python3-grib_2.0.0-3_amd64.deb Checksums-Sha256: 65c386103e65f47594016d5dfca1c8756012445752eba6a43db0c31686599415 2050 pygrib_2.0.0-3.dsc 919efc137d0ede09e0bc7d56df3619187b7aa6b5354e4ea5bbfa82f6918b28a3 10020 pygrib_2.0.0-3.debian.tar.xz 3ad15958710b12e3b14516cd4095899d53a5e72dd0f86b76872155d0f6063542 19111732 python-grib-doc_2.0.0-3_all.deb 8a7fd5f5e14004dbe7eadb19ab96bcfc3e5ffd1ea2ac7aac0a4a7485980e00d9 209810 python-grib_2.0.0-3_amd64.deb e254c1a2e44c98bc08aec4ec3c489910c23a2b4bc06d89a4772965c0be7dbae8 213724 python3-grib_2.0.0-3_amd64.deb Files: 343d63452956e021a4fbb9dbb938d5bd 2050 python optional pygrib_2.0.0-3.dsc 4723d8e261dc3ad7a6750145aaea773b 10020 python optional pygrib_2.0.0-3.debian.tar.xz bc9ce4e56ea603a8e9e43d7e9bd525c6 19111732 doc optional python-grib-doc_2.0.0-3_all.deb 35d6d2c3f7d5b84744eedcf34ab8a56b 209810 python optional python-grib_2.0.0-3_amd64.deb 5f0f59cd29ed5ee782f4187bf3245a7a 213724 python optional python3-grib_2.0.0-3_amd64.deb -BEGIN PGP SIGNATURE-
Bug#789541: abtransfers: Crash after successful money transfer
Dear Patrick, Am Donnerstag, den 25.06.2015, 18:25 +0200 schrieb Patrick Wacker: I'm the upstream author of AB-Transfers. Thank you for your detailed explanations. Thank you for writing AB-Transfers! […] Looking at the “bad” `history.ctx` it’s size is 41 MB (42626560 Bytes) and I think it contains strange characters due to umlauts I put into the “Verwendungszweck” with the middle click as it’s not allowed (for some reason) entering it with the keyboard. During development I had some issues with the German umlauts. Some banks supported it some don't. And also the aqbanking backend sometimes replaced some umlauts with spaces or not readable characters (but a crash did not happened). Therefore I decided to be on the save side and disabled the input of umlauts at abtransfers (didn't blocked/checked copypaste input, my fault). The Berliner Volksbank seems to support it. I guess this is a bug in AqBanking then. Also a size of 41 MB is pretty big, either you using the program for a long time with a lot of transfers or something else is wrong. A normal transfer should occupy around 1.2 KB at the history (34000 transfers needed to reach 41MB). Also looking at `history.ctx` after the crash yesterday, the format seems to be incorrect. The following is missing at the end of the file compared to the file written today. int cycle=0 int executionDay=0 char type=transaction char subType=none char status=none char charge=Nobody char sequenceType=once } #transfer } #transferList } #accountInfo } #accountInfoList A few lines above this missing entries (or directly at the end) of your bad history.ctx file should be a line starting with char purpose=. Could you remember which purpose (with umlauts) do you used? The last line in the “after crash” file is the following (without the closing ). char period=none It’s a transfer from last November. Which is the character that could not be written at the bad history.txt and maybe caused the crash? If I know this I could try to reproduce it here and maybe could fix it. The name of the account has umlauts in it: SG Friedrichshain Grün-Weiß 90 e. V.. Looking at the newly written `history.ctx` with only three transactions, it looks like the umlauts are recoded during each write. (The most recent entry is at the top.) char localName=SG Friedrichshain Gr%C3%BCn Wei%C3%9F char category=JobStatus%3A 5, JobType%3A 16 char localName=SG Friedrichshain Gr%C3%83%C2%BCn Wei%C3%83%C2%9F char category=JobStatus%3A 5, JobType%3A 16 char localName=SG Friedrichshain Gr%C3%83%C2%83%C3%82%C2%BCn Wei%C3%83%C2%83%C3%82%C2%9F char category=JobStatus%3A 5, JobType%3A 16 So with not a big number of transaction, that file gets pretty big as the `localName` lines get bigger after each transaction. In the faulty file the longest line has 12582962 columns. This probably causes the assertion in libgwenhywfar60 4.14.0-1. 3:2015/06/22 08-46-31:gwen(11198):buffer.c: 314: Size is beyond hard limit (1677727416777216) (Is the whole transfer block read in at once?) Thanks, Paul signature.asc Description: This is a digitally signed message part
Bug#786694: marked as done (fftw: FTBFS with TZ=GMT-14)
Your message dated Fri, 26 Jun 2015 06:48:50 + with message-id e1z8nrs-fw...@franck.debian.org and subject line Bug#786694: fixed in fftw 2.1.5-2 has caused the Debian Bug report #786694, regarding fftw: FTBFS with TZ=GMT-14 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.) -- 786694: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- source: rcs,fftw,qa.debian.org Severity: normal User: reproducible-bui...@lists.alioth.debian.org Usertags: environment x-debbugs-cc: reproducible-bui...@lists.alioth.debian.org Control: user qa.debian@packages.debian.org Control: usertag -1 jenkins Hi, While working on the “reproducible builds” effort [1], we have noticed that rcs and fftw and probably others fail like this: /tmp/buildd/rcs-5.9.4/build-aux/missing: line 81: makeinfo: command not found WARNING: 'makeinfo' is missing on your system. You should only need it if you modified a '.texi' file, or any other file indirectly affecting the aspect of the manual. You might want to install the Texinfo package: http://www.gnu.org/software/texinfo/ The spurious makeinfo call might also be the consequence of using a buggy 'make' (AIX, DU, IRIX), in which case you might want to install GNU make: http://www.gnu.org/software/make/ Makefile:1357: recipe for target 'rcs.info' failed make[2]: *** [rcs.info] Error 127 and similarily, /tmp/buildd/fftw-2.1.5/missing: line 81: makeinfo: command not found WARNING: 'makeinfo' is missing on your system. [...] Makefile:370: recipe for target 'fftw.info' failed make[2]: *** [fftw.info] Error 127 make[2]: Leaving directory '/tmp/buildd/fftw-2 See https://reproducible.debian.net/rbuild/unstable/amd64/rcs_5.9.4-1.rbuild.log and https://reproducible.debian.net/rbuild/unstable/amd64/fftw_2.1.5-1.rbuild.log for the full log. Strangely enough, when I build rcs in my local pbuilder setup (which like the jenkins.d.n one is based on wheezy currently), the build succeeds. I haven't tried fftw but I assume it will also succeed. (And I assume there are some more packages failing like this for reproducible.d.n.) According to apt-file search, texinfo is the only package directly providing /usr/bin/makeinfo, and neither package has texinfo in its build-depends - what I don't get is why it succeeded in my local pbuilder... At the moment I'm a bit clueless where the bug comes from, help welcome! cheers, Holger [1]: https://wiki.debian.org/ReproducibleBuilds signature.asc Description: This is a digitally signed message part. ---End Message--- ---BeginMessage--- Source: fftw Source-Version: 2.1.5-2 We believe that the bug you reported is fixed in the latest version of fftw, 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 786...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thibaut Paumard thib...@debian.org (supplier of updated fftw 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: Tue, 23 Jun 2015 11:48:16 +0200 Source: fftw Binary: fftw2 fftw-dev sfftw2 sfftw-dev fftw-docs Architecture: source amd64 all Version: 2.1.5-2 Distribution: unstable Urgency: low Maintainer: Debian Science Team debian-science-maintain...@lists.alioth.debian.org Changed-By: Thibaut Paumard thib...@debian.org Description: fftw-dev - library for computing Fast Fourier Transforms fftw-docs - documentation for fftw fftw2 - library for computing Fast Fourier Transforms sfftw-dev - library for computing Fast Fourier Transforms sfftw2 - library for computing Fast Fourier Transforms Closes: 786694 Changes: fftw (2.1.5-2) unstable; urgency=low . * Team upload. * Bug fix: FTBFS with TZ=GMT-14, thanks to Holger Levsen (Closes: #786694). * Fix fftw.texi and make sure it is always rebuilt. * Check against Policy 3.9.6 Checksums-Sha1: a2c344c03ca5316f89a5927a8219b251615b45a5 2136 fftw_2.1.5-2.dsc 047f49346bed178aeea3412e5122179489d82903 57448 fftw_2.1.5-2.debian.tar.xz 4a2fd6328abcb09335340124835b082fa2f03eaa 266882
Bug#790005: calibre-bin not instalable for dependency problem
Package: calibre-bin Version: 2.24.0+dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, I try to install calibre-bin with aptitude. It does not work because there is a dependency on qtbase-abi-5-3-2 which does not exist on the package list. aptitude shows only a virtual module qtbase-abi-5-4-2 when I find for qtbase-abi.. Regards Francois -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (900, 'unstable'), (400, 'testing') Architecture: i386 (i686) Kernel: Linux 4.0.0-2-686-pae (SMP w/1 CPU core) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages calibre-bin depends on: ii libc6 2.19-18 ii libchm12:0.40a-3+b1 ii libfreetype6 2.5.2-4 ii libgcc11:5.1.1-12 ii libicu52 52.1-9 pn libmagickcore5 none pn libmagickwand5 none ii libmtp91.1.9-3 ii libpodofo0.9.0 0.9.0-1.2+b2 ii libpython2.7 2.7.10-2 ii libqt4-dbus4:4.8.7+dfsg-1 ii libqt4-svg 4:4.8.7+dfsg-1 ii libqtcore4 4:4.8.7+dfsg-1 ii libqtgui4 4:4.8.7+dfsg-1 ii libstdc++6 5.1.1-12 ii libusb-1.0-0 2:1.0.19-1 ii python-sip [sip-api-11.0] 4.16.8+dfsg-2 ii python2.7 2.7.10-2 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages calibre-bin recommends: pn calibre none calibre-bin 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
Processed: tagging 787644
Processing commands for cont...@bugs.debian.org: tags 787644 + wheezy jessie stretch sid Bug #787644 [src:libwmf] libwmf: CVE-2015-0848 CVE-2015-4588 Added tag(s) jessie, sid, stretch, and wheezy. thanks Stopping processing here. Please contact me if you need assistance. -- 787644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787644 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#778124: marked as done (slirp: ftbfs with GCC-5)
Your message dated Fri, 26 Jun 2015 07:04:17 + with message-id e1z8ngp-0003kc...@franck.debian.org and subject line Bug#778124: fixed in slirp 1:1.0.17-8 has caused the Debian Bug report #778124, regarding slirp: 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.) -- 778124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:slirp Version: 1:1.0.17-7 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/slirp_1.0.17-7_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] inline void insque_32 _P((void *, void *)); ^ gcc -Wl,-z,relro -Wl,--as-needed -o slirp auth.o bsd-comp.o ccp.o chap.o fsm.o ipcp.o lcp.o magic.o md5.o pppdfncs.o upap.o ppp.o cksum.o debug.o if.o ip_icmp.o ip_input.o ip_output.o main.o mbuf.o misc.o options.o sbuf.o sl.o slcompress.o socket.o tcp_input.o tcp_output.o tcp_subr.o tcp_timer.o terminal.o ttys.o udp.o -lcrypt -lnsl if.o: In function `if_output': /«PKGBUILDDIR»/src/./if.c:265: undefined reference to `slirp_insque' /«PKGBUILDDIR»/src/./if.c:226: undefined reference to `slirp_remque' /«PKGBUILDDIR»/src/./if.c:285: undefined reference to `slirp_remque' if.o: In function `if_start': /«PKGBUILDDIR»/src/./if.c:403: undefined reference to `slirp_remque' /«PKGBUILDDIR»/src/./if.c:408: undefined reference to `slirp_insque' if.o: In function `if_output': /«PKGBUILDDIR»/src/./if.c:288: undefined reference to `slirp_insque' ip_input.o: In function `ip_reass': /«PKGBUILDDIR»/src/ip_input.c:379: undefined reference to `remque_32' /«PKGBUILDDIR»/src/ip_input.c:268: undefined reference to `insque_32' ip_input.o: In function `ip_freef': /«PKGBUILDDIR»/src/ip_input.c:409: undefined reference to `remque_32' mbuf.o: In function `m_get': /«PKGBUILDDIR»/src/./mbuf.c:73: undefined reference to `slirp_remque' /«PKGBUILDDIR»/src/./mbuf.c:77: undefined reference to `slirp_insque' mbuf.o: In function `m_free': /«PKGBUILDDIR»/src/./mbuf.c:115: undefined reference to `slirp_insque' /«PKGBUILDDIR»/src/./mbuf.c:102: undefined reference to `slirp_remque' misc.o: In function `relay': /«PKGBUILDDIR»/src/./misc.c:575: undefined reference to `writen' /«PKGBUILDDIR»/src/./misc.c:584: undefined reference to `writen' socket.o: In function `sofree': /«PKGBUILDDIR»/src/./socket.c:82: undefined reference to `slirp_remque' socket.o: In function `solisten': /«PKGBUILDDIR»/src/./socket.c:552: undefined reference to `slirp_insque' tcp_input.o: In function `tcp_reass': /«PKGBUILDDIR»/src/./tcp_input.c:193: undefined reference to `remque_32' /«PKGBUILDDIR»/src/./tcp_input.c:200: undefined reference to `insque_32' /«PKGBUILDDIR»/src/./tcp_input.c:217: undefined reference to `remque_32' /«PKGBUILDDIR»/src/./tcp_input.c:200: undefined reference to `insque_32' tcp_subr.o: In function `tcp_close': /«PKGBUILDDIR»/src/./tcp_subr.c:291: undefined reference to `remque_32' tcp_subr.o: In function `tcp_attach': /«PKGBUILDDIR»/src/./tcp_subr.c:552: undefined reference to `slirp_insque' udp.o: In function `udp_attach': /«PKGBUILDDIR»/src/./udp.c:319: undefined reference to `slirp_insque' udp.o: In function `udp_listen': /«PKGBUILDDIR»/src/./udp.c:608: undefined reference to `slirp_insque' collect2: error: ld returned 1 exit status make[1]: *** [slirp] Error 1 Makefile:46: recipe for target 'slirp' failed make[1]: Leaving directory '/«PKGBUILDDIR»/src' make: *** [src/slirp-fullbolt] Error 2
Processed: severity of 778010 is important
Processing commands for cont...@bugs.debian.org: severity 778010 important Bug #778010 [src:mkvtoolnix] mkvtoolnix: ftbfs with GCC-5 Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 778010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778010 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#778057: marked as done (pdns: ftbfs with GCC-5)
Your message dated Fri, 26 Jun 2015 09:15:33 +0200 with message-id 20150626071533.ga89...@sx.home.zeha.at and subject line Re: #778057: pdns: ftbfs with GCC-5 has caused the Debian Bug report #778057, regarding pdns: 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.) -- 778057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:pdns Version: 3.4.1-4 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/pdns_3.4.1-4_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] checking for x86_64-linux-gnu-gcc option to produce PIC... -fPIC -DPIC checking if x86_64-linux-gnu-gcc PIC flag -fPIC -DPIC works... yes checking if x86_64-linux-gnu-gcc static flag -static works... yes checking if x86_64-linux-gnu-gcc supports -c -o file.o... yes checking if x86_64-linux-gnu-gcc supports -c -o file.o... (cached) yes checking whether the x86_64-linux-gnu-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 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... no checking how to run the C++ preprocessor... x86_64-linux-gnu-g++ -E checking for ld used by x86_64-linux-gnu-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 x86_64-linux-gnu-g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking for x86_64-linux-gnu-g++ option to produce PIC... -fPIC -DPIC checking if x86_64-linux-gnu-g++ PIC flag -fPIC -DPIC works... yes checking if x86_64-linux-gnu-g++ static flag -static works... yes checking if x86_64-linux-gnu-g++ supports -c -o file.o... yes checking if x86_64-linux-gnu-g++ supports -c -o file.o... (cached) yes checking whether the x86_64-linux-gnu-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 how to force completely read-only GOT table... -Wl,-z -Wl,relro -Wl,-z -Wl,now checking whether struct tm is in sys/time.h or time.h... time.h checking for tm_gmtoff in struct tm... yes checking for x86_64-linux-gnu-pkg-config... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking sys/mman.h usability... yes checking sys/mman.h presence... yes checking for sys/mman.h... yes checking for mmap... yes checking for ragel... ragel checking for asciidoc... no checking for LUA... no checking for LUA... no checking for LUA... yes checking for chosen LUA... lua-5.1 checking for Boost headers version = 1.35.0... yes checking for Boost's header version... configure: error: invalid value: boost_major_version= make[1]: *** [override_dh_auto_configure] Error 1 debian/rules:17: recipe for target 'override_dh_auto_configure' 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--- fixed -1 3.4.5-1 This has been fixed
Bug#789985: FTBFS: IRanges_defines.h: fatal error: S4Vectors_defines.h: No such file or directory
Hi, thanks for this bug report. I guess some other r-bioc-* packages are similarly affected. There is a transition to a new version of these packages ongoing and the problem will be dealt with soon. Kind regards Andreas. On Thu, Jun 25, 2015 at 08:30:04PM +, Chris West (Faux) wrote: Package: r-bioc-shortread Version: 1.22.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: config.status: creating src/Makevars ** libs make[1]: Entering directory '/tmp/buildd/r-bioc-shortread-1.22.0/src' gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -I/usr/lib/R/site-library/IRanges/include -I/usr/lib/R/site-library/XVector/include -I/usr/lib/R/site-library/Biostrings/include -fopenmp -fpic -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -g -c Biostrings_stubs.c -o Biostrings_stubs.o In file included from /usr/lib/R/site-library/Biostrings/include/Biostrings_defines.h:18:0, from /usr/lib/R/site-library/Biostrings/include/Biostrings_interface.h:114, from /usr/lib/R/site-library/Biostrings/include/_Biostrings_stubs.c:1, from Biostrings_stubs.c:1: /usr/lib/R/site-library/IRanges/include/IRanges_defines.h:18:31: fatal error: S4Vectors_defines.h: No such file or directory #include S4Vectors_defines.h ^ compilation terminated. /usr/lib/R/etc/Makeconf:134: recipe for target 'Biostrings_stubs.o' failed Maybe this is a bug in r-bioc-biostrings, or r-bioc-iranges? The same bug affects at least r-bioc-genomicalignments, r-bioc-rtracklayer, and r-bioc-variantannotation. (all same maintainer) Full build log: https://reproducible.debian.net/rb-pkg/testing/amd64/r-bioc-shortread.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ___ Debian-med-packaging mailing list debian-med-packag...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 777997
Processing commands for cont...@bugs.debian.org: tags 777997 + pending Bug #777997 [src:masscan] masscan: ftbfs with GCC-5 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 777997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777997 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 (with 1 errors): Re: Bug#790008: texlive-bin: texlive-binaries uninstallable on several architectures
Processing commands for cont...@bugs.debian.org: severity 790006 serious Bug #790006 [texlive-binaries] I think there is some dependency problem for the new texlive package Severity set to 'serious' from 'important' merge 790008 790006 Bug #790008 [src:texlive-bin] texlive-bin: texlive-binaries uninstallable on several architectures Unable to merge bugs because: package of #790006 is 'texlive-binaries' not 'src:texlive-bin' Failed to merge 790008: Did not alter merged bugs. stop Stopping processing here. Please contact me if you need assistance. -- 790006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790006 790008: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790008 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#790008: texlive-bin: texlive-binaries uninstallable on several architectures
severity 790006 serious merge 790008 790006 stop On 26.06.2015 10:27, Edmund Grimley Evans wrote: texlive-binaries depends unconditionally on libtexluajit2, which is only built for Architecture: amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc Fixed in git and already reported. H. -- http://www.hilmar-preusse.de.vu/ #206401 http://counter.li.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777861: [Pkg-gauche-devel] Bug#777861: gauche-c-wrapper: ftbfs with GCC-5
Severity: important -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: likely invalid
Processing commands for cont...@bugs.debian.org: severity 777861 important Bug #777861 [src:gauche-c-wrapper] gauche-c-wrapper: ftbfs with GCC-5 Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 777861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777861 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: Bug#789121: segfaults in libc6 when accessing ssl keys and signatures
Processing control commands: severity 789121 important Bug #789121 [claws-mail] segfaults in libc6 when accessing ssl keys and signatures Severity set to 'important' from 'grave' -- 789121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789121 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#789121: segfaults in libc6 when accessing ssl keys and signatures
Control: severity 789121 important Hi Andrea, On Thu, Jun 18, 2015 at 03:31:33AM +0200, Andrea Lusuardi wrote: Package: claws-mail Version: 3.11.1-3 Severity: grave This severity is not correct with current bug info, I've readjusted it to a more suitable value¹. Hi, since latest update claws-mail on my debian sid starts up correctly and i can access emails and even send one, until i try to fetch unread emails from any ssl/tls protected source, it then immediately segfaults. I am attaching some of the final strace output hoping this helps. Thanks and let me know how i can help with the debugging, i have some experience with gdb and related. Great, then please try to get a proper backtrace with gdb. You can read upstream's page for help on debugging, which also includes specifics for Debian: http://www.claws-mail.org/faq/index.php/Debugging_Claws thanks in advance, ¹ https://www.debian.org/Bugs/Developer.en.html#severities -- Ricardo Mones ~ Never send a human to do a machine's job. Agent Smith signature.asc Description: Digital signature
Bug#790008: texlive-bin: texlive-binaries uninstallable on several architectures
Source: texlive-bin Version: 2015.20150524.37493-2 Severity: serious texlive-binaries depends unconditionally on libtexluajit2, which is only built for Architecture: amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc according to debian/control, but that list may be too long as libtexluajit2 does not really get build for hurd-i386 and mips, according to https://packages.debian.org/sid/libtexluajit2 A lot of packages have texlive-binaries as a Build-Depends, so this seems quite serious to me. Those packages could specify their Build-Depends more precisely but presumably this should be fixed in texlive-bin as there is no point in having texlive-binaries if it is uninstallable. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778136: marked as done (t38modem: ftbfs with GCC-5)
Your message dated Fri, 26 Jun 2015 10:37:14 -0400 with message-id 20150626143714.ga1...@jirafa.cyrius.com and subject line Re: Bug#778136: t38modem: ftbfs with GCC-5 has caused the Debian Bug report #778136, regarding t38modem: 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.) -- 778136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:t38modem Version: 2.0.0-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/t38modem_2.0.0-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 [...] compilation terminated. make[1]: *** [pmodem.o] Error 1 make[1]: *** Waiting for unfinished jobs Makefile:113: recipe for target 'pmodem.o' failed In file included from /usr/include/ptlib/contain.h:42:0, from /usr/include/ptlib.h:56, from t30.cxx:44: /usr/include/ptlib/critsec.h:46:33: fatal error: bits/atomicity.h: No such file or directory compilation terminated. compilation terminated. make[1]: *** [hdlc.o] Error 1 Makefile:113: recipe for target 'hdlc.o' failed In file included from /usr/include/ptlib/contain.h:42:0, from /usr/include/ptlib.h:56, from drivers.cxx:41: /usr/include/ptlib/critsec.h:46:33: fatal error: bits/atomicity.h: No such file or directory In file included from /usr/include/ptlib/contain.h:42:0, from /usr/include/ptlib.h:56, from t30tone.cxx:54: /usr/include/ptlib/critsec.h:46:33: fatal error: bits/atomicity.h: No such file or directory make[1]: *** [pmutils.o] Error 1 Makefile:113: recipe for target 'pmutils.o' failed compilation terminated. make[1]: *** [pmodemi.o] Error 1 Makefile:113: recipe for target 'pmodemi.o' failed compilation terminated. compilation terminated. make[1]: *** [dle.o] Error 1 Makefile:113: recipe for target 'dle.o' failed compilation terminated. make[1]: *** [drivers.o] Error 1 Makefile:113: recipe for target 'drivers.o' failed make[1]: *** [t30.o] Error 1 Makefile:113: recipe for target 't30.o' failed make[1]: *** [t30tone.o] Error 1 Makefile:113: recipe for target 't30tone.o' failed make[1]: *** [tone_gen.o] Error 1 Makefile:113: recipe for target 'tone_gen.o' failed In file included from /usr/include/ptlib/contain.h:42:0, from /usr/include/ptlib.h:56, from fcs.cxx:39: /usr/include/ptlib/critsec.h:46:33: fatal error: bits/atomicity.h: No such file or directory compilation terminated. make[1]: *** [fcs.o] Error 1 Makefile:113: recipe for target 'fcs.o' failed make[1]: Leaving directory '/«PKGBUILDDIR»' dh_auto_build: make -j10 returned exit code 2 make: *** [build-arch] Error 2 debian/rules:9: recipe for target 'build-arch' failed dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ---End Message--- ---BeginMessage--- * Matthias Klose d...@debian.org [2015-02-12 10:37]: Makefile:113: recipe for target 'pmodem.o' failed In file included from /usr/include/ptlib/contain.h:42:0, from /usr/include/ptlib.h:56, from t30.cxx:44: /usr/include/ptlib/critsec.h:46:33: fatal error: bits/atomicity.h: No such file or directory compilation terminated. compilation terminated. make[1]: *** [hdlc.o] Error 1 The problem is in ptlib (#778074). Now that this bug is closed, I verified that t38modem builds fine with GCC 5. I'm therefore closing this bug. -- Martin Michlmayr Linux for HP Helion OpenStack,
Bug#789118: No issues with clean upgrade
On Fri, Jun 26, 2015 at 11:42:44AM +0200, Emilio Pozuelo Monfort wrote: Control: found -1 3.14.4-1 On 22/06/15 02:36, Michel Dänzer wrote: On 22.06.2015 03:39, Josh Triplett wrote: On Sun, Jun 21, 2015 at 07:52:10PM +0200, Michael Biebl wrote: Am 20.06.2015 um 08:54 schrieb Michel Dänzer: On Thu, 18 Jun 2015 21:19:20 +0400 George Hertz george...@gmail.com wrote: I've just upgraded to 3.16 on unstable, but restarted the system right after the update finished. No problems unlocking. Yeah, the problem only occurs with a gnome-shell which is already running during the upgrade. However, the problem also occurs when only locking the session after the upgrade has completed. One possible workaround after the upgrade is killall -HUP gnome-shell gnome-settings-daemon I didn't know you could HUP gnome-shell to unlock the session; that's useful to know. Sending SIGHUP to gnome-shell only is enough to be able to unlock the session, but gnome-settings-daemon also needs to be restarted, or some things such as keyboard shortcuts don't work properly in the new gnome-shell. Unfortuantely we don't have a proper mechanism to restart programs in the desktop session. Using killall in postinst is something I'd be wary about. It's also not OK to unexpectedly unlock someone's session due to a concurrent upgrade; can't unlock my session is bad, but unlocked my screen during upgrade is a critical security bug. SIGHUP doesn't unlock the session, it just makes gnome-shell restart itself, after which the upgraded version of gnome-shell runs and unlocking the session works normally. This bug is preventing testing migration, which is causing a lot of other bugs because of version mismatches between gtk+, gnome-settings-daemon and mutter/gnome-shell (see e.g. #789618, #789891, #789866, #789725, #789575, #789484...). I've talked about it to some team members and we agreed that this is RC, but that it'd be better to let gnome-shell migrate for the time being. So I'm doing some trick to let it migrate, but we'll fix this. I wouldn't be surprised if the bug exists in previous versions of gnome-shell as well, so allowing migration to testing seems fine. (Or actually, it's not obvious whether the bug exists in current versions, as it's the previous version which failed to unlock after upgrade.) The new version likely isn't any more broken than the old; it's the upgrade that's broken, and preventing that upgrade indefinitely doesn't make the problem go away. (Also, those other bugs seem to indicate that either the interactions between those components need to be made less fragile, or package dependencies need to prevent installing incompatible versions.) Josh, any chance you can try the SIGHUP approach and confirm that solves your problem and doesn't cause any other undesired effect? I've tested sending a SIGHUP to gnome-shell, and that approach causes several significant undesired effects. 1) Sending SIGHUP to gnome-shell momentarily drops the screen lock. This reveals the applications behind the screen lock, and even allows interacting with them. (For a fraction of a second, sure, but still, that's a security issue.) 2) If gnome-shell restarts twice in the same session, the second time it puts up the Oh no! dialog, which only allows the user to restart their session, losing anything they have open. So if gnome-shell has already restarted once in the user's session for unrelated reasons, sending SIGHUP to it will force the user to restart their session entirely and lose any open applications. Based on the above, I think it'd be an extremely bad idea to send SIGHUP to a user's gnome-shell from a maintainer script. I think it's going to be necessary to teach gnome-shell to handle screen unlocking after an upgrade. I've forwarded this bug upstream to https://bugzilla.gnome.org/show_bug.cgi?id=751544 . - 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#790024: package pandas FTBFS on big-endian
Package: pandas
Version: 0.15.1+git125-ge463818-1
Severity: serious
Tags: sid + patch
User: debian-m...@lists.debian.org
Usertags: mips-patch
Hello,
Package FTBFS on big-endian builds:
https://buildd.debian.org/status/package.php?p=pandassuite=sid
With following message:
==
FAIL: test_to_records (pandas.tests.test_categorical.TestCategoricalAsBlock)
--
Traceback (most recent call last):
File
/«BUILDDIR»/pandas-0.15.1+git125-ge463818/debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/test_categorical.py,
line 2393, in test_to_records
tm.assert_almost_equal(result,expected)
File das/src/testing.pyx, line 58, in pandas._testing.assert_almost_equal
(pandas/src/testing.c:2745)
File das/src/testing.pyx, line 93, in pandas._testing.assert_almost_equal
(pandas/src/testing.c:1830)
File das/src/testing.pyx, line 143, in pandas._testing.assert_almost_equal
(pandas/src/testing.c:2618)
AssertionError: (0L, 'a') != (0L, 'a')
-
With the patch attached package builds successfully on both MIPS big-endian and
little-endian.
Patch is changing test_categorical to work with native endian instead of
little-endian.
Same patch is available upstream:
https://github.com/pydata/pandas/pull/10438
Could you please consider including this patch?
Thank you!
Regards,
Jurica
--- pandas-0.15.1+git125-ge463818.orig/pandas/tests/test_categorical.py
+++ pandas-0.15.1+git125-ge463818/pandas/tests/test_categorical.py
@@ -2389,7 +2389,7 @@ class TestCategoricalAsBlock(tm.TestCase
# this coerces
result = df.to_records()
expected = np.rec.array([(0, 'a'), (1, 'b'), (2, 'c')],
-dtype=[('index', 'i8'), ('0', 'O')])
+dtype=[('index', '=i8'), ('0', 'O')])
tm.assert_almost_equal(result,expected)
def test_numeric_like_ops(self):
Bug#790051: texlive-music: fails to install and configure because same file is present in different package
Package: texlive-music Version: 2015.20150524-1 Justification: renders package unusable Severity: grave Dear Maintainer, I was upgrading tex*-all when was hit with this :- Preparing to unpack .../texlive-music_2015.20150625-1_all.deb ... D01: process_archive oldversionstatus=installed Unpacking texlive-music (2015.20150625-1) over (2015.20150524-1) ... Replacing files in old package texlive-pictures (2015.20150524-1) ... dpkg: error processing archive /var/cache/apt/archives/texlive-music_2015.20150625-1_all.deb (--unpack): trying to overwrite '/usr/share/doc/texlive-doc/latex/piano/README', which is also in package texlive-pictures-doc 2015.20150524-1 dpkg: considering deconfiguration of texlive-music, which would be broken by installation of texlive-pictures ... dpkg: yes, will deconfigure texlive-music (broken by texlive-pictures) Could you figure out what the issue is and please fix it. -- Package-specific info: IMPORTANT INFORMATION: We will only consider bug reports concerning the packaging of TeX Live as relevant. If you have problems with combination of packages in a LaTeX document, please consult your local TeX User Group, the comp.text.tex user group, the author of the original .sty file, or any other help resource. In particular, bugs that are related to up-upstream, i.e., neither Debian nor TeX Live (upstream), but the original package authors, will be closed immediately. *** The Debian TeX Team is *not* a LaTeX Help Desk *** If you report an error when running one of the TeX-related binaries (latex, pdftex, metafont,...), or if the bug is related to bad or wrong output, please include a MINIMAL example input file that produces the error in your report. Please run your example with (pdf)latex -recorder ... (or any other program that supports -recorder) and send us the generated file with the extension .fls, it lists all the files loaded during the run and can easily explain problems induced by outdated files in your home directory. Don't forget to also include minimal examples of other files that are needed, e.g. bibtex databases. Often it also helps to include the logfile. Please, never send included pictures! If your example file isn't short or produces more than one page of output (except when multiple pages are needed to show the problem), you can probably minimize it further. Instructions on how to do that can be found at http://www.minimalbeispiel.de/mini-en.html (english) or http://www.minimalbeispiel.de/mini.html (german) ## minimal input file ## other files ## List of ls-R files -rw-r--r-- 1 root root 2466 Jun 26 20:49 /var/lib/texmf/ls-R lrwxrwxrwx 1 root root 29 Jun 25 11:12 /usr/share/texmf/ls-R - /var/lib/texmf/ls-R-TEXMFMAIN lrwxrwxrwx 1 root root 31 Jun 25 13:16 /usr/share/texlive/texmf-dist/ls-R - /var/lib/texmf/ls-R-TEXLIVEDIST lrwxrwxrwx 1 root root 31 Jun 25 13:16 /usr/share/texlive/texmf-dist/ls-R - /var/lib/texmf/ls-R-TEXLIVEDIST -rw-r--r-- 1 root root 80 Apr 14 2014 /usr/share/texlive/texmf/ls-R ## Config files -rw-r--r-- 1 root root 1101 Jun 26 20:46 /etc/texmf/web2c/texmf.cnf -rw-r--r-- 1 root root 5770 Jun 13 10:47 /var/lib/texmf/web2c/fmtutil.cnf lrwxrwxrwx 1 root root 32 Jun 25 13:16 /usr/share/texmf/web2c/updmap.cfg - /var/lib/texmf/updmap.cfg-DEBIAN -rw-r--r-- 1 root root 2844 Jun 26 20:49 /var/lib/texmf/tex/generic/config/language.dat ## Files in /etc/texmf/web2c/ total 8 -rw-r--r-- 1 root root 283 Jun 15 2013 mktex.cnf -rw-r--r-- 1 root root 1101 Jun 26 20:46 texmf.cnf ## md5sums of texmf.d ca40c66f144b4bafc3e59a2dd32ecb9c /etc/texmf/texmf.d/00debian.cnf 055e06548bac99958d8ab2dd1248f2b4 /etc/texmf/texmf.d/80tex4ht.cnf -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental'), (1, 'unstable'), (1, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-2-amd64 (SMP w/2 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 texlive-music depends on: ii dpkg1.18.1 ii m-tx0.60d.ctan20131224-1 ii musixtex1:1.17.ctan20150601-1 ii pmx 2.7.0.ctan20150301-1 ii python 2.7.9-1 ii tex-common 6.01 ii texlive-base2015.20150625-1 ii texlive-binaries2015.20150524.37493-2 ii texlive-latex-base 2015.20150625-1 texlive-music recommends no packages. texlive-music suggests no packages. Versions of packages tex-common depends on: ii dpkg 1.18.1 ii ucf 3.0030 Versions of packages tex-common suggests: ii debhelper 9.20150507 Versions of packages texlive-music is related to: ii tex-common6.01 ii
Processed: tagging 777914
Processing commands for cont...@bugs.debian.org: tags 777914 + patch Bug #777914 [src:insserv] insserv: ftbfs with GCC-5 Ignoring request to alter tags of bug #777914 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 777914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777914 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#790052: pelican: trying to overwrite '/usr/share/man/man1/pelican-themes.1.gz', which is also in package python-pelican 3.6.0-1
Package: pelican Version: 3.6.0-2 Severity: serious Dear Maintainer, pelican has the vrong version in its Breaks and Replaces header which makes the installation fail if python-pelican was installed before (i.e. upon a python-pelican upgrade): […] Unpacking pelican (3.6.0-2) ... dpkg: error processing archive /var/cache/apt/archives/pelican_3.6.0-2_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/pelican-themes.1.gz', which is also in package python-pelican 3.6.0-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to unpack .../python-pelican_3.6.0-2_all.deb ... Unpacking python-pelican (3.6.0-2) over (3.6.0-1) ... […] Errors were encountered while processing: /var/cache/apt/archives/pelican_3.6.0-2_all.deb […] E: Sub-process /usr/bin/dpkg returned an error code (1) […] dpkg: dependency problems prevent configuration of python-pelican: python-pelican depends on pelican; however: Package pelican is not installed. dpkg: error processing package python-pelican (--configure): dependency problems - leaving unconfigured […] Errors were encountered while processing: python-pelican Current headers: Replaces: python-pelican ( 3.6.0-1) Breaks: python-pelican ( 3.6.0-1) What the headers should look like: Replaces: python-pelican ( 3.6.0-2~) Breaks: python-pelican ( 3.6.0-2~) -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pelican depends on: ii libpython2.7-stdlib [python-argparse] 2.7.10-2 ii python 2.7.9-1 ii python-blinker 1.3.dfsg2-1 ii python-dateutil2.2-2 ii python-docutils0.12+dfsg-1 ii python-feedgenerator 1.7-1 ii python-jinja2 2.7.3-1 ii python-markdown2.6.2-1 ii python-pkg-resources 17.0-1 ii python-pygments2.0.1+dfsg-1.1 ii python-six 1.9.0-3 ii python-tz 2012c+dfsg-0.1 ii python-unidecode 0.04.16-1 pn python:any none pelican recommends no packages. Versions of packages pelican suggests: ii pandoc 1.13.2.1~dfsg-1+b4 ii python-bs4 4.3.2-2 -- 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#555168: Many locales files do not permit modification
As a data point, glibc upstream seem to believe that localedata is not copyrightable: https://sourceware.org/ml/libc-locales/2012-q2/msg00136.html -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777918: marked as done (ipsec-tools: ftbfs with GCC-5)
Your message dated Fri, 26 Jun 2015 16:48:47 + with message-id e1z8wo3-va...@franck.debian.org and subject line Bug#777918: fixed in ipsec-tools 1:0.8.2+20140711-4 has caused the Debian Bug report #777918, regarding ipsec-tools: ftbfs with GCC-5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 777918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:ipsec-tools Version: 1:0.8.2+20140711-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/ipsec-tools_0.8.2+20140711-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 [...] mv -f .deps/algorithm.Tpo .deps/algorithm.Po x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I./../libipsec -D_GNU_SOURCE -include ./src/include-glibc/glibc-bugs.h -I./src/include-glibc -I./src/include-glibc -D_FORTIFY_SOURCE=2 -isystem /usr/include/mit-krb5 -I../../src/racoon/missing -D_GNU_SOURCE -include ../../src/include-glibc/glibc-bugs.h -I../../src/include-glibc -I../../src/include-glibc -DSYSCONFDIR=\/etc/racoon\ -DADMINPORTDIR=\/var/run/racoon\ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -Wno-unused -MT proposal.o -MD -MP -MF .deps/proposal.Tpo -c -o proposal.o proposal.c mv -f .deps/proposal.Tpo .deps/proposal.Po x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I./../libipsec -D_GNU_SOURCE -include ./src/include-glibc/glibc-bugs.h -I./src/include-glibc -I./src/include-glibc -D_FORTIFY_SOURCE=2 -isystem /usr/include/mit-krb5 -I../../src/racoon/missing -D_GNU_SOURCE -include ../../src/include-glibc/glibc-bugs.h -I../../src/include-glibc -I../../src/include-glibc -DSYSCONFDIR=\/etc/racoon\ -DADMINPORTDIR=\/var/run/racoon\ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -Wno-unused -MT sainfo.o -MD -MP -MF .deps/sainfo.Tpo -c -o sainfo.o sainfo.c mv -f .deps/sainfo.Tpo .deps/sainfo.Po x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I./../libipsec -D_GNU_SOURCE -include ./src/include-glibc/glibc-bugs.h -I./src/include-glibc -I./src/include-glibc -D_FORTIFY_SOURCE=2 -isystem /usr/include/mit-krb5 -I../../src/racoon/missing -D_GNU_SOURCE -include ../../src/include-glibc/glibc-bugs.h -I../../src/include-glibc -I../../src/include-glibc -DSYSCONFDIR=\/etc/racoon\ -DADMINPORTDIR=\/var/run/racoon\ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -Wno-unused -MT strnames.o -MD -MP -MF .deps/strnames.Tpo -c -o strnames.o strnames.c mv -f .deps/strnames.Tpo .deps/strnames.Po x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I./../libipsec -D_GNU_SOURCE -include ./src/include-glibc/glibc-bugs.h -I./src/include-glibc -I./src/include-glibc -D_FORTIFY_SOURCE=2 -isystem /usr/include/mit-krb5 -I../../src/racoon/missing -D_GNU_SOURCE -include ../../src/include-glibc/glibc-bugs.h -I../../src/include-glibc -I../../src/include-glibc -DSYSCONFDIR=\/etc/racoon\ -DADMINPORTDIR=\/var/run/racoon\ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -Wno-unused -MT schedule.o -MD -MP -MF .deps/schedule.Tpo -c -o schedule.o schedule.c mv -f .deps/schedule.Tpo .deps/schedule.Po x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I./../libipsec -D_GNU_SOURCE -include ./src/include-glibc/glibc-bugs.h -I./src/include-glibc -I./src/include-glibc -D_FORTIFY_SOURCE=2 -isystem /usr/include/mit-krb5 -I../../src/racoon/missing -D_GNU_SOURCE -include
Bug#787638: php5-curl: php segfaults immediately with php5-curl installed
Package: php5-curl Version: 5.6.9+dfsg-1 Followup-For: Bug #787638 Dear Maintainer, I confirm this bug: I have exactly the same problem on this machine. -- Package-specific info: Additional PHP 5 information PHP 5 SAPI (php5query -S): apache2 cli cgi PHP 5 Extensions (php5query -M -v): intl (Enabled for apache2 by maintainer script) intl (Enabled for cli by maintainer script) intl (Enabled for cgi by maintainer script) readline (Enabled for apache2 by maintainer script) readline (Enabled for cli by maintainer script) readline (Enabled for cgi by maintainer script) pdo_mysql (Enabled for apache2 by maintainer script) pdo_mysql (Enabled for cli by maintainer script) pdo_mysql (Enabled for cgi by maintainer script) pdo_sqlite (Enabled for apache2 by maintainer script) pdo_sqlite (Enabled for cli by maintainer script) pdo_sqlite (Enabled for cgi by maintainer script) mysql (Enabled for apache2 by maintainer script) mysql (Enabled for cli by maintainer script) mysql (Enabled for cgi by maintainer script) mysqli (Enabled for apache2 by maintainer script) mysqli (Enabled for cli by maintainer script) mysqli (Enabled for cgi by maintainer script) imagick (Enabled for apache2 by maintainer script) imagick (Enabled for cli by maintainer script) imagick (Enabled for cgi by maintainer script) oauth (Enabled for apache2 by maintainer script) oauth (Enabled for cli by maintainer script) oauth (Enabled for cgi by maintainer script) imap (Enabled for apache2 by maintainer script) imap (Enabled for cli by maintainer script) imap (Enabled for cgi by maintainer script) pspell (Enabled for apache2 by maintainer script) pspell (Enabled for cli by maintainer script) pspell (Enabled for cgi by maintainer script) curl (Enabled for apache2 by maintainer script) curl (Enabled for cli by maintainer script) curl (Enabled for cgi by maintainer script) gd (Enabled for apache2 by maintainer script) gd (Enabled for cli by maintainer script) gd (Enabled for cgi by maintainer script) mcrypt (Enabled for apache2 by maintainer script) mcrypt (Enabled for cli by maintainer script) mcrypt (Enabled for cgi by maintainer script) pdo (Enabled for apache2 by maintainer script) pdo (Enabled for cli by maintainer script) pdo (Enabled for cgi by maintainer script) apcu (Enabled for apache2 by maintainer script) apcu (Enabled for cli by maintainer script) apcu (Enabled for cgi by maintainer script) json (Enabled for apache2 by maintainer script) json (Enabled for cli by maintainer script) json (Enabled for cgi by maintainer script) opcache (Enabled for apache2 by maintainer script) opcache (Enabled for cli by maintainer script) opcache (Enabled for cgi by maintainer script) sqlite3 (Enabled for apache2 by maintainer script) sqlite3 (Enabled for cli by maintainer script) sqlite3 (Enabled for cgi by maintainer script) ldap (Enabled for apache2 by maintainer script) ldap (Enabled for cli by maintainer script) ldap (Enabled for cgi by maintainer script) Configuration files: /etc/php5/mods-available/curl.ini extension=curl.so -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 4.0.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages php5-curl depends on: ii libc6 2.19-18 ii libcurl3 7.43.0-1 ii php5-common [phpapi-20131226] 5.6.9+dfsg-1 ii ucf3.0030 php5-curl recommends no packages. php5-curl suggests no packages. Versions of packages php5-common depends on: ii libc6 2.19-18 ii lsof4.86+dfsg-1 ii psmisc 22.21-2 ii sed 4.2.2-6 ii ucf 3.0030 Versions of packages php5-common suggests: ii php5-apcu [php5-user-cache] 4.0.7-1 Versions of packages php5-cli depends on: ii libbz2-1.01.0.6-8 ii libc6 2.19-18 ii libcomerr21.42.13-1 ii libdb5.3 5.3.28-9 ii libedit2 3.1-20150325-1 ii libgssapi-krb5-2 1.13.2+dfsg-2 ii libk5crypto3 1.13.2+dfsg-2 ii libkrb5-3 1.13.2+dfsg-2 ii libmagic1 1:5.22+15-2 ii libonig2 5.9.6-1 ii libpcre3 2:8.35-6 ii libqdbm14 1.8.78-5+b3 ii libssl1.0.0 1.0.2c-1 ii libxml2 2.9.2+dfsg1-3 ii mime-support 3.58 ii php5-common 5.6.9+dfsg-1 ii php5-json 1.3.6-1 ii tzdata2015e-1 ii ucf 3.0030 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages php5-cli recommends: ii php5-readline 5.6.9+dfsg-1 Versions of packages php5-cli suggests: ii php-pear 5.6.9+dfsg-1 Versions of packages libapache2-mod-php5 depends on: ii apache2 2.4.12-2 ii apache2-bin [apache2-api-20120211] 2.4.12-2 ii libbz2-1.0 1.0.6-8 ii libc6
Bug#778043: marked as done (openam: ftbfs with GCC-5)
Your message dated Fri, 26 Jun 2015 10:36:19 -0400 with message-id 20150626143619.ga...@jirafa.cyrius.com and subject line Re: Bug#778043: openam: ftbfs with GCC-5 has caused the Debian Bug report #778043, regarding openam: 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.) -- 778043: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:openam Version: 1.4.0-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/openam_1.4.0-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 [...] dpkg-buildpackage: source changed by Mark Purcell m...@debian.org dpkg-source --before-build openam-1.4.0 dpkg-buildpackage: host architecture amd64 fakeroot debian/rules clean dh_testdir dh_testroot rm -f build-stamp [ ! -f Makefile -o ! -f /usr/share/openh323/openh323u.mak ]||/usr/bin/make OPENH323DIR=/usr/share/openh323 PTLIBDIR=/usr/share/ptlib PTLIB_FILE=. PREFIX=/usr OH323_LIBDIR=/usr/lib/ optclean clean make[1]: Entering directory '/«PKGBUILDDIR»' /usr/bin/make DEBUG= default_clean make[2]: Entering directory '/«PKGBUILDDIR»' rm -rf ./obj_linux_x86_64/main.o ./obj_linux_x86_64/main.dep core ./obj_linux_x86_64/openam make[2]: Leaving directory '/«PKGBUILDDIR»' /usr/bin/make DEBUG=1 default_clean make[2]: Entering directory '/«PKGBUILDDIR»' rm -rf ./obj_linux_x86_64_d/main.o ./obj_linux_x86_64_d/main.dep core ./obj_linux_x86_64_d/openam make[2]: Leaving directory '/«PKGBUILDDIR»' /usr/bin/make DEBUG= P_SHAREDLIB=0 default_clean make[2]: Entering directory '/«PKGBUILDDIR»' rm -rf ./obj_linux_x86_64_s/main.o ./obj_linux_x86_64_s/main.dep core ./obj_linux_x86_64_s/openam make[2]: Leaving directory '/«PKGBUILDDIR»' /usr/bin/make DEBUG=1 P_SHAREDLIB=0 default_clean make[2]: Entering directory '/«PKGBUILDDIR»' rm -rf ./obj_linux_x86_64_d_s/main.o ./obj_linux_x86_64_d_s/main.dep core ./obj_linux_x86_64_d_s/openam make[2]: Leaving directory '/«PKGBUILDDIR»' make[1]: Leaving directory '/«PKGBUILDDIR»' rm -rf obj_* dh_clean dpkg-buildpackage: warning: debian/rules must be updated to support the 'build-arch' and 'build-indep' targets (at least 'build-arch' seems to be missing) debian/rules build dh_testdir /usr/bin/make OPENH323DIR=/usr/share/openh323 PTLIBDIR=/usr/share/ptlib PTLIB_FILE=. PREFIX=/usr OH323_LIBDIR=/usr/lib/ opt optshared make[1]: Entering directory '/«PKGBUILDDIR»' /usr/bin/make DEBUG= default_target make[2]: Entering directory '/«PKGBUILDDIR»' [CC] main.cxx In file included from /usr/include/ptlib/contain.h:42:0, from /usr/include/ptlib.h:56, from main.cxx:460: /usr/include/ptlib/critsec.h:46:33: fatal error: bits/atomicity.h: No such file or directory compilation terminated. make[2]: *** [obj_linux_x86_64/main.o] Error 1 /usr/share/ptlib/make/common.mak:96: recipe for target 'obj_linux_x86_64/main.o' failed make[2]: Leaving directory '/«PKGBUILDDIR»' make[1]: *** [opt] Error 2 /usr/share/ptlib/make/common.mak:289: recipe for target 'opt' failed make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [build-stamp] Error 2 debian/rules:13: recipe for target 'build-stamp' failed dpkg-buildpackage: error: debian/rules build gave error exit status 2 ---End Message--- ---BeginMessage--- * Matthias Klose d...@debian.org [2015-02-12 10:35]: make[2]: Entering directory '/«PKGBUILDDIR»' [CC] main.cxx In file included from /usr/include/ptlib/contain.h:42:0,
Bug#788442: marked as done (bcache-tools: fails to install: bcache-tools.postinst: update-initramfs: not found)
Your message dated Fri, 26 Jun 2015 15:20:37 + with message-id e1z8vqj-n3...@franck.debian.org and subject line Bug#788442: fixed in bcache-tools 1.0.8-2 has caused the Debian Bug report #788442, regarding bcache-tools: fails to install: bcache-tools.postinst: update-initramfs: not found 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.) -- 788442: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788442 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bcache-tools Version: 1.0.8-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package bcache-tools. (Reading database ... (Reading database ... 7695 files and directories currently installed.) Preparing to unpack .../bcache-tools_1.0.8-1_amd64.deb ... Unpacking bcache-tools (1.0.8-1) ... Setting up bcache-tools (1.0.8-1) ... /var/lib/dpkg/info/bcache-tools.postinst: 6: /var/lib/dpkg/info/bcache-tools.postinst: update-initramfs: not found dpkg: error processing package bcache-tools (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: bcache-tools This is a regression by lowering initramfs-tools from Depends to Recommends (#775674: bcache-tools should not depend on initramfs-tools) - now the maintainer scripts must check for update-initramfs existence before calling it. cheers, Andreas bcache-tools_1.0.8-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: bcache-tools Source-Version: 1.0.8-2 We believe that the bug you reported is fixed in the latest version of bcache-tools, 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 788...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Mohr da...@mcbf.net (supplier of updated bcache-tools 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, 11 Jun 2015 10:23:48 -0600 Source: bcache-tools Binary: bcache-tools Architecture: source amd64 Version: 1.0.8-2 Distribution: unstable Urgency: medium Maintainer: David Mohr da...@mcbf.net Changed-By: David Mohr da...@mcbf.net Description: bcache-tools - bcache userspace tools Closes: 788442 Changes: bcache-tools (1.0.8-2) unstable; urgency=medium . * Only run update-initramfs if installed. Fix dracut. (Closes: #788442) Checksums-Sha1: 7692e7aafb9e5ed14c6e42a11a1efbe48beee74d 1957 bcache-tools_1.0.8-2.dsc 2e80693c55b3256ef1daa68f3256f1aa25f64338 4596 bcache-tools_1.0.8-2.debian.tar.xz cb90fa0179cdf8442a7184c93ece4543207958a5 18346 bcache-tools_1.0.8-2_amd64.deb Checksums-Sha256: 3ecd4b3d4e4c9c17e8980a4119c40e99496a5facb3c90d9070fd60ef1203571c 1957 bcache-tools_1.0.8-2.dsc 536a5d45a6c5e4239c56373cb6669b6ea972908a69591b7f63d8fd8c6763b4df 4596 bcache-tools_1.0.8-2.debian.tar.xz f950fe3c6ee2674373cffc0cc3313ccfe51060492bea9a5be9b7b49c4ef4f501 18346 bcache-tools_1.0.8-2_amd64.deb Files: 76d7d891382c07212229802861863ab5 1957 utils optional bcache-tools_1.0.8-2.dsc 97afec386ca537e7e599267f4a045f65 4596 utils optional bcache-tools_1.0.8-2.debian.tar.xz e84e0f52c52179549518d974ba83648c 18346 utils optional bcache-tools_1.0.8-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVjWF4AAoJEL/srsug59jD/WkQAJ1Rrpg1k0146XulDUOvyEap +SNBTFa/jM63+GNwiwSahq+CMO6greYPMf+KRK0BX8XrAfrdwcwF0xGJ/afcoV3I G5mEF0Pq1Mflxkuhehk2CxPExqd/lRsclG9CKQiiw0Up2WeoWirwCUQLCNx+qlYk TfmA2JQpg8WpBqcZIiaKOpyfO+qB/954+M5d/CrkkY0syLwDvGH7Y6l8m16SMu1f j5mUVo8RGxoNbTurAmaInv6QgeT4KdiBw92PTB1+JpY24SntJPef3HCHkNVm8EgT W6qCGEX9ooXiES4hvvlomvuAxW7Z1bxPULIz6zW7rHuT5EYamxIzB2T+hzFxuG5x mnMTCf6OLdnXUeLdXFByffdm79jXD0eLClXGWddPFN9WzNfWMK7DxvqgfO4/Jd27 oQ6OA7H2hbBXoKZj5MJTSn/rk36fQRC8VovhfXzNyePYHzCh5ja+AUK45zSOOivY JEZ+k4C0hyieGEWHRSd2KAS1AGP8kYkC4/ghrrQDWP83+Vt9e4kIoImR2ngc+ht9
Bug#778104: gcc-5 / regina-normal
* Ben Burton b...@debian.org [2015-06-26 11:54]: I’d be happy if you could do another test rebuild to see if it’s still broken at your end, or if the problem has sorted itself out since the bug was filed back in February. I'm not Matthias Klose, but I just did a rebuild and it als works for me. I suggest you close the bug. -- Martin Michlmayr Linux for HP Helion OpenStack, Hewlett-Packard -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790043: mapnik: no longer builds python bindings
Source: mapnik Version: 3.0.0~rc3+ds-1 Severity: serious Hi, mapnik no longer builds the python bindings, but tilelite still depends on those. Something needs to be done here so that mapnik can be in a releasable state: either the bindings are brought back (possibly from a different source package) or codelite needs to be fixed / removed. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 789118 is forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=751544
Processing commands for cont...@bugs.debian.org: forwarded 789118 https://bugzilla.gnome.org/show_bug.cgi?id=751544 Bug #789118 [gnome-shell] Cannot unlock screen after upgrading GNOME if locked before upgrade Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=751544'. thanks Stopping processing here. Please contact me if you need assistance. -- 789118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789118 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#789668: marked as done (python-swiftclient-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/man/man1/swift.1.gz)
Your message dated Fri, 26 Jun 2015 13:51:06 + with message-id e1z8u26-0001rm...@franck.debian.org and subject line Bug#789668: fixed in python-swiftclient 1:2.4.0-3 has caused the Debian Bug report #789668, regarding python-swiftclient-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/man/man1/swift.1.gz 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.) -- 789668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-swiftclient-doc Version: 1:2.4.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 python-swiftclient-doc. Preparing to unpack .../python-swiftclient-doc_1%3a2.4.0-1_all.deb ... Unpacking python-swiftclient-doc (1:2.4.0-1) ... dpkg: error processing archive /var/cache/apt/archives/python-swiftclient-doc_1%3a2.4.0-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/swift.1.gz', which is also in package python-swiftclient 1:2.3.1-1 Errors were encountered while processing: /var/cache/apt/archives/python-swiftclient-doc_1%3a2.4.0-1_all.deb cheers, Andreas python-swiftclient=1%2.3.1-1_python-swiftclient-doc=1%2.4.0-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: python-swiftclient Source-Version: 1:2.4.0-3 We believe that the bug you reported is fixed in the latest version of python-swiftclient, 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. Thomas Goirand z...@debian.org (supplier of updated python-swiftclient 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, 26 Jun 2015 15:44:59 +0200 Source: python-swiftclient Binary: python-swiftclient python3-swiftclient python-swiftclient-doc Architecture: source all Version: 1:2.4.0-3 Distribution: experimental Urgency: medium Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org Changed-By: Thomas Goirand z...@debian.org Description: python-swiftclient - Client library for Openstack Swift API - Python 2.7 python-swiftclient-doc - Client library for Openstack Swift API - doc python3-swiftclient - Client library for Openstack Swift API - Python 3.x Closes: 789668 Changes: python-swiftclient (1:2.4.0-3) experimental; urgency=medium . * Added Breaks: + Replaces: of python-swiftclient in python-swiftclient-doc because the -doc package now contains the swift man page (Closes: #789668). Checksums-Sha1: 7c37911d23f087bfc32b715fe7ee9a3f5babf675 2652 python-swiftclient_2.4.0-3.dsc ec06e080f4828d72c96bcbba028b633e37390bfb 4416 python-swiftclient_2.4.0-3.debian.tar.xz 49e0623c68129e583733e5351257452900ad4943 41056 python-swiftclient-doc_2.4.0-3_all.deb 4fd72101660051f1e776ac2a237deb0346e9cd21 40434 python-swiftclient_2.4.0-3_all.deb 1e40b901fa9bdc61a934a12b1d08d8750d5dd042 40502 python3-swiftclient_2.4.0-3_all.deb Checksums-Sha256: b32bc172049ef1511895f71d4abccb80f73394ae0640b8ee4ea545a5ddc167ff 2652 python-swiftclient_2.4.0-3.dsc b47decda05ecbf5b43f7b433aa1c7da50ed5ae161230281691aaeca2b46f4133 4416 python-swiftclient_2.4.0-3.debian.tar.xz 9662f5997d1291accb5bf8f91a09aed2f19f22e526e70bef46fdaa3f10b3a0b8 41056 python-swiftclient-doc_2.4.0-3_all.deb 366d550aff84c4a58a63091a06d97038cebd9df960fc8f642069ea894c8f0b4f 40434 python-swiftclient_2.4.0-3_all.deb d473a742f3be69e3e76ad60c877fd57c2e91348160d193b9c92abe0a1ea678e4 40502 python3-swiftclient_2.4.0-3_all.deb Files: c6dc923654ece99f09c4a8875158d7e5 2652 python extra python-swiftclient_2.4.0-3.dsc d3f3279ba99bc40ba792e76cb9f216ed 4416 python extra
Bug#778074: Patch for GCC 5 build issue
* Eugen Dedu eugen.d...@univ-fcomte.fr [2015-06-26 12:23]: Thank you very much, I have uploaded it. I forgot to add your name in the changelog, sorry. No problem. Thanks for the quick fix! -- Martin Michlmayr Linux for HP Helion OpenStack, Hewlett-Packard -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789849: marked as done (FTBFS: missing build-dep on git(?))
Your message dated Fri, 26 Jun 2015 15:26:16 +
with message-id e1z8vwc-0002s5...@franck.debian.org
and subject line Bug#789849: fixed in python-scciclient 0.1.0-1
has caused the Debian Bug report #789849,
regarding FTBFS: missing build-dep on git(?)
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.)
--
789849: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: python-scciclient
Version: 0.0.1-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
The package fails to build in a clean chroot.
I believe this is because it assumes git(1) is present, and it isn't in the
build-deps nor build-essential.
pyversions: missing debian/pyversions file, fall back to supported versions
python setup.py clean -a
error in setup command: Error parsing /python-scciclient-0.0.1/setup.cfg:
OSError: [Errno 2] No such file or directory
dh_auto_clean: python setup.py clean -a returned exit code 1
debian/rules:12: recipe for target 'clean' failed
root@base:/python-scciclient-0.0.1# strace -ff -e execve 21 dpkg-buildpackage
| fgrep git
[pid 16699] execve(/bin/git, [git, rev-parse, --git-dir], [/* 89 vars
*/]) = -1 ENOENT (No such file or directory)
-- 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: python-scciclient
Source-Version: 0.1.0-1
We believe that the bug you reported is fixed in the latest version of
python-scciclient, 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.
Thomas Goirand z...@debian.org (supplier of updated python-scciclient 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, 26 Jun 2015 15:50:36 +0200
Source: python-scciclient
Binary: python-scciclient python3-scciclient python-scciclient-doc
Architecture: source all
Version: 0.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org
Changed-By: Thomas Goirand z...@debian.org
Description:
python-scciclient - Python ServerView Common Command Interface (SCCI) Client
Library
python-scciclient-doc - Python ServerView Common Command Interface (SCCI)
Client Library
python3-scciclient - Python ServerView Common Command Interface (SCCI) Client
Library
Closes: 789849
Changes:
python-scciclient (0.1.0-1) unstable; urgency=medium
.
* New upstream release.
* Added missing build-depends on openstack-pkg-tools and inconditionally
include pkgos.make. Also adds missing build-depends on python{3,}-pbr.
Thanks to Chris West for the bug report (Closes: #789849).
* Removed versions of build-depends already satisfied in Jessie/Trusty.
Checksums-Sha1:
39404697400369b051df7f725e426dc59f46f48e 2633 python-scciclient_0.1.0-1.dsc
62d787c64c77fa6de1fcf533ae36734188a78aa0 18308
python-scciclient_0.1.0.orig.tar.xz
a42e9716fedb3830cc83c6a87fcfba89f5cef919 2948
python-scciclient_0.1.0-1.debian.tar.xz
fcf3c00e0272e46e386167690f11f5facc231788 25882
python-scciclient-doc_0.1.0-1_all.deb
c8ac151350a5fe47e1cf33f7a58c91f479dacd08 8666 python-scciclient_0.1.0-1_all.deb
90cc833e8a694877c6f8975e1da98acc9d12a848 8756
python3-scciclient_0.1.0-1_all.deb
Checksums-Sha256:
57bd4015f33a32c9eec6e5b30d2b093a459e5fe62b8b50b5a6d033fc6e38bb73 2633
python-scciclient_0.1.0-1.dsc
ef18511a37fc0e8b8e1190a0bf9c0f15a98be0b75ff91494241c9fc4a64adc9e 18308
python-scciclient_0.1.0.orig.tar.xz
873a70f754a6f5da5899221d22203b683c657ddd037d20b4dbe41860e5ae8e94 2948
python-scciclient_0.1.0-1.debian.tar.xz
c47ccf4c1721dbaa1f26baa375fbd174fda05cdaca3e863643382c9bf075a746 25882
python-scciclient-doc_0.1.0-1_all.deb
Bug#777955: liblas: ftbfs with GCC-5
Hi Matthias, On 02/13/2015 10:48 PM, Sebastiaan Couwenberg wrote: This looks like looks like #778220. The boost issue (#778220) is no longer a problem. But unfortunately liblas still fails to build with GCC 5, now due to undefined references to Boost methods. See for example this build log: http://linuxminded.nl/tmp/liblas-gcc5.txt An example: undefined reference to `boost::program_options::invalid_option_value::invalid_option_value(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' This seems similar to the lucene++ issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777993#27 The comments hints to the need to rebuild boost on top of the new C++ ABI. Can you shed some light how to best fix this issue with liblas? 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
Processed: reassign 784270 to python2.7, closing 784270
Processing commands for cont...@bugs.debian.org:
# Reassign to the correct package to convince BTS that it's fixed.
reassign 784270 python2.7 2.7.9-4
Bug #784270 {Done: Matthias Klose d...@debian.org} [src:python-docutils]
python-docutils: FTBFS: test_invalid_raw_xml fails with TypeError
Bug reassigned from package 'src:python-docutils' to 'python2.7'.
No longer marked as found in versions python-docutils/0.12+dfsg-1.
No longer marked as fixed in versions python2.7/2.7.9-5.
Bug #784270 {Done: Matthias Klose d...@debian.org} [python2.7]
python-docutils: FTBFS: test_invalid_raw_xml fails with TypeError
Marked as found in versions python2.7/2.7.9-4.
close 784270 2.7.9-5
Bug #784270 {Done: Matthias Klose d...@debian.org} [python2.7]
python-docutils: FTBFS: test_invalid_raw_xml fails with TypeError
Marked as fixed in versions python2.7/2.7.9-5.
Bug #784270 {Done: Matthias Klose d...@debian.org} [python2.7]
python-docutils: FTBFS: test_invalid_raw_xml fails with TypeError
Bug 784270 is already marked as done; not doing anything.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
784270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784270
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#790043: mapnik: no longer builds python bindings
On 06/26/2015 07:26 PM, Jérémy Lal wrote: indeed upstream moved python bindings development to a separate project https://github.com/mapnik/python-mapnik Anyone interested in helping ? I'm not used to packaging python modules. Yes, I'm started to work on a python-mapnik package from that git repository. I was unstable to use pypi.debian.net despite there being a 0.1 release on pypi.python.org. python-mapnik doesn't support Python 3, so that will need to be fixed for it to have a future post-buster. 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#777930: ksh: ftbfs with GCC-5
* Matthias Klose d...@debian.org, 2015-02-12, 10:32: mamake: *** exit code 1 making cmd/ksh93 package: make done at Sat Feb 7 09:11:22 UTC 2015 in /ÂŤBUILDDIRÂť/ksh-93u+20120801/arch/linux.i386-64 touch build-stamp fakeroot debian/rules binary-arch dh_testdir dh_testroot dh_installdirs install -p-o root -g root -m 755 -s arch/linux.i386-64/bin/ksh debian/ksh/bin/ksh93 install: cannot stat 'arch/linux.i386-64/bin/ksh': No such file or directory make: *** [install] Error 1 The upstream build system seems to be ignoring errors. :/ I believe the culprit appears much earlier in the build log: + cc -D_BLD_DLL -fPIC -D_BLD_ast -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I. -I/«BUILDDIR»/ksh-93u+20120801/src/lib/libast -Icomp -I/«BUILDDIR»/ksh-93u+20120801/src/lib/libast/comp -Iinclude -I/«BUILDDIR»/ksh-93u+20120801/src/lib/libast/include -Istd -I/«BUILDDIR»/ksh-93u+20120801/src/lib/libast/std -D_PACKAGE_ast -c /«BUILDDIR»/ksh-93u+20120801/src/lib/libast/comp/tmpnam.c /«BUILDDIR»/ksh-93u+20120801/src/lib/libast/comp/tmpnam.c: In function 'tmpnam': /«BUILDDIR»/ksh-93u+20120801/src/lib/libast/comp/tmpnam.c:48:14: error: storage size of 'buf' isn't known static char buf[L_tmpnam]; ^ /«BUILDDIR»/ksh-93u+20120801/src/lib/libast/comp/tmpnam.c:50:39: error: expected expression before ',' token return pathtemp(s ? s : buf, L_tmpnam, NiL, tn, NiL); ^ mamake [lib/libast]: *** exit code 1 making tmpnam.o -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789541: abtransfers: Crash after successful money transfer
Dear Paul, On Friday 26 June 2015 08:42:19 Paul Menzel wrote: [...] Which is the character that could not be written at the bad history.txt and maybe caused the crash? If I know this I could try to reproduce it here and maybe could fix it. The name of the account has umlauts in it: SG Friedrichshain Grün-Weiß 90 e. V.. Looking at the newly written `history.ctx` with only three transactions, it looks like the umlauts are recoded during each write. (The most recent entry is at the top.) char localName=SG Friedrichshain Gr%C3%BCn Wei%C3%9F char category=JobStatus%3A 5, JobType%3A 16 char localName=SG Friedrichshain Gr%C3%83%C2%BCn Wei%C3%83%C2%9F char category=JobStatus%3A 5, JobType%3A 16 char localName=SG Friedrichshain Gr%C3%83%C2%83%C3%82%C2%BCn Wei%C3%83%C2%83%C3%82%C2%9F char category=JobStatus%3A 5, JobType%3A 16 So with not a big number of transaction, that file gets pretty big as the `localName` lines get bigger after each transaction. In the faulty file the longest line has 12582962 columns. This probably causes the assertion in libgwenhywfar60 4.14.0-1. 3:2015/06/22 08-46-31:gwen(11198):buffer.c: 314: Size is beyond hard limit (1677727416777216) OK, this is definitive the cause for the crash! But it is even worse: The history is saved when a transaction was made and also when the program is closed! I simply edited a history entry at my own file with your 'localName' value and when I closed the program the history was saved and the value for 'localName' was saved as twice as big as before. Therefore the crash could also happen when you open and close the program x times. I will try to figure out why this happens. It could be that a wrong encoding is used when accessing the AqBanking functions. I will fix this, but it could take some time. In the meantime a workaround for you could be that you replace the umlauts at the owner name of the AqBanking account name or that you manually delete every transfer that was made from the history. Thank you very much for this information. Patrick Wacker -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790043: mapnik: no longer builds python bindings
2015-06-26 16:53 GMT+02:00 Emilio Pozuelo Monfort po...@debian.org: Source: mapnik Version: 3.0.0~rc3+ds-1 Severity: serious Hi, mapnik no longer builds the python bindings, but tilelite still depends on those. Something needs to be done here so that mapnik can be in a releasable state: either the bindings are brought back (possibly from a different source package) or codelite needs to be fixed / removed. Emilio Hello, indeed upstream moved python bindings development to a separate project https://github.com/mapnik/python-mapnik Anyone interested in helping ? I'm not used to packaging python modules. Jérémy.
Bug#769350: prelink: statically linked against libc6 without a Built-Using: field
* Aurelien Jarno aure...@debian.org, 2014-11-13, 00:15: prelink provides /usr/sbin/prelink.bin which is statically linked against libc6. According to Debian Policy §7.8 such a package MUST list the glibc source package (and possibly others) in the Built-Using: field. Beware that generating Built-Using for glibc is tricky, because the binary package names varies with architecture. Please take a look on src:sash for an example how to do it right. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: notfixed 666502 in 2010c, fixed 666502 in 2011h-0.1
Processing commands for cont...@bugs.debian.org:
# correct version information
notfixed 666502 2010c
Bug #666502 {Done: Scott Kitterman deb...@kitterman.com} [python-tz]
python-tz: returns incorrect UTC offsets
There is no source info for the package 'python-tz' at version '2010c' with
architecture ''
Unable to make a source version for version '2010c'
No longer marked as fixed in versions 2010c.
fixed 666502 2011h-0.1
Bug #666502 {Done: Scott Kitterman deb...@kitterman.com} [python-tz]
python-tz: returns incorrect UTC offsets
Marked as fixed in versions python-tz/2011h-0.1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
666502: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666502
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: retitle 765567 to docbook-xsl: please avoid recursion in string.subst
Processing commands for cont...@bugs.debian.org: retitle 765567 docbook-xsl: please avoid recursion in string.subst Bug #765567 [docbook-xsl] Please use non-recursive version Changed Bug title to 'docbook-xsl: please avoid recursion in string.subst' from 'Please use non-recursive version' thanks Stopping processing here. Please contact me if you need assistance. -- 765567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765567 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: tagging 747958
Processing commands for cont...@bugs.debian.org: tags 747958 + fixed-upstream - patch Bug #747958 [gimp-help] FTBFS: parser error : Start tag expected, '' not found Added tag(s) fixed-upstream. Bug #747958 [gimp-help] FTBFS: parser error : Start tag expected, '' not found Removed tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 747958: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747958 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#790077: emoslib: FTBFS on most architectures: -mcmodel=medium problematic
Source: emoslib Version: 2:4.0.3+dfsg.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of emoslib for most Linux architectures have been failing because it always specifies the non-portable flag -mcmodel=medium. Judging by the ppc64el error I'll report separately, you might have to write most of these architectures off, but you could first try to do without the flag. * On most architectures, GCC doesn't accept -mcmodel at all: error: unrecognized command line option '-mcmodel=medium' * On arm64, it accepts -mcmodel in general, but not -mcmodel=medium: error: unrecognized argument in option '-mcmodel=medium' note: valid arguments to '-mcmodel=' are: large small tiny * On i386 and (32-bit) powerpc, GCC says -mcmodel is only available for 64-bit targets: error: code model 'medium' not supported in the 32 bit mode 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#790078: emoslib: FTBFS on ppc64el: relocation overflows
Source: emoslib Version: 2:4.0.3+dfsg1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) The ppc64el build of emoslib failed with link errors: /usr/bin/gfortran -fPIC -ffixed-line-length-none -fcray-pointer -fno-second-underscore -Wuninitialized -DSHAREDMEMORY -O2 -mtune=native -Wl,-z,relro -Wl,--disable-new-dtags -shared -Wl,-soname,libemos.so.0d -o ../lib/libemos.so.0d CMakeFiles/emos_sp_shared.dir/__/libemos_version.c.o CMakeFiles/emos_sp_shared.dir/__/interpolation/dummy.F.o CMakeFiles/emos_sp_shared.dir/__/interpolation/dummy2.F.o CMakeFiles/emos_sp_shared.dir/__/interpolation/areachk.F.o CMakeFiles/emos_sp_shared.dir/__/interpolation/estima.F.o ... CMakeFiles/emos_sp_shared.dir/__/grib_api_merging/intuvs2.c.o -lgrib_api_f90 -lgrib_api_f77 -lgrib_api -Wl,-rpath,\$ORIGIN/../lib CMakeFiles/emos_sp_shared.dir/__/interpolation/sharedll.c.o: In function `sharedll_': /«BUILDDIR»/emoslib-4.0.3+dfsg.1/interpolation/sharedll.c:113:(.text+0x114): relocation truncated to fit: R_PPC64_TOC16_HA against `.bss' CMakeFiles/emos_sp_shared.dir/__/interpolation/sharedgg.c.o: In function `sharedgg_': /«BUILDDIR»/emoslib-4.0.3+dfsg.1/interpolation/sharedgg.c:111:(.text+0xe4): relocation truncated to fit: R_PPC64_TOC16_HA against `.bss' CMakeFiles/emos_sp_shared.dir/__/interpolation/jopnggsm.c.o: In function `jopnggsm_': /«BUILDDIR»/emoslib-4.0.3+dfsg.1/interpolation/jopnggsm.c:223:(.text+0xf8): relocation truncated to fit: R_PPC64_TOC16_HA against `.bss' /«BUILDDIR»/emoslib-4.0.3+dfsg.1/interpolation/jopnggsm.c:223:(.text+0x13c): relocation truncated to fit: R_PPC64_TOC16_HA against `.bss' /«BUILDDIR»/emoslib-4.0.3+dfsg.1/interpolation/jopnggsm.c:236:(.text+0x248): relocation truncated to fit: R_PPC64_TOC16_HA against `.bss'+8 /«BUILDDIR»/emoslib-4.0.3+dfsg.1/interpolation/jopnggsm.c:319:(.text+0x40c): relocation truncated to fit: R_PPC64_TOC16_HA against `.bss'+140 /«BUILDDIR»/emoslib-4.0.3+dfsg.1/interpolation/jopnggsm.c:319:(.text+0x420): relocation truncated to fit: R_PPC64_TOC16_HA against `.bss'+148 /«BUILDDIR»/emoslib-4.0.3+dfsg.1/interpolation/jopnggsm.c:399:(.text+0x528): relocation truncated to fit: R_PPC64_TOC16_HA against `.bss'+148 /«BUILDDIR»/emoslib-4.0.3+dfsg.1/interpolation/jopnggsm.c:331:(.text+0x62c): relocation truncated to fit: R_PPC64_TOC16_HA against `.bss'+140 /«BUILDDIR»/emoslib-4.0.3+dfsg.1/interpolation/jopnggsm.c:331:(.text+0x640): relocation truncated to fit: R_PPC64_TOC16_HA against `.bss'+148 /«BUILDDIR»/emoslib-4.0.3+dfsg.1/interpolation/jopnggsm.c:274:(.text+0x708): additional relocation overflows omitted from the output collect2: error: ld returned 1 exit status make[3]: *** [lib/libemos.so.0d] Error 1 You might try going to -mcmodel=large there, bearing in mind that -mcmodel is generally non-portable (#790077). 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#777933: marked as done (lgeneral: ftbfs with GCC-5)
Your message dated Fri, 26 Jun 2015 19:50:07 + with message-id e1z8zdx-00085q...@franck.debian.org and subject line Bug#777933: fixed in lgeneral 1.2.6-2 has caused the Debian Bug report #777933, regarding lgeneral: 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.) -- 777933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:lgeneral Version: 1.2.3+dfsg-3 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/lgeneral_1.2.3+dfsg-3_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 [...] config.status: executing po-directories commands config.status: creating po/lgeneral/POTFILES config.status: creating po/lgeneral/Makefile config.status: executing po-lgeneral commands config.status: executing po-pg commands make[1]: Leaving directory '/«BUILDDIR»/lgeneral-1.2.3+dfsg' dh_auto_build -a -O--parallel make[1]: Entering directory '/«BUILDDIR»/lgeneral-1.2.3+dfsg' make all-recursive make[2]: Entering directory '/«BUILDDIR»/lgeneral-1.2.3+dfsg' Making all in intl make[3]: Entering directory '/«BUILDDIR»/lgeneral-1.2.3+dfsg/intl' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/«BUILDDIR»/lgeneral-1.2.3+dfsg/intl' Making all in util make[3]: Entering directory '/«BUILDDIR»/lgeneral-1.2.3+dfsg/util' gcc -DHAVE_CONFIG_H -DDATADIR=\/usr/share/games\ -DPREFIX=\/usr\ -I. -I. -I.. -I.. -D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wall -c localize.c gcc -DHAVE_CONFIG_H -DDATADIR=\/usr/share/games\ -DPREFIX=\/usr\ -I. -I. -I.. -I.. -D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wall -c hashtable.c gcc -DHAVE_CONFIG_H -DDATADIR=\/usr/share/games\ -DPREFIX=\/usr\ -I. -I. -I.. -I.. -D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wall -c hashtable_itr.c gcc -DHAVE_CONFIG_H -DDATADIR=\/usr/share/games\ -DPREFIX=\/usr\ -I. -I. -I.. -I.. -D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wall -c hashtable_utility.c gcc -DHAVE_CONFIG_H -DDATADIR=\/usr/share/games\ -DPREFIX=\/usr\ -I. -I. -I.. -I.. -D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wall -c paths.c gcc -DHAVE_CONFIG_H -DDATADIR=\/usr/share/games\ -DPREFIX=\/usr\ -I. -I. -I.. -I.. -D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wall -c portability.c hashtable_itr.c:29:1: error: redefinition of 'hashtable_iterator_key' hashtable_iterator_key(struct hashtable_itr *i) ^ In file included from hashtable_itr.c:5:0: hashtable_itr.h:32:1: note: previous definition of 'hashtable_iterator_key' was here hashtable_iterator_key(struct hashtable_itr *i) ^ hashtable_itr.c:33:1: error: redefinition of 'hashtable_iterator_value' hashtable_iterator_value(struct hashtable_itr *i) ^ In file included from hashtable_itr.c:5:0: hashtable_itr.h:41:1: note: previous definition of 'hashtable_iterator_value' was here hashtable_iterator_value(struct hashtable_itr *i) ^ make[3]: *** [hashtable_itr.o] Error 1 make[3]: *** Waiting for unfinished jobs Makefile:304: recipe for target 'hashtable_itr.o' failed make[3]: Leaving directory '/«BUILDDIR»/lgeneral-1.2.3+dfsg/util' make[2]: *** [all-recursive] Error 1 Makefile:358: recipe for target 'all-recursive' failed make[2]: Leaving directory
Bug#790079: emoslib: FTBFS on the Hurd: ecBuild is untested for this operating system
Source: emoslib Version: 2:4.0.3+dfsg.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) The Hurd build of emoslib failed: -- Detecting C compile features CMake Error at cmake/ecbuild_check_os.cmake:336 (message): ecBuild is untested for this operating system: [GNU] -- refusing to continue. Disable this check with -DDISABLE_OS_CHECK=ON Call Stack (most recent call first): cmake/ecbuild_system.cmake:264 (include) CMakeLists.txt:20 (include) This flag might also be necessary on kFreeBSD, once dpkg-dev bug #790073 is resolved. 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: tagging 778029
Processing commands for cont...@bugs.debian.org: # I can't reproduce it either tags 778029 + unreproducible Bug #778029 [src:nsis] nsis: ftbfs with GCC-5 Added tag(s) unreproducible. thanks Stopping processing here. Please contact me if you need assistance. -- 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#789118: No issues with clean upgrade
Control: found -1 3.14.4-1 On 22/06/15 02:36, Michel Dänzer wrote: On 22.06.2015 03:39, Josh Triplett wrote: On Sun, Jun 21, 2015 at 07:52:10PM +0200, Michael Biebl wrote: Am 20.06.2015 um 08:54 schrieb Michel Dänzer: On Thu, 18 Jun 2015 21:19:20 +0400 George Hertz george...@gmail.com wrote: I've just upgraded to 3.16 on unstable, but restarted the system right after the update finished. No problems unlocking. Yeah, the problem only occurs with a gnome-shell which is already running during the upgrade. However, the problem also occurs when only locking the session after the upgrade has completed. One possible workaround after the upgrade is killall -HUP gnome-shell gnome-settings-daemon I didn't know you could HUP gnome-shell to unlock the session; that's useful to know. Sending SIGHUP to gnome-shell only is enough to be able to unlock the session, but gnome-settings-daemon also needs to be restarted, or some things such as keyboard shortcuts don't work properly in the new gnome-shell. Unfortuantely we don't have a proper mechanism to restart programs in the desktop session. Using killall in postinst is something I'd be wary about. It's also not OK to unexpectedly unlock someone's session due to a concurrent upgrade; can't unlock my session is bad, but unlocked my screen during upgrade is a critical security bug. SIGHUP doesn't unlock the session, it just makes gnome-shell restart itself, after which the upgraded version of gnome-shell runs and unlocking the session works normally. This bug is preventing testing migration, which is causing a lot of other bugs because of version mismatches between gtk+, gnome-settings-daemon and mutter/gnome-shell (see e.g. #789618, #789891, #789866, #789725, #789575, #789484...). I've talked about it to some team members and we agreed that this is RC, but that it'd be better to let gnome-shell migrate for the time being. So I'm doing some trick to let it migrate, but we'll fix this. Josh, any chance you can try the SIGHUP approach and confirm that solves your problem and doesn't cause any other undesired effect? Thanks, Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#789118: No issues with clean upgrade
Processing control commands: found -1 3.14.4-1 Bug #789118 [gnome-shell] Cannot unlock screen after upgrading GNOME if locked before upgrade Marked as found in versions gnome-shell/3.14.4-1. -- 789118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789118 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#778104: gcc-5 / regina-normal
I’ve just tried to reproduce this, and I can’t - regina-normal seems to be building fine under current sid/amd64 with gcc-5 and g++-5 installed and the relevant CC / CXX environment variables set. The build log confirms that gcc-5 and g++-5 are indeed being called during the build. I’d be happy if you could do another test rebuild to see if it’s still broken at your end, or if the problem has sorted itself out since the bug was filed back in February. Thanks - Ben. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790016: qscintilla2: packages depend on unavailable libq{, t5}scintilla2 instead of libq{, t5}scintilla2-12
Source: qscintilla2 Version: 2.9+dfsg-2 Severity: serious e.g. libqt5scintilla2-designer: libqt5scintilla2 python-qscintilla2: libqscintilla2 python3-pyqt4.qsci: libqscintilla2 Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762852: marked as done (libprocps4-dev: broken symlink /usr/lib/i386-linux-gnu/libprocps.so)
Your message dated Fri, 26 Jun 2015 10:02:16 + with message-id e1z8qse-0006oq...@franck.debian.org and subject line Bug#762852: fixed in procps 2:3.3.10-2 has caused the Debian Bug report #762852, regarding libprocps4-dev: broken symlink /usr/lib/i386-linux-gnu/libprocps.so 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.) -- 762852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libprocps4-dev Version: 1:3.3.10-1 Severity: serious Packages linking with -lprocps are going to be linked statically or depend on libprocps3 instead of libprocps4, depending on whether the latter is installed in the build environment: , | $ file /usr/lib/i386-linux-gnu/libprocps.so | /usr/lib/i386-linux-gnu/libprocps.so: broken symbolic link to `/lib/i386-linux-gnu/libprocps.so.3' ` -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.16.3-nouveau (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libprocps4-dev depends on: ii libprocps4 1:3.3.10-1 libprocps4-dev recommends no packages. libprocps4-dev suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: procps Source-Version: 2:3.3.10-2 We believe that the bug you reported is fixed in the latest version of procps, 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 762...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Craig Small csm...@debian.org (supplier of updated procps 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: Sun, 14 Jun 2015 15:00:30 +1000 Source: procps Binary: procps libprocps4 libprocps4-dev Architecture: source amd64 Version: 2:3.3.10-2 Distribution: unstable Urgency: medium Maintainer: Craig Small csm...@debian.org Changed-By: Craig Small csm...@debian.org Description: libprocps4 - library for accessing process information from /proc libprocps4-dev - library for accessing process information from /proc procps - /proc file system utilities Closes: 732494 762852 766292 Changes: procps (2:3.3.10-2) unstable; urgency=medium . * libprocps4-dev: fixed symbolic link from .so.3 to .so.4 Closes: #762852 * Removed mention of fork and update site url Closes: #766292 * Update copyright to new format Closes: #732494 Checksums-Sha1: 84fd1a913166e5dd768366d34751513e8f93d885 2120 procps_3.3.10-2.dsc 26a58f2c87e2f00557d1c9f412a4f7f4899c27c2 26496 procps_3.3.10-2.debian.tar.xz c8f68ccfaed8e09a802ca06c767448d0181b9077 69742 libprocps4-dev_3.3.10-2_amd64.deb 57b38e9a7dc78530c90e07fd315090e8526b97e9 58342 libprocps4_3.3.10-2_amd64.deb 1adf2d55e2b8664745a9f389b19f3ad61b7a023a 245218 procps_3.3.10-2_amd64.deb Checksums-Sha256: 5fc36a3300f66fe874f447fd90ebd7494ab348544e8aa777c560e6b6d8a1423c 2120 procps_3.3.10-2.dsc 9c8b669347d612a7db9ea4b7322c85ac70cc9459bcc5c6788d8bd003b715d928 26496 procps_3.3.10-2.debian.tar.xz 05ea18d6448bc9a8a1398a60a9485b931729d08e161e89d72d77b28a2159f1a7 69742 libprocps4-dev_3.3.10-2_amd64.deb 360715238e4fe1507de593ba76a93fa37964a777d1e43d8c25d6b72e5d4ff376 58342 libprocps4_3.3.10-2_amd64.deb 88537039747ed9dc57c093c58bc4d0745877368c20650ba84943e10dcdae801f 245218 procps_3.3.10-2_amd64.deb Files: 824c6457b4142e3c9dbe0cb1d6dea18e 2120 admin important procps_3.3.10-2.dsc ad7c9874f4543d225b2449dab1d9176b 26496 admin important procps_3.3.10-2.debian.tar.xz 6601dc61021be897be8e1f2055bdbc48 69742 libdevel optional libprocps4-dev_3.3.10-2_amd64.deb fd7f04c279358e277671a05e07468d02 58342 libs important libprocps4_3.3.10-2_amd64.deb 44309edd41fbbd624ab6bf5efda468a8 245218 admin important procps_3.3.10-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJVfRHQAAoJEDk4+WvfUP6lV9AP/2Awq3MQkB0nTHTEAv7PlGex FhHaSAJO/MdzM/nHBeM8eAkBy3Vk/kSVxVRNMkqmanvSqSFezOT/oBVYwwXudzbe 2ixedp1/BCybzk40bmBiIbkDjoM8WyfUj4fBX0vsmfTuB1HToId5C6Qqb7JyjWz2
Bug#788520: marked as done (libobrender 3.6.0-1 is binary incompatible with previous versions but no ABI changed)
Your message dated Fri, 26 Jun 2015 10:02:13 +
with message-id e1z8qsb-0006md...@franck.debian.org
and subject line Bug#788520: fixed in openbox 3.6.0-2
has caused the Debian Bug report #788520,
regarding libobrender 3.6.0-1 is binary incompatible with previous versions but
no ABI changed
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.)
--
788520: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788520
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libobrender29
Version: 3.6.0-1
Severity: grave
This is actually an upstream bug but it is a problem because it makes any
of packages dependent on libobrender29 broken completely, any application
compiled using libobrender29 version 3.5.x will crash using libobrender29
version 3.6.0-1.
There are only two ways to deal with this problem:
1) patch upstream file configure.ac in openbox source package changing
the values:
RR_MICRO_VERSION=31
-RR_INTERFACE_AGE=2
-RR_BINARY_AGE=2
+RR_INTERFACE_AGE=0
+RR_BINARY_AGE=0
RR_VERSION=$RR_MAJOR_VERSION.$RR_MINOR_VERSION
which will bump ABI to 31 (therefore libobrender29 becomes libobrender31)
and make sure libobrender29 vesrion 3.6.0-1 never come into testing.
2) request a bump version from every dependent package where the package
will set dependency on libobrender29 (= 3.6.0-1) and in libobrender29 set
Breaks: the_package ( new_version)
against each dependent package (or otherwise package manager would never
upgrade any dependent package).
I believe the second way is ugly and inacceptable one.
I've mailed to upstream list about broken ABI and I hope they will
release fixed version shortly, until then I suggest to fix the openbox
source package instead.
---End Message---
---BeginMessage---
Source: openbox
Source-Version: 3.6.0-2
We believe that the bug you reported is fixed in the latest version of
openbox, 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 788...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mateusz Łukasik mat...@linuxmint.pl (supplier of updated openbox 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, 12 Jun 2015 19:31:23 +0200
Source: openbox
Binary: openbox libobt4 libobrender31 openbox-dev gnome-panel-control
openbox-gnome-session openbox-kde-session
Architecture: source amd64 all
Version: 3.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Mateusz Łukasik mat...@linuxmint.pl
Changed-By: Mateusz Łukasik mat...@linuxmint.pl
Description:
gnome-panel-control - command line utility to invoke GNOME panel run
dialog/menu
libobrender31 - rendering library for openbox themes
libobt4- parsing library for openbox
openbox- standards-compliant, fast, light-weight and extensible window man
openbox-dev - development files for the openbox window manager
openbox-gnome-session - command line utility to run Openbox as GNOME session
openbox-kde-session - command line utility to run Openbox as KDE SC session
Closes: 788520
Changes:
openbox (3.6.0-2) unstable; urgency=medium
.
* debian/openbox.post{rm,inst}:
+ Fix command-with-path-in-maintainer-script lintian warning.
* Change libobrender ABI from 29 to 31: (Closes: #788520)
+ Add debian/patches/788520_change_libobrender_abi.patch
+ Rename debian/libobrender29.install to debian/libobrender31.install.
+ Add updated symbols file debian/libobrender31.symbols.
* Change libobt ABI from 2 to 4:
+ Add debian/patches/788520_change_libobt_abi.patch.
+ Rename debian/libobt2.install to debian/libobt4.install.
+ Add updated symbols file debian/libobt4.symbols.
* debian/control:
+ Update names of binary packages to reflect new so versions.
Checksums-Sha1:
454f2e789f944d7cd573a962e929f86f06f438e5 2434 openbox_3.6.0-2.dsc
767e76e9d4b35a44bc0e00a9e504f69802403d8e 35884 openbox_3.6.0-2.debian.tar.xz
a2afebbcfab2ec9c7516925456c4c83dd785de53 44252
gnome-panel-control_3.6.0-2_amd64.deb
75413088a8423c32b419766cea22aeedd62711eb 75022 libobrender31_3.6.0-2_amd64.deb
bf553e4d9bf2ac84156aac4d26a07d6624fbdca5 64690 libobt4_3.6.0-2_amd64.deb
Processed: Re: Bug#778065: pktools: ftbfs with GCC-5
Processing control commands: forwarded -1 https://savannah.nongnu.org/bugs/index.php?45416 Bug #778065 [src:pktools] pktools: ftbfs with GCC-5 Set Bug forwarded-to-address to 'https://savannah.nongnu.org/bugs/index.php?45416'. tags -1 pending Bug #778065 [src:pktools] pktools: ftbfs with GCC-5 Added tag(s) pending. -- 778065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778065 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#790019: texinfo: depends on gawk, but texindex calls mawk
Package: texinfo Version: 5.9.96.dfsg.1-1 Severity: serious I read bug #790004 and wondered where gawk is actually called… turns out it isn't, since on i386 (and most likely on other architectures) texindex actually calls mawk: --8---cut here---start-8--- --- amd64/texindex 2015-06-26 11:44:36.471766815 +0200 +++ i386/texindex 2015-06-25 18:10:11.0 +0200 @@ -44,7 +44,7 @@ # # else use configured value for awk. if test -z $awk_binary; then - awk_binary=gawk + awk_binary=mawk fi # # that should never be empty, but just in case, else fall back to plain --8---cut here---end---8--- Remedy: either add a build dependency on gawk, or, if the outcome of #790004 is that any awk implementation will do, configure with AWK=awk. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 4.0.6-nouveau (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages texinfo depends on: ii gawk1:4.1.1+dfsg-1 ii libintl-perl1.23-1 ii libtext-unidecode-perl 1.22-1 ii libxml-libxml-perl 2.0116+dfsg-4 texinfo recommends no packages. Versions of packages texinfo suggests: ii texinfo-doc-nonfree 5.9.96-1 ii texlive-base 2015.20150625-1 ii texlive-generic-recommended 2015.20150625-1 ii texlive-latex-base 2015.20150625-1 -- 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#778065: pktools: ftbfs with GCC-5
Control: forwarded -1 https://savannah.nongnu.org/bugs/index.php?45416
Control: tags -1 pending
Hi Matthias,
Thanks for your work on GCC.
On 02/12/2015 11:35 AM, Matthias Klose wrote:
In file included from pkfssvm.cc:28:0:
../../src/algorithms/FeatureSelector.h:52:177: error: redeclaration of
'double FeatureSelector::forwardUnivariate(std::vectorVector2dT ,
CostFactory, std::listint, int, short int)' may not have default
arguments [-fpermissive]
templateclass T double FeatureSelector::forwardUnivariate(std::vector
Vector2dT v, CostFactory theCostFactory, std::listint subset, int
maxFeatures=0, short verbose){
^
../../src/algorithms/FeatureSelector.h:111:167: error: redeclaration of
'double FeatureSelector::forward(std::vectorVector2dT , CostFactory,
std::listint, int, short int)' may not have default arguments
[-fpermissive]
templateclass T double FeatureSelector::forward(std::vector Vector2dT
v, CostFactory theCostFactory, std::listint subset, int maxFeatures=0,
short verbose){
I've patched this issue and forwarded it upstream. A new revision for
unstable will be uploaded soon.
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#790021: apertium: build-depends on liblttoolbox3-3.1-0-dev but it is superceded
Package: apertium Version: 3.1.0-2 Severity: serious apertium has a fixed build-dependency on liblttoolbox3-3.1-0-dev but it is superceded by liblttoolbox3-3.3-dev. That transition is now blocked. Please update the dependency. -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (SMP w/4 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#790022: tahoe-lafs: Depends on python2.6 which is no more available in unstable for 2 years
Package: tahoe-lafs Version: 1.10.1-1 Severity: serious Dear Maintainer, tahoe-lafs can't be upgraded in Sid (at least on amd64) as the new package release depends on python2.6 (while the previous package didn't) which is no more available in Sid for two years now. (The information below shows dependencies for the package version 1.10.0-2.) -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tahoe-lafs depends on: ii net-tools 1.60-26+b1 ii python 2.7.9-1 ii python-crypto 2.6.1-5+b2 ii python-foolscap0.6.5-1 ii python-mock1.0.1-3 ii python-nevow 0.11.1-1 ii python-openssl 0.14-1 ii python-pkg-resources 17.0-1 ii python-pyasn1 0.1.7-1 ii python-pycryptopp 0.6.0.20120313-1 ii python-setuptools 17.0-1 ii python-simplejson 3.7.3-1 ii python-twisted 14.0.2-3 ii python-zfec1.4.5-2 ii python-zope.interface 4.1.1-3.1 tahoe-lafs recommends no packages. tahoe-lafs suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788524: marked as done (lxappearance-obconf depends on broken libobrender29)
Your message dated Sat, 27 Jun 2015 01:48:48 + with message-id e1z8fee-0001nl...@franck.debian.org and subject line Bug#788524: fixed in lxappearance-obconf 0.2.2-3 has caused the Debian Bug report #788524, regarding lxappearance-obconf depends on broken libobrender29 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.) -- 788524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788524 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: lxappearance-obconf Version: 0.2.2-2 Severity: grave The latest package in sid is built against openbox library libobrender29 version 3.6.0-1 with broken ABI (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788520) and therefore version 0.2.2-2 of lxappearance-obconf should never come to the testing distribution until mentioned problem is fixed. ---End Message--- ---BeginMessage--- Source: lxappearance-obconf Source-Version: 0.2.2-3 We believe that the bug you reported is fixed in the latest version of lxappearance-obconf, 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 788...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andriy Grytsenko and...@rep.kiev.ua (supplier of updated lxappearance-obconf 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, 26 Jun 2015 23:09:42 +0300 Source: lxappearance-obconf Binary: lxappearance-obconf lxappearance-obconf-dbg Architecture: source amd64 Version: 0.2.2-3 Distribution: unstable Urgency: low Maintainer: Debian LXDE Maintainers pkg-lxde-maintain...@lists.alioth.debian.org Changed-By: Andriy Grytsenko and...@rep.kiev.ua Description: lxappearance-obconf - LXDE GTK+ theme switcher (plugin) lxappearance-obconf-dbg - LXDE GTK+ theme switcher (plugin - debug) Closes: 788524 Changes: lxappearance-obconf (0.2.2-3) unstable; urgency=low . * Disabling build with openbox 3.6.0-1 which is broken (Closes: #788524). Checksums-Sha1: e1cc647193b7c54c165a1d3f49655c95463df14a 2270 lxappearance-obconf_0.2.2-3.dsc 5006f6e6743a9290e0957346c13e0739d2555f31 2700 lxappearance-obconf_0.2.2-3.debian.tar.xz 2d9f347b00979ae512180bcbdfbd8c4b2d37f01a 63710 lxappearance-obconf-dbg_0.2.2-3_amd64.deb 28bc7538777df0fe2152abc327fd089525e61c1b 52610 lxappearance-obconf_0.2.2-3_amd64.deb Checksums-Sha256: 14dd761aa9e5d2f78f449958b62fa4b784419ec8d2422ce76f788597b790abb4 2270 lxappearance-obconf_0.2.2-3.dsc 4a8f02005eb8d79c23aad5dc3777678afab3eb509e54a75f0b6c690b3fc03b90 2700 lxappearance-obconf_0.2.2-3.debian.tar.xz 73946fb675f3beccaef15543c48a4530231beb66607882bd1f6312f15f80aecd 63710 lxappearance-obconf-dbg_0.2.2-3_amd64.deb b43cf3994402c05f6140bfa3e987838ad2c4192bcf8af21b26678d10538cba08 52610 lxappearance-obconf_0.2.2-3_amd64.deb Files: 472dd4b0d264a9bb3c2c1c5b777ed907 2270 x11 optional lxappearance-obconf_0.2.2-3.dsc 642fbbe0aa4683bae731bd7dbf0db6ec 2700 x11 optional lxappearance-obconf_0.2.2-3.debian.tar.xz ba331f6cf29410cd9279e5fb9acb6eff 63710 debug extra lxappearance-obconf-dbg_0.2.2-3_amd64.deb 5502db4c6a493f9f5a57c007a6475012 52610 x11 optional lxappearance-obconf_0.2.2-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCgAGBQJVjflSAAoJEAV2MC/hidTSccQQALc0oFmdndaV0lYjcRhTNSIS U2vAHc0PTG9HdldFkWlJTfNXaw7cgd7N5h1csUNjebqq9X8cSZiqQpxFKa807TCt fHjwAYR43cCX8PKkaQAnA1nEV1VivLu7xheC6Ca9bYrrbpEEeaZeKwHBeYD65V6M GqhLktkTa/T3UpvPp5lkwOIJHT3vUyA+uw18ZjumVzybynxoUfA4kFX9JuGTN8nT qGMfyRS5sWGxoBnstlsRsOp92Ru5FpdXzYgkGZhNTVKuc9uZC0O1S7X7mtHevu0G 9ZOBofkIid60FpgLZhnOl9ZGC+APL7yYEDzxGpssZ5IY1055jLUmzlotJfcAz7Qz G5e9X5e7S1tnwFChhMemffQ/YkmNOw0WjYx7Tyz+s5LCHC8QiGLjiZlB7RwNVg9s fOuQeq4oqNO8yeAX6Uv3VFWP5sOygc6L7UF4rvD6NpIkroXAc15nCILqk3ueyCe8 9bVNKsFV/0p/3Hp5gyGqqD8YSaItulFuT/75NfE4/VEnm89eCOwZHtEfk/YS72xx jYK4IDoh4xNQNuw0MY6RQsWlZFl8tPaYyadbw4I+733tn/YokL7XJimwBXYhBsDf 1mK9qLp2RtiJSKjXtVRBJhZ3AyjnmmEQoTnOCLFdI2iVlvp1PfJAR4e8f+i7O+VX MNXXI/2LDRlV/bVBJBtj =0I0C -END PGP SIGNATUREEnd Message---
Bug#790094: FTBFS: glibmm incompatability(?): macro bind_property requires 4 arguments, but only 3 given
Package: flush Version: 0.9.12-3.1 Severity: serious Justification: fails to build from source (but built successfully in the past) User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build with various awful C errors, starting with: In file included from /usr/include/glibmm-2.4/glibmm.h:96:0, from /usr/include/gtkmm-2.4/gtkmm/dialog.h:7, from application.cpp:37: /usr/include/glibmm-2.4/glibmm/binding.h:324:41: error: macro bind_property requires 4 arguments, but only 3 given BindingFlags flags = BINDING_DEFAULT) ^ /usr/include/glibmm-2.4/glibmm/binding.h:507:41: error: macro bind_property passed 5 arguments, but takes just 4 const T_functor_from transform_from) ^ then it looks like a random variable name gets defined as a macro and it goes totally nuts. Some hilights: /usr/include/freetype2/config/ftconfig.h:525:28: error: expected declaration before end of line #pragma GCC diagnostic push /usr/include/glibmm-2.4/glibmm/binding.h:637:30: error: 'virtual' outside class declaration virtual void unreference() const; /usr/include/boost/signal.hpp:17:4: warning: #warning Boost.Signals is no longer being maintained and is now deprecated. Please switch to Boost.Signals2. Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/flush.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: user reproducible-bui...@lists.alioth.debian.org, tagging 790092
Processing commands for cont...@bugs.debian.org: # this is currently a sid only bug due to the mentioned transition user reproducible-bui...@lists.alioth.debian.org Setting user to reproducible-bui...@lists.alioth.debian.org (was mat...@mapreri.org). tags 790092 - stretch Bug #790092 [src:kivy] FTBFS: rejects Cython 0.22 which is now in sid Removed tag(s) stretch. thanks Stopping processing here. Please contact me if you need assistance. -- 790092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790092 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#789481: My bad
My bad, musescore in testing is still built against qt4, so it should not be a problem for Qt5 transitioning. Sorry for the noise! -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#790089: FTBFS: makeinfo could not open stumpwm.texi: No such file or directory
Package: stumpwm
Version: 2:0.9.9-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build:
(SB-IMPL::READER-FIND-PACKAGE STUMPWM #SB-IMPL::STRING-INPUT-STREAM
{100BBEA603})
0]
* makeinfo stumpwm.texi
could not open stumpwm.texi: No such file or directory
Makefile:36: recipe for target 'stumpwm.info' failed
make[1]: *** [stumpwm.info] Error 1
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/stumpwm.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790091: FTBFS: coffee -c: File not found: .. debian/missing-sources/gauge
Source: ntopng Version: 1.2.1+dfsg1-1.1 Severity: serious Tags: sid stretch Justification: fails to build from source (but built successfully in the past) User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: make[2]: Leaving directory '/tmp/buildd/ntopng-1.2.1+dfsg1' mkdir -p debian/generated-code/ coffee -c -o debian/generated-code/ debian/missing-sources/gauge File not found: /tmp/buildd/ntopng-1.2.1+dfsg1/debian/missing-sources/gauge debian/rules:13: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 1 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/ntopng.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: -Werror is on by default, so FTBFS in sid
Processing control commands: severity -1 serious Bug #776292 [ffrenzy] ffrenzy: FTBFS with -Werror Severity set to 'serious' from 'normal' -- 776292: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776292 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#777816: marked as done (chromium-browser: ftbfs with GCC-5)
Your message dated Fri, 26 Jun 2015 18:16:15 -0400 with message-id CANTw=MO5fA3HNVjS4oBPFiR84ipHML5SZz5Gq=oqbjwcpth...@mail.gmail.com and subject line re: gcc-5 has caused the Debian Bug report #777816, regarding chromium-browser: 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.) -- 777816: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:chromium-browser Version: 40.0.2214.91-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/chromium-browser_40.0.2214.91-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 [...] [18/16389] CC obj/third_party/openmax_dl/dl/sp/src/x86/openmax_dl.x86SP_FFT_CToC_FC32_Fwd_Radix4_ls.o FAILED: /usr/bin/clang++ -MMD -MF obj/build/linux/obj/build/linux/libpci.gen/libpci.libpci_loader.o.d -DV8_DEPRECATION_WARNINGS -D_FILE_OFFSET_BITS=64 -DNO_TCMALLOC -DDISABLE_NACL -DCHROMIUM_BUILD -DCR_CLANG_REVISION=218707 -DTOOLKIT_VIEWS=1 -DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_AURA=1 -DUSE_ASH=1 -DUSE_PANGO=1 -DUSE_CAIRO=1 -DUSE_DEFAULT_RENDER_THEME=1 -DUSE_LIBJPEG_TURBO=1 -DUSE_X11=1 -DUSE_CLIPBOARD_AURAX11=1 -DENABLE_ONE_CLICK_SIGNIN -DENABLE_PRE_SYNC_BACKUP -DUSE_XI2_MT=2 -DENABLE_WEBRTC=1 -DUSE_PROPRIETARY_CODECS -DENABLE_PEPPER_CDMS -DENABLE_CONFIGURATION_POLICY -DENABLE_NOTIFICATIONS -DUSE_UDEV -DDONT_EMBED_BUILD_METADATA -DENABLE_TASK_MANAGER=1 -DENABLE_EXTENSIONS=1 -DENABLE_PLUGINS=1 -DENABLE_SESSION_SERVICE=1 -DENABLE_THEMES=1 -DENABLE_AUTOFILL_DIALOG=1 -DENABLE_BACKGROUND=1 -DENABLE_GOOGLE_NOW=1 -DCLD_VERSION=2 -DCLD2_DATA_SOURCE=static -DENABLE_PRINTING=1 -DENABLE_BASIC_PRINTING=1 -DENABLE_PRINT_PREVIEW=1 -DENABLE_SPELLCHECK=1 -DENABLE_CAPTIVE_PORTAL_DETECTION=1 -DENABLE _APP_LIST=1 -DENABLE_SETTINGS_APP=1 -DENABLE_MANAGED_USERS=1 -DENABLE_MDNS=1 -DENABLE_SERVICE_DISCOVERY=1 -DENABLE_LOAD_COMPLETION_HACKS=1 -DUSE_LIBPCI=1 -DUSE_GLIB=1 -DUSE_NSS=1 -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -Igen -I../.. -fstack-protector --param=ssp-buffer-size=4 -pthread -fno-strict-aliasing -Wno-unused-parameter -Wno-missing-field-initializers -fvisibility=hidden -pipe -fPIC -Wno-reserved-user-defined-literal -fcolor-diagnostics -Wheader-hygiene -Wno-char-subscripts -Wno-unneeded-internal-declaration -Wno-covered-switch-default -Wstring-conversion -Wno-c++11-narrowing -Wno-deprecated-register -Wno-unused-local-typedef -Wno-format -Wno-unused-result -m64 -march=x86-64 -O2 -fno-ident -fdata-sections -ffunction-sections -funwind-tables -D_FORTIFY_SOURCE=2 -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -fno-exceptions -fno-rtti -fno-threadsafe-statics -fvisibility-inlines-hidden -std=gnu++11 -Wno-deprecated -c obj/build/linux/libpci. gen/libpci_loader.cc -o obj/build/linux/obj/build/linux/libpci.gen/libpci.libpci_loader.o warning: unknown warning option '-Wno-unused-local-typedef' [-Wunknown-warning-option] In file included from obj/build/linux/libpci.gen/libpci_loader.cc:4: In file included from ../../out/Release/gen/library_loaders/libpci.h:14: /usr/bin/../lib/gcc/x86_64-linux-gnu/5.0.0/../../../../include/c++/5.0.0/string:38:10: fatal error: 'bits/c++config.h' file not found #include bits/c++config.h ^ 1 warning and 1 error generated. warning: unknown warning option '-Wno-unused-local-typedef' [-Wunknown-warning-option] 1 warning generated. warning: unknown warning option '-Wno-unused-local-typedef' [-Wunknown-warning-option] 1 warning generated.
Bug#777911: marked as done (icinga2: ftbfs with GCC-5)
Your message dated Fri, 26 Jun 2015 23:57:29 +0100 with message-id canbhlujhpvdvqy01p4sh7sxcd0ny1z3d5l4scvpbeg5ebvn...@mail.gmail.com and subject line Re: icinga2: ftbfs with GCC-5 has caused the Debian Bug report #777911, regarding icinga2: 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.) -- 777911: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:icinga2 Version: 2.2.4-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/icinga2_2.2.4-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 [...] /«PKGBUILDDIR»/lib/base/process.cpp: In member function 'void icinga::Process::Run(const boost::functionvoid(const icinga::ProcessResult))': /«PKGBUILDDIR»/lib/base/process.cpp:295:57: error: no matching function for call to 'call_once(boost::once_flag, void (*)())' boost::call_once(l_OnceFlag, Process::ThreadInitialize); ^ In file included from /usr/include/boost/thread/once.hpp:20:0, from /«PKGBUILDDIR»/lib/base/process.cpp:32: /usr/include/boost/thread/pthread/once_atomic.hpp:121:15: note: candidate: templateclass Function, class ... ArgTypes void boost::call_once(boost::once_flag, boost::detail::thread_move_tT, boost::detail::thread_move_tArgs...) inline void call_once(once_flag flag, BOOST_THREAD_RV_REF(Function) f, BOOST_THREAD_RV_REF(ArgTypes)... args) ^ /usr/include/boost/thread/pthread/once_atomic.hpp:121:15: note: template argument deduction/substitution failed: /«PKGBUILDDIR»/lib/base/process.cpp:295:57: note: mismatched types 'boost::detail::thread_move_tT' and 'void (*)()' boost::call_once(l_OnceFlag, Process::ThreadInitialize); ^ In file included from /«PKGBUILDDIR»/lib/base/process.cpp:32:0: /usr/include/boost/thread/once.hpp:35:13: note: candidate: templateclass Function void boost::call_once(Function, boost::once_flag) inline void call_once(Function func,once_flag flag) ^ /usr/include/boost/thread/once.hpp:35:13: note: template argument deduction/substitution failed: /«PKGBUILDDIR»/lib/base/process.cpp:295:57: note: cannot convert 'icinga::Process::ThreadInitialize' (type 'void (*)()') to type 'boost::once_flag' boost::call_once(l_OnceFlag, Process::ThreadInitialize); ^ /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles [ 13%] Building CXX object lib/base/CMakeFiles/base.dir/socket.cpp.o cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/lib/base /usr/bin/c++ -DI2_BASE_BUILD -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -g -fPIC -I/«PKGBUILDDIR» -I/«PKGBUILDDIR»/lib -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/lib -I/«PKGBUILDDIR»/third-party/execvpe -I/«PKGBUILDDIR»/third-party/mmatch -o CMakeFiles/base.dir/socket.cpp.o -c /«PKGBUILDDIR»/lib/base/socket.cpp /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 11 [ 14%] Building CXX object lib/base/CMakeFiles/base.dir/stacktrace.cpp.o cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/lib/base /usr/bin/c++ -DI2_BASE_BUILD -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -g -fPIC -I/«PKGBUILDDIR» -I/«PKGBUILDDIR»/lib
Processed: FTBFS on amd64/sid
Processing control commands: severity -1 serious Bug #745224 [src:stretchplayer] stretchplayer: FTBFS due to version of cmake Severity set to 'serious' from 'important' -- 745224: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745224 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#790090: FTBFS: uacctd.h: fatal error: linux/netfilter_ipv4/ipt_ULOG.h: No such file or directory
Package: pmacct Version: 1.5.1-1 Severity: serious Tags: sid stretch Justification: fails to build from source (but built successfully in the past) User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: In file included from uacctd.c:27:0: uacctd.h:9:43: fatal error: linux/netfilter_ipv4/ipt_ULOG.h: No such file or directory #include linux/netfilter_ipv4/ipt_ULOG.h Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/pmacct.html Similar errors in other ulog projects: https://bugs.debian.org/785518 -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790092: FTBFS: rejects Cython 0.22 which is now in sid
Source: kivy
Version: 1.9.0-1
Severity: serious
Tags: sid stretch
Justification: fails to build from source (but built successfully in the past)
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build with cython 0.22. Looks like the transition of
cython 0.22
to testing is blocked for some reason, so this is sid-only.
I: pybuild base:170: python2.7 setup.py clean
Detected Cython version 0.22
This version of Cython suffers from known bugs and is unsupported.
Please install the newest supported version, 0.21.2, if possible, but
the minimum supported version is 0.20.
If your platform provides a Cython package, check if you can install
a supported version. Otherwise, uninstall the platform package and
install Cython via pip:
pip install -I Cython==0.21.2
Please note that the following versions of Cython are not supported
at all: 0.22, 0.22.beta0, 0.22.alpha0
Cython is missing, its required for compiling kivy !
Traceback (most recent call last):
File setup.py, line 184, in module
raise ImportError('Incompatible Cython Version')
ImportError: Incompatible Cython Version
E: pybuild pybuild:256: clean: plugin distutils failed with: exit code=1:
python2.7 setup.py clean
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/kivy.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790012: gcalcli: Fails to run giving error report.
Package: gcalcli Version: 3.3-1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Running `gcalcli` from the command line. * What was the outcome of this action? An error message: ERROR: Missing module - cannot import name GoogleCredentials then the program exited. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (300, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gcalcli depends on: ii python2.7.9-1 ii python-dateutil 2.2-2 ii python-gflags 1.5.1-2 ii python-googleapi 1.4.0-1 Versions of packages gcalcli recommends: ii gxmessage 2.20.0-1 ii python-parsedatetime 1.4-1 ii python-simplejson 3.7.3-1 ii python-vobject0.8.1c-4 gcalcli suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777997: marked as done (masscan: ftbfs with GCC-5)
Your message dated Fri, 26 Jun 2015 09:20:04 + with message-id e1z8pno-0003kt...@franck.debian.org and subject line Bug#777997: fixed in masscan 1.0.3-95-gb395f18~ds0-2 has caused the Debian Bug report #777997, regarding masscan: 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.) -- 777997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777997 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:masscan Version: 1.0.3-90-g2441f18~ds0-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/masscan_1.0.3-90-g2441f18~ds0-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 [...] printf(xring: selftest failed with % PRIu64 \n, result); ^ src/xring.c:199:20: warning: spurious trailing '%' in format [-Wformat=] printf(xring: selftest failed with % PRIu64 \n, result); ^ make[1]: *** [tmp/proto-ntp.o] Error 1 make[1]: *** Waiting for unfinished jobs Makefile:87: recipe for target 'tmp/proto-ntp.o' failed make[1]: *** [tmp/xring.o] Error 1 Makefile:87: recipe for target 'tmp/xring.o' failed In file included from src/rawsock-arp.c:17:0: src/string_s.h:94:3: error: #error unknown compiler # error unknown compiler ^ make[1]: *** [tmp/rawsock-arp.o] Error 1 Makefile:87: recipe for target 'tmp/rawsock-arp.o' failed make[1]: *** [tmp/proto-dns.o] Error 1 Makefile:87: recipe for target 'tmp/proto-dns.o' failed src/output.c: In function 'reason_string': src/output.c:103:5: warning: implicit declaration of function 'sprintf_s' [-Wimplicit-function-declaration] sprintf_s(buffer, sizeof_buffer, %s%s%s%s%s%s%s%s, ^ src/output.c: In function 'output_do_rotate': src/output.c:548:15: warning: implicit declaration of function 'gmtime_s' [-Wimplicit-function-declaration] err = gmtime_s(tm, out-rotate.last); ^ src/output.c:550:15: warning: implicit declaration of function 'localtime_s' [-Wimplicit-function-declaration] err = localtime_s(tm, out-rotate.last); ^ src/main.c: In function 'receive_thread': src/main.c:628:13: warning: implicit declaration of function 'sprintf_s' [-Wimplicit-function-declaration] sprintf_s(foo, sizeof(foo), %u, masscan-tcp_connection_timeout); ^ src/main.c: In function 'main_scan': src/main.c:1238:9: warning: implicit declaration of function 'gmtime_s' [-Wimplicit-function-declaration] gmtime_s(x, now); ^ src/main.c: In function 'main': src/main.c:1411:5: warning: implicit declaration of function 'strcpy_s' [-Wimplicit-function-declaration] strcpy_s( masscan-output.rotate.directory, ^ make[1]: *** [tmp/output.o] Error 1 Makefile:87: recipe for target 'tmp/output.o' failed make[1]: *** [tmp/main.o] Error 1 Makefile:87: recipe for target 'tmp/main.o' 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 target 'build-arch' failed dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ---End Message--- ---BeginMessage--- Source: masscan Source-Version: 1.0.3-95-gb395f18~ds0-2 We believe that the bug you reported is fixed in the latest version of masscan, 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
Bug#777893: marked as done (gyoto: ftbfs with GCC-5)
Your message dated Fri, 26 Jun 2015 09:19:47 + with message-id e1z8pnx-0003ap...@franck.debian.org and subject line Bug#777893: fixed in gyoto 1.0.2-1 has caused the Debian Bug report #777893, regarding gyoto: 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.) -- 777893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777893 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:gyoto Version: 0.2.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/gyoto_0.2.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 [...] 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 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 whether ln -s works... yes checking whether make sets $(MAKE)... (cached) yes checking for pkg-config... no checking for doxygen... no checking for pdflatex... no checking for bibtex... no checking for kpsewhich... no checking whether C++ compiler accepts ... yes checking whether C++ compiler accepts -rdynamic... yes checking whether C++ compiler accepts -DGYOTO_NO_DEPRECATED... yes checking for dlopen in -ldl... (cached) yes checking for stdbool.h that conforms to C99... yes checking for _Bool... no checking for size_t... yes checking for error_at_line... yes checking for working strtod... yes checking for sincos... yes checking whether g++ supports C++11 features by default... no checking whether g++ supports C++11 features with -std=gnu++11... yes checking for Boost headers version = 1.53.1... yes checking for Boost's header version... configure: error: invalid value: boost_major_version= make: *** [configure-stamp] Error 1 debian/rules:77: recipe for target 'configure-stamp' failed dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 ---End Message--- ---BeginMessage--- Source: gyoto Source-Version: 1.0.2-1 We believe that the bug you reported is fixed in the latest version of gyoto, 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
Bug#777850: marked as done (flamerobin: ftbfs with GCC-5)
Your message dated Fri, 26 Jun 2015 09:19:22 +
with message-id e1z8pn8-0003lt...@franck.debian.org
and subject line Bug#777850: fixed in flamerobin 0.9.3~+20150308.6c0559c-1
has caused the Debian Bug report #777850,
regarding flamerobin: 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.)
--
777850: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:flamerobin
Version: 0.9.3~+20140206.3f9645c-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/flamerobin_0.9.3~+20140206.3f9645c-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
[...]
PLATFORM_MAC=''
PLATFORM_MACOS=''
PLATFORM_MACOSX=''
PLATFORM_MSDOS=''
PLATFORM_OS2=''
PLATFORM_UNIX=''
PLATFORM_WIN32=''
RANLIB='ranlib'
REZ=''
SED='/bin/sed'
SETFILE=''
SET_MAKE=''
SHARED_LD_CC=''
SHARED_LD_CXX=''
SHARED_LD_MODULE_CC=''
SHARED_LD_MODULE_CXX=''
SHELL='/bin/bash'
SONAME_FLAG=''
SO_SUFFIX=''
SO_SUFFIX_MODULE=''
STRIP='strip'
USE_MACVERSION=''
USE_SOTWOSYMLINKS=''
USE_SOVERCYGWIN=''
USE_SOVERLINUX=''
USE_SOVERSION=''
USE_SOVERSOLARIS=''
WINDOWS_IMPLIB=''
WINDRES=''
WX_CFLAGS='-I/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0
-I/usr/include/wx-3.0 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread'
WX_CFLAGS_ONLY='-pthread'
WX_CONFIG_PATH='/usr/bin/wx-config'
WX_CPPFLAGS='-I/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0
-I/usr/include/wx-3.0 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__'
WX_CXXFLAGS='-I/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0
-I/usr/include/wx-3.0 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread'
WX_CXXFLAGS_ONLY=''
WX_INCLUDES=''
WX_LIBS='-L/usr/lib/x86_64-linux-gnu -pthread -lwx_gtk2u_aui-3.0
-lwx_gtk2u_stc-3.0 -lwx_gtk2u_xrc-3.0 -lwx_gtk2u_html-3.0 -lwx_gtk2u_qa-3.0
-lwx_gtk2u_adv-3.0 -lwx_gtk2u_core-3.0 -lwx_baseu_xml-3.0 -lwx_baseu_net-3.0
-lwx_baseu-3.0 '
WX_LIBS_STATIC=''
WX_RESCOMP=''
WX_VERSION='3.0.2'
WX_VERSION_MAJOR='3'
WX_VERSION_MICRO='2'
WX_VERSION_MINOR='0'
ac_ct_AR='ar'
ac_ct_CC='gcc'
ac_ct_CXX='g++'
ac_ct_DUMPBIN=''
bindir='${exec_prefix}/bin'
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
---End Message---
---BeginMessage---
Source: flamerobin
Source-Version: 0.9.3~+20150308.6c0559c-1
We believe that the bug you reported is fixed in the latest version of
flamerobin, 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.
Damyan Ivanov d...@debian.org (supplier of updated flamerobin 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, 26 Jun 2015 08:43:43 +
Source: flamerobin
Binary: flamerobin
Architecture: source amd64
Version: 0.9.3~+20150308.6c0559c-1
Distribution: unstable
Urgency: medium
Maintainer: Damyan Ivanov d...@debian.org
Changed-By: Damyan Ivanov d...@debian.org
Description:
flamerobin - graphical database administration tool for Firebird DBMS
Closes: 777850
Changes:
flamerobin
Processed: Re: Bug#790008: texlive-bin: texlive-binaries uninstallable on several architectures
Processing commands for cont...@bugs.debian.org: reassign 790008 texlive-binaries Bug #790008 [src:texlive-bin] texlive-bin: texlive-binaries uninstallable on several architectures Bug reassigned from package 'src:texlive-bin' to 'texlive-binaries'. No longer marked as found in versions texlive-bin/2015.20150524.37493-2. Ignoring request to alter fixed versions of bug #790008 to the same values previously set merge 790008 790006 Bug #790008 [texlive-binaries] texlive-bin: texlive-binaries uninstallable on several architectures Bug #790008 [texlive-binaries] texlive-bin: texlive-binaries uninstallable on several architectures Marked as found in versions texlive-bin/2015.20150524.37493-2. Bug #790006 [texlive-binaries] I think there is some dependency problem for the new texlive package Merged 790006 790008 stop Stopping processing here. Please contact me if you need assistance. -- 790006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790006 790008: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790008 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#790008: texlive-bin: texlive-binaries uninstallable on several architectures
reassign 790008 texlive-binaries merge 790008 790006 stop On 26.06.2015 10:27, Edmund Grimley Evans wrote: Next try H. -- http://www.hilmar-preusse.de.vu/ #206401 http://counter.li.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777897: Question on yi / haskell-gtk AUTORM, reason FTBFS w/ GCC-5
Hi Marcel, Am Freitag, den 26.06.2015, 10:25 +0200 schrieb Marcel Fourné: I have just seen on https://udd.debian.org/cgi-bin/autoremovals.cgi that yi (for which I care) is marked for automatic removal from testing because of a buggy dependency, namely haskell-gtk. The bug in question seems to be #777897 (and likewise #777898 for haskell -gtk3). Since the migration to testing of our packages just started, I'm somewhat puzzled - I simply don't know enough about the necessary invocations for haskell-gtk[3], but don't want packages depending on haskell-gtk to disappear from testing again. Does anybody know more about this bug and care to help? thanks for bringing this up. I don’t think anybody looked into it in detail yet. You could start by reproducing the problem locally. Maybe it is actually unrelated to GCC. You could then check if there are new upstream versions of haskell-gtk or gtk2hs-buildtools that might fix the issue. It would also be interesting to see the code that GHC (not gcc!) stumbles over. Maybe you can solve the problem this way. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#790101: FTBFS: Missing build-dependency on help2man; patch attached
Package: tex-common Version: 6.01 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu wily ubuntu-patch In Ubuntu, the attached patch was applied to achieve the following: * Add missing build-dependency on help2man. Without this patch, the build fails with the following error: cd scripts; help2man -n generate hyphenation configuration for TeX engines -s 8 -S Debian -N ./update-language update-language.8 /bin/sh: 1: help2man: not found make: *** [build-stamp] Error 127 ... Adam -- System Information: Debian Release: jessie/sid APT prefers wily-updates APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-3-generic (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages texlive-base depends on: ii debconf [debconf-2.0] 1.5.55ubuntu2 ii dpkg 1.17.25ubuntu1 ii libpaper-utils 1.1.24+nmu2ubuntu3 ii texlive-binaries 2014.20140926.35254-6build2 ii ucf3.0030 ii xdg-utils 1.1.0~rc1-2ubuntu11 Versions of packages texlive-base recommends: pn lmodern none Versions of packages texlive-base suggests: ii evince [postscript-viewer] 3.16.1-0ubuntu1 ii ghostscript [postscript-viewer] 9.15+dfsg-0ubuntu3 pn perl-tk none pn xpdf-reader | pdf-viewer none Versions of packages texlive-binaries depends on: ii dpkg 1.17.25ubuntu1 ii install-info 5.2.0.dfsg.1-6 ii libc6 2.21-0ubuntu4 ii libfontconfig12.11.1-0ubuntu6 ii libgcc1 1:5.1.1-12ubuntu1 ii libgmp10 2:6.0.0+dfsg-6ubuntu1 ii libgraphite2-31.2.4-3ubuntu1 ii libgs99.15+dfsg-0ubuntu3 ii libharfbuzz-icu0 0.9.40-3 ii libharfbuzz0b 0.9.40-3 ii libicu52 52.1-9 ii libkpathsea6 2014.20140926.35254-6build2 ii libmpfr4 3.1.3-1 ii libpaper1 1.1.24+nmu2ubuntu3 ii libpixman-1-0 0.32.6-3 ii libpoppler52 0.33.0-0ubuntu1 ii libpotrace0 1.12-1 ii libptexenc1 2014.20140926.35254-6build2 ii libstdc++65.1.1-12ubuntu1 ii libsynctex1 2014.20140926.35254-6build2 ii libx11-6 2:1.6.3-1ubuntu1 ii libxaw7 2:1.0.12-2 ii libxi62:1.7.4-1 ii libxmu6 2:1.1.2-1 ii libxpm4 1:3.5.11-1 ii libxt61:1.1.4-1 ii libzzip-0-13 0.13.62-3 ii perl 5.20.2-6 ii zlib1g1:1.2.8.dfsg-2ubuntu1 Versions of packages texlive-binaries recommends: ii python2.7.9-1 ii ruby 1:2.1.0.4ubuntu1 ii texlive-base 2014.20141024-2ubuntu1 ii tk [wish] 8.6.0+6ubuntu3 diff -Nru tex-common-6.01/debian/control tex-common-6.01ubuntu1/debian/control --- tex-common-6.01/debian/control 2015-06-24 23:41:50.0 -0600 +++ tex-common-6.01ubuntu1/debian/control 2015-06-26 21:22:54.0 -0600 @@ -4,7 +4,7 @@ Maintainer: Debian TeX maintainers debian-tex-ma...@lists.debian.org Uploaders: Julian Gilbey j...@debian.org, Frank Küster fr...@debian.org, Florent Rougon f...@debian.org, Norbert Preining prein...@debian.org Build-Depends: debhelper (= 8.1.0~) -Build-Depends-Indep: debiandoc-sgml +Build-Depends-Indep: debiandoc-sgml, help2man Standards-Version: 3.9.6 Vcs-Git: git://anonscm.debian.org/debian-tex/tex-common.git Vcs-Browser: http://anonscm.debian.org/gitweb/?p=debian-tex/tex-common.git
Processed: Re: Bug#777810: GCC 5 build issue
Processing commands for cont...@bugs.debian.org: fixed 777810 0.5.2-2 Bug #777810 [src:capnproto] capnproto: ftbfs with GCC-5 Marked as fixed in versions capnproto/0.5.2-2. thanks Stopping processing here. Please contact me if you need assistance. -- 777810: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777810 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#778104: marked as done (regina-normal: ftbfs with GCC-5)
Your message dated Sat, 27 Jun 2015 06:49:37 +0200 with message-id d3714eee-90e0-4728-97c4-ab24cd9dd...@debian.org and subject line Re: Bug#778104: gcc-5 / regina-normal has caused the Debian Bug report #778104, regarding regina-normal: 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.) -- 778104: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:regina-normal Version: 4.96-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/regina-normal_4.96-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 [...] 2: NAngleStructureListTest::tautVsAll... ok. 2: NAngleStructureListTest::tautStrictTreeVsDD... ok. 2: NCensusTest::lookup... ok. 2: NCensusTest::rawCounts... ok. 2: NCensusTest::rawCountsCompact... ok. 2: NCensusTest::rawCountsPrimeMinimalOr... ok. 2: NCensusTest::rawCountsPrimeMinimalNor... ok. 2: NCensusTest::rawCountsBounded... ok. 2: NCensusTest::rawCountsHypMin... ok. 2: NFacePairingTest::rawCountsClosed... ok. 2: NFacePairingTest::rawCountsBounded... ok. 2: NFacePairingTest::badSubgraphs... ok. 2: Dim2CensusTest::rawCountsClosed... ok. 2: Dim2CensusTest::rawCountsBounded... ok. 2: Dim2CensusTest::rawCountsClosedMinimal... ok. 2: Dim2EdgePairingTest::rawCounts... ok. 2: NSnapPeaTriangulationTest::incompatible... ok. 2: NSnapPeaTriangulationTest::volume... ok. 2: NSnapPeaTriangulationTest::flat... ok. 2: NSnapPeaTriangulationTest::degenerate... ok. 2: NSnapPeaTriangulationTest::spunBoundaries... ok. 2: NSnapPeaTriangulationTest::stability... ok. 2: 2: 2: 2: !!!FAILURES!!! 2: Test Results: 2: Run: 240 Failures: 1 Errors: 0 2: 2: 2: 1) test: NBitmaskTest::assignment (F) line: 88 /«PKGBUILDDIR»/testsuite/utilities/nbitmask.cpp 2: forced failure 2: - NBitmask assignment resizing error. 2: 2: 2/2 Test #2: cpp-test .***Failed 87.60 sec 50% tests passed, 1 tests failed out of 2 Total Test time (real) = 88.82 sec The following tests FAILED: 2 - cpp-test (Failed) Errors while running CTest make[1]: *** [test] Error 8 Makefile:137: recipe for target 'test' failed make[1]: Leaving directory '/«PKGBUILDDIR»/builds/debbuild' make: *** [build-stamp] Error 2 debian/rules:44: recipe for target 'build-stamp' failed dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ---End Message--- ---BeginMessage--- I'm not Matthias Klose, but I just did a rebuild and it als works for me. I suggest you close the bug. Ta - closing the report then. - Ben.---End Message---
Bug#789344: marked as done (libnet-ssleay-perl: FTBFS: Test failure)
Your message dated Sat, 27 Jun 2015 05:04:01 + with message-id e1z8ihz-jd...@franck.debian.org and subject line Bug#789344: fixed in libnet-ssleay-perl 1.70-1 has caused the Debian Bug report #789344, regarding libnet-ssleay-perl: FTBFS: Test failure 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.) -- 789344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789344 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libnet-ssleay-perl Version: 1.68-1 Severity: serious From my pbuilder build log: ... t/local/33_x509_create_cert.t .. 1..123 ok 1 - BIO_new_file 1 ok 2 - PEM_read_bio_X509 ok 3 - BIO_new_file 2 ok 4 - PEM_read_bio_PrivateKey ok 5 - X509_verify ok 6 - X509_get_subject_name ok 7 - X509_get_issuer_name ok 8 - X509_NAME_cmp ok 9 - EVP_PKEY_new ok 10 - RSA_generate_key ok 11 - EVP_PKEY_assign_RSA ok 12 - X509_new ok 13 - X509_set_pubkey ok 14 - X509_get_subject_name ok 15 - X509_NAME_add_entry_by_NID ok 16 - OBJ_nid2obj ok 17 - X509_NAME_add_entry_by_OBJ ok 18 - X509_NAME_add_entry_by_txt ok 19 - X509_set_version ok 20 - X509_get_serialNumber ok 21 - ASN1_INTEGER_get ok 22 - P_ASN1_INTEGER_get_hex ok 23 - ASN1_INTEGER_get ok 24 - P_ASN1_INTEGER_get_dec ok 25 - P_ASN1_INTEGER_get_hex ok 26 - P_ASN1_TIME_set_isotime+X509_get_notBefore ok 27 - P_ASN1_TIME_set_isotime+X509_get_notAfter ok 28 - P_X509_add_extensions ok 29 - EVP_get_digestbyname ok 30 - X509_sign ok 31 - X509_get_version ok 32 - X509_verify ok 33 - PEM_get_string_X509 ok 34 - PEM_get_string_PrivateKey+nopasswd ok 35 - PEM_get_string_PrivateKey+passwd ok 36 - EVP_get_cipherbyname ok 37 - PEM_get_string_PrivateKey+passwd+enc_alg ok 38 - EVP_get_cipherbyname not ok 39 - PEM_get_string_PrivateKey+passwd+enc_alg # Failed test 'PEM_get_string_PrivateKey+passwd+enc_alg' # at t/local/33_x509_create_cert.t line 104. # undef # doesn't match '(?^:-BEGIN (ENCRYPTED|RSA) PRIVATE KEY-)' ok 40 - X509_NAME_print_ex ok 41 - X509_get_ext_by_NID ok 42 - X509_get_ext ok 43 - X509V3_EXT_print ok 44 - EVP_PKEY_new ok 45 - RSA_generate_key ok 46 - EVP_PKEY_assign_RSA ok 47 - X509_REQ_new ok 48 - X509_REQ_set_pubkey ok 49 - X509_REQ_get_subject_name ok 50 - X509_NAME_add_entry_by_txt ok 51 - X509_NAME_add_entry_by_txt ok 52 - X509_NAME_add_entry_by_txt ok 53 - P_X509_REQ_add_extensions ok 54 - X509_REQ_add1_attr_by_NID ok 55 - X509_REQ_add1_attr_by_NID ok 56 - X509_REQ_set_version ok 57 - EVP_get_digestbyname ok 58 - X509_REQ_sign ok 59 - X509_REQ_get_pubkey ok 60 - X509_REQ_verify ok 61 - X509_REQ_get_version ok 62 - OBJ_txt2obj ok 63 - OBJ_obj2nid ok 64 - X509_REQ_get_attr_count ok 65 - X509_REQ_get_attr_by_NID ok 66 - X509_REQ_get_attr_by_OBJ ok 67 - P_X509_REQ_get_attr ok 68 - attr_values size ok 69 - attr_values[0] ok 70 - PEM_get_string_X509_REQ ok 71 - PEM_get_string_PrivateKey ok 72 - X509_new ok 73 - X509_set_version ok 74 - X509_get_serialNumber ok 75 - X509_gmtime_adj + X509_get_notBefore ok 76 - X509_gmtime_adj + X509_get_notAfter ok 77 - X509_set_subject_name + X509_REQ_get_subject_name ok 78 - P_X509_copy_extensions ok 79 - X509_REQ_get_pubkey ok 80 - X509_set_pubkey ok 81 - X509_sign ok 82 - PEM_get_string_X509 ok 83 - X509_NAME_print_ex 1 ok 84 - X509_NAME_print_ex 2 ok 85 - X509_get_notBefore ok 86 - X509_get_notAfter ok 87 - X509_certificate_type ok 88 - X509_REQ_free ok 89 - X509_free ok 90 - X509_new ok 91 - X509_get_subject_name ok 92 - X509_NAME_add_entry_by_txt ok 93 - X509_NAME_add_entry_by_txt ok 94 - X509_NAME_print_ex ok 95 - BIO_new_file ok 96 - PEM_read_bio_X509 ok 97 - EVP_PKEY_new ok 98 - RSA_generate_key ok 99 - EVP_PKEY_assign_RSA ok 100 - X509_new ok 101 - X509_set_pubkey ok 102 - X509_get_subject_name ok 103 - X509_set_subject_name ok 104 - X509_get_serialNumber ok 105 - X509_get_serialNumber ok 106 - P_ASN1_TIME_set_isotime+X509_get_notBefore ok 107 - P_ASN1_TIME_set_isotime+X509_get_notAfter ok 108 - EVP_get_digestbyname ok 109 - X509_sign ok 110 - PEM_get_string_X509 ok 111 - PEM_get_string_PrivateKey ok 112 - BIO_new_file ok 113 - PEM_read_bio_X509 ok 114 - EVP_get_digestbyname ok 115 - X509_REQ_digest ok 116 - X509_REQ_new ok 117 - X509_REQ_get_subject_name ok 118 - X509_REQ_set_subject_name ok 119 - X509_REQ_free ok 120 - BIO_new_file ok 121 - d2i_X509_REQ_bio ok 122 - BIO_new_file ok 123 - d2i_X509_bio # Looks like you failed 1 test of 123. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/123 subtests ... Test Summary Report --- t/local/33_x509_create_cert.t(Wstat: 256 Tests: 123 Failed: 1) Failed test: 39 Non-zero
Bug#778102: recoll: ftbfs with GCC-5
Seems I can't reach Kartik Mistry by direct email, trying through the bug report: The diagnostic from the log is a Xapian one, saying that they are trying to build Recoll with a compiler ABI version which is not the same as the one which was used to build the Xapian library. The include file which causes the issue (xapian/version.h) is created during the Xapian build. The lines which cause the error are the following: #ifdef __GNUC__ #if __GNUC__ 3 || (__GNUC__ == 3 __GNUC_MINOR__ == 0) #error Xapian no longer supports GCC 3.1 #else #if !defined(__GXX_ABI_VERSION) || __GXX_ABI_VERSION != 1002 #error The C++ ABI version of compiler you are using does not match #error that of the compiler used to build the library. The versions #error must match or your program will not work correctly. #error The Xapian library was built with g++ 4.7.2 #endif I initially saw 2 possibilities here: - Either they are actually building Recoll with gcc5 with a libxapian dev package which was created with gcc4 (then I guess that their method is wrong, they should build the dependancy packages before the ones which depend on them). - Or the test in the Xapian file is wrong or incompatible with gcc 5 (then it's a Xapian bug). I don't see how this could possibly be a Recoll issue. Except maybe if this is related to how the libxapian dependancy is expressed in the recoll package ? Actually, I checked with other xapian-based packages (e.g. xapian-omega itself) and the builds fail with the same error. https://people.debian.org/~doko/logs/gcc5-20150205/xapian-omega_1.2.19-1_unstable_gcc5.log So this really seems a problem with the package rebuild method. It seems that it is necessary to build and install libxapian with gcc5 before they building dependant packages. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777885: marked as done (gnugk: ftbfs with GCC-5)
Your message dated Sat, 27 Jun 2015 15:33:09 +1000 with message-id 7107822.iMYqIWaiua@acer and subject line fixed with ptlib upload has caused the Debian Bug report #777885, regarding gnugk: 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.) -- 777885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:gnugk Version: 2:3.6-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/gnugk_3.6-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 'obj_linux_x86_64/h323util.o' failed make[3]: *** [obj_linux_x86_64/singleton.o] Error 1 /usr/share/ptlib//make/common.mak:96: recipe for target 'obj_linux_x86_64/singleton.o' failed compilation terminated. compilation terminated. make[3]: *** [obj_linux_x86_64/RasTbl.o] Error 1 In file included from /usr/include/ptlib/contain.h:42:0, from /usr/include/ptlib.h:56, from SoftPBX.cxx:14: /usr/include/ptlib/critsec.h:46:33: fatal error: bits/atomicity.h: No such file or directory compilation terminated. /usr/share/ptlib//make/common.mak:96: recipe for target 'obj_linux_x86_64/RasTbl.o' failed make[3]: *** [obj_linux_x86_64/Routing.o] Error 1 /usr/share/ptlib//make/common.mak:96: recipe for target 'obj_linux_x86_64/Routing.o' failed In file included from /usr/include/ptlib/contain.h:42:0, from /usr/include/ptlib.h:56, from job.cxx:18: /usr/include/ptlib/critsec.h:46:33: fatal error: bits/atomicity.h: No such file or directory compilation terminated. make[3]: *** [obj_linux_x86_64/job.o] Error 1 /usr/share/ptlib//make/common.mak:96: recipe for target 'obj_linux_x86_64/job.o' failed In file included from /usr/include/ptlib/contain.h:42:0, from /usr/include/ptlib.h:56, from Toolkit.cxx:14: /usr/include/ptlib/critsec.h:46:33: fatal error: bits/atomicity.h: No such file or directory compilation terminated. make[3]: *** [obj_linux_x86_64/Toolkit.o] Error 1 /usr/share/ptlib//make/common.mak:96: recipe for target 'obj_linux_x86_64/Toolkit.o' failed make[3]: *** [obj_linux_x86_64/SoftPBX.o] Error 1 /usr/share/ptlib//make/common.mak:96: recipe for target 'obj_linux_x86_64/SoftPBX.o' failed In file included from /usr/include/ptlib/contain.h:42:0, from /usr/include/ptlib.h:56, from yasocket.cxx:15: /usr/include/ptlib/critsec.h:46:33: fatal error: bits/atomicity.h: No such file or directory compilation terminated. make[3]: *** [obj_linux_x86_64/yasocket.o] Error 1 /usr/share/ptlib//make/common.mak:96: recipe for target 'obj_linux_x86_64/yasocket.o' failed make[3]: Leaving directory '/«PKGBUILDDIR»' make[2]: *** [opt] Error 2 make[2]: *** Waiting for unfinished jobs /usr/share/ptlib//make/common.mak:289: recipe for target 'opt' failed make[3]: Leaving directory '/«PKGBUILDDIR»/docs/manual' make[2]: Leaving directory '/«PKGBUILDDIR»' dh_auto_build: make -j10 opt doc returned exit code 2 make[1]: *** [override_dh_auto_build] Error 2 debian/rules:31: recipe for target 'override_dh_auto_build' failed make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [build-arch] Error 2 debian/rules:25: recipe for target 'build-arch' failed dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ---End Message--- ---BeginMessage--- This bug is fixed with ptlib upload: #778074 Mark---End Message---
Bug#789966: marked as done (redshift-gtk: trying to overwrite '/usr/bin/redshift-gtk', which is also in package gtk-redshift 1.10-1)
Your message dated Fri, 26 Jun 2015 10:49:36 + with message-id e1z8rcs-00026t...@franck.debian.org and subject line Bug#789966: fixed in redshift 1.10-3 has caused the Debian Bug report #789966, regarding redshift-gtk: trying to overwrite '/usr/bin/redshift-gtk', which is also in package gtk-redshift 1.10-1 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.) -- 789966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: redshift-gtk Version: 1.10-2 Severity: serious Dear Maintainer, the (IMHO completely unnecessary) switch from gtk-redshift to redshift-gtk fails because the Breaks/Replaces headers in redshift-gtk are against the wrong version of the gtk-redshift package: Unpacking redshift-gtk (1.10-2) ... dpkg: error processing archive /var/cache/apt/archives/redshift-gtk_1.10-2_all.deb (--unpack): trying to overwrite '/usr/bin/redshift-gtk', which is also in package gtk-redshift 1.10-1 […] Errors were encountered while processing: /var/cache/apt/archives/redshift-gtk_1.10-2_all.deb […] E: Sub-process /usr/bin/dpkg returned an error code (1) Failed to perform requested operation on package. Trying to recover: […] Current headers are: Replaces: gtk-redshift ( 1.10-1~) Breaks: gtk-redshift ( 1.10-1~) But they should be: Replaces: gtk-redshift ( 1.10-2~) Breaks: gtk-redshift ( 1.10-2~) -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages redshift-gtk depends on: ii gir1.2-appindicator3-0.1 0.4.92-3.1 ii python-gtk2 2.24.0-4 ii python3 3.4.2-2 ii python3-gi3.16.2-1 ii python3-xdg 0.25-4 pn python3:any none ii redshift 1.10-2 Versions of packages redshift-gtk recommends: ii at-spi2-core 2.16.0-1 redshift-gtk suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: redshift Source-Version: 1.10-3 We believe that the bug you reported is fixed in the latest version of redshift, 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. Ritesh Raj Sarraf r...@debian.org (supplier of updated redshift package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 26 Jun 2015 16:00:07 +0530 Source: redshift Binary: redshift redshift-gtk gtk-redshift Architecture: source amd64 all Version: 1.10-3 Distribution: unstable Urgency: medium Maintainer: Ritesh Raj Sarraf r...@debian.org Changed-By: Ritesh Raj Sarraf r...@debian.org Description: gtk-redshift - transitional dummy package redshift - Adjusts the color temperature of your screen redshift-gtk - Adjusts the color temperature of your screen with GTK+ integratio Closes: 789966 Changes: redshift (1.10-3) unstable; urgency=medium . * [a62084b] Fix exact version in Breaks and Replaces. Thanks to Axel Beckert (Closes: #789966) * [e7f571d] Add build dependency on dh-python * [f7ea959] Refresh patches * [3263caa] No need to override dh_auto_install * [2b1374c] Bump compat level to 9 Checksums-Sha1: 9c5ca6bfe07a3b0211798f60f51dedb84ea7dc0c 2180 redshift_1.10-3.dsc 2fc1f80709d8745a08ef137cc939839212206561 6812 redshift_1.10-3.debian.tar.xz 0e054e4e6cf02c78fddeb320592d3e07fd97a427 61336 redshift_1.10-3_amd64.deb 856c620ab98542fb30e4be3b3ecb9acad735e014 33512 redshift-gtk_1.10-3_all.deb fbadd1bd439f2f57783a2dc40ad809db944e27fc 7758 gtk-redshift_1.10-3_all.deb Checksums-Sha256: 881190741568087a3bf05a21f7647fe1135f43e48c8ac60446db3e1b161314b2 2180 redshift_1.10-3.dsc 11ff3557837ffdaf104a1ed8846f55e7f759c071a85286f6e10497a10c8a9ae7 6812 redshift_1.10-3.debian.tar.xz
Processed: affects 789927, affects 788253, affects 789914, user debian...@lists.debian.org, usertagging 789966
Processing commands for cont...@bugs.debian.org: affects 789927 + fcitx-anthy anthy Bug #789927 [libanthyinput0] libanthyinput0: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/libanthyinput.so.0.0.0' Added indication that 789927 affects fcitx-anthy and anthy affects 788253 + gfmd Bug #788253 [dh-systemd] gfsd: unowned files after purge (policy 6.8, 10.8): /var/lib/systemd/deb-systemd-helper-masked/gfsd.service Added indication that 788253 affects gfmd affects 789914 + fusionforge-web Bug #789914 [apache2.2-common] apache2: fails to install: ERROR: Module mpm_event is enabled - cannot proceed due to conflicts. It needs to be disabled first! Added indication that 789914 affects fusionforge-web user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). usertags 789966 piuparts There were no usertags set. Usertags are now: piuparts. thanks Stopping processing here. Please contact me if you need assistance. -- 788253: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788253 789914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789914 789927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789927 789966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789966 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#790019: texinfo: depends on gawk, but texindex calls mawk
On Fri, 26 Jun 2015, Sven Joachim wrote: - awk_binary=gawk + awk_binary=mawk That is due to auto-detection of awk in the configure script. I had to build several other packages in a chroot and had gawk installed there. I have already a package in testing that changes that to awk_binary=awk by setting AWK=awk ./configure ... and have changed the dep from gawk to awk. That should do it. Remedy: either add a build dependency on gawk, or, if the outcome of #790004 is that any awk implementation will do, configure with AWK=awk Indeed, that is what I do. Norbert PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778065: marked as done (pktools: ftbfs with GCC-5)
Your message dated Fri, 26 Jun 2015 11:19:52 +
with message-id e1z8rfk-0008ni...@franck.debian.org
and subject line Bug#778065: fixed in pktools 2.6.3-2
has caused the Debian Bug report #778065,
regarding pktools: 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.)
--
778065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:pktools
Version: 2.5.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/pktools_2.5.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
[...]
#define PACKAGE_STRING
^
In file included from ../../src/base/Optionpk.h:41:0,
from pkfssvm.cc:25:
../../config.h:66:0: warning: PACKAGE_TARNAME redefined
#define PACKAGE_TARNAME pktools
^
In file included from /usr/include/gdal/cpl_port.h:80:0,
from /usr/include/gdal/ogr_core.h:33,
from /usr/include/gdal/ogr_geometry.h:34,
from /usr/include/gdal/ogr_feature.h:33,
from ../../src/base/Optionpk.h:38,
from pkfssvm.cc:25:
/usr/include/gdal/cpl_config.h:207:0: note: this is the location of the
previous definition
#define PACKAGE_TARNAME
^
In file included from ../../src/base/Optionpk.h:41:0,
from pkfssvm.cc:25:
../../config.h:72:0: warning: PACKAGE_VERSION redefined
#define PACKAGE_VERSION 2.5.3
^
In file included from /usr/include/gdal/cpl_port.h:80:0,
from /usr/include/gdal/ogr_core.h:33,
from /usr/include/gdal/ogr_geometry.h:34,
from /usr/include/gdal/ogr_feature.h:33,
from ../../src/base/Optionpk.h:38,
from pkfssvm.cc:25:
/usr/include/gdal/cpl_config.h:213:0: note: this is the location of the
previous definition
#define PACKAGE_VERSION
^
In file included from pkfssvm.cc:28:0:
../../src/algorithms/FeatureSelector.h:52:177: error: redeclaration of 'double
FeatureSelector::forwardUnivariate(std::vectorVector2dT , CostFactory,
std::listint, int, short int)' may not have default arguments [-fpermissive]
templateclass T double FeatureSelector::forwardUnivariate(std::vector
Vector2dT v, CostFactory theCostFactory, std::listint subset, int
maxFeatures=0, short verbose){
^
../../src/algorithms/FeatureSelector.h:111:167: error: redeclaration of 'double
FeatureSelector::forward(std::vectorVector2dT , CostFactory,
std::listint, int, short int)' may not have default arguments [-fpermissive]
templateclass T double FeatureSelector::forward(std::vector Vector2dT
v, CostFactory theCostFactory, std::listint subset, int maxFeatures=0,
short verbose){
^
make[3]: *** [pkfssvm.o] Error 1
Makefile:952: recipe for target 'pkfssvm.o' failed
make[3]: Leaving directory '/«PKGBUILDDIR»/src/apps'
make[2]: *** [all-recursive] Error 1
Makefile:502: recipe for target 'all-recursive' failed
make[2]: Leaving directory '/«PKGBUILDDIR»'
make[1]: *** [all] Error 2
Makefile:389: recipe for target 'all' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
dh_auto_build: make -j1 returned exit code 2
make: *** [build-arch] Error 2
Bug#790019: marked as done (texinfo: depends on gawk, but texindex calls mawk)
Your message dated Fri, 26 Jun 2015 12:05:43 + with message-id e1z8so7-0003ab...@franck.debian.org and subject line Bug#790019: fixed in texinfo 5.9.96.dfsg.1-2 has caused the Debian Bug report #790019, regarding texinfo: depends on gawk, but texindex calls mawk 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.) -- 790019: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790019 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: texinfo Version: 5.9.96.dfsg.1-1 Severity: serious I read bug #790004 and wondered where gawk is actually called… turns out it isn't, since on i386 (and most likely on other architectures) texindex actually calls mawk: --8---cut here---start-8--- --- amd64/texindex 2015-06-26 11:44:36.471766815 +0200 +++ i386/texindex 2015-06-25 18:10:11.0 +0200 @@ -44,7 +44,7 @@ # # else use configured value for awk. if test -z $awk_binary; then - awk_binary=gawk + awk_binary=mawk fi # # that should never be empty, but just in case, else fall back to plain --8---cut here---end---8--- Remedy: either add a build dependency on gawk, or, if the outcome of #790004 is that any awk implementation will do, configure with AWK=awk. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 4.0.6-nouveau (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages texinfo depends on: ii gawk1:4.1.1+dfsg-1 ii libintl-perl1.23-1 ii libtext-unidecode-perl 1.22-1 ii libxml-libxml-perl 2.0116+dfsg-4 texinfo recommends no packages. Versions of packages texinfo suggests: ii texinfo-doc-nonfree 5.9.96-1 ii texlive-base 2015.20150625-1 ii texlive-generic-recommended 2015.20150625-1 ii texlive-latex-base 2015.20150625-1 -- no debconf information ---End Message--- ---BeginMessage--- Source: texinfo Source-Version: 5.9.96.dfsg.1-2 We believe that the bug you reported is fixed in the latest version of texinfo, 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. Norbert Preining prein...@debian.org (supplier of updated texinfo 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, 26 Jun 2015 20:27:35 +0900 Source: texinfo Binary: texinfo info install-info Architecture: source amd64 Version: 5.9.96.dfsg.1-2 Distribution: unstable Urgency: medium Maintainer: Debian TeX maintainers debian-tex-ma...@lists.debian.org Changed-By: Norbert Preining prein...@debian.org Description: info - Standalone GNU Info documentation browser install-info - Manage installed documentation in info format texinfo- Documentation system for on-line information and printed output Closes: 790004 790019 Changes: texinfo (5.9.96.dfsg.1-2) unstable; urgency=medium . * use awk by default, change dep to awk (Closes: #790004, #790019) Checksums-Sha1: a232889192d4bfeaafce694f19eb83d282df8d65 2136 texinfo_5.9.96.dfsg.1-2.dsc 4f8f81df608312bd3975e1b35c1fe7b2ff1038e5 22744 texinfo_5.9.96.dfsg.1-2.debian.tar.xz 27c1076db4839634de5d40d6be90c0584c128f1b 327506 info_5.9.96.dfsg.1-2_amd64.deb 61b3ae1f42b67bfffc79a319b9e292409cba6a92 253152 install-info_5.9.96.dfsg.1-2_amd64.deb 2ef7e56a8480bf6004eb21ba1803dd2ca0c21f93 1062972 texinfo_5.9.96.dfsg.1-2_amd64.deb Checksums-Sha256: 72d7cff441c583bd7356e0fe9881ac525fd0a55403f2f72b281077e65f1ee537 2136 texinfo_5.9.96.dfsg.1-2.dsc cf0a0fa23693a4baa92b03b58b6d37430c617b33c282ac77170ea8f2b46ca5b9 22744 texinfo_5.9.96.dfsg.1-2.debian.tar.xz cf331124b79eb57042aadcf7e4b9df66e9a351bed74b70ac36d4f1526beece0e 327506 info_5.9.96.dfsg.1-2_amd64.deb 2b2f81c800c33ae7a85f0171ee806a60d5b14082bb9283ff9cf985cd8ca34965 253152 install-info_5.9.96.dfsg.1-2_amd64.deb c617ba8ca99fa31ad7e111df900debb510c5dc6f59b110f632522a733c0fab7a
Bug#777829: marked as done (dahdi-tools: ftbfs with GCC-5)
Your message dated Fri, 26 Jun 2015 13:20:50 + with message-id e1z8tyo-0003cn...@franck.debian.org and subject line Bug#777829: fixed in dahdi-tools 1:2.10.2-1 has caused the Debian Bug report #777829, regarding dahdi-tools: ftbfs with GCC-5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 777829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:dahdi-tools Version: 1:2.10.0.1-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/dahdi-tools_2.10.0.1-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 [...] ranlib libtonezone.a gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I. -O2 -g -fPIC -Wall -DBUILDING_TONEZONE -MD -MT fxotune.o -MF .fxotune.o.d -MP -c -o fxotune.o fxotune.c gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I. -O2 -g -fPIC -Wall -DBUILDING_TONEZONE -Wl,-z,relro fxotune.o version.o -lm -o fxotune gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I. -O2 -g -fPIC -Wall -DBUILDING_TONEZONE -MD -MT dahdi_cfg.o -MF .dahdi_cfg.o.d -MP -c -o dahdi_cfg.o dahdi_cfg.c gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I. -O2 -g -fPIC -Wall -DBUILDING_TONEZONE -Wl,-z,relro dahdi_cfg.o version.o libtonezone.a -lm -lpthread -o dahdi_cfg gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I. -O2 -g -fPIC -Wall -DBUILDING_TONEZONE -MD -MT dahdi_monitor.o -MF .dahdi_monitor.o.d -MP -c -o dahdi_monitor.o dahdi_monitor.c gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I. -O2 -g -fPIC -Wall -DBUILDING_TONEZONE -Wl,-z,relro dahdi_monitor.o version.o -o dahdi_monitor gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I. -O2 -g -fPIC -Wall -DBUILDING_TONEZONE -MD -MT dahdi_test.o -MF .dahdi_test.o.d -MP -c -o dahdi_test.o dahdi_test.c gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I. -O2 -g -fPIC -Wall -DBUILDING_TONEZONE -Wl,-z,relro dahdi_test.o version.o -o dahdi_test gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I. -O2 -g -fPIC -Wall -DBUILDING_TONEZONE -MD -MT dahdi_scan.o -MF .dahdi_scan.o.d -MP -c -o dahdi_scan.o dahdi_scan.c gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I. -O2 -g -fPIC -Wall -DBUILDING_TONEZONE -Wl,-z,relro dahdi_scan.o version.o -o dahdi_scan gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I. -O2 -g -fPIC -Wall -DBUILDING_TONEZONE -MD -MT dahdi_maint.o -MF .dahdi_maint.o.d -MP -c -o dahdi_maint.o dahdi_maint.c gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I. -O2 -g -fPIC -Wall -DBUILDING_TONEZONE -Wl,-z,relro dahdi_maint.o version.o -o dahdi_maint gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I. -O2 -g -fPIC -Wall -DBUILDING_TONEZONE-MD -MT dahdi_tool.o -MF .dahdi_tool.o.d -MP -c -o dahdi_tool.o dahdi_tool.c gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I. -O2 -g -fPIC -Wall -DBUILDING_TONEZONE-Wl,-z,relro dahdi_tool.o version.o -lnewt -o dahdi_tool gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I. -O2 -g -fPIC -Wall -DBUILDING_TONEZONE -MD -MT sethdlc.o -MF .sethdlc.o.d -MP -c -o sethdlc.o sethdlc.c gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I. -O2 -g -fPIC -Wall -DBUILDING_TONEZONE -Wl,-z,relro
Bug#777941: marked as done (libcli: ftbfs with GCC-5)
Your message dated Fri, 26 Jun 2015 11:49:58 + with message-id e1z8s8s-000513...@franck.debian.org and subject line Bug#777941: fixed in libcli 1.9.7-2 has caused the Debian Bug report #777941, regarding libcli: 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.) -- 777941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:libcli Version: 1.9.7-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/libcli_1.9.7-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 [...] SCHROOT_GID=1001 SCHROOT_GROUP=user SCHROOT_SESSION_ID=unstable-amd64-sbuild-2a6d6e68-19e5-443b-b728-651dd849b47d SCHROOT_UID=1001 SCHROOT_USER=user SHELL=/bin/sh USER=user dpkg-buildpackage âââââââââââââââââ dpkg-buildpackage: source package libcli dpkg-buildpackage: source version 1.9.7-1 dpkg-buildpackage: source distribution unstable dpkg-buildpackage: source changed by Jonathan McDowell nood...@earth.li dpkg-source --before-build libcli-1.9.7 dpkg-buildpackage: host architecture amd64 fakeroot debian/rules clean dh_testdir dh_testroot rm -f build-stamp configure-stamp /usr/bin/make clean make[1]: Entering directory '/«PKGBUILDDIR»' rm -f *.o libcli.so* libcli.a clitest make[1]: Leaving directory '/«PKGBUILDDIR»' dh_clean debian/rules build-arch dh_testdir touch configure-stamp dh_testdir /usr/bin/make PREFIX=/usr make[1]: Entering directory '/«PKGBUILDDIR»' gcc -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O3 -Wall -std=c99 -pedantic -Wformat-security -Wno-format-zero-length -Werror -Wwrite-strings -Wformat -fdiagnostics-show-option -Wextra -Wsign-compare -Wcast-align -Wno-unused-parameter -fPIC -o libcli.o -c libcli.c gcc -o libcli.so.1.9.7 libcli.o -Wl,-z,relro -shared -Wl,-soname,libcli.so.1.9 -lcrypt rm -f libcli.so libcli.so.1.9 ln -s libcli.so.1.9.7 libcli.so.1.9 ln -s libcli.so.1.9 libcli.so ar rcs libcli.a libcli.o gcc -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O3 -Wall -std=c99 -pedantic -Wformat-security -Wno-format-zero-length -Werror -Wwrite-strings -Wformat -fdiagnostics-show-option -Wextra -Wsign-compare -Wcast-align -Wno-unused-parameter -fPIC -o clitest.o -c clitest.c clitest.c: In function 'cmd_test': clitest.c:75:45: error: ISO C does not support '__FUNCTION__' predefined identifier [-Werror=pedantic] cli_print(cli, called %s with \%s\, __FUNCTION__, command); ^ cc1: all warnings being treated as errors make[1]: *** [clitest.o] Error 1 Makefile:41: recipe for target 'clitest.o' failed make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [build-stamp] Error 2 debian/rules:29: recipe for target 'build-stamp' failed dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ---End Message--- ---BeginMessage--- Source: libcli Source-Version: 1.9.7-2 We believe that the bug you reported is fixed in the latest version of libcli, 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. Jonathan McDowell nood...@earth.li
Bug#790006: marked as done (I think there is some dependency problem for the new texlive package)
Your message dated Fri, 26 Jun 2015 11:51:49 + with message-id e1z8saf-0006dk...@franck.debian.org and subject line Bug#790006: fixed in texlive-bin 2015.20150524.37493-3 has caused the Debian Bug report #790006, regarding I think there is some dependency problem for the new texlive package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 790006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: texlive-binaries Version: 2015.20150524.37493-2 Severity: important On Fri, 26 Jun 2015, Friedrich Beckmann wrote: i think there is some build dependency problem in the new texlive package group. See Indeed, what a pity. These architectures do NOT support building luajittex etc, so the packages are not built there, but somehow in the dependency list this got forgotten. I have to fix the dependencies to exclude the luajit* in case of the unsupported libs. Thanks for the report Norbert PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 ---End Message--- ---BeginMessage--- Source: texlive-bin Source-Version: 2015.20150524.37493-3 We believe that the bug you reported is fixed in the latest version of texlive-bin, 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. Norbert Preining prein...@debian.org (supplier of updated texlive-bin 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, 26 Jun 2015 16:53:02 +0900 Source: texlive-bin Binary: texlive-binaries libkpathsea6 libkpathsea-dev libptexenc1 libptexenc-dev libsynctex1 libsynctex-dev libtexlua52 libtexlua52-dev libtexluajit2 libtexluajit-dev luatex Architecture: source amd64 all Version: 2015.20150524.37493-3 Distribution: unstable Urgency: medium Maintainer: Debian TeX Maintainers debian-tex-ma...@lists.debian.org Changed-By: Norbert Preining prein...@debian.org Description: libkpathsea-dev - TeX Live: path search library for TeX (development part) libkpathsea6 - TeX Live: path search library for TeX (runtime part) libptexenc-dev - TeX Live: ptex encoding library (development part) libptexenc1 - TeX Live: pTeX encoding library libsynctex-dev - Tex Live: SyncTeX parser library (development part) libsynctex1 - TeX Live: SyncTeX parser library libtexlua52 - TeX Live: Lua 5.2, modified for use with LuaTeX libtexlua52-dev - Tex Live: Lua 5.2, modified for use with LuaTeX (development part libtexluajit-dev - Tex Live: LuaJIT, modified for use with LuaJITTeX (development pa libtexluajit2 - TeX Live: LuaJIT, modified for use with LuaJITTeX luatex - TeX Live: transitional dummy package texlive-binaries - Binaries for TeX Live Closes: 790006 Changes: texlive-bin (2015.20150524.37493-3) unstable; urgency=medium . * fix deps for archs were not luajittex is available (Closes: #790006) Checksums-Sha1: b17b797ef845693641fcfe61ada315095e291c57 3339 texlive-bin_2015.20150524.37493-3.dsc 7d097abc252d980e2ec3e0e71641a361c3d70a86 47884 texlive-bin_2015.20150524.37493-3.debian.tar.xz 72d74e42ce3d1769323eeb522564e1765cf7a4e4 180870 libkpathsea-dev_2015.20150524.37493-3_amd64.deb a52b22e38de90ea5fa7771e8a5beeb8c19bf3566 155532 libkpathsea6_2015.20150524.37493-3_amd64.deb 89405eb410590da7924becca9e1e606a7c881bf9 54224 libptexenc-dev_2015.20150524.37493-3_amd64.deb d9a7d555bd3a088b6ef54cf4dc1fabc369ad12ee 54904 libptexenc1_2015.20150524.37493-3_amd64.deb d4e5f65166c20f6d7d6e5793d108b3d1b8f27270 60260 libsynctex-dev_2015.20150524.37493-3_amd64.deb 6b414576506188c077d9a5806347f958a4e75d63 62184 libsynctex1_2015.20150524.37493-3_amd64.deb a5d619b32898b589e778f75a6acc0cad437d302e 128114 libtexlua52-dev_2015.20150524.37493-3_amd64.deb 0553a78bc3e815d15a6f01427c5c1a4c40bb1e48 106936
Bug#790008: marked as done (texlive-bin: texlive-binaries uninstallable on several architectures)
Your message dated Fri, 26 Jun 2015 11:51:49 + with message-id e1z8saf-0006dk...@franck.debian.org and subject line Bug#790006: fixed in texlive-bin 2015.20150524.37493-3 has caused the Debian Bug report #790006, regarding texlive-bin: texlive-binaries uninstallable on several architectures 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.) -- 790006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: texlive-bin Version: 2015.20150524.37493-2 Severity: serious texlive-binaries depends unconditionally on libtexluajit2, which is only built for Architecture: amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc according to debian/control, but that list may be too long as libtexluajit2 does not really get build for hurd-i386 and mips, according to https://packages.debian.org/sid/libtexluajit2 A lot of packages have texlive-binaries as a Build-Depends, so this seems quite serious to me. Those packages could specify their Build-Depends more precisely but presumably this should be fixed in texlive-bin as there is no point in having texlive-binaries if it is uninstallable. ---End Message--- ---BeginMessage--- Source: texlive-bin Source-Version: 2015.20150524.37493-3 We believe that the bug you reported is fixed in the latest version of texlive-bin, 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. Norbert Preining prein...@debian.org (supplier of updated texlive-bin 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, 26 Jun 2015 16:53:02 +0900 Source: texlive-bin Binary: texlive-binaries libkpathsea6 libkpathsea-dev libptexenc1 libptexenc-dev libsynctex1 libsynctex-dev libtexlua52 libtexlua52-dev libtexluajit2 libtexluajit-dev luatex Architecture: source amd64 all Version: 2015.20150524.37493-3 Distribution: unstable Urgency: medium Maintainer: Debian TeX Maintainers debian-tex-ma...@lists.debian.org Changed-By: Norbert Preining prein...@debian.org Description: libkpathsea-dev - TeX Live: path search library for TeX (development part) libkpathsea6 - TeX Live: path search library for TeX (runtime part) libptexenc-dev - TeX Live: ptex encoding library (development part) libptexenc1 - TeX Live: pTeX encoding library libsynctex-dev - Tex Live: SyncTeX parser library (development part) libsynctex1 - TeX Live: SyncTeX parser library libtexlua52 - TeX Live: Lua 5.2, modified for use with LuaTeX libtexlua52-dev - Tex Live: Lua 5.2, modified for use with LuaTeX (development part libtexluajit-dev - Tex Live: LuaJIT, modified for use with LuaJITTeX (development pa libtexluajit2 - TeX Live: LuaJIT, modified for use with LuaJITTeX luatex - TeX Live: transitional dummy package texlive-binaries - Binaries for TeX Live Closes: 790006 Changes: texlive-bin (2015.20150524.37493-3) unstable; urgency=medium . * fix deps for archs were not luajittex is available (Closes: #790006) Checksums-Sha1: b17b797ef845693641fcfe61ada315095e291c57 3339 texlive-bin_2015.20150524.37493-3.dsc 7d097abc252d980e2ec3e0e71641a361c3d70a86 47884 texlive-bin_2015.20150524.37493-3.debian.tar.xz 72d74e42ce3d1769323eeb522564e1765cf7a4e4 180870 libkpathsea-dev_2015.20150524.37493-3_amd64.deb a52b22e38de90ea5fa7771e8a5beeb8c19bf3566 155532 libkpathsea6_2015.20150524.37493-3_amd64.deb 89405eb410590da7924becca9e1e606a7c881bf9 54224 libptexenc-dev_2015.20150524.37493-3_amd64.deb d9a7d555bd3a088b6ef54cf4dc1fabc369ad12ee 54904 libptexenc1_2015.20150524.37493-3_amd64.deb d4e5f65166c20f6d7d6e5793d108b3d1b8f27270 60260 libsynctex-dev_2015.20150524.37493-3_amd64.deb 6b414576506188c077d9a5806347f958a4e75d63 62184 libsynctex1_2015.20150524.37493-3_amd64.deb a5d619b32898b589e778f75a6acc0cad437d302e 128114 libtexlua52-dev_2015.20150524.37493-3_amd64.deb 0553a78bc3e815d15a6f01427c5c1a4c40bb1e48 106936 libtexlua52_2015.20150524.37493-3_amd64.deb cbc0fa9139d27e2a6631d522c02f27d1e6706038 264176 libtexluajit-dev_2015.20150524.37493-3_amd64.deb
Bug#790022: marked as done (tahoe-lafs: Depends on python2.6 which is no more available in unstable for 2 years)
Your message dated Fri, 26 Jun 2015 11:20:47 + with message-id e1z8rgd-lk...@franck.debian.org and subject line Bug#790022: fixed in tahoe-lafs 1.10.1-2 has caused the Debian Bug report #790022, regarding tahoe-lafs: Depends on python2.6 which is no more available in unstable for 2 years 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.) -- 790022: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: tahoe-lafs Version: 1.10.1-1 Severity: serious Dear Maintainer, tahoe-lafs can't be upgraded in Sid (at least on amd64) as the new package release depends on python2.6 (while the previous package didn't) which is no more available in Sid for two years now. (The information below shows dependencies for the package version 1.10.0-2.) -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tahoe-lafs depends on: ii net-tools 1.60-26+b1 ii python 2.7.9-1 ii python-crypto 2.6.1-5+b2 ii python-foolscap0.6.5-1 ii python-mock1.0.1-3 ii python-nevow 0.11.1-1 ii python-openssl 0.14-1 ii python-pkg-resources 17.0-1 ii python-pyasn1 0.1.7-1 ii python-pycryptopp 0.6.0.20120313-1 ii python-setuptools 17.0-1 ii python-simplejson 3.7.3-1 ii python-twisted 14.0.2-3 ii python-zfec1.4.5-2 ii python-zope.interface 4.1.1-3.1 tahoe-lafs recommends no packages. tahoe-lafs suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: tahoe-lafs Source-Version: 1.10.1-2 We believe that the bug you reported is fixed in the latest version of tahoe-lafs, 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. Ramakrishnan Muthukrishnan rkrish...@debian.org (supplier of updated tahoe-lafs 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, 26 Jun 2015 16:29:43 +0530 Source: tahoe-lafs Binary: tahoe-lafs Architecture: source all Version: 1.10.1-2 Distribution: unstable Urgency: medium Maintainer: Ramakrishnan Muthukrishnan rkrish...@debian.org Changed-By: Ramakrishnan Muthukrishnan rkrish...@debian.org Description: tahoe-lafs - Secure distributed file store Closes: 790022 Changes: tahoe-lafs (1.10.1-2) unstable; urgency=medium . * debian/pyversions: depend on 2.7 or above, as 2.6 is no longer available in sid (Closes: #790022). Checksums-Sha1: 9b29f8b44d5d99ff0dcdd59a8bb11fba6c423804 2015 tahoe-lafs_1.10.1-2.dsc d96711074c3af46ca502897de21d89a3d8d1a045 14420 tahoe-lafs_1.10.1-2.debian.tar.xz 3c9720c47e06854071b6dc7466257cf67b8dcedb 1112656 tahoe-lafs_1.10.1-2_all.deb Checksums-Sha256: 1c55960cbaf01c4dee26a3c292152db2c9da87ead727207b68bf51bc9dfc530e 2015 tahoe-lafs_1.10.1-2.dsc ed07150d5c92c605311d194f163c749ab1328e39c4d7a955488467acb1133b3c 14420 tahoe-lafs_1.10.1-2.debian.tar.xz 958081dba8aa4d30d75395bc6f9b5a051a0e4185267e7fe2ab313061b4e7b986 1112656 tahoe-lafs_1.10.1-2_all.deb Files: 36411c422bd82d32defbb147068f8a3f 2015 utils optional tahoe-lafs_1.10.1-2.dsc d7e80ca2f27f576b7847c4d6542ba369 14420 utils optional tahoe-lafs_1.10.1-2.debian.tar.xz fca706beb01da2f56b2c2ab307fa2ba8 1112656 utils optional tahoe-lafs_1.10.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVjTEtAAoJEM9kzWHrRsqa0d4P/jkoJs66RUWmVSSDXoZHdss9 aFhbSF4XHSo8qcW6f5svAjyrGBDHoheO7mNe5w2R6a9sxP2B6dxUudSXPQiTG+xt 0BSA5xQhucaL/dSqrRcgbzMOQtKDvzDJKJ3NeYj3W5kwCjk88lQEHAKEznRTMuz/ xvWyaZPu6W5ogMkGu2IU2bgFb1c4jO9i8XUmmIRBHYbBhBLoMR7y+MDc/nsqEvVu n1ba8E2wPo9tajrgZIjSA9vLBeNC3d/Q+igLIrKstQ/azfuaHjHnlyoA28kvZY5Z
Bug#778074: marked as done (ptlib: ftbfs with GCC-5)
Your message dated Fri, 26 Jun 2015 10:20:19 + with message-id e1z8qk7-0005jx...@franck.debian.org and subject line Bug#778074: fixed in ptlib 2.10.10~dfsg-5 has caused the Debian Bug report #778074, regarding ptlib: 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.) -- 778074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778074 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:ptlib Version: 2.10.10~dfsg-4.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/ptlib_2.10.10~dfsg-4.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 [...] compilation terminated. make[4]: *** [/«PKGBUILDDIR»/lib_linux_x86_64/obj/videoio.o] Error 1 ../make/common.mak:96: recipe for target '/«PKGBUILDDIR»/lib_linux_x86_64/obj/videoio.o' failed In file included from /«PKGBUILDDIR»/include/ptlib/contain.h:42:0, from /«PKGBUILDDIR»/include/ptlib.h:56, from ptlib/common/vfakeio.cxx:31: /«PKGBUILDDIR»/include/ptlib/critsec.h:46:33: fatal error: bits/atomicity.h: No such file or directory compilation terminated. make[4]: *** [/«PKGBUILDDIR»/lib_linux_x86_64/obj/vfakeio.o] Error 1 Makefile:101: recipe for target '/«PKGBUILDDIR»/lib_linux_x86_64/obj/vfakeio.o' failed make[4]: *** [/«PKGBUILDDIR»/lib_linux_x86_64/obj/vsdl.o] Error 1 Makefile:79: recipe for target '/«PKGBUILDDIR»/lib_linux_x86_64/obj/vsdl.o' failed In file included from /«PKGBUILDDIR»/include/ptlib/contain.h:42:0, from /«PKGBUILDDIR»/include/ptlib.h:56, from ptclib/pldap.cxx:35: /«PKGBUILDDIR»/include/ptlib/critsec.h:46:33: fatal error: bits/atomicity.h: No such file or directory compilation terminated. make[4]: *** [/«PKGBUILDDIR»/lib_linux_x86_64/obj/pldap.o] Error 1 ../make/common.mak:96: recipe for target '/«PKGBUILDDIR»/lib_linux_x86_64/obj/pldap.o' failed In file included from /«PKGBUILDDIR»/include/ptlib/contain.h:42:0, from /«PKGBUILDDIR»/include/ptlib.h:56, from ptclib/psasl.cxx:35: /«PKGBUILDDIR»/include/ptlib/critsec.h:46:33: fatal error: bits/atomicity.h: No such file or directory compilation terminated. make[4]: *** [/«PKGBUILDDIR»/lib_linux_x86_64/obj/pils.o] Error 1 ../make/common.mak:96: recipe for target '/«PKGBUILDDIR»/lib_linux_x86_64/obj/pils.o' failed make[4]: *** [/«PKGBUILDDIR»/lib_linux_x86_64/obj/psasl.o] Error 1 ../make/common.mak:96: recipe for target '/«PKGBUILDDIR»/lib_linux_x86_64/obj/psasl.o' failed In file included from /«PKGBUILDDIR»/include/ptlib/contain.h:42:0, from /«PKGBUILDDIR»/include/ptlib.h:56, from ptlib/common/vconvert.cxx:33: /«PKGBUILDDIR»/include/ptlib/critsec.h:46:33: fatal error: bits/atomicity.h: No such file or directory compilation terminated. make[4]: *** [/«PKGBUILDDIR»/lib_linux_x86_64/obj/vconvert.o] Error 1 ../make/common.mak:96: recipe for target '/«PKGBUILDDIR»/lib_linux_x86_64/obj/vconvert.o' failed make[4]: Leaving directory '/«PKGBUILDDIR»/src' make[3]: *** [optshared] Error 2 ../make/common.mak:292: recipe for target 'optshared' failed make[3]: Leaving directory '/«PKGBUILDDIR»/src' make[2]: *** [optshared] Error 2 make[2]: *** Waiting for unfinished jobs Makefile:91: recipe for target 'optshared' failed make[2]: Leaving directory '/«PKGBUILDDIR»' dh_auto_build: make -j10 optshared docs returned exit code 2 make[1]: *** [override_dh_auto_build] Error 2 debian/rules:26: recipe for
Bug#778074: Patch for GCC 5 build issue
On 25/06/15 19:27, Martin Michlmayr wrote: tags 778074 + patch thanks Here's a patch for the GCC 5 build issue. Sorry, I'm not sure how best to send patches for packages using quilt. BTW, it seems this issue is no longer present upstream: svn ls svn://svn.code.sf.net/p/opalvoip/code/ptlib/trunk/include/ptlib/ | grep crit It seems this is properly handled in configure now. Thank you very much, I have uploaded it. I forgot to add your name in the changelog, sorry. Kind regards, -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763218: marked as done (python-pysam: FTBFS: Tests failures)
Your message dated Fri, 26 Jun 2015 11:00:13 +
with message-id e1z8rmj-0007a2...@franck.debian.org
and subject line Bug#763218: fixed in python-pysam 0.8.3+ds1-1
has caused the Debian Bug report #763218,
regarding python-pysam: FTBFS: Tests failures
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.)
--
763218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: python-pysam
Version: 0.7.7-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140926 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
==
FAIL: testBAM (__main__.TestUnmappedReads)
--
Traceback (most recent call last):
File ./pysam_test_offline.py, line 998, in testBAM
self.assertEqual( len(list(samfile.fetch( until_eof = True))), 2 )
AssertionError: 0 != 2
--
Ran 158 tests in 9.110s
FAILED (failures=2, errors=31)
E: pybuild pybuild:256: test: plugin custom failed with: exit code=1: cd
tests PYTHONPATH=/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build python2.7
./pysam_test_offline.py
dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned exit
code 13
make[1]: *** [override_dh_auto_test] Error 13
debian/rules:29: recipe for target 'override_dh_auto_test' failed
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/09/26/python-pysam_0.7.7-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
---End Message---
---BeginMessage---
Source: python-pysam
Source-Version: 0.8.3+ds1-1
We believe that the bug you reported is fixed in the latest version of
python-pysam, 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 763...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Afif Elghraoui a...@ghraoui.name (supplier of updated python-pysam package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 25 Jun 2015 10:44:30 +0200
Source: python-pysam
Binary: python-pysam python3-pysam python-pysam-tests
Architecture: source all amd64
Version: 0.8.3+ds1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Med Packaging Team
debian-med-packag...@lists.alioth.debian.org
Changed-By: Afif Elghraoui a...@ghraoui.name
Description:
python-pysam - interface for the SAM/BAM sequence alignment and mapping format
(
python-pysam-tests - interface for the SAM/BAM sequence alignment and mapping
format (
python3-pysam - interface for the SAM/BAM sequence alignment and mapping
format (
Closes: 763218
Changes:
python-pysam (0.8.3+ds1-1) experimental; urgency=medium
.
* Team upload.
.
[ Jorge Soares ]
* New upstream version
* provide python3-pysam
.
[ Charles Plessy ]
* Requires Python 2.7 or higher.
.
[ Andreas Tille ]
* Link against htslib
* d/watch: dversionmangle
.
[ Afif Elghraoui ]
* New upstream releases (Closes: #763218)
* Remove unnecessary test-suite declaration in d/control
* Remove nonexistent files from copyright explanations
* Allow building of the package when non-ASCII characters are in the path
* Add to package long description
* Resolve lintian duplicated-compressed-file
* Make package descriptions unique
* Remove extra license definitions from d/copyright
* Fix spelling errors in source distribution (forwarded upstream as well)
* Add lintian overrides
* Exclude bundled htslib convenience-copy
* Provide get-orig-source rule
* Support building with missing htslib directory
* Add
Processed: Doesn't affect stable
Processing commands for cont...@bugs.debian.org:
notfound 778065 pktools/2.5.3-1
Bug #778065 {Done: Bas Couwenberg sebas...@debian.org} [src:pktools] pktools:
ftbfs with GCC-5
No longer marked as found in versions pktools/2.5.3-1.
found 778065 pktools/2.6.3-1
Bug #778065 {Done: Bas Couwenberg sebas...@debian.org} [src:pktools] pktools:
ftbfs with GCC-5
Marked as found in versions pktools/2.6.3-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
778065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778065
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
