Bug#862154: wolfssl: CVE-2017-2800 / TALOS-2017-0293
Source: wolfssl Version: 3.10.2+dfsg-2 Severity: grave Tags: upstream security Hi, the following vulnerability was published for wolfssl. CVE-2017-2800[0]: No description was found (try on a search engine) If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-2800 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2800 [1] http://www.talosintelligence.com/reports/TALOS-2017-0293/ Regards, Salvatore
Bug#862098: marked as done (lxterminal: CVE-2016-10369: socket can be blocked by another user)
Your message dated Tue, 09 May 2017 06:34:08 + with message-id and subject line Bug#862098: fixed in lxterminal 0.3.0-2 has caused the Debian Bug report #862098, regarding lxterminal: CVE-2016-10369: socket can be blocked by another user 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.) -- 862098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lxterminal Version: 0.3.0-1 Severity: grave Tags: upstream patch security Justification: user security hole -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 This vulnerability is discussed in a Stackexchange website: https://unix.stackexchange.com/questions/333539/lxterminal-in-the-netstat-output/333578 The socket placed in /tmp is predictable and public-writable, Therefore if Alice placed a file or lxterminal socket in /tmp/.lxterminal-socket:0-bob, bob is unable to open lxterminal, or open a lxterminal instance for Alice. This bug is fixed in the commit: https://git.lxde.org/gitweb/?p=lxde/lxterminal.git;a=commit;h=f99163c6ff8b2f57c5f37b1ce5d62cf7450d4648 - -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lxterminal depends on: ii libatk1.0-0 2.22.0-1 ii libc62.24-10 ii libcairo21.14.8-1 ii libfontconfig1 2.11.0-6.7+b1 ii libfreetype6 2.6.3-3.2 ii libgdk-pixbuf2.0-0 2.36.5-2 ii libglib2.0-0 2.50.3-2 ii libgtk2.0-0 2.24.31-2 ii libpango-1.0-0 1.40.5-1 ii libpangocairo-1.0-0 1.40.5-1 ii libpangoft2-1.0-01.40.5-1 ii libvte9 1:0.28.2-5+b2 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 lxterminal recommends no packages. lxterminal suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQJCBAEBCAAsFiEE/tVDSEUoffJikxSJz7v84LdPGxQFAlkQbdkOHG13ZWlAbHhk ZS5vcmcACgkQz7v84LdPGxSZuA/+NEEhU73k2esU8FveOzTc0ei0b5NLC2y5zvY/ /To8BTaUJAQE3J1icvgV3JRPJI8YOin5Ombz1n+4URt+f17G00mWplyGQgFiXcKP oooPl93If2rfi3POFM3MoC6grRc5UdwpUcTimwaX4OEE/PUZNHnfoNI2pWPk0Z34 AcGVqbJzxagpqzwvzsjjHC2EOncSeTfm2nZzUIwWfXV+LdGgq2Sf2oyaAYH/QnuV bvGAGgCZCNFejn9m3VHA7SIEU8AV+/FaJ/8sT5WJIyWWBoEBkcig50Ya5UG71zVq VTixWAbnCLhfQ44xKsFvGD+h6LH4c6qgQxnxk16yQrUOAZsIFHDuc9xIMBJtGLJt G3hZFY7x0sry4GVgHdqDvxI51UgWuZuUJNTTtXOuu0Yno0gcwY8TCC3QBtIk+4kQ 61tTbNoho7wTjn8reY+SgcUXeLdUAbKXdcv3IOp25LmiPLHV5dGfnRXH8Gw/ZQCz B9Tli0Ge3yNXaC0MJzgyaopNPdqzBNII5IWwfjknVy6K6uQCiHx9UCbOfxDre9sp DbgENkagS5P8+lNVOtGHr55n/2bg+kKLOztOKBBp0vqdwaKnKAuE0BZfOx78msgs P+vGhzOARu/y2V/n4AAPPiE9SlRZIQg+oX1+5syzXiRD2dLOUbXqRLmVZwaqLsKG 0oN43Nk= =fmHh -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: lxterminal Source-Version: 0.3.0-2 We believe that the bug you reported is fixed in the latest version of lxterminal, 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 862...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yao Wei (魏銘廷) (supplier of updated lxterminal 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: Tue, 09 May 2017 12:13:07 +0800 Source: lxterminal Binary: lxterminal lxterminal-dbg Architecture: source Version: 0.3.0-2 Distribution: unstable Urgency: high Maintainer: Debian LXDE Maintainers Changed-By: Yao Wei (魏銘廷) Description: lxterminal - LXDE terminal emulator lxterminal-dbg - LXDE terminal emulator (debug) Closes: 862096 862098 Changes: lxterminal (0.3.0-2) unstable; urgency=high . * Fix improper use of /tmp for a socket file. (CVE-2016-10369) (Closes: #862098) * Fix tab renaming dialog. (Closes: #862096) Checksums-Sha1: 31a95d70463145b8aad662f4ce2dfea74743c901 2124 lxterminal_0.3.0-2.dsc a24fd7df8742321d1a5ad828ccb397333e8e406f 7320 lxterminal_0.3.0-2.debian.tar.xz b1cada92dcd40aec33d39efb0553ad101b1cd836 11218 lxterminal_0.3.0-2_source.
Bug#860225: marked as done (bind9: CVE-2017-3137: A response packet can cause a resolver to terminate when processing an answer containing a CNAME or DNAME)
Your message dated Tue, 09 May 2017 04:48:34 + with message-id and subject line Bug#860225: fixed in bind9 1:9.10.3.dfsg.P4-12.3 has caused the Debian Bug report #860225, regarding bind9: CVE-2017-3137: A response packet can cause a resolver to terminate when processing an answer containing a CNAME or DNAME 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.) -- 860225: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860225 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bind9 Version: 1:9.9.5.dfsg-9 Severity: grave Tags: patch upstream security fixed-upstream Hi, the following vulnerability was published for bind9. CVE-2017-3137[0]: |A response packet can cause a resolver to terminate when processing an |answer containing a CNAME or DNAME If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-3137 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3137 [1] https://kb.isc.org/article/AA-01466 Please adjust the affected versions in the BTS as needed. Regards, Salvatore -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) 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: sysvinit (via /sbin/init) --- End Message --- --- Begin Message --- Source: bind9 Source-Version: 1:9.10.3.dfsg.P4-12.3 We believe that the bug you reported is fixed in the latest version of bind9, 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 860...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated bind9 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 May 2017 15:22:46 +0200 Source: bind9 Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-140 libdns162 libirs141 libisc160 liblwres141 libisccc140 libisccfg140 dnsutils lwresd libbind-export-dev libdns-export162 libdns-export162-udeb libisc-export160 libisc-export160-udeb libisccfg-export140 libisccc-export140 libisccc-export140-udeb libisccfg-export140-udeb libirs-export141 libirs-export141-udeb Architecture: all source Version: 1:9.10.3.dfsg.P4-12.3 Distribution: unstable Urgency: high Maintainer: LaMont Jones Changed-By: Salvatore Bonaccorso Closes: 860224 860225 860226 Description: bind9 - Internet Domain Name Server bind9-doc - Documentation for BIND bind9-host - Version of 'host' bundled with BIND 9.X bind9utils - Utilities for BIND dnsutils - Clients provided with BIND host - Transitional package libbind-dev - Static Libraries and Headers used by BIND libbind-export-dev - Development files for the exported BIND libraries libbind9-140 - BIND9 Shared Library used by BIND libdns-export162 - Exported DNS Shared Library libdns-export162-udeb - Exported DNS library for debian-installer (udeb) libdns162 - DNS Shared Library used by BIND libirs-export141 - Exported IRS Shared Library libirs-export141-udeb - Exported IRS library for debian-installer (udeb) libirs141 - DNS Shared Library used by BIND libisc-export160 - Exported ISC Shared Library libisc-export160-udeb - Exported ISC library for debian-installer (udeb) libisc160 - ISC Shared Library used by BIND libisccc-export140 - Command Channel Library used by BIND libisccc-export140-udeb - Command Channel Library used by BIND (udeb) libisccc140 - Command Channel Library used by BIND libisccfg-export140 - Exported ISC CFG Shared Library libisccfg-export140-udeb - Exported ISC CFG library for debian-installer (udeb) libisccfg140 - Config File Handling Library used by BIND liblwres141 - Lightweight Resolver Library used by BIND lwresd - Lightweight Resolver Daemon Changes: bind9 (1:9.10.3.dfsg.P4-12.3) unstable; urgency=high . * Non-maintainer upload. * Dns64 with "break-dnssec yes;" can result in a assertion failure (CVE
Bug#860225: bind9: diff for NMU version 1:9.10.3.dfsg.P4-12.3
Hi Michael, On Mon, May 08, 2017 at 06:23:23PM -0400, Michael Gilbert wrote: > On Sun, May 7, 2017 at 10:38 AM, Salvatore Bonaccorso wrote: > > I've prepared an NMU for bind9 (versioned as 1:9.10.3.dfsg.P4-12.3) and > > uploaded it to DELAYED/5. Please feel free to tell me if I > > should delay it longer. > > Hi Salvatore, > > I reviewed the diff. It does look correct to me, so please feel free > to remove the delay. Okay rescheduled! > I don't have the free time to prepare the jessie DSA right now, are > you willing to do it? Okay I will try to come up with the patchset/debdiff and will post it here for testing. Regards, Salvatore
Bug#860225: bind9: diff for NMU version 1:9.10.3.dfsg.P4-12.3
Hi, On Mon, May 08, 2017 at 06:28:51PM -0400, Michael Gilbert wrote: > On Mon, May 8, 2017 at 6:23 PM, Michael Gilbert wrote: > > I reviewed the diff. It does look correct to me, so please feel free > > to remove the delay. > > There is also CVE-2017-3139 now [0]. This should only affect Red Hat bind9 version as in Red Hat 6 and not ustream bind, so Debian should furthermore not be affected by this. Was this assessment wrong? Regards, Salvatore
Bug#854872: marked as done (golang-github-docker-docker-credential-helpers FTBFS on 32bit: type [1073741824]*C.char larger than address space)
Your message dated Tue, 09 May 2017 00:33:31 + with message-id and subject line Bug#854872: fixed in golang-github-docker-docker-credential-helpers 0.5.0-2 has caused the Debian Bug report #854872, regarding golang-github-docker-docker-credential-helpers FTBFS on 32bit: type [1073741824]*C.char larger than address space 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.) -- 854872: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-docker-docker-credential-helpers Version: 0.3.0+git20160906.22.f72c04f-1 Severity: serious https://buildd.debian.org/status/package.php?p=golang-github-docker-docker-credential-helpers ... make[1]: Entering directory '/«BUILDDIR»/golang-github-docker-docker-credential-helpers-0.3.0+git20160906.22.f72c04f' dh_auto_build go install -v -p 1 github.com/docker/docker-credential-helpers/client github.com/docker/docker-credential-helpers/credentials github.com/docker/docker-credential-helpers/secretservice github.com/docker/docker-credential-helpers/secretservice/cmd github.com/docker/docker-credential-helpers/credentials github.com/docker/docker-credential-helpers/client github.com/docker/docker-credential-helpers/secretservice # github.com/docker/docker-credential-helpers/secretservice src/github.com/docker/docker-credential-helpers/secretservice/secretservice_linux.go:98: type [1073741824]*C.char larger than address space src/github.com/docker/docker-credential-helpers/secretservice/secretservice_linux.go:98: type [1073741824]*C.char too large src/github.com/docker/docker-credential-helpers/secretservice/secretservice_linux.go:99: type [1073741824]*C.char larger than address space src/github.com/docker/docker-credential-helpers/secretservice/secretservice_linux.go:99: type [1073741824]*C.char too large dh_auto_build: go install -v -p 1 github.com/docker/docker-credential-helpers/client github.com/docker/docker-credential-helpers/credentials github.com/docker/docker-credential-helpers/secretservice github.com/docker/docker-credential-helpers/secretservice/cmd returned exit code 2 debian/rules:7: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory '/«BUILDDIR»/golang-github-docker-docker-credential-helpers-0.3.0+git20160906.22.f72c04f' debian/rules:4: recipe for target 'build-arch' failed make: *** [build-arch] Error 2 --- End Message --- --- Begin Message --- Source: golang-github-docker-docker-credential-helpers Source-Version: 0.5.0-2 We believe that the bug you reported is fixed in the latest version of golang-github-docker-docker-credential-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 854...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jordi Mallach (supplier of updated golang-github-docker-docker-credential-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: SHA512 Format: 1.8 Date: Tue, 09 May 2017 00:03:09 +0200 Source: golang-github-docker-docker-credential-helpers Binary: golang-github-docker-docker-credential-helpers-dev golang-docker-credential-helpers Architecture: source amd64 all Version: 0.5.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Jordi Mallach Description: golang-docker-credential-helpers - Use native stores to safeguard Docker credentials golang-github-docker-docker-credential-helpers-dev - Use native stores to safeguard Docker credentials Closes: 854872 Changes: golang-github-docker-docker-credential-helpers (0.5.0-2) unstable; urgency=medium . * Attempt to fix 32bit builds by reducing the slice conversion (closes: #854872). Checksums-Sha1: 1dec5d2ad2d855d4f288b2714798cb56fccdf288 2591 golang-github-docker-docker-credential-helpers_0.5.0-2.dsc 071c55d5f4beb5bd9c3256b545f8f4ca9c64f800 2600 golang-github-docker-docker-credential-helpers_0.5.0-2.debian.tar.xz 935b78c3a992cf95b2bc04344ba43ac2f5972dfb 253126 golang-docker-credential-helpers-dbgsym_0.5.0-2_amd64.deb fb824ea3e808041847c36832e86de8ab6761fe1c 474394 go
Bug#861539: marked as done (tcpreplay FTBFS on armel/armhf/mips*: L7 fuzzing test: Makefile:963: recipe for target 'rewrite_l7fuzzing' failed)
Your message dated Tue, 09 May 2017 00:18:39 + with message-id and subject line Bug#861539: fixed in tcpreplay 4.2.5-1 has caused the Debian Bug report #861539, regarding tcpreplay FTBFS on armel/armhf/mips*: L7 fuzzing test: Makefile:963: recipe for target 'rewrite_l7fuzzing' failed 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.) -- 861539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tcpreplay Version: 4.2.4-1 Severity: serious https://buildd.debian.org/status/package.php?p=tcpreplay&suite=sid ... [tcprewrite] Seeded Keep MAC test: OK [tcprewrite] L7 fuzzing test: Makefile:963: recipe for target 'rewrite_l7fuzzing' failed make[2]: *** [rewrite_l7fuzzing] Error 1 make[2]: Target 'test' not remade because of errors. make[2]: Leaving directory '/«PKGBUILDDIR»/test' Makefile:888: recipe for target 'test' failed make[1]: *** [test] Error 2 --- End Message --- --- Begin Message --- Source: tcpreplay Source-Version: 4.2.5-1 We believe that the bug you reported is fixed in the latest version of tcpreplay, 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 861...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Biedl (supplier of updated tcpreplay 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: Tue, 09 May 2017 01:10:08 +0200 Source: tcpreplay Binary: tcpreplay Architecture: source powerpc Version: 4.2.5-1 Distribution: unstable Urgency: medium Maintainer: Christoph Biedl Changed-By: Christoph Biedl Description: tcpreplay - Tool to replay saved tcpdump files at arbitrary speeds Closes: 861539 Changes: tcpreplay (4.2.5-1) unstable; urgency=medium . * New upstream version 4.2.5. Also fixes test for architectures where unaligned memory access is not acceptable. Closes: #861539 Checksums-Sha1: ba43c1c2b4aecaf45e043290b4a7d49a7ce3fc37 1761 tcpreplay_4.2.5-1.dsc 18f695597693a10918a9b4c0af4abeb7253ed5da 714028 tcpreplay_4.2.5.orig.tar.xz 80c16b26d2e5437c5f4af5d957385540d1fece54 7512 tcpreplay_4.2.5-1.debian.tar.xz 21c4e7f97bbbd253110c45f24ae82762b4188299 679184 tcpreplay-dbgsym_4.2.5-1_powerpc.deb 0ac449e26360100c393f5c36c9b5870087b405f4 4926 tcpreplay_4.2.5-1_powerpc.buildinfo 7d6776c5d0e8be163608fd472372afbfdb87c9d3 214994 tcpreplay_4.2.5-1_powerpc.deb Checksums-Sha256: 92ad8a09c5e2a446c19caf63ca22b5941fad6f5f635cdbd0d18c9c805d1d8ece 1761 tcpreplay_4.2.5-1.dsc 4c8739a34040ff78ac5a6133105a1220218de4f4ea865673950bd54da74d34d4 714028 tcpreplay_4.2.5.orig.tar.xz 8ab2420f79d366b8f191316be742534d092382f52a17e3cbd4d4b63b23e426a5 7512 tcpreplay_4.2.5-1.debian.tar.xz f1245c846be402fc516b5dc25496f9c3ad4439870975ce0945481fc6db855748 679184 tcpreplay-dbgsym_4.2.5-1_powerpc.deb 095e9bb61037953e1e0af67c9b3c1a7e21be9f510887232e8bc7a6f68c3344a1 4926 tcpreplay_4.2.5-1_powerpc.buildinfo 60fed547ca343f6a2aa1e2fa155bc63ec93144de4769ce066ec28b683fcfcb5d 214994 tcpreplay_4.2.5-1_powerpc.deb Files: 11104e6dc9ae891bf8dd07af1d1b6264 1761 net optional tcpreplay_4.2.5-1.dsc 755ce8821132b4a5adcb508aaa7f1f81 714028 net optional tcpreplay_4.2.5.orig.tar.xz f8df13418d6046268854f62b47b3a785 7512 net optional tcpreplay_4.2.5-1.debian.tar.xz 31627d877e36781328cd6feba6a490b1 679184 debug extra tcpreplay-dbgsym_4.2.5-1_powerpc.deb 0a69c28051f272db8a6e245443b0b55a 4926 net optional tcpreplay_4.2.5-1_powerpc.buildinfo cda7a8adab3a07517a48395beca2aa0c 214994 net optional tcpreplay_4.2.5-1_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJZEQTfAAoJEMQsWOtZFJL9lT0P/RAU/QXsiCKFik5RGxmKOFmr AdMzPsXyBD4j/EL8Lvqp0BLYD3yRu7x9X72/71qDpgNlNL3pXpLZ1eCKLreY4y6r 2WHCwfUhnwa4yE2aor3+l94OTepTW0OhfcAhYcA+PlYExSSDwWncEOceNJtfT7y1 AMeIpgvwFjy9Ta93mlyCB7rPI1BZIahFjzVLOBjLNTsrBCnXTY+FdYYmWzdD+EeY mfhn/R91Mp3YFQajGXW4OzUldZBLAzYFoYTZ50GOLYXxDet+zHBjIZEbEohCMUur ceiMGPBwd0HIC0gzpSMoDbZeHyUXWCxjMM/6HLF4ns/ri5RzO+V2r8xuXDheNK1b nuhYJOYa6EF9oHkSWGqdSSxU9hxwLUSRNHjxdy3YoHd77w6tgMSh40nZopec8XgI kkcmdSYhY5MLu3u2g2P1CYpFyDkC2dg2UD6LIzXMT7ezAQBKpfd9aUVlciBT+s9b IBjfJAsL4Zd8TcmZhbdFLIgLGj3SnXzrzCr9lFTWFbcph0
Bug#860225: bind9: diff for NMU version 1:9.10.3.dfsg.P4-12.3
On Mon, May 8, 2017 at 6:23 PM, Michael Gilbert wrote: > I reviewed the diff. It does look correct to me, so please feel free > to remove the delay. There is also CVE-2017-3139 now [0]. Best wishes, Mike [0] https://access.redhat.com/errata/RHSA-2017:1202
Bug#860225: bind9: diff for NMU version 1:9.10.3.dfsg.P4-12.3
On Sun, May 7, 2017 at 10:38 AM, Salvatore Bonaccorso wrote: > I've prepared an NMU for bind9 (versioned as 1:9.10.3.dfsg.P4-12.3) and > uploaded it to DELAYED/5. Please feel free to tell me if I > should delay it longer. Hi Salvatore, I reviewed the diff. It does look correct to me, so please feel free to remove the delay. I don't have the free time to prepare the jessie DSA right now, are you willing to do it? Best wishes, Mike
Bug#861591: Bug#862071: password-store: FTBFS when built in a path with >= 74 characters
gregor herrmann wrote: > > This is due to GNUPGHOME needing to fit within sockaddr_un.sun_path. > > Also #861591, where the same happens. > > I'm not sure how RC-ish this should be, as build paths by our usual > tools (sbuild, pbuilder) are, IIRC, shorter (/build//…), so > this shouldn't be a problem in most cases. As it happens, it appears to also fail when HOME is non-existent: https://gist.github.com/lamby/72f051e7c4dd75cfbdd23e48a2151f5e/raw … which is even more dubious as RC severity, but I'll leave that to the Release Team. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Processed: use a temporary $GNUPGHOME for test suites
Processing control commands: > affects 862071 + src:gnupg2 Bug #862071 [src:password-store] password-store: FTBFS when built in a path with >= 74 characters Added indication that 862071 affects src:gnupg2 -- 862071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862071 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#862071: use a temporary $GNUPGHOME for test suites
Control: affects 862071 + src:gnupg2 Upstream's recommendation is currently to use a temporary $GNUPGHOME (with a short path) for test suites which depend on GnuPG with an ephemeral homedir. --dkg signature.asc Description: PGP signature
Bug#861591: Bug#862071: password-store: FTBFS when built in a path with >= 74 characters
On Mon, 08 May 2017 22:25:54 +0100, Chris Lamb wrote: > retitle 862071 password-store: FTBFS when built in a path with >= 74 > characters > thanks > > > (Yes, really.) > This is due to GNUPGHOME needing to fit within sockaddr_un.sun_path. Also #861591, where the same happens. I'm not sure how RC-ish this should be, as build paths by our usual tools (sbuild, pbuilder) are, IIRC, shorter (/build//…), so this shouldn't be a problem in most cases. Cheers, gregor -- .''`. https://info.comodo.priv.at/ - Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Tom Waits: Lost in the Harbour signature.asc Description: Digital Signature
Bug#862071: password-store: FTBFS when built in a path with >= 74 characters
retitle 862071 password-store: FTBFS when built in a path with >= 74 characters thanks (Yes, really.) This is due to GNUPGHOME needing to fit within sockaddr_un.sun_path. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Processed: Re: password-store: FTBFS when built in a path with >= 74 characters
Processing commands for cont...@bugs.debian.org: > retitle 862071 password-store: FTBFS when built in a path with >= 74 > characters Bug #862071 [src:password-store] password-store: FTBFS: not ok 1 - Test "generate" command Changed Bug title to 'password-store: FTBFS when built in a path with >= 74 characters' from 'password-store: FTBFS: not ok 1 - Test "generate" command'. > thanks Stopping processing here. Please contact me if you need assistance. -- 862071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862071 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#861771: Fails to install: postinst script returned error exit status 1
Processing control commands: > found 861771 0.13-1 Bug #861771 [nodm] Fails to install: postinst script returned error exit status 1 Marked as found in versions nodm/0.13-1. > tags 861771 + patch Bug #861771 [nodm] Fails to install: postinst script returned error exit status 1 Added tag(s) patch. -- 861771: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861771 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#861771: Fails to install: postinst script returned error exit status 1
Control: found 861771 0.13-1
Control: tags 861771 + patch
On Mon, 08 May 2017 at 20:14:28 +0100, Simon McVittie wrote:
> If you try to downgrade to 0.13-1 (in testing), do you still get this?
I can reproduce this with 0.13-1, so it should not block migration.
> I think the attached patch should hopefully fix this bug (thanks to
> Ansgar Burchardt for suggesting this approach)
This doesn't work: if an ExecStartPre command exits with the
SuccessExitStatus then systemd proceeds to ExecStart, so I don't think
we can have an ExecStartPre that cancels start without marking the service
as failed (which would in turn make the postinst fragment fail). But it
can be adapted by using a non-trivial ExecStartPre, as in the attached.
The long-term solution would be to not enable the display manager at
the update-rc.d level) if it wasn't enabled by the user, and migrate
enabledness like this pseudocode:
if (enabled, using the same algorithm as invoke-rc.d &&
enabled in /etc/default/nodm) {
update-rc.d nodm enable
} else {
update-rc.d nodm disable
}
then remove NODM_ENABLED from /etc/default/nodm. openarena-server has
code in its preinst to do something similar.
But that definitely seems like a job for post-stretch, particularly
if it gets entangled with a new approach to registering for the
display-manager.service symlink (#852125).
S
From: Simon McVittie
Date: Mon, 8 May 2017 17:01:40 +0100
Subject: nodm.service: Don't respawn or fail if disabled in
/etc/default
Bug-Debian: https://bugs.debian.org/861771
---
nodm.service.in | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/nodm.service.in b/nodm.service.in
index 0b7e95b..b53fef8 100644
--- a/nodm.service.in
+++ b/nodm.service.in
@@ -5,8 +5,11 @@ After=plymouth-quit.service systemd-user-sessions.service
[Service]
EnvironmentFile=-/etc/default/nodm
-ExecStartPre=/usr/bin/test ${NODM_ENABLED} != no -a ${NODM_ENABLED} != false
-ExecStart=@sbindir@/nodm $NODM_OPTIONS
+# 77 is EX_NOPERM, and doesn't seem to be used by nodm itself
+# Don't respawn or mark as failed if disabled via /etc/default/nodm
+RestartPreventExitStatus=77
+SuccessExitStatus=77
+ExecStart=/bin/sh -c 'if test ${NODM_ENABLED} = no || test ${NODM_ENABLED} = false; then exit 77; else exec @sbindir@/nodm $NODM_OPTIONS; fi'
Restart=always
KillMode=mixed
TimeoutStopSec=10
Processed: user release.debian....@packages.debian.org, usertagging 851819, tagging 851819
Processing commands for cont...@bugs.debian.org: > user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was ni...@thykier.net). > usertags 851819 - stretch-can-defer Usertags were: stretch-can-defer. Usertags are now: . > tags 851819 - stretch-ignore Bug #851819 [flashplugin-nonfree] ERROR: wget failed to download http://people.debian.org/~bartm/... Bug #851066 [flashplugin-nonfree] flashplugin-nonfree: Mismatch between detected and available versions (Download file not available at people.debian.org) Bug #853095 [flashplugin-nonfree] flashplugin-nonfree: Unable to update to the last flash version Bug #854467 [flashplugin-nonfree] cannot upgrade Bug #857765 [flashplugin-nonfree] flashplugin-nonfree has 33 severe security flaws, orphaned? Removed tag(s) stretch-ignore. Removed tag(s) stretch-ignore. Removed tag(s) stretch-ignore. Removed tag(s) stretch-ignore. Removed tag(s) stretch-ignore. > thanks Stopping processing here. Please contact me if you need assistance. -- 851066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851066 851819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851819 853095: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853095 854467: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854467 857765: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#861771: Fails to install: postinst script returned error exit status 1
On Wed, 03 May 2017 at 16:13:25 -0400, Ryan Kavanagh wrote:
> nodm fails to install/upgrade.
What version did you upgrade from, and how long had you had that version
installed before upgrading?
If you try to downgrade to 0.13-1 (in testing), do you still get this?
If you do, please mark this bug as found in 0.13-1 so the fix for #860463
can migrate - at the moment this bug report is preventing another RC bug
from being fixed in testing.
I suspect this regressed in 0.12-1.1 with the addition of the native
systemd unit.
> I marked the severity as grave because the package fails
> to install/upgrade, thus rendering it unusable to (all?) users.
I think this bug makes it unusable to users who boot with systemd and
have configured nodm to not be started on boot (which does prompt the
question of why it's installed at all), so not all users.
A systemd unit identical to the one in 0.13-1 works fine for me on
a system where nodm is enabled.
I think the attached patch should hopefully fix this bug (thanks to
Ansgar Burchardt for suggesting this approach) but I haven't had a
chance to test it on a system with NODM_ENABLED=false yet.
S
From: Simon McVittie
Date: Mon, 8 May 2017 17:01:40 +0100
Subject: nodm.service: Don't respawn or fail if disabled in
/etc/default
Bug-Debian: https://bugs.debian.org/861771
---
nodm.service.in | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/nodm.service.in b/nodm.service.in
index 0b7e95b..b6c77fa 100644
--- a/nodm.service.in
+++ b/nodm.service.in
@@ -5,7 +5,11 @@ After=plymouth-quit.service systemd-user-sessions.service
[Service]
EnvironmentFile=-/etc/default/nodm
-ExecStartPre=/usr/bin/test ${NODM_ENABLED} != no -a ${NODM_ENABLED} != false
+# 77 is EX_NOPERM, and doesn't seem to be used by nodm itself
+ExecStartPre=/bin/sh -c 'if test ${NODM_ENABLED} = no || test ${NODM_ENABLED} = false; then exit 77; fi'
+# Don't respawn or mark as failed if disabled via /etc/default/nodm
+RestartPreventExitStatus=77
+SuccessExitStatus=77
ExecStart=@sbindir@/nodm $NODM_OPTIONS
Restart=always
KillMode=mixed
Processed: reopening 862103
Processing commands for cont...@bugs.debian.org: > reopen 862103 Bug #862103 [mariadb-server-10.1] mariadb-server-10.1: MariaDB crash after throwing an instance of 'std::out_of_range' Bug 862103 is not marked as done; doing nothing. > thanks Stopping processing here. Please contact me if you need assistance. -- 862103: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862103 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 862098 to lxterminal: CVE-2016-10369: socket can be blocked by another user
Processing commands for cont...@bugs.debian.org: > retitle 862098 lxterminal: CVE-2016-10369: socket can be blocked by another > user Bug #862098 [lxterminal] lxterminal: socket can be blocked by another user Changed Bug title to 'lxterminal: CVE-2016-10369: socket can be blocked by another user' from 'lxterminal: socket can be blocked by another user'. > thanks Stopping processing here. Please contact me if you need assistance. -- 862098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#862052: marked as done (Latest slim upgrade caused involuntary crashes/logouts...)
Your message dated Mon, 08 May 2017 17:29:00 + with message-id <1d3c25fa-0033-79a1-a5d9-e0c33c9ff...@thykier.net> and subject line Re: Latest slim upgrade caused involuntary crashes/logouts... has caused the Debian Bug report #862052, regarding Latest slim upgrade caused involuntary crashes/logouts... 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.) -- 862052: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862052 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: slim Version: 1.3.6-5 Severity: serious When upgrading from 1.3.6-4+b2 to 1.3.6-5 of slim I noticed that my window manager appeared to suddenly "crash" and logged me out. However I had not changed anything related to that but I had recently upgraded slim so I investigated it a bit. I compiled 1.3.6-5 without the fix for 860465 as mentioned in the -5 debian patch (but keeping all other additions from -4+b2 to -5 the same). Without this "fix" my desktop no longer had problems. Could this be because I don't have plymouth installed (whatever that is)? I'm happy to do further testing if you can provide something for me to test. Besides this minor mishap I'm actually a happy slim user, thanks for putting in the effort. :) / Sebastian --- End Message --- --- Begin Message --- Source: slim Source-Version: 1.3.6-5.1 Sebastian Rasmussen: >>> Could you please try to upgrade to slim/1.3.6-5.1 to see if that >>> fixes your issue? >> Of course, no problem, but it will have to wait a day or so. > > I can now confirm that upgrading to 1.3.6-5.1 does indeed fix > the issue I was experiencing. From my perspective that means > that you may mark this bug as resolved, but you might want to > tie it to to the 1.3.6-5.1 release some how. With the -done + plus the above Pseudo-headers the bug will now be closed in 1.3.6-5.1 and later. > Thanks for being responsive and helpful! :) > > / Sebastian > You are welcome. :) Thanks, ~Niels--- End Message ---
Bug#861134: marked as done (slim: Reloads automatically and queries login-prompt after running window manager for some (a short) time)
Your message dated Mon, 08 May 2017 17:29:00 + with message-id <1d3c25fa-0033-79a1-a5d9-e0c33c9ff...@thykier.net> and subject line Re: Latest slim upgrade caused involuntary crashes/logouts... has caused the Debian Bug report #862052, regarding slim: Reloads automatically and queries login-prompt after running window manager for some (a short) time 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.) -- 862052: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862052 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: slim Version: 1.3.6-5 Severity: important Dear Maintainer, * Slim has been set up as the default display manager * After running the Window Manager (XFCE in my case) and working with it causes a sudden reload of Slim and (re-)querying the login prompt * So there is a login-prompt query over and over again -- System Information: Debian Release: 9.0 APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 4.9.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages slim depends on: ii dbus 1.10.18-1 ii debconf [debconf-2.0] 1.5.60 ii libc6 2.24-10 ii libfontconfig1 2.11.0-6.7+b1 ii libfreetype6 2.6.3-3.1 ii libgcc11:7-20161115-1 ii libjpeg62-turbo1:1.5.1-2 ii libpam0g 1.1.8-3.5 ii libpng16-161.6.28-1 ii libstdc++6 7-20161115-1 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 ii libxft22.3.2-1+b2 ii libxmu62:1.1.2-2 ii libxrandr2 2:1.5.1-1 ii libxrender11:0.9.10-1 ii lsb-base 9.20161125 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages slim recommends: ii xterm 327-2 Versions of packages slim suggests: pn scrot ii xauth 1:1.0.9-1+b2 -- debconf information excluded --- End Message --- --- Begin Message --- Source: slim Source-Version: 1.3.6-5.1 Sebastian Rasmussen: >>> Could you please try to upgrade to slim/1.3.6-5.1 to see if that >>> fixes your issue? >> Of course, no problem, but it will have to wait a day or so. > > I can now confirm that upgrading to 1.3.6-5.1 does indeed fix > the issue I was experiencing. From my perspective that means > that you may mark this bug as resolved, but you might want to > tie it to to the 1.3.6-5.1 release some how. With the -done + plus the above Pseudo-headers the bug will now be closed in 1.3.6-5.1 and later. > Thanks for being responsive and helpful! :) > > / Sebastian > You are welcome. :) Thanks, ~Niels--- End Message ---
Bug#861474: marked as done (slim: Session restarts in a loop rendering the whole system useless)
Your message dated Mon, 08 May 2017 17:29:00 + with message-id <1d3c25fa-0033-79a1-a5d9-e0c33c9ff...@thykier.net> and subject line Re: Latest slim upgrade caused involuntary crashes/logouts... has caused the Debian Bug report #862052, regarding slim: Session restarts in a loop rendering the whole system useless 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.) -- 862052: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862052 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: slim Version: 1.3.6-5 Severity: critical Justification: breaks the whole system I am not sure that this is a slim problem, but as the system is almost unusable, I cannot investigate. After an apt-get upgrade earlier today, the system presents a new slim login page. Logging in works, but then the whole system restarts X (presumably) and the sylim login prompt appear again. This ahhpens in what seems to be an infinite loop, roughly every minute or so. I am only able to compose this message outside X using a pseudo terminal. The restarts interrupt the terminal and represents the slim login page. Fortunately the terminal context is retained so I can switch back to the terminal. I have not yet tried removing slim which I hope I may be able to do despite the constant restarts. I suspect slim because it seems to be the only likely candidate in the set of upgrades earlier today, and it is the slim login screen which keeps looping. Presumably others will report this problem as well. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages slim depends on: ii dbus 1.10.18-1 ii debconf [debconf-2.0] 1.5.60 ii libc6 2.24-10 ii libfontconfig1 2.11.0-6.7+b1 ii libfreetype6 2.6.3-3.1 ii libgcc11:6.3.0-14 ii libjpeg62-turbo1:1.5.1-2 ii libpam0g 1.1.8-3.5 ii libpng16-161.6.28-1 ii libstdc++6 6.3.0-14 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 ii libxft22.3.2-1+b2 ii libxmu62:1.1.2-2 ii libxrandr2 2:1.5.1-1 ii libxrender11:0.9.10-1 ii lsb-base 9.20161125 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages slim recommends: ii xterm 327-2 Versions of packages slim suggests: pn scrot ii xauth 1:1.0.9-1+b2 -- debconf information: * shared/default-x-display-manager: slim slim/daemon_name: /usr/bin/slim --- End Message --- --- Begin Message --- Source: slim Source-Version: 1.3.6-5.1 Sebastian Rasmussen: >>> Could you please try to upgrade to slim/1.3.6-5.1 to see if that >>> fixes your issue? >> Of course, no problem, but it will have to wait a day or so. > > I can now confirm that upgrading to 1.3.6-5.1 does indeed fix > the issue I was experiencing. From my perspective that means > that you may mark this bug as resolved, but you might want to > tie it to to the 1.3.6-5.1 release some how. With the -done + plus the above Pseudo-headers the bug will now be closed in 1.3.6-5.1 and later. > Thanks for being responsive and helpful! :) > > / Sebastian > You are welcome. :) Thanks, ~Niels--- End Message ---
Processed: severity of 862052 is critical, fixed 862052 in 1.3.6-5.1, closing 862052, merging 862052 861474
Processing commands for cont...@bugs.debian.org:
> severity 862052 critical
Bug #862052 [slim] Latest slim upgrade caused involuntary crashes/logouts...
Severity set to 'critical' from 'serious'
> fixed 862052 1.3.6-5.1
Bug #862052 [slim] Latest slim upgrade caused involuntary crashes/logouts...
Marked as fixed in versions slim/1.3.6-5.1.
> close 862052 1.3.6-5.1
Bug #862052 [slim] Latest slim upgrade caused involuntary crashes/logouts...
Ignoring request to alter fixed versions of bug #862052 to the same values
previously set
Bug #862052 [slim] Latest slim upgrade caused involuntary crashes/logouts...
Marked Bug as done
> merge 862052 861474
Bug #862052 {Done: Apollon Oikonomopoulos } [slim] Latest
slim upgrade caused involuntary crashes/logouts...
Bug #862052 {Done: Apollon Oikonomopoulos } [slim] Latest
slim upgrade caused involuntary crashes/logouts...
Added tag(s) moreinfo and patch.
Bug #861134 {Done: Samuel Hym } [slim]
slim: Reloads automatically and queries login-prompt after running window
manager for some (a short) time
Bug #861474 {Done: Apollon Oikonomopoulos } [slim] slim:
Session restarts in a loop rendering the whole system useless
Merged 861134 861474 862052
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
861134: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861134
861474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861474
862052: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862052
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: found 862098 in 0.2.0-1
Processing commands for cont...@bugs.debian.org: > found 862098 0.2.0-1 Bug #862098 [lxterminal] lxterminal: socket can be blocked by another user Marked as found in versions lxterminal/0.2.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 862098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#862098: lxterminal: socket can be blocked by another user
Hi I have requested a CVE via https://cveform.mitre.org . Regards, Salvatore
Bug#862103: mariadb-server-10.1: MariaDB crash after throwing an instance of 'std::out_of_range'
Follow up : Patrick Gaus just suggested on the MariaDB bug report that the same fix should also be applied to XtraDB (storage/xtradb/dict/dict0stats.cc - Around line 1171), and not just in InnoDB. Makes sense.
Bug#862103: mariadb-server-10.1: MariaDB crash after throwing an instance of 'std::out_of_range'
Thanks! Hope the fix will be good enough to solve this issue. Unfortunately, Kazuhiko Shiozaki reported 3 days ago on the MariaDB bug report (http://cpc.cx/jg3) that the same crash happened to MariaDB 10.1.23 with the patch applied. That's the only report so far. PS: The package currently available in testing (10.1.22-3) seems badly affected by this issue (no problem with the previous 10.1.21-5). > Hi Sam, > > thanks for the heads-up and for the link to the patch - it applies > cleanly (after whitespace fixes) to MariaDB 10.1.23, so I am just > building 10.1.23-5 with the patch applied. > > Cheers, > -- > Ondřej Surý > Knot DNS (https://www.knot-dns.cz/) - a high-performance DNS server > Knot Resolver (https://www.knot-resolver.cz/) - secure, privacy-aware, > fast DNS(SEC) resolver > Vše pro chleba (https://vseprochleba.cz) - Mouky ze mlýna a potřeby pro > pečení chleba všeho druhu
Bug#862052: Latest slim upgrade caused involuntary crashes/logouts...
>> Could you please try to upgrade to slim/1.3.6-5.1 to see if that >> fixes your issue? > Of course, no problem, but it will have to wait a day or so. I can now confirm that upgrading to 1.3.6-5.1 does indeed fix the issue I was experiencing. From my perspective that means that you may mark this bug as resolved, but you might want to tie it to to the 1.3.6-5.1 release some how. Thanks for being responsive and helpful! :) / Sebastian
Bug#860618: golang-github-seccomp-libseccomp-golang: FTBFS on i386: dh_auto_test
unblock report filed: #862108 -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1 pgpDcNjbHuTyp.pgp Description: PGP signature
Bug#862103: mariadb-server-10.1: MariaDB crash after throwing an instance of 'std::out_of_range'
Hi Sam, thanks for the heads-up and for the link to the patch - it applies cleanly (after whitespace fixes) to MariaDB 10.1.23, so I am just building 10.1.23-5 with the patch applied. Cheers, -- Ondřej Surý Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware, fast DNS(SEC) resolver Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro pečení chleba všeho druhu On Mon, May 8, 2017, at 16:32, Sam D. wrote: > Package: mariadb-server-10.1 > Version: 10.1.22-3 > Severity: grave > Tags: newcomer upstream > Justification: causes non-serious data loss > > Dear Maintainer, > > A critical MySQL bug was discovered in InnoDB storage engine (related to > statistics calculation) some weeks ago. > > This bug affects MariaDB 10.1 as well and is present in the current > Debian Stretch (MariaDB 10.1.22) package > [mariadb Ver 15.1 Distrib 10.1.22-MariaDB, for debian-linux-gnu (x86_64) > using readline 5.2]. > > Seems to also affect the unstable 10.1.23-3 package. > > MariaDB crash very often on many of our server, from many times daily to > many times hourly. > > The bug (and fix) is well described here : > > https://bugs.mysql.com/bug.php?id=84940 (rated serious) > > and here > > https://jira.mariadb.org/browse/MDEV-12281 (rated critical) > > The bug come from a missing bracket in the InnoDB Stats code and a patch > is available here : > > https://github.com/mysql/mysql-server/commit/0241e1c1b216d87050cdfcb4531ffc17f9eb1dc7 > > Data corruption in InnoDB tables may occur as a side effect. > > > Typical Error/crash log : > > --- > > Version: '10.1.22-MariaDB-' socket: '/var/run/mysqld/mysqld.sock' port: > 3306 Debian 9.0 > terminate called after throwing an instance of 'std::out_of_range' > what(): vector::_M_range_check: __n (which is 4294967295) >= > this->size() (which is 0) > 170508 13:55:21 [ERROR] mysqld got signal 6 ; > This could be because you hit a bug. It is also possible that this binary > or one of the libraries it was linked against is corrupt, improperly > built, > or misconfigured. This error can also be caused by malfunctioning > hardware. > > To report this bug, see https://mariadb.com/kb/en/reporting-bugs > > We will try our best to scrape up some info that will hopefully help > diagnose the problem, but since we have already crashed, > something is definitely wrong and this may fail. > > Server version: 10.1.22-MariaDB- > key_buffer_size=16777216 > read_buffer_size=131072 > max_used_connections=5 > max_threads=386 > thread_count=2 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = > 864227 K bytes of memory > Hope that's ok; if not, decrease some variables in the equation. > > Thread pointer: 0x0 > Attempting backtrace. You can use the following information to find out > where mysqld died. If you see no messages after this, something went > terribly wrong... > stack_bottom = 0x0 thread_stack 0x3 > /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x5607ce9d50ce] > /usr/sbin/mysqld(handle_fatal_signal+0x3bd)[0x5607ce51e50d] > /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7feadffc90c0] > /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7feade8c4fcf] > /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7feade8c63fa] > /usr/lib/x86_64-linux-gnu/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x15d)[0x7feadefc50ad] > /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8f066)[0x7feadefc3066] > /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8f0b1)[0x7feadefc30b1] > /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8f2c9)[0x7feadefc32c9] > /usr/lib/x86_64-linux-gnu/libstdc++.so.6(_ZSt24__throw_out_of_range_fmtPKcz+0xf5)[0x7feadefebb85] > /usr/sbin/mysqld(+0x9ace97)[0x5607ce931e97] > /usr/sbin/mysqld(+0x9b07f4)[0x5607ce9357f4] > /usr/sbin/mysqld(+0x9b4626)[0x5607ce939626] > /usr/sbin/mysqld(+0x9b5d19)[0x5607ce93ad19] > /lib/x86_64-linux-gnu/libpthread.so.0(+0x7494)[0x7feadffbf494] > /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7feade97a93f] > The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html > contains > information that should help you find out what is causing the crash. > 2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Using mutexes to ref > count buffer pool pages > 2017-05-08 13:55:27 140012981801536 [Note] InnoDB: The InnoDB memory heap > is disabled > 2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Mutexes and rw_locks > use GCC atomic builtins > 2017-05-08 13:55:27 140012981801536 [Note] InnoDB: GCC builtin > __atomic_thread_fence() is used for memory barrier > 2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Compressed tables use > zlib 1.2.8 > 2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Using Linux native AIO > 2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Using SSE crc32 > instructions
Bug#862103: mariadb-server-10.1: MariaDB crash after throwing an instance of 'std::out_of_range'
Package: mariadb-server-10.1 Version: 10.1.22-3 Severity: grave Tags: newcomer upstream Justification: causes non-serious data loss Dear Maintainer, A critical MySQL bug was discovered in InnoDB storage engine (related to statistics calculation) some weeks ago. This bug affects MariaDB 10.1 as well and is present in the current Debian Stretch (MariaDB 10.1.22) package [mariadb Ver 15.1 Distrib 10.1.22-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2]. Seems to also affect the unstable 10.1.23-3 package. MariaDB crash very often on many of our server, from many times daily to many times hourly. The bug (and fix) is well described here : https://bugs.mysql.com/bug.php?id=84940 (rated serious) and here https://jira.mariadb.org/browse/MDEV-12281 (rated critical) The bug come from a missing bracket in the InnoDB Stats code and a patch is available here : https://github.com/mysql/mysql-server/commit/0241e1c1b216d87050cdfcb4531ffc17f9eb1dc7 Data corruption in InnoDB tables may occur as a side effect. Typical Error/crash log : --- Version: '10.1.22-MariaDB-' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian 9.0 terminate called after throwing an instance of 'std::out_of_range' what(): vector::_M_range_check: __n (which is 4294967295) >= this->size() (which is 0) 170508 13:55:21 [ERROR] mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. To report this bug, see https://mariadb.com/kb/en/reporting-bugs We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. Server version: 10.1.22-MariaDB- key_buffer_size=16777216 read_buffer_size=131072 max_used_connections=5 max_threads=386 thread_count=2 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 864227 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0x0 thread_stack 0x3 /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x5607ce9d50ce] /usr/sbin/mysqld(handle_fatal_signal+0x3bd)[0x5607ce51e50d] /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7feadffc90c0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7feade8c4fcf] /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7feade8c63fa] /usr/lib/x86_64-linux-gnu/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x15d)[0x7feadefc50ad] /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8f066)[0x7feadefc3066] /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8f0b1)[0x7feadefc30b1] /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8f2c9)[0x7feadefc32c9] /usr/lib/x86_64-linux-gnu/libstdc++.so.6(_ZSt24__throw_out_of_range_fmtPKcz+0xf5)[0x7feadefebb85] /usr/sbin/mysqld(+0x9ace97)[0x5607ce931e97] /usr/sbin/mysqld(+0x9b07f4)[0x5607ce9357f4] /usr/sbin/mysqld(+0x9b4626)[0x5607ce939626] /usr/sbin/mysqld(+0x9b5d19)[0x5607ce93ad19] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7494)[0x7feadffbf494] /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7feade97a93f] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2017-05-08 13:55:27 140012981801536 [Note] InnoDB: The InnoDB memory heap is disabled 2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2017-05-08 13:55:27 140012981801536 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Compressed tables use zlib 1.2.8 2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Using Linux native AIO 2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Using SSE crc32 instructions 2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Initializing buffer pool, size = 2.0G 2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Completed initialization of buffer pool 2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Highest supported file format is Barracuda. 2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Starting crash recovery from checkpoint LSN=195680453668 2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 1 row operations to undo InnoDB: Trx id counter is 100954368 2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Starting fin
Bug#861736:
Here after rebuilding hdf5 in debug mode
:~/Debian/nexus$ ./bug.py
H5get_libversion(majnum=0xbf8a5b04, minnum=0xbf8a5b08, relnum=0xbf8a5b0c) =
SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
H5open() = SUCCEED;
H5Pcreate(cls=8 (genprop class)) = 18 (genprop list);
H5Pget_cache(plist=18 (genprop list), mdc_nelmts=0xbf8a5af8,
rdcc_nslots=0xbf8a5afc, rdcc_nbytes=0xbf8a5b00, rdcc_w0=0xbf8a5b10) = SUCCEED;
H5Pset_cache(plist=18 (genprop list), mdc_nelmts=0, rdcc_nslots=521,
rdcc_nbytes=1024000, rdcc_w0=0.75) = SUCCEED;
H5Pset_fclose_degree(plist=18 (genprop list), degree=H5F_CLOSE_STRONG) =
SUCCEED;
H5check_version(majnum=1, minnum=10, relnum=0) = SUCCEED;
H5open() = SUCCEED;
H5Fcreate(filename=0x82517ef8, flags=2, fcpl=H5P_DEFAULT, fapl=18 (genprop
list)) = 0 (file);
H5Pclose(plist=18 (genprop list)) = SUCCEED;
ERROR: cannot open file: filenamenxs.h5
Traceback (most recent call last):
File "./bug.py", line 5, in
e.save("filenamenxs.h5", 'w5')
File "/usr/lib/python2.7/dist-packages/nxs/tree.py", line 868, in save
file = NeXusTree(filename, format)
File "/usr/lib/python2.7/dist-packages/nxs/napi.py", line 320, in __init__
raise NeXusError, "Could not %s %s"%(op,filename)
nxs.napi.NeXusError: Could not create filenamenxs.h5
H5Eget_auto2(estack=H5P_DEFAULT, func=0xbf8a6954, client_data=NULL) = SUCCEED;
H5Eauto_is_v2(estack=H5P_DEFAULT, is_stack=0xbf8a6898) = SUCCEED;
H5Eget_auto2(estack=H5P_DEFAULT, func=0xbf8a689c, client_data=0xbf8a68a0) =
SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
H5Eauto_is_v2(estack=H5P_DEFAULT, is_stack=0xbf8a6858) = SUCCEED;
H5Eget_auto2(estack=H5P_DEFAULT, func=0xbf8a685c, client_data=0xbf8a6860) =
SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
H5Eauto_is_v2(estack=H5P_DEFAULT, is_stack=0xbf8a6858) = SUCCEED;
H5Eget_auto2(estack=H5P_DEFAULT, func=0xbf8a685c, client_data=0xbf8a6860) =
SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
H5Eauto_is_v2(estack=H5P_DEFAULT, is_stack=0xbf8a6888) = SUCCEED;
H5Eget_auto2(estack=H5P_DEFAULT, func=0xbf8a688c, client_data=0xbf8a6890) =
SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
H5Eauto_is_v2(estack=H5P_DEFAULT, is_stack=0xbf8a6888) = SUCCEED;
H5Eget_auto2(estack=H5P_DEFAULT, func=0xbf8a688c, client_data=0xbf8a6890) =
SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
H5Eauto_is_v2(estack=H5P_DEFAULT, is_stack=0xbf8a6888) = SUCCEED;
H5Eget_auto2(estack=H5P_DEFAULT, func=0xbf8a688c, client_data=0xbf8a6890) =
SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
H5Eauto_is_v2(estack=H5P_DEFAULT, is_stack=0xbf8a6898) = SUCCEED;
H5Eget_auto2(estack=H5P_DEFAULT, func=0xbf8a689c, client_data=0xbf8a68a0) =
SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
H5Eauto_is_v2(estack=H5P_DEFAULT, is_stack=0xbf8a6868) = SUCCEED;
H5Eget_auto2(estack=H5P_DEFAULT, func=0xbf8a686c, client_data=0xbf8a6870) =
SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
H5Eauto_is_v2(estack=H5P_DEFAULT, is_stack=0xbf8a6868) = SUCCEED;
H5Eget_auto2(estack=H5P_DEFAULT, func=0xbf8a686c, client_data=0xbf8a6870) =
SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
H5Eauto_is_v2(estack=H5P_DEFAULT, is_stack=0xbf8a6868) = SUCCEED;
H5Eget_auto2(estack=H5P_DEFAULT, func=0xbf8a686c, client_data=0xbf8a6870) =
SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
H5Eset_auto2(estack=H5P_DEFAULT, func=NULL, client_data=NULL) = SUCCEED;
Processed: severity of 862095 is wishlist
Processing commands for cont...@bugs.debian.org: > severity 862095 wishlist Bug #862095 [reportbug] reportbug: Bugs in backported packages must not be sent to the BTS Severity set to 'wishlist' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 862095: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#862095: reportbug: Bugs in backported packages must not be sent to the BTS
On Mon, 2017-05-08 at 15:00 +0200, Thorsten Glaser wrote: > Hi! > > I disagree with making this RC right now, for the following reasons: [...] I also disagree, and I like bugs for backported linux packages going to the BTS as they are rarely specific to the backport. Ben. -- Ben Hutchings [W]e found...that it wasn't as easy to get programs right as we had thought. ... I realized that a large part of my life from then on was going to be spent in finding mistakes in my own programs. - Maurice Wilkes, 1949 signature.asc Description: This is a digitally signed message part
Bug#862095: reportbug: Bugs in backported packages must not be sent to the BTS
On Mon, May 08, 2017 at 03:00:13PM +0200, Thorsten Glaser wrote: >... > > Bugs against backported packages (~bpo versions) are not allowed > > to be reported to the BTS without explicit permission from the > > maintainer to do so > > 1. There is no automated way for the maintainers to agree to that >currently, formally (but see below). Doing that per-package would be the worst possible option, there should be one place (mailing list or BTS query) for getting all bugs. And bugs like #860147 that are reported against backport A but caused by backport B would be a real pain to handle with a per-package policy. >... > 4. Due to the above, I believe a short-circuit/knee-jerk reaction >to force reportbug to deliver _all_ bpo bugreports to the bpo >mailing list is wrong, and this should at the least be tagged >with stretch-ignore and discussed more broadly. What you call "short-circuit/knee-jerk reaction" is the official policy: https://backports.debian.org/FAQ/ Q: Where shall I report bugs I found in packages from backports to? A: Please report them to the debian-backports mailing list. The Debian bugtracking system doesn't know anything about backports versions, and sometimes the backporter isn't in the Debian packaging team so they might miss the report. The default bug reporting tool doing the exact opposite of the official policy is plainly wrong and leads to lost bug reports like #860147 or #854610 - the bug reporting tool and the documented procedure should result in the bug going to the same location. > bye, > //mirabilos cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#852059: marked as done (opendnssec-signer: installation hangs on invoke-rc.d due to script name being to long)
Your message dated Mon, 08 May 2017 13:18:30 +
with message-id
and subject line Bug#852059: fixed in opendnssec 1:2.0.4-3
has caused the Debian Bug report #852059,
regarding opendnssec-signer: installation hangs on invoke-rc.d due to script
name being to long
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.)
--
852059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: opendnssec-signer
Version: 1:2.0.3-5
Severity: important
Dear Maintainer,
During installation of opendnssec the installation of this package
and opendnssec-enforcer hang on command:
invoke-rc.d start
Each configuration round teh script has to be killed to end the
wait. Don't know of this should be reported here, as the scriptname is
longer then 15 characters, or with the maintainers of invoke-rc.d or the
start-stop-daemon function.
The scripts will never start this way. (at least on this system)
I haven't been able to fix this, and as this is a new installation, no
comparisons with older versions.
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing'), (500, 'oldstable'), (60, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.8.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages opendnssec-signer depends on:
ii init-system-helpers 1.46
ii libc62.24-8
ii libldns2 1.7.0-1
ii libssl1.11.1.0c-2
ii libxml2 2.9.4+dfsg1-2.1
ii opendnssec-common1:2.0.3-5
Versions of packages opendnssec-signer recommends:
iu opendnssec 1:2.0.3-5
ih opendnssec-enforcer 1:2.0.3-5
pn softhsm2
opendnssec-signer suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: opendnssec
Source-Version: 1:2.0.4-3
We believe that the bug you reported is fixed in the latest version of
opendnssec, 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 852...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ondřej Surý (supplier of updated opendnssec 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: Mon, 08 May 2017 14:47:39 +0200
Source: opendnssec
Binary: opendnssec-common opendnssec opendnssec-doc opendnssec-enforcer
opendnssec-enforcer-mysql opendnssec-enforcer-sqlite3 opendnssec-signer
libhsm-bin
Architecture: source
Version: 1:2.0.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Packaging
Changed-By: Ondřej Surý
Description:
libhsm-bin - library for interfacing PKCS#11 Hardware Security Modules
opendnssec - dependency package to install full OpenDNSSEC suite
opendnssec-common - common configuration files for OpenDNSSEC suite
opendnssec-doc - documentation for OpenDNSSEC suite
opendnssec-enforcer - tool to prepare DNSSEC keys (common package)
opendnssec-enforcer-mysql - tool to prepare DNSSEC keys (MySQL backend)
opendnssec-enforcer-sqlite3 - tool to prepare DNSSEC keys (sqlite3 backend)
opendnssec-signer - daemon to sign DNS zone files periodically
Closes: 852059 859418
Changes:
opendnssec (1:2.0.4-3) unstable; urgency=medium
.
* Fix reading the tmpfiles (Thanks Michael Biebl for catching that)
(Closes: #852059)
* Add /var/lib/opendnssec/{signer,enforcer} to the list of managed
directories (Closes: #859418)
Checksums-Sha1:
62f8cf3a0512f663722ec842dd18bc11a9737763 2835 opendnssec_2.0.4-3.dsc
f3e7d8396d0ca17e930b8ce573069fa136ca2a6c 23760 opendnssec_2.0.4-3.debian.tar.xz
caf6a3be5ca5b8b0a6103543def2b6135679678a 14881
opendnssec_2.0.4-3_amd64.buildinfo
Checksums-Sha256:
40eaea4aa8ecbf209000d13f92a3bf57cdeef2e3c01aec60b1941c2bf20ac9ff 2835
opendnssec_2.0.4-3.dsc
cebcee30c6d0ff32702fc6472ac0113e1524bd4e65cc0dcd2b713643791421c1 23760
opendnssec_2.0.4-3.debian.tar.xz
a71c9b06519b5b6ecebadb9ee5af393ffc87660a28aa9c4fdfbc29e69b80edb3 14881
opendnssec_2.0.4-3_amd64.buildinfo
Files:
f86f4e55e07eda0024d572a52f7a7a89 2835 admin extra ope
Processed: Re: Bug#859419: non-functional after installation (service fails to start)
Processing control commands: > severity -1 important Bug #859419 [opendnssec-enforcer] non-functional after installation (service fails to start) Severity set to 'important' from 'serious' -- 859419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#859418: marked as done (non-functional after installation (service fails to start))
Your message dated Mon, 08 May 2017 13:18:30 +
with message-id
and subject line Bug#859418: fixed in opendnssec 1:2.0.4-3
has caused the Debian Bug report #859418,
regarding non-functional after installation (service fails to start)
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.)
--
859418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: opendnssec-signer
Version: 1:2.0.4-2
Severity: serious
After running apt-get install opendnssec-signer, the service fails to
start. See attached screenshot from a test VM
-- System Information:
Debian Release: 9.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: opendnssec
Source-Version: 1:2.0.4-3
We believe that the bug you reported is fixed in the latest version of
opendnssec, 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 859...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ondřej Surý (supplier of updated opendnssec 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: Mon, 08 May 2017 14:47:39 +0200
Source: opendnssec
Binary: opendnssec-common opendnssec opendnssec-doc opendnssec-enforcer
opendnssec-enforcer-mysql opendnssec-enforcer-sqlite3 opendnssec-signer
libhsm-bin
Architecture: source
Version: 1:2.0.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Packaging
Changed-By: Ondřej Surý
Description:
libhsm-bin - library for interfacing PKCS#11 Hardware Security Modules
opendnssec - dependency package to install full OpenDNSSEC suite
opendnssec-common - common configuration files for OpenDNSSEC suite
opendnssec-doc - documentation for OpenDNSSEC suite
opendnssec-enforcer - tool to prepare DNSSEC keys (common package)
opendnssec-enforcer-mysql - tool to prepare DNSSEC keys (MySQL backend)
opendnssec-enforcer-sqlite3 - tool to prepare DNSSEC keys (sqlite3 backend)
opendnssec-signer - daemon to sign DNS zone files periodically
Closes: 852059 859418
Changes:
opendnssec (1:2.0.4-3) unstable; urgency=medium
.
* Fix reading the tmpfiles (Thanks Michael Biebl for catching that)
(Closes: #852059)
* Add /var/lib/opendnssec/{signer,enforcer} to the list of managed
directories (Closes: #859418)
Checksums-Sha1:
62f8cf3a0512f663722ec842dd18bc11a9737763 2835 opendnssec_2.0.4-3.dsc
f3e7d8396d0ca17e930b8ce573069fa136ca2a6c 23760 opendnssec_2.0.4-3.debian.tar.xz
caf6a3be5ca5b8b0a6103543def2b6135679678a 14881
opendnssec_2.0.4-3_amd64.buildinfo
Checksums-Sha256:
40eaea4aa8ecbf209000d13f92a3bf57cdeef2e3c01aec60b1941c2bf20ac9ff 2835
opendnssec_2.0.4-3.dsc
cebcee30c6d0ff32702fc6472ac0113e1524bd4e65cc0dcd2b713643791421c1 23760
opendnssec_2.0.4-3.debian.tar.xz
a71c9b06519b5b6ecebadb9ee5af393ffc87660a28aa9c4fdfbc29e69b80edb3 14881
opendnssec_2.0.4-3_amd64.buildinfo
Files:
f86f4e55e07eda0024d572a52f7a7a89 2835 admin extra opendnssec_2.0.4-3.dsc
b2001c6bb58af5e08979ea10af262eb2 23760 admin extra
opendnssec_2.0.4-3.debian.tar.xz
8f40e84bce786e1c37f048fdac647f17 14881 admin extra
opendnssec_2.0.4-3_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQKTBAEBCgB9FiEEMLkz2A/OPZgaLTj7DJm3DvT8uwcFAlkQbDlfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDMw
QjkzM0Q4MEZDRTNEOTgxQTJEMzhGQjBDOTlCNzBFRjRGQ0JCMDcACgkQDJm3DvT8
uwcpKA//WIXEq8LRO2v0dANFC+9RttzHWrHpmecwckdP5uDmzjjRmwzqkW2zzdVd
R43KblPU/Oxf3JKbB4G1w/rh7Qm4UX/ftwuxIlqNy14Ss/A/NU5m6E0RxN/I6a1O
UxlukzkJMpqe/Zea6h/txZn28sy0CB7ly44tmHC552hdBVtql2VMOLDfsSIkIg0U
d3oDT9VJrO/40yXioS/qbRo0YECpPcMh7Fb23wdPuhGiF2ZFE79DQApLWcEg6V8G
OGBr86oEsXKHSyITLdoWt06036Unna0CFturT77wH8CudO+umPCE3rWQURfhXkaJ
3Ys4kDcuc8XtnZY2qGRgEtZvy9UuyPxHp9hoWq97u5qi5puIrR6yosuPFSrWjyZA
X8FzYK4yqAiCqEytlpFiedSZTYEzMRmqZAKUxmBchhTLMICQiRZOOSZ7EHxpFoAl
/l962lboFAjVi/FfZb5g+M6V
Bug#859419: non-functional after installation (service fails to start)
Control: severity -1 important Hi, this is not something really fixable without breaking existing user base (for now). The problem is that you need configured and initialized HSM store for the keys, and that something the user must do manually, because he is expected to provide his own HSM - and while softhsm2 is the most common implementation used together with OpenDNSSEC, it's not the only one. I could probably provide --no-start to dh_systemd_start invocation, but doing that now inside the stretch freeze would be very disruptive (in my opinion). It might be also fixed upstream to not exit violently when no key store is configured, but just refuse to generate new keys and log that prominently. I have fixed the other two RC bugs, and I am lowering the severity on this one, as this is how the OpenDNSSEC have worked since the beginning. Cheers, -- Ondřej Surý Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware, fast DNS(SEC) resolver Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro pečení chleba všeho druhu
Bug#862098: lxterminal: socket can be blocked by another user
Package: lxterminal Version: 0.3.0-1 Severity: grave Tags: upstream patch security Justification: user security hole -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 This vulnerability is discussed in a Stackexchange website: https://unix.stackexchange.com/questions/333539/lxterminal-in-the-netstat-output/333578 The socket placed in /tmp is predictable and public-writable, Therefore if Alice placed a file or lxterminal socket in /tmp/.lxterminal-socket:0-bob, bob is unable to open lxterminal, or open a lxterminal instance for Alice. This bug is fixed in the commit: https://git.lxde.org/gitweb/?p=lxde/lxterminal.git;a=commit;h=f99163c6ff8b2f57c5f37b1ce5d62cf7450d4648 - -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lxterminal depends on: ii libatk1.0-0 2.22.0-1 ii libc62.24-10 ii libcairo21.14.8-1 ii libfontconfig1 2.11.0-6.7+b1 ii libfreetype6 2.6.3-3.2 ii libgdk-pixbuf2.0-0 2.36.5-2 ii libglib2.0-0 2.50.3-2 ii libgtk2.0-0 2.24.31-2 ii libpango-1.0-0 1.40.5-1 ii libpangocairo-1.0-0 1.40.5-1 ii libpangoft2-1.0-01.40.5-1 ii libvte9 1:0.28.2-5+b2 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 lxterminal recommends no packages. lxterminal suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQJCBAEBCAAsFiEE/tVDSEUoffJikxSJz7v84LdPGxQFAlkQbdkOHG13ZWlAbHhk ZS5vcmcACgkQz7v84LdPGxSZuA/+NEEhU73k2esU8FveOzTc0ei0b5NLC2y5zvY/ /To8BTaUJAQE3J1icvgV3JRPJI8YOin5Ombz1n+4URt+f17G00mWplyGQgFiXcKP oooPl93If2rfi3POFM3MoC6grRc5UdwpUcTimwaX4OEE/PUZNHnfoNI2pWPk0Z34 AcGVqbJzxagpqzwvzsjjHC2EOncSeTfm2nZzUIwWfXV+LdGgq2Sf2oyaAYH/QnuV bvGAGgCZCNFejn9m3VHA7SIEU8AV+/FaJ/8sT5WJIyWWBoEBkcig50Ya5UG71zVq VTixWAbnCLhfQ44xKsFvGD+h6LH4c6qgQxnxk16yQrUOAZsIFHDuc9xIMBJtGLJt G3hZFY7x0sry4GVgHdqDvxI51UgWuZuUJNTTtXOuu0Yno0gcwY8TCC3QBtIk+4kQ 61tTbNoho7wTjn8reY+SgcUXeLdUAbKXdcv3IOp25LmiPLHV5dGfnRXH8Gw/ZQCz B9Tli0Ge3yNXaC0MJzgyaopNPdqzBNII5IWwfjknVy6K6uQCiHx9UCbOfxDre9sp DbgENkagS5P8+lNVOtGHr55n/2bg+kKLOztOKBBp0vqdwaKnKAuE0BZfOx78msgs P+vGhzOARu/y2V/n4AAPPiE9SlRZIQg+oX1+5syzXiRD2dLOUbXqRLmVZwaqLsKG 0oN43Nk= =fmHh -END PGP SIGNATURE-
Bug#862095: reportbug: Bugs in backported packages must not be sent to the BTS
Hi! I disagree with making this RC right now, for the following reasons: > Bugs against backported packages (~bpo versions) are not allowed > to be reported to the BTS without explicit permission from the > maintainer to do so 1. There is no automated way for the maintainers to agree to that currently, formally (but see below). >, and should instead automatically be sent > to debian-backpo...@lists.debian.org 2. This is normally the backporter’s duty: reportbug supports a Bugs: field in debian/control which lists an eMail address where bugreports should be sent to; for an example of a package using this, look at e.g. my wtf package: https://www.mirbsd.org/~tg/Debs/dists/sarge/wtf/Pkgs/wtf/wtf_2016_all.deb 3. Absense of such a field *could*, however, be seen as maintainer approval of bugreports in the BTS (especially if the backporter is the maintainer), so there’s nothing that reportbug should do at the moment. 4. Due to the above, I believe a short-circuit/knee-jerk reaction to force reportbug to deliver _all_ bpo bugreports to the bpo mailing list is wrong, and this should at the least be tagged with stretch-ignore and discussed more broadly. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Bug#862095: reportbug: Bugs in backported packages must not be sent to the BTS
Package: reportbug Version: 6.6.3 Severity: serious Bugs against backported packages (~bpo versions) are not allowed to be reported to the BTS without explicit permission from the maintainer to do so, and should instead automatically be sent to debian-backpo...@lists.debian.org Example for a bug that was wrongly sent to the BTS: #860147
Bug#862052: same bug
Hi, Same bug for me with 1.3.6-5 Solved with 1.3.6-5.1
Bug#840516: patterns are deprecated
There are several reasons why graphite-web does not work with Django
1.10 (the current version in sid). One of them is that it uses the
"patterns" variable:
Traceback (most recent call last):
File "/usr/bin/graphite-manage", line 15, in
execute_from_command_line(sys.argv)
File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py",
line 367, in execute_from_command_line
utility.execute()
File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py",
line 359, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line
294, in run_from_argv
self.execute(*args, **cmd_options)
File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line
342, in execute
self.check()
File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line
374, in check
include_deployment_checks=include_deployment_checks,
File
"/usr/lib/python2.7/dist-packages/django/core/management/commands/migrate.py",
line 62, in _run_checks
issues.extend(super(Command, self)._run_checks(**kwargs))
File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line
361, in _run_checks
return checks.run_checks(**kwargs)
File "/usr/lib/python2.7/dist-packages/django/core/checks/registry.py", line
81, in run_checks
new_errors = check(app_configs=app_configs)
File "/usr/lib/python2.7/dist-packages/django/core/checks/urls.py", line 14,
in check_url_config
return check_resolver(resolver)
File "/usr/lib/python2.7/dist-packages/django/core/checks/urls.py", line 24,
in check_resolver
for pattern in resolver.url_patterns:
File "/usr/lib/python2.7/dist-packages/django/utils/functional.py", line 35,
in __get__
res = instance.__dict__[self.name] = self.func(instance)
File "/usr/lib/python2.7/dist-packages/django/urls/resolvers.py", line 313,
in url_patterns
patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
File "/usr/lib/python2.7/dist-packages/django/utils/functional.py", line 35,
in __get__
res = instance.__dict__[self.name] = self.func(instance)
File "/usr/lib/python2.7/dist-packages/django/urls/resolvers.py", line 306,
in urlconf_module
return import_module(self.urlconf_name)
File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
File "/usr/lib/python2.7/dist-packages/graphite/urls.py", line 29, in
urlpatterns = patterns('',
NameError: name 'patterns' is not defined
Which has been removed from Django in 1.9:
https://docs.djangoproject.com/en/1.9/ref/urls/#patterns
Bug#861913: mariadb-client-10.1: trying to overwrite '/usr/bin/mytop', which is also in package mytop 1.9.1-4
https://anonscm.debian.org/git/pkg-mysql/mariadb-10.1.git/commit/?id=2a17c70476de768f1e166b65f4a1b3865ac9757f -- Ondřej Surý Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware, fast DNS(SEC) resolver Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro pečení chleba všeho druhu On Mon, May 8, 2017, at 12:08, Olaf van der Spek wrote: > 2017-05-08 11:42 GMT+02:00 Ondřej Surý : > > Definitely, I am just building the fixed version. I did a cleanup of > > upstream files not being installed in the last bigger mariadb update, > > and I was just not aware mytop was already packaged. Sorry for the > > troubles. > > Shouldn't it also declare a Replaces?
Bug#861913: mariadb-client-10.1: trying to overwrite '/usr/bin/mytop', which is also in package mytop 1.9.1-4
2017-05-08 11:42 GMT+02:00 Ondřej Surý : > Definitely, I am just building the fixed version. I did a cleanup of > upstream files not being installed in the last bigger mariadb update, > and I was just not aware mytop was already packaged. Sorry for the > troubles. Shouldn't it also declare a Replaces?
Bug#861913: marked as done (mariadb-client-10.1: trying to overwrite '/usr/bin/mytop', which is also in package mytop 1.9.1-4)
Your message dated Mon, 08 May 2017 10:03:55 + with message-id and subject line Bug#861913: fixed in mariadb-10.1 10.1.23-4 has caused the Debian Bug report #861913, regarding mariadb-client-10.1: trying to overwrite '/usr/bin/mytop', which is also in package mytop 1.9.1-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.) -- 861913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mariadb-client-10.1 Version: 10.1.22-3 Severity: normal Hi, Not sure how mytop ended up in mariadb-client.. # apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: mariadb-client-10.1 The following packages will be upgraded: mariadb-client-10.1 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 38 not fully installed or removed. Need to get 0 B/5,816 kB of archives. After this operation, 21.5 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 64666 files and directories currently installed.) Preparing to unpack .../mariadb-client-10.1_10.1.23-3_amd64.deb ... Unpacking mariadb-client-10.1 (10.1.23-3) over (10.1.22-3) ... dpkg: error processing archive /var/cache/apt/archives/mariadb-client-10.1_10.1.23-3_amd64.deb (--unpack): trying to overwrite '/usr/bin/mytop', which is also in package mytop 1.9.1-4 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/mariadb-client-10.1_10.1.23-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Gr, Olaf -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages mariadb-client-10.1 depends on: ii debianutils 4.8.1.1 ii libc6 2.24-10 ii libstdc++66.3.0-16 iu mariadb-client-core-10.1 10.1.23-3 pn perl:any ii zlib1g1:1.2.8.dfsg-5 Versions of packages mariadb-client-10.1 recommends: ii libdbd-mysql-perl 4.041-2 ii libdbi-perl 1.636-1+b1 ii libterm-readkey-perl 2.37-1 mariadb-client-10.1 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: mariadb-10.1 Source-Version: 10.1.23-4 We believe that the bug you reported is fixed in the latest version of mariadb-10.1, 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 861...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý (supplier of updated mariadb-10.1 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: Mon, 08 May 2017 11:31:13 +0200 Source: mariadb-10.1 Binary: libmariadbclient18 libmariadbclient-dev libmariadbclient-dev-compat libmariadbd18 libmariadbd-dev mariadb-common mariadb-client-core-10.1 mariadb-client-10.1 mariadb-server-core-10.1 mariadb-server-10.1 mariadb-server mariadb-client mariadb-plugin-connect mariadb-plugin-oqgraph mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client mariadb-plugin-cracklib-password-check mariadb-test mariadb-test-data Architecture: source Version: 10.1.23-4 Distribution: unstable Urgency: medium Maintainer: Debian MySQL Maintainers Changed-By: Ondřej Surý Description: libmariadbclient-dev - MariaDB database development files libmariadbclient-dev-compat - MariaDB database development files (libmysqlclient compatibility) libmariadbclient18 - MariaDB database client library libmariadbd-dev - MariaDB embedded database, development files libmariadbd18 - MariaDB embedded database, shared library mariadb-client - MariaDB database client (metapackage depending on the latest vers mariadb-client-10.1 - M
Bug#860618: marked as done (golang-github-seccomp-libseccomp-golang: FTBFS on i386: dh_auto_test: go test -v -p 1 github.com/seccomp/libseccomp-golang returned exit code 1)
Your message dated Mon, 08 May 2017 09:48:26 + with message-id and subject line Bug#860618: fixed in golang-github-seccomp-libseccomp-golang 0.0~git20150813.0.1b506fc-2 has caused the Debian Bug report #860618, regarding golang-github-seccomp-libseccomp-golang: FTBFS on i386: dh_auto_test: go test -v -p 1 github.com/seccomp/libseccomp-golang returned exit code 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.) -- 860618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-seccomp-libseccomp-golang Version: 0.0~git20150813.0.1b506fc-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=golang --with=golang >dh_testdir -O--buildsystem=golang >dh_update_autotools_config -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang >dh_auto_build -O--buildsystem=golang > go install -v -p 1 github.com/seccomp/libseccomp-golang > github.com/seccomp/libseccomp-golang >dh_auto_test -O--buildsystem=golang > go test -v -p 1 github.com/seccomp/libseccomp-golang > === RUN TestActionSetReturnCode > --- PASS: TestActionSetReturnCode (0.00s) > === RUN TestSyscallGetName > Got name of syscall 0x1 on native arch as exit > --- PASS: TestSyscallGetName (0.00s) > === RUN TestSyscallGetNameByArch > --- PASS: TestSyscallGetNameByArch (0.00s) > === RUN TestGetSyscallFromName > Got syscall number of write on native arch as 4 > --- PASS: TestGetSyscallFromName (0.00s) > === RUN TestGetSyscallFromNameByArch > Got syscall number of write on AMD64 as 1 > --- PASS: TestGetSyscallFromNameByArch (0.00s) > === RUN TestMakeCondition > --- PASS: TestMakeCondition (0.00s) > === RUN TestGetNativeArch > Got native arch of system as x86 > --- PASS: TestGetNativeArch (0.00s) > === RUN TestFilterCreateRelease > --- PASS: TestFilterCreateRelease (0.00s) > === RUN TestFilterReset > --- PASS: TestFilterReset (0.00s) > === RUN TestFilterArchFunctions > --- PASS: TestFilterArchFunctions (0.00s) > === RUN TestFilterAttributeGettersAndSetters > --- PASS: TestFilterAttributeGettersAndSetters (0.00s) > === RUN TestMergeFilters > --- PASS: TestMergeFilters (0.00s) > === RUN TestRuleAddAndLoad > --- FAIL: TestRuleAddAndLoad (0.00s) > seccomp_test.go:455: Syscall should have returned error code! > FAIL > exit status 1 > FAIL github.com/seccomp/libseccomp-golang0.004s > dh_auto_test: go test -v -p 1 github.com/seccomp/libseccomp-golang returned > exit code 1 The full build log is available from: http://aws-logs.debian.net/2017/04/18/golang-github-seccomp-libseccomp-golang_0.0~git20150813.0.1b506fc-1_testing-i386.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: golang-github-seccomp-libseccomp-golang Source-Version: 0.0~git20150813.0.1b506fc-2 We believe that the bug you reported is fixed in the latest version of golang-github-seccomp-libseccomp-golang, 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 860...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roger Shimizu (supplier of updated golang-github-seccomp-libseccomp-golang package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 May 2017 12:09:57 +0900 Source: golang-github-seccomp-libseccomp-golang Binary: golang-github-seccomp-libseccomp-golang-dev Architecture: source Version: 0.0~git20150813.0.1b506fc-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team
Bug#861804: marked as done (slrn non-free license issue)
Your message dated Mon, 08 May 2017 09:49:14 +
with message-id
and subject line Bug#861804: fixed in slrn 1.0.3+dfsg-1
has caused the Debian Bug report #861804,
regarding slrn non-free license issue
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.)
--
861804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: slrn non-free license issue
Package: slrn
Version: 1.0.3a-1
The slrn sources contain a file with a non-free license with
slrn-1.0.3/src/vms.c:
> Copyright : (c) Copyright 1991-95 by Iain Lea & Andrew Greer
> You may freely copy or redistribute this software,
> so long as there is no profit made from its use, sale
> trade or reproduction. You may not change this copy-
> right notice, and it must be included in any copy made
This file is only used when building on VMS and can be removed from the
tarball.
The sources are non-free nevertheless due the the non-commercial
restriction.
In addition, slrn-1.0.3/src/help.c refers to a non-free license.
It is printed only VMS where SLRN_USE_SLTCP is 1:
> This software is Copyright 1991 by Stan Barber.
>
> Permission is hereby granted to copy, reproduce, redistribute or otherwise
> use this software as long as: there is no monetary profit gained
> specifically from the use or reproduction or this software, it is not
> sold, rented, traded or otherwise marketed, and this copyright notice is
> included prominently in any copy made.
It applies to slrn-1.0.3/src/clientlib.{c,h}, which have already been
cleared
from the upstream tarball:
> #error This file has been removed from the slrn source tarball because its
> #error license is more restrictive than the one of slrn itself.
>
> #error If you want to compile slrn for VMS and need this file, please
get it
> #error from http://slrn.sourceforge.net/data/clientlib.tar.gz
The help output may be cleared:
sed '/^#if ! SLRN_USE_SLTCP$/,/^#endif$/d'
--- End Message ---
--- Begin Message ---
Source: slrn
Source-Version: 1.0.3+dfsg-1
We believe that the bug you reported is fixed in the latest version of
slrn, 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 861...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Moritz Muehlenhoff (supplier of updated slrn package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 05 May 2017 19:35:29 +0200
Source: slrn
Binary: slrn slrnpull
Architecture: source amd64
Version: 1.0.3+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Moritz Muehlenhoff
Changed-By: Moritz Muehlenhoff
Description:
slrn - threaded text-mode news reader
slrnpull - pulls a small newsfeed from an NNTP server
Closes: 861804
Changes:
slrn (1.0.3+dfsg-1) unstable; urgency=medium
.
* Strip non-free vms.c from the tarball (only needed for builds
on VMS). Thanks to Andreas Stieger for the report (Closes: #861804)
Checksums-Sha1:
7e244730f7fd7270cb5069ff701115bf17b754c5 1957 slrn_1.0.3+dfsg-1.dsc
357a21ababaac3a5fed4776436726e4a803e6427 1036038 slrn_1.0.3+dfsg.orig.tar.bz2
0db6e628ed59fe03170be22f9834e333141983f5 50212 slrn_1.0.3+dfsg-1.debian.tar.xz
9aea13d0cb5c1dd3ad0f32620dde4f7e2c3e286f 6554 slrn_1.0.3+dfsg-1_amd64.buildinfo
f84abd42cd432b2d02cb694ca38b9d77e1e62846 564420 slrn_1.0.3+dfsg-1_amd64.deb
09914af9d10914d4121e0fa5a9d42eb6ff17d438 139082 slrnpull_1.0.3+dfsg-1_amd64.deb
Checksums-Sha256:
54acc1bebb8724f2ef4376a601feaa9db6e0b5188a2b0ec9d56c6f7ff55034bd 1957
slrn_1.0.3+dfsg-1.dsc
1513dbb1fe3916437cd0d9e6c08aeeff85d222b1d67c40d507601680b55373d1 1036038
slrn_1.0.3+dfsg.orig.tar.bz2
bd0547f3fc07f25478af768d5d5bb7b2923e20449a73b8c373cb4a8408023cb8 50212
slrn_1.0.3+dfsg-1.debian.tar.xz
68dc9cba21f092b2739191672973c65e457db26b48ceae88c13cbd0a299a1342 6554
slrn_1.0.3+dfsg-1_amd64.buildinfo
9001d0cee516f11b127545c8c1f4620bf3adcbee3b4b2013db4c892ba573d4ba 564420
slrn_1.0.3+dfsg-1_amd64.deb
c15cfddbf640c1631993b8a2cd12576eb15a8892f4c8af761ac611eb51dea77a 139082
slrnpull_1.0.3+dfsg-1_amd64.deb
Files:
899cd49f9dca7378972deda8d1529069 1957 news o
Bug#861913: mariadb-client-10.1: trying to overwrite '/usr/bin/mytop', which is also in package mytop 1.9.1-4
Hi Ondřej, Shouldn't it conflict / replace the mytop pkg? 2017-05-08 11:34 GMT+02:00 Ondřej Surý : > Hi Olaf, > > mytop is part of MariaDB a version that fixes little bugs here and > there: > > +=item Michael "Monty" Widenius > + > +Fixed a couple of minor bugs that gave warnings on startup. > +Added support for MariaDB (show MariaDB at top and % done). > +Cut long server version names to display width. > +Made 'State' length dynamic.
Bug#861913: mariadb-client-10.1: trying to overwrite '/usr/bin/mytop', which is also in package mytop 1.9.1-4
Definitely, I am just building the fixed version. I did a cleanup of upstream files not being installed in the last bigger mariadb update, and I was just not aware mytop was already packaged. Sorry for the troubles. Cheers, -- Ondřej Surý Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware, fast DNS(SEC) resolver Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro pečení chleba všeho druhu On Mon, May 8, 2017, at 11:40, Olaf van der Spek wrote: > Hi Ondřej, > > Shouldn't it conflict / replace the mytop pkg? > > 2017-05-08 11:34 GMT+02:00 Ondřej Surý : > > Hi Olaf, > > > > mytop is part of MariaDB a version that fixes little bugs here and > > there: > > > > +=item Michael "Monty" Widenius > > + > > +Fixed a couple of minor bugs that gave warnings on startup. > > +Added support for MariaDB (show MariaDB at top and % done). > > +Cut long server version names to display width. > > +Made 'State' length dynamic.
Bug#861913: mariadb-client-10.1: trying to overwrite '/usr/bin/mytop', which is also in package mytop 1.9.1-4
Hi Olaf, mytop is part of MariaDB a version that fixes little bugs here and there: +=item Michael "Monty" Widenius + +Fixed a couple of minor bugs that gave warnings on startup. +Added support for MariaDB (show MariaDB at top and % done). +Cut long server version names to display width. +Made 'State' length dynamic. Cheers, -- Ondřej Surý Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware, fast DNS(SEC) resolver Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro pečení chleba všeho druhu On Fri, May 5, 2017, at 21:21, Olaf van der Spek wrote: > Package: mariadb-client-10.1 > Version: 10.1.22-3 > Severity: normal > > Hi, > > Not sure how mytop ended up in mariadb-client.. > > # apt --fix-broken install > Reading package lists... Done > Building dependency tree > Reading state information... Done > Correcting dependencies... Done > The following additional packages will be installed: > mariadb-client-10.1 > The following packages will be upgraded: > mariadb-client-10.1 > 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > 38 not fully installed or removed. > Need to get 0 B/5,816 kB of archives. > After this operation, 21.5 MB of additional disk space will be used. > Do you want to continue? [Y/n] > (Reading database ... 64666 files and directories currently installed.) > Preparing to unpack .../mariadb-client-10.1_10.1.23-3_amd64.deb ... > Unpacking mariadb-client-10.1 (10.1.23-3) over (10.1.22-3) ... > dpkg: error processing archive > /var/cache/apt/archives/mariadb-client-10.1_10.1.23-3_amd64.deb > (--unpack): > trying to overwrite '/usr/bin/mytop', which is also in package mytop > 1.9.1-4 > dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) > Errors were encountered while processing: > /var/cache/apt/archives/mariadb-client-10.1_10.1.23-3_amd64.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > > Gr, > > Olaf > > -- System Information: > Debian Release: 9.0 > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 > (x86_64) > > Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages mariadb-client-10.1 depends on: > ii debianutils 4.8.1.1 > ii libc6 2.24-10 > ii libstdc++66.3.0-16 > iu mariadb-client-core-10.1 10.1.23-3 > pn perl:any > ii zlib1g1:1.2.8.dfsg-5 > > Versions of packages mariadb-client-10.1 recommends: > ii libdbd-mysql-perl 4.041-2 > ii libdbi-perl 1.636-1+b1 > ii libterm-readkey-perl 2.37-1 > > mariadb-client-10.1 suggests no packages. > > -- no debconf information >
Bug#861855: marked as done (php7.0-fpm: Uses kill without depending on procps)
Your message dated Mon, 08 May 2017 09:18:45 + with message-id and subject line Bug#861855: fixed in php7.0 7.0.18-3 has caused the Debian Bug report #861855, regarding php7.0-fpm: Uses kill without depending on procps 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.) -- 861855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: php7.0-fpm Version: 7.0.16-3 Severity: serious Justification: Policy 3.5 /lib/systemd/system/php7.0-fpm.service contains: ``` ExecReload=/bin/kill -USR2 $MAINPID ``` procps is not Essential. --- End Message --- --- Begin Message --- Source: php7.0 Source-Version: 7.0.18-3 We believe that the bug you reported is fixed in the latest version of php7.0, 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 861...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý (supplier of updated php7.0 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: Mon, 08 May 2017 10:25:18 +0200 Source: php7.0 Binary: libapache2-mod-php7.0 libphp7.0-embed php7.0 php7.0-cgi php7.0-cli php7.0-dev php7.0-fpm php7.0-phpdbg php7.0-xsl php7.0-intl php7.0-odbc php7.0-readline php7.0-recode php7.0-sqlite3 php7.0-xml php7.0-zip php7.0-sybase php7.0-gd php7.0-gmp php7.0-ldap php7.0-common php7.0-tidy php7.0-mcrypt php7.0-snmp php7.0-curl php7.0-json php7.0-pgsql php7.0-mbstring php7.0-enchant php7.0-opcache php7.0-imap php7.0-mysql php7.0-bcmath php7.0-soap php7.0-dba php7.0-interbase php7.0-xmlrpc php7.0-pspell php7.0-bz2 Architecture: source Version: 7.0.18-3 Distribution: unstable Urgency: medium Maintainer: Debian PHP Maintainers Changed-By: Ondřej Surý Description: libapache2-mod-php7.0 - server-side, HTML-embedded scripting language (Apache 2 module) libphp7.0-embed - HTML-embedded scripting language (Embedded SAPI library) php7.0 - server-side, HTML-embedded scripting language (metapackage) php7.0-bcmath - Bcmath module for PHP php7.0-bz2 - bzip2 module for PHP php7.0-cgi - server-side, HTML-embedded scripting language (CGI binary) php7.0-cli - command-line interpreter for the PHP scripting language php7.0-common - documentation, examples and common module for PHP php7.0-curl - CURL module for PHP php7.0-dba - DBA module for PHP php7.0-dev - Files for PHP7.0 module development php7.0-enchant - Enchant module for PHP php7.0-fpm - server-side, HTML-embedded scripting language (FPM-CGI binary) php7.0-gd - GD module for PHP php7.0-gmp - GMP module for PHP php7.0-imap - IMAP module for PHP php7.0-interbase - Interbase module for PHP php7.0-intl - Internationalisation module for PHP php7.0-json - JSON module for PHP php7.0-ldap - LDAP module for PHP php7.0-mbstring - MBSTRING module for PHP php7.0-mcrypt - libmcrypt module for PHP php7.0-mysql - MySQL module for PHP php7.0-odbc - ODBC module for PHP php7.0-opcache - Zend OpCache module for PHP php7.0-pgsql - PostgreSQL module for PHP php7.0-phpdbg - server-side, HTML-embedded scripting language (PHPDBG binary) php7.0-pspell - pspell module for PHP php7.0-readline - readline module for PHP php7.0-recode - recode module for PHP php7.0-snmp - SNMP module for PHP php7.0-soap - SOAP module for PHP php7.0-sqlite3 - SQLite3 module for PHP php7.0-sybase - Sybase module for PHP php7.0-tidy - tidy module for PHP php7.0-xml - DOM, SimpleXML, WDDX, XML, and XSL module for PHP php7.0-xmlrpc - XMLRPC-EPI module for PHP php7.0-xsl - XSL module for PHP (dummy) php7.0-zip - Zip module for PHP Closes: 861855 Changes: php7.0 (7.0.18-3) unstable; urgency=medium . * php-fpm has to depend on procps due kill usage in systemd service file (Closes: #861855) * Regenerate d/control * Do a fresh rewrap of debian/ directory Checksums-Sha1: 9634b9e01bbff31a9da14611b096ecc7441e4b11 5762 php7.0_7.0.18-3.dsc 5fa251e91729a8cf4c94de2c712af984e32e454f 91456 php7.0_7.0.18-3.debian.tar.xz e672b74edc018aefa634f10f013ad9d912909dad 33547 php7.0_7.0.18-3_amd64.buildinfo Checksums-Sha256: 9cc7ca6c4803b00702764b49d02169f6bde98ca2b215afa413388570335a7f7e 5762 ph
Processed: Bug housekeeping
Processing commands for cont...@bugs.debian.org:
> # The BTS still considers this bug to apply to testing
> # and unstable, hopefully this command is enough to mark
> # the bug as done there.
> fixed 859805 3.1.4-4
Bug #859805 {Done: Scott Kitterman } [postfix-ldap]
postfix-ldap: unsupported dictionary type: ldap after upgrade
Marked as fixed in versions postfix/3.1.4-4.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
859805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#851545: Version tracking fix
Control: found -1 1.1.8-3.1 What causes this breakage is the date in the manpage, which is the date of the package build. Always likely to hit on jessie when the upload contained amd64 (or i386) binaries. On stretch this is breakage waiting to happen when a DSA gets built on different days on different architectures. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: iceweasel is now firefox
Processing commands for cont...@bugs.debian.org: > reassign 788721 src:firefox-esr Bug #788721 [src:iceweasel] [src:iceweasel] Some sources are not included in your package Warning: Unknown package 'src:iceweasel' Bug reassigned from package 'src:iceweasel' to 'src:firefox-esr'. No longer marked as found in versions iceweasel/43.0.4-1, iceweasel/44.0-1, and iceweasel/39.0~b1-1. Ignoring request to alter fixed versions of bug #788721 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 788721: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788721 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Version tracking fix
Processing control commands: > found -1 1.1.8-3.1 Bug #851545 [libpam-modules] libpam-modules: multiarch packages with differing files Marked as found in versions pam/1.1.8-3.1. -- 851545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#855927: marked as done (golang-prometheus-client: FTBFS: dh_auto_build: go install -v -p 1 github.com/prometheus/client_golang/deps/bitbucket.org/ww/goautoneg github.com/prometheus/client_golang/d
Your message dated Mon, 8 May 2017 11:35:37 +0300 with message-id <20170508083535.d5hogtbpxxbdsjeo@localhost> and subject line src:golang-prometheus-client binaries have been removed from stretch/sid has caused the Debian Bug report #855927, regarding golang-prometheus-client: FTBFS: dh_auto_build: go install -v -p 1 github.com/prometheus/client_golang/deps/bitbucket.org/ww/goautoneg github.com/prometheus/client_golang/deps/github.com/beorn7/perks/quantile github.com/prometheus/client_golang/extraction github.com/prometheus/client_golang/model github.com/prometheus/client_golang/prometheus github.com/prometheus/client_golang/text returned exit code 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.) -- 855927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-prometheus-client Version: 0.7.0+ds-3 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170221 qa-ftbfs Justification: FTBFS in stretch on amd64 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>/golang-prometheus-client-0.7.0+ds' > dh_auto_configure -O--buildsystem=golang > mkdir -p obj-x86_64-linux-gnu > Copy examples/simple/main.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/examples/simple/main.go > Copy examples/random/main.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/examples/random/main.go > Copy model/signature.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/model/signature.go > Copy model/labelname.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/model/labelname.go > Copy model/labelvalue_test.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/model/labelvalue_test.go > Copy model/sample.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/model/sample.go > Copy model/labelset.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/model/labelset.go > Copy model/fingerprinting.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/model/fingerprinting.go > Copy model/labelvalue.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/model/labelvalue.go > Copy model/timestamp.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/model/timestamp.go > Copy model/samplevalue.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/model/samplevalue.go > Copy model/model.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/model/model.go > Copy model/sample_test.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/model/sample_test.go > Copy model/labelname_test.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/model/labelname_test.go > Copy model/timestamp_test.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/model/timestamp_test.go > Copy model/signature_test.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/model/signature_test.go > Copy model/metric_test.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/model/metric_test.go > Copy model/metric.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/model/metric.go > Copy prometheus/push.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/prometheus/push.go > Copy prometheus/histogram.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/prometheus/histogram.go > Copy prometheus/process_collector_test.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/prometheus/process_collector_test.go > Copy prometheus/histogram_test.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/prometheus/histogram_test.go > Copy prometheus/registry.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/prometheus/registry.go > Copy prometheus/vec_test.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/prometheus/vec_test.go > Copy prometheus/go_collector_test.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/prometheus/go_collector_test.go > Copy prometheus/registry_test.go -> > obj-x86_64-linux-gnu/src/github.com/prometheus/client_golang/prome
Bug#860608: marked as done (golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt)
Your message dated Mon, 8 May 2017 11:27:50 +0300 with message-id <20170508082750.lh5tt7d75uomuhpu@localhost> and subject line src:golang binaries have been removed from stretch/sid has caused the Debian Bug report #860608, regarding golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt 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.) -- 860608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang Version: 2:1.6.1-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418 qa-ftbfs Justification: FTBFS in stretch on amd64 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > set -ex; \ > cd src; \ > export PATH="/<>/bin:$PATH"; \ > eval "$(go tool dist env)"; \ > bash run.bash -k -no-rebuild; > + cd src > + export > PATH=/<>/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games > + go tool dist env > + eval CC="gcc" > CC_FOR_TARGET="gcc" > GOROOT="/<>" > GOBIN="/<>/bin" > GOARCH="amd64" > GOOS="linux" > GOHOSTARCH="amd64" > GOHOSTOS="linux" > GOTOOLDIR="/<>/pkg/tool/linux_amd64" > + CC=gcc > + CC_FOR_TARGET=gcc > + GOROOT=/<> > + GOBIN=/<>/bin > + GOARCH=amd64 > + GOOS=linux > + GOHOSTARCH=amd64 > + GOHOSTOS=linux > + GOTOOLDIR=/<>/pkg/tool/linux_amd64 > + bash run.bash -k -no-rebuild > > # Testing packages. > okarchive/tar 0.019s > okarchive/zip 0.215s > okbufio 0.193s > okbytes 0.204s > okcompress/bzip2 0.247s > okcompress/flate 0.831s > okcompress/gzip 0.100s > okcompress/lzw0.039s > okcompress/zlib 0.168s > okcontainer/heap 0.009s > okcontainer/list 0.038s > okcontainer/ring 0.017s > okcrypto/aes 0.083s > okcrypto/cipher 0.015s > okcrypto/des 0.085s > okcrypto/dsa 0.055s > okcrypto/ecdsa0.072s > okcrypto/elliptic 0.125s > okcrypto/hmac 0.024s > okcrypto/md5 0.047s > okcrypto/rand 0.050s > okcrypto/rc4 0.213s > okcrypto/rsa 0.146s > okcrypto/sha1 0.049s > okcrypto/sha256 0.036s > okcrypto/sha512 0.019s > okcrypto/subtle 0.008s > okcrypto/tls 2.594s > okcrypto/x509 3.088s > okdatabase/sql0.136s > okdatabase/sql/driver 0.066s > okdebug/dwarf 0.039s > okdebug/elf 0.117s > okdebug/gosym 0.520s > okdebug/macho 0.032s > okdebug/pe0.034s > okdebug/plan9obj 0.017s > okencoding/ascii850.088s > okencoding/asn1 0.021s > okencoding/base32 0.020s > okencoding/base64 0.035s > okencoding/binary 0.043s > okencoding/csv0.037s > okencoding/gob0.055s > okencoding/hex0.048s > okencoding/json 0.412s > okencoding/pem0.046s > okencoding/xml0.024s > okerrors 0.021s > okexpvar 0.017s > okflag0.026s > okfmt 0.205s > okgo/ast 0.040s > okgo/build0.205s > okgo/constant 0.023s > okgo/doc 0.125s > okgo/format 0.041s > okgo/internal/gccgoimporter 0.013s > okgo/internal/gcimporter 0.314s > okgo/parser 0.086s > okgo/printer 0.716s > okgo/scanner 0.049s > okgo/token0.044s > okgo/types1.656s > okhash/adler320.032s > okhash/crc32 0.039s > okhash/crc64 0.045s > okhash/fnv0.038s > okhtml0.019s > okhtml/template 0.078s > okimage 0.226s > okimage/color 0.110s > okimage/draw 0.117s > okimage/gif 0.160s > okimage/jpeg 0.341s > okimage/png 0.103s > okindex/suffixarray 0.044s > okinternal/golang.org/x/net/http2/hpack 0.029s > okinternal/singleflight 0.062s > okinternal/trace 0.069s > okio 0.048s > okio/ioutil 0.014s > oklog 0.020s > oklog/syslog 2.055s > okmath0.017s > okmath/big1.017s > okmath/cmplx 0.009s > okmath/rand 0.189s > okmime0.087s > okmime/multipart 1.560s > okmime/quotedprintable0.759s > oknet 1.464s > oknet/http10.894s > oknet/http/cgi0.616s > oknet/http/cookiejar 0.012s > oknet/http/fcgi 0.009s > oknet/http/httptest 0.026s > oknet/http/httputil 0.21
Bug#860606: marked as done (golang-1.6: FTBFS: Go version is "go1.6.3", ignoring -next /<>/api/next.txt)
Your message dated Mon, 8 May 2017 11:24:11 +0300 with message-id <20170508082410.kfmh3l6khny5x2ez@localhost> and subject line src:golang-1.6 binaries have been removed from stretch/sid has caused the Debian Bug report #860606, regarding golang-1.6: FTBFS: Go version is "go1.6.3", ignoring -next /<>/api/next.txt 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.) -- 860606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-1.6 Version: 1.6.3-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418 qa-ftbfs Justification: FTBFS in stretch on amd64 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > set -ex; \ > cd src; \ > export PATH="/<>/bin:$PATH"; \ > eval "$(go tool dist env)"; \ > bash run.bash -k -no-rebuild; > + cd src > + export > PATH=/<>/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games > + go tool dist env > + eval CC="gcc" > CC_FOR_TARGET="gcc" > GOROOT="/<>" > GOBIN="/<>/bin" > GOARCH="amd64" > GOOS="linux" > GOHOSTARCH="amd64" > GOHOSTOS="linux" > GOTOOLDIR="/<>/pkg/tool/linux_amd64" > + CC=gcc > + CC_FOR_TARGET=gcc > + GOROOT=/<> > + GOBIN=/<>/bin > + GOARCH=amd64 > + GOOS=linux > + GOHOSTARCH=amd64 > + GOHOSTOS=linux > + GOTOOLDIR=/<>/pkg/tool/linux_amd64 > + bash run.bash -k -no-rebuild > > # Testing packages. > okarchive/tar 0.121s > okarchive/zip 0.207s > okbufio 0.168s > okbytes 0.254s > okcompress/bzip2 0.209s > okcompress/flate 0.832s > okcompress/gzip 0.125s > okcompress/lzw0.008s > okcompress/zlib 0.142s > okcontainer/heap 0.015s > okcontainer/list 0.037s > okcontainer/ring 0.029s > okcrypto/aes 0.066s > okcrypto/cipher 0.032s > okcrypto/des 0.025s > okcrypto/dsa 0.066s > okcrypto/ecdsa0.125s > okcrypto/elliptic 0.067s > okcrypto/hmac 0.019s > okcrypto/md5 0.021s > okcrypto/rand 0.070s > okcrypto/rc4 0.154s > okcrypto/rsa 0.156s > okcrypto/sha1 0.029s > okcrypto/sha256 0.015s > okcrypto/sha512 0.030s > okcrypto/subtle 0.031s > okcrypto/tls 2.701s > okcrypto/x509 2.735s > okdatabase/sql0.201s > okdatabase/sql/driver 0.025s > okdebug/dwarf 0.039s > okdebug/elf 0.060s > okdebug/gosym 0.476s > okdebug/macho 0.035s > okdebug/pe0.078s > okdebug/plan9obj 0.061s > okencoding/ascii850.026s > okencoding/asn1 0.010s > okencoding/base32 0.018s > okencoding/base64 0.030s > okencoding/binary 0.018s > okencoding/csv0.037s > okencoding/gob0.107s > okencoding/hex0.062s > okencoding/json 0.350s > okencoding/pem0.064s > okencoding/xml0.016s > okerrors 0.036s > okexpvar 0.112s > okflag0.018s > okfmt 0.270s > okgo/ast 0.034s > okgo/build0.111s > okgo/constant 0.020s > okgo/doc 0.124s > okgo/format 0.077s > okgo/internal/gccgoimporter 0.023s > okgo/internal/gcimporter 0.369s > okgo/parser 0.079s > okgo/printer 0.624s > okgo/scanner 0.110s > okgo/token0.080s > okgo/types1.885s > okhash/adler320.053s > okhash/crc32 0.013s > okhash/crc64 0.009s > okhash/fnv0.021s > okhtml0.072s > okhtml/template 0.095s > okimage 0.326s > okimage/color 0.306s > okimage/draw 0.143s > okimage/gif 0.183s > okimage/jpeg 0.349s > okimage/png 0.084s > okindex/suffixarray 0.092s > okinternal/golang.org/x/net/http2/hpack 0.015s > okinternal/singleflight 0.122s > okinternal/trace 0.060s > okio 0.115s > okio/ioutil 0.082s > oklog 0.064s > oklog/syslog 2.079s > okmath0.031s > okmath/big0.949s > okmath/cmplx 0.039s > okmath/rand 0.126s > okmime0.019s > okmime/multipart 1.139s > okmime/quotedprintable0.639s > oknet 1.470s > oknet/http10.713s > oknet/http/cgi1.495s > oknet/http/cookiejar 0.034s > oknet/http/fcgi 0.033s > oknet/http/httptest 0.045s > oknet/http/httputil
Bug#862071: password-store: FTBFS: not ok 1 - Test "generate" command
Source: password-store
Version: 1.6.5-5
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Dear Maintainer,
password-store fails to build from source in unstable/amd64:
[…]
dh_auto_configure
dh_auto_build
make -j1
make[1]: Entering directory '«BUILDDIR»'
Password store is a shell script, so there is nothing to do. Try "make
install" instead.
make[1]: Leaving directory '«BUILDDIR»'
dh_auto_test
make -j1 test
make[1]: Entering directory '«BUILDDIR»'
ok 1 - Make sure we can run pass
ok 2 - Make sure we can initialize our test store
# passed all 2 test(s)
1..2
not ok 1 - Test "generate" command
#
# "$PASS" init $KEY1 &&
# "$PASS" generate cred 19 &&
# [[ $("$PASS" show cred | wc -m) -eq 20 ]]
#
not ok 2 - Test replacement of first line
#
# "$PASS" insert -m cred2 <<<"$(printf "this is a
big\\npassword\\nwith\\nmany\\nlines\\nin it bla bla")" &&
# PATH="$TEST_HOME:$PATH" FAKE_PWGEN_PASSWORD="This is a fake
password" "$PASS" generate -i cred2 88 &&
# [[ $("$PASS" show cred2) == "$(printf "This is a fake
password\\npassword\\nwith\\nmany\\nlines\\nin it bla bla")" ]]
#
# failed 2 among 2 test(s)
1..2
Makefile:67: recipe for target 'tests/t0010-generate-tests.sh' failed
make[1]: *** [tests/t0010-generate-tests.sh] Error 1
make[1]: Leaving directory '«BUILDDIR»'
dh_auto_test: make -j1 test returned exit code 2
debian/rules:3: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
[…]
The full build log is attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
password-store.1.6.5-5.unstable.amd64.log.txt.gz
Description: Binary data
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 861913 serious Bug #861913 [mariadb-client-10.1] mariadb-client-10.1: trying to overwrite '/usr/bin/mytop', which is also in package mytop 1.9.1-4 Severity set to 'serious' from 'normal' > quit Stopping processing here. Please contact me if you need assistance. -- 861913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
