Bug#903635: docker.io: use of iptables-legacy is incompatible with nftables-based iptables

On 5/24/19 4:33 PM, Jonathan Dowland wrote: > Hi Arnaud - sorry I missed your messages until now. No problem :) > > On Fri, May 10, 2019 at 09:03:41AM +0700, Arnaud Rebillout wrote: >> As I mentioned above, there's a discussion with a work in progress to >> fix that upstream:

Bug#929567: libgtk-3-0:amd64: Emacs constantly crashes on startup with "X protocol error: BadLength..."

Testcase: $ printf '\u26D4\n' > test $ emacs -Q test It is U+26D4 NO ENTRY that triggers the crash. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#926182: Patch: Use alternatives system for guile-2.2-dev binaries

Vagrant Cascadian writes: > It seems like simply providing the binaries with the versioned links > would be sufficient, since guile-2.2-dev conflicts/provides > libguile-dev, guile-2.0-dev and guile-2.2-dev can't be installed at the > same time. > > I guess it's possible the alternative for

Bug#868483: marked as done (cross-config: cross-config files missing for multiple architectures)

Your message dated Sun, 26 May 2019 21:48:31 + with message-id and subject line Bug#868483: fixed in dpkg-cross 2.6.15-3 has caused the Debian Bug report #868483, regarding cross-config: cross-config files missing for multiple architectures to be marked as done. This means that you claim

Processed: user debian...@lists.debian.org, unarchiving 705109, usertagging 705109

Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > unarchive 705109 Bug #705109 {Done: Michael Gilbert } [slapd] Upgrade from 2.4.11-1+lenny2.1 to slapd 2.4.23-7.3 fails Unarchived Bug 705109 >

Processed: Re: Bug#925173: ltsp: codename detection code not useful for stable

Processing control commands: > severity 925173 serious Bug #925173 [src:ltsp] ltsp: codename detection code not useful for stable Severity set to 'serious' from 'important' -- 925173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925173 Debian Bug Tracking System Contact

Bug#929297: minissdpd: CVE-2019-12106

On Sat, May 25, 2019 at 09:08:32AM +0100, Chris Lamb wrote: > Hey, > > > > The following vulnerability was published for minissdpd. > > > > > > CVE-2019-12106[0]: > > > | The updateDevice function in minissdpd.c in MiniUPnP MiniSSDPd 1.4 and > > > | 1.5 allows a remote attacker to crash the

Bug#929560: marked as done (libhmsbeagle1v5: broken symlink: /usr/lib/i686-linux-gnu/jni/libhmsbeagle-jni.so -> ../libhmsbeagle-jni.so)

Your message dated Sun, 26 May 2019 20:48:33 + with message-id and subject line Bug#929560: fixed in libhmsbeagle 3.1.2+dfsg-6 has caused the Debian Bug report #929560, regarding libhmsbeagle1v5: broken symlink: /usr/lib/i686-linux-gnu/jni/libhmsbeagle-jni.so -> ../libhmsbeagle-jni.so to be

Processed: affects 929600

Processing commands for cont...@bugs.debian.org: > affects 929600 release.debian.org Bug #929600 [slurm-llnl] slurm-llnl: FTBFS on 32-bit architectures Added indication that 929600 affects release.debian.org > thanks Stopping processing here. Please contact me if you need assistance. -- 929600:

Processed: slurm-llnl: FTBFS on 32-bit architectures

Processing control commands: > affects -1 + slurm-wlm-torque Bug #929600 [slurm-llnl] slurm-llnl: FTBFS on 32-bit architectures Added indication that 929600 affects slurm-wlm-torque -- 929600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929600 Debian Bug Tracking System Contact

Bug#929600: slurm-llnl: FTBFS on 32-bit architectures

Package: slurm-llnl Version: 16.05.9-1+deb9u3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + slurm-wlm-torque Hi, the stretch update of slurm-llnl FTBFS on the

Bug#929597: CVE-2019-12211 CVE-2019-12212 CVE-2019-12213 CVE-2019-12214

Hi Moritz, thanks for the reporting. As far as I see, there is still no available fix from upstream. Cheers Anton Am So., 26. Mai 2019 um 21:27 Uhr schrieb Moritz Muehlenhoff : > > Source: freeimage > Severity: grave > Tags: security > > Please see >

Bug#929597: CVE-2019-12211 CVE-2019-12212 CVE-2019-12213 CVE-2019-12214

Source: freeimage Severity: grave Tags: security Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12211 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12212 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12213

Bug#927674: CVE-2019-3902

On Sun, Apr 21, 2019 at 12:32:13AM +0200, Moritz Muehlenhoff wrote: > Source: mercurial > Version: 4.8.2-1 > Severity: grave > Tags: security > > See https://www.mercurial-scm.org/wiki/WhatsNew from 4.9: > > This was assigned CVE-2019-3902: > It was possible to use symlinks and subrepositories

Bug#929283: zookeeper: CVE-2019-0201: information disclosure vulnerability

On Fri, May 24, 2019 at 09:19:00AM +0100, Chris Lamb wrote: > tags 929283 + patch > thanks > > Hi Moritz, > > > > > zookeeper: CVE-2019-0201: information disclosure vulnerability > > > > > > Happy to prepare an update for stretch; I plan to do one for jessie > > > LTS (which, helpfully, has the

Processed: Bug#929560 marked as pending in libhmsbeagle

Processing control commands: > tag -1 pending Bug #929560 [libhmsbeagle1v5] libhmsbeagle1v5: broken symlink: /usr/lib/i686-linux-gnu/jni/libhmsbeagle-jni.so -> ../libhmsbeagle-jni.so Added tag(s) pending. -- 929560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929560 Debian Bug Tracking

Bug#929560: marked as pending in libhmsbeagle

Control: tag -1 pending Hello, Bug #929560 in libhmsbeagle reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#929588: lsat missing source for configure

Source: lsat Version: 0.9.7.1-2.2 Severity: serious Justification: DFSG #2 The lsat source package is missing the source code for the file ./configure. That file identifies itself as being generated using autoconf. The source tarball does not contain any corresponding source. This is a DFSG #2

Bug#929584: Not suitable for buster

Source: golang-github-rackspace-gophercloud Version: 1.0.0+git20160603.920.934dbf8-1 Severity: serious Please don't ship this package in buster. There's no {build-,}rdepends in buster, and it's suppressed by golang-github-gophercloud-gophercloud. -- Shengjing Zhu signature.asc Description:

Bug#929581: zfs-dkms: fails to build module for 4.19.0-5-686-pae

Package: zfs-dkms Version: 0.8.0~rc4-1 Severity: serious Tags: ftbfs Justification: fails to build from source User: debian...@lists.debian.org Usertags: piuparts Hi, zfs-dkms fails to build a module for the i386 kernel from sid: Setting up zfs-dkms (0.8.0~rc4-1) ... Loading new

Processed: bug 927255 only applies to port architectures

Processing commands for cont...@bugs.debian.org: > tags 927255 buster-ignore Bug #927255 [powerpc-utils] powerpc-utils is uninstallable Added tag(s) buster-ignore. > thanks Stopping processing here. Please contact me if you need assistance. -- 927255:

Processed: Re: coturn: overwrites database file /var/lib/turn/turndb on upgrade or reinstall

Processing commands for cont...@bugs.debian.org: > tags 929269 + pending patch Bug #929269 [coturn] coturn: overwrites database file /var/lib/turn/turndb on upgrade or reinstall Added tag(s) pending and patch. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#929269: coturn: overwrites database file /var/lib/turn/turndb on upgrade or reinstall

tags 929269 + pending patch thanks I've uploaded coturn 4.5.1.1-1.1 to DELAYED/5: coturn (4.5.1.1-1.1) unstable; urgency=medium * Non-maintainer upload. * Don't ship the (empty) /var/lib/turn/turndb SQLite database and generate it on-demand in the postinst instead, avoiding

Bug#929575: simpleid: Not compatible with PHP 7

Source: simpleid Version: 0.8.1-15 Severity: serious Justification: Does not work with PHP 7 in buster Dear Maintainer, According to the upstrem bug tracker, simpleid is not compatible with PHP7, which would mean that it does not work in buster. Upstream also seems to indicate that the project

Bug#929567: libgtk-3-0:amd64: Emacs constantly crashes on startup with "X protocol error: BadLength..."

Control: forwarded -1 https://gitlab.gnome.org/GNOME/gtk/issues/221 (This is the new upstream bug URL.) -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP,

Processed: Re: libgtk-3-0:amd64: Emacs constantly crashes on startup with "X protocol error: BadLength..."

Processing control commands: > forwarded -1 https://gitlab.gnome.org/GNOME/gtk/issues/221 Bug #929567 [libgtk-3-0] libgtk-3-0:amd64: Emacs constantly crashes on startup with "X protocol error: BadLength..." Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/gtk/issues/221'. --

Bug#868483: cross-config: cross-config files missing for multiple architectures

On Sat, 25 May 2019 07:21:19 +0200 Helmut Grohne wrote: > Control: severity -1 serious > > On Sat, May 25, 2019 at 02:13:39AM +0100, Wookey wrote: > > > I think this should be fixed asap, ideally in buster. Do you > > > agree with bumping this bug to rcness? > > > > Yes > > Bumped. > > > > Do

Processed: limit source to dpkg-cross, tagging 868483

Processing commands for cont...@bugs.debian.org: > limit source dpkg-cross Limiting to bugs with field 'source' containing at least one of 'dpkg-cross' Limit currently set to 'source':'dpkg-cross' > tags 868483 + pending Bug #868483 [src:dpkg-cross] cross-config: cross-config files missing for

Bug#922346: Fix for this issue still not available in testing

Hello, I saw that Mesa 18.3.6-2 was accepted into unstable on 2019-05-11. That version still hasn't migrated to testing because of the freeze. Could you please contact the release team to get this release in testing ASAP as I (and probably other users) am still experiencing this issue and it is

Bug#929567: libgtk-3-0:amd64: Emacs constantly crashes on startup with "X protocol error: BadLength..."

On 2019-05-26 11:05:01 +0200, Vincent Lefevre wrote: > Package: libgtk-3-0 > Version: 3.24.5-1 > Severity: grave > Tags: upstream > Justification: renders package unusable > > When starting Emacs on a large file, I always get the following error. > This makes Emacs impossible to use. [...] I've

Processed: found 872238 in 3.0.8-5, found 857768 in libllvm-ocaml-dev/1:7.0-47.1, found 880361 in 3.17-7 ...

Processing commands for cont...@bugs.debian.org: > found 872238 3.0.8-5 Bug #872238 [cyrus-murder] cyrus-murder: broken symlink: /usr/lib/cyrus/bin/mupdatetest -> imtest Marked as found in versions cyrus-imapd/3.0.8-5. > found 857768 libllvm-ocaml-dev/1:7.0-47.1 Bug #857768 [libllvm-ocaml-dev]

Bug#929567: libgtk-3-0:amd64: Emacs constantly crashes on startup with "X protocol error: BadLength..."

Package: libgtk-3-0 Version: 3.24.5-1 Severity: grave Tags: upstream Justification: renders package unusable When starting Emacs on a large file, I always get the following error. This makes Emacs impossible to use. X protocol error: BadLength (poly request too large or internal Xlib length

Bug#929561: libnb-ide14-java: broken symlink: /usr/share/netbeans/ide14/modules/ext/gson-2.7.jar -> ../../../../java/gson.jar

Package: libnb-ide14-java Version: 10.0-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 1m9.4s ERROR: FAIL: Broken symlinks:

Bug#929560: libhmsbeagle1v5: broken symlink: /usr/lib/i686-linux-gnu/jni/libhmsbeagle-jni.so -> ../libhmsbeagle-jni.so

Package: libhmsbeagle1v5 Version: 3.1.2+dfsg-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m26.4s ERROR: FAIL: Broken