Bug#880047: closed by Peter Palfrader (Re: Bug#880047: postgrey doesn't start because it can't write its pid)

On Wed, May 15, 2019 at 08:12:07AM +, Debian Bug Tracking System wrote: > It seems to me that the default init script that ships with Debian 9 > does not use the directory /var/run/postgrey. postgrey/1.36-3+deb9u2 has worked just fine for me on Debian 9. I didn't experience any problems relate

Bug#908057: closing 908057

close 908057 18.06.0+dfsg1-1 thanks

Processed: closing 908057

Processing commands for cont...@bugs.debian.org: > close 908057 18.06.0+dfsg1-1 Bug #908057 [docker.io] docker.io: CVE-2018-10892 Ignoring request to alter fixed versions of bug #908057 to the same values previously set Bug #908057 [docker.io] docker.io: CVE-2018-10892 Marked Bug as done > thanks

Bug#877106: pinta: Pinta 1.6-2 crashes on image scaling and other image manipulation.

I am not able to reproduce this issue. Resizing images and using the paintbrush tool works without crashes in my testing. Using Pinta 1.6-2 from stretch, -- System Information: Debian Release: 10.0   APT prefers testing   APT policy: (500, 'testing'), (1, 'unstable') Architecture: amd64 (x86_64

Bug#926825: marked as done (faudio: FTBFS (Missing build-dependency on cmake))

Your message dated Sun, 9 Jun 2019 00:36:20 -0400 with message-id and subject line Re: Bug#926825: faudio: FTBFS (Missing build-dependency on cmake) has caused the Debian Bug report #926825, regarding faudio: FTBFS (Missing build-dependency on cmake) to be marked as done. This means that you cl

Bug#928282: filezilla: CVE-2019-5429

On Fri, 7 Jun 2019 22:20:45 +0900 Kentaro Hayashi wrote: > Hi, > > I'm not a user of filezilla, but I've picked it up fixing RC bug as a > challenge. > I've attached debdiff to fix CVE-2019-5429 using tracker information as a > hint. > > I hope it will help to close this bug. I've added +pa

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tags 928282 + patch Bug #928282 [src:filezilla] filezilla: CVE-2019-5429 Added tag(s) patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 928282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=92828

Bug#926578: marked as done (faudio: Incomplete debian/copyright?)

Your message dated Sun, 09 Jun 2019 03:48:25 + with message-id and subject line Bug#926578: fixed in faudio 19.06.07-1 has caused the Debian Bug report #926578, regarding faudio: Incomplete debian/copyright? to be marked as done. This means that you claim that the problem has been dealt with.

Bug#927451: marked as done (libfaudio0: library has SONAME libFAudio.so instead of libFAudio.so.0)

Your message dated Sun, 09 Jun 2019 03:48:25 + with message-id and subject line Bug#927451: fixed in faudio 19.06.07-1 has caused the Debian Bug report #927451, regarding libfaudio0: library has SONAME libFAudio.so instead of libFAudio.so.0 to be marked as done. This means that you claim that

Bug#929662: docker.io: CVE-2018-15664 - upstream backport of patch for 18.09

Hello, Is any help needed on this? Upstream has a backport of the patch for the 18.09 series (same as Unstable): https://github.com/docker/engine/pull/253 Hopefully it won't be too much work to incorporate it. thanks and regards Afif -- Afif Elghraoui | عفيف الغراوي https://afif.ghraoui.nam

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

Hello, On Fri, 24 May 2019 10:33:34 +0100 Jonathan Dowland wrote: > Hi Arnaud - sorry I missed your messages until now. > > 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: https://git

Bug#922214: libpng12-0: libpng12.so.0 can not be installed, file or directory not found

Hi, > Package: libpng12-0 > Version: 1.2.50-2+deb8u3 > Severity: grave > Tags: a11y d-i > Justification: renders package unusable > > dpkg says while trying to install: > file /usr/lib/x86_64-gnu-linux/libpng12-0.so.0 can not be installed, file or > directory not found > and the installation is a

Bug#930232: vlc: No video output in any video

Control: tags -1 moreinfo Control: severity -1 important Control: found -1 3.0.6-1 On 2019-06-08 23:20:15, Ralf Jung wrote: > Package: vlc > Version: 3.0.7-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > No matter which video file I try to open with VLC, VL

Processed: Re: Bug#930232: vlc: No video output in any video

Processing control commands: > tags -1 moreinfo Bug #930232 [vlc] vlc: No video output in any video Added tag(s) moreinfo. > severity -1 important Bug #930232 [vlc] vlc: No video output in any video Severity set to 'important' from 'grave' > found -1 3.0.6-1 Bug #930232 [vlc] vlc: No video output

Bug#929617: d3-format: latest-debian-changelog-entry-reuses-existing-version

I have uploaded an NMU with the attached patch to DELAYED/3. Please also see the change in https://salsa.debian.org/js-team/d3-format/merge_requests/2 Cheers, Balint -- Balint Reczey Ubuntu & Debian Developer From bd8e713e8365dcff22a6b883a4512fc12e1d51b2 Mon Sep 17 00:00:00 2001 From: Balint Rec

Bug#930232: vlc: No video output in any video

Package: vlc Version: 3.0.7-1 Severity: grave Justification: renders package unusable Dear Maintainer, No matter which video file I try to open with VLC, VLC fails to display any image. All I get is a flickering VLC icon. I will attach a "-vv" log for one of the many files that I tried. The sa

Bug#924787: marked as done (yubikey-personalization: Devices unuseable after upgrade (udev rules missing))

Your message dated Sat, 08 Jun 2019 21:00:11 + with message-id and subject line Bug#924787: fixed in yubikey-personalization 1.19.3-3 has caused the Debian Bug report #924787, regarding yubikey-personalization: Devices unuseable after upgrade (udev rules missing) to be marked as done. This m

Processed: Re: [pre-approval] unblock: icu/63.2-1

Processing control commands: > tags -1 moreinfo Bug #928111 [release.debian.org] [pre-approval] unblock: icu/63.2-1 Added tag(s) moreinfo. > block -1 by 928097 Bug #928111 [release.debian.org] [pre-approval] unblock: icu/63.2-1 928111 was not blocked by any bugs. 928111 was not blocking any bugs.

Bug#930056: marked as done (synphot-data: creates world writable files: /usr/share/synphot/grp/hst/cdbs/comp/acs/acs_*_syn.fits)

Your message dated Sat, 08 Jun 2019 19:18:30 + with message-id and subject line Bug#930056: fixed in pysynphot 0.9.12+dfsg-3 has caused the Debian Bug report #930056, regarding synphot-data: creates world writable files: /usr/share/synphot/grp/hst/cdbs/comp/acs/acs_*_syn.fits to be marked as

Bug#930227: mender-client fails to build from source on all architectures

Source: mender-client Version: 1.7.0-4 Severity: serious Justification: FTBFS Tags: security ftbfs While rebuilding all packages in buster for CVE-2018-17846 / CVE-2018-17847 / CVE-2018-17848 in golang-golang-x-net-dev, mender-client fails to build from source on all architectures where it was tri

Bug#930218: marked as done (FTBFS on mips*)

Your message dated Sat, 08 Jun 2019 18:18:43 + with message-id and subject line Bug#930218: fixed in cargo 0.35.0-2 has caused the Debian Bug report #930218, regarding FTBFS on mips* to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#930218: [Pkg-rust-maintainers] Bug#930218: FTBFS on mips*

Mike Hommey: > On Sat, Jun 08, 2019 at 10:27:15PM +0900, Mike Hommey wrote: >> Package: cargo >> Version: 0.35.0-1 >> Severity: serious >> >> https://buildd.debian.org/status/fetch.php?pkg=cargo&arch=mips&ver=0.35.0-1&stamp=1559294265&raw=0 >> https://buildd.debian.org/status/fetch.php?pkg=cargo&ar

Bug#903124: marked as done (libevent-rpc-perl: 1.08-2 FTBFS: expired SSL certificate)

Your message dated Sat, 08 Jun 2019 17:47:08 + with message-id and subject line Bug#903124: fixed in libevent-rpc-perl 1.08-2+deb9u1 has caused the Debian Bug report #903124, regarding libevent-rpc-perl: 1.08-2 FTBFS: expired SSL certificate to be marked as done. This means that you claim tha

Bug#924397: marked as done (corekeeper: insecure use of world-writable /var/crash)

Your message dated Sat, 08 Jun 2019 17:32:08 + with message-id and subject line Bug#924397: fixed in corekeeper 1.7~deb9u1 has caused the Debian Bug report #924397, regarding corekeeper: insecure use of world-writable /var/crash to be marked as done. This means that you claim that the problem

Bug#918736: marked as done (libthrift-java: CVE-2018-1320)

Your message dated Sat, 08 Jun 2019 17:32:25 + with message-id and subject line Bug#918736: fixed in libthrift-java 0.9.1-2.1~deb9u1 has caused the Debian Bug report #918736, regarding libthrift-java: CVE-2018-1320 to be marked as done. This means that you claim that the problem has been deal

Bug#929297: marked as done (minissdpd: CVE-2019-12106)

Your message dated Sat, 08 Jun 2019 17:32:26 + with message-id and subject line Bug#929297: fixed in minissdpd 1.2.20130907-4.1+deb9u1 has caused the Debian Bug report #929297, regarding minissdpd: CVE-2019-12106 to be marked as done. This means that you claim that the problem has been dealt

Processed: control

Processing commands for cont...@bugs.debian.org: > reassign 929567 emacs Bug #929567 [libgtk-3-0] libgtk-3-0:amd64: Emacs constantly crashes on startup with "X protocol error: BadLength..." Bug reassigned from package 'libgtk-3-0' to 'emacs'. No longer marked as found in versions gtk+3.0/3.24.5-1

Bug#929907: libgnutls30: Connections to older GnUTLS servers break

On 2019-06-04 Andreas Metzler wrote: > On 2019-06-03 Dominik George wrote: [...] > >pwgen 16383 | gnutls-cli --no-ca-verification --port 5556 localhost > > From a size of 16383 bytes onwards, I get: > > |<1>| Received packet with illegal length: 16385 > > |<1>| Discarded message[1] due to i

Bug#926392: marked as done (libregexp-pattern-license-perl: Exponential runtime regexes on some input)

Your message dated Sat, 08 Jun 2019 17:04:19 + with message-id and subject line Bug#926392: fixed in libregexp-pattern-license-perl 3.1.93-1 has caused the Debian Bug report #926392, regarding libregexp-pattern-license-perl: Exponential runtime regexes on some input to be marked as done. Thi

Bug#908678: Update on the security-tracker git discussion

Hi, On Thu, Jun 06, 2019 at 06:11:53PM +0200, Salvatore Bonaccorso wrote: > Hi Daniel, > > On Thu, Jun 06, 2019 at 08:35:47AM +0200, Daniel Lange wrote: > > Am 06.06.19 um 07:31 schrieb Salvatore Bonaccorso: > > > Could you again point me to your splitted up variant mirror? > > > > https://git.f

Processed: tagging 928959

Processing commands for cont...@bugs.debian.org: > tags 928959 + pending Bug #928959 [src:papi] papi: DFSG-unfree file in source Ignoring request to alter tags of bug #928959 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 928959: h

Bug#928959: *** GMX Spamverdacht *** Bug#928959: papi: DFSG-unfree file in source

tags +928959 pending thanks Hi, On Mon, May 20, 2019 at 10:32:51PM +0200, Xavier wrote: > Le 20/05/2019 à 22:19, Xavier a écrit : > > Hi all, > > > > papi embeds iozone in appio component. This software has been declared > > non-DFSG (https://lists.debian.org/debian-legal/2000/03/msg00024.html >

Bug#929903: m2crypto: prosposed patch

Control: tags 929903 + patch Dear maintainer, please find attached a proposed NMU to address this problem. Regards. Sebastian diff -Nru m2crypto-0.31.0/debian/changelog m2crypto-0.31.0/debian/changelog --- m2crypto-0.31.0/debian/changelog 2019-03-11 19:44:01.0 +0100 +++ m2crypto-0.31.0/d

Processed: m2crypto: prosposed patch

Processing control commands: > tags 929903 + patch Bug #929903 [m2crypto] m2crypto: testing for a fixed openssl causing test case regression Added tag(s) patch. -- 929903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929903 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

Bug#930218: FTBFS on mips*

On Sat, Jun 08, 2019 at 10:27:15PM +0900, Mike Hommey wrote: > Package: cargo > Version: 0.35.0-1 > Severity: serious > > https://buildd.debian.org/status/fetch.php?pkg=cargo&arch=mips&ver=0.35.0-1&stamp=1559294265&raw=0 > https://buildd.debian.org/status/fetch.php?pkg=cargo&arch=mips64el&ver=0.35

Processed: not RC in my opinion

Processing control commands: > severity -1 important Bug #911623 [src:btrfs-tools] /bin/mkfs.btrfs and /bin/fsck.btrfs are Policy and FHS violations Severity set to 'important' from 'serious' -- 911623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911623 Debian Bug Tracking System Contact

Bug#911623: not RC in my opinion

Control: severity -1 important > Severity: serious > Justification: Debian Policy violation > /bin/mkfs.btrfs and /bin/fsck.btrfs are Policy and FHS violations. I don't believe this is in any way RC -- for Buster nor likely any future release. There's no functional lossage, AFAIK. fsck probabl

Processed: Only happens when used with paramiko

Processing commands for cont...@bugs.debian.org: > severity 930213 normal Bug #930213 [bzr] bzr: "bzr branch" fails: NameError: global name 'self' is not defined Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 930213: https:/

Bug#930213: Only happens when used with paramiko

severity 930213 normal thanks This only happens when bzr is used with paramiko and if there are SSH agent keys. You should be able to work around this by setting BZR_SSH=openssh in your environment or uninstalling paramiko.

Bug#930218: FTBFS on mips*

Package: cargo Version: 0.35.0-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=cargo&arch=mips&ver=0.35.0-1&stamp=1559294265&raw=0 https://buildd.debian.org/status/fetch.php?pkg=cargo&arch=mips64el&ver=0.35.0-1&stamp=1559294794&raw=0 https://buildd.debian.org/status/fetch.php?pk

Bug#930212: libmupdf-dev: undefined reference when linking

Control: severity -1 important Hi Reiner, Quoting Reiner Herrmann (2019-06-08 13:33:52) > > $ gcc -I/usr/include/freetype2 -I/usr/include/libpng16 -lmupdf -ljbig2dec > > -ljpeg -lz -lm -lfreetype -lpng16 -lm -lz -lm -lz test.c > > /usr/bin/ld: /tmp/ccCPwEIx.o: in function `main': > > test.c:(.te

Processed: Re: libmupdf-dev: undefined reference when linking

Processing control commands: > severity -1 important Bug #930212 [libmupdf-dev] libmupdf-dev: undefined reference when linking Severity set to 'important' from 'grave' -- 930212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930212 Debian Bug Tracking System Contact ow...@bugs.debian.org wit

Bug#930212: libmupdf-dev: undefined reference when linking

Hi josch, > $ gcc -I/usr/include/freetype2 -I/usr/include/libpng16 -lmupdf -ljbig2dec > -ljpeg -lz -lm -lfreetype -lpng16 -lm -lz -lm -lz test.c > /usr/bin/ld: /tmp/ccCPwEIx.o: in function `main': > test.c:(.text+0x26): undefined reference to `fz_new_context_imp' > collect2: error: ld returned 1

Bug#930213: bzr: "bzr branch" fails: NameError: global name 'self' is not defined

Package: bzr Version: 2.7.0+bzr6622-15 Severity: grave Justification: renders package unusable Dear Maintainer, The command `bzr branch lp:mailman/2.1` (which https://code.launchpad.net/~mailman-coders/mailman/2.1 tells me to run to get the mailman source code) fails, with the following error: `

Bug#930212: libmupdf-dev: undefined reference when linking

Package: libmupdf-dev Version: 1.14.0+ds1-4 Severity: grave Justification: renders package unusable Hi, it does not seem to be possible to use the static library from libmupdf-dev at all. Consider the following minimal test case: #include "mupdf/fitz.h" #include "mupdf/pdf.h" #

Bug#929903: openssl: m2crypto test case regression

On 2019-06-08 10:28:38 [+0200], Matěj Cepl wrote: > Sebastian Andrzej Siewior píše v Út 04. 06. 2019 v 23:10 +0200: > > It did not if I understand the python correctly: > > >with self.assertRaises(RSA.RSAError): > > >priv.private_decrypt(ctxt, RSA.sslv23_padding) > > > > you ex

Bug#929903: openssl: m2crypto test case regression

Sebastian Andrzej Siewior píše v Út 04. 06. 2019 v 23:10 +0200: > It did not if I understand the python correctly: > >with self.assertRaises(RSA.RSAError): > >priv.private_decrypt(ctxt, RSA.sslv23_padding) > > you expect that `priv.private_decrypt()' raised an RSA.RSAError > ex

Processed: retitle 927159 to libqb: CVE-2019-12779: Insecure Temporary Files

Processing commands for cont...@bugs.debian.org: > retitle 927159 libqb: CVE-2019-12779: Insecure Temporary Files Bug #927159 {Done: Ferenc Wágner } [src:libqb] libqb: Insecure Temporary Files Changed Bug title to 'libqb: CVE-2019-12779: Insecure Temporary Files' from 'libqb: Insecure Temporary

Processed: Merging 915683 916416

Processing commands for cont...@bugs.debian.org: > unarchive 916416 Bug #916416 {Done: Nicolas Braud-Santoni } [kazam] kazam unable to start: ValueError: Invalid section name: 'DEFAULT' Unarchived Bug 916416 > forcemerge 916416 915683 Bug #916416 {Done: Nicolas Braud-Santoni } [kazam] kazam unab