Processed: notfound 832573 in 1:4.6.0-2, found 832573 in 4.6.0-2, tagging 832510
Processing commands for cont...@bugs.debian.org: > notfound 832573 1:4.6.0-2 Bug #832573 [iproute2] iproute uninstallable as it serves a file from another package (ifstat) There is no source info for the package 'iproute2' at version '1:4.6.0-2' with architecture '' Unable to make a source version for version '1:4.6.0-2' No longer marked as found in versions 1:4.6.0-2. > found 832573 4.6.0-2 Bug #832573 [iproute2] iproute uninstallable as it serves a file from another package (ifstat) Marked as found in versions iproute2/4.6.0-2. > tags 832510 + sid stretch Bug #832510 [src:skalibs] skalibs: FTBFS when built with dpkg-buildpackage -A (Missing build-indep target) Added tag(s) stretch and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 832510: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832510 832573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832573 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#832653: runit-systemd: fails to upgrade from 'testing' - trying to overwrite /lib/systemd/system/runit.service
Package: runit-systemd Version: 2.1.2-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package runit-systemd. Preparing to unpack .../runit-systemd_2.1.2-4_all.deb ... Unpacking runit-systemd (2.1.2-4) ... dpkg: error processing archive /var/cache/apt/archives/runit-systemd_2.1.2-4_all.deb (--unpack): trying to overwrite '/lib/systemd/system/runit.service', which is also in package runit 2.1.2-3 Errors were encountered while processing: /var/cache/apt/archives/runit-systemd_2.1.2-4_all.deb cheers, Andreas runit=2.1.2-3_runit-systemd=2.1.2-4.log.gz Description: application/gzip
Bug#832650: marked as done (systemd 230-7: boot fail panic abort due to wrong (outdated) Depends on libseccomp2, libidn11)
Your message dated Thu, 28 Jul 2016 08:38:40 +0200 with message-id <56d28cc5-a617-179d-4f00-3fd7ca251...@debian.org> and subject line Re: Bug#832650: systemd 230-7: boot fail panic abort due to wrong (outdated) Depends on libseccomp2, libidn11 has caused the Debian Bug report #832650, regarding systemd 230-7: boot fail panic abort due to wrong (outdated) Depends on libseccomp2, libidn11 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.) -- 832650: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 230-7 Severity: serious Justification: Debian Policy "3.5 Dependencies" (boot completely broken after upgrade [if init=/bin/systemd persisted], or annoyance) I just custom-upgraded (i.e., individual packages) to 230-7 and then tried manual (kernel cmdline) systemd activation via init=/bin/systemd . Was rather surprised to get the sufficiently well-known kernel init boot panic (see also related https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/init.txt), due to systemd being unable to reference libseccomp2.so.2 (and subsequently: libidn11.so.11). (sorry, no logs due to aborted boot-time output, and no camera at hand). Did an ldd on systemd, which showed references to /usr/... (i.e., PREFIX /usr), whereas at least this systemd version is now sitting at /bin (i.e., PREFIX /). Figured out that quite possibly libseccomp2 is woefully outdated. Upgraded libseccomp2, worked (but panic:ed at libidn11). Upgraded libidn11, successfully continued booting (albeit some "other unidentified issues", unfortunately). So, it strongly seems like Depends: of this systemd version is wrong (insufficient) since it definitely needs newer versions of libseccomp2, libidn11. And, to be precise, quite possibly it suffices to have a Depends: of the version value of these packages where they first had their PREFIX relocated from /usr to / (one could examine database contents of older packages to try to figure this out): # dpkg -L libidn11 /. /lib /lib/i386-linux-gnu /lib/i386-linux-gnu/libidn.so.11.6.15 /usr /usr/share /usr/share/doc /usr/share/doc/libidn11 /usr/share/doc/libidn11/changelog.Debian.gz /usr/share/doc/libidn11/changelog.gz /usr/share/doc/libidn11/copyright /lib/i386-linux-gnu/libidn.so.11 (these possibly lower-than-here version values may or may not be sufficient, depending on whether additional library features other than the PREFIX relocation are required by systemd) To be precise, here I am now at dpkg -l|egrep "libseccomp2|libidn11" ii libidn11:i3861.32-3.1 i386 GNU Libidn library, implementation of IETF IDN specifications ii libseccomp2:i386 2.3.1-2 i386 high level interface to Linux seccomp filter which are version values that are modern enough to be booting here, yet where certain older package versions might already be compatible as well. /var/log/dpkg.log: 2016-07-28 07:22:56 startup archives unpack 2016-07-28 07:23:02 upgrade joystick:i386 1:1.4.8-1 1:1.5.1-2 2016-07-28 07:23:02 status half-configured joystick:i386 1:1.4.8-1 2016-07-28 07:23:02 status unpacked joystick:i386 1:1.4.8-1 2016-07-28 07:23:02 status half-installed joystick:i386 1:1.4.8-1 2016-07-28 07:23:03 status triggers-pending man-db:i386 2.7.5-1 2016-07-28 07:23:03 status half-installed joystick:i386 1:1.4.8-1 2016-07-28 07:23:04 status unpacked joystick:i386 1:1.5.1-2 2016-07-28 07:23:04 status unpacked joystick:i386 1:1.5.1-2 2016-07-28 07:23:04 upgrade usb-modeswitch:i386 2.2.5+repack0-1 2.4.0+repack0-1 2016-07-28 07:23:04 status half-configured usb-modeswitch:i386 2.2.5+repack0-1 2016-07-28 07:23:04 status unpacked usb-modeswitch:i386 2.2.5+repack0-1 2016-07-28 07:23:04 status half-installed usb-modeswitch:i386 2.2.5+repack0-1 2016-07-28 07:23:05 status half-installed usb-modeswitch:i386 2.2.5+repack0-1 2016-07-28 07:23:05 status unpacked usb-modeswitch:i386 2.4.0+repack0-1 2016-07-28 07:23:05 status unpacked usb-modeswitch:i386 2.4.0+repack0-1 2016-07-28 07:23:06 upgrade udev:i386 215-18 230-7 2016-07-28 07:23:06 status half-configured udev:i386 215-18 2016-07-28 07:23:06 status unpacked udev:i386 215-18 2016-07-28 07:23:06 status half-installed udev:i386 215-18 2016-07-28 07:23:08 status triggers-pending systemd:i386 228-4 2016-07-28 07:23:10 status half-installed udev:i386 215-18 2016-07-28 07:23:10 status unpacked udev:i386 230-7 2016-07-28 07:23:10 status unpacked udev:i386 230-7 2016-07-28 07:23:10 upgrade libudev1:i386 215-18
Bug#832650: systemd 230-7: boot fail panic abort due to wrong (outdated) Depends on libseccomp2, libidn11
Package: systemd Version: 230-7 Severity: serious Justification: Debian Policy "3.5 Dependencies" (boot completely broken after upgrade [if init=/bin/systemd persisted], or annoyance) I just custom-upgraded (i.e., individual packages) to 230-7 and then tried manual (kernel cmdline) systemd activation via init=/bin/systemd . Was rather surprised to get the sufficiently well-known kernel init boot panic (see also related https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/init.txt), due to systemd being unable to reference libseccomp2.so.2 (and subsequently: libidn11.so.11). (sorry, no logs due to aborted boot-time output, and no camera at hand). Did an ldd on systemd, which showed references to /usr/... (i.e., PREFIX /usr), whereas at least this systemd version is now sitting at /bin (i.e., PREFIX /). Figured out that quite possibly libseccomp2 is woefully outdated. Upgraded libseccomp2, worked (but panic:ed at libidn11). Upgraded libidn11, successfully continued booting (albeit some "other unidentified issues", unfortunately). So, it strongly seems like Depends: of this systemd version is wrong (insufficient) since it definitely needs newer versions of libseccomp2, libidn11. And, to be precise, quite possibly it suffices to have a Depends: of the version value of these packages where they first had their PREFIX relocated from /usr to / (one could examine database contents of older packages to try to figure this out): # dpkg -L libidn11 /. /lib /lib/i386-linux-gnu /lib/i386-linux-gnu/libidn.so.11.6.15 /usr /usr/share /usr/share/doc /usr/share/doc/libidn11 /usr/share/doc/libidn11/changelog.Debian.gz /usr/share/doc/libidn11/changelog.gz /usr/share/doc/libidn11/copyright /lib/i386-linux-gnu/libidn.so.11 (these possibly lower-than-here version values may or may not be sufficient, depending on whether additional library features other than the PREFIX relocation are required by systemd) To be precise, here I am now at dpkg -l|egrep "libseccomp2|libidn11" ii libidn11:i3861.32-3.1 i386 GNU Libidn library, implementation of IETF IDN specifications ii libseccomp2:i386 2.3.1-2 i386 high level interface to Linux seccomp filter which are version values that are modern enough to be booting here, yet where certain older package versions might already be compatible as well. /var/log/dpkg.log: 2016-07-28 07:22:56 startup archives unpack 2016-07-28 07:23:02 upgrade joystick:i386 1:1.4.8-1 1:1.5.1-2 2016-07-28 07:23:02 status half-configured joystick:i386 1:1.4.8-1 2016-07-28 07:23:02 status unpacked joystick:i386 1:1.4.8-1 2016-07-28 07:23:02 status half-installed joystick:i386 1:1.4.8-1 2016-07-28 07:23:03 status triggers-pending man-db:i386 2.7.5-1 2016-07-28 07:23:03 status half-installed joystick:i386 1:1.4.8-1 2016-07-28 07:23:04 status unpacked joystick:i386 1:1.5.1-2 2016-07-28 07:23:04 status unpacked joystick:i386 1:1.5.1-2 2016-07-28 07:23:04 upgrade usb-modeswitch:i386 2.2.5+repack0-1 2.4.0+repack0-1 2016-07-28 07:23:04 status half-configured usb-modeswitch:i386 2.2.5+repack0-1 2016-07-28 07:23:04 status unpacked usb-modeswitch:i386 2.2.5+repack0-1 2016-07-28 07:23:04 status half-installed usb-modeswitch:i386 2.2.5+repack0-1 2016-07-28 07:23:05 status half-installed usb-modeswitch:i386 2.2.5+repack0-1 2016-07-28 07:23:05 status unpacked usb-modeswitch:i386 2.4.0+repack0-1 2016-07-28 07:23:05 status unpacked usb-modeswitch:i386 2.4.0+repack0-1 2016-07-28 07:23:06 upgrade udev:i386 215-18 230-7 2016-07-28 07:23:06 status half-configured udev:i386 215-18 2016-07-28 07:23:06 status unpacked udev:i386 215-18 2016-07-28 07:23:06 status half-installed udev:i386 215-18 2016-07-28 07:23:08 status triggers-pending systemd:i386 228-4 2016-07-28 07:23:10 status half-installed udev:i386 215-18 2016-07-28 07:23:10 status unpacked udev:i386 230-7 2016-07-28 07:23:10 status unpacked udev:i386 230-7 2016-07-28 07:23:10 upgrade libudev1:i386 215-18 230-7 2016-07-28 07:23:11 status triggers-pending libc-bin:i386 2.23-2 2016-07-28 07:23:11 status half-configured libudev1:i386 215-18 2016-07-28 07:23:11 status unpacked libudev1:i386 215-18 2016-07-28 07:23:11 status half-installed libudev1:i386 215-18 2016-07-28 07:23:11 status half-installed libudev1:i386 215-18 2016-07-28 07:23:11 status unpacked libudev1:i386 230-7 2016-07-28 07:23:11 status unpacked libudev1:i386 230-7 2016-07-28 07:23:11 trigproc man-db:i386 2.7.5-1 2016-07-28 07:23:11 status half-configured man-db:i386 2.7.5-1 2016-07-28 07:23:19 status installed man-db:i386 2.7.5-1 2016-07-28 07:23:19 trigproc systemd:i386 228-4 2016-07-28 07:23:19 status half-configured systemd:i386 228-4 2016-07-28 07:23:19 status installed systemd:i386 228-4 2016-07-28 07:23:19 trigproc libc-bin:i386 2.23-2 2016-07-28 07:23:19 status half-configured libc-bin:i386 2.23-2 2016-07-28 07:23:21 status installed libc-bin:i386 2.23-2 2016-07-28 07:23:22 startup packages con
Bug#832649: multi-display is broken (menu and panel appears only on external display)
package: systemsettings version: 4:5.7.0-1 severity: grave I have connected an HDMI monitor to my laptop and the menu and panel appears on the HDMI monitor, but when I remove the HDMI cable, the menu and panel does not appear on the laptop screen. I have to use run command and alt tab as a fallback. But I miss notifications, especially the power status and network status. kwin_x11 is the window manager. signature.asc Description: OpenPGP digital signature
Bug#832645: marked as done (jflex: FTBFS: build.xml:119: taskdef class JFlex.anttask.JFlexTask cannot be found)
Your message dated Thu, 28 Jul 2016 04:52:13 + with message-id and subject line Bug#832645: fixed in jflex 1.6.1-2 has caused the Debian Bug report #832645, regarding jflex: FTBFS: build.xml:119: taskdef class JFlex.anttask.JFlexTask cannot be 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.) -- 832645: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832645 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jflex Version: 1.6.1-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, jflex fails to build from source in unstable/amd64: [..] update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javah to provide /usr/bin/javah (javah) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstack to provide /usr/bin/jstack (jstack) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jrunscript to provide /usr/bin/jrunscript (jrunscript) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javac to provide /usr/bin/javac (javac) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jhat to provide /usr/bin/jhat (jhat) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javap to provide /usr/bin/javap (javap) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jar to provide /usr/bin/jar (jar) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/xjc to provide /usr/bin/xjc (xjc) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/schemagen to provide /usr/bin/schemagen (schemagen) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jps to provide /usr/bin/jps (jps) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/extcheck to provide /usr/bin/extcheck (extcheck) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jmap to provide /usr/bin/jmap (jmap) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstatd to provide /usr/bin/jstatd (jstatd) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jdb to provide /usr/bin/jdb (jdb) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/serialver to provide /usr/bin/serialver (serialver) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/wsgen to provide /usr/bin/wsgen (wsgen) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jcmd to provide /usr/bin/jcmd (jcmd) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jarsigner to provide /usr/bin/jarsigner (jarsigner) in auto mode Setting up openjdk-8-jre:amd64 (8u102-b14-2) ... update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/policytool to provide /usr/bin/policytool (policytool) in auto mode Setting up ant (1.9.7-3) ... Setting up maven-repo-helper (1.9.2) ... Setting up jflex (1.6.1-1) ... Setting up default-jre-headless (2:1.8-57) ... Setting up default-jdk-headless (2:1.8-57) ... Setting up openjdk-8-jdk:amd64 (8u102-b14-2) ... update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/appletviewer to provide /usr/bin/appletviewer (appletviewer) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jconsole to provide /usr/bin/jconsole (jconsole) in auto mode Setting up default-jre (2:1.8-57) ... Setting up default-jdk (2:1.8-57) ... Setting up jflex-build-deps (1.6.1-1) ... Processing triggers for libc-bin (2.23-4) ... Processing triggers for systemd (231-1) ... Processing triggers for ca-certificates (20160104) ... Updating certificates in /etc/ssl/certs... 173 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... Adding debian:ACCVRAIZ1.pem Adding debian:ACEDICOM_Root.pem Adding debian:AC_Raíz_Certicámara_S.A..pem Adding debian:Actalis_Authentication_Root_CA.pem Adding debian:AddTrust_External_Root.pem Adding debian:AddTrust_Low-Value_Services_Root.pem Adding debian:AddTrust_Public_Services_Root.pem Adding debian:AddTrust_Qualified_Certificates_Root.pem Adding debian:AffirmTrust_Commercial.pem Adding debian:AffirmTrust_Networking.pem Adding debian:AffirmTrust_Premium.pem Adding debian:AffirmTrust_Premiu
Bug#830300: RE: Bug#830300: bug in mdadm
I will give it a try in 5 days (currently I am away from the machine and don't want to experiment if it can boot or not with the new conig) and will report back. Thanks for the suggestion. - Цитат от Michael Biebl (bi...@debian.org), на 26.07.2016 в 15:36 - > On Sat, 9 Jul 2016 19:47:07 +0300 > =?utf-8?B?0JvRjtCx0LXQvSDQmtCw0YDQsNCy0LXQu9C+0LI=?= > wrote: >> Hi, >> >> The problem I am trying to solve is that my laptop (ASUS Zenbook UX301LAA) >> is using Intel RAID0 setup: >> >> 00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller >> [RAID mode] (rev 04) >> >> But it stopped working 5-6 months ago (3.3.2-5 was the last version that was >> working out of the box). My understanding is that for some reason mdadm is >> not recognizing the setup as being a IMSM RAID and I was forcing the RAID >> assembly to bypass this check with the envvars until this was also broken by >> the last mdadm update. >> >> BTW, I also tried another workaround but it does not work also for me with >> the last debian mdadm package: >> https://bbs.archlinux.org/viewtopic.php?id=202597 >> >> For the moment I downgraded the mdadm and put it on hold. >> >> Any other suggestions are welcome. >> > > You mentioned you tried the workaround from the arch forum, I suspect > you meant https://bbs.archlinux.org/viewtopic.php?pid=1565988#p1565988 > specifically. > Keep in mind, that you need to rebuild the initramfs (via > update-initramfs -u) after changing the udev rule. > > > # lsinitramfs /boot/initrd.img-$(uname -r) | grep env > shows that the initramfs installs the env utility under /bin/env and not > /usr/bin/env. So this would need to be considered when changing > 64-md-raid-assembly.rules. > > Maybe it's better to use --force instead, as upstream suggests. > The attached rules files should do that (please double check). > Please copy that to /etc/udev/rules.d/, update your initramfs via > update-initramfs -u and try again. > > Regards, > Michael > > > > *) It's usually also better to copy the file to /etc/udev/rules.d/ and > edit it there, so the file is not overwritten on upgrades. > > > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? -- Luben Karavelov
Bug#832638: marked as done (evolver: FTBFS on architectures not supported by libquadmath0)
Your message dated Thu, 28 Jul 2016 04:19:16 + with message-id and subject line Bug#832638: fixed in evolver 2.70+ds-2 has caused the Debian Bug report #832638, regarding evolver: FTBFS on architectures not supported by libquadmath0 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.) -- 832638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: evolver Version: 2.70+ds-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Evolver enthusiasts, it appears that the quadruple floating point format is not supported on all architectures: in its present form, the evolver package cannot build on these architectures. A workaround is on its way. Thanks, Jerome -- System Information: Debian Release: Jessie* APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.7-ckt20-0001-mbp62 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages evolver depends on: ii evolver-nox 2.70+ds-1 ii evolver-ogl 2.70+ds-1 evolver recommends no packages. evolver suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: evolver Source-Version: 2.70+ds-2 We believe that the bug you reported is fixed in the latest version of evolver, 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 832...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jerome Benoit (supplier of updated evolver package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 28 Jul 2016 00:43:59 + Source: evolver Binary: evolver evolver-nox evolver-ogl evolver-doc Architecture: source Version: 2.70+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Jerome Benoit Description: evolver- Surface Evolver evolver-doc - Surface Evolver - doc evolver-nox - Surface Evolver - with no X support evolver-ogl - Surface Evolver - with OpenGL display Closes: 832538 832540 832638 Changes: evolver (2.70+ds-2) unstable; urgency=medium . * FTBFS fixes release: - disable PROFILING on i386 architectures (Closes: #832538); - isolate architectures without sysinfo function (Closes: #832540); - manage quadruple floating point format support (Closes: #832638). * Debianization: - debian/patches/: - d/p/upstream-source-C2help2man.patch, slightly revisit. Checksums-Sha1: 889325dd30b9c977e41289f8ad29fa5fbd97 2969 evolver_2.70+ds-2.dsc ceadf879fbfb8d34274dfe265ae1704be3cafde0 2342100 evolver_2.70+ds.orig.tar.xz 160f199fbd8ce3718dfc2cba08a9d287ac3c1d34 26676 evolver_2.70+ds-2.debian.tar.xz Checksums-Sha256: 0180fd00cc6c5174aedd3f7b6f096343624d92a698e9fbdbd89ca43cd3273f4e 2969 evolver_2.70+ds-2.dsc a27320a34cea5adf83de5d95b300cc2b4c68c9cb74a8fb75a82cee20650fca5f 2342100 evolver_2.70+ds.orig.tar.xz 7f6d5485365111665b5ce67efb235cfb864e29d5b0ab132e9c232ea475d97176 26676 evolver_2.70+ds-2.debian.tar.xz Files: 26f9d2dce80c5ee4deff8b987fbe83b2 2969 math extra evolver_2.70+ds-2.dsc 01fa2a07b6870fca213321cc740f3bb1 2342100 math extra evolver_2.70+ds.orig.tar.xz 5fb4d12c4890fa4921c8c9c0e7dc8434 26676 math extra evolver_2.70+ds-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQQcBAEBCgAGBQJXmV8fAAoJED+SGaZ/NsaL0t0f/jkQGBGO9ScGmjeJFpbKcB7S YbGgpzD1X20LOZ6cG2O2iSXbO//rWaB754v3wuJiQmDvmfD2WDVIsqFT5Ayu2i1c w+fpyhP1xwSsU4M7YFwByZngmo+h8e7pzrTxWUXbYJLJ4euBTkz6ML6/Tu7o0AUI STCRNJ3+nzXRd3GLjla/T8GqI6sHMcFm+UGuL3zvA3qMM49k4+SFPNhdyhPP/K2Z TOr0icMdP68gy6XKs8cNAMnAgDWfWkqPY6mRBEeJY6AJp70JwjK2wRLNNNcp263s UkXJAm3pCrw03XI7guHWcVjD9+KA/rkXIVtTHA3aYXMjPbOfz80PSql2yWvKhygD V86ck84AvPBVJnoPAWw+Ik6YtBYVFuvdBK3igGUofhR/1oP8AYIWsjs7yURMCNEJ UPtvHpmumszsU8y7H5a0Nai9CnWYQ2GYAAGa4bCcZcY4FUn5DLS5c0HAuW29IH4y 7Yxksvql4TndQ/cTRafFHso0vBwbmX9BuNITdmtExactRcvpPirxFVlRfqoxaDiU 981wZMz3Pmu1pjgVq+gPaYctggvCVzoMb9qomSEM8kMzr6HESqIuwEmnzen3W7WD i
Bug#832449: marked as done (jed: FTBFS on arm64: machine `aarch64' not recognized)
Your message dated Thu, 28 Jul 2016 04:19:27 +
with message-id
and subject line Bug#832449: fixed in jed 1:0.99.19-6
has caused the Debian Bug report #832449,
regarding jed: FTBFS on arm64: machine `aarch64' not recognized
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.)
--
832449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jed
Version: 1:0.99.19-5
Severity: serious
Tags: patch
The latest version of jed FTBFS on arm64[1] because config.sub is too
old:
,
| checking build system type... Invalid configuration `aarch64-linux-gnu':
machine `aarch64' not recognized
| configure: error: /bin/bash autoconf/config.sub aarch64-linux-gnu failed
`
This should be fixed by replacing config.{sub,guess} with the files from
autotools-dev at build time. I have attached a possible patch which
does that via dh_update_autotools_config (included in debhelper since
version 9.20160114), but since I don't have an arm64 system, it's not
really tested.
Alternatively, dh_autotools-dev_updateconfig and
dh_autotools-dev_restoreconfig could be used (you should build-depend on
autotools-dev then).
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 4.6.4-nouveau (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
1.
https://buildd.debian.org/status/fetch.php?pkg=jed&arch=arm64&ver=1%3A0.99.19-5&stamp=1469420374
diff -Nru jed-0.99.19/debian/control jed-0.99.19/debian/control
--- jed-0.99.19/debian/control 2016-07-25 03:15:10.0 +0200
+++ jed-0.99.19/debian/control 2016-07-25 10:07:00.0 +0200
@@ -4,7 +4,7 @@
Maintainer: Wookey
Standards-Version: 3.9.8
Build-Depends-Indep: hevea
-Build-Depends: debhelper (>= 7), dh-autoreconf,
+Build-Depends: debhelper (>= 9.20160114), dh-autoreconf,
libxft-dev, libgpm-dev [linux-any],
libxt-dev, pkg-config, autotools-dev, slsh,
libslang2-dev, chrpath
diff -Nru jed-0.99.19/debian/rules jed-0.99.19/debian/rules
--- jed-0.99.19/debian/rules 2016-07-25 01:22:06.0 +0200
+++ jed-0.99.19/debian/rules 2016-07-25 10:09:01.0 +0200
@@ -53,12 +53,14 @@
clean:
dh_testdir
dh_autoreconf_clean
+ dh_update_autotools_config
dh_clean
[ ! -f Makefile ] || $(MAKE) distclean
rm -f build-stamp
config.status:
dh_testdir
+ dh_update_autotools_config
dh_autoreconf
./configure $(configure_flags) || \
{ rc=$$?; cat config.log; exit $$rc; }
--- End Message ---
--- Begin Message ---
Source: jed
Source-Version: 1:0.99.19-6
We believe that the bug you reported is fixed in the latest version of
jed, 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 832...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Wookey (supplier of updated jed 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: Wed, 27 Jul 2016 04:24:03 +0100
Source: jed
Binary: jed xjed jed-common
Architecture: source all amd64
Version: 1:0.99.19-6
Distribution: unstable
Urgency: medium
Maintainer: Wookey
Changed-By: Wookey
Description:
jed- editor for programmers (textmode version)
jed-common - S-Lang runtime files for jed and xjed
xjed - editor for programmers (x11 version)
Closes: 804083 832449 832450
Changes:
jed (1:0.99.19-6) unstable; urgency=medium
.
* Actually update config.{sub,guess} (Closes: # 832449)
* Correct setting of Multiarch dir (Closes: #832450)
* Solve termcap build issue (Closes: #804083)
* Remove dh-autoreconf for now as it needs more work
Checksums-Sha1:
4985d3f336c65d31155174c18cecde0bfd781b25 2021 jed_0.99.19-6.dsc
831216a831ef9b1a5fddf978697fadb7adcd1669 30356 jed_0.99.19-6.debian.tar.xz
d68cc2641f7797bff31b322518d9ea69139eb50d 444524 jed-common_0.99.19-6_all.deb
291314ea8ebc77a68df82db2e92085b151b0625b 270020 jed-dbgsym_0.99.19-6_amd64.deb
cdad5ecbd29e9e3ec8ee0a9cac37dd41cb4cded7 125514 jed_0.99.19-6_amd64.deb
5801fe3350ddb27275bf289
Bug#832645: jflex: FTBFS: build.xml:119: taskdef class JFlex.anttask.JFlexTask cannot be found
> Perhaps you should give us a little more time to fix the fallout, > especially when we do a (mini) transition and you see a lot of broken > Java packages popping up. I only saw a couple and did not notice an obvious trend, otherwise I would naturally have not reported. :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Processed: Re: Bug#832645: jflex: FTBFS: build.xml:119: taskdef class JFlex.anttask.JFlexTask cannot be found
Processing control commands: > tags -1 confirmed pending Bug #832645 [src:jflex] jflex: FTBFS: build.xml:119: taskdef class JFlex.anttask.JFlexTask cannot be found Added tag(s) confirmed and pending. -- 832645: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832645 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#832645: jflex: FTBFS: build.xml:119: taskdef class JFlex.anttask.JFlexTask cannot be found
Control: tags -1 confirmed pending On 28.07.2016 05:47, Chris Lamb wrote: > Source: jflex > Version: 1.6.1-1 > Severity: serious > Justification: fails to build from source > User: reproducible-bui...@lists.alioth.debian.org > Usertags: ftbfs > X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org > > Dear Maintainer, > > jflex fails to build from source in unstable/amd64: Hi, you are too quick Chris. :) Perhaps you should give us a little more time to fix the fallout, especially when we do a (mini) transition and you see a lot of broken Java packages popping up. I suppose 48 hours would be a reasonable time frame. That could save you some bug reporting time as well. Cheers, Markus signature.asc Description: OpenPGP digital signature
Bug#832645: jflex: FTBFS: build.xml:119: taskdef class JFlex.anttask.JFlexTask cannot be found
Source: jflex Version: 1.6.1-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, jflex fails to build from source in unstable/amd64: [..] update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javah to provide /usr/bin/javah (javah) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstack to provide /usr/bin/jstack (jstack) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jrunscript to provide /usr/bin/jrunscript (jrunscript) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javac to provide /usr/bin/javac (javac) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jhat to provide /usr/bin/jhat (jhat) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javap to provide /usr/bin/javap (javap) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jar to provide /usr/bin/jar (jar) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/xjc to provide /usr/bin/xjc (xjc) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/schemagen to provide /usr/bin/schemagen (schemagen) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jps to provide /usr/bin/jps (jps) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/extcheck to provide /usr/bin/extcheck (extcheck) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jmap to provide /usr/bin/jmap (jmap) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstatd to provide /usr/bin/jstatd (jstatd) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jdb to provide /usr/bin/jdb (jdb) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/serialver to provide /usr/bin/serialver (serialver) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/wsgen to provide /usr/bin/wsgen (wsgen) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jcmd to provide /usr/bin/jcmd (jcmd) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jarsigner to provide /usr/bin/jarsigner (jarsigner) in auto mode Setting up openjdk-8-jre:amd64 (8u102-b14-2) ... update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/policytool to provide /usr/bin/policytool (policytool) in auto mode Setting up ant (1.9.7-3) ... Setting up maven-repo-helper (1.9.2) ... Setting up jflex (1.6.1-1) ... Setting up default-jre-headless (2:1.8-57) ... Setting up default-jdk-headless (2:1.8-57) ... Setting up openjdk-8-jdk:amd64 (8u102-b14-2) ... update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/appletviewer to provide /usr/bin/appletviewer (appletviewer) in auto mode update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jconsole to provide /usr/bin/jconsole (jconsole) in auto mode Setting up default-jre (2:1.8-57) ... Setting up default-jdk (2:1.8-57) ... Setting up jflex-build-deps (1.6.1-1) ... Processing triggers for libc-bin (2.23-4) ... Processing triggers for systemd (231-1) ... Processing triggers for ca-certificates (20160104) ... Updating certificates in /etc/ssl/certs... 173 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... Adding debian:ACCVRAIZ1.pem Adding debian:ACEDICOM_Root.pem Adding debian:AC_Raíz_Certicámara_S.A..pem Adding debian:Actalis_Authentication_Root_CA.pem Adding debian:AddTrust_External_Root.pem Adding debian:AddTrust_Low-Value_Services_Root.pem Adding debian:AddTrust_Public_Services_Root.pem Adding debian:AddTrust_Qualified_Certificates_Root.pem Adding debian:AffirmTrust_Commercial.pem Adding debian:AffirmTrust_Networking.pem Adding debian:AffirmTrust_Premium.pem Adding debian:AffirmTrust_Premium_ECC.pem Adding debian:ApplicationCA_-_Japanese_Government.pem Adding debian:Atos_TrustedRoot_2011.pem Adding debian:Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.pem Adding debian:Baltimore_CyberTrust_Root.pem Adding debian:Buypass_Class_2_CA_1.pem Adding debian:Buypass_Class_2_Root_CA.pem Adding debian:Buypass_Class_3_Root_CA.pem Adding debian:CA_Disig.pem Adding debian:CA_Disig_Root_R1.pem Adding debian:CA_Disig_Root_R2.pem Adding debian:CA_WoSign_ECC_Root.pem Adding debian:CFCA_EV_ROOT.pem Adding debian:CNNIC_ROOT.pem Adding debian:COMODO_Certification_Authority.pem Adding debian:COMODO_ECC_Certification_Authority.pem Adding debian:COMODO_RSA_Certification_Authority.pem Adding debian:Camerfirma_Chambers_of_Commerce_Root.pem Adding debian:Camerfirma_Global_Chambersign_Root.pem Add
Bug#832291: bogofilter-{bdb, sqlite, tokyocabinet}: copyright file missing after upgrade (policy 12.5)
On 2016-07-28 02:55, Herbert wrote:
Read these two paragraphs from the original report! This is exactly your
problem!
>> Note that dpkg intentionally does not replace directories with symlinks
>> and vice versa, you need the maintainer scripts to do this.
>> See in particular the end of point 4 in
>> https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase
>>
>>
>> It is recommended to use the dpkg-maintscript-helper commands
>> 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
>> to perform the conversion, ideally using d/$PACKAGE.maintscript.
>> Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
>> See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
> bogofilter-{bdb, sqlite, tokyocabinet} depends on bogofilter-common[0],
> which has the copyright file[1]. And I used:
That's fine
> override_dh_installdocs:
> dh_installdocs --link-doc=bogofilter-common
Which is also fine, but not sufficient for clean upgrades.
Andreas
Bug#832291: bogofilter-{bdb, sqlite, tokyocabinet}: copyright file missing after upgrade (policy 12.5)
Hi Andreas Beckmann,
I did the last upload. Please see below.
a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.
This was observed on the following upgrade paths:
jessie -> stretch
>From the attached log (scroll to the bottom...):
1m18.5s ERROR: WARN: Inadequate results from running adequate!
bogofilter-bdb: missing-copyright-file /usr/share/doc/bogofilter-bdb/copyright
MISSING COPYRIGHT FILE: /usr/share/doc/bogofilter-bdb/copyright
# ls -lad /usr/share/doc/bogofilter-bdb
drwxr-xr-x 2 root root 40 Jun 10 11:52 /usr/share/doc/bogofilter-bdb
# ls -la /usr/share/doc/bogofilter-bdb/
total 0
drwxr-xr-x 2 root root 40 Jun 10 11:52 .
drwxr-xr-x 109 root root 2300 Jun 10 11:52 ..
Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile
Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase
It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
bogofilter-{bdb, sqlite, tokyocabinet} depends on bogofilter-common[0],
which has the copyright file[1]. And I used:
debian/rules:
override_dh_installdocs:
dh_installdocs --link-doc=bogofilter-common
[0] -
https://anonscm.debian.org/git/collab-maint/bogofilter.git/tree/debian/control
[1] - https://packages.debian.org/sid/all/bogofilter-common/filelist
Debian Policy 12.5 says:
"/usr/share/doc/package may be a symbolic link to another directory in
/usr/share/doc only if the two packages both come from the same source
and the first package Depends on the second. These rules are important
because copyright files must be extractable by mechanical means."
I will check the current dh_installdocs manpage tomorrow.
regards,
Herbert
Bug#832638: evolver: FTBFS on architectures not supported by libquadmath0
Package: evolver Version: 2.70+ds-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Evolver enthusiasts, it appears that the quadruple floating point format is not supported on all architectures: in its present form, the evolver package cannot build on these architectures. A workaround is on its way. Thanks, Jerome -- System Information: Debian Release: Jessie* APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.7-ckt20-0001-mbp62 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages evolver depends on: ii evolver-nox 2.70+ds-1 ii evolver-ogl 2.70+ds-1 evolver recommends no packages. evolver suggests no packages. -- no debconf information
Bug#822052: marked as done (lout: Build arch:all+arch:any but is missing build-{arch,indep} targets)
Your message dated Wed, 27 Jul 2016 23:34:02 +
with message-id
and subject line Bug#822052: fixed in lout 3.39-2
has caused the Debian Bug report #822052,
regarding lout: Build arch:all+arch:any but is missing build-{arch,indep}
targets
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.)
--
822052: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822052
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lout
Severity: normal
Usertags: arch-all-and-any-missing-targets
Hi,
The package lout builds an architecture independent *and* an
architecture dependent package, but does not have the (now mandatory)
"build-arch" and "build-indep" targets in debian/rules.
We would like to phase out the hacks in dpkg, which are currently
needed to ensure that lout builds despite its lack of these
targets.
* Please add build-arch and build-indep targets to lout at
your earliest convenience.
- This can also be solved by using e.g. the "dh"-style rules.
* The work around will be removed in the first dpkg upload after
the 1st of June. After that upload, lout will FTBFS if
this bug has not been fixed before then.
Thanks,
See also: https://lists.debian.org/debian-devel/2016/04/msg00023.html
--- End Message ---
--- Begin Message ---
Source: lout
Source-Version: 3.39-2
We believe that the bug you reported is fixed in the latest version of
lout, 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 822...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Santiago Vila (supplier of updated lout 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: Wed, 27 Jul 2016 23:59:46 +0100
Source: lout
Binary: lout lout-common lout-doc
Architecture: source
Version: 3.39-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Santiago Vila
Description:
lout - Typesetting system, an alternative to (La)TeX
lout-common - Common files for the Lout typesetting system
lout-doc - Documentation on the Lout typesetting system
Closes: 822052
Changes:
lout (3.39-2) unstable; urgency=medium
.
* QA upload.
* Package is orphaned (Bug #717188). Set maintainer to "Debian QA Group".
* Drop way outdated preinst from lout-common.
* Add build-arch and build-indep targets to debian/rules. Closes: #822052.
Checksums-Sha1:
9e06c7886170e2fb79179596ef4182b9c103b513 1448 lout_3.39-2.dsc
063b3f50dd7654efb51a1a43eb23cc0fa8a8ff1f 8160 lout_3.39-2.debian.tar.xz
Checksums-Sha256:
708bcd8eef7d5457763699535a620d32aaf694cc79aaa66dd6d55d02c0c7b355 1448
lout_3.39-2.dsc
846c1cfd19846fdaf4a44ab030406db968f416f41b0712a1c28beecdb082a086 8160
lout_3.39-2.debian.tar.xz
Files:
5ccd6535e8e721a31d9e0a18a78d7893 1448 text optional lout_3.39-2.dsc
ce0a22e395e907ed188e35efc907dc45 8160 text optional lout_3.39-2.debian.tar.xz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQEcBAEBCAAGBQJXmUCBAAoJEEHOfwufG4sy9wgH/jWoX+Joknr2VMEUcD2y6hjl
dGJNhHQ1ci+w7+KXgos73wynhowMveDsdYjd6lsPamJqaOtxA1arzgJRqEmaWLVv
8bDPwnd5cxuNXnaV8QjOiQTemU9WhvnA4/pltjhKmCTzt1jGz8OxX38rJ8Bo3SQI
8+WlvgK77js0JSSbPqhbH2H2P9ZOwRU0YEbWGe3En5tj6u2/MQ8ux0L5L1Eyk6VI
abFd0xxTA4al6HAVDBhipST4bGQh4UesBiQwaZc0dsPRoPqVctZYCIT5INYBDDem
jtcx61tKabMVvrfjEI/SB3ImKQCW6mCRhladwW5mHHFhBvtohoYdx04GXjVKW7M=
=vLEd
-END PGP SIGNATURE End Message ---
Bug#832626: python-requests: Importing the module fails
On 27-Jul-2016, Michel Le Bihan wrote: > >>> import requests > Traceback (most recent call last): > File "", line 1, in > File "/usr/lib/python2.7/dist-packages/requests/__init__.py", line 61, in > > from .packages.urllib3.exceptions import DependencyWarning > ImportError: cannot import name DependencyWarning Can you show more of the specifics on your system? On mine (Debian Stretch), I can see:: $ python2 Python 2.7.12 (default, Jun 29 2016, 08:18:26) [GCC 5.4.0 20160609] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.version_info sys.version_info(major=2, minor=7, micro=12, releaselevel='final', serial=0) >>> sys.executable '/usr/bin/python2' >>> sys.path ['', '/usr/lib/python2.7', '/usr/lib/python2.7/plat-x86_64-linux-gnu', '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload', '/usr/local/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist-packages/PILcompat', '/usr/lib/python2.7/dist-packages/gtk-2.0'] >>> import requests >>> requests.__version__ '2.10.0' >>> requests.__file__ '/usr/lib/python2.7/dist-packages/requests/__init__.pyc' Can you attempt the above session and paste the result in a message here? -- \ “Pinky, are you pondering what I'm pondering?” “Well, I think | `\ so (hiccup), but Kevin Costner with an English accent?” —_Pinky | _o__) and The Brain_ | Ben Finney signature.asc Description: PGP signature
Bug#822025: marked as done (starvoyager: Build arch:all+arch:any but is missing build-{arch,indep} targets)
Your message dated Wed, 27 Jul 2016 23:05:07 +
with message-id
and subject line Bug#822025: fixed in starvoyager 0.4.4-6
has caused the Debian Bug report #822025,
regarding starvoyager: Build arch:all+arch:any but is missing
build-{arch,indep} targets
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.)
--
822025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: starvoyager
Severity: normal
Usertags: arch-all-and-any-missing-targets
Hi,
The package starvoyager builds an architecture independent *and* an
architecture dependent package, but does not have the (now mandatory)
"build-arch" and "build-indep" targets in debian/rules.
We would like to phase out the hacks in dpkg, which are currently
needed to ensure that starvoyager builds despite its lack of these
targets.
* Please add build-arch and build-indep targets to starvoyager at
your earliest convenience.
- This can also be solved by using e.g. the "dh"-style rules.
* The work around will be removed in the first dpkg upload after
the 1st of June. After that upload, starvoyager will FTBFS if
this bug has not been fixed before then.
Thanks,
See also: https://lists.debian.org/debian-devel/2016/04/msg00023.html
--- End Message ---
--- Begin Message ---
Source: starvoyager
Source-Version: 0.4.4-6
We believe that the bug you reported is fixed in the latest version of
starvoyager, 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 822...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Santiago Vila (supplier of updated starvoyager 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: Wed, 27 Jul 2016 23:16:02 +0100
Source: starvoyager
Binary: starvoyager starvoyager-data
Architecture: source
Version: 0.4.4-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Santiago Vila
Description:
starvoyager - 2D space arcade game, themed around 'Star Trek' - binary
starvoyager-data - 2D space arcade game, themed around 'Star Trek' - data files
Closes: 817678 819347 822025
Changes:
starvoyager (0.4.4-6) unstable; urgency=medium
.
* QA upload.
* Package is orphaned (Bug #831806). Set maintainer to "Debian QA Group".
* Switch to "3.0 (quilt)" source format.
* Raise debhelper compat level to 9. Closes: #817678.
* Apply deterministic-linker-input patch from Sascha Steinbiss.
Should make the build reproducible. Closes: #819347
* Switch to dh. Closes: #822025.
Checksums-Sha1:
196ff311f46327530513b8c14278064261b7c7eb 1482 starvoyager_0.4.4-6.dsc
353901ac573d122a021e672fdbd965e248b62e71 5552 starvoyager_0.4.4-6.debian.tar.xz
Checksums-Sha256:
c948562bfdde74d03ba9ef2b1f8480e31c29144373b59d88621248807914a6dc 1482
starvoyager_0.4.4-6.dsc
c6792e5a0e760da755bff4b5417910fc0010473591d745a6a6a5f068b6e6b3bd 5552
starvoyager_0.4.4-6.debian.tar.xz
Files:
60b7e445e234db7021dbcc48302e9c2e 1482 games optional starvoyager_0.4.4-6.dsc
4e5f39d6f6c1fe6a8505120de8fbb478 5552 games optional
starvoyager_0.4.4-6.debian.tar.xz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQEcBAEBCAAGBQJXmTteAAoJEEHOfwufG4syRSoH+QFrsewat/0oGuybztdRJZQk
FV7bJKJXoPJKhTQXr5ECNlcGOqJ7dh53oHkmZGjVOXPwV5uthz8Gsy2vnftIjUH8
D060MkSrqOm+3PhjeW71L/QSacROOOj690Xb7J0dq85Ebhq2PuVNa+XT/xIzMecF
BHO/0iRSUFXZqWSIikmFVRdKEe8Hpq6Q3Ezno5/N67q7MEIjVxbYZn8StGD3pntI
LXSbfxkfVSpUMqLKG+A9jF8HWE1u6T1/Idsjr8xbU2g7lYiVL2exiNApQuHiUoNJ
x+6DTMILp0VMQSXkakjOajUF465Mjmty6byD6mcn8aMROy2y81rBD7UOaymfk2k=
=205U
-END PGP SIGNATURE End Message ---
Bug#817678: marked as done (starvoyager: Removal of debhelper compat 4)
Your message dated Wed, 27 Jul 2016 23:05:07 + with message-id and subject line Bug#817678: fixed in starvoyager 0.4.4-6 has caused the Debian Bug report #817678, regarding starvoyager: Removal of debhelper compat 4 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.) -- 817678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: starvoyager Severity: important Usertags: compat-4-removal Hi, The package starvoyager uses debhelper with a compat level of 4, which is deprecated and scheduled for removal. * Please bump the debhelper compat at your earliest convenience. on the 15th of June. - Compat 9 is recommended - Compat 5 is the bare minimum - If the package has been relying on dh_install being lenient about missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1]. * Compat level 4 will be removed on the first debhelper upload after the 15th of June. Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2015/09/msg00257.html --- End Message --- --- Begin Message --- Source: starvoyager Source-Version: 0.4.4-6 We believe that the bug you reported is fixed in the latest version of starvoyager, 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 817...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Santiago Vila (supplier of updated starvoyager 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: Wed, 27 Jul 2016 23:16:02 +0100 Source: starvoyager Binary: starvoyager starvoyager-data Architecture: source Version: 0.4.4-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Santiago Vila Description: starvoyager - 2D space arcade game, themed around 'Star Trek' - binary starvoyager-data - 2D space arcade game, themed around 'Star Trek' - data files Closes: 817678 819347 822025 Changes: starvoyager (0.4.4-6) unstable; urgency=medium . * QA upload. * Package is orphaned (Bug #831806). Set maintainer to "Debian QA Group". * Switch to "3.0 (quilt)" source format. * Raise debhelper compat level to 9. Closes: #817678. * Apply deterministic-linker-input patch from Sascha Steinbiss. Should make the build reproducible. Closes: #819347 * Switch to dh. Closes: #822025. Checksums-Sha1: 196ff311f46327530513b8c14278064261b7c7eb 1482 starvoyager_0.4.4-6.dsc 353901ac573d122a021e672fdbd965e248b62e71 5552 starvoyager_0.4.4-6.debian.tar.xz Checksums-Sha256: c948562bfdde74d03ba9ef2b1f8480e31c29144373b59d88621248807914a6dc 1482 starvoyager_0.4.4-6.dsc c6792e5a0e760da755bff4b5417910fc0010473591d745a6a6a5f068b6e6b3bd 5552 starvoyager_0.4.4-6.debian.tar.xz Files: 60b7e445e234db7021dbcc48302e9c2e 1482 games optional starvoyager_0.4.4-6.dsc 4e5f39d6f6c1fe6a8505120de8fbb478 5552 games optional starvoyager_0.4.4-6.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJXmTteAAoJEEHOfwufG4syRSoH+QFrsewat/0oGuybztdRJZQk FV7bJKJXoPJKhTQXr5ECNlcGOqJ7dh53oHkmZGjVOXPwV5uthz8Gsy2vnftIjUH8 D060MkSrqOm+3PhjeW71L/QSacROOOj690Xb7J0dq85Ebhq2PuVNa+XT/xIzMecF BHO/0iRSUFXZqWSIikmFVRdKEe8Hpq6Q3Ezno5/N67q7MEIjVxbYZn8StGD3pntI LXSbfxkfVSpUMqLKG+A9jF8HWE1u6T1/Idsjr8xbU2g7lYiVL2exiNApQuHiUoNJ x+6DTMILp0VMQSXkakjOajUF465Mjmty6byD6mcn8aMROy2y81rBD7UOaymfk2k= =205U -END PGP SIGNATURE End Message ---
Bug#831201: marked as done (torcs: FTBFS with GCC 6: geometry.cpp:373:15: error: 'isnan' was not declared in this scope)
Your message dated Wed, 27 Jul 2016 22:55:28 +
with message-id
and subject line Bug#831201: fixed in torcs 1.3.3+dfsg-0.4
has caused the Debian Bug report #831201,
regarding torcs: FTBFS with GCC 6: geometry.cpp:373:15: error: 'isnan' was not
declared in this scope
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.)
--
831201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: torcs
Version: 1.3.3+dfsg-0.3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64
Hi,
During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html
Relevant part (hopefully):
> g++ -I/«BUILDDIR»/torcs-1.3.3+dfsg/export/include
> -I/«BUILDDIR»/torcs-1.3.3+dfsg -g -O2 -fstack-protector-strong -Wformat
> -Werror=format-security -Wall -fPIC -fno-strict-aliasing -O2 -DUSE_RANDR_EXT
> -DGL_GLEXT_PROTOTYPES -Wall -fPIC -fno-strict-aliasing -O2 -DUSE_RANDR_EXT
> -DGL_GLEXT_PROTOTYPES -Wdate-time -D_FORTIFY_SOURCE=2 -D_SVID_SOURCE
> -D_BSD_SOURCE -DSHM -DHAVE_CONFIG_H -c geometry.cpp
> In file included from
> /usr/include/x86_64-linux-gnu/c++/6/bits/os_defines.h:39:0,
> from
> /usr/include/x86_64-linux-gnu/c++/6/bits/c++config.h:495,
> from /usr/include/c++/6/bits/stl_algobase.h:59,
> from /usr/include/c++/6/vector:60,
> from geometry.h:24,
> from geometry.cpp:21:
> /usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
> # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
>^~~
> geometry.cpp: In function 'void EstimateSphere(std::vector,
> ParametricSphere*)':
> geometry.cpp:373:15: error: 'isnan' was not declared in this scope
> if (isnan(r)) {
>^
> geometry.cpp:373:15: note: suggested alternative:
> In file included from geometry.cpp:23:0:
> /usr/include/c++/6/cmath:655:5: note: 'std::isnan'
> isnan(_Tp __x)
> ^
> make[5]: *** [geometry.o] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2016/07/13/torcs_1.3.3+dfsg-0.3_unstable_gcc6.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 ---
--- Begin Message ---
Source: torcs
Source-Version: 1.3.3+dfsg-0.4
We believe that the bug you reported is fixed in the latest version of
torcs, 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 831...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Aurelien Jarno (supplier of updated torcs 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: Wed, 27 Jul 2016 22:05:12 +
Source: torcs
Binary: torcs torcs-data torcs-data-cars torcs-data-tracks
Architecture: source
Version: 1.3.3+dfsg-0.4
Distribution: unstable
Urgency: medium
Maintainer: Rudy Godoy
Changed-By: Aurelien Jarno
Description:
torcs - 3D racing cars simulator game using OpenGL
torcs-data - base data files for TORCS game
torcs-data-cars - data files for TORCS game - Cars set
torcs-data-tracks - data files for TORCS game - Tracks set
Closes: 831201
Changes:
torcs (1.3.3+dfsg-0.4) unstable; urgency=medium
.
* Non-maintainer upload.
* Replace fix-ftbfs-glib.patch by 0003-fix-glibc-isnan-isinf.patch: better
patch to fix the build failure with glibc 2.23.
* Add 0004-fix-gcc6-isnan.patch: fix the build failure with GCC 6 (Closes:
#831201).
* Add 0005-fix-glib
Bug#831201: torcs: FTBFS with GCC 6: geometry.cpp:373:15: error: 'isnan' was not declared in this scope
On 2016-07-14 09:28, Lucas Nussbaum wrote:
> Source: torcs
> Version: 1.3.3+dfsg-0.3
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20160713 qa-ftbfs
> Justification: FTBFS with GCC 6 on amd64
>
> Hi,
>
> During a rebuild of all packages in sid using the gcc-defaults package
> available in experimental to make GCC default to version 6, your package
> failed
> to build on amd64. For more information about GCC 6 and Stretch, see:
> - https://wiki.debian.org/GCC6
> - https://lists.debian.org/debian-devel-announce/2016/06/msg7.html
>
> Relevant part (hopefully):
> > g++ -I/«BUILDDIR»/torcs-1.3.3+dfsg/export/include
> > -I/«BUILDDIR»/torcs-1.3.3+dfsg -g -O2 -fstack-protector-strong -Wformat
> > -Werror=format-security -Wall -fPIC -fno-strict-aliasing -O2
> > -DUSE_RANDR_EXT -DGL_GLEXT_PROTOTYPES -Wall -fPIC -fno-strict-aliasing -O2
> > -DUSE_RANDR_EXT -DGL_GLEXT_PROTOTYPES -Wdate-time -D_FORTIFY_SOURCE=2
> > -D_SVID_SOURCE -D_BSD_SOURCE -DSHM -DHAVE_CONFIG_H -c geometry.cpp
> > In file included from
> > /usr/include/x86_64-linux-gnu/c++/6/bits/os_defines.h:39:0,
> > from
> > /usr/include/x86_64-linux-gnu/c++/6/bits/c++config.h:495,
> > from /usr/include/c++/6/bits/stl_algobase.h:59,
> > from /usr/include/c++/6/vector:60,
> > from geometry.h:24,
> > from geometry.cpp:21:
> > /usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and
> > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
> > # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use
> > _DEFAULT_SOURCE"
> >^~~
> > geometry.cpp: In function 'void EstimateSphere(std::vector,
> > ParametricSphere*)':
> > geometry.cpp:373:15: error: 'isnan' was not declared in this scope
> > if (isnan(r)) {
> >^
> > geometry.cpp:373:15: note: suggested alternative:
> > In file included from geometry.cpp:23:0:
> > /usr/include/c++/6/cmath:655:5: note: 'std::isnan'
> > isnan(_Tp __x)
> > ^
> > make[5]: *** [geometry.o] Error 1
>
> The full build log is available from:
>
> http://people.debian.org/~lucas/logs/2016/07/13/torcs_1.3.3+dfsg-0.3_unstable_gcc6.log
>
As the package has been removed from stretch, I have just done an NMU to
fix the issue. Please find the diff attached.
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
diff -Nru torcs-1.3.3+dfsg/debian/changelog torcs-1.3.3+dfsg/debian/changelog
--- torcs-1.3.3+dfsg/debian/changelog 2016-07-11 14:27:24.0 +
+++ torcs-1.3.3+dfsg/debian/changelog 2016-07-27 22:05:13.0 +
@@ -1,3 +1,15 @@
+torcs (1.3.3+dfsg-0.4) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Replace fix-ftbfs-glib.patch by 0003-fix-glibc-isnan-isinf.patch: better
+patch to fix the build failure with glibc 2.23.
+ * Add 0004-fix-gcc6-isnan.patch: fix the build failure with GCC 6 (Closes:
+#831201).
+ * Add 0005-fix-glibc-default-source.patch: kill deprecation warnings when
+building with glibc >= 2.23.
+
+ -- Aurelien Jarno Wed, 27 Jul 2016 22:05:12 +
+
torcs (1.3.3+dfsg-0.3) unstable; urgency=medium
* d/p/fix-ftbfs-glib.patch: Fix build failure
diff -Nru torcs-1.3.3+dfsg/debian/patches/0003-fix-glibc-isnan-isinf.patch torcs-1.3.3+dfsg/debian/patches/0003-fix-glibc-isnan-isinf.patch
--- torcs-1.3.3+dfsg/debian/patches/0003-fix-glibc-isnan-isinf.patch 1970-01-01 00:00:00.0 +
+++ torcs-1.3.3+dfsg/debian/patches/0003-fix-glibc-isnan-isinf.patch 2016-07-27 22:00:27.0 +
@@ -0,0 +1,23 @@
+From: Aurelien Jarno
+Date: Wed, 27 Jul 2016 23:57:49 +0200
+Subject: fix is isnan/isinf on an integer value.
+
+car->ctrl->gear is defined as int, therefore it can never be infinite or
+NaN. Just drop the tests.
+
+--- torcs-1.3.3+dfsg.orig/src/modules/simu/simuv2/simu.cpp
torcs-1.3.3+dfsg/src/modules/simu/simuv2/simu.cpp
+@@ -61,13 +61,11 @@ ctrlCheck(tCar *car)
+ if (isnan(car->ctrl->brakeCmd)) car->ctrl->brakeCmd = 0;
+ if (isnan(car->ctrl->clutchCmd)) car->ctrl->clutchCmd = 0;
+ if (isnan(car->ctrl->steer)) car->ctrl->steer = 0;
+-if (isnan(car->ctrl->gear)) car->ctrl->gear = 0;
+ #else
+ if (isnan(car->ctrl->accelCmd) || isinf(car->ctrl->accelCmd)) car->ctrl->accelCmd = 0;
+ if (isnan(car->ctrl->brakeCmd) || isinf(car->ctrl->brakeCmd)) car->ctrl->brakeCmd = 0;
+ if (isnan(car->ctrl->clutchCmd) || isinf(car->ctrl->clutchCmd)) car->ctrl->clutchCmd = 0;
+ if (isnan(car->ctrl->steer) || isinf(car->ctrl->steer)) car->ctrl->steer = 0;
+-if (isnan(car->ctrl->gear) || isinf(car->ctrl->gear)) car->ctrl->gear = 0;
+ #endif
+
+ /* When the car is broken try to send it on the track side */
diff -Nru torcs-1.3.3+dfsg/debian/patches/0004-fix-gcc6-isnan.patch torcs-1.3.3+dfsg/debian/patches/0004-fix-gcc6-isnan.patch
--- torcs-1.3.3+dfsg/debian/patches
Bug#832626: python-requests: Importing the module fails
tag 832626 + moreinfo thanks Hello Michel, On Wednesday, July 27, 2016 09:29:21 PM Michel Le Bihan wrote: > Package: python-requests > Version: 2.10.0-2 > Severity: grave > Justification: renders package unusable > > >>> import requests > > Traceback (most recent call last): > File "", line 1, in > File "/usr/lib/python2.7/dist-packages/requests/__init__.py", line 61, in > > from .packages.urllib3.exceptions import DependencyWarning > ImportError: cannot import name DependencyWarning Please, can you show your sys.path? I'm not able to riproduce your problem. ❯ python -c "import requests; print requests.__version__" 2.10.0 ❯ python -c "from requests.packages.urllib3.exceptions import DependencyWarning; print DependencyWarning" It's also working on a clean pbuilder chroot: I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/base.tgz] I: copying local configuration I: mounting /proc filesystem I: mounting /sys filesystem I: mounting /run/shm filesystem I: mounting /dev/pts filesystem I: Mounting /home/eriol/devel/debian/deps I: policy-rc.d already exists W: no hooks of type H found -- ignoring I: Obtaining the cached apt archive contents I: entering the shell I: File extracted to: /var/cache/pbuilder/build/7695 W: no hooks of type F found -- ignoring root@mornie:/# apt install python-requests Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: ca-certificates libexpat1 libffi6 libpython-stdlib libpython2.7-minimal libpython2.7-stdlib libssl1.0.2 mime-support openssl python python-chardet python-minimal python-pkg-resources python-six python-urllib3 python2.7 python2.7-minimal Suggested packages: python-doc python-tk python-setuptools python-ndg-httpsclient python-openssl python-pyasn1 python-socks python-ntlm python2.7-doc binfmt-support Recommended packages: file python-ndg-httpsclient python-openssl python-pyasn1 The following NEW packages will be installed: ca-certificates libexpat1 libffi6 libpython-stdlib libpython2.7-minimal libpython2.7-stdlib libssl1.0.2 mime-support openssl python python-chardet python-minimal python-pkg-resources python-requests python-six python-urllib3 python2.7 python2.7-minimal 0 upgraded, 18 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/6798 kB of archives. After this operation, 24.0 MB of additional disk space will be used. Do you want to continue? [Y/n] Preconfiguring packages ... Selecting previously unselected package libpython2.7-minimal:amd64. (Reading database ... 12977 files and directories currently installed.) Preparing to unpack .../libpython2.7-minimal_2.7.12-1_amd64.deb ... Unpacking libpython2.7-minimal:amd64 (2.7.12-1) ... Selecting previously unselected package python2.7-minimal. Preparing to unpack .../python2.7-minimal_2.7.12-1_amd64.deb ... Unpacking python2.7-minimal (2.7.12-1) ... Selecting previously unselected package python-minimal. Preparing to unpack .../python-minimal_2.7.11-2_amd64.deb ... Unpacking python-minimal (2.7.11-2) ... Selecting previously unselected package mime-support. Preparing to unpack .../mime-support_3.60_all.deb ... Unpacking mime-support (3.60) ... Selecting previously unselected package libexpat1:amd64. Preparing to unpack .../libexpat1_2.2.0-1_amd64.deb ... Unpacking libexpat1:amd64 (2.2.0-1) ... Selecting previously unselected package libffi6:amd64. Preparing to unpack .../libffi6_3.2.1-4_amd64.deb ... Unpacking libffi6:amd64 (3.2.1-4) ... Selecting previously unselected package libssl1.0.2:amd64. Preparing to unpack .../libssl1.0.2_1.0.2h-1_amd64.deb Unpacking libssl1.0.2:amd64 (1.0.2h-1) ... Selecting previously unselected package libpython2.7-stdlib:amd64. Preparing to unpack .../libpython2.7-stdlib_2.7.12-1_amd64.deb ... Unpacking libpython2.7-stdlib:amd64 (2.7.12-1) ... Selecting previously unselected package python2.7. Preparing to unpack .../python2.7_2.7.12-1_amd64.deb ... Unpacking python2.7 (2.7.12-1) ...
Bug#822033: marked as done (udo: Build arch:all+arch:any but is missing build-{arch,indep} targets)
Your message dated Wed, 27 Jul 2016 22:25:02 +
with message-id
and subject line Bug#822033: fixed in udo 6.4.1-2
has caused the Debian Bug report #822033,
regarding udo: Build arch:all+arch:any but is missing build-{arch,indep} targets
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.)
--
822033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udo
Severity: normal
Usertags: arch-all-and-any-missing-targets
Hi,
The package udo builds an architecture independent *and* an
architecture dependent package, but does not have the (now mandatory)
"build-arch" and "build-indep" targets in debian/rules.
We would like to phase out the hacks in dpkg, which are currently
needed to ensure that udo builds despite its lack of these
targets.
* Please add build-arch and build-indep targets to udo at
your earliest convenience.
- This can also be solved by using e.g. the "dh"-style rules.
* The work around will be removed in the first dpkg upload after
the 1st of June. After that upload, udo will FTBFS if
this bug has not been fixed before then.
Thanks,
See also: https://lists.debian.org/debian-devel/2016/04/msg00023.html
--- End Message ---
--- Begin Message ---
Source: udo
Source-Version: 6.4.1-2
We believe that the bug you reported is fixed in the latest version of
udo, 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 822...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Santiago Vila (supplier of updated udo 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: Wed, 27 Jul 2016 22:27:10 +0100
Source: udo
Binary: udo udo-doc-en udo-doc-de
Architecture: source
Version: 6.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Santiago Vila
Description:
udo- universal document - text processing utility
udo-doc-de - universal document - German documentation
udo-doc-en - universal document - English documentation
Closes: 817706 822033
Changes:
udo (6.4.1-2) unstable; urgency=medium
.
* QA upload.
* Package is orphaned (Bug #831579). Set maintainer to "Debian QA Group".
* Switch to "3.0 (quilt)" source format.
* Raise debhelper compat level to 6. Closes: #817706.
A level higher than that requires deeper changes to debian/rules.
* Add build-arch and build-indep targets to debian/rules. Closes: #822033.
Checksums-Sha1:
1926a31ddc4000a93d67383e437f17fb1ba6ed6f 1367 udo_6.4.1-2.dsc
ab3a292973153edc4c2b957f7eeb11b029c49c43 2316 udo_6.4.1-2.debian.tar.xz
Checksums-Sha256:
5951cbfb8daab1943d86ce32bc69fba3a1231ad142d210d7028233cef337a1a4 1367
udo_6.4.1-2.dsc
bf260ccda2b1d738f091c01ea7fe09e65a18d3806023b812ca9cd17f80c26e3f 2316
udo_6.4.1-2.debian.tar.xz
Files:
b56ff4976c1cd2e3e0e8dde7ff50267f 1367 text optional udo_6.4.1-2.dsc
d1cb5cac839546b2b4c851e30ae4f66c 2316 text optional udo_6.4.1-2.debian.tar.xz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQEcBAEBCAAGBQJXmSc+AAoJEEHOfwufG4symq0IAIHXSjEyXDeU7NbUWQAHbhTX
iy6lXA1WTM8kDrL7SwlqQpQwu1tBWNnx2YYw1/hqAbejyaG/hhfeztXcRJpW8Sge
LXFiAcJXUlWjJyCyIenBqVlZhDFYSdiL4KYnPQnHJ61kL4PCU/P6UZQTHHFYlZBR
aQxke9NUxuEXDH6SRipgON0FL6ReLhxkllNz1oj/OefK8NaW7FEbYibubpaL3ygR
jQad+LYJkPMry5xYjkDQO6v7p6hloF593TqlrDXmyDRdHRBkcVAb37Sp5/wzZT2S
1eEh4k4gDa0fazyc2pHUVcF+F/JeaKOZLeJigO1cPNRBigop2t9yVJ9cX+EoLjU=
=m32+
-END PGP SIGNATURE End Message ---
Bug#817706: marked as done (udo: Removal of debhelper compat 4)
Your message dated Wed, 27 Jul 2016 22:25:02 + with message-id and subject line Bug#817706: fixed in udo 6.4.1-2 has caused the Debian Bug report #817706, regarding udo: Removal of debhelper compat 4 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.) -- 817706: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: udo Severity: important Usertags: compat-4-removal Hi, The package udo uses debhelper with a compat level of 4, which is deprecated and scheduled for removal. * Please bump the debhelper compat at your earliest convenience. on the 15th of June. - Compat 9 is recommended - Compat 5 is the bare minimum - If the package has been relying on dh_install being lenient about missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1]. * Compat level 4 will be removed on the first debhelper upload after the 15th of June. Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2015/09/msg00257.html --- End Message --- --- Begin Message --- Source: udo Source-Version: 6.4.1-2 We believe that the bug you reported is fixed in the latest version of udo, 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 817...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Santiago Vila (supplier of updated udo 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: Wed, 27 Jul 2016 22:27:10 +0100 Source: udo Binary: udo udo-doc-en udo-doc-de Architecture: source Version: 6.4.1-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Santiago Vila Description: udo- universal document - text processing utility udo-doc-de - universal document - German documentation udo-doc-en - universal document - English documentation Closes: 817706 822033 Changes: udo (6.4.1-2) unstable; urgency=medium . * QA upload. * Package is orphaned (Bug #831579). Set maintainer to "Debian QA Group". * Switch to "3.0 (quilt)" source format. * Raise debhelper compat level to 6. Closes: #817706. A level higher than that requires deeper changes to debian/rules. * Add build-arch and build-indep targets to debian/rules. Closes: #822033. Checksums-Sha1: 1926a31ddc4000a93d67383e437f17fb1ba6ed6f 1367 udo_6.4.1-2.dsc ab3a292973153edc4c2b957f7eeb11b029c49c43 2316 udo_6.4.1-2.debian.tar.xz Checksums-Sha256: 5951cbfb8daab1943d86ce32bc69fba3a1231ad142d210d7028233cef337a1a4 1367 udo_6.4.1-2.dsc bf260ccda2b1d738f091c01ea7fe09e65a18d3806023b812ca9cd17f80c26e3f 2316 udo_6.4.1-2.debian.tar.xz Files: b56ff4976c1cd2e3e0e8dde7ff50267f 1367 text optional udo_6.4.1-2.dsc d1cb5cac839546b2b4c851e30ae4f66c 2316 text optional udo_6.4.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJXmSc+AAoJEEHOfwufG4symq0IAIHXSjEyXDeU7NbUWQAHbhTX iy6lXA1WTM8kDrL7SwlqQpQwu1tBWNnx2YYw1/hqAbejyaG/hhfeztXcRJpW8Sge LXFiAcJXUlWjJyCyIenBqVlZhDFYSdiL4KYnPQnHJ61kL4PCU/P6UZQTHHFYlZBR aQxke9NUxuEXDH6SRipgON0FL6ReLhxkllNz1oj/OefK8NaW7FEbYibubpaL3ygR jQad+LYJkPMry5xYjkDQO6v7p6hloF593TqlrDXmyDRdHRBkcVAb37Sp5/wzZT2S 1eEh4k4gDa0fazyc2pHUVcF+F/JeaKOZLeJigO1cPNRBigop2t9yVJ9cX+EoLjU= =m32+ -END PGP SIGNATURE End Message ---
Processed: Re: Bug#832626: python-requests: Importing the module fails
Processing commands for cont...@bugs.debian.org: > tag 832626 + moreinfo Bug #832626 [python-requests] python-requests: Importing the module fails Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 832626: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832626 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#811744: marked as done (libraw: FTBFS with GCC 6: narrowing conversion)
Your message dated Wed, 27 Jul 2016 22:21:36 +
with message-id
and subject line Bug#811744: fixed in libraw 0.17.2-4
has caused the Debian Bug report #811744,
regarding libraw: FTBFS with GCC 6: narrowing conversion
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.)
--
811744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libraw
Version: 0.17.1-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-narrowing
This package fails to build with GCC 6. GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.
Note that only the first error is reported; there might be more. You
can find a snapshot of GCC 6 in experimental. To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.
You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html
> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> make[1]: Entering directory '/<>'
> /bin/bash ./libtool --tag=CXX --mode=compile g++ -DPACKAGE_NAME=\"LibRaw\"
> -DPACKAGE_TARNAME=\"libraw\" -DPACKAGE_VERSION=\"0.17.1\"
> -DPACKAGE_STRING=\"LibRaw\ 0.17.1\" -DPACKAGE_BUGREPORT=\"i...@libraw.org\"
> -DPACKAGE_URL=\"http://www.libraw.org\"; -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
> -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1
> -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1
> -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_JPEGLIB_H=1 -DHAVE_JPEGLIB_H=1
> -DHAVE_JASPER_JASPER_H=1 -I. -Wdate-time -D_FORTIFY_SOURCE=2
> -I/usr/local/include -DUSE_JPEG -DUSE_JPEG8 -DUSE_JASPER -DUSE_LCMS2 -g -O2
> -fstack-protector-strong -Wformat -Werror=format-security -fopenmp -c -o
> internal/dcraw_common.lo internal/dcraw_common.cpp
> libtool: compile: g++ -DPACKAGE_NAME=\"LibRaw\" -DPACKAGE_TARNAME=\"libraw\"
> -DPACKAGE_VERSION=\"0.17.1\" "-DPACKAGE_STRING=\"LibRaw 0.17.1\""
> -DPACKAGE_BUGREPORT=\"i...@libraw.org\"
> -DPACKAGE_URL=\"http://www.libraw.org\"; -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
> -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1
> -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1
> -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_JPEGLIB_H=1 -DHAVE_JPEGLIB_H=1
> -DHAVE_JASPER_JASPER_H=1 -I. -Wdate-time -D_FORTIFY_SOURCE=2
> -I/usr/local/include -DUSE_JPEG -DUSE_JPEG8 -DUSE_JASPER -DUSE_LCMS2 -g -O2
> -fstack-protector-strong -Wformat -Werror=format-security -fopenmp -c
> internal/dcraw_common.cpp -fPIC -DPIC -o internal/.libs/dcraw_common.o
> In file included from ./libraw/libraw.h:40:0,
> from internal/dcraw_common.cpp:29:
> ./libraw/libraw_datastream.h:96:10: warning: 'template class
> std::auto_ptr' is deprecated [-Wdeprecated-declarations]
> std::auto_ptr f; /* will close() automatically through
> dtor */
> ^~~~
>
> In file included from /usr/include/c++/6/memory:81:0,
> from ./libraw/libraw_datastream.h:38,
> from ./libraw/libraw.h:40,
> from internal/dcraw_common.cpp:29:
> /usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
>
> In file included from ./libraw/libraw.h:40:0,
> from internal/dcraw_common.cpp:29:
> ./libraw/libraw_datastream.h:97:10: warning: 'template class
> std::auto_ptr' is deprecated [-Wdeprecated-declarations]
> std::auto_ptr saved_f; /* when *f is a subfile, *saved_f
> is the master file */
> ^~~~
>
> In file included from /usr/include/c++/6/memory:81:0,
> from ./libraw/libraw_datastream.h:38,
> from ./libraw/libraw.h:40,
> from internal/dcraw_common.cpp:29:
> /usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
>
> internal/dcraw_common.cpp: In member function 'void
> LibRaw::vng_interpolate()':
> internal/dcraw_common.cpp:4539:3: error: narrowing conversion of '128' from
> 'int' to 'signed char' inside { } [-Wnarrowing]
>}, chood[] = { -1,-1, -1,0, -1,+1, 0,+1, +1,+1, +1,0, +1,-1, 0,-1 };
>^
>
> internal/dcraw_common.cpp:4539:3: error: narrowing conversion of '136' from
> 'int' to 'signed char' inside { } [-Wnarrowing]
> internal/dcraw_common.cpp:4539:3: error: narrowing conversion of '128' from
> 'int' to 'signed char' inside { } [-Wnarro
Processed: Bug#811671: FTBFS with GCC 6: cannot convert x to y
Processing control commands: > tags -1 fixed-upstream Bug #811671 [audacity] FTBFS with GCC 6: cannot convert x to y Added tag(s) fixed-upstream. -- 811671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#811671: FTBFS with GCC 6: cannot convert x to y
Control: tags -1 fixed-upstream This bug was fixed upstream in this commit: https://github.com/audacity/audacity/commit/60f23220 James signature.asc Description: This is a digitally signed message part
Bug#811993: terminatorx: FTBFS with GCC 6: call overloaded is ambiguous
Hi, upstream has a new release that - among other things - has these issues fixed. Current release is 4.0.1; also note that I have updated the debian package for my own builds (clone from https://terminatorX.org/src/debian.git) maybe some of the modifications can be reused. Regards, Alex
Bug#832633: Fix a pbd file out of bound access
Package: imagemagick Version: 8:6.7.7.10-5 Severity: grave Tags: patch security X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org This is a partial bug fix Bug: https://github.com/ImageMagick/ImageMagick/issues/107 origin: upstream, https://github.com/ImageMagick/ImageMagick/commit/https://github.com/ImageMagick/ImageMagick/issues/107 bug-ubuntu: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1539061 bug-debian: https://bugs.debian.org/823750
Bug#811695: FTBFS with GCC 6: invalid suffix on literal
On Tue, Jan 19, 2016 at 05:03:55PM -0800, Martin Michlmayr wrote: > Package: mstflint > Version: 4.1.0+1.46.gb1cdaf7-1 > Severity: important > User: debian-...@lists.debian.org > Usertags: ftbfs-gcc-6 gcc-6-literal-suffix > > This package fails to build with GCC 6. GCC 6 has not been released > yet, but it's expected that GCC 6 will become the default compiler for > stretch. > [...] For NMUers and interested people: upstream is aware of this issue and planning to fix this around september. Ana
Bug#832626: python-requests: Importing the module fails
Package: python-requests Version: 2.10.0-2 Severity: grave Justification: renders package unusable >>> import requests Traceback (most recent call last): File "", line 1, in File "/usr/lib/python2.7/dist-packages/requests/__init__.py", line 61, in from .packages.urllib3.exceptions import DependencyWarning ImportError: cannot import name DependencyWarning -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (700, 'testing'), (650, 'unstable'), (600, 'experimental'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-requests depends on: ii ca-certificates 20160104 ii python-chardet 2.3.0-2 ii python-urllib3 1.15.1-2 pn python:any python-requests recommends no packages. Versions of packages python-requests suggests: ii python-ndg-httpsclient 0.4.2-1 ii python-openssl 16.0.0-2 ii python-pyasn1 0.1.9-1 pn python-socks -- no debconf information
Bug#811927: marked as done (xneur: FTBFS with GCC 6: defined but not used)
Your message dated Wed, 27 Jul 2016 21:48:24 +0300
with message-id <20160727214824.30b80...@brick.gerasiov.net>
and subject line Re: Bug#811927: xneur: FTBFS with GCC 6: defined but not used
has caused the Debian Bug report #811927,
regarding xneur: FTBFS with GCC 6: defined but not used
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.)
--
811927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xneur
Version: 0.17.0-2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-unused-const-variable
This package fails to build with GCC 6. GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.
Note that only the first error is reported; there might be more. You
can find a snapshot of GCC 6 in experimental. To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.
You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html
> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time
> -D_FORTIFY_SOURCE=2 -I../../lib/config -I../../lib/misc -I../../lib/notify
> -I../../lib/ai -I../../lib/lib -I../../lib/rec -Wall -Wextra -Werror -g0
> -std=gnu99 -fPIC -DXNEUR_PLUGIN_DIR=\"/usr/lib/x86_64-linux-gnu/xneur\" -g
> -O2 -fstack-protector-strong -Wformat -Werror=format-security -c focus.c
> -fPIC -DPIC -o .libs/libxnmain_la-focus.o
> In file included from focus.c:30:0:
> defines.h:30:18: error: 'groups' defined but not used
> [-Werror=unused-const-variable]
> static const int groups[4] = {0x, 0x2000, 0x4000,
> 0x6000};
> ^~
>
> cc1: all warnings being treated as errors
> Makefile:486: recipe for target 'libxnmain_la-focus.lo' failed
> make[4]: *** [libxnmain_la-focus.lo] Error 1
--
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Hello Martin,
On Wed, 27 Jul 2016 11:45:10 -0700
Martin Michlmayr wrote:
> * Alexander Gerasiov [2016-07-27 21:39]:
> > > Note that only the first error is reported; there might be more.
> > > You can find a snapshot of GCC 6 in experimental. To build with
> > > GCC 6, you can set CC=gcc-6 CXX=g++-6 explicitly.
> >
> > Finally new upstream version out and I got some time to package it.
> > Unfortunately I cant reproduce the problem not with 0.17.0-2 you
> > reported, nor with the new one.
>
> I used a pre-released version of GCC 6 so it's possible something has
> been fixed in the compiler in the meantime.
>
> If you don't see the problem, go ahead and close this bug.
> Unfortunately, I cannot do my own GCC 6 retests at the moment.
Ok, fine.
--
Best regards,
Alexander Gerasiov
Contacts:
e-mail: g...@cs.msu.su Homepage: http://gerasiov.net Skype: gerasiov
PGP fingerprint: 04B5 9D90 DF7C C2AB CD49 BAEA CA87 E9E8 2AAC 33F1--- End Message ---
Bug#811927: xneur: FTBFS with GCC 6: defined but not used
* Alexander Gerasiov [2016-07-27 21:39]: > > Note that only the first error is reported; there might be more. You > > can find a snapshot of GCC 6 in experimental. To build with GCC 6, > > you can set CC=gcc-6 CXX=g++-6 explicitly. > > Finally new upstream version out and I got some time to package it. > Unfortunately I cant reproduce the problem not with 0.17.0-2 you > reported, nor with the new one. I used a pre-released version of GCC 6 so it's possible something has been fixed in the compiler in the meantime. If you don't see the problem, go ahead and close this bug. Unfortunately, I cannot do my own GCC 6 retests at the moment. -- Martin Michlmayr HPE Linux, Hewlett Packard Enterprise
Processed: Re: Bug#811927: xneur: FTBFS with GCC 6: defined but not used
Processing commands for cont...@bugs.debian.org: > tag 811927 moreinfo unreproducible Bug #811927 [xneur] xneur: FTBFS with GCC 6: defined but not used Added tag(s) moreinfo and unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. -- 811927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#811927: xneur: FTBFS with GCC 6: defined but not used
tag 811927 moreinfo unreproducible
thanks
Hello Martin,
On Tue, 19 Jan 2016 19:47:22 -0800
Martin Michlmayr wrote:
> Package: xneur
> Version: 0.17.0-2
> Severity: important
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-6 gcc-6-unused-const-variable
>
> This package fails to build with GCC 6. GCC 6 has not been released
> yet, but it's expected that GCC 6 will become the default compiler for
> stretch.
>
> Note that only the first error is reported; there might be more. You
> can find a snapshot of GCC 6 in experimental. To build with GCC 6,
> you can set CC=gcc-6 CXX=g++-6 explicitly.
Finally new upstream version out and I got some time to package it.
Unfortunately I cant reproduce the problem not with 0.17.0-2 you
reported, nor with the new one.
I add gcc,cpp,g++ (>=4:6) to dependencies and run
sbuild --dist experimental --build-dep-resolver=aptitude
It installs gcc 4:6-20160101-3 but builds everything without problem:
> Build Architecture: amd64
> Build-Space: 25200
> Build-Time: 37
> Distribution: experimental
> Host Architecture: amd64
> Install-Time: 115
> Job: /home/gq/debian/packages/xneur_0.17.0-2.dsc
> Machine Architecture: amd64
> Package: xneur
> Package-Time: 157
> Source-Version: 0.17.0-2
> Space: 25200
> Status: successful
> Version: 0.17.0-2
Do I miss something?
>
> You may be able to find out more about this issue at
> https://gcc.gnu.org/gcc-6/changes.html
>
> > sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
> ...
> > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time
> > -D_FORTIFY_SOURCE=2 -I../../lib/config -I../../lib/misc
> > -I../../lib/notify -I../../lib/ai -I../../lib/lib -I../../lib/rec
> > -Wall -Wextra -Werror -g0 -std=gnu99 -fPIC
> > -DXNEUR_PLUGIN_DIR=\"/usr/lib/x86_64-linux-gnu/xneur\" -g -O2
> > -fstack-protector-strong -Wformat -Werror=format-security -c
> > focus.c -fPIC -DPIC -o .libs/libxnmain_la-focus.o In file included
> > from focus.c:30:0: defines.h:30:18: error: 'groups' defined but not
> > used [-Werror=unused-const-variable] static const int groups[4] =
> > {0x, 0x2000, 0x4000, 0x6000}; ^~
> >
> > cc1: all warnings being treated as errors
> > Makefile:486: recipe for target 'libxnmain_la-focus.lo' failed
> > make[4]: *** [libxnmain_la-focus.lo] Error 1
>
--
Best regards,
Alexander Gerasiov
Contacts:
e-mail: g...@cs.msu.su Homepage: http://gerasiov.net Skype: gerasiov
PGP fingerprint: 04B5 9D90 DF7C C2AB CD49 BAEA CA87 E9E8 2AAC 33F1
Bug#831133: marked as done (ardour: FTBFS with GCC 6: ../libs/ardour/parameter_descriptor.cc:181:40: error: no matching function for call to 'max(double, float)')
Your message dated Wed, 27 Jul 2016 18:18:50 + with message-id and subject line Bug#831133: fixed in ardour 1:4.7~dfsg-2 has caused the Debian Bug report #831133, regarding ardour: FTBFS with GCC 6: ../libs/ardour/parameter_descriptor.cc:181:40: error: no matching function for call to 'max(double, float)' 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.) -- 831133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ardour Version: 1:4.7~dfsg-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160713 qa-ftbfs Justification: FTBFS with GCC 6 on amd64 Hi, During a rebuild of all packages in sid using the gcc-defaults package available in experimental to make GCC default to version 6, your package failed to build on amd64. For more information about GCC 6 and Stretch, see: - https://wiki.debian.org/GCC6 - https://lists.debian.org/debian-devel-announce/2016/06/msg7.html Relevant part (hopefully): > 18:28:42 runner ['/usr/bin/g++', '-I/«PKGBUILDDIR»', '-Wdate-time', > '-D_FORTIFY_SOURCE=2', '-g', '-O2', '-fstack-protector-strong', '-Wformat', > '-Werror=format-security', '-DWAF_BUILD', '-DNDEBUG', '-fshow-column', '-O3', > '-fomit-frame-pointer', '-ffast-math', '-fstrength-reduce', '-pipe', > '-DARCH_X86', '-mmmx', '-msse', '-mfpmath=sse', '-DUSE_XMMINTRIN', > '-DBUILD_SSE_OPTIMIZATIONS', '-DLXVST_64BIT', '-Wall', '-Wpointer-arith', > '-Wcast-qual', '-Wcast-align', '-Wno-unused-parameter', > '-DBOOST_SYSTEM_NO_DEPRECATED', '-D_ISOC9X_SOURCE', '-D_LARGEFILE64_SOURCE', > '-D_FILE_OFFSET_BITS=64', '-DENABLE_NLS', '-DPROGRAM_NAME="Ardour"', > u'-DPROGRAM_VERSION="4"', '-std=c++11', '-DBOOST_NO_AUTO_PTR', > '-Woverloaded-virtual', '-Wno-unused-local-typedefs', > '-D__STDC_LIMIT_MACROS', '-D__STDC_FORMAT_MACROS', '-DCANVAS_COMPATIBILITY', > '-DCANVAS_DEBUG', '-fPIC', '-fPIC', '-std=c++11', '-pthread', '-pthread', > '-pthread', '-pthread', '-std=c++11', '-pthread', '-std=c++11', > '-I/«PKGBUILDDIR»/build/libs/ardour', '-I/«PKGBUILDDIR»/libs/ardour', > '-I/«PKGBUILDDIR»/build/libs/surfaces/control_protocol', > '-I/«PKGBUILDDIR»/libs/surfaces/control_protocol', > '-I/«PKGBUILDDIR»/build/libs', '-I/«PKGBUILDDIR»/libs', > '-I/«PKGBUILDDIR»/build/libs/midi++2', '-I/«PKGBUILDDIR»/libs/midi++2', > '-I/«PKGBUILDDIR»/build/libs/evoral', '-I/«PKGBUILDDIR»/libs/evoral', > '-I/«PKGBUILDDIR»/build/libs/audiographer', > '-I/«PKGBUILDDIR»/libs/audiographer', > '-I/«PKGBUILDDIR»/build/libs/audiographer/src', > '-I/«PKGBUILDDIR»/libs/audiographer/src', '-I/«PKGBUILDDIR»/build/libs/pbd', > '-I/«PKGBUILDDIR»/libs/pbd', '-I/«PKGBUILDDIR»/build/libs/evoral/src/libsmf', > '-I/«PKGBUILDDIR»/libs/evoral/src/libsmf', > '-I/«PKGBUILDDIR»/build/libs/timecode', '-I/«PKGBUILDDIR»/libs/timecode', > '-I/usr/include/glibmm-2.4', > '-I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include', '-I/usr/include/glib-2.0', > '-I/usr/lib/x86_64-linux-gnu/glib-2.0/include', '-I/usr/include/sigc++-2.0', > '-I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include', '-I/usr/include/libxml2', > '-I/usr/include/taglib', '-I/usr/include/sratom-0', '-I/usr/include/sord-0', > '-I/usr/include/serd-0', '-I/usr/include/lilv-0', '-I/usr/include/suil-0', > '-I/usr/include/giomm-2.4', '-I/usr/lib/x86_64-linux-gnu/giomm-2.4/include', > '-I/«PKGBUILDDIR»/build', '-DINTERNAL_SHARED_LIBS=1', > '-DUSE_EXTERNAL_LIBS=1', '-DHAVE_DLOPEN=1', '-DHAVE_ALSA=1', '-DHAVE_GLIB=1', > '-DHAVE_GTHREAD=1', '-DHAVE_GLIBMM=1', '-DHAVE_SNDFILE=1', '-DHAVE_GIOMM=1', > '-DHAVE_CURL=1', '-DHAVE_LO=1', '-DHAVE_TAGLIB=1', '-DHAVE_VAMPSDK=1', > '-DHAVE_VAMPHOSTSDK=1', '-DHAVE_RUBBERBAND=1', > '-DEXPORT_VISIBILITY_HIDDEN=False', '-DENABLE_NLS=1', '-DLXVST_SUPPORT=1', > '-DCONFIG_ARCH="x86_64"', '-DHAVE_TOOLS_SANITY_CHECK=1', > '-DHAVE_TOOLS_GCCABICHECK=1', '-DHAVE_LIBS_CLEARLOOKS_NEWER=1', > '-DHAVE_LIBS_QM_DSP=1', '-DHAVE_FFTW3F=1', '-DHAVE_AUBIO=1', > '-DHAVE_AUBIO4=1', '-DHAVE_LIBS_VAMP_PLUGINS=1', '-DHAVE_LIBLTC=1', > '-DHAVE_LIBS_LIBLTC=1', '-DHAVE_LIBS_PTFORMAT=1', '-DHAVE_XML=1', > '-DHAVE_SIGCPP=1', '-DHAVE_GETMNTENT=1', '-DHAVE_EXECINFO=1', > '-DHAVE_POSIX_MEMALIGN=1', '-DHAVE_LOCALTIME_R=1', '-DHAVE_LIBS_PBD=1', > '-DHAVE_LIBS_MIDIPP2=1', '-DHAVE_LIBS_EVORAL=1', '-DHAVE_CWIID_H=1', > '-DHAVE_BLUETOOTH_H=1', '-DHAVE_CWIID=1', '-DBUILD_WIIMOTE=1', > '-DHAVE_CONTROL_PROTOCOL=1', '-DHAVE_FADERPORT=1', '-DHAVE_GENERIC_MIDI=1', > '-DHAVE_MACKIE=1', '-DHAVE_WIIMOTE=1', '-DHAVE_LIBS_SURFACES=1', > '-DHAVE_2IN2OUT=1', '-DHAVE_1IN2OUT=1', '-D
Processed: adjust severity
Processing commands for cont...@bugs.debian.org: > severity 832624 important Bug #832624 [libdrm-nouveau2] libdrm-nouveau2: GTX 660: screen is corrupted, with garbage, tears and the freezes Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 832624: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#831133: marked as pending
tag 831133 pending thanks Hello, Bug #831133 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=pkg-multimedia/ardour.git;a=commitdiff;h=896df6c --- commit 896df6cc4789cea6bbb6d5f2b8539ac9a1e741d6 Author: Jaromír Mikeš Date: Wed Jul 27 18:51:28 2016 +0200 Finalize changelog. diff --git a/debian/changelog b/debian/changelog index 2f6eb63..ca9601a 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,6 +1,11 @@ -ardour (1:4.7~dfsg-2) UNRELEASED; urgency=medium +ardour (1:4.7~dfsg-2) unstable; urgency=medium - * Start new upload. + * Add .gitignore file. + * Add patch to build with gcc6. (Closes: #831133) + * Bump Standards. + * Fix VCS fields. + * Fix hardening. + * Build-dep dh 9. -- Jaromír Mikeš Wed, 27 Jul 2016 15:31:34 +0200
Processed: Bug#831133 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 831133 pending Bug #831133 [src:ardour] ardour: FTBFS with GCC 6: ../libs/ardour/parameter_descriptor.cc:181:40: error: no matching function for call to 'max(double, float)' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 831133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#832624: libdrm-nouveau2: GTX 660: screen is corrupted, with garbage, tears and the freezes
Package: libdrm-nouveau2 Version: 2.4.68-1 Severity: critical Tags: upstream Justification: breaks the whole system This occurred after a half an hour to an hour of use. At the time I was using Virtualbox then switched to the native Chrome browser and scrolled the window. At that point the screen tears and freezes. The following error messages are logged: [ 3905.379386] nouveau E[ PGRAPH][:01:00.0] TRAP ch 6 [0x023f6ee000 chrome[3360]] [ 3905.379400] nouveau E[ PGRAPH][:01:00.0] GPC2/TPC0/MP trap: MULTIPLE_WARP_ERRORS GPR_OUT_OF_BOUNDS [ 3905.379422] nouveau E[ PGRAPH][:01:00.0] TRAP ch 6 [0x023f6ee000 chrome[3360]] [ 3905.379433] nouveau E[ PGRAPH][:01:00.0] GPC2/TPC0/MP trap: MULTIPLE_WARP_ERRORS GPR_OUT_OF_BOUNDS [ 3905.379494] nouveau E[ PGRAPH][:01:00.0] TRAP ch 6 [0x023f6ee000 chrome[3360]] [ 3905.379505] nouveau E[ PGRAPH][:01:00.0] GPC2/TPC0/MP trap: MULTIPLE_WARP_ERRORS GPR_OUT_OF_BOUNDS [ 3905.396083] nouveau E[ PGRAPH][:01:00.0] TRAP ch 6 [0x023f6ee000 chrome[3360]] [ 3905.396098] nouveau E[ PGRAPH][:01:00.0] GPC2/TPC0/MP trap: MULTIPLE_WARP_ERRORS GPR_OUT_OF_BOUNDS [ 3905.396124] nouveau E[ PGRAPH][:01:00.0] TRAP ch 6 [0x023f6ee000 chrome[3360]] [ 3905.396134] nouveau E[ PGRAPH][:01:00.0] GPC2/TPC0/MP trap: MULTIPLE_WARP_ERRORS GPR_OUT_OF_BOUNDS [ 3905.396977] nouveau E[ PGRAPH][:01:00.0] TRAP ch 6 [0x023f6ee000 chrome[3360]] [ 3905.396986] nouveau E[ PGRAPH][:01:00.0] GPC2/TPC0/MP trap: MULTIPLE_WARP_ERRORS GPR_OUT_OF_BOUNDS [ 3909.701685] nouveau E[ PFIFO][:01:00.0] SCHED_ERROR [ CTXSW_TIMEOUT ] [ 3909.701690] nouveau E[ PFIFO][:01:00.0] PGRAPH engine fault on channel 2, recovering... [ 3909.706025] nouveau E[ PGRAPH][:01:00.0] TRAP ch 6 [0x023f6ee000 chrome[3360]] [ 3909.706032] nouveau E[ PGRAPH][:01:00.0] GPC2/TPC0/MP trap: MULTIPLE_WARP_ERRORS GPR_OUT_OF_BOUNDS [ 3909.706054] nouveau E[ PGRAPH][:01:00.0] TRAP ch 6 [0x023f6ee000 chrome[3360]] [ 3909.706069] nouveau E[ PGRAPH][:01:00.0] GPC2/TPC0/MP trap: MULTIPLE_WARP_ERRORS GPR_OUT_OF_BOUNDS [ 3909.706092] nouveau E[ PGRAPH][:01:00.0] TRAP ch 6 [0x023f6ee000 chrome[3360]] [ 3909.706101] nouveau E[ PGRAPH][:01:00.0] GPC2/TPC0/MP trap: MULTIPLE_WARP_ERRORS GPR_OUT_OF_BOUNDS [ 3909.706123] nouveau E[ PGRAPH][:01:00.0] TRAP ch 6 [0x023f6ee000 chrome[3360]] [ 3909.706131] nouveau E[ PGRAPH][:01:00.0] GPC2/TPC0/MP trap: MULTIPLE_WARP_ERRORS GPR_OUT_OF_BOUNDS [ 4000.115586] traps: VirtualBox[5698] general protection ip:7f8f88cbea8d sp:7ffc72821920 error:0 [ 4000.115590] traps: VBoxCrWinCmd[5724] general protection ip:7f8f88cbea8d sp:7f8f4e256d40 error:0 [ 4000.115592] in libc-2.19.so[7f8f88c87000+1a2000] [ 4000.116162] in libc-2.19.so[7f8f88c87000+1a2000] [ 4014.961434] nouveau E[Xorg[835]] failed to idle channel 0x [Xorg[835]] [ 4029.983511] nouveau E[Xorg[835]] failed to idle channel 0x [Xorg[835]] [ 4045.005588] nouveau E[gnome-shell[3058]] failed to idle channel 0x [gnome-shell[3058]] [ 4060.027666] nouveau E[gnome-shell[3058]] failed to idle channel 0x [gnome-shell[3058]] [ 4075.049742] nouveau E[chrome[3360]] failed to idle channel 0x [chrome[3360]] [ 4090.071820] nouveau E[chrome[3360]] failed to idle channel 0x [chrome[3360]] [ 4090.072235] nouveau E[ PFIFO][:01:00.0] read fault at 0x013000 [PTE] from PBDMA0/HOST_CPU on channel 0x023f6ee000 [unknown] [ 4092.049527] nouveau E[ DRM] GPU lockup - switching to software fbcon [ 4105.097902] nouveau E[VBoxCrWinCmd[5724]] failed to idle channel 0x [VBoxCrWinCmd[5724]] [ 4120.119979] nouveau E[VBoxCrWinCmd[5724]] failed to idle channel 0x [VBoxCrWinCmd[5724]] [ 4181.982895] nouveau E[gnome-session-c[7025]] failed to idle channel 0x [gnome-session-c[7025]] [ 4197.004972] nouveau E[gnome-session-c[7025]] failed to idle channel 0x [gnome-session-c[7025]] [ 4212.027048] nouveau E[gnome-session-c[7025]] failed to idle channel 0x [gnome-session-c[7025]] [ 4227.049126] nouveau E[gnome-session-c[7025]] failed to idle channel 0x [gnome-session-c[7025]] [ 4242.071203] nouveau E[gnome-session-c[7025]] failed to idle channel 0x [gnome-session-c[7025]] [ 4257.093279] nouveau E[gnome-session-c[7025]] failed to idle channel 0x [gnome-session-c[7025]] [ 4272.115356] nouveau E[gnome-session-c[7025]] failed to idle channel 0x [gnome-session-c[7025]] -- System Information: Debian Release: 8.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (100, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libdrm-nouveau2 depends on: ii libc62.19-18+deb8u4 ii libdrm2 2.4.68-1 libd
Bug#821990: marked as done (gworldclock: Build arch:all+arch:any but is missing build-{arch,indep} targets)
Your message dated Wed, 27 Jul 2016 17:48:50 +
with message-id
and subject line Bug#821990: fixed in gworldclock 1.4.4-10
has caused the Debian Bug report #821990,
regarding gworldclock: Build arch:all+arch:any but is missing
build-{arch,indep} targets
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.)
--
821990: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gworldclock
Severity: normal
Usertags: arch-all-and-any-missing-targets
Hi,
The package gworldclock builds an architecture independent *and* an
architecture dependent package, but does not have the (now mandatory)
"build-arch" and "build-indep" targets in debian/rules.
We would like to phase out the hacks in dpkg, which are currently
needed to ensure that gworldclock builds despite its lack of these
targets.
* Please add build-arch and build-indep targets to gworldclock at
your earliest convenience.
- This can also be solved by using e.g. the "dh"-style rules.
* The work around will be removed in the first dpkg upload after
the 1st of June. After that upload, gworldclock will FTBFS if
this bug has not been fixed before then.
Thanks,
See also: https://lists.debian.org/debian-devel/2016/04/msg00023.html
--- End Message ---
--- Begin Message ---
Source: gworldclock
Source-Version: 1.4.4-10
We believe that the bug you reported is fixed in the latest version of
gworldclock, 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 821...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Drew Parsons (supplier of updated gworldclock package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 28 Jul 2016 00:45:49 +0800
Source: gworldclock
Binary: gworldclock tzwatch
Architecture: source amd64 all
Version: 1.4.4-10
Distribution: unstable
Urgency: medium
Maintainer: Drew Parsons
Changed-By: Drew Parsons
Description:
gworldclock - Displays time and date in specified time zones
tzwatch- Displays time and date in specified time zones on console
Closes: 735396 821990
Changes:
gworldclock (1.4.4-10) unstable; urgency=medium
.
* Standards-Version: 3.9.8
- Remove deprecated Debian menu entry in favour of FreeDesktop
specification.
* Enable separate arch and arch-indep build targets.
Thanks Santiago Vila for the patch. Closes: #821990.
* Update autotools config files at build time.
Thanks Logan Rosen for the patch. Closes: #735396.
* debian/compat = 9
- apply hardening flags during build
Checksums-Sha1:
0c621f42bb02d476539abb6980377bec950cfbeb 1770 gworldclock_1.4.4-10.dsc
a314832bfb1557c80136f8159e8ee8149d4a1b81 11679 gworldclock_1.4.4-10.diff.gz
17a38c112391b8f6050cf0a83a752f5bfa281ef6 81602
gworldclock-dbgsym_1.4.4-10_amd64.deb
2d4da749af3cb4cac222817e6130f88c3c2f25bb 34176 gworldclock_1.4.4-10_amd64.deb
d582ba8d3b33fe8aaf0e168af04ae83f4898d97c 13006 tzwatch_1.4.4-10_all.deb
Checksums-Sha256:
a8e646806df8e6ed7d3a51777c6153b00b8f64fbbcb61e3991c0ba53ac3a40d7 1770
gworldclock_1.4.4-10.dsc
4d6edf564a228fa9a8b408b78f69a0d88041b476516fb371fa5302ec8573cbf7 11679
gworldclock_1.4.4-10.diff.gz
7f1154ae5b239bf8c0ee47aad08a9169db227a1d55335a4dcb74b979eafab50b 81602
gworldclock-dbgsym_1.4.4-10_amd64.deb
6479b3c7088a20c668dd65bbad516dd80f56c02c356f1f6cb6c247753991767a 34176
gworldclock_1.4.4-10_amd64.deb
d10f19c1c9c60023f4d87e5db2b0c85207424e48260151cd2d32de533a83850f 13006
tzwatch_1.4.4-10_all.deb
Files:
a7b4ee37bc36a5632972a955e75f0e12 1770 utils optional gworldclock_1.4.4-10.dsc
8a3513adfcfe631522cc2eeb14a20053 11679 utils optional
gworldclock_1.4.4-10.diff.gz
d6fbdf802c649ffae503735059de69b3 81602 debug extra
gworldclock-dbgsym_1.4.4-10_amd64.deb
86af3233e56d555cfec8552c32d1a2a6 34176 utils optional
gworldclock_1.4.4-10_amd64.deb
7e4320bee99d8f51ffe89dc089c0dba9 13006 utils optional tzwatch_1.4.4-10_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBCgAGBQJXmO7cAAoJEFc+8eS9WgH6RvMQAIyg1Gr2FACDzWDaLTteFCUc
GGc07WGkXO3E8yEEpxNNH/NIbKnhdDwSyTVbUGvcL1qjQ5ZtlIIO5J5NoqyDC+R2
lxEZzXvSxOFGKhiQPODam+Tp6A0lKgkM7xv
Bug#830241: marked as done (Could not find 'ntlm-http' (>= 0.1.1, ~> 0.1))
Your message dated Wed, 27 Jul 2016 17:34:08 + with message-id and subject line Bug#830241: fixed in ruby-mechanize 2.7.4-2 has caused the Debian Bug report #830241, regarding Could not find 'ntlm-http' (>= 0.1.1, ~> 0.1) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 830241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ruby-mechanize Version: 2.7.4-1 Severity: serious X-Debbugs-CC: debian-r...@lists.debian.org Dear Maintainer, your gem library fails to load on ruby2.3: % ruby -e 'gem "mechanize"' /usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 'ntlm-http' (>= 0.1.1, ~> 0.1) among 62 total gem(s) (Gem::LoadError) [...] -- ,''`. Christian Hofstaedtler : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- --- End Message --- --- Begin Message --- Source: ruby-mechanize Source-Version: 2.7.4-2 We believe that the bug you reported is fixed in the latest version of ruby-mechanize, 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 830...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lucas Nussbaum (supplier of updated ruby-mechanize 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: Wed, 27 Jul 2016 19:09:10 +0200 Source: ruby-mechanize Binary: ruby-mechanize Architecture: source Version: 2.7.4-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Lucas Nussbaum Description: ruby-mechanize - library used for automating interaction with websites Closes: 830241 Changes: ruby-mechanize (2.7.4-2) unstable; urgency=medium . * Team upload * Update debian/control: bump Standards-Version to 3.9.8 (no changes needed), update dependencies. * Refresh debian/rules and add dependencies check. This would have caught #830241. * Add patch 0003-Replace-dep-on-ntlm-http-by-rubyntlm.patch. Closes: #830241 Checksums-Sha1: 6109d9fff29de0b7df038e9b78411effb1631c75 2313 ruby-mechanize_2.7.4-2.dsc 1e4c03f64c650912706a5f5d0862d980b3014b22 5888 ruby-mechanize_2.7.4-2.debian.tar.xz Checksums-Sha256: a86ab6d291041a0b383bc2d0e3ec73f3e65d7b72c900375d185da56886e51cec 2313 ruby-mechanize_2.7.4-2.dsc 9ad65d570e1c6f63c4aa615a9e6fcc2817e0a6e717c93cb4e4ae6be7119e83f0 5888 ruby-mechanize_2.7.4-2.debian.tar.xz Files: d46b7c4e61639575f771903ff254852b 2313 ruby optional ruby-mechanize_2.7.4-2.dsc 12ba4cc416f0ed806eb0b9a03485c9fe 5888 ruby optional ruby-mechanize_2.7.4-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIVAwUBV5jtTzkUtTL0376ZAQqPNQ//VKZzzlhsLpBTAiwgGTpzXVhGAWZ0wDtg QWRA38f1jDZgFYQ9bxfWDsYUJFtBHbaIenN7Rm/rjN5T48Q4Lnby7sSlFfeGRdIJ oPYMTWCepJp9FLAYrv41d5SRxTOPmDcIw0MUqqmghEwb3h9BQEfeZZvO20Uy/gFY +DX5bbvYKumwF0+TIhLFnQWWQ8/IaiJ5Y0lQKuR0YE1zEXpIqENfIbX6///3Z4st foUZhP9ecxaQUJGsoRxnM6uO1g13woTnV3f0U8VvcJbJnFRKJHmlM5E6pf1gkLNE fpZUlwiUuNPW3k3fJz2MqqMzrc35HrbfDCn35fFY0dLBBx2wSOVagZoi0YvTQuvj jAt2fIXZILhnbFYFOdO9OOYZSezWRBkM20bEKWPgK5n2L0iae2Y2nhUVi++yY81+ 1MrA20a7nlQVo/OxMjymWL+SXJmd0zSxCCZW/2pEWSqqQEf7bwDRnxpjo0HromKf J9GsZitI5UnRKUn4gfOzeOJMwR55hSj5by9bwAEbM6cpJefYMIFfYSVXztvvwS1P JlCM8cDbkq1QCCQYjzvgJYuKgMyOKV3FVsg+v531TAFrfB4ApiHanR+PKdHcv0+N K31Estv77Tze/ZMHmXWqpf+c2lrqo5PRJkUPa//Z006mNBCyXCxX4041hHzcmGvu hwESgIIRi2U= =Z2WB -END PGP SIGNATURE End Message ---
Processed: Re: ruby-uglifier: embedded code copy of uglifyJS (should depend on some package built from uglifyjs source)
Processing control commands: > severity -1 serious Bug #718367 [ruby-uglifier] ruby-uglifier: embedded code copy of uglifyJS (should depend on some package built from uglifyjs source) Severity set to 'serious' from 'normal' > block -1 by 830978 Bug #718367 [ruby-uglifier] ruby-uglifier: embedded code copy of uglifyJS (should depend on some package built from uglifyjs source) 718367 was blocked by: 757877 718367 was not blocking any bugs. Added blocking bug(s) of 718367: 830978 -- 718367: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718367 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#832091: marked as done (kpatch install: Error! Bad return status for module build on kernel: 4.6.0-1-amd64 (x86_64))
Your message dated Wed, 27 Jul 2016 17:20:17 + with message-id and subject line Bug#832091: fixed in kpatch 0.3.2-3 has caused the Debian Bug report #832091, regarding kpatch install: Error! Bad return status for module build on kernel: 4.6.0-1-amd64 (x86_64) 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.) -- 832091: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832091 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kpatch Version: 0.3.2-2 Severity: grave Justification: renders package unusable Dear Maintainer, When install the kpatch with apt, it comes: Error! Bad return status for module build on kernel: 4.6.0-1-amd64 (x86_64) And the error log of build: DKMS make.log for kpatch-0.3.2 for kernel 4.6.0-1-amd64 (x86_64) 2016年 07月 22日 星期五 15:51:07 CST make: Entering directory '/var/lib/dkms/kpatch/0.3.2/build/kmod' make -C core clean make[1]: Entering directory '/var/lib/dkms/kpatch/0.3.2/build/kmod/core' rm -f -Rf .*.o.cmd .*.ko.cmd .tmp_versions *.o *.ko *.mod.c \ Module.symvers make[1]: Leaving directory '/var/lib/dkms/kpatch/0.3.2/build/kmod/core' make -C core make[1]: Entering directory '/var/lib/dkms/kpatch/0.3.2/build/kmod/core' make -C /lib/modules/4.6.0-1-amd64/build M=/var/lib/dkms/kpatch/0.3.2/build/kmod/core kpatch.ko make[2]: Entering directory '/var/lib/dkms/kpatch/0.3.2/build/kmod/core' make[2]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. CC [M] /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.o /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:255:13: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .address = kpatch_backtrace_address_verify, ^
Bug#826842: marked as done (gammaray: FTBFS on i386 and mips: tests fail/timeout)
Your message dated Wed, 27 Jul 2016 17:19:56 +
with message-id
and subject line Bug#826842: fixed in gammaray 2.5.0-1
has caused the Debian Bug report #826842,
regarding gammaray: FTBFS on i386 and mips: tests fail/timeout
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.)
--
826842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gammaray
Version: 2.4.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
gammaray FTBFS on mips (tests timeout) and i386 (tests fail):
https://buildd.debian.org/status/fetch.php?pkg=gammaray&arch=mips&ver=2.4.0-1&stamp=1460020494
https://buildd.debian.org/status/fetch.php?pkg=gammaray&arch=i386&ver=2.4.0-1&stamp=1452367783
Start 21: quickinspectortest
21/21 Test #21: quickinspectortest ...***Failed2.82 sec
* Start testing of QuickInspectorTest *
Config: Using QtTest library 5.5.1, Qt 5.5.1 (i386-little_endian-ilp32 shared
(dynamic) release build; by GCC 5.3.1 20160101)
PASS : QuickInspectorTest::initTestCase()
QWARN : QuickInspectorTest::testModelsReparent() Unable to receive probe
settings, cannot attach to shared memory region "gammaray-21069"
"/tmp/qipc_sharedmemory_gammaray33681cc668d82f050d1de6b1c3a7437e49e763a4" ,
error is: "QSharedMemory::handle:: UNIX key file doesn't exist"
QWARN : QuickInspectorTest::testModelsReparent() Continuing anyway, with
default settings.
QWARN : QuickInspectorTest::testModelsReparent() Unable to receive probe
settings, cannot attach to shared memory region "gammaray-21069"
"/tmp/qipc_sharedmemory_gammaray33681cc668d82f050d1de6b1c3a7437e49e763a4" ,
error is: "QSharedMemory::handle:: UNIX key file doesn't exist"
QWARN : QuickInspectorTest::testModelsReparent() Continuing anyway, with
default settings.
PASS : QuickInspectorTest::testModelsReparent()
PASS : QuickInspectorTest::testModelsCreateDestroy()
PASS : QuickInspectorTest::testModelsCreateDestroyProxy()
PASS : QuickInspectorTest::testItemPicking()
FAIL! : QuickInspectorTest::testFetchingPreview() Compared values are not the
same
Actual (img.pixel(1,1)): 4289709278
Expected (QColor(QStringLiteral("lightsteelblue")).rgb()): 4289774814
Loc: [/«PKGBUILDDIR»/tests/quickinspectortest.cpp(241)]
PASS : QuickInspectorTest::testCustomRenderModes()
PASS : QuickInspectorTest::cleanupTestCase()
Totals: 7 passed, 1 failed, 0 skipped, 0 blacklisted
* Finished testing of QuickInspectorTest *
95% tests passed, 1 tests failed out of 21
Total Test time (real) = 44.67 sec
The following tests FAILED:
21 - quickinspectortest (Failed)
Errors while running CTest
Makefile:86: recipe for target 'test' failed
make[2]: *** [test] Error 8
Andreas
--- End Message ---
--- Begin Message ---
Source: gammaray
Source-Version: 2.5.0-1
We believe that the bug you reported is fixed in the latest version of
gammaray, 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 826...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jakub Adam (supplier of updated gammaray package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 26 Jul 2016 09:35:26 +0200
Source: gammaray
Binary: gammaray gammaray-probe-qt4 gammaray-plugin-objectvisualizer
gammaray-plugin-quickinspector gammaray-plugin-kjobtracker
gammaray-plugin-bluetooth gammaray-plugin-positioning gammaray-dev
Architecture: source
Version: 2.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team
Changed-By: Jakub Adam
Description:
gammaray - Tool for examining the internals of Qt application
gammaray-dev - GammaRay plugin development files
gammaray-plugin-bluetooth - QtBluetooth type support for GammaRay
gammaray-plugin-kjobtracker - KJob tracker plugin for GammaRay
gammaray-plugin-objectvisualizer - QObject hierarchy visualization plugin for
GammaRay
gammaray-plugin-positioning - Qt5Positioning type support for GammaRay
gammaray-plugin-quickinspector - GammaRay plugin for inspecting Q
Bug#831879: marked as done (diaspora-common: fails to install: Error: The new file /var/lib/diaspora-common/diaspora.conf does not exist!)
Your message dated Wed, 27 Jul 2016 22:29:45 +0530 with message-id <1917fa5d-f8ee-090b-a340-121f0997a...@debian.org> and subject line Re: diaspora-common: fails to install: Error: The new file /var/lib/diaspora-common/diaspora.conf does not exist! has caused the Debian Bug report #831879, regarding diaspora-common: fails to install: Error: The new file /var/lib/diaspora-common/diaspora.conf does not exist! to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 831879: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831879 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: diaspora-common Version: 0.5.9.1+debian2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package diaspora-common. (Reading database ... (Reading database ... 11340 files and directories currently installed.) Preparing to unpack .../diaspora-common_0.5.9.1+debian2_all.deb ... Unpacking diaspora-common (0.5.9.1+debian2) ... Setting up diaspora-common (0.5.9.1+debian2) ... dbconfig-common: writing config to /etc/dbconfig-common/diaspora-common.conf Creating config file /etc/dbconfig-common/diaspora-common.conf with new version creating postgres user diaspora: success. verifying creation of user: success. creating database diaspora_production: success. verifying database diaspora_production exists: success. dbconfig-common: flushing administrative password SSL enabled, configuring nginx for localhost... grep: /etc/diaspora.conf: No such file or directory Services List Registering /etc/diaspora.conf via ucf Error: The new file /var/lib/diaspora-common/diaspora.conf does not exist! dpkg: error processing package diaspora-common (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: diaspora-common cheers, Andreas diaspora-common_0.5.9.1+debian2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Control: fixed -1 0.5.9.1+debian4 signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#832568: marked as done (libsmali-java: use source target Java 6)
Your message dated Wed, 27 Jul 2016 16:20:30 + with message-id and subject line Bug#832568: fixed in libsmali-java 2.1.3-1 has caused the Debian Bug report #832568, regarding libsmali-java: use source target Java 6 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.) -- 832568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apktool Version: 2.1.1+dfsg-2 Severity: serious Justification: Policy 3.5 I just installed apktool, and when I run it, it fails like so: $ apktool Exception in thread "main" java.lang.UnsupportedClassVersionError: org/jf/baksmali/baksmali : Unsupported major.minor version 52.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:803) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) at java.net.URLClassLoader.access$100(URLClassLoader.java:71) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at brut.androlib.ApktoolProperties.loadProps(ApktoolProperties.java:54) at brut.androlib.ApktoolProperties.get(ApktoolProperties.java:37) at brut.androlib.ApktoolProperties.get(ApktoolProperties.java:32) at brut.androlib.Androlib.getVersion(Androlib.java:656) at brut.apktool.Main.usage(Main.java:438) at brut.apktool.Main.main(Main.java:100) The version 52 suggests that the class was compiled to run on Java 8[1]. My java alternative points at /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java, so naturally, this doesn't work. [1] https://en.wikipedia.org/wiki/Java_class_file -- System Information: Debian Release: 8.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (102, 'testing'), (101, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages apktool depends on: ii aapt 21-2 ii android-framework-res1:6.0.1+r43-1 ii default-jre-headless [java7-runtime-headless]2:1.7-52 ii libantlr3-runtime-java 3.5.2-5 ii libcommons-cli-java 1.2-3 ii libcommons-io-java 2.4-2 ii libcommons-lang3-java3.3.2-1 ii libguava-java17.0-1 ii libjsr305-java 0.1~+svn49-4 ii libsmali-java2.1.2-1 ii libstringtemplate-java 3.2.1-2 ii libxmlunit-java 1.5-1 ii libxpp3-java 1.1.4c-2 ii libyaml-snake-java 1.12-2 ii openjdk-7-jre-headless [java7-runtime-headless] 7u101-2.6.6-2~deb8u1 apktool recommends no packages. apktool suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libsmali-java Source-Version: 2.1.3-1 We believe that the bug you reported is fixed in the latest version of libsmali-java, 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 832...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated libsmali-java 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: Wed, 27 Jul 2016 15:28:18 +0200 Source: libsmali-java Binary: libsmali-java
Bug#831162: marked as done (libvmime: FTBFS with GCC 6: ../vmime/base.hpp:255:26: error: expected primary-expression before '>' token)
Your message dated Wed, 27 Jul 2016 16:20:43 + with message-id and subject line Bug#831162: fixed in libvmime 0.9.1-6 has caused the Debian Bug report #831162, regarding libvmime: FTBFS with GCC 6: ../vmime/base.hpp:255:26: error: expected primary-expression before '>' token 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.) -- 831162: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831162 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libvmime Version: 0.9.1-5 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160713 qa-ftbfs Justification: FTBFS with GCC 6 on amd64 Hi, During a rebuild of all packages in sid using the gcc-defaults package available in experimental to make GCC default to version 6, your package failed to build on amd64. For more information about GCC 6 and Stretch, see: - https://wiki.debian.org/GCC6 - https://lists.debian.org/debian-devel-announce/2016/06/msg7.html Relevant part (hopefully): > /bin/bash ../libtool --tag=CXX --mode=compile x86_64-linux-gnu-g++ > -DHAVE_CONFIG_H -I. -I.. -I/usr/include -I.. -D_REENTRANT=1 > -D_THREAD_SAFE=1 -I/usr/include/p11-kit-1 -fPIC -DPIC -ansi -pedantic -W > -Wall -Wpointer-arith -Wold-style-cast -Wconversion -Wdate-time > -D_FORTIFY_SOURCE=2 -g -c -o address.lo address.cpp > libtool: compile: x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. > -I/usr/include -I.. -D_REENTRANT=1 -D_THREAD_SAFE=1 -I/usr/include/p11-kit-1 > -fPIC -DPIC -ansi -pedantic -W -Wall -Wpointer-arith -Wold-style-cast > -Wconversion -Wdate-time -D_FORTIFY_SOURCE=2 -g -c address.cpp -fPIC -DPIC > -o .libs/address.o > In file included from ../vmime/address.hpp:28:0, > from address.cpp:24: > ../vmime/base.hpp: In function 'vmime::utility::ref > vmime::dynamicCast(vmime::utility::ref)': > ../vmime/base.hpp:255:26: error: expected primary-expression before '>' token >return y.dynamicCast (); > ^ > ../vmime/base.hpp:255:28: error: expected primary-expression before ')' token >return y.dynamicCast (); > ^ > make[3]: *** [address.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2016/07/13/libvmime_0.9.1-5_unstable_gcc6.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 --- --- Begin Message --- Source: libvmime Source-Version: 0.9.1-6 We believe that the bug you reported is fixed in the latest version of libvmime, 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 831...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Carsten Schoenert (supplier of updated libvmime package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 26 Jul 2016 19:44:24 +0200 Source: libvmime Binary: libvmime-dev libvmime0 Architecture: source Version: 0.9.1-6 Distribution: unstable Urgency: medium Maintainer: Giraffe Maintainers Changed-By: Carsten Schoenert Description: libvmime-dev - C++ mail library (development files) libvmime0 - C++ mail library (runtime library) Closes: 831162 Changes: libvmime (0.9.1-6) unstable; urgency=medium . [ Carsten Schoenert ] * [d8329e8] debian/control: fixup https URI for Git cloning * [a1d9a5d] update Standard-Versions to 3.9.8 * [797ac38] rebuild patch queue from patch-queue branch - Fixing FTBFS with GCC-6 (Thanks Jan Engelhard from Zarafa) (Closes: #831162) * [64ba751] libvmime-dev: increase dependency on libgnutls28-dev to 3.4.0 Checksums-Sha1: 978d64a04574fd4a226ec9743e21b6b8a908c140 2053 libvmime_0.9.1-6.dsc 4e172c6876ea6f41f99a9fe3fda7d92d8cd0814a 13084 libvmime_0.9.1-6.debian.tar.xz Checksums-Sha256: 84243db9d8715bb0084b8b2edd57fcc7bfeae213e9a47fef1cab748556a92c56 2053 libvmime_0.9.1-6.dsc c5ddc4a0e88dc3205fbb523c
Bug#830445: marked as done (cafeobj: FTBFS: ! LaTeX Error: File `iftex.sty' not found.)
Your message dated Wed, 27 Jul 2016 16:19:25 + with message-id and subject line Bug#830445: fixed in cafeobj 1.5.5-1 has caused the Debian Bug report #830445, regarding cafeobj: FTBFS: ! LaTeX Error: File `iftex.sty' 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.) -- 830445: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830445 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cafeobj Version: 1.5.4-4 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160707 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»/doc/refman' > pandoc -f markdown --table-of-contents --toc-depth=2 --template=template.tex > --biblatex -V biblio-files=manual.bib -V papersize=a4paper -V > mainfont='FreeSerif' -V sansfont='FreeSans' -V monofont='FreeMono' -V > documentclass=memoir --latex-engine=xelatex --template=template.tex -t latex > -s -o reference-manual.tex reference-manual.md introduction.md overview.md > cloudsync.md reference-head.md reference.md > xelatex reference-manual.tex > This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/Debian) > (preloaded format=xelatex) > restricted \write18 enabled. > entering extended mode > (./reference-manual.tex > LaTeX2e <2016/03/31> patch level 1 > Babel <3.9r> and hyphenation patterns for 3 language(s) loaded. > (/usr/share/texlive/texmf-dist/tex/latex/memoir/memoir.cls > Document Class: memoir 2016/05/16 v3.7f configurable book, report, article > docu > ment class > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty) > (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty) > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty) > (/usr/share/texlive/texmf-dist/tex/latex/memoir/mem10.clo) > (/usr/share/texlive/texmf-dist/tex/latex/memoir/mempatch.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty) > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifvtex.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty > (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def)) > (/usr/share/texmf/tex/latex/lm/lmodern.sty) > (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty > (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty > For additional information on amsmath, use the `?' option. > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty) > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg) > (/usr/share/texlive/texmf-dist/tex/xelatex/xetex-def/xetex.def > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/infwarerr.sty) > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ltxcmds.sty))) > (/usr/share/texlive/texmf-dist/tex/latex/tools/calc.sty) > (/usr/share/texlive/texmf-dist/tex/latex/base/fixltx2e.sty > > Package fixltx2e Warning: fixltx2e is not required with releases after 2015 > (fixltx2e)All fixes are now in the LaTeX kernel. > (fixltx2e)See the latexrelease package for details. > > ) (/usr/share/texlive/texmf-dist/tex/latex/upquote/upquote.sty > (/usr/share/texlive/texmf-dist/tex/latex/base/textcomp.sty > (/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.def))) > (/usr/share/texlive/texmf-dist/tex/xelatex/mathspec/mathspec.sty > (/usr/share/texlive/texmf-dist/tex/latex/etoolbox/etoolbox.sty) > (/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.sty > (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty > (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3-code.tex) > (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3xdvipdfmx.def)) > (/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty) > (/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec-xetex.sty > (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty > (/usr/share/texlive/texmf-dist/tex/latex/euenc/eu1enc.def) > (/usr/share/texlive/texmf-dist/tex/latex/euenc/eu1lmr.fd)) > (/usr/share/texlive/texmf-dist/tex/xelatex/xunicode/xunicode.sty > (/usr/share/texmf/tex/latex/tipa/t3enc.def > (/usr/share/texlive/texmf-dist/tex/latex/eu
Bug#832622: clang-3.9: Uninstallable in unstable
Package: clang-3.9 Version: 3.9-svn274438-1 Severity: serious Justification: Policy 7.6.1 (Reading database ... 179237 files and directories currently installed.) Preparing to unpack .../clang-3.9_1%3a3.9~svn274438-1_amd64.deb ... Unpacking clang-3.9 (1:3.9~svn274438-1) ... dpkg: error processing archive /var/cache/apt/archives/clang-3.9_1%3a3.9~svn274438-1_amd64.deb (--unpack): trying to overwrite '/usr/share/llvm-3.9/cmake', which is also in package llvm-3.9-dev 1:3.9~svn274438-1 Errors were encountered while processing: /var/cache/apt/archives/clang-3.9_1%3a3.9~svn274438-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) llvm-3.9-dev is: Version: 1:3.9~svn274438-1, not sure if the problem is actually there.. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-rc5+ (SMP w/8 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#821979: dvdisaster: Build arch:all+arch:any but is missing build-{arch,indep} targets
Version: 0.72.4-1 On Wed, 20 Apr 2016, ni...@thykier.net wrote: > Package: dvdisaster > Severity: normal > Usertags: arch-all-and-any-missing-targets > > Hi, > > The package dvdisaster builds an architecture independent *and* an > architecture dependent package, but does not have the (now mandatory) > "build-arch" and "build-indep" targets in debian/rules. Seems a false positive to me. This package has a dh-style debian/rules, so it does not need explicit "build-arch" or "build-indep" targets. (I've also checked and it builds ok with "dpkg-buildpackage -A" in sid). BTW: This package was removed from testing because of this bug. Thanks.
Bug#821980: marked as done (elk: Build arch:all+arch:any but is missing build-{arch,indep} targets)
Your message dated Wed, 27 Jul 2016 17:22:55 +0200 (CEST)
with message-id
and subject line Re: elk: Build arch:all+arch:any but is missing
build-{arch,indep} targets
has caused the Debian Bug report #821980,
regarding elk: Build arch:all+arch:any but is missing build-{arch,indep} targets
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.)
--
821980: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821980
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elk
Severity: normal
Usertags: arch-all-and-any-missing-targets
Hi,
The package elk builds an architecture independent *and* an
architecture dependent package, but does not have the (now mandatory)
"build-arch" and "build-indep" targets in debian/rules.
We would like to phase out the hacks in dpkg, which are currently
needed to ensure that elk builds despite its lack of these
targets.
* Please add build-arch and build-indep targets to elk at
your earliest convenience.
- This can also be solved by using e.g. the "dh"-style rules.
* The work around will be removed in the first dpkg upload after
the 1st of June. After that upload, elk will FTBFS if
this bug has not been fixed before then.
Thanks,
See also: https://lists.debian.org/debian-devel/2016/04/msg00023.html
--- End Message ---
--- Begin Message ---
Version: 3.99.8-4
On Wed, 20 Apr 2016, ni...@thykier.net wrote:
> Package: elk
> Severity: normal
> Usertags: arch-all-and-any-missing-targets
>
> Hi,
>
> The package elk builds an architecture independent *and* an
> architecture dependent package, but does not have the (now mandatory)
> "build-arch" and "build-indep" targets in debian/rules.
Seems a false positive to me.
This package has a dh-style debian/rules, so it does not need explicit
"build-arch" or "build-indep" targets.
(I've also checked and it builds ok with "dpkg-buildpackage -A" in sid).
Thanks.--- End Message ---
Bug#821980: elk: Build arch:all+arch:any but is missing build-{arch,indep} targets
Version: 3.99.8-4 On Wed, 20 Apr 2016, ni...@thykier.net wrote: > Package: elk > Severity: normal > Usertags: arch-all-and-any-missing-targets > > Hi, > > The package elk builds an architecture independent *and* an > architecture dependent package, but does not have the (now mandatory) > "build-arch" and "build-indep" targets in debian/rules. Seems a false positive to me. This package has a dh-style debian/rules, so it does not need explicit "build-arch" or "build-indep" targets. (I've also checked and it builds ok with "dpkg-buildpackage -A" in sid). Thanks.
Bug#821979: marked as done (dvdisaster: Build arch:all+arch:any but is missing build-{arch,indep} targets)
Your message dated Wed, 27 Jul 2016 17:21:04 +0200 (CEST)
with message-id
and subject line Re: dvdisaster: Build arch:all+arch:any but is missing
build-{arch,indep} targets
has caused the Debian Bug report #821979,
regarding dvdisaster: Build arch:all+arch:any but is missing build-{arch,indep}
targets
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.)
--
821979: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821979
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dvdisaster
Severity: normal
Usertags: arch-all-and-any-missing-targets
Hi,
The package dvdisaster builds an architecture independent *and* an
architecture dependent package, but does not have the (now mandatory)
"build-arch" and "build-indep" targets in debian/rules.
We would like to phase out the hacks in dpkg, which are currently
needed to ensure that dvdisaster builds despite its lack of these
targets.
* Please add build-arch and build-indep targets to dvdisaster at
your earliest convenience.
- This can also be solved by using e.g. the "dh"-style rules.
* The work around will be removed in the first dpkg upload after
the 1st of June. After that upload, dvdisaster will FTBFS if
this bug has not been fixed before then.
Thanks,
See also: https://lists.debian.org/debian-devel/2016/04/msg00023.html
--- End Message ---
--- Begin Message ---
Version: 0.72.4-1
On Wed, 20 Apr 2016, ni...@thykier.net wrote:
> Package: dvdisaster
> Severity: normal
> Usertags: arch-all-and-any-missing-targets
>
> Hi,
>
> The package dvdisaster builds an architecture independent *and* an
> architecture dependent package, but does not have the (now mandatory)
> "build-arch" and "build-indep" targets in debian/rules.
Seems a false positive to me.
This package has a dh-style debian/rules, so it does not need explicit
"build-arch" or "build-indep" targets.
(I've also checked and it builds ok with "dpkg-buildpackage -A" in sid).
BTW: This package was removed from testing because of this bug.
Thanks.--- End Message ---
Bug#822783: eztrace-contrib: FTBFS with libc 2.23: 'memcpy' was not declared in this scope
For reference, the attached commit (commitdiff [1]) from glibc shows the
changes made in string/string.h.
[1]
https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=05a910f7b420c2b831f35ba90e61c80f001c0606
>From 05a910f7b420c2b831f35ba90e61c80f001c0606 Mon Sep 17 00:00:00 2001
From: Wilco Dijkstra
Date: Wed, 5 Aug 2015 15:58:15 +0100
Subject: [PATCH] Improve performance of mempcpy by inlining and using memcpy. Enable
this for all targets except sparc which has an optimized mempcpy
implementation.
---
ChangeLog |6 ++
string/string.h | 19 +++
sysdeps/sparc/bits/string.h |3 +++
3 files changed, 28 insertions(+), 0 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 65592c3..4a45eed 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,11 @@
2015-08-05 Wilco Dijkstra
+ * string/string.h: (mempcpy): Redirect to __mempcpy_inline.
+ (__mempcpy): Likewise. (__mempcpy_inline): New inline function.
+ * sysdeps/sparc/bits/string.h: (_HAVE_STRING_ARCH_mempcpy): Define.
+
+2015-08-05 Wilco Dijkstra
+
* string/memccpy.c (memccpy):
Improve performance by using memchr/memcpy/__mempcpy.
diff --git a/string/string.h b/string/string.h
index 54a4d39..3ab7103 100644
--- a/string/string.h
+++ b/string/string.h
@@ -636,6 +636,25 @@ extern char *basename (const char *__filename) __THROW __nonnull ((1));
# endif
#endif
+#if defined __USE_GNU && defined __OPTIMIZE__ \
+&& defined __extern_always_inline && __GNUC_PREREQ (3,2)
+# if !defined _FORCE_INLINES && !defined _HAVE_STRING_ARCH_mempcpy
+
+#undef mempcpy
+#undef __mempcpy
+#define mempcpy(dest, src, n) __mempcpy_inline (dest, src, n)
+#define __mempcpy(dest, src, n) __mempcpy_inline (dest, src, n)
+
+__extern_always_inline void *
+__mempcpy_inline (void *__restrict __dest,
+ const void *__restrict __src, size_t __n)
+{
+ return (char *) memcpy (__dest, __src, __n) + __n;
+}
+
+# endif
+#endif
+
__END_DECLS
#endif /* string.h */
diff --git a/sysdeps/sparc/bits/string.h b/sysdeps/sparc/bits/string.h
index 36fbb4c..4eb9447 100644
--- a/sysdeps/sparc/bits/string.h
+++ b/sysdeps/sparc/bits/string.h
@@ -26,3 +26,6 @@
/* sparc32 and sparc64 strchr(x, '\0') perform better than
__rawmemchr(x, '\0'). */
#define _HAVE_STRING_ARCH_strchr 1
+
+/* Don't inline mempcpy into memcpy as sparc has an optimized mempcpy. */
+#define _HAVE_STRING_ARCH_mempcpy 1
--
1.7.1
Bug#832118: ruby-puppet-forge: FTBFS: psych.rb:471:in `initialize': No such file or directory @ rb_sysopen - /usr/lib/ruby/locales/config.yaml (Errno::ENOENT)
❦ 22 juillet 2016 16:11 CEST, Chris Lamb : > ruby-puppet-forge fails to build from source in unstable/amd64: It also fails to run. This seems due to the introduction of ruby-gettext-setup. The config.yaml file from locales/config.yaml should be installed in /usr/lib/ruby/locales but it is application specific. So, I suppose that ruby-puppet-forge should be patched as well to search inside its own locales directory. The problem doesn't seem limited to ruby-puppet-forge. ruby-semantic-puppet has the same problem. Commenting the Gettext.initialize() call fix the problem for me. -- There is an old time toast which is golden for its beauty. "When you ascend the hill of prosperity may you not meet a friend." -- Mark Twain signature.asc Description: PGP signature
Bug#832605: ruby-unindent: FTBFS: cannot load such file -- nanotest (LoadError)
Source: ruby-unindent Version: 1.0-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, ruby-unindent fails to build from source in unstable/amd64: [..] ** ** Starting build ** ** Package: ruby-unindent Version: 1.0-1 Build architecture: amd64 Date: Wed, 27 Jul 2016 08:55:06 -0400 Hostname: 5f911484ac4f Uname:Linux 5f911484ac4f 4.6.0-1-amd64 #1 SMP Debian 4.6.2-2 (2016-06-25) x86_64 GNU/Linux /etc/timezone:America/New_York ** ** Installing build dependencies ** ** dh_testdir dh_testroot dh_prep dh_testdir dh_testroot dh_install dh_installdocs dh_installchangelogs dh_compress dh_fixperms dh_installdeb dh_gencontrol dh_md5sums dh_builddeb dpkg-deb: building package 'ruby-unindent-build-deps' in '../ruby-unindent-build-deps_1.0-1_all.deb'. The package has been created. Attention, the package has been created in the current directory, not in ".." as indicated by the message above! Selecting previously unselected package ruby-unindent-build-deps. (Reading database ... 23136 files and directories currently installed.) Preparing to unpack ruby-unindent-build-deps_1.0-1_all.deb ... Unpacking ruby-unindent-build-deps (1.0-1) ... Reading package lists... Building dependency tree... Reading state information... Correcting dependencies... Done The following additional packages will be installed: ca-certificates gem2deb gem2deb-test-runner libgmp-dev libgmpxx4ldbl libruby2.3 libyaml-0-2 openssl rake ruby ruby-all-dev ruby-did-you-mean ruby-minitest ruby-net-telnet ruby-power-assert ruby-setup ruby-test-unit ruby2.3 ruby2.3-dev rubygems-integration Suggested packages: gmp-doc libgmp10-doc libmpfr-dev ri ruby-dev bundler Recommended packages: apt-file python3-debian zip fonts-lato libjs-jquery The following NEW packages will be installed: ca-certificates gem2deb gem2deb-test-runner libgmp-dev libgmpxx4ldbl libruby2.3 libyaml-0-2 openssl rake ruby ruby-all-dev ruby-did-you-mean ruby-minitest ruby-net-telnet ruby-power-assert ruby-setup ruby-test-unit ruby2.3 ruby2.3-dev rubygems-integration 0 upgraded, 20 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 6359 kB of archives. After this operation, 24.2 MB of additional disk space will be used. Get:1 http://httpredir.debian.org/debian sid/main amd64 openssl amd64 1.0.2h-1 [681 kB] Get:2 http://httpredir.debian.org/debian sid/main amd64 ca-certificates all 20160104 [200 kB] Get:3 http://httpredir.debian.org/debian sid/main amd64 rubygems-integration all 1.10 [4882 B] Get:4 http://httpredir.debian.org/debian sid/main amd64 ruby-did-you-mean all 1.0.0-2 [11.2 kB] Get:5 http://httpredir.debian.org/debian sid/main amd64 ruby-minitest all 5.9.0-1 [51.1 kB] Get:6 http://httpredir.debian.org/debian sid/main amd64 ruby-net-telnet all 0.1.1-2 [12.5 kB] Get:7 http://httpredir.debian.org/debian sid/main amd64 ruby-power-assert all 0.3.0-1 [7902 B] Get:8 http://httpredir.debian.org/debian sid/main amd64 ruby-test-unit all 3.1.7-2 [69.6 kB] Get:9 http://httpredir.debian.org/debian sid/main amd64 libyaml-0-2 amd64 0.1.6-3 [50.4 kB] Get:10 http://httpredir.debian.org/debian sid/main amd64 libruby2.3 amd64 2.3.1-5 [3093 kB] Get:11 http://httpredir.debian.org/debian sid/main amd64 ruby2.3 amd64 2.3.1-5 [178 kB] Get:12 http://httpredir.debian.org/debian sid/main amd64 ruby amd64 1:2.3.0+4 [10.5 kB] Get:13 http://httpredir.debian.org/debian sid/main amd64 rake all 10.5.0-2 [49.4 kB] Get:14 http://httpredir.debian.org/debian sid/main amd64 gem2deb-test-runner amd64 0.31 [19.9 kB] Get:15 http://httpredir.debian.org/debian sid/main amd64 libgmpxx4ldbl amd64 2:6.1.1+dfsg-1 [22.3 kB] Get:16 http://httpredir.debian.org/debian sid/main amd64 libgmp-dev amd64 2:6.1.1+dfsg-1 [629 kB] Get:17 http://httpredir.debian.org/debian sid/main amd64 ruby2.3-dev amd64 2.3.1-5 [1170 kB] Get:18 http://httpredir.debian.org/debian sid/main amd64 ruby-all-dev amd64 1:2.3.0+4 [9996 B] Get:19 http://httpredir.debian.org/debian sid/main amd64 ruby-setup all 3.4.1-9 [34.2 kB] Get:20 http://httpredir.debian.org/debian sid/main amd64 gem2deb amd64 0.31 [55.6 kB] Fetched 6359 kB in 0
Bug#832604: ruby-parser: FTBFS: 2915 runs, 14956 assertions, 70 failures, 0 errors, 12 skips
Source: ruby-parser
Version: 3.6.6-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
ruby-parser fails to build from source in unstable/amd64:
[..]
s(:true),
49) Failure:
TestRuby19Parser#test_next [/usr/lib/ruby/vendor_ruby/pt_testcase.rb:151]:
failed on input: "loop { next if false }".
--- expected
+++ actual
@@ -1 +1 @@
-s(:iter, s(:call, nil, :loop), 0, s(:if, s(:false), s(:next), nil))
+s(:iter, s(:call, nil, :loop), s(:args), s(:if, s(:false), s(:next), nil))
50) Failure:
TestRuby19Parser#test_dasgn_icky
[/usr/lib/ruby/vendor_ruby/pt_testcase.rb:151]:
failed on input: "a do\n v = nil\n assert_block(full_message) do\n
begin\n yield\nrescue Exception => v\n break\nend\n
end\nend".
--- expected
+++ actual
@@ -1,11 +1,11 @@
s(:iter,
s(:call, nil, :a),
- 0,
+ s(:args),
s(:block,
s(:lasgn, :v, s(:nil)),
s(:iter,
s(:call, nil, :assert_block, s(:call, nil, :full_message)),
- 0,
+ s(:args),
s(:rescue,
s(:yield),
s(:resbody,
51) Failure:
TestRuby19Parser#test_postexe [/usr/lib/ruby/vendor_ruby/pt_testcase.rb:151]:
failed on input: "END { 1 }".
--- expected
+++ actual
@@ -1 +1 @@
-s(:iter, s(:postexe), 0, s(:lit, 1))
+s(:iter, s(:postexe), s(:args), s(:lit, 1))
52) Failure:
TestRuby19Parser#test_defs_empty
[/usr/lib/ruby/vendor_ruby/pt_testcase.rb:151]:
failed on input: "def self.empty\n # do nothing\nend".
--- expected
+++ actual
@@ -1 +1 @@
-s(:defs, s(:self), :empty, s(:args), s(:nil))
+s(:defs, s(:self), :empty, s(:args))
53) Failure:
TestRuby19Parser#test_defs_expr_wtf
[/usr/lib/ruby/vendor_ruby/pt_testcase.rb:151]:
failed on input: "def (a.b).empty(*)\n # do nothing\nend".
--- expected
+++ actual
@@ -1 +1 @@
-s(:defs, s(:call, s(:call, nil, :a), :b), :empty, s(:args, :*), s(:nil))
+s(:defs, s(:call, s(:call, nil, :a), :b), :empty, s(:args, :*))
54) Failure:
TestRuby19Parser#test_next_arg [/usr/lib/ruby/vendor_ruby/pt_testcase.rb:151]:
failed on input: "loop { next 42 if false }".
--- expected
+++ actual
@@ -1,4 +1,4 @@
s(:iter,
s(:call, nil, :loop),
- 0,
+ s(:args),
s(:if, s(:false), s(:next, s(:lit, 42)), nil))
55) Failure:
TestRuby18Parser#test_postexe [/usr/lib/ruby/vendor_ruby/pt_testcase.rb:151]:
failed on input: "END { 1 }".
--- expected
+++ actual
@@ -1 +1 @@
-s(:iter, s(:postexe), 0, s(:lit, 1))
+s(:iter, s(:postexe), s(:args), s(:lit, 1))
56) Failure:
TestRuby18Parser#test_break [/usr/lib/ruby/vendor_ruby/pt_testcase.rb:151]:
failed on input: "loop { break if true }".
--- expected
+++ actual
@@ -1 +1 @@
-s(:iter, s(:call, nil, :loop), 0, s(:if, s(:true), s(:break), nil))
+s(:iter, s(:call, nil, :loop), s(:args), s(:if, s(:true), s(:break), nil))
57) Failure:
TestRuby18Parser#test_proc_args_0
[/usr/lib/ruby/vendor_ruby/pt_testcase.rb:151]:
failed on input: "proc { || (x + 1) }".
--- expected
+++ actual
@@ -1,4 +1 @@
-s(:iter,
- s(:call, nil, :proc),
- s(:args),
- s(:call, s(:call, nil, :x), :+, s(:lit, 1)))
+s(:iter, s(:call, nil, :proc), 0, s(:call, s(:call, nil, :x), :+, s(:lit,
1)))
58) Failure:
TestRuby18Parser#test_block_mystery_block
[/usr/lib/ruby/vendor_ruby/pt_testcase.rb:151]:
failed on input: "a(b) do\n if b then\ntrue\n else\nc = false\n
d { |x| c = true }\nc\n end\nend".
--- expected
+++ actual
@@ -1,6 +1,6 @@
s(:iter,
s(:call, nil, :a, s(:call, nil, :b)),
- 0,
+ s(:args),
s(:if,
s(:call, nil, :b),
s(:true),
59) Failure:
TestRuby18Parser#test_defs_expr_wtf
[/usr/lib/ruby/vendor_ruby/pt_testcase.rb:151]:
failed on input: "def (a.b).empty(*)\n # do nothing\nend".
--- expected
+++ actual
@@ -1 +1 @@
-s(:defs, s(:call, s(:call, nil, :a), :b), :empty, s(:args, :*), s(:nil))
+s(:defs, s(:call, s(:call, nil, :a), :b), :empty, s(:args, :*))
60) Failure:
TestRuby18Parser#test_proc_args_no
[/usr/lib/ruby/vendor_ruby/pt_testcase.rb:151]:
failed on input: "proc { (x + 1) }".
--- expected
+++ actual
@@ -1 +1,4 @@
-s(:iter, s(:call, nil, :proc), 0, s(:call, s(:call, nil, :x), :+, s(:lit,
1)))
+s(:iter,
+ s(:call, nil, :proc),
+ s(:args),
+ s(:call, s(:call, nil, :x), :+, s(:lit, 1)))
61) Failure:
TestRuby18Parser#test_lvar_def_boundary
[/usr/lib/ruby/vendor_ruby/pt_testcase.rb:151]:
failed on input: "b = 42\ndef a\n c do\nbegin\n do_stuff\n
rescue RuntimeError => b\n puts(b)\nend\n end\nend\n".
--- expected
+++ actual
@@ -5,7 +5,7 @@
s(:args),
s(:iter,
s(:call, nil, :c),
- 0,
+ s(:args),
s(:rescue,
Processed: limit source to runit, tagging 832545
Processing commands for cont...@bugs.debian.org: > limit source runit Limiting to bugs with field 'source' containing at least one of 'runit' Limit currently set to 'source':'runit' > tags 832545 + pending Bug #832545 [src:runit] runit: FTBFS when built with dpkg-buildpackage -A (No such file or directory) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 832545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#821347: libsecret porting for s390x
On 27/07/16 14:16, Aurelien Jarno wrote: > On 2016-07-10 21:24, Andreas Henriksson wrote: >> Hello Bastian Blank. >> >> On Sun, Jul 10, 2016 at 12:33:12PM +0200, Bastian Blank wrote: >>> On Sun, Jun 26, 2016 at 10:12:31PM +0200, Andreas Henriksson wrote: I'd like to ask for your help with looking at the problems building libsecret on s390x. It's currently the only (release-)architecture not building and blocking testing migration for a long time. :( >>> >>> What was the result of your manual build on the s390x porter machine? >> >> Building on a porter box (zelenka) seems to run into the same issue >> and build gets stuck after: >> PASS: test-collection 27 /collection/search-secrets-async >> >> Same as in: >> https://buildd.debian.org/status/fetch.php?pkg=libsecret&arch=s390x&ver=0.18.5-1&stamp=1462961523 > > Note that it also fails the same way on ppc64 and s390x. It therefore > looks like a 64-bit big endian issue. It could be for example a pointer > to an int value casted to a pointer to a long value or vice-versa. I started to look at this the last weekend. I haven't found the cause yet, but I believe it's a bug in gobject-introspection, indeed related to 32 vs 64 bit values. I will try to look at it some more in the next few days. Cheers, Emilio
Bug#821347: libsecret porting for s390x
On 2016-07-10 21:24, Andreas Henriksson wrote: > Hello Bastian Blank. > > On Sun, Jul 10, 2016 at 12:33:12PM +0200, Bastian Blank wrote: > > On Sun, Jun 26, 2016 at 10:12:31PM +0200, Andreas Henriksson wrote: > > > I'd like to ask for your help with looking at the problems building > > > libsecret on s390x. It's currently the only (release-)architecture > > > not building and blocking testing migration for a long time. :( > > > > What was the result of your manual build on the s390x porter machine? > > Building on a porter box (zelenka) seems to run into the same issue > and build gets stuck after: > PASS: test-collection 27 /collection/search-secrets-async > > Same as in: > https://buildd.debian.org/status/fetch.php?pkg=libsecret&arch=s390x&ver=0.18.5-1&stamp=1462961523 Note that it also fails the same way on ppc64 and s390x. It therefore looks like a 64-bit big endian issue. It could be for example a pointer to an int value casted to a pointer to a long value or vice-versa. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#828621: marked as done (opencolorio: FTBFS: ! Undefined control sequence.)
Your message dated Wed, 27 Jul 2016 11:48:46 + with message-id and subject line Bug#828621: fixed in opencolorio 1.0.9~dfsg0-6 has caused the Debian Bug report #828621, regarding opencolorio: FTBFS: ! Undefined control sequence. 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.) -- 828621: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828621 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: opencolorio Version: 1.0.9~dfsg0-5 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, opencolorio fails to build from source in unstable/amd64: [..] Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 518, in import_object __import__(self.modname) ImportError: No module named PyOpenColorIO /home/lamby/temp/cdt.20160626122618.uMWLWemApZ.opencolorio/opencolorio-1.0.9~dfsg0/debian/cmake/docs/developers/bindings/PythonAPI.rst:119: WARNING: autodoc: failed to import function u'SetCurrentConfig' from module u'PyOpenColorIO'; the following exception was raised: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 518, in import_object __import__(self.modname) ImportError: No module named PyOpenColorIO /home/lamby/temp/cdt.20160626122618.uMWLWemApZ.opencolorio/opencolorio-1.0.9~dfsg0/debian/cmake/docs/developers/bindings/PythonAPI.rst:121: WARNING: autodoc: failed to import function u'SetLoggingLevel' from module u'PyOpenColorIO'; the following exception was raised: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 518, in import_object __import__(self.modname) ImportError: No module named PyOpenColorIO /home/lamby/temp/cdt.20160626122618.uMWLWemApZ.opencolorio/opencolorio-1.0.9~dfsg0/debian/cmake/docs/developers/bindings/PythonAPI.rst:126: WARNING: autodoc: failed to import class u'Config' from module u'PyOpenColorIO'; the following exception was raised: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 518, in import_object __import__(self.modname) ImportError: No module named PyOpenColorIO /home/lamby/temp/cdt.20160626122618.uMWLWemApZ.opencolorio/opencolorio-1.0.9~dfsg0/debian/cmake/docs/developers/bindings/PythonAPI.rst:133: WARNING: autodoc: failed to import class u'ColorSpace' from module u'PyOpenColorIO'; the following exception was raised: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 518, in import_object __import__(self.modname) ImportError: No module named PyOpenColorIO /home/lamby/temp/cdt.20160626122618.uMWLWemApZ.opencolorio/opencolorio-1.0.9~dfsg0/debian/cmake/docs/developers/bindings/PythonAPI.rst:140: WARNING: autodoc: failed to import class u'Look' from module u'PyOpenColorIO'; the following exception was raised: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 518, in import_object __import__(self.modname) ImportError: No module named PyOpenColorIO /home/lamby/temp/cdt.20160626122618.uMWLWemApZ.opencolorio/opencolorio-1.0.9~dfsg0/debian/cmake/docs/developers/bindings/PythonAPI.rst:147: WARNING: autodoc: failed to import class u'Processor' from module u'PyOpenColorIO'; the following exception was raised: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 518, in import_object __import__(self.modname) ImportError: No module named PyOpenColorIO /home/lamby/temp/cdt.20160626122618.uMWLWemApZ.opencolorio/opencolorio-1.0.9~dfsg0/debian/cmake/docs/developers/bindings/PythonAPI.rst:154: WARNING: autodoc: failed to import class u'Context' from module u'PyOpenColorIO'; the following exception was raised: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 518, in import_object __import__(self.modname) ImportError: No module named PyOpenColorIO /home/lamby/temp/cdt.20160626122618.uMWLWemApZ.opencolorio/opencolorio-1.0.9~dfsg0/debian/cmake/docs/developers/bindings/PythonTransforms.rst:17: WARNING: autodoc: failed to import class u'Transform' from module u'PyOpenColorIO'; the following exception was raised: Traceback (most recent call last): File "/usr/lib/python2
Bug#832600: djbdns: FTBFS when built with dpkg-buildpackage -A (Missing build-indep target)
Package: src:djbdns
Version: 1:1.05-8
Severity: serious
Tags: patch
Dear maintainer:
I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:
[...]
debian/rules build-indep
make: *** No rule to make target 'build-indep'. Stop.
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
This kind of bug is now considered RC (see Bug #830997 for details).
I recommend switching to "dh", but in the meantime a simple patch
like the appended should probably work.
Thanks.
--- a/djbdns-1.05/debian/rules
+++ b/djbdns-1.05/debian/rules
@@ -28,6 +28,8 @@ dbndns/patch-stamp: configure-stamp
done
touch dbndns/patch-stamp
+build-arch: build
+build-indep: build
build: deb-checkdir build-stamp dbndns/build-stamp
build-stamp: patch-stamp
test -r conf-home'{orig}' || cp -f conf-home conf-home'{orig}'
@@ -129,7 +131,7 @@ binary-indep: install-indep dnscache-run.deb
dpkg-gencontrol -isp -pdnscache-run -P'$(DIRCACHERUN)'
dpkg -b '$(DIRCACHERUN)' ..
-.PHONY: configure patch dbndns/patch build dbndns/build clean install \
+.PHONY: configure patch dbndns/patch build build-arch build-indep dbndns/build
clean install \
binary-indep binary-arch binary
include debian/implicit
Bug#832599: Fails to start after upgrade
Package: iodine
Version: 0.7.0-5
Severity: serious
After the upgrade, chosing not to auto-start the daemon, I get this:
Setting up iodine (0.7.0-5) ...
Job for iodined.service failed because the control process exited with error
code.
See "systemctl status iodined.service" and "journalctl -xe" for details.
invoke-rc.d: initscript iodined, action "start" failed.
● iodined.service - A daemon for tunneling traffic over DNS queries
Loaded: loaded (/lib/systemd/system/iodined.service; disabled; vendor
preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2016-07-27
13:17:34 CEST; 4ms ago
Docs: man:iodined(8)
Process: 2277 ExecStartPre=/bin/sh -xc test ${START_IODINED} = true
(code=exited, status=1/FAILURE)
Jul 27 13:17:34 fishbowl systemd[1]: Failed to start A daemon for tunneling
traffic over DNS queries.
Jul 27 13:17:34 fishbowl systemd[1]: iodined.service: Unit entered failed state.
Jul 27 13:17:34 fishbowl systemd[1]: iodined.service: Failed with result
'exit-code'.
dpkg: error processing package iodine (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
iodine
Please use systemd masking instead of the silly shell test and
/etc/default/* file variable to control whether the daemon should be
started.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages iodine depends on:
ii adduser3.115
ii debconf [debconf-2.0] 1.5.59
ii libc6 2.23-4
ii libsystemd0231-1
ii udev 231-1
ii zlib1g 1:1.2.8.dfsg-2+b1
iodine recommends no packages.
Versions of packages iodine suggests:
ii dnsutils 1:9.10.3.dfsg.P4-10.1
ii fping 3.13-1
ii gawk 1:4.1.3+dfsg-0.1
pn ipcalc
ii iproute2 4.6.0-2
pn network-manager-iodine
pn network-manager-iodine-gnome
-- debconf information:
* iodine/start_daemon: false
iodine/daemon_options:
--
.''`. martin f. krafft @martinkrafft
: :' : proud Debian developer
`. `'` http://people.debian.org/~madduck
`- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#831816: marked as done (jflex: no human maintainer Debian Policy 3.3)
Your message dated Wed, 27 Jul 2016 11:18:42 + with message-id and subject line Bug#831816: fixed in jflex 1.6.1-1 has caused the Debian Bug report #831816, regarding jflex: no human maintainer Debian Policy 3.3 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.) -- 831816: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jflex Version: 1.4.3+dfsg-2 Severity: serious jflex is currently team-maintained but no human maintainer is listed in the Uploaders field. This is a violation of Debian Policy 3.3. I'm currently looking into upgrading the package to the latest upstream release, so this issue might be resolved soon. Markus --- End Message --- --- Begin Message --- Source: jflex Source-Version: 1.6.1-1 We believe that the bug you reported is fixed in the latest version of jflex, 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 831...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated jflex 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: Wed, 27 Jul 2016 06:48:48 +0200 Source: jflex Binary: jflex Architecture: source Version: 1.6.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Description: jflex - lexical analyzer generator for Java Closes: 831816 Changes: jflex (1.6.1-1) unstable; urgency=medium . * Imported Upstream version 1.6.1 * Update watch file. The project moved to Github. * Add get-orig-source target. * Update jflex.poms and use upstream's pom.xml file. * Move the package to Git. * Add myself to Uploaders. (Closes: #831816) * Remove debian/logo.gif because it is no longer needed for the docs. * Drop all patches because they are either obsolete or applied upstream. * Add build.patch and jflex-executable.patch to adjust build system and wrapper script for Debian. * Build-Depend on jflex and cup. * Add LexScan.flex.patch to fix FTBFS with the older version of JFlex. * Drop dirs file and remove dh_install override. Use install file instead. * Install changelog.md as upstream changelog. * Update debian/copyright to copyright format 1.0. * Depend on default-jre | java6-runtime because jflex requires a X11 environment. Compile the source code for Java 6 from now on which is de facto already the minimum requirement in Debian. Checksums-Sha1: dc8bf7361745953bf864acb9d69156d36eb516e1 2042 jflex_1.6.1-1.dsc cfbef0b8e36fb1724cc118331e4d91728fe1bca5 622684 jflex_1.6.1.orig.tar.xz ff11c4860f06498c311161b747cc2db1a3ef4ec3 6200 jflex_1.6.1-1.debian.tar.xz Checksums-Sha256: 1d7610d5a215e3be87ce1c612459292d0ccc3b3cdcc31217faac5fec1b80bea4 2042 jflex_1.6.1-1.dsc 79363e047b06620179ad0fadff96ec9e9a29ee97f4a1239e114c2495e87178de 622684 jflex_1.6.1.orig.tar.xz fa334d45d3174c3ccd703241fb8a37e3a3863f541ced242404c5072e7a7eaaa6 6200 jflex_1.6.1-1.debian.tar.xz Files: 1d8a4f3674a4aceefbc0469ea59fa3dd 2042 java optional jflex_1.6.1-1.dsc fc3b36a7cd5cef6cf6b1b08df3e69216 622684 java optional jflex_1.6.1.orig.tar.xz ab83e4e48124f9f0c7b0062806d22dae 6200 java optional jflex_1.6.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJXmJBEXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE OUFEMTRCOTUxM0I1MUU0AAoJENmtFLlRO1HkCQUP/iKWSR4oOxrJJbZEYgVzil+X UQAKjDTWHXj9T75K2bBb4JWplLwChhzd23W6recvMmj0LepvOEO5bGX/Yvlp/mTw cTrKH6fKZEtmNq05NU2dc8iRtS5BUH/GnmpeuV36MoUi57XPEJZX8bh31UByFehy Zs3NXGLvZx23frLh3qZfvgyDhA2JeINBNF8ukRzlubEZgve1TQU/3nYoLkEomJ84 sCcohqGHSCNAUuuFy94UGidJ/bsK8TgRMr6XbAMH1onFttiq1E/g8ykjH9FHBM0K PHgB0E29lt/gy/R5NlrNTNLqSqoQa+cwJSAPCY11y/l6VLlpryIIUycPZfPYXF0M T67mHVNicC6mB+GxwQXQZv0q8Xv746SDeaYxhRzk80W13XND5AHDVQVYE45Sc7vf dYKuDnjAPFMyxTgnxukdtZIfPiOqM3fT3sZZ4PrfqqpwQYW2fBswvIfRm4X+v9hJ jwi3f3L01L5AJ+y+LUoAp8b2LXWwIwIa88ouOJADL9xI0DdtXlk6o9OlE/D0+JKz wNY5EcW2K8fpUO803/dqXEQowp1jx2zk8aWbP99i73KYY8U/S2xfdAOpWqP3MeTl MYYjPq87lTWasmC/UjKVT8mtxdBinfrj3L77l+ojR5jngu74rEdvnQmcHFwqNRk/ QhL64L
Bug#830770: marked as done (mdadm: initramfs broken)
Your message dated Wed, 27 Jul 2016 10:37:25 +
with message-id
and subject line Bug#830770: fixed in mdadm 3.4-3
has caused the Debian Bug report #830770,
regarding mdadm: initramfs broken
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.)
--
830770: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830770
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mdadm
Version: 3.4-2
Severity: important
With 3.4-2 my lvm on partitioned md system has stopped initializing
correctly. For starters when upgrading from 3.4-1 to 3.4-2 I get
this:
W: mdadm: the array /dev/md/d0 with UUID 4c4bcb71:267c92fc:fe08e7ef:27569e0b
W: mdadm: is currently active, but it is not listed in mdadm.conf. if
W: mdadm: it is needed for boot, then YOUR SYSTEM IS NOW UNBOOTABLE!
W: mdadm: please inspect the output of /usr/share/mdadm/mkconf, compare
W: mdadm: it to /etc/mdadm/mdadm.conf, and make the necessary changes.
This is thanks to the change of:
if ! grep -qi "uuid=$uuid" $DESTMDADMCONF; then
to
if ! grep -q "UUID=$uuid" $DESTMDADMCONF; then
The manpage uses uuid=, the examples use both uuid= and UUID=, and the
uuid itself had better be treated as case-insensitive... so if you ask
me, it's cleaner and more correct, to just do:
uuid=`echo "$params" | grep -oi ' uuid=[0-9a-f:]\+'`
if ! grep -qi "$uuid" $DESTMDADMCONF; then
...
That said, this isn't why my system stopped booting after updating to
3.4-2, it's just an irritating distraction.
AFAICT, the new initramfs-tools scripts simply never assemble
any arrays. The old local-top/mdadm script ran either
$MDADM --assemble --scan --run --auto=yes${extra_args:+ $extra_args}
or $MDADM --assemble --scan --run --auto=yes $dev
depending on $MD_DEVS.
If run I mdadm --assemble --scan manually after the initramfs has
dumped me to a shell, and then keep kicking various lvm scripts until
I get my root device to show up, I can proceed, but this new package
strikes me as very, very broken.
Here's some of the blather from /usr/share/bug/mdadm/script but let me
prefix this with, I've pruned out detail that wasn't germane, and my
topology is lvm on top of md raid1 on a traditional sysvinit system.
--- mdadm.conf
DEVICE /dev/sd[ab]
HOMEHOST
MAILADDR root
ARRAY /dev/md/d0 metadata=1.0 UUID=4c4bcb71:267c92fc:fe08e7ef:27569e0b
name=cucamonga:d0
--- /etc/default/mdadm
AUTOCHECK=true
START_DAEMON=true
DAEMON_OPTIONS="--syslog"
VERBOSE=false
--- /proc/mdstat:
Personalities : [raid1]
md_d0 : active raid1 sda[0] sdb[1]
976762448 blocks super 1.0 [2/2] [UU]
unused devices:
--- /proc/partitions:
major minor #blocks name
80 976762584 sda
8 16 976762584 sdb
2530 976762448 md_d0
2531 968373248 md_d0p1
25328388176 md_d0p2
--- LVM physical volumes:
File descriptor 3 (/dev/pts/5) leaked on pvs invocation. Parent PID 16632:
/bin/bash
PV VG Fmt Attr PSize PFree
/dev/md_d0p1 S lvm2 a-- 923.51g 545.51g
--- /proc/modules:
dm_crypt 24576 1 - Live 0xa0222000
raid1 32768 1 - Live 0xa0016000
md_mod 98304 4 raid1, Live 0xa0021000
dm_mod 86016 26 dm_crypt, Live 0xa000
--- volume detail:
/dev/sda:
Magic : a92b4efc
Version : 1.0
Feature Map : 0x0
Array UUID : 4c4bcb71:267c92fc:fe08e7ef:27569e0b
Name : cucamonga:d0 (local to host cucamonga)
Creation Time : Fri Feb 11 07:29:10 2011
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 1953524896 (931.51 GiB 1000.20 GB)
Array Size : 976762448 (931.51 GiB 1000.20 GB)
Super Offset : 1953525152 sectors
Unused Space : before=0 sectors, after=256 sectors
State : clean
Device UUID : 03d87172:57951a8c:b9b40189:051ed01b
Update Time : Mon Jul 11 09:27:06 2016
Checksum : b10e71e7 - correct
Events : 2479
Device Role : Active device 0
Array State : AA ('A' == active, '.' == missing, 'R' == replacing)
--
/dev/sdb:
Magic : a92b4efc
Version : 1.0
Feature Map : 0x0
Array UUID : 4c4bcb71:267c92fc:fe08e7ef:27569e0b
Name : cucamonga:d0 (local to host cucamonga)
Creation Time : Fri Feb 11 07:29:10 2011
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 1953524896 (931.51 GiB 1000.20 GB)
Array Size : 976762448 (931.51 GiB 1000.20 GB)
Super Offset : 1953525152 sectors
Unused Space : before=0 sectors, after=256 sectors
State : clean
Device UUID : dcee8016:570d79ee:40fd87f0:26c35131
Update Time : Mon Jul 11 09:27:06 201
Bug#830300: marked as done (bug in mdadm)
Your message dated Wed, 27 Jul 2016 10:37:25 + with message-id and subject line Bug#830300: fixed in mdadm 3.4-3 has caused the Debian Bug report #830300, regarding bug in mdadm 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.) -- 830300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mdadm Version: 3.4-2 Severity: critical In the initrd image your script should source the /conf/param.conf. This brakes the boot of certain systems that depend on it (like mine). Here is the long explanation: In /scripts/init-premount/export_md_vars I have: #!/bin/sh # skip broken platform check in mdadm echo "Setting up envvars" if [ -d /conf ]; then echo "export IMSM_NO_PLATFORM=1" >> /conf/param.conf echo "Exported" fi That bypasses a check that is clearly wrong for my platform. Until last patch release it was working but now the system fails to boot. Please correct it or suggest a better place to insert the export. Thanks in advance, Luben Karavelov -- Package-specific info: --- mdadm.conf CREATE owner=root group=disk mode=0660 auto=yes HOMEHOST MAILADDR root ARRAY metadata=imsm UUID=518b7355:90f15f1b:d74e62c6:e0c9c9da ARRAY /dev/md/ASUS_OS container=518b7355:90f15f1b:d74e62c6:e0c9c9da member=0 UUID=6274cc4a:a22ed1d4:7a1173d6:f24c1fc7 --- /etc/default/mdadm AUTOCHECK=true START_DAEMON=true DAEMON_OPTIONS="--syslog" VERBOSE=false --- /proc/mdstat: Personalities : [raid0] md126 : active raid0 sda[1] sdb[0] 500113408 blocks super external:/md127/0 128k chunks md127 : inactive sda[1](S) sdb[0](S) 4520 blocks super external:imsm unused devices: --- /proc/partitions: major minor #blocks name 8 16 250059096 sdb 80 250059096 sda 9 126 500113408 md126 2590 102400 md126p1 2591 195584 md126p2 2592 99961856 md126p3 2593 19992576 md126p4 25947812096 md126p5 2595 372046848 md126p6 --- LVM physical volumes: LVM does not seem to be used. --- mount output sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=3794428k,nr_inodes=948607,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=760956k,mode=755) /dev/md126p3 on / type ext4 (rw,noatime,errors=remount-ro,stripe=64,data=ordered) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=27,pgrp=1,timeout=0,minproto=5,maxproto=5,direct) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) mqueue on /dev/mqueue type mqueue (rw,relatime) /dev/md126p4 on /var type ext4 (rw,noatime,nodiratime,discard,stripe=64,data=ordered) /dev/md126p2 on /boot type ext4 (rw,noatime,nodiratime,discard,stripe=256,data=ordered) /dev/md126p6 on /home type ext4 (rw,noatime,nodiratime,discard,stripe=64,data=ordered) /dev/md126p1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,
Bug#829488: marked as done (dist-upgrading while switching from openrc to file-rc is broken)
Your message dated Wed, 27 Jul 2016 10:06:25 + with message-id and subject line Bug#829488: fixed in openrc 0.21-2 has caused the Debian Bug report #829488, regarding dist-upgrading while switching from openrc to file-rc is broken 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.) -- 829488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openrc Version: 0.21-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'jessie'. It installed fine in 'jessie', then the upgrade to 'stretch' fails. >From the attached log (scroll to the bottom...): [...] Preparing to unpack .../util-linux_2.28-5_i386.deb ... Unpacking util-linux (2.28-5) over (2.25.2-6) ... Replacing files in old package initscripts (2.88dsf-59) ... Processing triggers for systemd (215-17+deb8u4) ... Setting up util-linux (2.28-5) ... Installing new version of config file /etc/init.d/hwclock.sh ... /var/lib/dpkg/info/util-linux.postinst: 35: /var/lib/dpkg/info/util-linux.postinst: update-rc.d: not found dpkg: error processing package util-linux (--configure): subprocess installed post-installation script returned error exit status 127 Processing triggers for systemd (215-17+deb8u4) ... Errors were encountered while processing: util-linux This seems to be related to openrc, since I haven't seen a similar failure without openrc installed. cheers, Andreas openrc_0.21-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: openrc Source-Version: 0.21-2 We believe that the bug you reported is fixed in the latest version of openrc, 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 829...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Benda Xu (supplier of updated openrc 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: Wed, 27 Jul 2016 16:04:40 +0900 Source: openrc Binary: openrc librc1 librc-dev libeinfo1 libeinfo-dev Architecture: source amd64 Version: 0.21-2 Distribution: unstable Urgency: medium Maintainer: OpenRC Debian Maintainers Changed-By: Benda Xu Description: libeinfo-dev - dependency based service manager (pretty control display developm libeinfo1 - dependency based service manager (pretty console display library) librc-dev - dependency based service manager (runtime development) librc1 - dependency based service manager (runtime library) openrc - dependency based service manager (runlevel change mechanism) Closes: 829488 Changes: openrc (0.21-2) unstable; urgency=medium . * Move Recommends init-system-helpers to Pre-Depend (Closes: 829488). * Drop Provides sysv-rc. * Install transit into /etc/init.d directly. Checksums-Sha1: da75bbf2bef5f213943e6956b8c4d45b699f79c8 2194 openrc_0.21-2.dsc 39166c0b56a9ddde70280b2d6ea572fd6a4aee29 23356 openrc_0.21-2.debian.tar.xz 2513dc8209be069275ee24043402a256f32e8a1d 11550 libeinfo-dev_0.21-2_amd64.deb 93a83ed570ed7922fa641153457ab462e5df1be3 16096 libeinfo1-dbgsym_0.21-2_amd64.deb b5a69a1d217862b169f6a1d7de654a5526aee756 15054 libeinfo1_0.21-2_amd64.deb 055028e835f75b0740358cb928f3cf5a1999f72f 21448 librc-dev_0.21-2_amd64.deb 22933c169cc0db48a7099fd65833ea08f18fd9f6 69398 librc1-dbgsym_0.21-2_amd64.deb 61784afe44dd6457100b2b6ef8fe200adbdb89c7 32130 librc1_0.21-2_amd64.deb d689d1e29ce334f36512790c8bf9a3f25a9b01fc 332762 openrc-dbgsym_0.21-2_amd64.deb 83208b05c631cea9d7307c2f897be463b597ff7e 120068 openrc_0.21-2_amd64.deb Checksums-Sha256: 380df234d34b7ee7ca6643e0a802397fb520ac09d5044c85cca868a4bd519cd7 2194 openrc_0.21-2.dsc 2ae858cfb15ae3a00a00955cde12d88cc51c1ab8e80b438fe85a96f394d8fd5a 23356 openrc_0.21-2.debian.tar.xz 9ad6e675e6cc784a4cd6e52b7dd79228cf3b5f82aa52ec18dc7692557a7deda9 11550 libeinfo-dev_0.21-2_amd64.deb c1f87593b120c439b1d2ceaae223e4649e17ac6b1ba9fb356dc66e26c49963c8 16096 libeinfo1-dbgsym_0.21-2_amd64.deb dacc4e09ca666542c7f9aa34e6d9b05ad11f7eb37ff4d8d7c4d33390da3c7030 15054 libeinfo1_0.21-2_amd64.deb 2
Bug#831210: marked as done (squirrel3: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors)
Your message dated Wed, 27 Jul 2016 10:07:25 + with message-id and subject line Bug#831210: fixed in squirrel3 3.1-4 has caused the Debian Bug report #831210, regarding squirrel3: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors 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.) -- 831210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: squirrel3 Version: 3.1-3 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160713 qa-ftbfs Justification: FTBFS with GCC 6 on amd64 Hi, During a rebuild of all packages in sid using the gcc-defaults package available in experimental to make GCC default to version 6, your package failed to build on amd64. For more information about GCC 6 and Stretch, see: - https://wiki.debian.org/GCC6 - https://lists.debian.org/debian-devel-announce/2016/06/msg7.html Relevant part (hopefully): > make[1]: Entering directory '/«PKGBUILDDIR»' > dh_compress -X.pdf > make[1]: Leaving directory '/«PKGBUILDDIR»' >dh_fixperms -a >dh_strip -a >dh_makeshlibs -a > dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libsquirrel3-0/DEBIAN/symbols doesn't match > completely debian/libsquirrel3-0.symbols.amd64 > --- debian/libsquirrel3-0.symbols.amd64 (libsquirrel3-0_3.1-3_amd64) > +++ dpkg-gensymbolsWCPy2O 2016-07-13 19:27:49.06400 + > @@ -110,7 +110,7 @@ > (c++)"SQClass::SQClass(SQSharedState*, SQClass*)@Base" 3.1 > (c++)"SQClass::SetAttributes(SQObjectPtr const&, SQObjectPtr const&)@Base" > 3.1 > (c++)"SQClass::~SQClass()@Base" 3.1 > - (c++)"SQClosure::Create(SQSharedState*, SQFunctionProto*, SQWeakRef*)@Base" > 3.1 > +#MISSING: 3.1-3# (c++)"SQClosure::Create(SQSharedState*, SQFunctionProto*, > SQWeakRef*)@Base" 3.1 > (c++)"SQClosure::Finalize()@Base" 3.1 > (c++)"SQClosure::GetType()@Base" 3.1 > (c++)"SQClosure::Load(SQVM*, void*, long long (*)(void*, void*, long long), > SQObjectPtr&)@Base" 3.1 > @@ -240,7 +240,7 @@ > (c++)"SQNativeClosure::Release()@Base" 3.1 > (c++)"SQNativeClosure::~SQNativeClosure()@Base" 3.1 > (c++)"SQObjectPtr::operator=(SQObjectPtr const&)@Base" 3.1 > - (c++)"SQObjectPtr::operator=(long long)@Base" 3.1 > +#MISSING: 3.1-3# (c++)"SQObjectPtr::operator=(long long)@Base" 3.1 > (c++)"SQObjectPtr::operator=(tagSQObject const&)@Base" 3.1 > (c++)"SQObjectPtr::~SQObjectPtr()@Base" 3.1 > (c++)"SQOuter::Finalize()@Base" 3.1 > dh_makeshlibs: failing due to earlier errors > make: *** [binary-arch] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2016/07/13/squirrel3_3.1-3_unstable_gcc6.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 --- --- Begin Message --- Source: squirrel3 Source-Version: 3.1-4 We believe that the bug you reported is fixed in the latest version of squirrel3, 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 831...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabian Wolff (supplier of updated squirrel3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 22 Jul 2016 13:43:59 +0200 Source: squirrel3 Binary: squirrel3 libsquirrel3-0 libsquirrel-dev Architecture: source Version: 3.1-4 Distribution: unstable Urgency: medium Maintainer: Fabian Wolff Changed-By: Fabian Wolff Closes: 831210 Description: libsquirrel3-0 - runtime libraries for the Squirrel programming language libsquirrel-dev - development files for the Squirrel programming language squirrel3 - lightweight, high-level, embeddable programming language Changes: squirrel3 (3.1-4) unstable; urgency=medium . * Delete libsquirrel3-0.symbols.amd64 (Closes: #831210).
Bug#832582: marked as done (update-rc.d foo disable broken without insserv)
Your message dated Wed, 27 Jul 2016 10:05:33 +
with message-id
and subject line Bug#832582: fixed in init-system-helpers 1.41
has caused the Debian Bug report #832582,
regarding update-rc.d foo disable broken without insserv
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.)
--
832582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: init-system-helpers
Version: 1.40
Severity: serious
In the latest upload, we dropped the insserv dependency and added some
fallback code for SysV init scripts for the case where insserv is not
installed [1].
Unfortunately, the disable case is not handled correctly. It removes all
symlinks:
# for "disable" we cannot rely on the init script still being present, as
# this gets called in postrm for purging. Just remove all symlinks.
if ("disable" eq $action) { unlink($_) for
glob("/etc/rc?.d/[SK][0-9][0-9]$scriptname"); return; }
On package upgrades, the SysV init script gets enabled again via
update-rc.d foo defaults. This means
1/ For SysV only service, we enable and start a service, overriding the
admins settings.
2/ For a package with native service files and a SysV init script, the
state gets out of sync.
I consider 1/ a blocker, which is why I'm marking this as RC.
The correct why to handle disable a SysV init script, is to turn
existing S symlinks in runlevel S,2,3,4,5 into K symlinks.
For this we don't need the LSB header, we simply have to check for the
existence symlinks on the disk.
The update-rc.d man page says that the sequence number of the K symlink
should be 100 minus the priority of the S symlink.
For simplicities reason, I would simply turn S symlinks into K01
symlinks.
Enable would be the reverse action. We check in runlevels S,2,3,4,5 for
K symlinks and turn them into S symlinks.
Again, I would just use priority S01 here.
So, a disable + enable on service foo might change the priority of that
SysV init script, but under systemd those priorities are ignored and if
sysvinit-core is installed, it will pull in insserv which will correct
the priorities. So we do not lose any relevant (admin) configuration.
Regards,
Michael
[1]
http://anonscm.debian.org/cgit/collab-maint/init-system-helpers.git/commit/?id=f51e81cabe
-- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages init-system-helpers depends on:
ii perl-base 5.22.2-3
init-system-helpers recommends no packages.
init-system-helpers suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: init-system-helpers
Source-Version: 1.41
We believe that the bug you reported is fixed in the latest version of
init-system-helpers, 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 832...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Biebl (supplier of updated init-system-helpers
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: Wed, 27 Jul 2016 11:42:54 +0200
Source: init-system-helpers
Binary: init-system-helpers dh-systemd init
Architecture: source
Version: 1.41
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers
Changed-By: Michael Biebl
Description:
dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
init - init metapackage
init-system-helpers - helper tools for all init systems
Closes: 832582
Changes:
init-system-helpers (1.41) unstable; urgency=medium
.
* update-rc.d: Properly handle enable|disable for SysV init scripts if
insserv is not available. (Closes: #832582)
Checksums-Sha1:
4298cac09e2e5f589de05e34986f9184f51a2b72 1916 init-system-helpers_1.41.dsc
9af9eb9008b770ef21aa43ad74ed5ab51ad620c7 41756 init-system
Bug#832390: marked as done (libgd2: FTBFS on *i386: FAIL: gdimagerotate/bug00067)
Your message dated Wed, 27 Jul 2016 10:05:48 + with message-id and subject line Bug#832390: fixed in libgd2 2.2.3-2 has caused the Debian Bug report #832390, regarding libgd2: FTBFS on *i386: FAIL: gdimagerotate/bug00067 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.) -- 832390: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libgd2 Version: 2.2.2-43-g22cba39-1 Severity: serious Dear Maintainer, Your package fails to build on i386, kfreebsd-i386 and hurd-i386 with the same testsuite failure, while it builds fine everywhere else: | FAIL: gdimagerotate/bug00067 | | | gdimagerotate/bug00067.c:46: Total pixels changed: 14143 with a maximum channel difference of 255. | gdimagerotate/bug00067.c:47: comparing rotated image to ./gdimagerotate/bug00067_150_exp.png failed. | FAIL gdimagerotate/bug00067 (exit status: 1) A full build log is available here: https://buildd.debian.org/status/fetch.php?pkg=libgd2&arch=i386&ver=2.2.2-43-g22cba39-1&stamp=1469396971 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: libgd2 Source-Version: 2.2.3-2 We believe that the bug you reported is fixed in the latest version of libgd2, 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 832...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý (supplier of updated libgd2 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: Wed, 27 Jul 2016 09:12:12 +0200 Source: libgd2 Binary: libgd-tools libgd-dev libgd3 libgd-dbg Architecture: source Version: 2.2.3-2 Distribution: unstable Urgency: medium Maintainer: GD team Changed-By: Ondřej Surý Description: libgd-dbg - Debug symbols for GD Graphics Library libgd-dev - GD Graphics Library (development version) libgd-tools - GD command line tools and example code libgd3 - GD Graphics Library Closes: 832390 Changes: libgd2 (2.2.3-2) unstable; urgency=medium . * Remove the failing test from the test suite rather than juggling with architecture tests (Closes: #832390) Checksums-Sha1: 8e36635936447d941408fc18cb96e02c0d849fbb 2326 libgd2_2.2.3-2.dsc 9ac35d2cdf1b4b526e0a092b20fffda3f345 23628 libgd2_2.2.3-2.debian.tar.xz Checksums-Sha256: 3e43d18109d72d8a74cd364a219ed65c53a49ab5f4a889e9dc3d8759bf085eca 2326 libgd2_2.2.3-2.dsc cda1983022ee0936ba7460dba0d095f8b5380b835e103bc836164bb5ceb942f7 23628 libgd2_2.2.3-2.debian.tar.xz Files: 7c846b4b3ec9aeced25ac9107a7ea3d3 2326 graphics optional libgd2_2.2.3-2.dsc 0899efb7c277cb9836f49af4eeb9d71b 23628 graphics optional libgd2_2.2.3-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXmHQdXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH7BAQAJ5bMV5iOm55zZ0dWNxxfIeO slhwM7VY+L6UCElpBRHeK34SsPSQOdtSCikyMjDHk9feBIkpJpB9Pz4NOb14BfAI +vGtYErz8ygEw8jBjAkhOq4hUlDgY3D2AXvu4faN3nSRCD5JXlVxgC60Pluxlgwc +xB8zMY9j/KWcO1VGjodfS9WFk9TRnsxLHI2uhxAK4AmfFJnLbsSZ9q0vcAAH6lx AV5hfCWLUCLl3Sv/GR9QIpopBpie6GPKIOvqgq5CFHvLYh+Yeqkqxbu7w/UT3IXw 7j1fzqt36OtPOirZAkl3kQvKeNWijqNZy/Qny1tyfKYunL7T+B6Ei0JIoLwMmxLA TFcNvZkFN9F6rgTyhAzXgFUZTfy813KtvGQpJf3xJeYpnG3vMBYeuY4YoImEmmbG MMTdPIZ2Z69oJK73xW9XAK9VHYTugDbPA7+gzrjdVNs1aKLQUwfEh3CCREt5pNuN 9Gpgi2+l7pwLh9TUdL4M6rsQ5mpBDvZ1gdARMotloWV28OTjptEnvcj5ttdBgjUG xPwjKDrKDDL9LQswuQjRzM3WviLc0vV3FXAJJzk5seTBMJgwp4UfMaSlrK8iIORC y6MXmzk6GdRW2VXUt6OCWqqqGCODZNWBWZ6NgnzBmTNczkLNzSZOP/F3SnJ/bZZ9 2+3QT0lfZ58jEVQEv4WK =xSJT -END PGP SIGNATURE End Message ---
Bug#811940: marked as done (infinipath-psm: FTBFS with GCC 6: defined but not used)
Your message dated Wed, 27 Jul 2016 10:05:29 + with message-id and subject line Bug#811940: fixed in infinipath-psm 3.3+19.g67c0807.open-2 has caused the Debian Bug report #811940, regarding infinipath-psm: FTBFS with GCC 6: defined but not used 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.) -- 811940: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: infinipath-psm Version: 3.3+7.gec1d6d2-3 Severity: important User: debian-...@lists.debian.org Usertags: ftbfs-gcc-6 gcc-6-unused-const-variable This package fails to build with GCC 6. GCC 6 has not been released yet, but it's expected that GCC 6 will become the default compiler for stretch. Note that only the first error is reported; there might be more. You can find a snapshot of GCC 6 in experimental. To build with GCC 6, you can set CC=gcc-6 CXX=g++-6 explicitly. You may be able to find out more about this issue at https://gcc.gnu.org/gcc-6/changes.html > sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux ... > cc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall > -Werror -fpic -fPIC -D_GNU_SOURCE -funwind-tables -O3 -g3 -DNVALGRIND > -Wall -Werror -fpic -fPIC -D_GNU_SOURCE -funwind-tables -O3 -g3 > -DPSM_USE_SYS_UUID -DNVALGRIND -I. > -I/<>/infinipath-psm-3.3+7.gec1d6d2/include > -I/<>/infinipath-psm-3.3+7.gec1d6d2/mpspawn > -I/<>/infinipath-psm-3.3+7.gec1d6d2/include/linux-x86_64 > -I/<>/infinipath-psm-3.3+7.gec1d6d2 -c am_reqrep.c -o am_reqrep.o > In file included from > /<>/infinipath-psm-3.3+7.gec1d6d2/psm_user.h:51:0, > from am_reqrep.c:35: > /<>/infinipath-psm-3.3+7.gec1d6d2/psm_help.h:131:62: error: > '__psm_ss_amsh_qtail_info_t' defined but not used > [-Werror=unused-const-variable] > #define PSMI_STRICT_SIZE_DECL(member,sz) static const size_t __psm_ss_ ## > member = sz > ^ > > psm_am_internal.h:425:1: note: in expansion of macro 'PSMI_STRICT_SIZE_DECL' > PSMI_STRICT_SIZE_DECL(amsh_qtail_info_t,64); > ^ > > /<>/infinipath-psm-3.3+7.gec1d6d2/psm_help.h:131:62: error: > '__psm_ss_am_ctl_blockhdr_t' defined but not used > [-Werror=unused-const-variable] > #define PSMI_STRICT_SIZE_DECL(member,sz) static const size_t __psm_ss_ ## > member = sz > ^ > > psm_am_internal.h:351:1: note: in expansion of macro 'PSMI_STRICT_SIZE_DECL' > PSMI_STRICT_SIZE_DECL(am_ctl_blockhdr_t,128*3); > ^ > > /<>/infinipath-psm-3.3+7.gec1d6d2/psm_help.h:131:62: error: > '__psm_ss_am_ctl_qhdr_t' defined but not used [-Werror=unused-const-variable] > #define PSMI_STRICT_SIZE_DECL(member,sz) static const size_t __psm_ss_ ## > member = sz > ^ > > psm_am_internal.h:338:1: note: in expansion of macro 'PSMI_STRICT_SIZE_DECL' > PSMI_STRICT_SIZE_DECL(am_ctl_qhdr_t,128); > ^ > > /<>/infinipath-psm-3.3+7.gec1d6d2/psm_help.h:131:62: error: > '__psm_ss_am_pkt_short_t' defined but not used [-Werror=unused-const-variable] > #define PSMI_STRICT_SIZE_DECL(member,sz) static const size_t __psm_ss_ ## > member = sz > ^ > > psm_am_internal.h:308:1: note: in expansion of macro 'PSMI_STRICT_SIZE_DECL' > PSMI_STRICT_SIZE_DECL(am_pkt_short_t,64); -- Martin Michlmayr Linux for HPE Helion, Hewlett Packard Enterprise --- End Message --- --- Begin Message --- Source: infinipath-psm Source-Version: 3.3+19.g67c0807.open-2 We believe that the bug you reported is fixed in the latest version of infinipath-psm, 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 811...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ana Beatriz Guerrero Lopez (supplier of updated infinipath-psm 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: Wed, 27 Jul 2016 00:57:22 +0200 Source: infinipath-psm Binary: libpsm-infinipath1 libpsm-infi
Bug#832578: cpl-plugin-visir: does not work with packaged swarp
Since SWarp upstream seems to move to Github: https://github.com/astromatic (psfex is already there) there is some hope that they will be a bit more transparent then now [1]. Therefore it may be useful to have them ready for that day. And since you are already using some RCS internally, it would probably be easy to extract the SWarp related changes and put them somewhere. They may be still a hint for someone who runs into similar problems. Best regards Ole [1] you may put "transparency" also onto ESO development's wishlist, BTW ;-)
Bug#832578: cpl-plugin-visir: does not work with packaged swarp
I agree that the patches should be more easily extractable, this was originally planned but time constrains did not allow this for the last two releases, hopefully next time the changes will be included as separate patch files. The patches are for the most part incomplete and not upstreamable as they fix the bugs only for the configuration used by visir or add a feature only in points visir needs it. There has not been time to generalize and test them for the many ways swarp can be used. The last time this was done it was promptly broken again in the next code dump so motivation is low to do so again.
Bug#832589: nvidia-cuda-toolkit: FTBFS when built with dpkg-buildpackage -A (Missing build-indep target)
Package: src:nvidia-cuda-toolkit Version: 7.5.18-2 Severity: serious Dear maintainer: I tried to build this package with "dpkg-buildpackage -A" (i.e. only architecture-independent packages), and it failed: [...] debian/rules build-indep make: *** No rule to make target 'build-indep'. Stop. dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2 This prevents the package from being uploaded in source-only form (which I see you already do). This kind of bug is now considered RC (see Bug #830997 for details), but being this such a big package (more than 1 GB), I'd say it is in your own interest to fix it, so that you can continue to upload the package in source-only form. Thanks.
Bug#832568: [Android-tools-devel] Bug#832568: apktool fails to run on Java 7 because it was compiled to target Java 8
Control: reassign -1 libsmali-java Control: retitle -1 libsmali-java: use source target Java 6 On 27.07.2016 02:42, Simon Ruggier wrote: > Package: apktool > Version: 2.1.1+dfsg-2 > Severity: serious > Justification: Policy 3.5 > > I just installed apktool, and when I run it, it fails like so: > $ apktool > Exception in thread "main" java.lang.UnsupportedClassVersionError: > org/jf/baksmali/baksmali : Unsupported major.minor version 52.0 Hi, actually this is a bug in libsmali-java, one of apktool's dependencies. Markus signature.asc Description: OpenPGP digital signature
Processed: Re: [Android-tools-devel] Bug#832568: apktool fails to run on Java 7 because it was compiled to target Java 8
Processing control commands: > reassign -1 libsmali-java Bug #832568 [apktool] apktool fails to run on Java 7 because it was compiled to target Java 8 Bug reassigned from package 'apktool' to 'libsmali-java'. No longer marked as found in versions apktool/2.1.1+dfsg-2. Ignoring request to alter fixed versions of bug #832568 to the same values previously set > retitle -1 libsmali-java: use source target Java 6 Bug #832568 [libsmali-java] apktool fails to run on Java 7 because it was compiled to target Java 8 Changed Bug title to 'libsmali-java: use source target Java 6' from 'apktool fails to run on Java 7 because it was compiled to target Java 8'. -- 832568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity
Processing commands for cont...@bugs.debian.org: > severity 825121 important Bug #825121 [libradcli4] libradcli4: prompting due to modified conffiles which were not modified by the user: /etc/radcli/dictionary Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 825121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825121 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#832582: update-rc.d foo disable broken without insserv
Package: init-system-helpers
Version: 1.40
Severity: serious
In the latest upload, we dropped the insserv dependency and added some
fallback code for SysV init scripts for the case where insserv is not
installed [1].
Unfortunately, the disable case is not handled correctly. It removes all
symlinks:
# for "disable" we cannot rely on the init script still being present, as
# this gets called in postrm for purging. Just remove all symlinks.
if ("disable" eq $action) { unlink($_) for
glob("/etc/rc?.d/[SK][0-9][0-9]$scriptname"); return; }
On package upgrades, the SysV init script gets enabled again via
update-rc.d foo defaults. This means
1/ For SysV only service, we enable and start a service, overriding the
admins settings.
2/ For a package with native service files and a SysV init script, the
state gets out of sync.
I consider 1/ a blocker, which is why I'm marking this as RC.
The correct why to handle disable a SysV init script, is to turn
existing S symlinks in runlevel S,2,3,4,5 into K symlinks.
For this we don't need the LSB header, we simply have to check for the
existence symlinks on the disk.
The update-rc.d man page says that the sequence number of the K symlink
should be 100 minus the priority of the S symlink.
For simplicities reason, I would simply turn S symlinks into K01
symlinks.
Enable would be the reverse action. We check in runlevels S,2,3,4,5 for
K symlinks and turn them into S symlinks.
Again, I would just use priority S01 here.
So, a disable + enable on service foo might change the priority of that
SysV init script, but under systemd those priorities are ignored and if
sysvinit-core is installed, it will pull in insserv which will correct
the priorities. So we do not lose any relevant (admin) configuration.
Regards,
Michael
[1]
http://anonscm.debian.org/cgit/collab-maint/init-system-helpers.git/commit/?id=f51e81cabe
-- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages init-system-helpers depends on:
ii perl-base 5.22.2-3
init-system-helpers recommends no packages.
init-system-helpers suggests no packages.
-- no debconf information
Bug#832578: cpl-plugin-visir: does not work with packaged swarp
Hi Julian, you are right; it is probably the best to include the patched swarp in the package as long as the packaged version does not do the job jere. Although I know that SWarp's upstream is not very responsive: could you please document the bugs you found with Swarp somewhere publicely, together with the fixes you use? The same for your feature extensions. It is quite hard to extract them by comparing the sources in cpl-plugin-visir with the original sources. And having an undocumented hidden fork in some software (be it packaged for Debian or not) is IMO quite ugly. At least the bug fixes may be worth to be applied to the SWarp Debian package so that others could benefit here as well. Best regards Ole
Bug#832578: cpl-plugin-visir: does not work with packaged swarp
Package: cpl-plugin-visir Version: 4.3.0+dfsg-1 Severity: serious I have already told you in the past that visir does not work with the packaged swarp. The swarp included in visir is patched to behave as the pipeline needs it. There are also feature patches which go beyond the bugfix patches I have already told you about. To test this run esorex visir_img_reduce sof with sof: img/drs/burst-NEII/IRAS21032-0024-NEII-182_0245.fits BURST img/drs/burst-NEII/IRAS21032-0024-NEII-182_0246.fits BURST from the demo data. To my big surprise it does not crash but the results are still wrong. Check the error extension of the visir_util_join_bCOMBINED.fits, it has an average 200 while it should be around 10. So I repeat, please use the bundled swarp or remove the package from the archive. cheers, Julian
Bug#828119: marked as pending
tag 828119 pending thanks Hello, Bug #828119 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=python-modules/packages/twill.git;a=commitdiff;h=155cfed --- commit 155cfeded3fbbea2367f0bb7b25d9329a4aee63a Author: Arnaud Fontaine Date: Wed Jul 27 15:53:41 2016 +0900 d/rules: CDBS DEB_PYTHON_MODULE_PACKAGE has been removed. Closes: #828119. diff --git a/debian/changelog b/debian/changelog index fa86ddd..06e39a3 100644 --- a/debian/changelog +++ b/debian/changelog @@ -10,6 +10,7 @@ twill (0.9-4) UNRELEASED; urgency=low * d/control: + Bump Standards-Version to 3.9.8. No change needed. + debhelper compatibility version 5 is not recommended anymore. + * d/rules: CDBS DEB_PYTHON_MODULE_PACKAGE has been removed. Closes: #828119. -- Arnaud Fontaine Wed, 27 Jul 2016 15:51:25 +0900
Processed: Bug#828119 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 828119 pending Bug #828119 [src:twill] twill: FTBFS: debian/twill-fork.1: No such file or directory at /usr/bin/dh_installman line 131. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 828119: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#828119: marked as done (twill: FTBFS: debian/twill-fork.1: No such file or directory at /usr/bin/dh_installman line 131.)
Your message dated Wed, 27 Jul 2016 07:33:45 + with message-id and subject line Bug#828119: fixed in twill 0.9-4 has caused the Debian Bug report #828119, regarding twill: FTBFS: debian/twill-fork.1: No such file or directory at /usr/bin/dh_installman line 131. 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.) -- 828119: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: twill Version: 0.9-3 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, twill fails to build from source in unstable/amd64: [..] ** ** Starting build ** ** Package: twill Version: 0.9-3 Build architecture: amd64 Date: Sat, 25 Jun 2016 08:32:55 +0200 Hostname: b25e65075ed8 Uname:Linux b25e65075ed8 4.5.0-2-amd64 #1 SMP Debian 4.5.4-1 (2016-05-16) x86_64 GNU/Linux /etc/timezone:Africa/Johannesburg ** ** Installing build dependencies ** ** dh_testdir dh_testroot dh_prep dh_testdir dh_testroot dh_install dh_installdocs dh_installchangelogs dh_compress dh_fixperms dh_installdeb dh_gencontrol dh_md5sums dh_builddeb dpkg-deb: building package 'twill-build-deps' in '../twill-build-deps_0.9-3_all.deb'. The package has been created. Attention, the package has been created in the current directory, not in ".." as indicated by the message above! Selecting previously unselected package twill-build-deps. (Reading database ... 23074 files and directories currently installed.) Preparing to unpack twill-build-deps_0.9-3_all.deb ... Unpacking twill-build-deps (0.9-3) ... Reading package lists... Building dependency tree... Reading state information... Correcting dependencies... Done The following additional packages will be installed: cdbs docbook-xml docbook-xsl libxslt1.1 sgml-base sgml-data xml-core xsltproc Suggested packages: docbook docbook-dsssl docbook-defguide dbtoepub docbook-xsl-doc-html | docbook-xsl-doc-pdf | docbook-xsl-doc-text | docbook-xsl-doc docbook-xsl-saxon fop libsaxon-java libxalan2-java libxslthl-java xalan sgml-base-doc perlsgml w3-recs opensp libxml2-utils The following NEW packages will be installed: cdbs docbook-xml docbook-xsl libxslt1.1 sgml-base sgml-data xml-core xsltproc 0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 1982 kB of archives. After this operation, 20.1 MB of additional disk space will be used. Get:1 http://httpredir.debian.org/debian sid/main amd64 cdbs all 0.4.142 [80.7 kB] Get:2 http://httpredir.debian.org/debian sid/main amd64 libxslt1.1 amd64 1.1.28-4 [231 kB] Get:3 http://httpredir.debian.org/debian sid/main amd64 xsltproc amd64 1.1.28-4 [118 kB] Get:4 http://httpredir.debian.org/debian sid/main amd64 sgml-base all 1.28 [14.7 kB] Get:5 http://httpredir.debian.org/debian sid/main amd64 xml-core all 0.13+nmu2 [24.2 kB] Get:6 http://httpredir.debian.org/debian sid/main amd64 docbook-xsl all 1.79.1+dfsg-1 [1249 kB] Get:7 http://httpredir.debian.org/debian sid/main amd64 sgml-data all 2.0.10 [181 kB] Get:8 http://httpredir.debian.org/debian sid/main amd64 docbook-xml all 4.5-7.3 [83.3 kB] Fetched 1982 kB in 0s (49.4 MB/s) Selecting previously unselected package cdbs. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading databas
