Bug#863886: closing 863886, closing 863886

close 863886 0.13-4 close 863886 0.13-4~deb8u1 thanks

Processed: closing 863886, closing 863886

Processing commands for cont...@bugs.debian.org: > close 863886 0.13-4 Bug #863886 [jbig2dec] jbig2dec: CVE-2016-8729 Marked as fixed in versions jbig2dec/0.13-4. Bug #863886 [jbig2dec] jbig2dec: CVE-2016-8729 Marked Bug as done > close 863886 0.13-4~deb8u1 Bug #863886 {Done: Salvatore Bonaccorso

Bug#853599: opensurgsim: ftbfs with GCC-7

Hi Andreas, sorry about my radio silence. I'll take a look. -Paul On Wed, Sep 20, 2017, at 03:56 AM, Andreas Tille wrote: > Hi Paul, > > that's the last open gcc-7 bug of the Debian Med team. Could you please > have a look (or at least signal that you will not be able to care about > it)? > >

Bug#875535: [Pkg-d-devel] Bug#875535: closed by Matthias Klumpp <m...@debian.org> (Re: Bug#875878: ldc 1.3 doesn't build any of it's reverse dependencies)

Hi, 2017-09-21 8:20 GMT+09:00 Matthias Klumpp : > 2017-09-20 5:28 GMT+02:00 Nobuhiro Iwamatsu : >> Hi, >> >> sambamba package has not fixed this problem with ldc 1:1.4.0-1. >> Also, I confirmed that diet-ng fixed this problem. > > This is a different bug: >

Processed: gqrx-sdr: gqrx fails to start looking for old version of boost

Processing commands for cont...@bugs.debian.org: > tags 870094 +moreinfo +unreproducible Bug #870094 [gqrx-sdr] gqrx-sdr: gqrx fails to start looking for old version of boost Added tag(s) moreinfo. Bug #870094 [gqrx-sdr] gqrx-sdr: gqrx fails to start looking for old version of boost Added

Processed: tagging 876305, retitle 869783 to nvidia-driver: CVE-2017-6257, CVE-2017-6259, tagging 871046

Processing commands for cont...@bugs.debian.org: > tags 876305 + sid buster Bug #876305 {Done: Ralf Treinen } [src:polygen] polygen: FTBFS with ocaml 4.05.0 Added tag(s) sid and buster. > retitle 869783 nvidia-driver: CVE-2017-6257, CVE-2017-6259 Bug #869783 {Done: Andreas

Bug#876414: nvidia-kernel-dkms: security issues CVE-2017-6266, CVE-2017-6267, CVE-2017-6272

On Fri, 2017-09-22 at 00:15 +0200, Andreas Beckmann wrote: > On 09/21/2017 11:55 PM, Luca Boccassi wrote: > > 3 CVEs affecting the NVIDIA proprietary kernel modules have been > > published [1]: > > > > CVE-2017-6266, CVE-2017-6267, CVE-2017-6272 > > > > All affecting only the 384 branch, and

Bug#876416: libzstd FTBFS on mips(el): Allocation error : not enough memory

Source: libzstd Version: 1.3.1+dfsg-1 Severity: serious Hi Maintainer Builds of libzstd/1.3.1+dfsg-1 FTBFS on mips and mipsel where they were successful in the past. /*stdin*\: 5.90% (9900 => 5842431 bytes, /*stdout*\) roundTripTest: ./datagen -g60 -P99 |

Processed: bug 876353 is forwarded to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82284

Processing commands for cont...@bugs.debian.org: > forwarded 876353 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82284 Bug #876353 [gccgo-7] gccgo-7: unhandled signal 11 at s390x/ppc64 Changed Bug forwarded-to-address to 'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82284' from

Processed: bug 876353 is forwarded to https://github.com/golang/go/issues/21972

Processing commands for cont...@bugs.debian.org: > forwarded 876353 https://github.com/golang/go/issues/21972 Bug #876353 [gccgo-7] gccgo-7: unhandled signal 11 at s390x/ppc64 Changed Bug forwarded-to-address to 'https://github.com/golang/go/issues/21972' from 'https://gcc.gnu.org/PR82284'. >

Bug#875423: [Pkg-openssl-devel] Bug#875423: openssl: Please re-enable TLS 1.0 and TLS 1.1 (at least in testing)

On Mon, Sep 11, 2017 at 12:30:30PM +0200, Raphael Hertzog wrote: > But in Debian testing, we have real end-users (direct and through > "rolling" derivatives) and they should not have to be impacted by this > experiment IMO. I have to admit that I didn't consider derivatives that take a snapshot

Bug#876414: nvidia-kernel-dkms: security issues CVE-2017-6266, CVE-2017-6267, CVE-2017-6272

On 09/21/2017 11:55 PM, Luca Boccassi wrote: > 3 CVEs affecting the NVIDIA proprietary kernel modules have been > published [1]: > > CVE-2017-6266, CVE-2017-6267, CVE-2017-6272 > > All affecting only the 384 branch, and fixed in the 384.90 release. Since NVIDIA published these today, but nothing

Bug#875423: [Pkg-openssl-devel] Bug#875423: openssl: Please re-enable TLS 1.0 and TLS 1.1 (at least in testing)

On Mon, Sep 11, 2017 at 11:33:22AM +0200, Raphaël Hertzog wrote: > Or at least I would like a system-wide flag (in a configuration file?) to > let me re-enable old protocols easily. It was my understanding that other people also prefered to do this on a per package level and not system wide.

Bug#876414: nvidia-kernel-dkms: security issues CVE-2017-6266, CVE-2017-6267, CVE-2017-6272

Package: nvidia-kernel-dkms Version: 384.69-1 Severity: grave 3 CVEs affecting the NVIDIA proprietary kernel modules have been published [1]: CVE-2017-6266, CVE-2017-6267, CVE-2017-6272 All affecting only the 384 branch, and fixed in the 384.90 release. Kind regards, Luca Boccassi [1]

Processed: severity of 876070 is normal

Processing commands for cont...@bugs.debian.org: > severity 876070 normal Bug #876070 {Done: Michael Biebl } [libavahi-core7] libavahi-core7: Does not install Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#876342: [Pkg-utopia-maintainers] Bug#876342: Bug#876342: avahi-daemon: upgrade failed: failed to configure

Am 21.09.2017 um 20:05 schrieb Vincent Lefevre: > On 2017-09-21 18:47:40 +0200, Michael Biebl wrote: >> Can you provide steps how to reproduce the issue? I've upgraded avahi on >> several systems and did not run into this particular problem. > > I don't know whether this is reproducible, but this

Processed: severity of 876342 is normal

Processing commands for cont...@bugs.debian.org: > severity 876342 normal Bug #876342 [avahi-daemon] avahi-daemon: upgrade failed: failed to configure Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 876342:

Bug#876240: libghc-xmonad-contrib-dev: unmet dependency libghc-x11-xft-dev-0.3.1-c557c

On Wed, Sep 20, 2017 at 12:16:13AM +0200, Sacha Delanoue wrote: > I tried to install libghc-xmonad-contrib-dev by doing > `apt install libghc-xmonad-contrib-dev` on an up-to-date 9.1 Debian. > The install failed with the following information: > > The following packages have unmet dependencies: >

Bug#875423: openssl: Please re-enable TLS 1.0 and TLS 1.1 (at least in testing)

On 2017-09-11 12:30:30 [+0200], Raphael Hertzog wrote: > Yes, I'm aware of that but Kurt never said that he would be willing to > back off from completely disabling it before the buster release and > I don't see any benefit in modifying all server applications to re-enable > the protocols that we

Bug#871831: mono-tools: Depends on libwebkit1.1-cil which is deprecated

On Thu, Sep 21, 2017 at 2:21 PM, Jo Shields wrote: > Go ahead and NMU. Here's 2 git patches to apply on top of the previous one. I'll upload shortly. There are 2 rdepends for monodoc-browser: monodoc-manual (from src:mono) and gmime2.6. I'll file the gmime2.6 bug.

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

Control: clone 873508 -1 Control: retitle -1 Please use cgcc to check hosted C code instead of sparse Control: severity -1 normal Control: reassign -1 horst On Fri, Sep 01, 2017 at 09:46:44AM +0200, Uwe Kleine-König wrote: > @anarcat: Given that cgcc seems to work, would you agree to apply the >

Processed: Re: Bug#873508: sparse test failures on ppc32le (and other not so common archs)

Processing control commands: > clone 873508 -1 Bug #873508 [src:sparse] parsing horst source code fails on s390x and ppc64el Bug 873508 cloned as bug 876402 > retitle -1 Please use cgcc to check hosted C code instead of sparse Bug #876402 [src:sparse] parsing horst source code fails on s390x and

Bug#876400: php-horde-image: CVE-2017-14650: remote code execution n _raw() via $index parameter

Source: php-horde-image Version: 2.0.1-1 Severity: grave Tags: patch upstream security Hi, the following vulnerability was published for php-horde-image. CVE-2017-14650[0]: | A Remote Code Execution vulnerability has been found in the Horde_Image | library when using the "Im" backend that

Bug#871831: mono-tools: Depends on libwebkit1.1-cil which is deprecated

Go ahead and NMU. The problem with libwebkit2gtk-4.0-37 is it's a wrapper for allowing Gtk2 plugins in a Gtk3 browser - it's not a way for Gtk2 apps to continue to use Webkit Sent from Outlook From: Jeremy Bicha

Bug#876398: mysqltest can't read config proberly

Package: mariadb-test Version: 10.1.26-0+deb9u1 Severity: grave Hello, if I run mysqltest I get: > mysqltest mysqltest: unknown variable 'default-character-set=utf8mb4' mysqltest stops after that message and isn't useable. CU Jörg -- System Information: Debian Release: 9.1 APT prefers

Processed: closing 823511

Processing commands for cont...@bugs.debian.org: > # php-zend-diactoros and php-symfony-psr-http-message-bridge currently in NEW > depend on php-psr-http-message > close 823511 Bug #823511 [php-psr-http-message] Useless in Debian Marked Bug as done > thanks Stopping processing here. Please

Bug#876342: [Pkg-utopia-maintainers] Bug#876342: avahi-daemon: upgrade failed: failed to configure

On 2017-09-21 18:47:40 +0200, Michael Biebl wrote: > Can you provide steps how to reproduce the issue? I've upgraded avahi on > several systems and did not run into this particular problem. I don't know whether this is reproducible, but this was just an upgrade with aptitude. Here's the Aptitude

Bug#871831: mono-tools: Depends on libwebkit1.1-cil which is deprecated

Just to be clear, monodoc won't run if it's not built against webkitgtk (or one of a few other dependencies that aren't in Debian any more) so we should drop the monodoc package too. Thanks, Jeremy Bicha

Processed: forwarded GCC issue

Processing commands for cont...@bugs.debian.org: > forwarded 876353 https://gcc.gnu.org/PR82284 Bug #876353 [gccgo-7] gccgo-7: unhandled signal 11 at s390x/ppc64 Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR82284'. > tags 876353 + upstream Bug #876353 [gccgo-7] gccgo-7: unhandled signal

Processed: [bts-link] source package fwupd

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package fwupd > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to

Bug#818616: marked as done (luajit: laujit segfaults on arm64)

Your message dated Thu, 21 Sep 2017 18:50:26 +0200 with message-id <1c5598ec-4693-ad52-0a33-cfe9034ec...@debian.org> and subject line Re: luajit: laujit segfaults on arm64 has caused the Debian Bug report #818616, regarding luajit: laujit segfaults on arm64 to be marked as done. This means that

Processed: your mail

Processing commands for cont...@bugs.debian.org: > notfound 873320 ettercap/1:0.8.2-6 Bug #873320 {Done: Gianfranco Costamagna } [src:ettercap] ettercap FTBFS with luajit 2.1 Ignoring request to alter found versions of bug #873320 to the same values previously set >

Processed: Re: [Pkg-utopia-maintainers] Bug#876342: avahi-daemon: upgrade failed: failed to configure

Processing control commands: > tags -1 moreinfo unreproducible Bug #876342 [avahi-daemon] avahi-daemon: upgrade failed: failed to configure Added tag(s) moreinfo and unreproducible. -- 876342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876342 Debian Bug Tracking System Contact

Bug#876342: [Pkg-utopia-maintainers] Bug#876342: avahi-daemon: upgrade failed: failed to configure

Control: tags -1 moreinfo unreproducible Am 21.09.2017 um 10:28 schrieb Vincent Lefevre: > Package: avahi-daemon > Version: 0.7-3 > Severity: grave > Justification: renders package unusable > > The upgrade of avahi-daemon failed: > > Setting up avahi-daemon (0.7-3) ... > Installing new version

Bug#867655: marked as done (ruby-gemnasium-gitlab-service: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: @connection.request(request))

Your message dated Thu, 21 Sep 2017 16:31:11 + with message-id and subject line Bug#867655: fixed in ruby-gemnasium-gitlab-service 0.2.6-2 has caused the Debian Bug report #867655, regarding ruby-gemnasium-gitlab-service: FTBFS: ERROR: Test "ruby2.3"

Bug#844976: marked as done (clisp: FTBFS: Cannot map memory to address 0x8020875b2000 .)

Your message dated Thu, 21 Sep 2017 18:25:01 +0200 with message-id <1506011101.1818.34.ca...@debian.org> and subject line Re: clisp: FTBFS: Cannot map memory to address 0x8020875b2000 . has caused the Debian Bug report #844976, regarding clisp: FTBFS: Cannot map memory to address 0x8020875b2000 .

Processed: Bug#867655 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 867655 pending Bug #867655 [src:ruby-gemnasium-gitlab-service] ruby-gemnasium-gitlab-service: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: @connection.request(request) Added tag(s) pending. > thanks Stopping processing here. Please

Bug#867655: marked as pending

tag 867655 pending thanks Hello, Bug #867655 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-gemnasium-gitlab-service.git/commit/?id=44506f9 --- commit

Bug#876274: wordpress: 9 security bugs in wordpress 4.8.1 and earlier

On Thu, Sep 21, 2017 at 09:54:49AM +0200, Ángel wrote: > Salvatore wrote: > > have you identified already the issue -> fixing commit mappings? > > For version 4.8.1 [buster, sid], upstream fixed them on 4.8.2 > https://codex.wordpress.org/Version_4.8.2 And for jessie backports I'll update as

Bug#874764: marked as done (389-ds-base-dev: broken symlinks: /usr/lib//dirsrv/lib{sds, nunc-stans, ns-dshttpd}.so)

Your message dated Thu, 21 Sep 2017 15:20:19 + with message-id and subject line Bug#874764: fixed in 389-ds-base 1.3.6.7-5 has caused the Debian Bug report #874764, regarding 389-ds-base-dev: broken symlinks: /usr/lib//dirsrv/lib{sds, nunc-stans,

Bug#874524: Invalid symlink: /usr/bin/r2-indent -> /build/radare2-1.6.0+dfsg/sys/indent.sh

> Severity: serious > > This symlink is obviously wrong: uh ? Could you please mention the section of the standard that is not respected (must/should) ? Ref: https://www.debian.org/Bugs/Developer#severities Thx

Bug#818616: luajit: laujit segfaults on arm64

I think this bug was fixed in 2.1.0~beta3. Can it be closed please? Any objections? # tail -n 1 /proc/self/maps eb71-eb731000 rw-p 00:00 0 [stack] # dpkg -i libluajit-5.1-2_2.1.0~beta2+dfsg-1_arm64.deb

Processed: Re: busybox-static: execs applets when chrooting

Processing control commands: > tags -1 confirmed Bug #774227 [busybox-static] busybox-static: execs applets when chrooting Added tag(s) confirmed. > severity -1 normal Bug #774227 [busybox-static] busybox-static: execs applets when chrooting Severity set to 'normal' from 'serious' -- 774227:

Bug#774227: busybox-static: execs applets when chrooting

Control: tags -1 confirmed Control: severity -1 normal On 03/07/17 11:49, Alexander Kurtz wrote: > As you can see, chroot will run the applet rather than the binary > unless the full path is given. While this *may* be useful in some > situations, it can also lead to *really* subtle failures in

Bug#876277: marked as done (opendnssec: FTBFS with debhelper 10.9)

Your message dated Thu, 21 Sep 2017 12:22:28 + with message-id and subject line Bug#876277: fixed in opendnssec 1:2.1.3-0.2 has caused the Debian Bug report #876277, regarding opendnssec: FTBFS with debhelper 10.9 to be marked as done. This means that you

Bug#875637: marked as done (iipimage-server: Wrong configuration file /etc/apache2/mods-available/iipsrv.conf)

Your message dated Thu, 21 Sep 2017 12:06:12 + with message-id and subject line Bug#875637: fixed in iipimage 1.0-2 has caused the Debian Bug report #875637, regarding iipimage-server: Wrong configuration file /etc/apache2/mods-available/iipsrv.conf to be

Bug#874693: breaks other packages

On Fri, Sep 8, 2017 at 2:06 PM, Michael Biebl wrote: > The version from experimental apparently breaks other packages like > gnome-weather: Yes, I remember now that several GNOME 3.22 packages had to be updated to work with gjs 1.48. But by this point, all those packages have

Bug#876353: gccgo-7: unhandled signal 11 at s390x/ppc64

> is this limited to big endian 64bit systems? Maybe somebody could check on > ppc64el, sparc64 and mips64el as well? AFAICT, ppc64el works fine. mips, s390x, ppc64 fail in same reason on buildd -- Best regards, Shengjing Zhu

Bug#876353: gccgo-7: unhandled signal 11 at s390x/ppc64

On 21.09.2017 11:54, Shengjing Zhu wrote: >> please could you recheck with gcc-snapshot? > > Thanks, > gcc-snapshot works > > # /usr/lib/gcc-snapshot/bin/go version > go version go1.9 gccgo (Debian 20170917-1) 8.0.0 20170917 > (experimental) [trunk revision 252892] linux/ppc64 is this limited

Bug#876353: gccgo-7: unhandled signal 11 at s390x/ppc64

> please could you recheck with gcc-snapshot? Thanks, gcc-snapshot works # /usr/lib/gcc-snapshot/bin/go version go version go1.9 gccgo (Debian 20170917-1) 8.0.0 20170917 (experimental) [trunk revision 252892] linux/ppc64 -- Best regards, Shengjing Zhu

Bug#876353: gccgo-7: unhandled signal 11 at s390x/ppc64

On 21.09.2017 11:17, Shengjing Zhu wrote: > Package: gccgo-7 > Version: 7.2.0-6 > Severity: grave > Justification: renders package unusable > > Dear maintainer, > > with gccgo-7 7.2.0-6, segmentation fault if I run `go-7 version` on > ppc64 arch. > > dmesg is > [1619215.799421] go-7[12079]:

Bug#876353: gccgo-7: unhandled signal 11 at s390x/ppc64

Since there's only 7.2.0-1 on http://snapshot.debian.org/archive/debian-ports/ I can confirm this version works on ppc64 Thanks Shengjing Zhu

Processed: Re: avahi-daemon: upgrade failed: failed to configure

Processing control commands: > severity -1 serious Bug #876342 [avahi-daemon] avahi-daemon: upgrade failed: failed to configure Severity set to 'serious' from 'grave' -- 876342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876342 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#876342: avahi-daemon: upgrade failed: failed to configure

Control: severity -1 serious The configure problem got eventually solved (I don't know how). But this should not have made the upgrade fail in the first place. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Bug#876288: marked as done (python3-fabio-dbg should depend on python3-pyqt4-dbg)

Your message dated Thu, 21 Sep 2017 09:25:53 + with message-id and subject line Bug#876288: fixed in python-fabio 0.5.0+dfsg-2 has caused the Debian Bug report #876288, regarding python3-fabio-dbg should depend on python3-pyqt4-dbg to be marked as done.

Bug#876130: marked as done (libcamp-dev: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/include/camp/args.hpp)

Your message dated Thu, 21 Sep 2017 09:20:48 + with message-id and subject line Bug#876130: fixed in camp 0.8.1-2 has caused the Debian Bug report #876130, regarding libcamp-dev: fails to upgrade from 'stable' to 'sid' - trying to overwrite

Bug#876353: gccgo-7: unhandled signal 11 at s390x/ppc64

Package: gccgo-7 Version: 7.2.0-6 Severity: grave Justification: renders package unusable Dear maintainer, with gccgo-7 7.2.0-6, segmentation fault if I run `go-7 version` on ppc64 arch. dmesg is [1619215.799421] go-7[12079]: unhandled signal 11 at 1010a540 nip 7fff95bfadac lr

Bug#876342: avahi-daemon: upgrade failed: failed to configure

On 2017-09-21 10:28:25 +0200, Vincent Lefevre wrote: > Setting up avahi-daemon (0.7-3) ... > Installing new version of config file /etc/avahi/avahi-daemon.conf ... > Job for avahi-daemon.service failed because the control process exited with > error code. > See "systemctl status

Bug#876342: avahi-daemon: upgrade failed: failed to configure

Package: avahi-daemon Version: 0.7-3 Severity: grave Justification: renders package unusable The upgrade of avahi-daemon failed: Setting up avahi-daemon (0.7-3) ... Installing new version of config file /etc/avahi/avahi-daemon.conf ... Job for avahi-daemon.service failed because the control

Bug#876274: wordpress: 9 security bugs in wordpress 4.8.1 and earlier

Salvatore wrote: > have you identified already the issue -> fixing commit mappings? For version 4.8.1 [buster, sid], upstream fixed them on 4.8.2 https://codex.wordpress.org/Version_4.8.2 For version 4.7.5 [stretch], upstream fixed them on 4.7.6 https://codex.wordpress.org/Version_4.7.6 For

Processed: retitle 874693 to ES6 syntax in 1.48+ breaks packages that redeclare variables with 'let'

Processing commands for cont...@bugs.debian.org: > retitle 874693 ES6 syntax in 1.48+ breaks packages that redeclare variables > with 'let' Bug #874693 [gjs] breaks other packages Changed Bug title to 'ES6 syntax in 1.48+ breaks packages that redeclare variables with 'let'' from 'breaks other

Processed: bug 870834 is forwarded to https://github.com/pavouk/lgi/issues/167

Processing commands for cont...@bugs.debian.org: > forwarded 870834 https://github.com/pavouk/lgi/issues/167 Bug #870834 [src:lua-lgi] lua-lgi FTBFS: test failures Set Bug forwarded-to-address to 'https://github.com/pavouk/lgi/issues/167'. > thanks Stopping processing here. Please contact me if

Bug#868719: marked as done (golang-github-couchbase-moss FTBFS: FAIL: TestStoreCollHistograms)

Your message dated Thu, 21 Sep 2017 06:19:24 + with message-id and subject line Bug#868719: fixed in golang-github-couchbase-moss 0.0~git20170828.0.61afce4-1 has caused the Debian Bug report #868719, regarding golang-github-couchbase-moss FTBFS: FAIL: