Bug#929781: rkt: CVE-2019-10144 CVE-2019-10145 CVE-2019-10147

2019-05-30 Thread Salvatore Bonaccorso
Source: rkt Version: 1.30.0+dfsg-7 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://github.com/rkt/rkt/issues/3998 Hi, The following vulnerabilities were published for rkt. CVE-2019-10144[0]: rkt: processes run with `rkt enter` are given all capabiliti

Processed: severity of 929780 is important

2019-05-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 929780 important Bug #929780 [src:linux] linux-image-4.19.0-5-amd64: xps13 crashes on suspend/resume with latest kernel Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assista

Bug#929780: linux-image-4.19.0-5-amd64: xps13 crashes on suspend/resume with latest kernel

2019-05-30 Thread Philip Walls
Package: src:linux Version: 4.19.37-3 Severity: critical Justification: breaks the whole system The failure is reproducible 100% of the time. All that is required is to close the lid on my laptop, wait a moment, and then open the lid. When the lid is opened, the kernel immediately boots back to t

Processed: Re: Bug#929709: libgdbm6: file exists in libgdbm-dev as well as gdbm

2019-05-30 Thread Debian Bug Tracking System
Processing control commands: > severity -1 minor Bug #929709 [libgdbm6] libgdbm6: file exists in libgdbm-dev as well as gdbm Severity set to 'minor' from 'serious' -- 929709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929709 Debian Bug Tracking System Contact ow...@bugs.debian.org with pr

Bug#929709: libgdbm6: file exists in libgdbm-dev as well as gdbm

2019-05-30 Thread Dmitry Bogatov
control: severity -1 minor [2019-05-29 13:31] lkcl > Package: libgdbm6 > Version: 1.18.1-4 > Severity: serious > Justification: 2 > > Unpacking libgdbm-dev:amd64 (1.18.1-4) ... > dpkg: error processing archive > /var/cache/apt/archives/libgdbm-dev_1.18.1-4_amd64.deb (--unpack): > trying to ov

Bug#929719: marked as done (gucharmap: FTBFS: unsatisfiable build-dependency: unicode-data (< 11.1) but 12.1.0~pre1-2 is to be installed)

2019-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 31 May 2019 07:29:04 +0900 with message-id <20190531072904.bdf5c7ff8bf3f8646e45c...@iijmio-mail.jp> and subject line has caused the Debian Bug report #929719, regarding gucharmap: FTBFS: unsatisfiable build-dependency: unicode-data (< 11.1) but 12.1.0~pre1-2 is to be insta

Processed: backports has too new a version of netdata

2019-05-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # we are not going to delay the release for this, there is nothing we > # can do (except accepting a package that doesn't qualify) > tags 929151 buster-ignore Bug #929151 {Done: Andreas Beckmann } [netdata-core] netdata-core: version in stretch-b

Bug#929588: usat: source tarballs are missing the source of the configure script

2019-05-30 Thread Carsten Schoenert
Hi, previous and the most recent release of the usat tarballs is missing the source for the configure script. http://usat.sourceforge.net/code/lsat-0.9.8.2.zip For Debian this makes the package [1] non-free due the regulation of the Debian Free Software Guidelines [2]. It also makes it impossibl

Processed: Re: Bug#929588: lsat missing source for configure

2019-05-30 Thread Debian Bug Tracking System
Processing control commands: > tags -1 upstream Bug #929588 [src:lsat] lsat missing source for configure Added tag(s) upstream. -- 929588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#929588: lsat missing source for configure

2019-05-30 Thread Carsten Schoenert
Control: tags -1 upstream On Sun, May 26, 2019 at 08:16:19PM +0200, Helmut Grohne wrote: > 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. >

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

2019-05-30 Thread tony mancill
On Mon, May 27, 2019 at 10:07:38PM -0700, tony mancill wrote: > On Sun, May 26, 2019 at 08:58:29PM +0200, Moritz Mühlenhoff wrote: > > Looks fine, but can you please also include the test case upstream added? > > Given that it's quite complex to reconstruct the specific affected ZK setup, > > we sh

Bug#927978: marked as done (gst-plugins-base1.0: CVE-2019-9928: Buffer overflow in RTSP parsing)

2019-05-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 May 2019 11:19:26 + with message-id and subject line Bug#927978: fixed in gst-plugins-base1.0 1.14.4-2 has caused the Debian Bug report #927978, regarding gst-plugins-base1.0: CVE-2019-9928: Buffer overflow in RTSP parsing to be marked as done. This means that you c

Bug#929017: marked as done (mutt: undefined behavior on huge integer in a RFC 2231 header)

2019-05-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 May 2019 11:20:13 + with message-id and subject line Bug#929017: fixed in mutt 1.10.1-2.1 has caused the Debian Bug report #929017, regarding mutt: undefined behavior on huge integer in a RFC 2231 header to be marked as done. This means that you claim that the probl

Processed: tagging 928429

2019-05-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 928429 + patch Bug #928429 [dpkg] dpkg: trigger cycle postgresql-common -> sgml-base while upgrading from stretch to buster Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 928429: https:/

Bug#928175: Could be related?

2019-05-30 Thread Jochen Pawletta
Hello I just upgraded from Jessie to Stretch 2 days ago and have the following problem which could be related: May 30 06:31:46 anton procmail[29067]: Renamed bogus "/var/mail/andrea" into "/var/mail/BOGUS.andrea.Lhj1" May 30 07:24:42 anton procmail[5147]: Renamed bogus "/var/mail/markes" into "

Bug#926180: scilab: FTBFS on all

2019-05-30 Thread Rebecca N. Palmer
Some further searching suggests that Java triggers and catches SIGSEGVs as part of normal operation, and hence is expected to not work under gdb without "handle SIGSEGV nostop pass". With this, both 6.0.1 and 6.0.2 don't crash in gdb, i.e. the crash in gdb probably isn't this bug. This sugges

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

2019-05-30 Thread Rob Browning
Rob Browning writes: > Yep -- I'm not sure yet, but I may lean toward providing: > > bin/guile -> ./guile-2.2 # or whatever the selected alternative is > bin/guild -> ./guild-2.2 # or whatever the selected alternative is OK, I think I'll have an upload this weekend using the built in ./con