Processed: Bumping severity of 701674 to grave because this makes it totally broken in jessie
Processing commands for cont...@bugs.debian.org: severity 701674 grave Bug #701674 [apf-firewall] apf-firewall doesn't work with kernel-version = 3.0 Severity set to 'grave' from 'important' # This package is completely broken on jessie, which has no 2.x kernels thanks Stopping processing here. Please contact me if you need assistance. -- 701674: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701674 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#792758: fsl-core: fsl fails to start on the command line
Package: fsl-core
Version: 5.0.8-3~nd80+1
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer, Dear Michael and co,
* What led up to the situation?
source /etc/fsl/fsl.sh fsl
* What was the outcome of this action?
Error in startup script: invalid command name Widget::syncoptions
while executing
Widget::syncoptions FileEntry Entry .e {-text {}}
(in namespace eval ::FileEntry script line 32)
invoked from within
namespace eval FileEntry {
Widget::define FileEntry fileentry Entry LabelFrame Button
Widget::declare FileEntry {
{-filebitmap String 1}
...
(file /usr/share/fsl/5.0/tcl/BWidget/BWExtras-1.0.0/fileentry.tcl line
63)
invoked from within
source /usr/share/fsl/5.0/tcl/BWidget/BWExtras-1.0.0/fileentry.tcl
(package ifneeded BWFileEntry 1.0.0 script)
invoked from within
package require BWFileEntry
(file /usr/share/fsl/5.0/tcl/fslstart.tcl line 51)
invoked from within
source [ file dirname [ info script ] ]/fslstart.tcl
(file /usr/share/fsl/5.0/tcl/fsl.tcl line 71)
invoked from within
source ${FSLDIR}/tcl/${origname}.tcl
(file /usr/lib/fsl/5.0/fsl line 25)
=-=-=-
If have tried to use wish tclsh 8.5 instead of the 8.6 default version (in
debian jessie) but the result is the same.
Could it be i am just missing some package? I installed 'fsl-complete'
Thank you in advance, regards,
Vincent
-- System Information:
Debian Release: 8.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/64 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages fsl-core depends on:
ii fsl-5.0-core 5.0.8-3~nd80+1
fsl-core recommends no packages.
fsl-core suggests no packages.
-- no debconf information
--
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is
uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onterecht
ontvangt, wordt u verzocht de inhoud niet te gebruiken en de afzender direct
te informeren door het bericht te retourneren. Het Universitair Medisch
Centrum Utrecht is een publiekrechtelijke rechtspersoon in de zin van de W.H.W.
(Wet Hoger Onderwijs en Wetenschappelijk Onderzoek) en staat geregistreerd bij
de Kamer van Koophandel voor Midden-Nederland onder nr. 30244197.
Denk s.v.p aan het milieu voor u deze e-mail afdrukt.
--
This message may contain confidential information and is intended exclusively
for the addressee. If you receive this message unintentionally, please do not
use the contents but notify the sender immediately by return e-mail. University
Medical Center Utrecht is a legal person by public law and is registered at
the Chamber of Commerce for Midden-Nederland under no. 30244197.
Please consider the environment before printing this e-mail.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Merge and tag
Processing commands for cont...@bugs.debian.org: merge 792741 792742 Bug #792741 [sqlitebrowser] [sqlitebrowser] Bug #792742 [sqlitebrowser] [sqlitebrowser] Merged 792741 792742 tags 792741 + moreinfo unreproducible Bug #792741 [sqlitebrowser] [sqlitebrowser] Bug #792742 [sqlitebrowser] [sqlitebrowser] Added tag(s) moreinfo and unreproducible. Added tag(s) unreproducible and moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 792741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792741 792742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792742 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#786882: marked as done (debian-installer: FTBFS on arm64: can't find dtbs)
Your message dated Sat, 18 Jul 2015 06:19:18 + with message-id e1zglsw-0008sc...@franck.debian.org and subject line Bug#786882: fixed in debian-installer 20150718 has caused the Debian Bug report #786882, regarding debian-installer: FTBFS on arm64: can't find dtbs 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.) -- 786882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: debian-installer Severity: serious Hi, The daily build FTBFS this way on arm64: | # These files are used to build special kernel images for some | # subarchitectures. Move them out of the way. | if [ -d ./tmp/device-tree/tree/usr/lib/kernel-image-4.0.0-1-arm64 ]; then mv ./tmp/device-tree/tree/usr/lib/kernel-image-4.0.0-1-arm64 ./tmp/device-tree/lib; fi; if [ -d ./tmp/device-tree/tree/usr/lib/linux-image-4.0.0-1-arm64 ]; then mv ./tmp/device-tree/tree/usr/lib/linux-image-4.0.0-1-arm64 ./tmp/device-tree/lib; fi; | # Move the kernel image out of the way. | mv -f ./tmp/device-tree/tree/boot/vmlinuz ./tmp/device-tree/vmlinuz; | test -e ./tmp/device-tree/tree/boot/zfs || rmdir ./tmp/device-tree/tree/boot/ | # Create an lsb release file. | if [ ! -e ./tmp/device-tree/tree/etc/lsb-release ]; then \ | set -e; \ | mkdir -p ./tmp/device-tree/tree/etc; \ | echo 'DISTRIB_ID=Debian' ./tmp/device-tree/tree/etc/lsb-release; \ | echo 'DISTRIB_DESCRIPTION=Debian GNU/Linux installer' ./tmp/device-tree/tree/etc/lsb-release; \ | echo 'DISTRIB_RELEASE=9 (stretch) - installer build 20150526-09:48' ./tmp/device-tree/tree/etc/lsb-release; \ | echo 'X_INSTALLATION_MEDIUM=device-tree' ./tmp/device-tree/tree/etc/lsb-release; \ | fi | mkdir -p ./dest/device-tree/ | set -ex ; for dtb in ./tmp/device-tree/lib/*.dtb ; do \ | tgt=./dest/device-tree/$(basename $dtb); \ | cp $dtb $tgt ; \ | update-manifest $tgt Device Tree Blob: $(basename $dtb);\ | done | + basename ./tmp/device-tree/lib/*.dtb | + tgt=./dest/device-tree/*.dtb | + cp ./tmp/device-tree/lib/*.dtb ./dest/device-tree/*.dtb | cp: cannot stat './tmp/device-tree/lib/*.dtb': No such file or directory | Makefile:772: recipe for target 'dest/device-tree/README' failed | make[2]: *** [dest/device-tree/README] Error 1 | Makefile:284: recipe for target '_build' failed | make[1]: *** [_build] Error 2 | Makefile:278: recipe for target 'build_device-tree' failed | make: *** [build_device-tree] Error 2 There seems to be some dtb dance here, and I think the src:linux's having relocated the dtbs under subdirectories is responsible for the FTBFS. Comparing some recent kernels: | kibi@wodi:/tmp/linux-kernel$ debdiff binary-kernel-image-3.16.0-4-arm64-di/kernel-image-3.16.0-4-arm64-di_3.16.7-ckt9-2_arm64.udeb binary-kernel-image-4.0.0-1-arm64-di/kernel-image-4.0.0-1-arm64-di_4.0.2-1_arm64.udeb | [The following lists of changes regard files as different if they have | different names, permissions or owners.] | | Files in second .deb but not in first | - | -rw-r--r-- root/root /lib/modules/4.0.0-1-arm64/modules.builtin | -rw-r--r-- root/root /lib/modules/4.0.0-1-arm64/modules.order | -rw-r--r-- root/root /usr/lib/linux-image-4.0.0-1-arm64/apm/apm-mustang.dtb | -rw-r--r-- root/root /usr/lib/linux-image-4.0.0-1-arm64/arm/foundation-v8.dtb | -rw-r--r-- root/root /usr/lib/linux-image-4.0.0-1-arm64/arm/juno.dtb | -rw-r--r-- root/root /usr/lib/linux-image-4.0.0-1-arm64/arm/rtsm_ve-aemv8a.dtb | | Files in first .deb but not in second | - | -rw-r--r-- root/root /lib/modules/3.16.0-4-arm64/modules.builtin | -rw-r--r-- root/root /lib/modules/3.16.0-4-arm64/modules.order | -rw-r--r-- root/root /usr/lib/linux-image-3.16.0-4-arm64/apm-mustang.dtb | -rw-r--r-- root/root /usr/lib/linux-image-3.16.0-4-arm64/foundation-v8.dtb | -rw-r--r-- root/root /usr/lib/linux-image-3.16.0-4-arm64/rtsm_ve-aemv8a.dtb → Besides the ABI bump, one can see apm/ and arm/ being introduced here. src:debian-installer likely needs to learn how to handle this. (Letting debian-arm@ know through x-d-cc.) Mraw, KiBi. ---End Message--- ---BeginMessage--- Source: debian-installer Source-Version: 20150718 We believe that the bug you reported is fixed in the latest version of debian-installer, 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
Bug#792741: marked as done ([sqlitebrowser])
Your message dated Sat, 18 Jul 2015 10:53:31 +0300 with message-id 877fpxq4uc@iki.fi and subject line Re: Bug#792742: [sqlitebrowser] has caused the Debian Bug report #792742, regarding [sqlitebrowser] 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.) -- 792742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sqlitebrowser Severity: grave --- Please enter the report below this line. --- Hi, I have installed sqliteborwser and synaptic declares that should exists the file /usr/bin/sqlitebrowser but it is not present! So this software is not usable Command 504 of 6 $ls /usr/bin/sq* /usr/bin/sq/usr/bin/sqlsharp /usr/bin/sqlt-diagram /usr/bin/sqlt-diff-old /usr/bin/sqlt-graph /usr/bin/squiggle /usr/bin/sqlmetal /usr/bin/sqlt /usr/bin/sqlt-diff /usr/bin/sqlt-dumper/usr/bin/squeak Please contact me if you need more information Best Marco --- System information. --- Architecture: amd64 Kernel: Linux 4.0.0-2-amd64 Debian Release: stretch/sid 500 testing-updates ftp.it.debian.org 500 testing www.deb-multimedia.org 500 testing security.debian.org 500 testing ftp.it.debian.org 500 testing apt.jenslody.de 500 stable-updates ftp.it.debian.org 500 stable security.debian.org 500 stable repo.wuala.com 500 stable ftp.it.debian.org 500 stable apt.spideroak.com 500 jessie linux.dropbox.com 500 debian packages.linuxmint.com 100 jessie-backports ftp.it.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- Think Marco, think different web site:http://www.di.unipi.it/~righi/ ---End Message--- ---BeginMessage--- HI PLEASE IGNORE MY PREVIOUS MESSAGE (IT FOLLOWS) I read this as this bug never existed, please close it, thus that is what I'm doing. If it does in fact exist please reopen it, and include at the very least the output of dpkg --status sqlitebrowser. -- Arto Jantunen---End Message---
Processed: found 788294 in rexical/1.0.5-1
Processing commands for cont...@bugs.debian.org: found 788294 rexical/1.0.5-1 Bug #788294 [rex,rexical] rex,rexical: error when trying to install together Marked as found in versions rexical/1.0.5-1. thanks Stopping processing here. Please contact me if you need assistance. -- 788294: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788294 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#792742: marked as done ([sqlitebrowser])
Your message dated Sat, 18 Jul 2015 10:53:31 +0300 with message-id 877fpxq4uc@iki.fi and subject line Re: Bug#792742: [sqlitebrowser] has caused the Debian Bug report #792742, regarding [sqlitebrowser] 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.) -- 792742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sqlitebrowser Severity: grave --- Please enter the report below this line. --- HI PLEASE IGNORE MY PREVIOUS MESSAGE (IT FOLLOWS) == Hi, I have installed sqliteborwser and synaptic declares that should exists the file /usr/bin/sqlitebrowser but it is not present! So this software is not usable Command 504 of 6 $ls /usr/bin/sq* /usr/bin/sq/usr/bin/sqlsharp /usr/bin/sqlt-diagram /usr/bin/sqlt-diff-old /usr/bin/sqlt-graph /usr/bin/squiggle /usr/bin/sqlmetal /usr/bin/sqlt /usr/bin/sqlt-diff /usr/bin/sqlt-dumper/usr/bin/squeak Please contact me if you need more information Best Marco --- System information. --- Architecture: amd64 Kernel: Linux 4.0.0-2-amd64 Debian Release: stretch/sid 500 testing-updates ftp.it.debian.org 500 testing www.deb-multimedia.org 500 testing security.debian.org 500 testing ftp.it.debian.org 500 testing apt.jenslody.de 500 stable-updates ftp.it.debian.org 500 stable security.debian.org 500 stable repo.wuala.com 500 stable ftp.it.debian.org 500 stable apt.spideroak.com 500 jessie linux.dropbox.com 500 debian packages.linuxmint.com 100 jessie-backports ftp.it.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- Think Marco, think different web site:http://www.di.unipi.it/~righi/ ---End Message--- ---BeginMessage--- HI PLEASE IGNORE MY PREVIOUS MESSAGE (IT FOLLOWS) I read this as this bug never existed, please close it, thus that is what I'm doing. If it does in fact exist please reopen it, and include at the very least the output of dpkg --status sqlitebrowser. -- Arto Jantunen---End Message---
Bug#792762: arc-gui-clients: /usr/bin/arcsub-ui segfaults, adequate reports symbol-size-mismatch
Package: arc-gui-clients Version: 0.4.6-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed adequate reports some issues with your package: 0m48.0s ERROR: WARN: Inadequate results from running adequate! arc-gui-clients: undefined-symbol /usr/bin/arcproxy-ui = _ZN3Arc3URLC1ERKSsb arc-gui-clients: undefined-symbol /usr/bin/arcstorage-ui = _ZN3Arc3URLC1ERKSsb arc-gui-clients: symbol-size-mismatch /usr/bin/arcsub-ui = _ZTVN3Arc11URLLocationE arc-gui-clients: undefined-symbol /usr/bin/arcsub-ui = _ZN3Arc3URLC1ERKSsb so I got curious and installed it in a (amd64) pbuilder chroot. Running the /usr/bin/arcsub-ui binary results in an immediate segfault. After rebuilding the package in sid the segfault is gone, so a binNMU would be sufficient to fix this. But the root cause for this bug needs to be investigated, otherwise it might happen again in the future. The size-mismatching symbol is part of libarccommon.so.3, package libarccommon3, so maybe the dependency versioning is not strict enough to prevent this bug. Andeas arc-gui-clients_0.4.6-1.log.gz Description: application/gzip
Bug#778055: marked as done (padevchooser: ftbfs with GCC-5)
Your message dated Sat, 18 Jul 2015 10:19:42 + with message-id e1zgpda-0006gm...@franck.debian.org and subject line Bug#778055: fixed in padevchooser 0.9.4-1.2 has caused the Debian Bug report #778055, regarding padevchooser: 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.) -- 778055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:padevchooser Version: 0.9.4-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/padevchooser_0.9.4-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 [...] checking for style of include used by make... GNU checking dependency style of gcc... none checking whether ln -s works... yes checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for GUILIBS... yes checking for PULSE... yes checking for AVAHI... yes checking for lynx... yes checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating doc/Makefile config.status: creating doc/README.html config.status: creating config.h config.status: executing depfiles commands configure: WARNING: unrecognized options: --disable-maintainer-mode dh_auto_build -a -O--parallel make[1]: Entering directory '/«PKGBUILDDIR»' make all-recursive make[2]: Entering directory '/«PKGBUILDDIR»' Making all in src make[3]: Entering directory '/«PKGBUILDDIR»/src' gcc -DHAVE_CONFIG_H -I. -I.. -D_REENTRANT -DORBIT2=1 -pthread -I/usr/include/libglade-2.0 -I/usr/include/libgnomeui-2.0 -I/usr/include/gnome-keyring-1 -I/usr/include/libbonoboui-2.0 -I/usr/include/libxml2 -I/usr/include/libgnome-2.0 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/orbit-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/gail-1.0 -I/usr/include/libart-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/x86_64-linux-gnu/gnome-vfs-2.0/include -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib -2.0/include -I/usr/include/freetype2 -I/usr/include/startup-notification-1.0 -I/usr/include/gnome-desktop-2.0 -D_REENTRANT -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -D_REENTRANT -DGLADE_FILE=\/usr/share/padevchooser/padevchooser.glade\ -DDESKTOP_FILE=\/usr/share/applications/padevchooser.desktop\ -DDESKTOP_DIR=\/usr/share/applications\ -D_FORTIFY_SOURCE=2 -pipe -Wall -W -Wno-unused-parameter -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o padevchooser.o padevchooser.c gcc -DHAVE_CONFIG_H -I. -I.. -D_REENTRANT -DORBIT2=1 -pthread -I/usr/include/libglade-2.0 -I/usr/include/libgnomeui-2.0 -I/usr/include/gnome-keyring-1 -I/usr/include/libbonoboui-2.0 -I/usr/include/libxml2
Bug#788294: marked as done (rex,rexical: error when trying to install together)
Your message dated Sat, 18 Jul 2015 10:50:20 + with message-id e1zgphe-00031d...@franck.debian.org and subject line Bug#788294: fixed in rexical 1.0.5-2 has caused the Debian Bug report #788294, regarding rex,rexical: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 788294: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788294 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: rex,rexical Version: 1.0.5-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 1.2.1-1 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package rex. Preparing to unpack .../archives/rex_1.2.1-1_all.deb ... Unpacking rex (1.2.1-1) ... dpkg: error processing archive /var/cache/apt/archives/rex_1.2.1-1_all.deb (--unpack): trying to overwrite '/usr/bin/rex', which is also in package rexical 1.0.5-1 Errors were encountered while processing: /var/cache/apt/archives/rex_1.2.1-1_all.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/bin/rex This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html rexical=1.0.5-1_rex=1.2.1-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: rexical Source-Version: 1.0.5-2 We believe that the bug you reported is fixed in the latest version of rexical, 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. Balasankar C balasank...@autistici.org (supplier of updated rexical package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 18 Jul 2015 15:51:08 +0530 Source: rexical Binary: rexical Architecture: source all Version: 1.0.5-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Balasankar C balasank...@autistici.org Description: rexical- Lexical scanner generator for Ruby Closes: 788294 Changes: rexical (1.0.5-2) unstable; urgency=medium . * Change name of binary from rex to rexical (Closes: #788294) Checksums-Sha1: a696ae27ed0c4b24cd21a4092bee3188ac323b0f 1661 rexical_1.0.5-2.dsc df35e7d351ca2407e998a32572b217b8e4989655 5164 rexical_1.0.5-2.debian.tar.xz a5b1a86e580eec964aa8a857bbe8dd21fb0f3cb7 14730 rexical_1.0.5-2_all.deb Checksums-Sha256: 8bac9c769a3c4a86935fdae8bcb2b7bb89e57fab5136969597135805e35eb069 1661 rexical_1.0.5-2.dsc 8622b01d6816c34a6f415f736736093f8388eec650eea5011a89b83c9f5050be 5164 rexical_1.0.5-2.debian.tar.xz 6107d1dbc38378caeb590390d8865e3a1ab28106fa347d23a22e45e119cb17a9 14730 rexical_1.0.5-2_all.deb Files: 71c222f3253abf08de03da556d656d95 1661 ruby optional rexical_1.0.5-2.dsc 7f2a177a08f2a99237e50723a5cfb59a 5164 ruby optional rexical_1.0.5-2.debian.tar.xz
Bug#792768: ruby-fog-powerdns: /usr/bin/console already used by conserver-client
Package: ruby-fog-powerdns Version: 0.1.1-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: affects -1 + conserver-client Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package ruby-fog-powerdns. Preparing to unpack .../ruby-fog-powerdns_0.1.1-1_all.deb ... Unpacking ruby-fog-powerdns (0.1.1-1) ... dpkg: error processing archive /var/cache/apt/archives/ruby-fog-powerdns_0.1.1-1_all.deb (--unpack): trying to overwrite '/usr/bin/console', which is also in package conserver-client 8.1.18-2.2 Errors were encountered while processing: /var/cache/apt/archives/ruby-fog-powerdns_0.1.1-1_all.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/bin/console This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html conserver-client=8.1.18-2.2_ruby-fog-powerdns=0.1.1-1.log.gz Description: application/gzip
Processed: ruby-fog-powerdns: /usr/bin/console already used by conserver-client
Processing control commands: affects -1 + conserver-client Bug #792768 [ruby-fog-powerdns] ruby-fog-powerdns: /usr/bin/console already used by conserver-client Added indication that 792768 affects conserver-client -- 792768: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792768 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#792767: python3-zipstream: ships /usr/lib/python3/dist-packages/tests/__init__.py
Package: python3-zipstream Version: 1.1.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite /usr/lib/python3/dist-packages/tests/__init__.py is a very generic name that is prone to file overwrite conflicts between packages (which caused its detection). Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: tag 792062 + pending Bug #792062 [src:circuits] FTBFS: test_secure_server fails: urlopen error: CERTIFICATE_VERIFY_FAILED Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 792062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792062 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#787866: marked as done (autogen: after upgrade to 5.18.5 autogen no longer works)
Your message dated Sat, 18 Jul 2015 15:34:51 +
with message-id e1zgu8z-00037u...@franck.debian.org
and subject line Bug#787866: fixed in autogen 1:5.18.6~pre3-2
has caused the Debian Bug report #787866,
regarding autogen: after upgrade to 5.18.5 autogen no longer works
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.)
--
787866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: autogen
Version: 1:5.18.5-2
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
Trying to run autogen on my def files fails consistently after upgrading
5.18.5. Downgrading to the .4 version works again.
* What exactly did you do (or not do) that was effective (or
ineffective)?
$ autogen ocpasswd-args.def
(the file is attached)
* What was the outcome of this action?
Error in template /usr/share/autogen/optlib.tlib, line 780
DEFINITIONS ERROR in /usr/share/autogen/optlib.tlib line 780 for
ocpasswd-args.h:
Error: value for opt passwd is `c'
must be single char or 'NUMBER'
Failing Guile command: = = = = =
(error (sprintf
Error: value for opt %s is `%s'\nmust be single char or 'NUMBER'
(get name) (get value)))
=
* What outcome did you expect instead?
no output. The .c and .h files should have been generated.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages autogen depends on:
ii guile-2.0-libs 2.0.11+1-9
ii libc6 2.19-18
ii libopts25 1:5.18.5-2
ii libopts25-dev 1:5.18.5-2
ii libxml2 2.9.2+dfsg1-3
Versions of packages autogen recommends:
ii autogen-doc 1:5.18.5-2
autogen suggests no packages.
AutoGen Definitions options;
prog-name = ocpasswd;
prog-title= OpenConnect server password utility;
prog-desc = OpenConnect VPN server plain password file handling program.;
disable-save;
no-xlate = opt;
gnu-usage;
config-header = config.h;
long-opts;
no-misuse-usage;
short-usage = Usage: ocpasswd -c [passwd] [options] username\nocpasswd
--help for usage instructions.\n;
explain = ;
reorder-args;
argument = [username];
detail = This program is openconnect password (ocpasswd) utility. It allows
the generation
and handling of a 'plain' password file used by ocserv.;
copyright = {
date = 2013, 2014;
owner = Nikos Mavrogiannopoulos;
author = Nikos Mavrogiannopoulos;
eaddr = openconnect-de...@lists.infradead.org;
type = gplv2;
};
flag = {
name = passwd;
value = c;
arg-type = file;
descrip = Password file;
doc = ;
};
flag = {
name = groupname;
value = g;
arg-type = string;
descrip = User's group name;
doc = ;
};
flag = {
name = delete;
value = d;
descrip = Delete user;
doc = Removes the specified user from the password file;
};
flag = {
name = lock;
value = l;
descrip = Lock user;
doc = Prevents the specified user from logging in;
};
flag = {
name = unlock;
value = u;
descrip = Unlock user;
doc = Re-enables login for the specified user;
};
help-value= h;
doc-section = {
ds-type = 'FILES';
ds-format = 'texi';
ds-text = -_EOT_
@subheading Password file format
The password format of ocpasswd is as follows.
@example
username:groupname:encoded-password
@end example
The crypt(3) encoding is used for the encoded-password.
_EOT_;
};
doc-section = {
ds-type = 'EXAMPLES';
ds-format = 'texi';
ds-text = -_EOT_
@subheading Adding a user
@example
$ ocpasswd -c ocpasswd my_username
@end example
@subheading Locking a user
@example
$ ocpasswd -c ocpasswd -l my_username
@end example
@subheading Unlocking a user
@example
$ ocpasswd -c ocpasswd -u my_username
@end example
_EOT_;
};
doc-section = {
ds-type = 'SEE ALSO';
ds-format = 'man';
ds-text = -_EOText_
ocserv(8), occtl(8)
_EOText_;
};
---End Message---
---BeginMessage---
Source: autogen
Source-Version: 1:5.18.6~pre3-2
We believe that the bug you reported is fixed in the latest version of
autogen, which is due to be installed in the Debian FTP
Bug#761211: marked as done (guile-gnome-platform: please migrate to guile-2.0)
Your message dated Sat, 18 Jul 2015 09:49:20 + with message-id e1zgokc-0001en...@franck.debian.org and subject line Bug#761211: fixed in guile-gnome-platform 2.16.2-2 has caused the Debian Bug report #761211, regarding guile-gnome-platform: please migrate to guile-2.0 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.) -- 761211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761211 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: guile-gnome-platform I'm planning to have guile-1.8 removed from unstable before the freeze; please migrate to guile-2.0 as soon as possible. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 ---End Message--- ---BeginMessage--- Source: guile-gnome-platform Source-Version: 2.16.2-2 We believe that the bug you reported is fixed in the latest version of guile-gnome-platform, 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 761...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann a...@debian.org (supplier of updated guile-gnome-platform 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: Sat, 18 Jul 2015 11:12:10 +0200 Source: guile-gnome-platform Binary: guile-gnome2-glib guile-gnome2-gconf guile-gnome2-gtk guile-gnome2-gnome guile-gnome2-gnome-ui guile-gnome2-canvas guile-gnome2-vfs guile-gnome2-dev Architecture: source Version: 2.16.2-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Andreas Beckmann a...@debian.org Description: guile-gnome2-canvas - Guile bindings for libgnomecanvas guile-gnome2-dev - Guile GObject binding support library, development files guile-gnome2-gconf - Guile bindings for GConf guile-gnome2-glib - Guile bindings for GLib guile-gnome2-gnome - Guile bindings for libgnome guile-gnome2-gnome-ui - Guile bindings for libgnome guile-gnome2-gtk - Guile bindings for GTK+, libglade, Pango and ATK guile-gnome2-vfs - Guile bindings for GnomeVFS Closes: 761211 Changes: guile-gnome-platform (2.16.2-2) unstable; urgency=medium . [ Andreas Beckmann ] * QA upload. * Set maintainer to Debian QA Group. (See: #743714) * Fix lintian warning build-depends-on-1-revision. . [ أحمد المحمودي (Ahmed El-Mahmoudy) ] * Sync changes from Ubuntu. (Closes: #761211) Checksums-Sha1: dd888444fc11f5eecd15982dce8780df45413f9c 2676 guile-gnome-platform_2.16.2-2.dsc 9a3ea46f766b128b2b0647537573ebdc8413cc2d 9588 guile-gnome-platform_2.16.2-2.debian.tar.xz Checksums-Sha256: a444fecb999149215d63a51dd58f48dc412553cff9b7e8a99a32bfe5ed89224b 2676 guile-gnome-platform_2.16.2-2.dsc ddf68c046b3f42f215d662983afdd7860a2908162f333bd91ade06c51e486d17 9588 guile-gnome-platform_2.16.2-2.debian.tar.xz Files: 1d1aec061a0c2c4e90671a41b99df850 2676 lisp extra guile-gnome-platform_2.16.2-2.dsc 19ec3ae4a452beb9a7f404f9c68fa00f 9588 lisp extra guile-gnome-platform_2.16.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVqh9nAAoJEF+zP5NZ6e0IBjQP/iJy20XwMzE7GCAmW0hVvTKh qmSFY2MCJxEcKkeFBBN6sYOsPx7Ovdd1C5MwG2C8vXPCLoqnBmwC2xkQKj0MEFXV fvaasebfkCKWSzJqvlz3UdP/AZAQXQAKQC35WbYy+4GJae93mDyc/k/86ro0qUIC 1dMmIPPEEfXtYOb9Lz564CNMSB3fBslpx2438XKu5FxB6zkNqHIq0uvefOlpMNdm mCpxRDekWlX0vr89emZi6Bl2v6+gN5mhyEsrSPXqsqI8K2v7L0xEQq2Xhjl43lk1 yEeLPYU1uLzgpyzzPfmPY2IISZGfK7VtNQYP95EhAfMAeCW8in8zuaXFBTzMHm/Y 15toTD9LDoyUZ3P/+lMPeXXO1aEKLHjRhZRWVjVso1EV5+BXNyojcFqFiXWL3fFT WdogyAO/GhO6KR5yl5ctKEl//TUAeqecYPXVHo97hDLB3QvbC5imyZjKTyQMfy5+ JDqBKgQbtCrpjqTZOpZFKy8+TajPka6co+JmzG1lW0PqMursb+iQjmRN87b6D1PE qlIS8Ln6e/7npem6qirPAasCSXjJHB3SHJBPp7jnXjp4GRueMXNA5fgMIr43f46Y jg/CiD84HLFuYNQexcma2bCV1A0maaD4Xpy4DFs+b5ll05r57Q4YpG7rQKsdJETR tlBm1AaGDTN8ksmRe7Xu =4BR4 -END PGP SIGNATUREEnd Message---
Bug#788294: rex,rexical: error when trying to install together
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Mon, 15 Jun 2015 16:26:40 +0200 Alex Mestiashvili a...@biotec.tu-dresden.de wrote: Hi Balasankar, Our packages have a name conflict - /usr/bin/rex. Please see the initial bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788294 Would you mind renaming the rex from rexical package to something else? rexical seem to be a good name for example. Alternatively I can consider renaming rex from rex package, but because your package is younger in terms of presence in Debian I think that it should be easier to rename rexical's rex. Sure. I'll rename rex to rexical ASAP. Sorry for the delay. - -- Regards Balasankar C http://balasankarc.in -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCgAGBQJVqiX2AAoJEJbtq5sua3FxJU4H/j/KPP554UberoiJICuKSXIg X1hN1V0X34pkuBAk7KlAfmbEb/8GRRXLBvk8jLSkNvBr+JjPACWjaQXcfHbPhFCs DH6Ur1OlA3JT+ezGw3M23rKUfotRD3QRP1OwvI/QORScj7VodJkXCHjk12mcgavL qHwSffwh+2pY7jIGetzQcuQYo3JIEDWLP93P5atCJwWVS/ryrEkemMKONpyzcmQf goPrPIjQpApzjFLGSK3mOisFCxP/T2ke9rEsCZRSWm4iaUILMz+kP+A4gRHc1PZG nu8ppS75xVDpQJ+5eq99GpcLI1x0pjdzKICug0RU2JvAIDA8O27qIwSGcw/QLZU= =aF4I -END PGP SIGNATURE- 0x2E6B7171.asc Description: application/pgp-keys
Bug#792766: python3-phply: ships /usr/lib/python3/dist-packages/tests/__init__.py
Package: python3-phply Version: 0.9.1-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite /usr/lib/python3/dist-packages/tests/__init__.py is a very generic name that is prone to file overrides conflicts between packages (which caused its detection). Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778157: user-mode-linux: diff for NMU version 4.0-1um-0.1
Control: tags -1 + patch pending
Dear maintainer,
I've prepared an NMU for user-mode-linux (versioned as 4.0-1um-0.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I should delay
it longer.
--
Jakub Wilk
diffstat for user-mode-linux-3.16-1um user-mode-linux-4.0-1um
config.amd64 | 248 +++---
config.i386 | 249 +++
debian/changelog | 11 +
debian/control |2
debian/patches/08-gcc5.patch | 23 +++
debian/patches/series|1
debian/rules |2
7 files changed, 404 insertions(+), 132 deletions(-)
Control files: lines which differ (wdiff format)
Build-Depends: debhelper ( 5.0.0), quilt, [-linux-source-3.16,-] {+linux-source-4.0,+} docbook-to-man, xz-utils, m4, module-init-tools, libvdeplug2-dev, libpcap-dev, bc, dpkg (= 1.16.2)
diff -Nru user-mode-linux-3.16-1um/config.amd64 user-mode-linux-4.0-1um/config.amd64
--- user-mode-linux-3.16-1um/config.amd64 2014-10-28 23:44:23.0 +0100
+++ user-mode-linux-4.0-1um/config.amd64 2015-07-17 23:23:08.0 +0200
@@ -1,13 +1,13 @@
#
# Automatically generated file; DO NOT EDIT.
-# User Mode Linux/x86_64 3.16.5 Kernel Configuration
+# User Mode Linux/x86_64 4.0.8 Kernel Configuration
#
CONFIG_UML=y
CONFIG_MMU=y
CONFIG_NO_IOMEM=y
# CONFIG_TRACE_IRQFLAGS_SUPPORT is not set
CONFIG_LOCKDEP_SUPPORT=y
-# CONFIG_STACKTRACE_SUPPORT is not set
+CONFIG_STACKTRACE_SUPPORT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_BUG=y
CONFIG_HZ=100
@@ -60,10 +60,12 @@
CONFIG_NEED_PER_CPU_KM=y
CONFIG_CLEANCACHE=y
CONFIG_FRONTSWAP=y
-# CONFIG_ZBUD is not set
# CONFIG_ZSWAP is not set
+CONFIG_ZPOOL=m
+# CONFIG_ZBUD is not set
CONFIG_ZSMALLOC=m
# CONFIG_PGTABLE_MAPPING is not set
+# CONFIG_ZSMALLOC_STAT is not set
CONFIG_LD_SCRIPT_DYN=y
CONFIG_BINFMT_ELF=y
# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
@@ -108,6 +110,7 @@
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_SHOW=y
+CONFIG_IRQ_DOMAIN=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
@@ -136,9 +139,12 @@
# RCU Subsystem
#
CONFIG_TINY_RCU=y
-# CONFIG_PREEMPT_RCU is not set
+CONFIG_SRCU=y
+# CONFIG_TASKS_RCU is not set
# CONFIG_RCU_STALL_COMMON is not set
# CONFIG_TREE_RCU_TRACE is not set
+CONFIG_RCU_KTHREAD_PRIO=0
+CONFIG_BUILD_BIN2C=y
CONFIG_IKCONFIG=m
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=14
@@ -149,7 +155,7 @@
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_CGROUP_CPUACCT=y
-CONFIG_RESOURCE_COUNTERS=y
+CONFIG_PAGE_COUNTER=y
CONFIG_MEMCG=y
CONFIG_MEMCG_DISABLED=y
CONFIG_MEMCG_SWAP=y
@@ -183,6 +189,7 @@
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
CONFIG_HAVE_UID16=y
+CONFIG_BPF=y
# CONFIG_EXPERT is not set
CONFIG_UID16=y
# CONFIG_SGETMASK_SYSCALL is not set
@@ -194,12 +201,15 @@
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
+CONFIG_HAVE_FUTEX_CMPXCHG=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
+# CONFIG_BPF_SYSCALL is not set
CONFIG_SHMEM=y
CONFIG_AIO=y
+CONFIG_ADVISE_SYSCALLS=y
# CONFIG_EMBEDDED is not set
#
@@ -210,7 +220,7 @@
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not set
CONFIG_SLUB=y
-# CONFIG_SYSTEM_TRUSTED_KEYRING is not set
+CONFIG_SYSTEM_TRUSTED_KEYRING=y
# CONFIG_PROFILING is not set
# CONFIG_UPROBES is not set
CONFIG_HAVE_64BIT_ALIGNED_ACCESS=y
@@ -221,6 +231,7 @@
#
# GCOV-based kernel profiling
#
+# CONFIG_ARCH_HAS_GCOV_PROFILE_ALL is not set
# CONFIG_HAVE_GENERIC_DMA_COHERENT is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
@@ -232,6 +243,7 @@
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
# CONFIG_MODULE_SIG is not set
+# CONFIG_MODULE_COMPRESS is not set
CONFIG_BLOCK=y
CONFIG_BLK_DEV_BSG=y
CONFIG_BLK_DEV_BSGLIB=y
@@ -280,7 +292,7 @@
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED=cfq
-CONFIG_ASN1=m
+CONFIG_ASN1=y
CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
CONFIG_INLINE_READ_UNLOCK=y
CONFIG_INLINE_READ_UNLOCK_IRQ=y
@@ -323,11 +335,14 @@
CONFIG_FW_LOADER=y
# CONFIG_FIRMWARE_IN_KERNEL is not set
CONFIG_EXTRA_FIRMWARE=
-CONFIG_FW_LOADER_USER_HELPER=y
+# CONFIG_FW_LOADER_USER_HELPER_FALLBACK is not set
+CONFIG_ALLOW_DEV_COREDUMP=y
# CONFIG_SYS_HYPERVISOR is not set
CONFIG_GENERIC_CPU_DEVICES=y
CONFIG_REGMAP=y
CONFIG_REGMAP_I2C=m
+CONFIG_REGMAP_SPMI=m
+CONFIG_REGMAP_IRQ=y
# CONFIG_DMA_SHARED_BUFFER is not set
#
@@ -353,7 +368,7 @@
CONFIG_BLK_DEV_RAM=m
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=4096
-CONFIG_BLK_DEV_XIP=y
+CONFIG_BLK_DEV_RAM_DAX=y
CONFIG_ATA_OVER_ETH=m
CONFIG_BLK_DEV_RBD=m
@@ -397,6 +412,10 @@
CONFIG_ALTERA_STAPL=m
#
+# Intel MIC Bus Driver
+#
+
+#
# Intel MIC Host Driver
#
@@ -404,6 +423,7 @@
# Intel MIC Card Driver
#
CONFIG_ECHO=m
+# CONFIG_CXL_BASE is not set
#
# SCSI device support
@@ -412,8 +432,8 @@
CONFIG_RAID_ATTRS=m
Processed: user-mode-linux: diff for NMU version 4.0-1um-0.1
Processing control commands: tags -1 + patch pending Bug #778157 [src:user-mode-linux] user-mode-linux: ftbfs with GCC-5 Added tag(s) pending and patch. -- 778157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778157 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#791784: marked as done (FTBFS: error: call to 'rb_check_safe_str' declared with attribute error: rb_check_safe_str() and Check_SafeStr() are obsolete)
Your message dated Sat, 18 Jul 2015 12:50:22 + with message-id e1zgrzo-0005fw...@franck.debian.org and subject line Bug#791784: fixed in ruby-serialport 1.3.1-1 has caused the Debian Bug report #791784, regarding FTBFS: error: call to 'rb_check_safe_str' declared with attribute error: rb_check_safe_str() and Check_SafeStr() are obsolete 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.) -- 791784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-serialport Version: 1.3.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, your package ruby-serialport currently FTBFS in unstable. Relevant snippet: /usr/include/ruby-2.2.0/ruby/ruby.h:551:27: error: call to 'rb_check_safe_str' declared with attribute error: rb_check_safe_str() and Check_SafeStr() are obsolete; use SafeStringValue() instead # define Check_SafeStr(v) rb_check_safe_str((VALUE)(v)) ^ posix_serialport_impl.c:129:10: note: in expansion of macro 'Check_SafeStr' Check_SafeStr(_port); ^ make[1]: *** [posix_serialport_impl.o] Error 1 Makefile:237: recipe for target 'posix_serialport_impl.o' failed make[1]: Leaving directory '/«PKGBUILDDIR»/ext/native' ↓ mkmf.log ~ cat: mkmf.log: No such file or directory /usr/lib/ruby/2.2.0/rubygems/ext/builder.rb:89:in `run': make failed, exit code 2 (Gem::InstallError) sbuild (Debian sbuild) 0.65.2 (24 Mar 2015) on sxl.home.zeha.at ╔══╗ ║ ruby-serialport 1.3.0-1 (amd64)08 Jul 2015 13:11 ║ ╚══╝ Package: ruby-serialport Version: 1.3.0-1 Source Version: 1.3.0-1 Distribution: sid Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 I: NOTICE: Log filtering will replace 'build/ruby-serialport-KnhGeW/ruby-serialport-1.3.0' with '«PKGBUILDDIR»' I: NOTICE: Log filtering will replace 'build/ruby-serialport-KnhGeW' with '«BUILDDIR»' I: NOTICE: Log filtering will replace 'var/lib/schroot/mount/sid-amd64-sbuild-99530d8d-057f-47c4-b1a3-b40136ce774b' with '«CHROOT»' ┌──┐ │ Update chroot│ └──┘ Get:1 http://ftp.at.debian.org sid InRelease [204 kB] Get:2 http://ftp.at.debian.org sid/main Sources/DiffIndex [7876 B] Get:3 http://ftp.at.debian.org sid/main amd64 Packages/DiffIndex [7876 B] Get:4 http://ftp.at.debian.org sid/main Translation-en/DiffIndex [7876 B] Get:5 http://ftp.at.debian.org sid/main 2015-07-01-2039.58.pdiff [18.5 kB] Get:6 http://ftp.at.debian.org sid/main 2015-07-02-0242.54.pdiff [16.2 kB] Get:7 http://ftp.at.debian.org sid/main 2015-07-02-0843.38.pdiff [7440 B] Get:8 http://ftp.at.debian.org sid/main 2015-07-02-1442.16.pdiff [11.6 kB] Get:9 http://ftp.at.debian.org sid/main 2015-07-02-2043.11.pdiff [20.4 kB] Get:10 http://ftp.at.debian.org sid/main 2015-07-03-0245.09.pdiff [6119 B] Get:11 http://ftp.at.debian.org sid/main 2015-07-03-0843.41.pdiff [24.5 kB] Get:12 http://ftp.at.debian.org sid/main 2015-07-03-1444.58.pdiff [13.1 kB] Get:13 http://ftp.at.debian.org sid/main 2015-07-03-2044.28.pdiff [10.5 kB] Get:14 http://ftp.at.debian.org sid/main 2015-07-04-0246.30.pdiff [7778 B] Get:15 http://ftp.at.debian.org sid/main 2015-07-04-0845.59.pdiff [5651 B] Get:16 http://ftp.at.debian.org sid/main 2015-07-04-1446.01.pdiff [4838 B] Get:17 http://ftp.at.debian.org sid/main 2015-07-04-2045.12.pdiff [14.4 kB] Get:18 http://ftp.at.debian.org sid/main 2015-07-05-0244.24.pdiff [14.9 kB] Get:19 http://ftp.at.debian.org sid/main 2015-07-05-0844.23.pdiff [4527 B] Get:20 http://ftp.at.debian.org sid/main 2015-07-05-1446.24.pdiff [5631 B] Get:21 http://ftp.at.debian.org sid/main 2015-07-05-2043.54.pdiff [17.5 kB] Get:22 http://ftp.at.debian.org sid/main 2015-07-06-0248.36.pdiff [6837 B] Get:23 http://ftp.at.debian.org sid/main 2015-07-06-0845.38.pdiff [4425 B] Get:24 http://ftp.at.debian.org sid/main 2015-07-06-1445.53.pdiff [6251 B] Get:25 http://ftp.at.debian.org sid/main 2015-07-06-2045.28.pdiff [9427 B] Get:26 http://ftp.at.debian.org sid/main 2015-07-07-0248.04.pdiff [18.8 kB] Get:27 http://ftp.at.debian.org sid/main 2015-07-07-0850.55.pdiff [5417 B] Get:28
Bug#790533: marked as done (octave: FTBFS on multiple archs during binNMU for qscintilla2 transition)
Your message dated Sat, 18 Jul 2015 12:49:28 + with message-id e1zgryw-0004h4...@franck.debian.org and subject line Bug#790533: fixed in octave 4.0.0-2 has caused the Debian Bug report #790533, regarding octave: FTBFS on multiple archs during binNMU for qscintilla2 transition 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.) -- 790533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: octave Version: 3.8.2-4+b1 Severity: serious Justification: fails to build from source (but built successfully in the past) FTBFS, but doesn't appear to be related to the qscintilla2 transition. So far on all archs attempted (amd64, i386, and powerpc). https://buildd.debian.org/status/fetch.php?pkg=octavearch=amd64ver=3.8.2-4%2Bb1stamp=1435623998 https://buildd.debian.org/status/fetch.php?pkg=octavearch=i386ver=3.8.2-4%2Bb1stamp=1435622628 https://buildd.debian.org/status/fetch.php?pkg=octavearch=powerpcver=3.8.2-4%2Bb1stamp=1435624362 Tail of log for octave on amd64/i386/powerpc: make[4]: *** Waiting for unfinished jobs Makefile:2118: recipe for target 'octave.dvi' failed make[4]: Leaving directory '/«PKGBUILDDIR»/doc/interpreter' make[3]: *** [all-recursive] Error 1 Makefile:1897: recipe for target 'all-recursive' failed make[3]: Leaving directory '/«PKGBUILDDIR»/doc' make[2]: *** [all-recursive] Error 1 Makefile:2118: recipe for target 'all-recursive' failed make[2]: Leaving directory '/«PKGBUILDDIR»' make[1]: *** [all] Error 2 Makefile:1983: recipe for target 'all' failed make[1]: Leaving directory '/«PKGBUILDDIR»' dh_auto_build: make -j6 returned exit code 2 make: *** [build-arch] Error 2 debian/rules:47: recipe for target 'build-arch' failed ---End Message--- ---BeginMessage--- Source: octave Source-Version: 4.0.0-2 We believe that the bug you reported is fixed in the latest version of octave, 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. Sébastien Villemot sebast...@debian.org (supplier of updated octave 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: Sat, 18 Jul 2015 14:20:22 +0200 Source: octave Binary: octave octave-dbg octave-common octave-doc octave-htmldoc octave-info liboctave3 liboctave-dev Architecture: source amd64 all Version: 4.0.0-2 Distribution: unstable Urgency: low Maintainer: Debian Octave Group pkg-octave-de...@lists.alioth.debian.org Changed-By: Sébastien Villemot sebast...@debian.org Description: liboctave-dev - Development files for the GNU Octave language liboctave3 - Shared libraries of the GNU Octave language octave - GNU Octave language for numerical computations octave-common - architecture-independent files for octave octave-dbg - Debug symbols for octave octave-doc - PDF documentation on the GNU Octave language octave-htmldoc - HTML documentation on the GNU Octave language octave-info - GNU Info documentation on the GNU Octave language Closes: 790533 Changes: octave (4.0.0-2) unstable; urgency=low . * Upload to unstable. * Fix FTBFS with texinfo 6. - Add texlive-fonts-recommended to build-depends (needed for texinfo 6) - Add debian/patches/dont-use-included-texinfo-texmfcnf.patch and xbackslash-texinfo.patch (Patches thanks to Norbert Preining and Mike Miller) (Closes: #790533) * Replace the long list of Breaks with a single Breaks against liboctave2. This should work now that #671711 is fixed in Jessie and later. Checksums-Sha1: 73b688336e84be78cddb3f4c6d24a52f7ebbd62c 3117 octave_4.0.0-2.dsc a9854ca377bc0b8ca9355648b75448b42321409a 133220 octave_4.0.0-2.debian.tar.xz 2a9b79d36314ba202bca53c9ee623cd2c947c1ea 1447768 octave-common_4.0.0-2_all.deb 0571fc61ff44f7baec3cfafc1a683327f342289f 4124956 octave-doc_4.0.0-2_all.deb 578357c6ee81d9f215f74b28dd5ce8d59600abe0 1847010 octave-htmldoc_4.0.0-2_all.deb f06013da854314403bf24cb6a92f5d2c636320be 1141654 octave-info_4.0.0-2_all.deb Checksums-Sha256: 43584eb3ac2da70db0c0846ca4ba4491305a3e8772bc1deed8e9d1810e6c6b6d 3117 octave_4.0.0-2.dsc
Bug#790626: marked as done (octave: FTBFS with GNU Texinfo 6: Argument of \\ has an extra })
Your message dated Sat, 18 Jul 2015 12:49:28 +
with message-id e1zgryw-0004h4...@franck.debian.org
and subject line Bug#790533: fixed in octave 4.0.0-2
has caused the Debian Bug report #790533,
regarding octave: FTBFS with GNU Texinfo 6: Argument of \\ has an extra }
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.)
--
790533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790533
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: octave
Version: 3.8.2-4
Severity: serious
fails to build in unstable, probably due to the octave new texlive.
sbuild (Debian sbuild) 0.65.2 (24 Mar 2015) on bl460gen8-30.hlinux.usa.hp.com
...
(/«PKGBUILDDIR»/doc/interpreter/gpl.texi Appendix J [856]
[857] [858] [859] [860] [861] [862] [863] [864] [865] [866])
(/«PKGBUILDDIR»/doc/interpreter/cp-idx.texi (Concept Index)
[867] [868] (./octave.cps
./octave.cps:56: Argument of \\ has an extra }.
inserted text
\par
to be read again
}
\initial ... .5\baselineskip \leftline {\secbf #1}
\nobreak \vskip
.33\baseli...
l.56 \initial {\\}
?
./octave.cps:56: Emergency stop.
inserted text
\par
to be read again
}
\initial ... .5\baselineskip \leftline {\secbf #1}
\nobreak \vskip
.33\baseli...
l.56 \initial {\\}
Output written on octave.dvi (882 pages, 2774212 bytes).
Transcript written on octave.log.
/usr/bin/texi2dvi: etex exited with bad status, quitting.
make[4]: *** [octave.dvi] Error 1
Makefile:2118: recipe for target 'octave.dvi' failed
--
Martin Michlmayr
Linux for HP Helion OpenStack, Hewlett-Packard
---End Message---
---BeginMessage---
Source: octave
Source-Version: 4.0.0-2
We believe that the bug you reported is fixed in the latest version of
octave, 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.
Sébastien Villemot sebast...@debian.org (supplier of updated octave 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: Sat, 18 Jul 2015 14:20:22 +0200
Source: octave
Binary: octave octave-dbg octave-common octave-doc octave-htmldoc octave-info
liboctave3 liboctave-dev
Architecture: source amd64 all
Version: 4.0.0-2
Distribution: unstable
Urgency: low
Maintainer: Debian Octave Group pkg-octave-de...@lists.alioth.debian.org
Changed-By: Sébastien Villemot sebast...@debian.org
Description:
liboctave-dev - Development files for the GNU Octave language
liboctave3 - Shared libraries of the GNU Octave language
octave - GNU Octave language for numerical computations
octave-common - architecture-independent files for octave
octave-dbg - Debug symbols for octave
octave-doc - PDF documentation on the GNU Octave language
octave-htmldoc - HTML documentation on the GNU Octave language
octave-info - GNU Info documentation on the GNU Octave language
Closes: 790533
Changes:
octave (4.0.0-2) unstable; urgency=low
.
* Upload to unstable.
* Fix FTBFS with texinfo 6.
- Add texlive-fonts-recommended to build-depends (needed for texinfo 6)
- Add debian/patches/dont-use-included-texinfo-texmfcnf.patch and
xbackslash-texinfo.patch (Patches thanks to Norbert Preining and
Mike Miller) (Closes: #790533)
* Replace the long list of Breaks with a single Breaks against liboctave2.
This should work now that #671711 is fixed in Jessie and later.
Checksums-Sha1:
73b688336e84be78cddb3f4c6d24a52f7ebbd62c 3117 octave_4.0.0-2.dsc
a9854ca377bc0b8ca9355648b75448b42321409a 133220 octave_4.0.0-2.debian.tar.xz
2a9b79d36314ba202bca53c9ee623cd2c947c1ea 1447768 octave-common_4.0.0-2_all.deb
0571fc61ff44f7baec3cfafc1a683327f342289f 4124956 octave-doc_4.0.0-2_all.deb
578357c6ee81d9f215f74b28dd5ce8d59600abe0 1847010 octave-htmldoc_4.0.0-2_all.deb
f06013da854314403bf24cb6a92f5d2c636320be 1141654 octave-info_4.0.0-2_all.deb
Checksums-Sha256:
43584eb3ac2da70db0c0846ca4ba4491305a3e8772bc1deed8e9d1810e6c6b6d 3117
Processed: user-mode-linux: diff for NMU version 4.0-1um-0.1
Processing control commands: tags -1 + patch pending Bug #787979 [src:user-mode-linux] user-mode-linux: FTBFS: build-dependency not installable: linux-source-3.16 Added tag(s) patch and pending. -- 787979: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787979 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: asmon: diff for NMU version 0.71-5.1
Processing control commands: tags 80 + pending Bug #80 [src:asmon] asmon: ftbfs with GCC-5 Added tag(s) pending. -- 80: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=80 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#788533: mapnik: FTBFS: virtual memory exhausted: Cannot allocate memory (Was: Bug#756867: transition: gdal)
Processing commands for cont...@bugs.debian.org: fixed 788533 mapnik/3.0.0+ds-2 Bug #788533 [src:mapnik] mapnik: FTBFS: virtual memory exhausted: Cannot allocate memory Marked as fixed in versions mapnik/3.0.0+ds-2. thanks Stopping processing here. Please contact me if you need assistance. -- 788533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788533 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#788533: marked as done (mapnik: FTBFS: virtual memory exhausted: Cannot allocate memory)
Your message dated Sat, 18 Jul 2015 17:34:39 +0200 with message-id 55aa720f.7070...@xs4all.nl and subject line Re: Bug#788533: mapnik: FTBFS: virtual memory exhausted: Cannot allocate memory (Was: Bug#756867: transition: gdal) has caused the Debian Bug report #788533, regarding mapnik: FTBFS: virtual memory exhausted: Cannot allocate memory 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.) -- 788533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: mapnik Version: 3.0.0~rc3+ds-1 Severity: serious Hi, Your package is failing to build on mips and mipsel (release architectures) and kfreebsd-i386: https://buildd.debian.org/status/logs.php?pkg=mapnikver=3.0.0~rc3%2Bds-1 This seems related to #742149. Cheers, Emilio ---End Message--- ---BeginMessage--- fixed 788533 mapnik/3.0.0+ds-2 thanks With the exclusion of mips* this issue should be fixed too. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1---End Message---
Bug#792766: marked as done (python3-phply: ships /usr/lib/python3/dist-packages/tests/__init__.py)
Your message dated Sat, 18 Jul 2015 11:03:56 + with message-id e1zgpuo-kp...@franck.debian.org and subject line Bug#792766: fixed in python-phply 0.9.1-2 has caused the Debian Bug report #792766, regarding python3-phply: ships /usr/lib/python3/dist-packages/tests/__init__.py 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.) -- 792766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792766 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python3-phply Version: 0.9.1-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite /usr/lib/python3/dist-packages/tests/__init__.py is a very generic name that is prone to file overrides conflicts between packages (which caused its detection). Andreas ---End Message--- ---BeginMessage--- Source: python-phply Source-Version: 0.9.1-2 We believe that the bug you reported is fixed in the latest version of python-phply, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 792...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna costamagnagianfra...@yahoo.it (supplier of updated python-phply 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: Sat, 18 Jul 2015 12:46:59 +0200 Source: python-phply Binary: python-phply python3-phply Architecture: source all Version: 0.9.1-2 Distribution: unstable Urgency: low Maintainer: Gianfranco Costamagna costamagnagianfra...@yahoo.it Changed-By: Gianfranco Costamagna costamagnagianfra...@yahoo.it Description: python-phply - PHP parser written in Python using PLY python3-phply - PHP parser written in Python 3 using PLY Closes: 792766 Changes: python-phply (0.9.1-2) unstable; urgency=low . * python3-phply.pyremove, exclude tests from install. (Closes: #792766) thanks Andreas Beckmann for the bug report. Checksums-Sha1: 6adfd0a464a6f2d8f1f9c39ea483faf1ad5076bc 2067 python-phply_0.9.1-2.dsc d487ab732ec02b425ef93f635f8afdb59a2d13b5 30640 python-phply_0.9.1.orig.tar.gz b9e975cf250ce81e3b3aad6b48c4d0887651b2d4 4448 python-phply_0.9.1-2.debian.tar.xz e2b9bfcd33d94e3365f7d1c1e8ef9d7d19130e2e 18694 python-phply_0.9.1-2_all.deb cb7c40a7621b0de895180d8bd7d5bebbaa593838 17924 python3-phply_0.9.1-2_all.deb Checksums-Sha256: 9603ce54e76fe7027d777e207bca6aeab0f9bbaf7529ab099c0f8921530e1925 2067 python-phply_0.9.1-2.dsc 6afe997a3b0ab3dbc2d5d8769d9c9e10d1fd9812e416d2deaf6ba56fd2565ed8 30640 python-phply_0.9.1.orig.tar.gz 99d70119567adfc351ec074e90a8865451e9f87f46687e15107a57b49eac0e2b 4448 python-phply_0.9.1-2.debian.tar.xz 21d21ec9623249348f095c14095a5d21db9a64afc9dd1ea97948050ca1391d72 18694 python-phply_0.9.1-2_all.deb a302afd5732af3415d833230004f57394866f95f84bc4fc9ecc9b349367cc41c 17924 python3-phply_0.9.1-2_all.deb Files: 2e4a596ae1009df0038654c718ac740f 2067 python optional python-phply_0.9.1-2.dsc f336ab9d35bd9c0f0a50ede3252b12ba 30640 python optional python-phply_0.9.1.orig.tar.gz 9ec02f051dcc3de2dbe64f45a21f4e60 4448 python optional python-phply_0.9.1-2.debian.tar.xz de2935afffd8b5610445ee2afbcfc69a 18694 python optional python-phply_0.9.1-2_all.deb 98aafbd94d8464e08ce3d98a3229ae07 17924 python optional python3-phply_0.9.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVqi/OAAoJEPNPCXROn13ZFNYP/1aAe4xFZH3pPrxcgPLgjXnI fLWKP2hP9FKlVMldHfYctYMwGk6Vf0TTYcFIrfuCl1xkG5l0DqPTWjJJ8t+UGROp gN+O6bLA+GVURPZy6OA6Wnfodejq0eKUeje127uyvc+X31/51mYGu0/Tn/TZc53u aVayOm/Ypoy42B3stdyhz6Fa/nu+X17MflvehFXrwPq0wt15KLA8ORW9RQOGRZN+ +Y39pylSX98cJVKu7Z+02JCMkYLtwdOjzF/5YPMhTFUOe9ozuvard3Ve/rBOxthW EilZ8xjEQJDZ7u0Bu02UtAC/772mNznHZzhFQqO0u69cqn0YqRBiIEk4cj2MlJHo bieanrZgWxgDoElQaVN+wsB16SnuXEPaDDKsdjlMi5e75h1ETnV8fhXV3NQ2GySB GPxyCdKEQdeMYwcdwYxwhAeutT5nAzB/fsUY1p6tBOa/Qtv1iUBVGz2sZj1zTRvU k3A6iEYvq8hOT8MN95vS06D0PUCx0A/AUTK86O5Ivi/22SxcEk4KpfVnshwhiyn/ ZxJxxtADZJNNr0Br0D6CqoUxdaYjqvZkVvV/qkSP/mJ6liv0xQXmbpZlsxPIhkI9 /y2cTidLQf2ede6OPyzCwyWBYk/D8cl+iF/aNqpJTFrmRB7JWuVlfrLauV0dwT2Y eM5ajoS+61REKNgoK6Dl =Fcr7 -END PGP SIGNATUREEnd Message---
Bug#792767: python3-zipstream: ships /usr/lib/python3/dist-packages/tests/__init__.py
On Sat, Jul 18, 2015 at 1:54 PM Andreas Beckmann a...@debian.org wrote: Package: python3-zipstream Version: 1.1.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite /usr/lib/python3/dist-packages/tests/__init__.py is a very generic name that is prone to file overwrite conflicts between packages (which caused its detection). Thanks! An upload fixing this is pending.
Bug#783920: atlas: FTBFS on arm64 in Jessie
Control: severity -1 important Dear Martin and Edmund, Le mercredi 01 juillet 2015 à 21:36 -0400, Martin Michlmayr a écrit : * Sébastien Villemot sebast...@debian.org [2015-05-01 12:39]: make[3]: Entering directory '/«PKGBUILDDIR»/build/atlas-base/lib' mkdir tmp cd tmp \ ar x ../libatlas.a \ if test -f ../libptf77blas.a -a -f ../libptcblas.a; then \ ar x ../libptf77blas.a \ ar x ../libptcblas.a; \ else \ ar x ../libf77blas.a \ ar x ../libcblas.a; \ fi ar: ../libf77blas.a: No such file or directory (It did build, clearly, on 2015-01-29 on arm-linaro-01. What might have changed since then?) ATLAS is a very delicate beast so anything is possible. Can you please provide me with the full build log? On which machine did you try the compilation? I just ran into the same issue. Note that earlier on I saw such errors: /«PKGBUILDDIR»/build/atlas-base/../..//CONFIG/src/backend/cpuid.S: Assembler messages: /«PKGBUILDDIR»/build/atlas-base/../..//CONFIG/src/backend/cpuid.S:32: Error: unknown mnemonic `subl' -- `subl $8,%esp' /«PKGBUILDDIR»/build/atlas-base/../..//CONFIG/src/backend/cpuid.S:33: Error: unknown mnemonic `movl' -- `movl %ebx,(%esp)' Thanks for your feedback. Unfortunately, I am unable to reproduce your problem. The package builds fine on the only arm64 machine to which I have access (asachi.debian.org). As a consequence, I am downgrading the severity to important, since it does not affect all arm64 machines. Nevertheless, there is obviously something wrong. Note that the assembly messages that Martin got are a red herring. In order to try to debug this: could one of you try to recompile the package after removing the file debian/archdefs/arm64/GENERIC64.tar.bz2? The compilation will take much longer, but I would be interested in seeing if it succeeds. If it does, could you then do the following after the end of the compilation: cd build/atlas-base/ARCHS make ArchNew tar caf GENERIC64.tar.bz2 GENERIC64 And send me the GENERIC64.tar.bz2 along with the full build log? Best, -- .''`.Sébastien Villemot : :' :Debian Developer `. `' http://sebastien.villemot.name `- GPG Key: 4096R/381A7594 signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#783920: atlas: FTBFS on arm64 in Jessie
Processing control commands: severity -1 important Bug #783920 [src:atlas] atlas: FTBFS on arm64 in Jessie Severity set to 'important' from 'serious' -- 783920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783920 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#792780: mariadb-10.0: FTBFS on powerpc but succeded previously
Source: mariadb-10.0 Version: 10.0.20-1 Severity: serious Justification: FTBFS on powerpc but succeeded for previous versions Hi mariadb-10.0 succeeded previously on powerpc but FTBFS fo 10.0.20. See: https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.0arch=powerpcver=10.0.20-2stamp=1436318764 Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786943: aapt: error while loading shared libraries: libhost.so: cannot open shared object file: No such file or directory
Followup-For: Bug #786943 Something weird happened on the buildd build of android-platform-frameworks-base/i386: * /usr/bin/aapt wants libhost.so instead of libhost.so.0 * the aapt package has no dependency on android-libhost I cannot reproduce this weird build result in neither sid nor jessie, so binNMUs for jessie and sid are sufficient to fix this = #792779. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#451535: Still reproduces in 2015
This bug still reproduces in Jessie. Any plans to fix it?
Bug#791514: [pkg-go] Bug#791514: golang-mreiferson-httpclient: FTBFS without internet access: attempts to connect to a service on the internet during tests
Instead of trying to fix this, I think it’s better to let the autoremoval remove this package from Debian. The functionality which the package provides is by now part of the standard library (HTTP request timeouts), and there are no dependencies on the package currently. On Sun, Jul 5, 2015 at 5:33 PM, Chris West (Faux) solo-debianb...@goeswhere.com wrote: Source: golang-mreiferson-httpclient Version: 0.0~git20140425-2 Severity: serious Tags: sid stretch Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package's tests fail when run on a pbuilder without networking, it attempts to make a request to a website on the internet: === RUN TestHttpsConnection --- FAIL: TestHttpsConnection (0.00s) httpclient_test.go:93: 1st request failed - Get https://httpbin.org/ip: dial tcp: lookup httpbin.org: no such host Packages are required to build without a network connection. Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/golang-mreiferson-httpclient.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) ___ Pkg-go-maintainers mailing list pkg-go-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers -- Best regards, Michael
Bug#792788: jruby: FTBFS Cannot find parent dependency org.jruby:jruby-artifacts:pom:1.7.21
Source: jruby Version: 1.7.21-1 Severity: serious Hi, jruby FTBFS in a clean sid cowbuilder environment. debian/rules override_dh_auto_configure make[1]: Entering directory '/tmp/buildd/jruby-1.7.21' /usr/share/maven-debian-helper/copy-repo.sh /tmp/buildd/jruby-1.7.21/debian mh_patchpoms -pjruby --debian-build --keep-pom-version \ --maven-repo=/tmp/buildd/jruby-1.7.21/debian/maven-repo --build-no-docs [ERROR] Cannot find parent dependency org.jruby:jruby-artifacts:pom:1.7.21, use --no-parent option to resolve this issue or install the parent POM in the Maven repository [ERROR] Cannot find parent dependency org.jruby:jruby-ext:pom:1.7.21, use --no-parent option to resolve this issue or install the parent POM in the Maven repository [ERROR] Cannot find parent dependency org.jruby:jruby-artifacts:pom:1.7.21, use --no-parent option to resolve this issue or install the parent POM in the Maven repository Markus -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: unable to detect -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 778157 is forwarded to http://sourceforge.net/p/user-mode-linux/mailman/message/34139609/
Processing commands for cont...@bugs.debian.org: forwarded 778157 http://sourceforge.net/p/user-mode-linux/mailman/message/34139609/ Bug #778157 [src:user-mode-linux] user-mode-linux: ftbfs with GCC-5 Set Bug forwarded-to-address to 'http://sourceforge.net/p/user-mode-linux/mailman/message/34139609/'. thanks Stopping processing here. Please contact me if you need assistance. -- 778157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778157 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#792773: meta-kde: kde-full and kde-plasma-desktop are uninstallable
Source: meta-kde Version: 5:85 Severity: grave Justification: renders package unusable Hi, kde-plasma-desktop is currently uninstallable because it depends on plasma-desktop and kde-workspace which then in turn depends on kde-workspace-bin. But plasma-desktop conflicts with kde-workspace-bin and thus kde-plasma-desktop cannot be installed. As a result, kde-full cannot be installed either. Here is an overview of the situation on qa.debian.org/dose: https://qa.debian.org/dose/debcheck/unstable_main/1437109207/packages/kde-full.html Thanks! cheers, josch -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: [pkg-octave/master] Fix FTBFS with texinfo 6.
Processing commands for cont...@bugs.debian.org:
tag 790533 pending
Bug #790533 {Done: Scott Kitterman sc...@kitterman.com} [src:octave] octave:
FTBFS on multiple archs during binNMU for qscintilla2 transition
Bug #790626 {Done: Scott Kitterman sc...@kitterman.com} [src:octave] octave:
FTBFS with GNU Texinfo 6: Argument of \\ has an extra }
Added tag(s) pending.
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
790533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790533
790626: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790626
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#790533: [pkg-octave/master] Fix FTBFS with texinfo 6.
tag 790533 pending thanks Date: Sat Jul 18 13:57:27 2015 +0200 Author: Sébastien Villemot sebast...@debian.org Commit ID: 78b0ec431a6e390649a2e394037d3243272c12e7 Commit URL: http://anonscm.debian.org/gitweb/?p=pkg-octave/octave.git;a=commitdiff;h=78b0ec431a6e390649a2e394037d3243272c12e7 Patch URL: http://anonscm.debian.org/gitweb/?p=pkg-octave/octave.git;a=commitdiff_plain;h=78b0ec431a6e390649a2e394037d3243272c12e7 Fix FTBFS with texinfo 6. - Add texlive-fonts-recommended to build-depends (needed for texinfo 6) - Add debian/patches/dont-use-included-texinfo-texmfcnf.patch and xbackslash-texinfo.patch (Patches thanks to Norbert Preining and Mike Miller) Closes: #790533 Git-Dch: Full -- 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#790291: kamailio-dnssec-modules: Module fails to load.
Processing commands for cont...@bugs.debian.org: forwarded 790291 https://github.com/kamailio/kamailio/pull/254 Bug #790291 [kamailio-dnssec-modules] kamailio-dnssec-modules: Module fails to load. Set Bug forwarded-to-address to 'https://github.com/kamailio/kamailio/pull/254'. thanks Stopping processing here. Please contact me if you need assistance. -- 790291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790291 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#777783: atftp: diff for NMU version 0.7.git20120829-2.1
Control: tags 83 + pending Dear maintainer, I've prepared an NMU for atftp (versioned as 0.7.git20120829-2.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Wir sind Helden: Lass uns verschwinden diff -u atftp-0.7.git20120829/debian/changelog atftp-0.7.git20120829/debian/changelog --- atftp-0.7.git20120829/debian/changelog +++ atftp-0.7.git20120829/debian/changelog @@ -1,3 +1,12 @@ +atftp (0.7.git20120829-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix ftbfs with GCC-5: apply patch from Martin Michlmayr to debian/rules: +use GNU89 inline style, and adjust buildflags handling. +(Closes: #83) + + -- gregor herrmann gre...@debian.org Sat, 18 Jul 2015 17:09:34 +0200 + atftp (0.7.git20120829-2) unstable; urgency=low * atftpd.postinst uses invalid protocol bug fixed. Closes: #688693 diff -u atftp-0.7.git20120829/debian/rules atftp-0.7.git20120829/debian/rules --- atftp-0.7.git20120829/debian/rules +++ atftp-0.7.git20120829/debian/rules @@ -12,10 +12,8 @@ # This has to be exported to make some magic below work. export DH_OPTIONS -export DEB_BUILD_MAINT_OPTIONS = hardening=+all -export DEB_CFLAGS_MAINT_APPEND = -Wall -pedantic -export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed - +dpkg_buildflags = DEB_BUILD_MAINT_OPTIONS=hardening=+all DEB_CFLAGS_MAINT_APPEND=-Wall -pedantic -std=gnu89 DEB_LDFLAGS_MAINT_APPEND=-Wl,--as-needed dpkg-buildflags + configure: configure-stamp configure-stamp: @@ -23,7 +21,7 @@ # Add here commands to configure the package. ./autogen.sh #./configure --prefix=/usr --mandir=/usr/share/man - dh_auto_configure -- $(shell dpkg-buildflags --export=configure) + dh_auto_configure -- $(shell $(dpkg_buildflags) --export=configure) touch configure-stamp signature.asc Description: Digital Signature
Processed: atftp: diff for NMU version 0.7.git20120829-2.1
Processing control commands: tags 83 + pending Bug #83 [src:atftp] atftp: ftbfs with GCC-5 Added tag(s) pending. -- 83: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=83 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#792767: marked as done (python3-zipstream: ships /usr/lib/python3/dist-packages/tests/__init__.py)
Your message dated Sat, 18 Jul 2015 13:20:38 + with message-id e1zgs2g-0001ah...@franck.debian.org and subject line Bug#792767: fixed in python-zipstream 1.1.0-2 has caused the Debian Bug report #792767, regarding python3-zipstream: ships /usr/lib/python3/dist-packages/tests/__init__.py 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.) -- 792767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python3-zipstream Version: 1.1.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite /usr/lib/python3/dist-packages/tests/__init__.py is a very generic name that is prone to file overwrite conflicts between packages (which caused its detection). Andreas ---End Message--- ---BeginMessage--- Source: python-zipstream Source-Version: 1.1.0-2 We believe that the bug you reported is fixed in the latest version of python-zipstream, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 792...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aigars Mahinovs aigar...@debian.org (supplier of updated python-zipstream 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: Sat, 18 Jul 2015 16:06:56 +0300 Source: python-zipstream Binary: python-zipstream python3-zipstream Architecture: source all Version: 1.1.0-2 Distribution: unstable Urgency: low Maintainer: Aigars Mahinovs aigar...@debian.org Changed-By: Aigars Mahinovs aigar...@debian.org Description: python-zipstream - Zipfile generator python3-zipstream - Zipfile generator Closes: 792767 Changes: python-zipstream (1.1.0-2) unstable; urgency=low . * Exlude tests from the installation (Closes: #792767) Checksums-Sha1: f5fcf3c01b7a85ad23a267d102a871061678c3e4 1915 python-zipstream_1.1.0-2.dsc 7cb95c681409410022131042cd3a4d1c0051563e 2200 python-zipstream_1.1.0-2.debian.tar.xz 70fb59b5f1be0fcd0f64d84f87c5926ce1f6d7c1 6890 python-zipstream_1.1.0-2_all.deb 1386f637ff11af23eb71be5934408e8465983e16 6988 python3-zipstream_1.1.0-2_all.deb Checksums-Sha256: 438fb3e1fa76493c34534ee8a5863d4d47444aa7a2f81202ecdd5d9a434d83da 1915 python-zipstream_1.1.0-2.dsc 694186b0625d58386dfe9d25677d68d2ac3e2215e1277e7184af7a15108804c4 2200 python-zipstream_1.1.0-2.debian.tar.xz 3664976f042fa8438b1a3b57aa84178a5b74755f5e802ea212493fadfdb77ff6 6890 python-zipstream_1.1.0-2_all.deb f1adcbc87062cbc98c829ca323bfa7af3587697585cf7aeb3e09be992456d2b4 6988 python3-zipstream_1.1.0-2_all.deb Files: 913ad8784ce74569775345f9cfd08524 1915 python optional python-zipstream_1.1.0-2.dsc 3c638b9c808e64447a5d0a65ebb2e057 2200 python optional python-zipstream_1.1.0-2.debian.tar.xz 731ad6ffa2ec84b393c1adfda8474cff 6890 python optional python-zipstream_1.1.0-2_all.deb d991c12f86d9c12ba3a147ba018e6eca 6988 python optional python3-zipstream_1.1.0-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVqlEnAAoJEPpkO6YdInr73M4QAKSp2tVCnWYEa0TEfC5U8gVb Tn7htXbR1d2Zbak0q2qcwewaqhQ5VbH9PMF1A0x8YhEMgnK4mRci1MyUURX6VuMK qSYTz4WNyWBbNjWgjD/WXO1BzQcx659Po5PbzZJedYH6G4kgcw+R6fJzNVz8a7i7 H2yc83nHI6qAY0Sk1o87Pwz1CvXKueYWLv7XblGp+XMTJGJ2dULkeLBF1moHZ7G4 AMyZaAdXjODJaWMxyVIP11mopFrpRqjwAaU1e4CALy7BM7bMdq++MNGgblghJH7p aNsiKfpt1yATdfPga+eIH+IfBwrR2ogbBcLllE3b/6i1SLymTvhykE+BczVsSiQs D77c2jQlVw9YdvcTR3mKK1IPccjXPF1snM6fEr1mJpfPLGYnpuigr1HzEOqMG0mr TaAAKpXUHzWfUGAHVQJRt5WC6o79h2O2MqUtO6jT2iM9MXbqMvxWrt5Dk4PGEqlk I1Sf2oN6po9bw3o68lIX6apF5toWNfEx7Lr9UxDjDTy0fkKk5KpbgVRP6obw/dT2 YX+KY+HcR3J86UxkubN7XbNwsiLvBRGtRDGj/2WDEXWuONaJHFmYVpWqPze4g7AV 56RCK36e5mp6+slWgQ8xy3ZqY5ngGSxPKQvy85H0xWiKubBDMqzb56xksYh7x+N4 +z61jVGTaEiyB8sYVkMX =+HAW -END PGP SIGNATUREEnd Message---
Bug#777780: asmon: diff for NMU version 0.71-5.1
Control: tags 80 + pending Dear maintainer, I've prepared an NMU for asmon (versioned as 0.71-5.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Ludwig Hirsch: Asta diff -u asmon-0.71/debian/changelog asmon-0.71/debian/changelog --- asmon-0.71/debian/changelog +++ asmon-0.71/debian/changelog @@ -1,3 +1,12 @@ +asmon (0.71-5.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix ftbfs with GCC-5: +apply patch from Martin Michlmayr to use GNU89 inline semantics. +(Closes: #80) + + -- gregor herrmann gre...@debian.org Sat, 18 Jul 2015 17:00:10 +0200 + asmon (0.71-5) unstable; urgency=low * Update for recent kernels, (Closes: #639528). Thanks Andrew Deason. diff -u asmon-0.71/asmon/Makefile asmon-0.71/asmon/Makefile --- asmon-0.71/asmon/Makefile +++ asmon-0.71/asmon/Makefile @@ -12,7 +12,7 @@ ../wmgeneral/list.o .c.o: - gcc -c -Wall $(SOLARIS) $ -o $*.o + gcc -c -std=gnu89 -Wall $(SOLARIS) $ -o $*.o asmon: $(OBJS) gcc -o asmon $(OBJS) $(LIBDIR) $(LIBS) signature.asc Description: Digital Signature
Bug#790453: marked as done (FTBFS in unstable due to build-depends on libmysqlclient15-dev)
Your message dated Sat, 18 Jul 2015 15:38:34 +
with message-id e1zguca-0003yj...@franck.debian.org
and subject line Bug#790453: fixed in libnss-mysql-bg 1.5-4
has caused the Debian Bug report #790453,
regarding FTBFS in unstable due to build-depends on libmysqlclient15-dev
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.)
--
790453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libnss-mysql-bg
Version: 1.5-3
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient15-dev
This package fails to build in unstable because the build-dependency on
libmysqlclient15-dev cannot be met. libmysqlclient15-dev used to be
provided by mysql-5.5, but this is no longer the case in version 5.6
(see #790257).
Please update your Build-Depends to libmysqlclient-dev
--
Martin Michlmayr
Linux for HP Helion OpenStack, Hewlett-Packard
---End Message---
---BeginMessage---
Source: libnss-mysql-bg
Source-Version: 1.5-4
We believe that the bug you reported is fixed in the latest version of
libnss-mysql-bg, 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.
Andreas Beckmann a...@debian.org (supplier of updated libnss-mysql-bg 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: Sat, 18 Jul 2015 16:27:05 +0200
Source: libnss-mysql-bg
Binary: libnss-mysql-bg
Architecture: source
Version: 1.5-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group packa...@qa.debian.org
Changed-By: Andreas Beckmann a...@debian.org
Description:
libnss-mysql-bg - NSS module for using MySQL as a naming service
Closes: 790453
Changes:
libnss-mysql-bg (1.5-4) unstable; urgency=medium
.
[ Andreas Beckmann ]
* QA upload.
* Set Maintainer to Debian QA Group. (See: #731759)
* d/control: Use ${misc:Pre-Depends} instead of hardcoding
multiarch-support.
.
[ Hideki Yamane ]
* debian/control
- s/libmysqlclient15-dev/libmysqlclient-dev/ to fix FTBFS (Closes: #790453)
Checksums-Sha1:
467d1f9a1d7974cf8693e56d9ce80c39f1656d88 1771 libnss-mysql-bg_1.5-4.dsc
5cd061f1703b1760eef154b385f4b3ffacc8139a 4852
libnss-mysql-bg_1.5-4.debian.tar.xz
Checksums-Sha256:
8dc3de7864ccc007d443a53d1b0fcdbfe612cf31703bd8d57190ea0a604a3ccb 1771
libnss-mysql-bg_1.5-4.dsc
95737d6536280d85a85a85aad10928e0bb0c261666c05273a6b4757ded99d9f8 4852
libnss-mysql-bg_1.5-4.debian.tar.xz
Files:
0c7f5e535a8923c912b0554a45cb83aa 1771 admin optional libnss-mysql-bg_1.5-4.dsc
80f5637840b07283778dc31f3cd22933 4852 admin optional
libnss-mysql-bg_1.5-4.debian.tar.xz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBCAAGBQJVqmNoAAoJEF+zP5NZ6e0IJCsP/13N+Epc6OY0TDf2VIR7IEEC
h2sPxdzYeRbQVP1KxQ32FevzUTbMhdb7IFVsdaV5Ya4cE1iKDWbdcovxVlUZF6h5
0/oumLHEo1xYt9dHO15QACQII+7HOVE7cBOQl7YfklHDjTL/OOhwVmV9HOPqc/B5
Yqjg4NkumiFHis8ELPhc78y1d+O+ilcXCBEqJBTWByCbMcUBxO3YTpvWphRrpIJK
Aie7qAmOVs2k80XuyaNfyfaqQeixlWXCJvJx39x63Fs1MX38yzDeumPOpUEesR+8
lkA4m8flYk8CSAgd3BkWJ70Mb0Be88v0pW2AiifRA44DeuIUIAtP/Hft+3Q/vTRM
Gk89GwrAyZ43gZ3Zfp2sCbdXip6YpHQmv0/6+avF+vZXFIsd6a29Q6YYgqKbSQCz
BJrU7GCdSQp/vhoWNLu0zQ3pnIBJ0FaB4WGWYqq5R+0KTcxGDLY9CNFWhbviQ8Uo
e9iyYf3ygA1Ew5LQFZIervUE5GWInFgBXLGoy2JxMo43SxBfSg6yd46DWosXeD5u
2ql33GCsmGmGZxeaysWKMab+vQNDTzAFR8fYZQGtfW6WaUlQACUCF0ecEtUXTX0y
mBEbYq+feIChT++J895AGmqQWWuw8+eRDr4W61pGW+WJX0FGRhyXTeojI2SizQwD
L1lwu6SiAZZhYXDpM5ko
=NGWv
-END PGP SIGNATUREEnd Message---
Processed: deborphan: diff for NMU version 1.7.28.8-0.2
Processing control commands: tags 777831 + pending Bug #777831 [src:deborphan] deborphan: ftbfs with GCC-5 Added tag(s) pending. -- 777831: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777831: deborphan: diff for NMU version 1.7.28.8-0.2
Control: tags 777831 + pending Dear maintainer, I've prepared an NMU for deborphan (versioned as 1.7.28.8-0.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Ry Cooder: Do Re Mi diff -Nru deborphan-1.7.28.8/debian/changelog deborphan-1.7.28.8/debian/changelog --- deborphan-1.7.28.8/debian/changelog 2014-09-08 13:41:20.0 +0200 +++ deborphan-1.7.28.8/debian/changelog 2015-07-18 18:18:59.0 +0200 @@ -1,3 +1,12 @@ +deborphan (1.7.28.8-0.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fix ftbfs with GCC-5: apply patch from Jakub Wilk: +changed semantics of inline keyword. +(Closes: #777831) + + -- gregor herrmann gre...@debian.org Sat, 18 Jul 2015 18:18:27 +0200 + deborphan (1.7.28.8-0.1) unstable; urgency=low * Non-maintainer upload with permission. diff -Nru deborphan-1.7.28.8/include/deborphan.h deborphan-1.7.28.8/include/deborphan.h --- deborphan-1.7.28.8/include/deborphan.h 2012-06-30 20:47:50.0 +0200 +++ deborphan-1.7.28.8/include/deborphan.h 2015-07-18 18:18:22.0 +0200 @@ -172,8 +172,8 @@ int string_to_priority(const char *priority); const char *priority_to_string(int priority); char *sstrsep(char **str, int c); -inline void strstripchr(char *s, int c); -inline unsigned int strhash(const char *line); +extern inline void strstripchr(char *s, int c); +extern inline unsigned int strhash(const char *line); /* keep.c */ dep *readkeep(const char *kfile); diff -Nru deborphan-1.7.28.8/include/xalloc.h deborphan-1.7.28.8/include/xalloc.h --- deborphan-1.7.28.8/include/xalloc.h 2012-06-30 20:47:50.0 +0200 +++ deborphan-1.7.28.8/include/xalloc.h 2015-07-18 18:18:22.0 +0200 @@ -7,7 +7,7 @@ Distributed under the terms of the Artistic License. */ -inline void *xcalloc(size_t nmemb, size_t size); -inline void *xmalloc(size_t size); -inline void *xrealloc(void *ptr, size_t size); -inline char *xstrdup(const char *s); +extern inline void *xcalloc(size_t nmemb, size_t size); +extern inline void *xmalloc(size_t size); +extern inline void *xrealloc(void *ptr, size_t size); +extern inline char *xstrdup(const char *s); signature.asc Description: Digital Signature
Bug#777853: flow-tools: diff for NMU version 1:0.68-12.2
Control: tags 777853 + pending
Dear maintainer,
I've prepared an NMU for flow-tools (versioned as 1:0.68-12.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe
`- NP: Aimee Mann: Ghost World
diff -u flow-tools-0.68/debian/changelog flow-tools-0.68/debian/changelog
--- flow-tools-0.68/debian/changelog
+++ flow-tools-0.68/debian/changelog
@@ -1,3 +1,12 @@
+flow-tools (1:0.68-12.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix ftbfs with GCC-5:
+add patch from Alexander Balderson (changed semantics for inline)
+(Closes: #777853)
+
+ -- gregor herrmann gre...@debian.org Sat, 18 Jul 2015 18:41:15 +0200
+
flow-tools (1:0.68-12.1) unstable; urgency=low
* Non-maintainer upload.
diff -u flow-tools-0.68/debian/patches/00list flow-tools-0.68/debian/patches/00list
--- flow-tools-0.68/debian/patches/00list
+++ flow-tools-0.68/debian/patches/00list
@@ -13,0 +14 @@
+15_gcc5
only in patch2:
unchanged:
--- flow-tools-0.68.orig/debian/patches/15_gcc5
+++ flow-tools-0.68/debian/patches/15_gcc5
@@ -0,0 +1,415 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## 15_gcc5 by Alexander Balderson alexander.balder...@hp.com
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: fix build failure with gcc5; changed semantics of inline
+
+@DPATCH@
+diff -urNad '--exclude=CVS' '--exclude=.svn' '--exclude=.git' '--exclude=.arch' '--exclude=.hg' '--exclude=_darcs' '--exclude=.bzr' flow-tools-0.68~/lib/ftfil.c flow-tools-0.68/lib/ftfil.c
+--- flow-tools-0.68~/lib/ftfil.c 2004-01-05 18:55:23.0 +0100
flow-tools-0.68/lib/ftfil.c 2015-07-18 18:38:52.662240928 +0200
+@@ -547,7 +547,7 @@
+ * returns: FT_FIL_MODE_PERMIT
+ * FT_FIL_MODE_DENY
+ */
+-inline int eval_match_src_as(struct ftfil_lookup_as *lookup, char *rec,
++extern inline int eval_match_src_as(struct ftfil_lookup_as *lookup, char *rec,
+ struct fts3rec_offsets *fo)
+ {
+ u_int16 *src_as;
+@@ -574,7 +574,7 @@
+ * returns: FT_FIL_MODE_PERMIT
+ * FT_FIL_MODE_DENY
+ */
+-inline int eval_match_dst_as(struct ftfil_lookup_as *lookup, char *rec,
++extern inline int eval_match_dst_as(struct ftfil_lookup_as *lookup, char *rec,
+ struct fts3rec_offsets *fo)
+ {
+ u_int16 *dst_as;
+@@ -602,7 +602,7 @@
+ * returns: FT_FIL_MODE_PERMIT
+ * FT_FIL_MODE_DENY
+ */
+-inline int eval_match_ip_prot(struct ftfil_lookup_ip_prot *lookup, char *rec,
++extern inline int eval_match_ip_prot(struct ftfil_lookup_ip_prot *lookup, char *rec,
+ struct fts3rec_offsets *fo)
+ {
+ u_int8 *ip_prot;
+@@ -630,7 +630,7 @@
+ * returns: FT_FIL_MODE_PERMIT
+ * FT_FIL_MODE_DENY
+ */
+-inline int eval_match_ip_src_prefix_len(struct ftfil_lookup_ip_prefix_len *lookup,
++extern inline int eval_match_ip_src_prefix_len(struct ftfil_lookup_ip_prefix_len *lookup,
+ char *rec, struct fts3rec_offsets *fo)
+ {
+ u_int8 *src_mask;
+@@ -658,7 +658,7 @@
+ * returns: FT_FIL_MODE_PERMIT
+ * FT_FIL_MODE_DENY
+ */
+-inline int eval_match_ip_dst_prefix_len(struct ftfil_lookup_ip_prefix_len *lookup,
++extern inline int eval_match_ip_dst_prefix_len(struct ftfil_lookup_ip_prefix_len *lookup,
+ char *rec, struct fts3rec_offsets *fo)
+ {
+ u_int8 *dst_mask;
+@@ -686,7 +686,7 @@
+ * returns: FT_FIL_MODE_PERMIT
+ * FT_FIL_MODE_DENY
+ */
+-inline int eval_match_ip_tos(struct ftfil_lookup_ip_tos *lookup,
++extern inline int eval_match_ip_tos(struct ftfil_lookup_ip_tos *lookup,
+ char *rec, struct fts3rec_offsets *fo)
+ {
+ u_int8 tos;
+@@ -714,7 +714,7 @@
+ * returns: FT_FIL_MODE_PERMIT
+ * FT_FIL_MODE_DENY
+ */
+-inline int eval_match_ip_marked_tos(struct ftfil_lookup_ip_tos *lookup,
++extern inline int eval_match_ip_marked_tos(struct ftfil_lookup_ip_tos *lookup,
+ char *rec, struct fts3rec_offsets *fo)
+ {
+ u_int8 marked_tos;
+@@ -743,7 +743,7 @@
+ * returns: FT_FIL_MODE_PERMIT
+ * FT_FIL_MODE_DENY
+ */
+-inline int eval_match_ip_tcp_flags(struct ftfil_lookup_ip_tcp_flags *lookup,
++extern inline int eval_match_ip_tcp_flags(struct ftfil_lookup_ip_tcp_flags *lookup,
+ char *rec, struct fts3rec_offsets *fo)
+ {
+ u_int8 tcp_flags;
+@@ -772,7 +772,7 @@
+ * returns: FT_FIL_MODE_PERMIT
+ * FT_FIL_MODE_DENY
+ */
+-inline int eval_match_ip_src_port(struct ftfil_lookup_ip_port *lookup,
++extern inline int eval_match_ip_src_port(struct ftfil_lookup_ip_port *lookup,
+ char *rec, struct fts3rec_offsets *fo)
+ {
+ u_int16 *src_port;
+@@ -799,7 +799,7 @@
+ * returns: FT_FIL_MODE_PERMIT
+ * FT_FIL_MODE_DENY
+ */
+-inline int eval_match_ip_dst_port(struct ftfil_lookup_ip_port *lookup,
++extern inline int eval_match_ip_dst_port(struct
Processed: flow-tools: diff for NMU version 1:0.68-12.2
Processing control commands: tags 777853 + pending Bug #777853 [src:flow-tools] flow-tools: ftbfs with GCC-5 Added tag(s) pending. -- 777853: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777831: marked as done (deborphan: ftbfs with GCC-5)
Your message dated Sat, 18 Jul 2015 16:49:22 + with message-id e1zgvig-000804...@franck.debian.org and subject line Bug#777831: fixed in deborphan 1.7.28.8-0.2 has caused the Debian Bug report #777831, regarding deborphan: 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.) -- 777831: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:deborphan Version: 1.7.28.8-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/deborphan_1.7.28.8-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 [...] keep.o: In function `readkeep': /«PKGBUILDDIR»/src/keep.c:85: undefined reference to `xmalloc' /«PKGBUILDDIR»/src/keep.c:98: undefined reference to `xstrdup' /«PKGBUILDDIR»/src/keep.c:102: undefined reference to `strstripchr' /«PKGBUILDDIR»/src/keep.c:112: undefined reference to `strhash' /«PKGBUILDDIR»/src/keep.c:117: undefined reference to `xrealloc' keep.o: In function `delkeep': /«PKGBUILDDIR»/src/keep.c:195: undefined reference to `xmalloc' keep.o: In function `hasduplicate': /«PKGBUILDDIR»/src/keep.c:258: undefined reference to `strhash' keep.o: In function `mergekeep': /«PKGBUILDDIR»/src/keep.c:280: undefined reference to `xmalloc' /«PKGBUILDDIR»/src/keep.c:280: undefined reference to `xmalloc' keep.o: In function `listkeep': /«PKGBUILDDIR»/src/keep.c:301: undefined reference to `xmalloc' keep.o: In function `parseargs': /«PKGBUILDDIR»/src/keep.c:330: undefined reference to `xcalloc' /«PKGBUILDDIR»/src/keep.c:344: undefined reference to `xmalloc' /«PKGBUILDDIR»/src/keep.c:345: undefined reference to `strstripchr' /«PKGBUILDDIR»/src/keep.c:346: undefined reference to `strstripchr' /«PKGBUILDDIR»/src/keep.c:347: undefined reference to `strstripchr' /«PKGBUILDDIR»/src/keep.c:352: undefined reference to `xstrdup' /«PKGBUILDDIR»/src/keep.c:342: undefined reference to `xrealloc' /«PKGBUILDDIR»/src/keep.c:336: undefined reference to `xrealloc' keep.o: In function `parseargs_as_dep': /«PKGBUILDDIR»/src/keep.c:374: undefined reference to `xmalloc' /«PKGBUILDDIR»/src/keep.c:388: undefined reference to `strhash' /«PKGBUILDDIR»/src/keep.c:374: undefined reference to `xmalloc' keep.o: In function `mergekeep': /«PKGBUILDDIR»/src/keep.c:280: undefined reference to `xmalloc' file.o: In function `debopen': /«PKGBUILDDIR»/src/file.c:89: undefined reference to `xmalloc' set.o: In function `set_dep': /«PKGBUILDDIR»/src/set.c:21: undefined reference to `xstrdup' /«PKGBUILDDIR»/src/set.c:30: undefined reference to `strhash' set.o: In function `set_provides': /«PKGBUILDDIR»/src/set.c:46: undefined reference to `xrealloc' set.o: In function `set_section': /«PKGBUILDDIR»/src/set.c:58: undefined reference to `xmalloc' /«PKGBUILDDIR»/src/set.c:64: undefined reference to `xstrdup' collect2: error: ld returned 1 exit status make[2]: *** [deborphan] Error 1 Makefile:276: recipe for target 'deborphan' failed make[2]: Leaving directory '/«PKGBUILDDIR»/src' make[1]: *** [all-recursive] Error 1 Makefile:282: recipe for target 'all-recursive' failed make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [build-stamp] Error 2 debian/rules:15: recipe for target 'build-stamp' failed dpkg-buildpackage: error: debian/rules build gave error exit status 2 ---End Message--- ---BeginMessage--- Source: deborphan Source-Version: 1.7.28.8-0.2 We believe that the bug you reported is fixed in the latest version of deborphan,
Bug#777965: Patch for libpam-chroot FTBFS with GCC-5
On Thu, 09 Jul 2015 12:47:21 -0600, Linn Crosetto wrote: Here is a patch to mark the non-standard function identifier __FUNCTION__ with the __extension__ keyword to work around the build failure with GCC-5. Thanks for this patch. Unfortunately there seems to be a problem. After applying it the build (with gcc 5 from experimental) fails with: debian/rules build dh_testdir /usr/bin/make make[1]: Entering directory '/tmp/buildd/libpam-chroot-0.9' gcc -fPIC -O2 -Wall -Werror -pedantic -I. -c -o pam_chroot.o pam_chroot.c pam_chroot.c: In function '_pam_opts_init': pam_chroot.c:71:45: error: ISO C does not support '__FUNCTION__' predefined identifier [-Werror=pedantic] _pam_log(LOG_ERR, %s: NULL opts pointer, __FUNCTION__); ^ pam_chroot.c: In function '_pam_opts_config': pam_chroot.c:94:45: error: ISO C does not support '__FUNCTION__' predefined identifier [-Werror=pedantic] _pam_log(LOG_ERR, %s: NULL opts pointer, __FUNCTION__); ^ pam_chroot.c: In function '_pam_opts_free': pam_chroot.c:165:45: error: ISO C does not support '__FUNCTION__' predefined identifier [-Werror=pedantic] _pam_log(LOG_ERR, %s: NULL opts pointer, __FUNCTION__); ^ pam_chroot.c: In function '_pam_get_groups': pam_chroot.c:264:19: error: ISO C does not support '__FUNCTION__' predefined identifier [-Werror=pedantic] opts-module, __FUNCTION__, strerror(errno)); ^ pam_chroot.c:271:19: error: ISO C does not support '__FUNCTION__' predefined identifier [-Werror=pedantic] opts-module, __FUNCTION__); ^ pam_chroot.c:276:19: error: ISO C does not support '__FUNCTION__' predefined identifier [-Werror=pedantic] opts-module, __FUNCTION__, user); ^ pam_chroot.c:285:19: error: ISO C does not support '__FUNCTION__' predefined identifier [-Werror=pedantic] opts-module, __FUNCTION__, strerror(errno)); ^ pam_chroot.c: In function '_pam_get_chrootdir': pam_chroot.c:536:22: error: ISO C does not support '__FUNCTION__' predefined identifier [-Werror=pedantic] opts-module, __FUNCTION__, strerror(errno)); ^ cc1: all warnings being treated as errors builtin: recipe for target 'pam_chroot.o' failed make[1]: *** [pam_chroot.o] Error 1 make[1]: Leaving directory '/tmp/buildd/libpam-chroot-0.9' debian/rules:16: recipe for target 'build-stamp' failed The build ins unstable with gcc 4.9 succeeds. Maybe removing -pedantic from Makefile would be a way forward? Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Treibhaus: Sergent Garcia signature.asc Description: Digital Signature
Bug#777975: libssh: diff for NMU version 0.6.3-4.1
Control: tags 777975 + pending
Dear maintainer,
I've prepared an NMU for libssh (versioned as 0.6.3-4.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe
`- NP: Wir sind Helden: The Geek (Small Inherit)
diff -Nru libssh-0.6.3/debian/changelog libssh-0.6.3/debian/changelog
--- libssh-0.6.3/debian/changelog 2015-01-27 00:28:06.0 +0100
+++ libssh-0.6.3/debian/changelog 2015-07-18 20:38:50.0 +0200
@@ -1,3 +1,12 @@
+libssh (0.6.3-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix ftbfs with GCC-5: add patch from Matthias Klose/Ubuntu:
+add __extension__ to __FUNCTION__.
+(Closes: #777975)
+
+ -- gregor herrmann gre...@debian.org Sat, 18 Jul 2015 20:38:30 +0200
+
libssh (0.6.3-4) unstable; urgency=medium
* Add debian/patches/0001_CVE-2014-8132.patch: Fixup error path in
diff -Nru libssh-0.6.3/debian/patches/gcc-5.diff libssh-0.6.3/debian/patches/gcc-5.diff
--- libssh-0.6.3/debian/patches/gcc-5.diff 1970-01-01 01:00:00.0 +0100
+++ libssh-0.6.3/debian/patches/gcc-5.diff 2015-07-18 20:35:00.0 +0200
@@ -0,0 +1,61 @@
+Index: b/include/libssh/pki_priv.h
+===
+--- a/include/libssh/pki_priv.h
b/include/libssh/pki_priv.h
+@@ -29,7 +29,7 @@
+ #define ECDSA_HEADER_END -END EC PRIVATE KEY-
+
+ #define ssh_pki_log(...) \
+-_ssh_pki_log(__FUNCTION__, __VA_ARGS__)
++_ssh_pki_log(__extension__ __FUNCTION__, __VA_ARGS__)
+ void _ssh_pki_log(const char *function,
+ const char *format, ...) PRINTF_ATTRIBUTE(2, 3);
+
+Index: b/include/libssh/priv.h
+===
+--- a/include/libssh/priv.h
b/include/libssh/priv.h
+@@ -179,7 +179,7 @@ void ssh_log_function(int verbosity,
+ const char *function,
+ const char *buffer);
+ #define SSH_LOG(priority, ...) \
+-_ssh_log(priority, __FUNCTION__, __VA_ARGS__)
++_ssh_log(priority, __extension__ __FUNCTION__, __VA_ARGS__)
+
+ /* LEGACY */
+ void ssh_log_common(struct ssh_common_struct *common,
+@@ -197,18 +197,18 @@ struct error_struct {
+ };
+
+ #define ssh_set_error(error, code, ...) \
+-_ssh_set_error(error, code, __FUNCTION__, __VA_ARGS__)
++_ssh_set_error(error, code, __extension__ __FUNCTION__, __VA_ARGS__)
+ void _ssh_set_error(void *error,
+ int code,
+ const char *function,
+ const char *descr, ...) PRINTF_ATTRIBUTE(4, 5);
+
+ #define ssh_set_error_oom(error) \
+-_ssh_set_error_oom(error, __FUNCTION__)
++_ssh_set_error_oom(error, __extension__ __FUNCTION__)
+ void _ssh_set_error_oom(void *error, const char *function);
+
+ #define ssh_set_error_invalid(error) \
+-_ssh_set_error_invalid(error, __FUNCTION__)
++_ssh_set_error_invalid(error, __extension__ __FUNCTION__)
+ void _ssh_set_error_invalid(void *error, const char *function);
+
+
+Index: b/src/auth.c
+===
+--- a/src/auth.c
b/src/auth.c
+@@ -1907,7 +1907,7 @@ int ssh_userauth_kbdint(ssh_session sess
+ * This should not happen
+ */
+ rc = SSH_AUTH_ERROR;
+-ssh_set_error(session,SSH_FATAL,Invalid state in %s, __FUNCTION__);
++ssh_set_error(session,SSH_FATAL,Invalid state in %s, __extension__ __FUNCTION__);
+ }
+ return rc;
+ }
diff -Nru libssh-0.6.3/debian/patches/series libssh-0.6.3/debian/patches/series
--- libssh-0.6.3/debian/patches/series 2015-01-27 00:28:06.0 +0100
+++ libssh-0.6.3/debian/patches/series 2015-07-18 20:35:24.0 +0200
@@ -3,3 +3,4 @@
1003-custom-lib-names.patch
2002-fix-html-doc-generation.patch
2003-disable-expand_tilde_unix-test.patch
+gcc-5.diff
signature.asc
Description: Digital Signature
Processed: libssh: diff for NMU version 0.6.3-4.1
Processing control commands: tags 777975 + pending Bug #777975 [src:libssh] libssh: ftbfs with GCC-5 Added tag(s) pending. -- 777975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777975 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#792808: coreutils: CRC file checks not consistent
On 7/18/2015 3:11 PM, Pádraig Brady wrote: On 18/07/15 19:38, Leslie Rhorer wrote: Package: coreutils Version: 8.23-4 Severity: grave Justification: renders package unusable Dear Maintainer, CRC checks on large files often return variable values. I have tried several different CRC check utilities, md5sum, md6sum, sha56sum, etc., and they all exhibit the same behavior. Multiple runs of the utility on a given file more often than not will return different values for many or all of the attempts. I have only noticed the effect on large files, but I cannot say with authority it only happens on large files. I noticed the effect when checking file integrity between identical files on two different systems. The backup server is running Squeeze, and checks on the files of that system are consistent, but when comparing the CRC between that system and the primary, which is running Jessie, the checks often failed. At first I of course thought this indicated file corruption on one server or the other, beut when I started investigating, I discovered sometimes the results were different on the two systems and sometimes the same. At that point I discovered it was only! th! e machine running Jessie that was producing inconsistent results. At first I thought I was having problems with the file system (and indeed I am, as it happens), but when I copied one of the large files over to a different file system, the problem perissts. One is an XFS file system (the one having the problems) and the other is an Ext4 file system. Note this impacts a great many very important procedures and utilities, including my backup and compare strategy using rsync, file systems checks, etc. RAID-Server:/# sha256sum /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 b2e15ca178832e9f12a4823c583eefb2028cec9f7c45f36ea9dfa2297c904d6d /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 RAID-Server:/# sha256sum /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 eb3067b250d5d16e1d5d3f2b328001be91c4e5107a14e0010940acdab6584f2b /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 RAID-Server:/# sha256sum /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 6eddb4174b49e9bac741070559ad159acaa39a404a1b75c395d716910e5c81ef /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 The inconsistent results are restricted to the Jessie system? I believe so, yes. I just booted up another Jessie system and copied over the file mentioned above, and it worked 3 times in a row. Although not proof positive, it suggests the issue is limited to this machine. I'd run memtest given results like that. I'm not able to reboot at the moment. I'll give it a look later, but memtester shows no errors. Of course that doesn't verify all the memory. Also I'd verify a separate checksum implementation. I don't think debian configures coreutils --with-openssl so this should be independent: openssl md5 largefile RAID-Server:/tmp/temp# openssl md5 Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 MD5(Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4)= fa54d754e0c51653d71d2419a26e18de RAID-Server:/tmp/temp# openssl md5 Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 MD5(Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4)= 6886fc9d69c5d1d3685ed158626ce563 thanks, Pádraig. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790689: marked as done (FTBFS: Makeinfo is missing. Info documentation will not be built.)
Your message dated Sat, 18 Jul 2015 21:34:55 + with message-id e1zgzl1-0006hb...@franck.debian.org and subject line Bug#790689: fixed in binutils-m68hc1x 1:2.18-5 has caused the Debian Bug report #790689, regarding FTBFS: Makeinfo is missing. Info documentation will not be built. 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.) -- 790689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: binutils-m68hc1x Version: 1:2.18-4 Severity: serious sbuild (Debian sbuild) 0.65.2 (24 Mar 2015) on bl460gen8-30.hlinux.usa.hp.com ... configure: creating cache ./config.cache checking whether to enable maintainer-specific portions of Makefiles... no checking for makeinfo... /«PKGBUILDDIR»/binutils-2.18/missing makeinfo --split-size=500 configure: WARNING: *** Makeinfo is missing. Info documentation will not be built. ... WARNING: `makeinfo' is missing on your system. You should only need it if you modified a `.texi' or `.texinfo' file, or any other file indirectly affecting the aspect of the manual. The spurious call might also be the consequence of using a buggy `make' (AIX, DU, IRIX). You might want to install the `Texinfo' package or the `GNU make' package. Grab either from any GNU archive site. make[4]: *** [bfd.info] Error 1 Makefile:388: recipe for target 'bfd.info' failed -- Martin Michlmayr Linux for HP Helion OpenStack, Hewlett-Packard ---End Message--- ---BeginMessage--- Source: binutils-m68hc1x Source-Version: 1:2.18-5 We believe that the bug you reported is fixed in the latest version of binutils-m68hc1x, 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. Andreas Beckmann a...@debian.org (supplier of updated binutils-m68hc1x 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: Sat, 18 Jul 2015 21:58:00 +0200 Source: binutils-m68hc1x Binary: binutils-m68hc1x Architecture: source Version: 1:2.18-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Andreas Beckmann a...@debian.org Description: binutils-m68hc1x - binary utilities that support Motorola's 68HC11/12 targets Closes: 790689 Changes: binutils-m68hc1x (1:2.18-5) unstable; urgency=medium . * QA upload. * Fix broken 02_missing_makeinfo.patch to fix FTBFS with texinfo 6. (Closes: #790689) Checksums-Sha1: f16da5089916285277e556508b5247bbcac73161 1779 binutils-m68hc1x_2.18-5.dsc 2616c85f21d23a1ccc8af882fbc9a91e30923131 99898 binutils-m68hc1x_2.18-5.diff.gz Checksums-Sha256: 2d952d049c2763994998d9a712ecdc72e545a00e5011e51c14f4796d82badf23 1779 binutils-m68hc1x_2.18-5.dsc 18718195a070a8e862e54ae6c1c2f77347108f93cda73f83f01ccde08c7cf4e3 99898 binutils-m68hc1x_2.18-5.diff.gz Files: b0c3325f6d31ef7334d9a6b6680e250f 1779 devel extra binutils-m68hc1x_2.18-5.dsc 3e2377ca5c3ddd9f250951734ff12ff2 99898 devel extra binutils-m68hc1x_2.18-5.diff.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVqrWrAAoJEF+zP5NZ6e0ItzoP/RzGWnxgGw57mxxKyXGpcJzh rNbRvrOPOJl448zS9ykNuydBvmBP2fben1f4e0VI2PLnDeyjhm80B0JoCgIH+PMB QROjRGHZgy1u/p7GGXgZ1RCtVcG7b9Wq14uyUFuRFA5uQRhpacF9XRdmWoknEpG/ jj+hS8XQKbAj06jxIJhcJFL2PhOWuasYqSrn6xyu+oCZUGizgYMDt4QOr60mpzFp nY4205S82o5V6aahCoKeBCp0iW6UtPBP2JBQft5dA7h2EsCygjf5BXpCv/ELqdzY 2iz6TXOv0tCkqnHTJbjoAubazN00K58KFCwkhlA2mMqou+LZIHUv1psskpXcgXAu 6+4+b6OeheNB0lIgatTQj1IRbI+AW856J3oNhty3HHQ/sDW44FNFsM1XPJyhx7j7 fF8+93St2J2oqWIzdewkcK96cS8Xk6X53mol49738LHXraMSOQn+eKtjHEKkdmVf Osa+eD714mGsgT/jv3BE0GAODONC/vyea4RrQOimzuZqT5P0BahAQDrVZWT3084p 1ITIPuHwJeGBulCxfm3D4kORzw236CpyZbtX3tloxBr66NCWaa5z3Xoqj8QAclxt 7846KEjkn3wjQvRVgzdroV/oHPrA83lKkGNYlRiupLp0vzNk88aCnc8trd43xFTf Cy23kGXl/LOypO+D5ETJ =WPhC -END PGP SIGNATUREEnd Message---
Processed: mkvmlinuz exited with return code 20
Processing commands for cont...@bugs.debian.org: tags 791868 + pending Bug #791868 [mkvmlinuz] /etc/kernel/postinst.d/mkvmlinuz exited with return code 20 Bug #741642 [mkvmlinuz] /etc/kernel/postinst.d/mkvmlinuz exited with return code 20 Added tag(s) pending. Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 741642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741642 791868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791868 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#777778: [Aptitude-devel] Bug#792681: cwidget ftbfs with GCC 5
2015-07-18 09:50 Matthias Klose: On 07/17/2015 06:57 PM, Manuel A. Fernandez Montecelo wrote: Hello, 2015-07-17 14:13 GMT+01:00 Matthias Klose d...@debian.org: Package: src:cwidget Version: 0.5.17-2 Severity: normal Tags: sid stretch patch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 GCC 5 complains about using c++11 features without passing -std=c++11. Also setting the maintainer flag without exporting it doesn't help. patch at https://launchpadlibrarian.net/211899860/cwidget_0.5.17-2ubuntu1_0.5.17-2ubuntu2.diff.gz If I found the correct build log where you determined this [1], the compiler fails when including In file included from /usr/include/c++/5/string:52:0, from ../../../src/cwidget/curses++.h:25, from colors.cc:22: Line 22 of colors is: #include cwidget/curses++.h And line 25 of curses++.h is: #include string The error is: --- /usr/include/c++/5/bits/basic_string.h: In instantiation of 'union std::__cxx11::basic_stringcwidget::wchtype::anonymous': /usr/include/c++/5/bits/basic_string.h:119:7: required from 'class std::__cxx11::basic_stringcwidget::wchtype' ../../../src/cwidget/curses++.h:199:31: required from here /usr/include/c++/5/bits/basic_string.h:121:53: error: member 'cwidget::wchtype std::__cxx11::basic_stringcwidget::wchtype::anonymous union::_M_local_buf [1]' with constructor not allowed in union _CharT _M_local_buf[_S_local_capacity + 1]; ^ /usr/include/c++/5/bits/basic_string.h:121:53: note: unrestricted unions only available with -std=c++11 or -std=gnu++11 --- This is because wchtype does not seem to be able to be used as part of unions inside basic_string.h because the constructors/destructors are not trivial enough. I was trying to work around this for a while, because I think that forcing c++11 mode will have cascading effects on rev-deps (currently only one within Debian, but it is aptitude with almost 100% of reported installations by popcon), but I could not find a satisfactory solution yet. Is there a deadline to fix this? yes, Jul 31. please see my email to d-d-a. OK. I knew of the deadline to set GCC-5 as default, I was asking in the case that you planned to NMU before that or not even after it was made default. [1] https://people.debian.org/~doko/logs/gcc5-20150701-ftbfs/logs-failed-gcc5/cwidget_0.5.17-2_unstable_gcc5.log this was the error I saw: [...] Making all in config make[5]: Entering directory '/scratch/packages/tmp/cwidget-0.5.17/src/cwidget/config' /bin/bash ../../../libtool --tag=CXX --mode=compile g++ -DLOCALEDIR=\/usr/share/locale\ -DHAVE_CONFIG_H -I. -I../../.. -Wall -Werror -I../../.. -I. -I../../.. -I../../../src -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -c -o colors.lo colors.cc libtool: compile: g++ -DLOCALEDIR=\/usr/share/locale\ -DHAVE_CONFIG_H -I. -I../../.. -Wall -Werror -I../../.. -I. -I../../.. -I../../../src -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -c colors.cc -fPIC -DPIC -o .libs/colors.o In file included from /usr/include/c++/5/string:52:0, from ../../../src/cwidget/curses++.h:25, from colors.cc:22: /usr/include/c++/5/bits/basic_string.h: In instantiation of 'union std::__cxx11::basic_stringcwidget::wchtype::anonymous': /usr/include/c++/5/bits/basic_string.h:119:7: required from 'class std::__cxx11::basic_stringcwidget::wchtype' ../../../src/cwidget/curses++.h:199:31: required from here /usr/include/c++/5/bits/basic_string.h:121:53: error: member 'cwidget::wchtype std::__cxx11::basic_stringcwidget::wchtype::anonymous union::_M_local_buf [1]' with constructor not allowed in union _CharT _M_local_buf[_S_local_capacity + 1]; ^ /usr/include/c++/5/bits/basic_string.h:121:53: note: unrestricted unions only available with -std=c++11 or -std=gnu++11 Makefile:448: recipe for target 'colors.lo' failed make[5]: *** [colors.lo] Error 1 make[5]: Leaving directory '/scratch/packages/tmp/cwidget-0.5.17/src/cwidget/config' Makefile:603: recipe for target 'all-recursive' failed make[4]: *** [all-recursive] Error 1 I get this error with GCC-5 even if I let the default or explicitly set -std=c++98, which is strange -- why does it try to include C++11 stuff even then, like the namespaces in required from 'class std::__cxx11::basic_stringcwidget::wchtype' in the errors above? It's a bit odd. Also, this code did not change for many years and it was compiling fine, I was trying to look at GCC changelog but I did not see anything immediately obvious that it causes it to fail after years working fine. Anyway, aptitude with GCC-5
Processed: [yaboot] FTBFS: Fails to build from source
Processing commands for cont...@bugs.debian.org: tags 792084 - help + pending Bug #792084 [yaboot] FTBFS: Fails to build from source Removed tag(s) help. Bug #792084 [yaboot] FTBFS: Fails to build from source Added tag(s) pending. tags 774845 - help - d-i + pending Bug #774845 [yaboot] yaboot 1.3.17 is out Removed tag(s) help. Bug #774845 [yaboot] yaboot 1.3.17 is out Removed tag(s) d-i. Bug #774845 [yaboot] yaboot 1.3.17 is out Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 774845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774845 792084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792084 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: FTBFS against Octave 4.0
Processing control commands: block 792740 by -1 Bug #792740 [release.debian.org] transition: octave4.0 792740 was not blocked by any bugs. 792740 was not blocking any bugs. Added blocking bug(s) of 792740: 792826 -- 792740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792740 792826: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792826 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: [yaboot] FTBFS: Fails to build from source
Processing commands for cont...@bugs.debian.org: tags 792084 - pending Bug #792084 [yaboot] FTBFS: Fails to build from source Removed tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 792084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792084 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#792808: coreutils: CRC file checks not consistent
On 18/07/15 19:38, Leslie Rhorer wrote: Package: coreutils Version: 8.23-4 Severity: grave Justification: renders package unusable Dear Maintainer, CRC checks on large files often return variable values. I have tried several different CRC check utilities, md5sum, md6sum, sha56sum, etc., and they all exhibit the same behavior. Multiple runs of the utility on a given file more often than not will return different values for many or all of the attempts. I have only noticed the effect on large files, but I cannot say with authority it only happens on large files. I noticed the effect when checking file integrity between identical files on two different systems. The backup server is running Squeeze, and checks on the files of that system are consistent, but when comparing the CRC between that system and the primary, which is running Jessie, the checks often failed. At first I of course thought this indicated file corruption on one server or the other, beut when I started investigating, I discovered sometimes the results were different on the two systems and sometimes the same. At that point I discovered it was only th! e machine running Jessie that was producing inconsistent results. At first I thought I was having problems with the file system (and indeed I am, as it happens), but when I copied one of the large files over to a different file system, the problem perissts. One is an XFS file system (the one having the problems) and the other is an Ext4 file system. Note this impacts a great many very important procedures and utilities, including my backup and compare strategy using rsync, file systems checks, etc. RAID-Server:/# sha256sum /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 b2e15ca178832e9f12a4823c583eefb2028cec9f7c45f36ea9dfa2297c904d6d /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 RAID-Server:/# sha256sum /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 eb3067b250d5d16e1d5d3f2b328001be91c4e5107a14e0010940acdab6584f2b /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 RAID-Server:/# sha256sum /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 6eddb4174b49e9bac741070559ad159acaa39a404a1b75c395d716910e5c81ef /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 The inconsistent results are restricted to the Jessie system? I'd run memtest given results like that. Also I'd verify a separate checksum implementation. I don't think debian configures coreutils --with-openssl so this should be independent: openssl md5 largefile thanks, Pádraig. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778176: Revised gcc-5 patch for x11-xserver-utils
On Sat, Jul 18, 2015 at 09:39:03 -0700, Daniel Schepler wrote: On Sat, 7 Mar 2015 08:57:48 +0100, Julien Cristau wrote: I don't think that's an acceptable way to fix this. How about this? (This is a patch to be directly quilt imported, not a debdiff.) How portable is -P? What change in gcc makes this necessary? What does the output without -P look like with cpp 5 vs 4.9? Cheers, Julien signature.asc Description: Digital signature
Bug#768717: marked as done (adzapper: FTBFS in jessie: build-dependency not installable: libswf-perl)
Your message dated Sat, 18 Jul 2015 23:14:23 +0200 with message-id 55aac1af.2060...@debian.org and subject line Re: adzapper: FTBFS in jessie: build-dependency not installable: libswf-perl has caused the Debian Bug report #768717, regarding adzapper: FTBFS in jessie: build-dependency not installable: libswf-perl 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.) -- 768717: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: adzapper Version: 20090301.dfsg.1-0.2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install adzapper build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-adzapper-dummy : Depends: libswf-perl but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/adzapper_20090301.dfsg.1-0.2_jessie.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--- On Sun, 9 Nov 2014 08:40:21 +0100 Lucas Nussbaum lu...@lucas-nussbaum.net wrote: Source: adzapper Version: 20090301.dfsg.1-0.2 During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Neither adzapper nor libswf-perl was included in the jessie release. adzapper builds fine in sid (just tested amd64 and i386), thus closing this bug. Andreas---End Message---
Processed: clearsilver: diff for NMU version 0.10.5-1.5
Processing control commands: tags 755963 + pending Bug #755963 [clearsilver] FTBFS with clang instead of gcc Bug #777817 [clearsilver] clearsilver: ftbfs with GCC-5 Added tag(s) pending. Added tag(s) pending. -- 755963: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755963 777817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777831: [Deborphan-devel] Bug#777831: deborphan: diff for NMU version 1.7.28.8-0.2
Hi Gregor, Jakub, Le 18/07/2015 18:22, gregor herrmann a écrit : I've prepared an NMU for deborphan (versioned as 1.7.28.8-0.2) … + * Fix ftbfs with GCC-5: apply patch from Jakub Wilk Thank you both! uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Feel free to reschedule it to DELAYED/0, I don’t expect any of the (wrongly) documented uploaders to vote against any (NM-)maintenance. Regards David signature.asc Description: OpenPGP digital signature
Bug#788766: marked as done (ifrit: FTBFS with libvtk5.8: VTK is not found.)
Your message dated Sat, 18 Jul 2015 16:34:28 + with message-id e1zgv4g-00059q...@franck.debian.org and subject line Bug#788766: fixed in ifrit 3.4.2-2 has caused the Debian Bug report #788766, regarding ifrit: FTBFS with libvtk5.8: VTK is 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.) -- 788766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788766 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ifrit Version: 3.4.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, The package fails to build as libvtk5-dev installs vtk-5.8: CMake Error at CMakeLists.txt:139 (INCLUDE): include could not find load file: /usr/share/cmake-3.2/Modules/FindVTK.cmake CMake Error at CMakeLists.txt:141 (MESSAGE): VTK is not found. Please check that VTKDIR variables is set properly. This class of problem seems to have been fixed before: #536904 The full build log is available on the Reproducible Builds builder: https://reproducible.debian.net/rb-pkg/unstable/amd64/ifrit.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-20-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ---End Message--- ---BeginMessage--- Source: ifrit Source-Version: 3.4.2-2 We believe that the bug you reported is fixed in the latest version of ifrit, 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. Andreas Beckmann a...@debian.org (supplier of updated ifrit 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: Sat, 18 Jul 2015 18:09:06 +0200 Source: ifrit Binary: ifrit Architecture: source Version: 3.4.2-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Andreas Beckmann a...@debian.org Description: ifrit - powerful tool for visualizing 3-dimensional data sets Closes: 788766 Changes: ifrit (3.4.2-2) unstable; urgency=medium . * QA upload. * Use the CMake 3.2 way to find VTK. (Closes: #788766) * Move packaging repository to collab-maint and import missing history. Checksums-Sha1: 0812547429a96fe3355315ea7850b4b7c8d2bc88 1898 ifrit_3.4.2-2.dsc c7bde93ba60bdc85dc6e65c6af692c01cd4010ee 7512 ifrit_3.4.2-2.debian.tar.xz Checksums-Sha256: 2a30bafd6b21e929cc198992258acb73b6dc173a0f4056c6b9795fb673b2c6c1 1898 ifrit_3.4.2-2.dsc 866f9b4830200dc93f14f71586aa5909166d5ec087050cc0404d3643633179e8 7512 ifrit_3.4.2-2.debian.tar.xz Files: 2782eeda4d5642c7d1fcc1c6e8e5f511 1898 science optional ifrit_3.4.2-2.dsc 8aa567a7e4f92a873b44fc0127117d9d 7512 science optional ifrit_3.4.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIbBAEBCAAGBQJVqn4SAAoJEF+zP5NZ6e0IyjMP9iWiXAAq9eUoDxUCJOTib98o Zq4kDdqV0oVUb2FpLnyz/KVowniuCdDUwQOXXm7NP6xmI6405uH8cUjYfBlDobXG e5q6ippMQdnFuxFzZ7RbUZU2Sha4c0LnMblwlW8AJpW6AMI2pCSg9dyf8l1ev+Pb yXfPGSVezS32wIrtBVUhV3LKvxZzKKT6hWKJxGICEStpC911iCm7UIY+5Opq1nan Mqg4T+NIYNj0xWrq4nSZh78XoY2DIe2A3aqlk0Id0auyP1NBi+wS8cmt/9eWEYfj WG7NaTFpK3uLOJHHpvmmdYsi7u2V5PpMDd938ocjtHZA9ZZgDcWoZjwJjfFtuzdo +tC4Ec0wPYlRVIQfMNls+C39LkFWc+48CRSOeI+CwnLgH9y6BOd9TAKCqsMimTok Oxc0UKEtagu7k5/uigmKZ2K6VeEjLbzntVjWZjvRegtYa5pXQ26kCQHl3SbFp/tG z6PgkW4Pa3MbT+7OhLb6aeUfGaCtD97MQeWr22LVGhqp+JMwb7qrMyq/9xbVd2xY kG4xp60altVoQ32BWMtWr8ZQyH63aq6kUJggGrv4bJPYaLQ5bfiG04kPv8dTtNZA u7DyfRdDlBM4wE09OWjNdjuISR9Pb8nWAG5Q/3cUR/+wsIk9VezZVb22JeCm9BYC Ht+7azFrmbTgZIV+gwg= =gj9V -END PGP SIGNATUREEnd Message---
Bug#777882: Patch for GCC 5 build issue
On Tue, 07 Jul 2015 18:04:47 +, Pearson, Greg wrote: Here's a fix for the GCC 5 build issue. I added extern to the callable copy of the inline functions to ensure an externally visible function is emitted, please see section Different semantics for inline functions at https://gcc.gnu.org/gcc-5/porting_to.html for more background. I can confirm that this patch fixes the GCC 5 build failure; but with it the build in unstable (i.e. with GCC 4.9) fails: xgnokii-xgnokii.o: In function `CreateAboutDialog': /tmp/buildd/gnokii-0.6.30+dfsg/xgnokii/xgnokii.c:1187: undefined reference to `GUI_HideAbout' xgnokii-xgnokii_logos.o:(.data+0x1c0): undefined reference to `CloseLogosWindow' collect2: error: ld returned 1 exit status Makefile:486: recipe for target 'xgnokii' failed Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Bettina Wegner: Sie hat's gewusst signature.asc Description: Digital Signature
Bug#777907: Patch for GCC5 build issue
On Wed, 15 Jul 2015 14:53:42 -0600, Nicholas Luedtke wrote: Here's a fix for the GCC 5 build issue. Removed extern from inline functions in hunt.h. The package builds and links with GCC 5 with this change. I can confirm that the patch fixes the build failure with GCC 5. But now it fails in unstable (i.e. with gcc 4.9): cc -o hunt hunt.o main.o c/list.o c/hash.o c/array.o util.o net.o rst.o menu.o hijack.o rstd.o sniff.o macdisc.o tap.o arphijack.o tty.o synchijack.o arpspoof.o hostup.o addpolicy.o options.o resolv.o timer.o pktrelay.o -lpthread main.o: In function `generate_key': /tmp/buildd/hunt-1.5/hunt.h:297: multiple definition of `generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:297: first defined here main.o: In function `uci_generate_key': /tmp/buildd/hunt-1.5/hunt.h:309: multiple definition of `uci_generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:309: first defined here util.o: In function `generate_key': /tmp/buildd/hunt-1.5/hunt.h:297: multiple definition of `generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:297: first defined here util.o: In function `uci_generate_key': /tmp/buildd/hunt-1.5/hunt.h:309: multiple definition of `uci_generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:309: first defined here net.o: In function `generate_key': /tmp/buildd/hunt-1.5/hunt.h:297: multiple definition of `generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:297: first defined here net.o: In function `uci_generate_key': /tmp/buildd/hunt-1.5/hunt.h:309: multiple definition of `uci_generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:309: first defined here rst.o: In function `generate_key': /tmp/buildd/hunt-1.5/hunt.h:297: multiple definition of `generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:297: first defined here rst.o: In function `uci_generate_key': /tmp/buildd/hunt-1.5/hunt.h:309: multiple definition of `uci_generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:309: first defined here menu.o: In function `generate_key': /tmp/buildd/hunt-1.5/hunt.h:297: multiple definition of `generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:297: first defined here menu.o: In function `uci_generate_key': /tmp/buildd/hunt-1.5/hunt.h:309: multiple definition of `uci_generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:309: first defined here hijack.o: In function `generate_key': /tmp/buildd/hunt-1.5/hunt.h:297: multiple definition of `generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:297: first defined here hijack.o: In function `uci_generate_key': /tmp/buildd/hunt-1.5/hunt.h:309: multiple definition of `uci_generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:309: first defined here rstd.o: In function `generate_key': /tmp/buildd/hunt-1.5/hunt.h:297: multiple definition of `generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:297: first defined here rstd.o: In function `uci_generate_key': /tmp/buildd/hunt-1.5/hunt.h:309: multiple definition of `uci_generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:309: first defined here sniff.o: In function `generate_key': /tmp/buildd/hunt-1.5/hunt.h:297: multiple definition of `generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:297: first defined here sniff.o: In function `uci_generate_key': /tmp/buildd/hunt-1.5/hunt.h:309: multiple definition of `uci_generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:309: first defined here macdisc.o: In function `generate_key': /tmp/buildd/hunt-1.5/hunt.h:297: multiple definition of `generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:297: first defined here macdisc.o: In function `uci_generate_key': /tmp/buildd/hunt-1.5/hunt.h:309: multiple definition of `uci_generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:309: first defined here tap.o: In function `generate_key': /tmp/buildd/hunt-1.5/hunt.h:297: multiple definition of `generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:297: first defined here tap.o: In function `uci_generate_key': /tmp/buildd/hunt-1.5/hunt.h:309: multiple definition of `uci_generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:309: first defined here arphijack.o: In function `generate_key': /tmp/buildd/hunt-1.5/hunt.h:297: multiple definition of `generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:297: first defined here arphijack.o: In function `uci_generate_key': /tmp/buildd/hunt-1.5/hunt.h:309: multiple definition of `uci_generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:309: first defined here tty.o: In function `generate_key': /tmp/buildd/hunt-1.5/hunt.h:297: multiple definition of `generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:297: first defined here tty.o: In function `uci_generate_key': /tmp/buildd/hunt-1.5/hunt.h:309: multiple definition of `uci_generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:309: first defined here synchijack.o: In function `generate_key': /tmp/buildd/hunt-1.5/hunt.h:297: multiple definition of `generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:297: first defined here synchijack.o: In function `uci_generate_key': /tmp/buildd/hunt-1.5/hunt.h:309: multiple definition of `uci_generate_key' hunt.o:/tmp/buildd/hunt-1.5/hunt.h:309: first
Bug#792656: marked as done (mirage: fails to install: mirage.postinst: update-desktop-database: not found)
Your message dated Sat, 18 Jul 2015 21:01:57 +0200 with message-id 55aaa2a5.8060...@debian.org and subject line Re: mirage: fails to install: mirage.postinst: update-desktop-database: not found has caused the Debian Bug report #792656, regarding mirage: fails to install: mirage.postinst: update-desktop-database: 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.) -- 792656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mirage Version: 0.9.5.1-4 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...): Setting up mirage (0.9.5.1-4) ... /var/lib/dpkg/info/mirage.postinst: 20: /var/lib/dpkg/info/mirage.postinst: update-desktop-database: not found dpkg: error processing package mirage (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: mirage cheers, Andreas mirage_0.9.5.1-4.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Version: 0.9.5.1-5 On Fri, 17 Jul 2015 09:51:16 +0200 Andreas Beckmann a...@debian.org wrote: Setting up mirage (0.9.5.1-4) ... /var/lib/dpkg/info/mirage.postinst: 20: /var/lib/dpkg/info/mirage.postinst: update-desktop-database: not found Seems to be fixed in the next upload. Andreas---End Message---
Bug#778039: Patch for GCC 5 build issue
On Thu, 16 Jul 2015 13:30:40 -0600, Josh Gadeken wrote: Here's a fix for the GCC 5 build issue. I added -Wno-error=format-security to the GNUmakefile. The package successfully builds and links using GCC 5 with this change. I don't think that's the best way forward. Since this is security-relevant I think we should rather fix the problem than ignoring the errors. And I remember that in some previous mass fix campaign in Debian we already fixed quite a few -Werror=format-security issues. Please note that dpkg-buildflags sets -Werror=format-security by default: % dpkg-buildflags CFLAGS=-g -O2 -fstack-protector-strong -Wformat -Werror=format-security [..] Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Rolling Stones: She's A Rainbow (45 version)/She's a Rainbow - 2 signature.asc Description: Digital Signature
Bug#788533: mapnik: FTBFS: virtual memory exhausted: Cannot allocate memory (Was: Bug#756867: transition: gdal)
On Thu, Jul 16, 2015 at 23:20:59 +0200, Jérémy Lal wrote:
Failing to build on a release architecture is generally an RC bug, which
prevents testing migration.
Kind Regards,
Bas
I'm very surprised by this. The opposite was explained to me on
#debian-devel by
by Julien Cristau (cc-ing him in case he can tell me how i got this the
wrong way).
Is this written somewhere ?
Failing to build on a release architecture is not an RC bug, unless it's
a regression. See section 4 of
https://release.debian.org/stretch/rc_policy.txt
If there's no version of the package on ${architecture} in unstable
(either because it never built or because old builds have been removed),
then a failure to build on ${architecture} is somewhere between
wishlist and important, but it's not RC.
Cheers,
Julien
signature.asc
Description: Digital signature
Bug#792048: marked as done (xdemorse: FTBFS: ***Error***: You must have automake = 1.9 installed)
Your message dated Sat, 18 Jul 2015 15:43:18 +
with message-id e1zgugk-0004kp...@franck.debian.org
and subject line Bug#792048: fixed in xdemorse 2.9-3
has caused the Debian Bug report #792048,
regarding xdemorse: FTBFS: ***Error***: You must have automake = 1.9 installed
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.)
--
792048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792048
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: xdemorse
Version: 2.9-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
The package depends on automake, but it checks up to automake 1.14, while now
the default is 1.15.
Please either expand the check or build-depend on a fixed automake version (the
former is slightly preferred).
Build log tail:
dh_autoreconf /tmp/buildd/xdemorse-2.9/autogen.sh
find ! -ipath ./debian/* -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f -exec
md5sum {} \; debian/autoreconf.before
/tmp/buildd/xdemorse-2.9/autogen.sh
checking for autoconf = 2.53...
testing autoconf2.50... not found.
testing autoconf... found 2.69
checking for automake = 1.9...
testing automake-1.14... not found.
testing automake-1.13... not found.
testing automake-1.12... not found.
testing automake-1.11... not found.
testing automake-1.10... not found.
testing automake-1.9... not found.
***Error***: You must have automake = 1.9 installed
to build Package. Download the appropriate package for
from your distribution or get the source tarball at
http://ftp.gnu.org/pub/gnu/automake/automake-1.9.tar.gz
find ! -ipath ./debian/* -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f -exec
md5sum {} \; debian/autoreconf.after
dh_autoreconf: /tmp/buildd/xdemorse-2.9/autogen.sh returned exit code 1
debian/rules:10: recipe for target 'override_dh_autoreconf' failed
make[1]: *** [override_dh_autoreconf] Error 2
make[1]: Leaving directory '/tmp/buildd/xdemorse-2.9'
debian/rules:7: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
E: Failed autobuilding of package
You can see a full build log at
https://reproducible.debian.net/rb-pkg/unstable/amd64/xdemorse.html
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: xdemorse
Source-Version: 2.9-3
We believe that the bug you reported is fixed in the latest version of
xdemorse, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 792...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann a...@debian.org (supplier of updated xdemorse 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: Sat, 18 Jul 2015 16:50:58 +0200
Source: xdemorse
Binary: xdemorse
Architecture: source
Version: 2.9-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group packa...@qa.debian.org
Changed-By: Andreas Beckmann a...@debian.org
Description:
xdemorse - decode Morse signals to text
Closes: 792048
Changes:
xdemorse (2.9-3) unstable; urgency=medium
.
* QA upload.
* Check for unversioned automake binary, too. (Closes: #792048)
Checksums-Sha1:
3119dc7f790fcf2258b4849578ea71a4d3d69fa9 1768 xdemorse_2.9-3.dsc
a6774c906d09889edd16526519904dabce8f1265 4672 xdemorse_2.9-3.debian.tar.xz
Checksums-Sha256:
3e59d2989aed77c6dcf3efe4189b7d6df76ed9ed68186c74800053d959bcafc3 1768
xdemorse_2.9-3.dsc
ec81b21024adb308a159d730c98ea49371dedaff52af4e9ce45b649b943b5787 4672
xdemorse_2.9-3.debian.tar.xz
Files:
4bdd57bd17defacbe4e7893f7b496d32
Bug#787178: marked as done (wdg-html-validator: Remove w3c-dtd-xhtml reference from d/control)
Your message dated Sat, 18 Jul 2015 15:43:14 + with message-id e1zgugg-0004jb...@franck.debian.org and subject line Bug#787178: fixed in wdg-html-validator 1.6.2-8 has caused the Debian Bug report #787178, regarding wdg-html-validator: Remove w3c-dtd-xhtml reference from d/control 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.) -- 787178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787178 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: wdg-html-validator Severity: serious Justification: rely on obsolete package Control: blocks 711332 with -1 Please remove reference to w3c-dtd-xhtml from debian/control. This package will be removed for stretch (see #711332), it has been superseded by w3c-sgml-lib. -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (700, 'stable'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ---End Message--- ---BeginMessage--- Source: wdg-html-validator Source-Version: 1.6.2-8 We believe that the bug you reported is fixed in the latest version of wdg-html-validator, 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 787...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann a...@debian.org (supplier of updated wdg-html-validator 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: Sat, 18 Jul 2015 15:55:22 +0200 Source: wdg-html-validator Binary: wdg-html-validator Architecture: source all Version: 1.6.2-8 Distribution: unstable Urgency: medium Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Andreas Beckmann a...@debian.org Description: wdg-html-validator - WDG HTML Validator Closes: 787178 Changes: wdg-html-validator (1.6.2-8) unstable; urgency=medium . * QA upload. * Switch B-D from w3c-dtd-xhtml to w3c-sgml-lib. (Closes: #787178) Checksums-Sha1: b7053f6a84d61f7ae279be117689d053338454b6 1771 wdg-html-validator_1.6.2-8.dsc 84b312192d35c9bfc73f61871d47d54640553208 13253 wdg-html-validator_1.6.2-8.diff.gz 31a7ef2e5ea8f06b59089941d3e0744797b8150f 186876 wdg-html-validator_1.6.2-8_all.deb Checksums-Sha256: 0d990ceb655fa5ef85ca666cb3b857dc04a4fb9dd3530c505f926be9f84a9d3d 1771 wdg-html-validator_1.6.2-8.dsc 60b948da33f0f4942fc7a247065a3fd5eac5246a33fbdeb3876b73f6efe127f0 13253 wdg-html-validator_1.6.2-8.diff.gz 3eb1592e490dc5ea94290899a683f572779a797fed1e995e4532cc2e435640eb 186876 wdg-html-validator_1.6.2-8_all.deb Files: a5643046b4297049bc1f6f2502cd7b6c 1771 web optional wdg-html-validator_1.6.2-8.dsc daedfeca3189088df50858c152d07f5a 13253 web optional wdg-html-validator_1.6.2-8.diff.gz 55c8ace8741ba3dca8f5bac95456079a 186876 web optional wdg-html-validator_1.6.2-8_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVqmP2AAoJEF+zP5NZ6e0IUkIQAIFMURY6yumA0BEfcKqNqHI8 LxyfYzg7DJCm2ECsr/8J75fFtDM4QhzXT0sU4UJoQp2/V1wTC820Y99phpieQ7yu Szhp8L8CKFa8yXhjuvtUp/moLilVcC0h5D+JDEKP2Cg8/Ct6n6Grahv4IJP3haDt JIjQInB/0ODjIoQT/KwPwJ0fi4rzZUCy+DPsgLJP/g6FCoX6fU1GlK5Rgcebd0SN 2iciXyrPNTkm3dpH/Vaa5dsLI+JG/PfUMvScXH/m5flqlPjkhGnPnL+13CLTjwLD a2nMqZGMFwu2unYV+Bwoib1vw3MoH1xsZx60rFrWzjP0YByW+JdOfhQRNKyWaQ0l TX56b3f0YKUia/FUEuTmU6ofnIHDrACqrFdo81VDL0GhsPkasfPKA7HRXxP91cGO 1lp7osK0PoupOY/faVjjRaCHSZUCapQQyMErb9pXjwW42LNs3awl5uqfEMNzUvAv eVd8EQkZzOTQPqWNHogjNkMQxLl/ewTwkTrENaL0xmSvkKRNWEeMHwJ8NydDaPaW tBDJ3Mnm9ZilaEDY6wlNWv3FjEgruNLbaKRmF0G17MNUcxvrCOyWC3yNhOvpdQUn e8GzZ67rGC7p5fbVVDPIGyQBAuBpRPu69MX/M/LV1owwwfk6B/BjFYtke1NXAsCD tiAfEchNfk2b3dggn3my =Tlsx -END PGP SIGNATUREEnd Message---
Bug#755961: marked as done (FTBFS with clang instead of gcc)
Your message dated Sat, 18 Jul 2015 16:18:55 + with message-id e1zgupd-0002tm...@franck.debian.org and subject line Bug#755961: fixed in autounit 0.20.1-5 has caused the Debian Bug report #755961, regarding FTBFS with clang instead of gcc 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.) -- 755961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: autounit Severity: minor Tags: patch User: pkg-llvm-t...@lists.alioth.debian.org Usertags: clang-ftbfs Hello, Using the rebuild infrastructure, your package fails to build with clang (instead of gcc). We detected this kinf of error: http://clang.debian.net/status.php?version=3.4.2key=EXPECTED_DECLARATION Full build log is available here: http://clang.debian.net/logs/2014-06-16/autounit_0.20.1-4_unstable_clang.log Thanks, Alexander -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- ./c-unit/autounit.h 2006-07-14 00:50:07.0 +0400 +++ ../autounit-0.20.1-my/./c-unit/autounit.h 2014-07-25 01:00:52.303321575 +0400 @@ -200,33 +200,33 @@ #if defined (__STDC_VERSION__) __STDC_VERSION__ = 199901L -#define au_assert(t, expr, err_msg, ...) au_assert_true(t, expr, __FILE__, __LINE__, err_msg, __VA_ARGS__) +#define au_assert(t, expr, err_msg, ...) au_assert_true(t, expr, __FILE__, __LINE__, err_msg, ##__VA_ARGS__) -#define au_assert_fail(t, err_msg, ...) au_assert_true(t, 0, __FILE__, __LINE__, err_msg, __VA_ARGS__) +#define au_assert_fail(t, err_msg, ...) au_assert_true(t, 0, __FILE__, __LINE__, err_msg, ##__VA_ARGS__) -#define au_assert_succeed(t, err_msg, ...) au_assert_true(t, 1, __FILE__, __LINE__, err_msg, __VA_ARGS__) +#define au_assert_succeed(t, err_msg, ...) au_assert_true(t, 1, __FILE__, __LINE__, err_msg, ##__VA_ARGS__) -#define au_asserteq_str(t, str1, str2, err_msg, ...) au_assert_str_int(t, AU_REL_EQUAL, str1, str2, __FILE__, __LINE__, err_msg, __VA_ARGS__) +#define au_asserteq_str(t, str1, str2, err_msg, ...) au_assert_str_int(t, AU_REL_EQUAL, str1, str2, __FILE__, __LINE__, err_msg, ##__VA_ARGS__) -#define au_assertrel_str(t, type, str1, str2, err_msg, ...) au_assert_str_int(t, type, str1, str2, __FILE__, __LINE__, err_msg, __VA_ARGS__) +#define au_assertrel_str(t, type, str1, str2, err_msg, ...) au_assert_str_int(t, type, str1, str2, __FILE__, __LINE__, err_msg, ##__VA_ARGS__) -#define au_asserteq_uint64(t, in1, in2, err_msg, ...) au_assert_guint64_int(t, AU_REL_EQUAL, in1, in2, __FILE__, __LINE__, err_msg, __VA_ARGS__) +#define au_asserteq_uint64(t, in1, in2, err_msg, ...) au_assert_guint64_int(t, AU_REL_EQUAL, in1, in2, __FILE__, __LINE__, err_msg, ##__VA_ARGS__) -#define au_assertrel_uint64(t, type, in1, in2, err_msg, ...) au_assert_guint64_int(t, type, in1, in2, __FILE__, __LINE__, err_msg, __VA_ARGS__) +#define au_assertrel_uint64(t, type, in1, in2, err_msg, ...) au_assert_guint64_int(t, type, in1, in2, __FILE__, __LINE__, err_msg, ##__VA_ARGS__) -#define au_asserteq_int(t, in1, in2, err_msg, ...) au_assert_gint64_int(t, AU_REL_EQUAL, in1, in2, __FILE__, __LINE__, err_msg, __VA_ARGS__) +#define au_asserteq_int(t, in1, in2, err_msg, ...) au_assert_gint64_int(t, AU_REL_EQUAL, in1, in2, __FILE__, __LINE__, err_msg, ##__VA_ARGS__) -#define au_assertrel_int(t, type, in1, in2, err_msg, ...) au_assert_gint64_int(t, type, in1, in2, __FILE__, __LINE__, err_msg, __VA_ARGS__) +#define au_assertrel_int(t, type, in1, in2, err_msg, ...) au_assert_gint64_int(t, type, in1, in2, __FILE__, __LINE__, err_msg, ##__VA_ARGS__) -#define au_asserteq_char(t, in1, in2, err_msg, ...) au_asserteq_char_int(t, in1, in2, __FILE__, __LINE__, err_msg, __VA_ARGS__) +#define au_asserteq_char(t, in1, in2, err_msg, ...) au_asserteq_char_int(t, in1, in2, __FILE__, __LINE__, err_msg, ##__VA_ARGS__) -#define au_asserteq_obj(t, ob1, ob2, compare_func, err_msg, ...) au_assert_obj_int(t, AU_REL_EQUAL, (gpointer)ob1, (gpointer)ob2, compare_func, 0, 0, __FILE__, __LINE__, err_msg, __VA_ARGS__) +#define au_asserteq_obj(t, ob1, ob2, compare_func, err_msg, ...) au_assert_obj_int(t, AU_REL_EQUAL, (gpointer)ob1, (gpointer)ob2, compare_func, 0, 0, __FILE__, __LINE__, err_msg, ##__VA_ARGS__) -#define au_assertrel_obj(t, type, ob1, ob2, compare_func, err_msg, ...) au_assert_obj_int(t, type, (gpointer)ob1,
Bug#777788: marked as done (autounit: ftbfs with GCC-5)
Your message dated Sat, 18 Jul 2015 16:18:55 + with message-id e1zgupd-0002tm...@franck.debian.org and subject line Bug#755961: fixed in autounit 0.20.1-5 has caused the Debian Bug report #755961, regarding autounit: 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.) -- 755961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:autounit Version: 0.20.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/autounit_0.20.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 [...] Making check in c-unit make[2]: Entering directory '/«PKGBUILDDIR»/c-unit' Making check in . make[3]: Entering directory '/«PKGBUILDDIR»/c-unit' /bin/bash ../libtool --tag=CC --mode=compile x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I..-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I../c-unit -I.. -I../intl -I../intl -g -O2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -MT test.lo -MD -MP -MF .deps/test.Tpo -c -o test.lo test.c libtool: compile: x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I../c-unit -I.. -I../intl -I../intl -g -O2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -MT test.lo -MD -MP -MF .deps/test.Tpo -c test.c -fPIC -DPIC -o .libs/test.o In file included from test.c:30:0: test.c: In function 'au_run_test_fork': ./autounit.h:203:106: error: expected expression before ')' token #define au_assert(t, expr, err_msg, ...) au_assert_true(t, expr, __FILE__, __LINE__, err_msg, __VA_ARGS__) ^ test.c:305:7: note: in expansion of macro 'au_assert' au_assert(t, 0, _(pipe failed)); ^ ./autounit.h:203:106: error: expected expression before ')' token #define au_assert(t, expr, err_msg, ...) au_assert_true(t, expr, __FILE__, __LINE__, err_msg, __VA_ARGS__) ^ test.c:311:7: note: in expansion of macro 'au_assert' au_assert(t, 0, _(fork failed)); ^ test.c:324:2: warning: implicit declaration of function 'exit' [-Wimplicit-function-declaration] exit(0); ^ test.c:324:2: warning: incompatible implicit declaration of built-in function 'exit' test.c:324:2: note: include 'stdlib.h' or provide a declaration of 'exit' In file included from test.c:30:0: ./autounit.h:203:106: error: expected expression before ')' token #define au_assert(t, expr, err_msg, ...) au_assert_true(t, expr, __FILE__, __LINE__, err_msg, __VA_ARGS__) ^ test.c:349:6: note: in expansion of macro 'au_assert' au_assert(t, 0, _(test failed with signal)); ^ ./autounit.h:203:106: error: expected expression before ')' token #define au_assert(t, expr, err_msg, ...) au_assert_true(t, expr, __FILE__, __LINE__, err_msg, __VA_ARGS__) ^ test.c:354:6: note: in expansion of macro 'au_assert' au_assert(t, 0, _(test failed with core dump)); ^ make[3]: *** [test.lo] Error 1 Makefile:475: recipe for target 'test.lo' failed make[3]: Leaving directory '/«PKGBUILDDIR»/c-unit'
Bug#777880: gnac: diff for NMU version 0.2.4-1.1
Control: tags 777880 + pending Dear maintainer, I've prepared an NMU for gnac (versioned as 0.2.4-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: STS: Regen fällt auf Milos diff -Nru gnac-0.2.4/debian/changelog gnac-0.2.4/debian/changelog --- gnac-0.2.4/debian/changelog 2012-04-15 20:17:08.0 +0200 +++ gnac-0.2.4/debian/changelog 2015-07-18 18:55:09.0 +0200 @@ -1,3 +1,12 @@ +gnac (0.2.4-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix ftbfs with GCC-5: +add patch from Greg Pearson: fix typo in header file. +(Closes: #777880) + + -- gregor herrmann gre...@debian.org Sat, 18 Jul 2015 18:55:05 +0200 + gnac (0.2.4-1) unstable; urgency=low * Initial release (Closes: #668665) diff -Nru gnac-0.2.4/debian/patches/gcc5.patch gnac-0.2.4/debian/patches/gcc5.patch --- gnac-0.2.4/debian/patches/gcc5.patch 1970-01-01 01:00:00.0 +0100 +++ gnac-0.2.4/debian/patches/gcc5.patch 2015-07-18 18:52:58.0 +0200 @@ -0,0 +1,18 @@ +Description: fix build failure with gcc5: typo in header file +Origin: vendor +Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777880 +Author: Pearson, Greg greg.pear...@hp.com +Reviewed-by: gregor herrmann gre...@debian.org +Last-Update: 2015-07-18 + +--- a/libgnac/libgnac-debug.h 2015-07-07 16:52:48.337744119 + b/libgnac/libgnac-debug.h 2015-07-07 16:55:00.145748723 + +@@ -52,7 +52,7 @@ + + #if defined(__STDC_VERSION__) __STDC_VERSION__ = 199901L + #define libgnac_critical(...) \ +-libgnac_critial_real (__func__, __FILE__, __LINE__, TRUE, __VA_ARGS__) ++libgnac_critical_real (__func__, __FILE__, __LINE__, TRUE, __VA_ARGS__) + #elif defined(__GNUC__) __GNUC__ = 3 + #define libgnac_critical(...) \ + libgnac_critical_real (__FUNCTION__, __FILE__, __LINE__, __VA_ARGS__) diff -Nru gnac-0.2.4/debian/patches/series gnac-0.2.4/debian/patches/series --- gnac-0.2.4/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ gnac-0.2.4/debian/patches/series 2015-07-18 18:51:50.0 +0200 @@ -0,0 +1 @@ +gcc5.patch signature.asc Description: Digital Signature
Processed: hugs98: diff for NMU version 98.200609.21-5.4
Processing control commands: tags 777903 + pending Bug #777903 [src:hugs98] hugs98: ftbfs with GCC-5 Added tag(s) pending. -- 777903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777903 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#777903: hugs98: diff for NMU version 98.200609.21-5.4
Control: tags 777903 + pending Dear maintainer, I've prepared an NMU for hugs98 (versioned as 98.200609.21-5.4) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Elmore James: The Sky Is Crying diff -u hugs98-98.200609.21/debian/rules hugs98-98.200609.21/debian/rules --- hugs98-98.200609.21/debian/rules +++ hugs98-98.200609.21/debian/rules @@ -56,7 +56,7 @@ done # touch so that patched configure does not trigger autoreconf touch configure.ac aclocal.m4 touch configure - CFLAGS='-Wall -fPIC' $(MAKE) EXTRA_CONFIGURE_OPTS=$(CONFIG_OPTS) + CFLAGS='-Wall -fPIC -std=gnu89' $(MAKE) EXTRA_CONFIGURE_OPTS=$(CONFIG_OPTS) touch $@ clean: diff -u hugs98-98.200609.21/debian/changelog hugs98-98.200609.21/debian/changelog --- hugs98-98.200609.21/debian/changelog +++ hugs98-98.200609.21/debian/changelog @@ -1,3 +1,13 @@ +hugs98 (98.200609.21-5.4) unstable; urgency=medium + + * Non-maintainer upload. + * Fix ftbfs with GCC-5: +apply patch from Elizabeth J Dall: +build with -std=gnu89 in debian/rules. +(Closes: #777903) + + -- gregor herrmann gre...@debian.org Sat, 18 Jul 2015 20:07:51 +0200 + hugs98 (98.200609.21-5.3) unstable; urgency=low * Non-maintainer upload. signature.asc Description: Digital Signature
Bug#778009: marked as done (mknbi: ftbfs with GCC-5)
Your message dated Sat, 18 Jul 2015 19:05:24 +
with message-id e1zgxqk-0006yf...@franck.debian.org
and subject line Bug#778009: fixed in mknbi 1.4.4-11
has caused the Debian Bug report #778009,
regarding mknbi: 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.)
--
778009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:mknbi
Version: 1.4.4-10
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/mknbi_1.4.4-10_unstable_gcc5.log
The last lines of the build log are at the end of this report.
To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t experimental install g++
Common build failures are C11 as the default C mode, new warnings
resulting in build failures with -Werror turned on, or new/dropped
symbols in Debian symbols files. For other C/C++ related build failures
see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html
[...]
^
In file included from string.h:2:0,
from first32.c:2:
linux-asm-string.h:274:22: note: expected 'const char *' but argument is of
type 'unsigned char *'
static inline size_t strlen(const char * s)
^
first32.c:552:36: warning: pointer targets in passing argument 1 of 'strlen'
differ in signedness [-Wpointer-sign]
i PARAMSIZE - 2 - strlen(params)) {
^
In file included from string.h:2:0,
from first32.c:2:
linux-asm-string.h:274:22: note: expected 'const char *' but argument is of
type 'unsigned char *'
static inline size_t strlen(const char * s)
^
gcc -I. -Os -ffreestanding -fstrength-reduce -fomit-frame-pointer
-fno-stack-protector -m32 -mcpu=i386 -Wall -W -Wno-format -Wno-unused
-DVERSION=\1.4.4\ -c memsizes.c
gcc: warning: '-mcpu=' is deprecated; use '-mtune=' or '-march=' instead
gcc -I. -Os -ffreestanding -fstrength-reduce -fomit-frame-pointer
-fno-stack-protector -m32 -mcpu=i386 -Wall -W -Wno-format -Wno-unused
-DVERSION=\1.4.4\ -c printf.c
gcc: warning: '-mcpu=' is deprecated; use '-mtune=' or '-march=' instead
gcc -I. -Os -ffreestanding -fstrength-reduce -fomit-frame-pointer
-fno-stack-protector -m32 -mcpu=i386 -Wall -W -Wno-format -Wno-unused
-DVERSION=\1.4.4\ -c string.c
gcc: warning: '-mcpu=' is deprecated; use '-mtune=' or '-march=' instead
gcc -E -DRELOC=0x92800 start32.S | as --32 -o start32@0x92800.o
ld -N -Ttext 0x92800 -e _start --oformat binary -m elf_i386 -o
first32@0x92800.linux start32@0x92800.o first32.o memsizes.o printf.o string.o
string.o: In function `__memcpy':
string.c:(.text+0x0): multiple definition of `__memcpy'
first32.o:first32.c:(.text+0x186): first defined here
string.o: In function `__constant_memcpy':
string.c:(.text+0x31): multiple definition of `__constant_memcpy'
first32.o:first32.c:(.text+0x1b7): first defined here
string.o: In function `memmove':
string.c:(.text+0x11b): multiple definition of `memmove'
first32.o:first32.c:(.text+0x2cc): first defined here
string.o: In function `__memset_generic':
string.c:(.text+0x142): multiple definition of `__memset_generic'
first32.o:first32.c:(.text+0x2f3): first defined here
string.o: In function `__constant_c_memset':
string.c:(.text+0x158): multiple definition of `__constant_c_memset'
first32.o:first32.c:(.text+0x309): first defined here
string.o: In function `__constant_c_and_count_memset':
string.c:(.text+0x189): multiple definition of `__constant_c_and_count_memset'
first32.o:first32.c:(.text+0x33a): first defined here
make[2]: *** [first32@0x92800.linux] Error 1
Makefile:93: recipe for target 'first32@0x92800.linux' failed
rm start32@0x92800.o
make[2]: Leaving directory '/«PKGBUILDDIR»'
make[1]: *** [override_dh_auto_build] Error 2
debian/rules:18: recipe for target 'override_dh_auto_build' failed
make[1]: Leaving directory
Bug#791850: marked as done (analog: FTBFS on sid due to unsatisfiable build-dependency on libgd2-(no)xpm-dev)
Your message dated Sat, 18 Jul 2015 19:04:32 + with message-id e1zgxpu-0006a2...@franck.debian.org and subject line Bug#791850: fixed in analog 2:6.0-21 has caused the Debian Bug report #791850, regarding analog: FTBFS on sid due to unsatisfiable build-dependency on libgd2-(no)xpm-dev 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.) -- 791850: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: analog Severity: serious Dear maintainer, your package analog ftbfs in current sid due to it Build-Depending on either libgd2-xpm-dev or libgd2-noxpm-dev with versioned restriction. The source package providing those packages dropped those transitive packages on libgd-dev in favour of a Provide, though a versioned dependecy won't be satisfy by a virtual package. Suggested action is swapping that build-dependency with one on libgd-dev, alternatively you can remove the version constraints and keep the old package name, though that's not suggested since they already were only transitive packages. Thanks for maintaining analog! -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: analog Source-Version: 2:6.0-21 We believe that the bug you reported is fixed in the latest version of analog, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 791...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann a...@debian.org (supplier of updated analog 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: Sat, 18 Jul 2015 20:43:25 +0200 Source: analog Binary: analog Architecture: source Version: 2:6.0-21 Distribution: unstable Urgency: medium Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Andreas Beckmann a...@debian.org Description: analog - web server log analyzer Closes: 618951 658779 674823 759872 788752 791850 Changes: analog (2:6.0-21) unstable; urgency=medium . * QA upload. * Build-Depend on libgd-dev. (Closes: #791850) * Fix FTBFS on HURD, thanks to Cyril Roelandt. (Closes: #674823) * debian/patches/02_windows_vista_7.patch: (Closes: #618951) (LP: #222813) add patch by Andrew Glen-Young to recognize Windows 7 and Vista. * Patch build system to allow the build date to be set externally, and set it to the latest debian/changelog entry for reproducibility. Thanks to Dhole. (Closes: #788752) * Ensure hardening flags are used during build. * Use source format 3.0 (quilt), stop using quilt directly. * Switch to debhelper compat level 9 and simplify d/rules. * Bump Standards-Version to 3.9.6. * Debconf translations: - Indonesian (id) by Mahyuddin Susanto. (Closes: #658779) - Turkish (tr) by Mert Dirik. (Closes: #759872) Checksums-Sha1: b20719658f032e7b43f72b23f85ca0c8cf984aa2 1887 analog_6.0-21.dsc 043d5def06bf99f37cba865c0d77afbd6879fecc 26992 analog_6.0-21.debian.tar.xz Checksums-Sha256: 4d8f95643c03cf052dc7dde807546c86cc9c1cddb8e1c9807f0efdee17809759 1887 analog_6.0-21.dsc e393724a564f7131b264d5e7e17cc2dda7f655cad3ad3cec2247f9ec2baa1fd9 26992 analog_6.0-21.debian.tar.xz Files: 5b8528af3924be326818bd6547277fd1 1887 web optional analog_6.0-21.dsc 0fb9a760f5c0d25caa78adac64d234bc 26992 web optional analog_6.0-21.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVqp7XAAoJEF+zP5NZ6e0IWLQP/3URThK/ROqiibfI+ObsFes3 tC9JpVKFGpdDei0H2WOR7nXnd6ai93TbotQxkRnYAwcYwstbmHAaqEmE63eM5GL6 SkcS8IXnerYjZOTMI0YdMOtQxpGIE/4LJRzoHUAWiiwZpjhNVS9vgccXL/wDjCPp RKwzWBc6ImQJtHWYoXabmHQp/C0JWYOzBnkpOe9iJ2QNDMZDblvkxaI6aMdFGQyz 7OTlTNfpd6mz7MftmDYTTrN9VQaBtkoc5Z5AbUT3haT+P0sE3gUgUVjRMj1hNZvH OcSDuNldSZ9KQnJG78oBpyRlvJFBtP7iEY7SbU12v/NpvNtACCjnMdGrpzI59zJt
Bug#778020: mz: diff for NMU version 0.40-1.1
Control: tags 778020 + pending
Dear maintainer,
I've prepared an NMU for mz (versioned as 0.40-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe
`- NP: U2: Mlk
diff -Nru mz-0.40/debian/changelog mz-0.40/debian/changelog
--- mz-0.40/debian/changelog 2010-07-07 22:34:52.0 +0200
+++ mz-0.40/debian/changelog 2015-07-18 21:18:33.0 +0200
@@ -1,3 +1,12 @@
+mz (0.40-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix ftbfs with GCC-5: add patch from Joshua Gadeken:
+Add -std=gnu89 to CMAKE_C_FLAGS in CMakeLists.txt.
+(Closes: #778020)
+
+ -- gregor herrmann gre...@debian.org Sat, 18 Jul 2015 21:18:03 +0200
+
mz (0.40-1) unstable; urgency=low
* New upstream version.
diff -Nru mz-0.40/debian/patches/gcc5.patch mz-0.40/debian/patches/gcc5.patch
--- mz-0.40/debian/patches/gcc5.patch 1970-01-01 01:00:00.0 +0100
+++ mz-0.40/debian/patches/gcc5.patch 2015-07-18 21:18:01.0 +0200
@@ -0,0 +1,18 @@
+Description: Resolve GCC5 build errors.
+ Add -std=gnu89 to CMAKE_C_FLAGS in CMakeLists.txt
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778020
+Author: Joshua Gadeken josh.gade...@hp.com
+Reviewed-by: gregor herrmann gre...@debian.org
+Last-Update: 2015-07-18
+
+--- a/CMakeLists.txt
b/CMakeLists.txt
+@@ -5,7 +5,7 @@
+ cmake_policy(SET CMP0003 NEW)
+ endif(COMMAND cmake_policy)
+
+-SET(CMAKE_C_FLAGS -Wall -pipe -fexceptions -fstack-protector --param=ssp-buffer-size=4 -fasynchronous-unwind-tables)
++SET(CMAKE_C_FLAGS -Wall -pipe -fexceptions -fstack-protector --param=ssp-buffer-size=4 -fasynchronous-unwind-tables -std=gnu89)
+
+ ADD_CUSTOM_TARGET(uninstall
+ COMMAND ${CMAKE_COMMAND} -E echo Use 'xargs rm install_manifest.txt' to uninstall this program
diff -Nru mz-0.40/debian/patches/series mz-0.40/debian/patches/series
--- mz-0.40/debian/patches/series 2010-07-07 22:34:52.0 +0200
+++ mz-0.40/debian/patches/series 2015-07-18 21:16:30.0 +0200
@@ -1 +1,2 @@
fix-spelling-error-in-binary.patch
+gcc5.patch
signature.asc
Description: Digital Signature
Processed: mz: diff for NMU version 0.40-1.1
Processing control commands: tags 778020 + pending Bug #778020 [src:mz] mz: ftbfs with GCC-5 Added tag(s) pending. -- 778020: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778020 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#792808: coreutils: CRC file checks not consistent
Package: coreutils Version: 8.23-4 Severity: grave Justification: renders package unusable Dear Maintainer, CRC checks on large files often return variable values. I have tried several different CRC check utilities, md5sum, md6sum, sha56sum, etc., and they all exhibit the same behavior. Multiple runs of the utility on a given file more often than not will return different values for many or all of the attempts. I have only noticed the effect on large files, but I cannot say with authority it only happens on large files. I noticed the effect when checking file integrity between identical files on two different systems. The backup server is running Squeeze, and checks on the files of that system are consistent, but when comparing the CRC between that system and the primary, which is running Jessie, the checks often failed. At first I of course thought this indicated file corruption on one server or the other, beut when I started investigating, I discovered sometimes the results were different on the two systems and sometimes the same. At that point I discovered it was only th! e machine running Jessie that was producing inconsistent results. At first I thought I was having problems with the file system (and indeed I am, as it happens), but when I copied one of the large files over to a different file system, the problem perissts. One is an XFS file system (the one having the problems) and the other is an Ext4 file system. Note this impacts a great many very important procedures and utilities, including my backup and compare strategy using rsync, file systems checks, etc. RAID-Server:/# sha256sum /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 b2e15ca178832e9f12a4823c583eefb2028cec9f7c45f36ea9dfa2297c904d6d /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 RAID-Server:/# sha256sum /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 eb3067b250d5d16e1d5d3f2b328001be91c4e5107a14e0010940acdab6584f2b /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 RAID-Server:/# sha256sum /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 6eddb4174b49e9bac741070559ad159acaa39a404a1b75c395d716910e5c81ef /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 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: sysvinit (via /sbin/init) Versions of packages coreutils depends on: ii libacl1 2.2.52-2 ii libattr1 1:2.4.47-2 ii libc62.19-18 ii libselinux1 2.3-2 coreutils recommends no packages. coreutils 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#778051: overgod: diff for NMU version 1.0-4.1
Control: tags 778051 + pending
Dear maintainer,
I've prepared an NMU for overgod (versioned as 1.0-4.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe
`- NP: J.J. Cale: After Midnight
diff -Nru overgod-1.0/debian/changelog overgod-1.0/debian/changelog
--- overgod-1.0/debian/changelog 2013-09-17 20:20:08.0 +0200
+++ overgod-1.0/debian/changelog 2015-07-18 21:31:20.0 +0200
@@ -1,3 +1,12 @@
+overgod (1.0-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix ftbfs with GCC-5: add patch from Nicholas Luedtke:
+add extern to inline functions.
+(Closes: #778051)
+
+ -- gregor herrmann gre...@debian.org Sat, 18 Jul 2015 21:31:19 +0200
+
overgod (1.0-4) unstable; urgency=low
* Team upload.
diff -Nru overgod-1.0/debian/patches/060_gcc5.patch overgod-1.0/debian/patches/060_gcc5.patch
--- overgod-1.0/debian/patches/060_gcc5.patch 1970-01-01 01:00:00.0 +0100
+++ overgod-1.0/debian/patches/060_gcc5.patch 2015-07-18 21:30:16.0 +0200
@@ -0,0 +1,33 @@
+Description: Fixed GCC5 build issue.
+ ADD extern to xpart and ypart functions
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778051
+Author: Nicholas Luedtke nicholas.lued...@hp.com
+Reviewed-by: gregor herrmann gre...@debian.org
+Last-Update: 2015-07-18
+
+--- a/stuff.c
b/stuff.c
+@@ -51,7 +51,6 @@
+ float cos_table [ANGLE_FULL];
+ float sin_table [ANGLE_FULL];
+
+-inline int xpart(int angle, int length);
+
+ void init_trig(void)
+ {
+@@ -66,13 +65,13 @@
+
+ }
+
+-inline int xpart(int angle, int length)
++extern inline int xpart(int angle, int length)
+ {
+ // return (lcos(angle) * length);// / ANGLE_FULL;
+ return (cos_table [angle 1023] * length);// / ANGLE_FULL;
+ }
+
+-inline int ypart(int angle, int length)
++extern inline int ypart(int angle, int length)
+ {
+ return (sin_table [angle 1023] * length);// / ANGLE_FULL;
+ }
diff -Nru overgod-1.0/debian/patches/series overgod-1.0/debian/patches/series
--- overgod-1.0/debian/patches/series 2013-09-17 20:20:08.0 +0200
+++ overgod-1.0/debian/patches/series 2015-07-18 21:28:13.0 +0200
@@ -3,3 +3,4 @@
030_security_build_warns.patch
040_fix_array_overrun.patch
050_fix_speaker_text.patch
+060_gcc5.patch
signature.asc
Description: Digital Signature
Processed: overgod: diff for NMU version 1.0-4.1
Processing control commands: tags 778051 + pending Bug #778051 [src:overgod] overgod: ftbfs with GCC-5 Added tag(s) pending. -- 778051: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778051 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#755963: clearsilver: diff for NMU version 0.10.5-1.5
Control: tags 755963 + pending Dear maintainer, I've prepared an NMU for clearsilver (versioned as 0.10.5-1.5) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Leonard Cohen: First We Take Manhattan diff -Nru clearsilver-0.10.5/debian/changelog clearsilver-0.10.5/debian/changelog --- clearsilver-0.10.5/debian/changelog 2014-08-02 17:51:15.0 +0200 +++ clearsilver-0.10.5/debian/changelog 2015-07-18 18:11:37.0 +0200 @@ -1,3 +1,12 @@ +clearsilver (0.10.5-1.5) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with clang instead of gcc and ftbfs with gcc5: +apply patch from Alexander sanek23...@gmail.com +(Closes: #755963) + + -- gregor herrmann gre...@debian.org Sat, 18 Jul 2015 18:11:32 +0200 + clearsilver (0.10.5-1.4) unstable; urgency=medium * Non-maintainer upload. diff -Nru clearsilver-0.10.5/debian/patches/clang-gcc5.patch clearsilver-0.10.5/debian/patches/clang-gcc5.patch --- clearsilver-0.10.5/debian/patches/clang-gcc5.patch 1970-01-01 01:00:00.0 +0100 +++ clearsilver-0.10.5/debian/patches/clang-gcc5.patch 2015-07-18 18:11:26.0 +0200 @@ -0,0 +1,28 @@ +Description: fix build with clang and gcc5 +Origin: vendor +Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755963 + https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777817 +Author: Alexander sanek23...@gmail.com +Reviewed-by: gregor herrmann gre...@debian.org +Last-Update: 2015-07-18 + +--- a/util/neo_err.h b/util/neo_err.h +@@ -85,7 +85,7 @@ + */ + #if defined(USE_C99_VARARG_MACROS) + #define nerr_raise(e,f,...) \ +- nerr_raisef(__PRETTY_FUNCTION__,__FILE__,__LINE__,e,f,__VA_ARGS__) ++ nerr_raisef(__PRETTY_FUNCTION__,__FILE__,__LINE__,e,f, ##__VA_ARGS__) + #elif defined(USE_GNUC_VARARG_MACROS) + #define nerr_raise(e,f,a...) \ +nerr_raisef(__PRETTY_FUNCTION__,__FILE__,__LINE__,e,f,##a) +@@ -99,7 +99,7 @@ + + #if defined(USE_C99_VARARG_MACROS) + #define nerr_raise_errno(e,f,...) \ +- nerr_raise_errnof(__PRETTY_FUNCTION__,__FILE__,__LINE__,e,f,__VA_ARGS__) ++ nerr_raise_errnof(__PRETTY_FUNCTION__,__FILE__,__LINE__,e,f, ##__VA_ARGS__) + #elif defined(USE_GNUC_VARARG_MACROS) + #define nerr_raise_errno(e,f,a...) \ +nerr_raise_errnof(__PRETTY_FUNCTION__,__FILE__,__LINE__,e,f,##a) diff -Nru clearsilver-0.10.5/debian/patches/series clearsilver-0.10.5/debian/patches/series --- clearsilver-0.10.5/debian/patches/series 2011-12-29 21:57:04.0 +0100 +++ clearsilver-0.10.5/debian/patches/series 2015-07-18 18:10:29.0 +0200 @@ -2,3 +2,4 @@ man_fixes.diff fix_64bit_crc_test.diff CVE-2011-4357.diff +clang-gcc5.patch signature.asc Description: Digital Signature
Bug#778176: Revised gcc-5 patch for x11-xserver-utils
On Sat, 7 Mar 2015 08:57:48 +0100, Julien Cristau wrote: I don't think that's an acceptable way to fix this. How about this? (This is a patch to be directly quilt imported, not a debdiff.) -- Daniel Schepler Index: x11-xserver-utils-7.7+4/sessreg/man/Makefile.am === --- x11-xserver-utils-7.7+4.orig/sessreg/man/Makefile.am +++ x11-xserver-utils-7.7+4/sessreg/man/Makefile.am @@ -10,7 +10,7 @@ SUFFIXES = .$(APP_MAN_SUFFIX) .man AM_CPPFLAGS = -I$(top_builddir) -I$(top_srcdir) filenames.sed: filenames.sed.c $(AM_V_GEN)$(CPP) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) \ - $(AM_CPPFLAGS) $(CPPFLAGS) $(srcdir)/filenames.sed.c | \ + $(AM_CPPFLAGS) $(CPPFLAGS) -P $(srcdir)/filenames.sed.c | \ $(SED) -n -e '/s|__/ p' -e '/^\/__/ p' $@ # String replacements in MAN_SUBSTS now come from xorg-macros.m4 via configure
Bug#777831: [Deborphan-devel] Bug#777831: deborphan: diff for NMU version 1.7.28.8-0.2
On Sat, 18 Jul 2015 18:33:59 +0200, David Prévot wrote: uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Feel free to reschedule it to DELAYED/0, I don’t expect any of the (wrongly) documented uploaders to vote against any (NM-)maintenance. Thanks, rescheduled. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Various Artists: West Coast of Clare signature.asc Description: Digital Signature
Processed: gnac: diff for NMU version 0.2.4-1.1
Processing control commands: tags 777880 + pending Bug #777880 [src:gnac] gnac: ftbfs with GCC-5 Added tag(s) pending. -- 777880: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777880 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#777881: gngb: diff for NMU version 20060309-3.1
Control: tags 777881 + pending
Dear maintainer,
I've prepared an NMU for gngb (versioned as 20060309-3.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe
`- NP: Bettina Wegner: Lied für meine verlassenen Freunde
diff -u gngb-20060309/debian/changelog gngb-20060309/debian/changelog
--- gngb-20060309/debian/changelog
+++ gngb-20060309/debian/changelog
@@ -1,3 +1,12 @@
+gngb (20060309-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix ftbfs with GCC-5: add patch from Greg Pearson: changed semantics of
+inline keyword.
+(Closes: #777881)
+
+ -- gregor herrmann gre...@debian.org Sat, 18 Jul 2015 19:01:39 +0200
+
gngb (20060309-3) unstable; urgency=low
* debian/control:
reverted:
--- gngb-20060309/.pc/.version
+++ gngb-20060309.orig/.pc/.version
@@ -1 +0,0 @@
-2
only in patch2:
unchanged:
--- gngb-20060309.orig/debian/patches/gngb_fcc5_fix.patch
+++ gngb-20060309/debian/patches/gngb_fcc5_fix.patch
@@ -0,0 +1,23 @@
+--- a/src/cpu.c 2015-07-07 17:13:40.761787869 +
b/src/cpu.c 2015-07-07 17:19:41.433800469 +
+@@ -2826,7 +2826,7 @@
+ }
+ }
+
+-__inline__ void cpu_run(void) {
++extern __inline__ void cpu_run(void) {
+ static Uint32 divid_cycle;
+ int v=0;
+ Uint8 a;
+diff -urN a/src/vram.c b/src/vram.c
+--- a/src/vram.c 2015-07-07 17:15:13.713791116 +
b/src/vram.c 2015-07-07 17:19:36.793800306 +
+@@ -242,7 +242,7 @@
+ conf.fs^=1;
+ }
+
+-__inline__ Uint8 get_nb_spr(void)
++extern __inline__ Uint8 get_nb_spr(void)
+ {
+ Uint8 *sp=oam_space;
+ Sint16 no_tile,x,y,att;
signature.asc
Description: Digital Signature
Processed: gngb: diff for NMU version 20060309-3.1
Processing control commands: tags 777881 + pending Bug #777881 [src:gngb] gngb: ftbfs with GCC-5 Added tag(s) pending. -- 777881: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777881 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#792773: marked as done (meta-kde: kde-full and kde-plasma-desktop are uninstallable)
Your message dated Sat, 18 Jul 2015 18:50:01 + with message-id e1zgxbr-0003bt...@franck.debian.org and subject line Bug#792773: fixed in meta-kde 5:86 has caused the Debian Bug report #792773, regarding meta-kde: kde-full and kde-plasma-desktop are uninstallable 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.) -- 792773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792773 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: meta-kde Version: 5:85 Severity: grave Justification: renders package unusable Hi, kde-plasma-desktop is currently uninstallable because it depends on plasma-desktop and kde-workspace which then in turn depends on kde-workspace-bin. But plasma-desktop conflicts with kde-workspace-bin and thus kde-plasma-desktop cannot be installed. As a result, kde-full cannot be installed either. Here is an overview of the situation on qa.debian.org/dose: https://qa.debian.org/dose/debcheck/unstable_main/1437109207/packages/kde-full.html Thanks! cheers, josch ---End Message--- ---BeginMessage--- Source: meta-kde Source-Version: 5:86 We believe that the bug you reported is fixed in the latest version of meta-kde, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 792...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Maximiliano Curia m...@debian.org (supplier of updated meta-kde 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: Sat, 18 Jul 2015 20:05:46 +0200 Source: meta-kde Binary: kde-plasma-desktop kde-standard kde-full kdeaccessibility kdeadmin kdeedu kdegames kdegraphics kdemultimedia kdenetwork kdesdk kdetoys kdeutils kde-sc-dev-latest kdegraphics-libs-data kdegraphics-strigi-plugins Architecture: source all amd64 Version: 5:86 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org Changed-By: Maximiliano Curia m...@debian.org Description: kde-full - complete KDE Software Compilation for end users kde-plasma-desktop - KDE Plasma Desktop and minimal set of applications kde-sc-dev-latest - ensure that the latest KDE Development Platform is installed kde-standard - KDE Plasma Desktop and standard set of applications kdeaccessibility - accessibility packages from the official KDE release kdeadmin - system administration tools from the official KDE release kdeedu - educational applications from the official KDE release kdegames - games from the official KDE release kdegraphics - graphics applications from the official KDE release kdegraphics-libs-data - transitional package for data files of various kdegraphics libs kdegraphics-strigi-plugins - transitional package for kdegraphics-related plugins kdemultimedia - multimedia applications from the official KDE release kdenetwork - networking applications from the official KDE release kdesdk - Software Development Kit from the official KDE release kdetoys- desktop toys from the official KDE release kdeutils - general-purpose utilities from the official KDE release Closes: 792318 792773 792775 Changes: meta-kde (5:86) unstable; urgency=medium . * Replace kde-workspace with plasma-workspace. (Closes: #792318, #792773, #792775) * Drop the metapackage kde-plasma-netbook. Checksums-Sha1: 9904d4bcf6477fb37ff6f1a3e911d2eef7092c0f 2719 meta-kde_86.dsc 1723ad90413c741213e0d9b3c8b833b94a243d60 13368 meta-kde_86.tar.xz d36f06dffa5c77c2d7be06a66cb322fed2844966 12572 kde-full_86_all.deb ffe09c6e936b4d797623635b464e42bbb70198e0 12494 kde-plasma-desktop_86_amd64.deb d9942888a89ba91143255827f18d9fa02ec673cb 12582 kde-sc-dev-latest_4.12+5.86_all.deb 19bbce1b069220de0b44236f1c40a041c1631c0c 12606 kde-standard_86_all.deb 1c260b3e7ff7a002075579896c4c5875f6d0d8e5 12546 kdeaccessibility_4.12+5.86_all.deb 71b5d191830686d726f090b701dd92c50a6d9fb5 12512 kdeadmin_4.12+5.86_all.deb 0f8654eb17c2b46d35ea07780f7115c19b0235ef 12590 kdeedu_4.12+5.86_all.deb ec949bbefab5708a704ff2281294b8489a77a5d1 12714 kdegames_4.12+5.86_all.deb 13c9d7769b9f812af55012fba10ac924bf4421c6 12256 kdegraphics-libs-data_4.12+5.86_all.deb
Bug#785088: marked as done (gyrus: still build-depends on libgnet-dev)
Your message dated Sat, 18 Jul 2015 15:36:16 + with message-id e1zgu9w-0003jo...@franck.debian.org and subject line Bug#785088: fixed in gyrus 0.3.10-3 has caused the Debian Bug report #785088, regarding gyrus: still build-depends on libgnet-dev 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.) -- 785088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gyrus Version: 0.3.10-1 Severity: important User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs gnet Your package stopped depending on libgnet, but it still build-depends on libgnet-dev. Please fix that. Emilio ---End Message--- ---BeginMessage--- Source: gyrus Source-Version: 0.3.10-3 We believe that the bug you reported is fixed in the latest version of gyrus, 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 785...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann a...@debian.org (supplier of updated gyrus 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: Sat, 18 Jul 2015 15:43:43 +0200 Source: gyrus Binary: gyrus Architecture: source Version: 0.3.10-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Andreas Beckmann a...@debian.org Description: gyrus - GNOME tool for Cyrus-IMAP servers administration Closes: 785088 Changes: gyrus (0.3.10-3) unstable; urgency=medium . * QA upload. * Drop unused B-D: libgnet-dev. (Closes: #785088) Checksums-Sha1: e77eafadeadb2916d058577df72a0f4de972c888 1759 gyrus_0.3.10-3.dsc 901cfbb19790e0df724cb227157a1916a3afd9cc 3344 gyrus_0.3.10-3.debian.tar.xz Checksums-Sha256: f5d8efcb817e1a9776d5e213ce3d6d4b3768b2472896166823eaf2ee376c6afb 1759 gyrus_0.3.10-3.dsc 3af8c4b85ec11f416d618de627f80817c2e6c5362e1da2dfb09e25cff94b7e9c 3344 gyrus_0.3.10-3.debian.tar.xz Files: 027b2aa233d63536f2016098fdaebafd 1759 mail optional gyrus_0.3.10-3.dsc b4834b5759039afc759a417b78fb409a 3344 mail optional gyrus_0.3.10-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVqloVAAoJEF+zP5NZ6e0IgYIP/1Yp+YYdAHJVJ+HoSmQShrqg X3i1SbZuduS2/rJb2ZC3wgdJ/eNx3pL8RdhsvfJGbBIeqCtulZruPeDsx3q52xUA 2sXxZTCc8Gp50pN8WIUxh4rzzckH6oqcPVy5cDmUgtqPMfUfsU7padqmi8ELU49k YSZZPdrWFEvXWfxqqHWzoNSTFds0KaW6t6Tnoz94wHURhhJzUy/P+pBVtXtTunoU lPtShEqD8xwDflenFGrJ/R6YVvv/0uChR/sKzfHxLlxyZ8l9F4sAIinvicrHkXXU +0cMHccUxcdq0AC5+VRqs04vZT6IVKEaI7RkVvWLU8axvvsBQicIAtOt7hK3vGCH mkBMtSszwB3R/Fj74FZ6MCWs4VvQjKjoXHkbzLWxI/C6w5qdFNq7YOSVyGxGKnPu MG1RLw2HrT6Y831iKkRB+4JXlMY2GEwBGfZFLbngEd4muYGl4cFZ2Q2rw6+6mxVF o0pKAYgSrmpfD8kbK/soA0jVtY1s/+4t9suex5W6M3mvZ2sUM+5TTXdx+9ID+UTv soa1R55wMqLOn6f0QRv0XkOQ0ZkTvworTnzUo1SNaitjVymDywtq53XqkzWur+Xe nvCKeEcyyaTJ+GB8VS92EaurVRJm6poTlNZP7xP6P2JHlkLZLJm90tk5ndvzwe1P wouGC/PRJcKo7jU+QYjh =g6k2 -END PGP SIGNATUREEnd Message---
Bug#778039: Patch for GCC 5 build issue
Package: src:oolite Followup-For: Bug #778039 Here's a fix for the GCC 5 build issue. I added -Wno-error=format-security I don't think that's the best way forward. Since this is security-relevant I think we should rather fix the problem than ignoring the errors. Fully agreed. However, thanks reporting The package successfully builds and links using GCC 5 with this change. because it shows that gcc-5 will not expose any other problem. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792808: coreutils: CRC file checks not consistent
The inconsistent results are restricted to the Jessie system? I'd run memtest given results like that. Well, what do you know? One of the memory sticks had a bunch of errors on it. I don't think debian configures coreutils --with-openssl so this should be independent: openssl md5 largefile I guess nothing is independent when one has bad memory. Thank you so much for pinpointing the issue, and so quickly, too! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784859: marked as done (Uninstallable in Sid: too strict version constraints)
Your message dated Sun, 19 Jul 2015 00:04:02 + with message-id e1zgc5k-0007i2...@franck.debian.org and subject line Bug#784859: fixed in ampache 3.6-rzb2752+dfsg-6 has caused the Debian Bug report #784859, regarding Uninstallable in Sid: too strict version constraints 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.) -- 784859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784859 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ampache-common Version: 3.6-rzb2752+dfsg-5 Severity: serious The version constraint for php-getid3 ( 1.9.8.0~) is too strict for no good reason. Since 1.9.9+dfsg-2 is in Sid, the package is not installable anymore. Maybe dh_linktree is not as useful as it looks. Regards David signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: ampache Source-Version: 3.6-rzb2752+dfsg-6 We believe that the bug you reported is fixed in the latest version of ampache, 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 784...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann a...@debian.org (supplier of updated ampache 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: Sat, 18 Jul 2015 23:05:29 +0200 Source: ampache Binary: ampache ampache-common Architecture: source all Version: 3.6-rzb2752+dfsg-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Andreas Beckmann a...@debian.org Description: ampache- web-based audio file management system ampache-common - web-based audio file management system common files Closes: 738217 781981 784859 Changes: ampache (3.6-rzb2752+dfsg-6) unstable; urgency=medium . * QA upload. * Rebuild against current versions of php-getid3, libphp-phpmailer. (Closes: #784859) * d/copyright: Fix syntax issues, drop obsolete sections. * Switch (Build-)Depends from ttf-freefont to fonts-freefont-ttf. (Closes: #738217) * Add alternative Suggests: virtual-mysql-server. (Closes: #781981) * Add lintian overrides for package-contains-broken-symlink caused by dh_linktree usage. * Update watch file. Checksums-Sha1: adde123b027dc7f620d3b90398c8f931e8a91dd9 1967 ampache_3.6-rzb2752+dfsg-6.dsc 7dbe75529cec56e143da8f4984dcc70f77d0e6ad 28096 ampache_3.6-rzb2752+dfsg-6.debian.tar.xz cfa20c23624e26315476119d9122e69e22ac5eff 784460 ampache-common_3.6-rzb2752+dfsg-6_all.deb fa58b5e10563ba4b4fc5a8f9b82a8b4c570aa68a 37232 ampache_3.6-rzb2752+dfsg-6_all.deb Checksums-Sha256: 3e87bacfcd5dde19dbd6d137d34e61f4a1cfaeb064d554ac40711f24dd1d7c07 1967 ampache_3.6-rzb2752+dfsg-6.dsc fb20699a0604df676bfe6173bd1e060b53a20c18fb13b1dbdadccacb58503d3e 28096 ampache_3.6-rzb2752+dfsg-6.debian.tar.xz 9f778b15795a582e8b342b1a0e79fb33348cc0d1845ddd8b9ac4d388b3851be2 784460 ampache-common_3.6-rzb2752+dfsg-6_all.deb 6a30027c2a6815f3253fab71c2db3a802e76c9dc0927ce2699c30489f6e17f19 37232 ampache_3.6-rzb2752+dfsg-6_all.deb Files: c75702d9b2d79b714896c2723b9a9e72 1967 web optional ampache_3.6-rzb2752+dfsg-6.dsc f65891233a9378ca1b5591d564faecb0 28096 web optional ampache_3.6-rzb2752+dfsg-6.debian.tar.xz 1daec613af0ecf7e3c13853120ade057 784460 web optional ampache-common_3.6-rzb2752+dfsg-6_all.deb 85ad5914221409b05a721ae53533b2e1 37232 web optional ampache_3.6-rzb2752+dfsg-6_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVquZuAAoJEF+zP5NZ6e0IbBkP/j0Qszl32qAu4XtyKorhA8bc xuK/1B8PBVj5alvVYeHhEj41iqH/VkXmaJ7UDaBXcUNpzN327jykky5C6txWSjKw cuQZzCONc0psKIbuWJdyVWEuV11mMOtx4+UdlbenZBjpFKbRL+villZfym8QUAqj xuIxzmHE7P66nKW2+XrBRUtWGmXtxkrW880S/S44l9dEHupChB4g9Q2lS6aVzon3 N1/cmL8PgJdH/0zwiuTQSyHXblxxIEgDcaD4ttspGRulqkcv9rAQiCI9CFbMqt7u LqK1V2NCirJaVxokdnO5n6vg7dt5au/fz5XGrixYDxKLGIQCGDwClQqIek5PPgYh 4tmM1MPH8doxXNnxT7m4jUpBjzAi0hV2hceRwOgPvOFwFKvEG85DkEKoc/t4p4Pb zphPxuqyCOJC06e/oCbk1DZdjfUa9FzxHQz8SPWyz7fmqQDSJUOqj5+3ab6RUOlZ xj1LLjKPpVjITDQeXXPckTqPRg85IBZNMlBT0JcZYqTNO4+GjxnW+F2MOq3vPbpj tK+L2o9fkEc0iVl39FaiKZXXELd3Khx1QvlUomhw4XR8GdIgrAEJy4W+Cq59qmkj FL8gb1kDnaDwzuP8+ShS3Hb+/gxmRrPOQ9L81FFarXxQjO55K3vFFFGSiHe/XMaQ
Processed: Close
Processing commands for cont...@bugs.debian.org: notfound 790043 mapnik/3.0.0~rc3+ds-1 Bug #790043 [python-mapnik] mapnik: no longer builds python bindings No longer marked as found in versions mapnik/3.0.0~rc3+ds-1. close 790043 Bug #790043 [python-mapnik] mapnik: no longer builds python bindings Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 790043: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790043 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#750274: marked as done (socks4-server: FTBFS: make[2]: *** No rule to make target '-lident', needed by 'sockd'. Stop.)
Your message dated Sun, 19 Jul 2015 00:48:59 + with message-id e1zgcmp-0006ke...@franck.debian.org and subject line Bug#750274: fixed in socks4-server 4.3.beta2-19 has caused the Debian Bug report #750274, regarding socks4-server: FTBFS: make[2]: *** No rule to make target '-lident', needed by 'sockd'. Stop. 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.) -- 750274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750274 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: socks4-server Version: 4.3.beta2-18 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140601 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[2]: Entering directory '/«PKGBUILDDIR»/sockd' /«PKGBUILDDIR»/sockd gcc -I../include -g -DLINUX -c -o sockd_ckcf.o sockd_ckcf.c gcc -I../include -g -DLINUX -c -o sockd_ckrt.o sockd_ckrt.c sockd_ckrt.c: In function 'sockd_ckrt': sockd_ckrt.c:24:2: warning: incompatible implicit declaration of built-in function 'exit' [enabled by default] exit(1); ^ gcc -I../include -g -DLINUX -c -o sockd_getspcmd.o sockd_getspcmd.c gcc -I../include -g -DLINUX -c -o sockd_fail.o sockd_fail.c sockd_fail.c: In function 'sockd_fail': sockd_fail.c:16:2: warning: incompatible implicit declaration of built-in function 'exit' [enabled by default] exit(1); ^ gcc -I../include -g -DLINUX -c -o setproctitle.o setproctitle.c gcc -I../include -g -DLINUX -c -o DoConnect.o DoConnect.c DoConnect.c: In function 'DoConnect': DoConnect.c:35:2: warning: incompatible implicit declaration of built-in function 'bzero' [enabled by default] bzero((char *)sin, sizeof(sin)); ^ gcc -I../include -g -DLINUX -c -o DoNewBind.o DoNewBind.c DoNewBind.c: In function 'DoNewBind': DoNewBind.c:50:2: warning: incompatible implicit declaration of built-in function 'bzero' [enabled by default] bzero((char *)sin, sizeof(sin)); ^ DoNewBind.c:139:4: warning: incompatible implicit declaration of built-in function 'exit' [enabled by default] exit(1); ^ gcc -I../include -g -DLINUX -DSOCKSIFIED_SOCKD -c -o RDoConnect.o DoConnect.c DoConnect.c: In function 'RDoConnect': DoConnect.c:35:2: warning: incompatible implicit declaration of built-in function 'bzero' [enabled by default] bzero((char *)sin, sizeof(sin)); ^ gcc -I../include -g -DLINUX -DSOCKSIFIED_SOCKD -c -o RDoNewBind.o DoNewBind.c DoNewBind.c: In function 'RDoNewBind': DoNewBind.c:50:2: warning: incompatible implicit declaration of built-in function 'bzero' [enabled by default] bzero((char *)sin, sizeof(sin)); ^ DoNewBind.c:76:2: warning: incompatible implicit declaration of built-in function 'strcpy' [enabled by default] strcpy(socks_srcsh.user, srcshp-user); ^ rm -f libsockd.a ar rc libsockd.a sockd_ckcf.o sockd_ckrt.o sockd_getspcmd.o sockd_fail.o setproctitle.o DoConnect.o DoNewBind.o RDoConnect.o RDoNewBind.o ranlib libsockd.a gcc -I../include -g -DLINUX -c -o sockd.o sockd.c sockd.c: In function 'readConfig': sockd.c:95:3: warning: incompatible implicit declaration of built-in function 'exit' [enabled by default] exit(1); ^ sockd.c:112:3: warning: incompatible implicit declaration of built-in function 'exit' [enabled by default] exit(1); ^ sockd.c: In function 'die': sockd.c:163:2: warning: incompatible implicit declaration of built-in function 'exit' [enabled by default] exit(1); ^ sockd.c: In function 'main': sockd.c:293:3: warning: incompatible implicit declaration of built-in function 'exit' [enabled by default] exit(1); ^ sockd.c:349:3: warning: incompatible implicit declaration of built-in function 'exit' [enabled by default] exit(1); ^ sockd.c:353:3: warning: incompatible implicit declaration of built-in function 'exit' [enabled by default] exit(1); ^ sockd.c:424:3: warning: incompatible implicit declaration of built-in function 'exit' [enabled by default] exit(1); ^ sockd.c:432:3: warning: incompatible implicit declaration of built-in function 'exit' [enabled by default] exit(1); ^ sockd.c:438:3: warning: incompatible implicit declaration of built-in function 'exit' [enabled by default] exit(1); ^ sockd.c:444:3: warning: incompatible implicit declaration of built-in function 'exit' [enabled by default] exit(1); ^
Bug#788742: marked as done (librdkafka: FTBFS: Unknown option disable-silent-rules)
Your message dated Sat, 18 Jul 2015 23:04:17 +
with message-id e1zgb9v-0005wu...@franck.debian.org
and subject line Bug#788742: fixed in librdkafka 0.8.6-1
has caused the Debian Bug report #788742,
regarding librdkafka: FTBFS: Unknown option disable-silent-rules
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.)
--
788742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: librdkafka
Version: 0.8.5-2
Severity: serious
From my pbuilder build log:
...
debian/rules build
dh build
dh_testdir
dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode
--disable-dependency-tracking
Unknown option disable-silent-rules
Usage: ./configure [OPTIONS...]
mklove configure script - mklove, not autoconf
Copyright (c) 2014 Magnus Edenhill - https://github.com/edenhill/mklove
Standard options:
--prefix=PATHInstall arch-independent files in PATH
[/usr/local]
--exec-prefix=PATH Install arch-dependent files in PATH
[$prefix]
--bindir=PATHUser executables [$exec_prefix/bin]
--sbindir=PATH System admin executables
[$exec_prefix/sbin]
--libexecdir=PATHProgram executables
[$exec_prefix/libexec]
--datadir=PATH Read-only arch-independent data
[$prefix/share]
--sysconfdir=PATHConfiguration data [$prefix/etc]
--sharedstatedir=PATHModifiable arch-independent data
[$prefix/com]
--localstatedir=PATH Modifiable local state data
[$prefix/var]
--libdir=PATHLibraries [$exec_prefix/lib]
--includedir=PATHC/C++ header files [$prefix/include]
--infodir=PATH Info documentation [$prefix/info]
--mandir=PATHManual pages [$prefix/man]
Configure tool options:
--list-modules List loaded mklove modules
--list-checksList checks
--fail-fatal All failures are fatal
--no-cache Dont use or generate config.cache
--debug Enable configure debugging
--clean Remove generated configure files
--reconfigureRerun configure with same arguments as
last run
--no-downloadDisable downloads of required mklove
modules
--update-modules Update modules from global repository
--repo-url=URL_OR_PATH Override mklove modules repo URL
[http://github.com/edenhill/mklove/raw/master]
--help Show configure usage
--program-prefix=PFX Program prefix
Compatibility options:
--enable-maintainer-mode Maintainer mode (no-op)
--disable-maintainer-modeMaintainer mode (no-op)
--disable-dependency-trackingDisable dependency tracking (no-op)
Cross-compilation options:
--host=HOST Configure to build programs to run on
HOST (no-op)
--build=BUILDConfigure for building on BUILD (no-op)
--target=TARGET Configure for building cross-toolkits
for platform TARGET (no-op)
Compiler options:
--cc=CC Build using C compiler CC [$CC]
--cxx=CXXBuild using C++ compiler CXX [$CXX]
--arch=ARCH Build for architecture [x86_64]
--cpu=CPUBuild and optimize for specific CPU
[generic]
--mbits=BITS Machine bits (32 or 64)
--CFLAGS=CFLAGS Add CFLAGS flags
--CPPFLAGS=CPPFLAGS Add CPPFLAGS flags
--CXXFLAGS=CXXFLAGS Add CXXFLAGS flags
--LDFLAGS=LDFLAGSAdd LDFLAGS flags
--ARFLAGS=ARFLAGSAdd ARFLAGS flags
--pkg-config-pathExtra paths for pkg-config
--enable-profiling Enable profiling
--enable-static Enable static linking
--disable-optimization Disable optimization
