Bug#989193: fixed in apparmor-profiles-extra 1.34

2021-06-21 Thread Paul Wise
On Wed, 09 Jun 2021 07:18:32 + intrigeri wrote: >* apt-cacher-ng: allow link operations on the contents of the cache > directory > (Closes: #989193). Thanks to Eduard Bloch for the patch. Here is a little bump to postpone the autoremoval so the fix gets into testing. -- bye,

Bug#990158: shim-signed-common: No UEFI boot with error "Could not create MokListXRT"

2021-06-21 Thread Steve McIntyre
Hi Ayke, Thanks for your bug report, and apologies for the problem :-/ On Mon, Jun 21, 2021 at 09:00:15PM +0200, Ayke Halder wrote: >Package: shim-signed-common >Version: 1.33+15+1533136590.3beb971-7 >Severity: critical >Justification: breaks the whole system > >Dear Maintainer, > >## What led

Bug#987461: libuima-adapter-soap-java is empty

2021-06-21 Thread tony mancill
On Tue, Jun 22, 2021 at 07:57:13AM +0900, Hideki Yamane wrote: > Hi, > > On Mon, 21 Jun 2021 11:52:14 -0700 > tony mancill wrote: > > I saw the note in the changelog that Breaks is in fact there to remove > > the empty package, but it's not happening for me when I try to upgrade > > locally. My

Bug#987461: libuima-adapter-soap-java is empty

2021-06-21 Thread Hideki Yamane
Hi, On Mon, 21 Jun 2021 11:52:14 -0700 tony mancill wrote: > I saw the note in the changelog that Breaks is in fact there to remove > the empty package, but it's not happening for me when I try to upgrade > locally. My test case is to install uima-utils (which will install >

Processed: Re: Bug#990123: [buster regression] iptables-netflow-dkms: No more compiles since linux-*-4.19.0-17-*: "implicit declaration of function ‘ref_module’" (Upstream kernel API regression in 4.1

2021-06-21 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 iptables-netflow-dkms Bug #990123 [iptables-netflow-dkms,linux-headers-4.19.0-17-amd64,linux-headers-4.19.0-17-i686-pae] [buster regression] iptables-netflow-dkms: No more compiles since linux-*-4.19.0-17-*: "implicit declaration of function

Bug#990123: [buster regression] iptables-netflow-dkms: No more compiles since linux-*-4.19.0-17-*: "implicit declaration of function ‘ref_module’" (Upstream kernel API regression in 4.19.191?)

2021-06-21 Thread Axel Beckert
Control: reassign -1 iptables-netflow-dkms Control: found -1 2.3-5 Control: notfound -1 2.5.1-2 Hi Salvatore, Salvatore Bonaccorso wrote: > On Mon, Jun 21, 2021 at 01:33:01PM +0200, Axel Beckert wrote: > > Since kernel packages linux-{image,headers}-4.19.0-17-*, at least with > > -amd64 and

Bug#990123: [buster regression] iptables-netflow-dkms: No more compiles since linux-*-4.19.0-17-*: "implicit declaration of function ‘ref_module’" (Upstream kernel API regression in 4.19.191?)

2021-06-21 Thread Salvatore Bonaccorso
Control: affects -1 + release.debian.org Hi Axel, On Mon, Jun 21, 2021 at 01:33:01PM +0200, Axel Beckert wrote: > Package: > iptables-netflow-dkms,linux-headers-4.19.0-17-amd64,linux-headers-4.19.0-17-i686-pae > Severity: serious > Version: iptables-netflow/2.3-5 > Version:

Processed: Re: Bug#990123: [buster regression] iptables-netflow-dkms: No more compiles since linux-*-4.19.0-17-*: "implicit declaration of function ‘ref_module’" (Upstream kernel API regression in 4.1

2021-06-21 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + release.debian.org Bug #990123 [iptables-netflow-dkms,linux-headers-4.19.0-17-amd64,linux-headers-4.19.0-17-i686-pae] [buster regression] iptables-netflow-dkms: No more compiles since linux-*-4.19.0-17-*: "implicit declaration of function

Bug#922981: tagging 922981 (ca-certificates-java: /etc/ca-certificates/update.d/jks-keystore doesn't update /etc/ssl/certs/java/cacerts)

2021-06-21 Thread Paul Gevers
Hi Julien, On Tue, 18 May 2021 21:38:46 +0200 Paul Gevers wrote: > On 08-04-2021 19:33, Julien Cristau wrote: > > I've started to look at it, I'm afraid building up context on this > > stuff to understand what it's doing is going to take a while... > > Just a friendly ping. Did you get anywhere

Bug#990000: marked as done (tor: CVE-2021-34548 CVE-2021-34549 CVE-2021-34550)

2021-06-21 Thread Debian Bug Tracking System
Your message dated Mon, 21 Jun 2021 19:02:13 + with message-id and subject line Bug#99: fixed in tor 0.3.5.15-1 has caused the Debian Bug report #99, regarding tor: CVE-2021-34548 CVE-2021-34549 CVE-2021-34550 to be marked as done. This means that you claim that the problem has been

Bug#989631: marked as done (nettle: CVE-2021-3580: Remote crash in RSA decryption via manipulated ciphertext)

2021-06-21 Thread Debian Bug Tracking System
Your message dated Mon, 21 Jun 2021 19:02:07 + with message-id and subject line Bug#989631: fixed in nettle 3.4.1-1+deb10u1 has caused the Debian Bug report #989631, regarding nettle: CVE-2021-3580: Remote crash in RSA decryption via manipulated ciphertext to be marked as done. This means

Bug#990158: shim-signed-common: No UEFI boot with error "Could not create MokListXRT"

2021-06-21 Thread Ayke Halder
Package: shim-signed-common Version: 1.33+15+1533136590.3beb971-7 Severity: critical Justification: breaks the whole system Dear Maintainer, ## What led up to the situation? Upgrade: * shim-signed:amd64 (1.33+15+1533136590.3beb971-7, 1.36~1+deb10u1+15.4-5~deb10u1) * shim-signed-common:amd64

Bug#987461: libuima-adapter-soap-java is empty

2021-06-21 Thread tony mancill
On Sat, Jun 19, 2021 at 07:46:28AM -0700, tony mancill wrote: > On Sat, Jun 19, 2021 at 10:29:25PM +0900, Hideki Yamane wrote: > > So let's remove its binary package and add Breaks: to it. > > MR is here, could someone review it, please? > >

Bug#990140: upgrade-reports: lxc-attach does not start with apparmor problem after ugrade to 10.10

2021-06-21 Thread Bernd Breuer
Hi Paul, thanks for your immediate response. Your assumption is right, booting into kernel 4.19.0-16 causes lxc-attach to behave as expected, no more apparmor related errors. Cheers Bernd Am 21.06.21 um 19:06 schrieb Paul Gevers: Hi Bernd, Thanks for your report. On 21-06-2021 18:04,

Bug#987461: marked as pending in uimaj

2021-06-21 Thread Tony Mancill
Control: tag -1 pending Hello, Bug #987461 in uimaj 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:

Processed: Bug#987461 marked as pending in uimaj

2021-06-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #987461 [libuima-adapter-soap-java] libuima-adapter-soap-java is empty Added tag(s) pending. -- 987461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: [bts-link] source package src:python-enable

2021-06-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:python-enable > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user

Processed: duplicate

2021-06-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # try two > forcemerge 990072 990140 Bug #990072 {Done: Salvatore Bonaccorso } [src:linux] lxc-attach fails after debian 10.10 update Bug #990075 {Done: Salvatore Bonaccorso } [src:linux] lxc-attach fails after debian 10.10 update Bug #990089

Bug#989749: marked as done (kore: flaky amd64 autopkgtest: regularly times out after 2:47 h)

2021-06-21 Thread Debian Bug Tracking System
Your message dated Mon, 21 Jun 2021 17:03:34 + with message-id and subject line Bug#989749: fixed in kore 4.1.0-3 has caused the Debian Bug report #989749, regarding kore: flaky amd64 autopkgtest: regularly times out after 2:47 h to be marked as done. This means that you claim that the

Bug#990026: Commonly-in-use characters

2021-06-21 Thread Matthias Urlichs
So far, we identified "/" and "=" as characters which definitely should be restored in order to not break our installations. -- -- Matthias Urlichs OpenPGP_signature Description: OpenPGP digital signature

Bug#989069: nvidia-driver: Crash when displayport is plugged.

2021-06-21 Thread Christian Marillat
On 25 mai 2021 08:10, Andreas Beckmann wrote: [...] >> Bug already reported upstream here : > > Not much we can do here :-( (besides not migrating this version to bullseye) Seems to be fixed : https://forums.developer.nvidia.com/t/465-24-02-page-fault/175782/135 Christian

Bug#897707: Should this package be removed from Debian?

2021-06-21 Thread Timo Röhling
Control: user debian...@lists.debian.org Control: usertag -1 + proposed-removal Given that this RC bug and #892288 have been unresolved for several years and the last upload dates back to 2016 with multiple upstream releases since, I believe this package should be considered for QA removal.

Bug#989731: marked as done (postgresql-13-q3c: drop Conflicts+Replaces: postgresql-q3c)

2021-06-21 Thread Debian Bug Tracking System
Your message dated Mon, 21 Jun 2021 14:20:29 + with message-id and subject line Bug#989731: fixed in postgresql-q3c 2.0.0-5 has caused the Debian Bug report #989731, regarding postgresql-13-q3c: drop Conflicts+Replaces: postgresql-q3c to be marked as done. This means that you claim that the

Bug#989732: marked as done (postgresql-13-pgsphere: drop Conflicts+Replaces: postgresql-pgsphere)

2021-06-21 Thread Debian Bug Tracking System
Your message dated Mon, 21 Jun 2021 15:54:52 +0200 with message-id <860266c8-670f-97ca-b852-954ef8389...@debian.org> and subject line Bug#989732: fixed in pgsphere 1.1.1+2020-10-20-2 has caused the Debian Bug report #989732, regarding postgresql-13-pgsphere: drop Conflicts+Replaces:

Bug#989731: marked as done (postgresql-13-q3c: drop Conflicts+Replaces: postgresql-q3c)

2021-06-21 Thread Debian Bug Tracking System
Your message dated Mon, 21 Jun 2021 13:48:29 + with message-id and subject line Bug#989731: fixed in pgsphere 1.1.1+2020-10-20-2 has caused the Debian Bug report #989731, regarding postgresql-13-q3c: drop Conflicts+Replaces: postgresql-q3c to be marked as done. This means that you claim that

Bug#989731: marked as pending in postgresql-q3c

2021-06-21 Thread Ole Streicher
Control: tag -1 pending Hello, Bug #989731 in postgresql-q3c 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:

Processed: Bug#989731 marked as pending in postgresql-q3c

2021-06-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #989731 [postgresql-13-pgsphere] postgresql-13-q3c: drop Conflicts+Replaces: postgresql-q3c Ignoring request to alter tags of bug #989731 to the same tags previously set -- 989731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989731 Debian

Processed: Bug#989731 marked as pending in pgsphere

2021-06-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #989731 [postgresql-13-pgsphere] postgresql-13-q3c: drop Conflicts+Replaces: postgresql-q3c Added tag(s) pending. -- 989731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989731 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#989731: marked as pending in pgsphere

2021-06-21 Thread Ole Streicher
Control: tag -1 pending Hello, Bug #989731 in pgsphere 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:

Processed: found 990123 in iptables-netflow/2.3-5, found 990123 in iptables-netflow/2.5.1-2 ...

2021-06-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # Version tracking seems to not have worked properly in the initial bug > submission > found 990123 iptables-netflow/2.3-5 Bug #990123 [iptables-netflow-dkms,linux-headers-4.19.0-17-amd64,linux-headers-4.19.0-17-i686-pae] [buster regression]

Bug#990107: marked as done (linux-image-4.19.0-17-amd64: lxc-attach Operation not permitted - Failed to set AppArmor label)

2021-06-21 Thread Debian Bug Tracking System
Your message dated Mon, 21 Jun 2021 12:02:07 + with message-id and subject line Bug#990072: fixed in linux 4.19.194-2 has caused the Debian Bug report #990072, regarding linux-image-4.19.0-17-amd64: lxc-attach Operation not permitted - Failed to set AppArmor label to be marked as done. This

Bug#990089: marked as done (linux-image-4.19.0-17-amd64: lxc-attach fails with Failed to set AppArmor label unconfined)

2021-06-21 Thread Debian Bug Tracking System
Your message dated Mon, 21 Jun 2021 12:02:07 + with message-id and subject line Bug#990072: fixed in linux 4.19.194-2 has caused the Debian Bug report #990072, regarding linux-image-4.19.0-17-amd64: lxc-attach fails with Failed to set AppArmor label unconfined to be marked as done. This

Bug#990072: marked as done (lxc-attach fails after debian 10.10 update)

2021-06-21 Thread Debian Bug Tracking System
Your message dated Mon, 21 Jun 2021 12:02:07 + with message-id and subject line Bug#990072: fixed in linux 4.19.194-2 has caused the Debian Bug report #990072, regarding lxc-attach fails after debian 10.10 update to be marked as done. This means that you claim that the problem has been dealt

Bug#990075: marked as done (lxc-attach fails after debian 10.10 update)

2021-06-21 Thread Debian Bug Tracking System
Your message dated Mon, 21 Jun 2021 12:02:07 + with message-id and subject line Bug#990072: fixed in linux 4.19.194-2 has caused the Debian Bug report #990072, regarding lxc-attach fails after debian 10.10 update to be marked as done. This means that you claim that the problem has been dealt

Bug#990123: [buster regression] iptables-netflow-dkms: No more compiles since linux-*-4.19.0-17-*: "implicit declaration of function ‘ref_module’" (Upstream kernel API regression in 4.19.191?)

2021-06-21 Thread Axel Beckert
Package: iptables-netflow-dkms,linux-headers-4.19.0-17-amd64,linux-headers-4.19.0-17-i686-pae Severity: serious Version: iptables-netflow/2.3-5 Version: iptables-netflow/2.5.1-2 Version: linux/4.19.194-1 Tags: buster Forwarded: https://github.com/aabc/ipt-netflow/issues/177 Since kernel packages

Bug#990089: linux-image-4.19.0-17-amd64: lxc-attach fails with Failed to set AppArmor label unconfined

2021-06-21 Thread Salvatore Bonaccorso
Hi, On Mon, Jun 21, 2021 at 10:24:31AM +0100, Gmail wrote: > Salvatore, > > On Sun, 2021-06-20 at 20:39 +0200, Salvatore Bonaccorso wrote: > > Hi Mark, > > > > On Sun, Jun 20, 2021 at 10:44:29AM +0100, Mark Grant wrote: > > > Package: src:linux > > > Version: 4.19.194-1 > > > Severity: normal >

Bug#990119: vip-manager: systemd service file uses incorrect parameter syntax

2021-06-21 Thread Chris Hofstaedtler
Hi, it appears not only have the numbers of dashes changed, but also the actual parameter names. In the current service file, I see: ExecStart=/usr/bin/vip-manager -ip="${VIP_IP}" -iface="${VIP_IFACE}" -key="${VIP_KEY}" -host="${VIP_HOST}" -type="${VIP_TYPE}" -endpoint="${VIP_ENDPOINT}"

Bug#990089: linux-image-4.19.0-17-amd64: lxc-attach fails with Failed to set AppArmor label unconfined

2021-06-21 Thread Gmail
Salvatore, On Sun, 2021-06-20 at 20:39 +0200, Salvatore Bonaccorso wrote: > Hi Mark, > > On Sun, Jun 20, 2021 at 10:44:29AM +0100, Mark Grant wrote: > > Package: src:linux > > Version: 4.19.194-1 > > Severity: normal > > > > Dear Maintainer, > > > > After upgrading from

Bug#990119: vip-manager: systemd service file uses incorrect parameter syntax

2021-06-21 Thread Chris Hofstaedtler
Package: vip-manager Version: 1.0.1-3+b2 Severity: serious Dear Maintainer, thanks for maintaining the vip-manager package. I've noticed that the service file /lib/systemd/system/vip-manager.service uses options with one dash (ex: `-ip=a.b.c.d`), but the vip-manager binary expects two dashes

Bug#989731: Bug#989732: Shall I upload?

2021-06-21 Thread Christoph Berg
Re: Ole Streicher > would you upload the packages with C+R removed soon? Or shall I do? I'd like > to have that fixed before the final freeze. Sorry I haven't got to these yet. If you could upload them, that would be nice. Thanks, Christoph

Bug#990072: Update

2021-06-21 Thread Salvatore Bonaccorso
Hi Matthew, On Sun, Jun 20, 2021 at 11:14:57PM -0400, Matthew Darwin wrote: > kernel 4.19.194-1a~test resolved the issue > > Applied > https://lore.kernel.org/stable/20210614102643.875096...@linuxfoundation.org/ > using the process described at >

Bug#978361: marked as done (hg-git: FTBFS: tests failed)

2021-06-21 Thread Debian Bug Tracking System
Your message dated Mon, 21 Jun 2021 08:33:31 + with message-id and subject line Bug#978361: fixed in hg-git 0.10.1-1 has caused the Debian Bug report #978361, regarding hg-git: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#982459: mdadm --examine in chroot without /proc,/dev,/sys mounted corrupts host's filesystem

2021-06-21 Thread Patrick Cernko
Hi, On 18.06.21 12:48, Patrick Cernko wrote: I will try to reproduce the bug now with one of /dev or /sys mounted and check if it still occurs or not. I will send my report about this later as this will take some time again. I could reproduce the bug with /dev *NOT* mounted in chroot. It

Bug#989731: Shall I upload?

2021-06-21 Thread Ole Streicher
Dear Christoph, would you upload the packages with C+R removed soon? Or shall I do? I'd like to have that fixed before the final freeze. Cheers Ole

Bug#933100: Bug has been fixed in upstream since 0.9.0

2021-06-21 Thread Timo Röhling
Control: fixed -1 0.9.0-1 Hi, it looks like upstream version 0.9.0 is no longer affected by this bug, the tests/test-illegal-contents.t was fixed: - error: Invalid path 'nested/.git/hooks/post-update' + error: [Ii]nvalid path 'nested/\.git/hooks/post-update' (re) Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀

Processed: Bug has been fixed in upstream since 0.9.0

2021-06-21 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 0.9.0-1 Bug #933100 [src:hg-git] hg-git: autopkgtest needs update for new version of git Marked as fixed in versions hg-git/0.9.0-1. -- 933100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933100 Debian Bug Tracking System Contact