Processed: reassign m2crypto bug

Processing commands for cont...@bugs.debian.org: > reassign 929903 m2crypto 0.31.0-3 Bug #929903 [openssl] openssl: m2crypto test case regression Bug reassigned from package 'openssl' to 'm2crypto'. No longer marked as found in versions openssl/1.1.1c-1. Ignoring request to alter fixed versions of

Bug#907135: [Box Backup] Debian now requires 2048bit RSA keys

On Wed, Jun 5, 2019 at 7:46 PM Chris Wilson wrote: > Hi Reinhard, > > Could you have a look at this patch > (documented > here > ) > to see if it's some

Bug#923433: marked as done (EncoderStrategy::Flush (this=0x5555557452f0) at ./src/encoderstrategy.h:156)

Your message dated Fri, 07 Jun 2019 20:49:24 + with message-id and subject line Bug#923433: fixed in dcmtk 3.6.4-2.1 has caused the Debian Bug report #923433, regarding EncoderStrategy::Flush (this=0x557452f0) at ./src/encoderstrategy.h:156 to be marked as done. This means that you claim

Bug#930168: plasma-discover hangs while looking for updates, emits many notifications when closed

Package: plasma-discover Version: 5.14.5.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, I've installed Kali Linux (rolling release) and selected the KDE/Plasma desktop. There's an icon on the taskbar that indicates there are upates available. Clicking on the icon p

Bug#930133: marked as done (Postinst tries to invoke systemctl on non-systemd systems)

Your message dated Fri, 07 Jun 2019 18:18:22 + with message-id and subject line Bug#930133: fixed in mailman-suite 0+20180916-8 has caused the Debian Bug report #930133, regarding Postinst tries to invoke systemctl on non-systemd systems to be marked as done. This means that you claim that th

Bug#930133: Postinst tries to invoke systemctl on non-systemd systems

Package: mailman3-web Version: 0+20180916-7 Severity: serious Hello, the mailman3-web postinst runs 'systemctl daemon-reload' during upgrades, regardless of whether systemd is installed on the system or not. This breaks installation of mailman3-web on systems with sysvinit. Cheers jonas

Processed: Upgrade bug severity

Processing control commands: > severity -1 serious Bug #919759 [src:gokey] gokey FTBFS on armel/mips*: FAIL github.com/cloudflare/gokey Severity set to 'serious' from 'normal' > tag -1 sid Bug #919759 [src:gokey] gokey FTBFS on armel/mips*: FAIL github.com/cloudflare/gokey Added tag(s) sid. --

Bug#903124: marked as pending in libevent-rpc-perl

Control: tag -1 pending Hello, Bug #903124 in libevent-rpc-perl 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: https://salsa.debian.org/perl-team/modules/packages/libevent-rpc-perl/com

Processed: Bug#903124 marked as pending in libevent-rpc-perl

Processing control commands: > tag -1 pending Bug #903124 [src:libevent-rpc-perl] libevent-rpc-perl: 1.08-2 FTBFS: expired SSL certificate Added tag(s) pending. -- 903124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903124 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

Bug#928282: filezilla: CVE-2019-5429

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. Regards, diff -Nru filezilla-3.39.0/debian/changelog filezilla-3.39.0/debian/changelog ---

Bug#900441: marked as done (Misses executable, possible candidate for removal?)

Your message dated Fri, 07 Jun 2019 11:48:24 + with message-id and subject line Bug#900441: fixed in bwbar 1.2.3-4 has caused the Debian Bug report #900441, regarding Misses executable, possible candidate for removal? to be marked as done. This means that you claim that the problem has been d

Bug#930016: marked as done (patroni: pg_createconfig_patroni writes empty configuration file if default dcs.yml is used)

Your message dated Fri, 07 Jun 2019 11:36:30 + with message-id and subject line Bug#930016: fixed in patroni 1.5.5-2 has caused the Debian Bug report #930016, regarding patroni: pg_createconfig_patroni writes empty configuration file if default dcs.yml is used to be marked as done. This mean

Bug#930015: marked as done (patroni: pg_createconfig_patroni writes unusable configuration for some ip-route outputs)

Your message dated Fri, 07 Jun 2019 11:36:30 + with message-id and subject line Bug#930015: fixed in patroni 1.5.5-2 has caused the Debian Bug report #930015, regarding patroni: pg_createconfig_patroni writes unusable configuration for some ip-route outputs to be marked as done. This means t

Bug#907135: marked as done (boxbackup FTBFS with OpenSSL 1.1.1)

Your message dated Fri, 07 Jun 2019 11:19:16 + with message-id and subject line Bug#907135: fixed in boxbackup 0.13~~git20180313.g16a11e86-2 has caused the Debian Bug report #907135, regarding boxbackup FTBFS with OpenSSL 1.1.1 to be marked as done. This means that you claim that the problem

Processed: tagging 929584, tagging 929650, tagging 888733, found 929882 in 4:18.04.0-1 ..., tagging 929954

Processing commands for cont...@bugs.debian.org: > tags 929584 + sid buster Bug #929584 [src:golang-github-rackspace-gophercloud] Not suitable for buster Added tag(s) sid and buster. > tags 929650 + sid Bug #929650 [src:openjdk-8] openjdk-8 is staying in unstable Added tag(s) sid. > tags 888733 +

Bug#929067: marked as done (Support for MDS)

Your message dated Fri, 07 Jun 2019 10:02:53 + with message-id and subject line Bug#929067: fixed in qemu 1:2.8+dfsg-6+deb9u7 has caused the Debian Bug report #929067, regarding Support for MDS to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#924616: marked as done (CVE-2018-15587: Signature Spoofing in PGP encrypted email)

Your message dated Fri, 07 Jun 2019 10:02:09 + with message-id and subject line Bug#924616: fixed in evolution 3.22.6-1+deb9u2 has caused the Debian Bug report #924616, regarding CVE-2018-15587: Signature Spoofing in PGP encrypted email to be marked as done. This means that you claim that the

Bug#872433: [with solution] Doesn't find modules installed in Debian directories

Hello, proposed patch can't be applied on stretch package.

Bug#900912: fixed in openjdk-11 11.0.3+7-2

[Ccing doko explicitly] On Sun, 21 Apr 2019 15:27:52 +0200 Paul Gevers wrote: > Just to confirm, you do consider openjdk-11/11.0.3+7-2 suitable for > buster, right? I haven't seen an unblock request, but would not be > surprised if you are expecting that I'll just unblock it. ^^ -- Sent from m

Bug#929567:

On 2019-06-06 09:31:28 +0200, Andreas Henriksson wrote: > On Wed, Jun 05, 2019 at 03:51:47PM +, J. Smith wrote: > > See https://debbugs.gnu.org/30045 (fixed in Emacs 26.2). > > According to the merged upstream duplicates these should be the relevant > fixes: > > http://git.savannah.gnu.org/cg

Bug#929954: Status of this issue WRT freeze

On 07.06.19 09:21, Elena ``of Valhalla'' wrote: > Hello > > I've given a look at the code, and I expect that what happened is an > implicit import that changed inside reportlab, but I agree that the > right place to fix this is in rst2pdf. > > Since we are in freeze, however, I'd like to know whe

Bug#922669: fixed in sqlalchemy 1.2.18+ds1-2

On 6/1/19 1:40 PM, Hideki Yamane wrote: > Hi, > > Do you file unblock for sqlalchemy? It's already migrated to Buster. > Or also add debian/NEWS file to indicate potential incompatibility for > applications? No, I haven't. However, the risk is just an SQL query not working, and apparently, o

Bug#930050: miniupnpd: CVE-2019-12107 CVE-2019-12108 CVE-2019-12109 CVE-2019-12110 CVE-2019-12111

On 6/6/19 9:38 AM, Salvatore Bonaccorso wrote: > Source: miniupnpd > Version: 2.1-5 > Severity: grave > Tags: security upstream > Justification: user security hole > Control: found -1 1.8.20140523-4.1+deb9u1 > Control: found -1 1.8.20140523-1 > > Hi, > > The following vulnerabilities were publish

Bug#929954: Status of this issue WRT freeze

Hello I've given a look at the code, and I expect that what happened is an implicit import that changed inside reportlab, but I agree that the right place to fix this is in rst2pdf. Since we are in freeze, however, I'd like to know whether the changed reportlab is meant to enter buster or not: I