Bug#1033752: marked as done (sniproxy: CVE-2023-25076)

2023-05-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 May 2023 19:32:29 + with message-id and subject line Bug#1033752: fixed in sniproxy 0.6.0-2+deb11u1 has caused the Debian Bug report #1033752, regarding sniproxy: CVE-2023-25076 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1036281: marked as done (libraw: CVE-2023-1729)

2023-05-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 May 2023 19:32:23 + with message-id and subject line Bug#1036281: fixed in libraw 0.20.2-1+deb11u1 has caused the Debian Bug report #1036281, regarding libraw: CVE-2023-1729 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: Re: systemd: please ship a placeholder in /usr/lib/modules-load.d/

2023-05-29 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1036920 [systemd] systemd: please ship a placeholder in /usr/lib/modules-load.d/ Severity set to 'important' from 'serious' -- 1036920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036920 Debian Bug Tracking System Contact

Bug#1036920: systemd: please ship a placeholder in /usr/lib/modules-load.d/

2023-05-29 Thread Luca Boccassi
Control: severity -1 important On Mon, 29 May 2023 14:42:14 +0200 Andreas Beckmann wrote: > Package: systemd > Version: 252.6-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts Given what was discussed: - bookworm is in hard freeze - there is no functional impact -

Bug#1036591: marked as done (reaver: segmentation fault)

2023-05-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 May 2023 17:48:55 + with message-id and subject line Bug#1036591: fixed in reaver 1.6.6-0.1 has caused the Debian Bug report #1036591, regarding reaver: segmentation fault to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: Adjust bug again

2023-05-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1036163 fcitx5-zhuyin/5.0.11-1 Bug #1036163 {Done: Shengjing Zhu } [fcitx5-zhuyin] failed.mmap /usr/share/fcitx5/zhuyin/gb_char.bin failed No longer marked as found in versions fcitx5-zhuyin/5.0.11-1. > thanks Stopping processing here.

Processed: Adjust bug 1036163 range

2023-05-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # BTS does not recognize binNMU > # Circumvent with somehow incorrect version numbers > # Actually fixed 1036163 fcitx5-zhuyin/5.0.11-1+b1 > notfixed 1036163 fcitx5-zhuyin/5.0.10-1 Bug #1036163 {Done: Shengjing Zhu } [fcitx5-zhuyin] failed.mmap

Bug#1035543: init-system-helpers: new systemd units may not get enabled on upgrades from bullseye if systemd is installed

2023-05-29 Thread James Addison
Followup-For: Bug #1035543 X-Debbugs-Cc: ty...@mit.edu, bi...@debian.org, hel...@subdivi.de, jspri...@debian.org, ans...@debian.org, a...@debian.org, debian.bugrep...@wodny.org I've been 'approximately' testing this locally on bookworm by: * Editing the Install.WantedBy in

Bug#1036920: systemd: please ship a placeholder in /usr/lib/modules-load.d/

2023-05-29 Thread Luca Boccassi
On Mon, 29 May 2023 15:17:51 +0200 Andreas Beckmann wrote: > On 29/05/2023 14.57, Luca Boccassi wrote: > >> Side question first: does systemd evaluate both > >> /usr/lib/modules-load.d/* and /lib/modules-load.d/* ? > >> Otherwise all packages shipping something in /lib/modules-load.d/ are > >>

Bug#1036920: systemd: please ship a placeholder in /usr/lib/modules-load.d/

2023-05-29 Thread Marco d'Itri
On May 29, Luca Boccassi wrote: > Does it matter that much if the empty directory is removed? Next time > a package shipping a modules-load config is installed it will be just > re-added, no? Or are there functional issues? I do not think that it is a big deal if /usr/lib/modules-load.d/

Bug#1036920: systemd: please ship a placeholder in /usr/lib/modules-load.d/

2023-05-29 Thread Helmut Grohne
Hi Andreas, On Mon, May 29, 2023 at 02:42:14PM +0200, Andreas Beckmann wrote: > during a test with piuparts I noticed your package ships an empty > directory (/usr/lib/modules-load.d/) which disappears after installation > and removal of another package (e.g. multipath-tools) in a merged-/usr >

Bug#1036920: systemd: please ship a placeholder in /usr/lib/modules-load.d/

2023-05-29 Thread Andreas Beckmann
On 29/05/2023 14.57, Luca Boccassi wrote: Side question first: does systemd evaluate both /usr/lib/modules-load.d/* and /lib/modules-load.d/* ? Otherwise all packages shipping something in /lib/modules-load.d/ are broken on unmerged-/usr because their config snippets are not being taken into

Bug#1036920: systemd: please ship a placeholder in /usr/lib/modules-load.d/

2023-05-29 Thread Luca Boccassi
On Mon, 29 May 2023 at 14:07, Andreas Beckmann wrote: > > On 29/05/2023 14.57, Luca Boccassi wrote: > > Wouldn't the correct workaround be to list /usr/lib/modules-load.d in > > systemd.dirs so that dpkg leaves it alone? Seems way too late for > > Bookworm though? > > for dpkg,

Bug#1036920: systemd: please ship a placeholder in /usr/lib/modules-load.d/

2023-05-29 Thread Andreas Beckmann
On 29/05/2023 14.57, Luca Boccassi wrote: Wouldn't the correct workaround be to list /usr/lib/modules-load.d in systemd.dirs so that dpkg leaves it alone? Seems way too late for Bookworm though? for dpkg, /usr/lib/modules-load.d is already owned by systemd, dpkg only accidentally deletes it

Bug#1036920: systemd: please ship a placeholder in /usr/lib/modules-load.d/

2023-05-29 Thread Luca Boccassi
On Mon, 29 May 2023 14:42:14 +0200 Andreas Beckmann wrote: > Package: systemd > Version: 252.6-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package ships an empty > directory (/usr/lib/modules-load.d/) which

Bug#1031046: Error while trying to create asterisk-20.3.0 deb file

2023-05-29 Thread Daniel Huhardeaux
Hi, I try to create a deb file using dh_make or cowbuilder and it fail with the same error: configure.ac:508: error: possibly undefined macro: AC_MSG_WARN   If this token and others are legitimate, please use m4_pattern_allow.   See the Autoconf documentation. configure.ac:849: error:

Bug#1036920: systemd: please ship a placeholder in /usr/lib/modules-load.d/

2023-05-29 Thread Andreas Beckmann
Package: systemd Version: 252.6-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships an empty directory (/usr/lib/modules-load.d/) which disappears after installation and removal of another package (e.g.

Bug#1036096: marked as done (jed,xjed: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

2023-05-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 May 2023 12:34:20 + with message-id and subject line Bug#1036096: fixed in jed 1:0.99.20~pre.180+dfsg-1 has caused the Debian Bug report #1036096, regarding jed,xjed: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE to be marked as done. This

Bug#1035839: marked as done (jed-common: Fails to upgrade: new jed-common package pre-installation script subprocess returned error exit status 1)

2023-05-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 May 2023 12:34:20 + with message-id and subject line Bug#1035839: fixed in jed 1:0.99.20~pre.180+dfsg-1 has caused the Debian Bug report #1035839, regarding jed-common: Fails to upgrade: new jed-common package pre-installation script subprocess returned error exit

Bug#1035780: marked as done (jed-common: Fails to upgrade: unable to install new version of '/usr/share/jed/doc/txt/abbrev.txt': No such file or directory)

2023-05-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 May 2023 12:34:20 + with message-id and subject line Bug#1035780: fixed in jed 1:0.99.20~pre.180+dfsg-1 has caused the Debian Bug report #1035780, regarding jed-common: Fails to upgrade: unable to install new version of '/usr/share/jed/doc/txt/abbrev.txt': No such

Bug#1035692: marked as done (jed-common: unhandled symlink to directory conversion: /usr/share/doc/jed-common/txt -> ../../jed/doc/txt)

2023-05-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 May 2023 12:34:20 + with message-id and subject line Bug#1035692: fixed in jed 1:0.99.20~pre.180+dfsg-1 has caused the Debian Bug report #1035692, regarding jed-common: unhandled symlink to directory conversion: /usr/share/doc/jed-common/txt -> ../../jed/doc/txt to

Bug#1036847: marked as done (sofia-sip: CVE-2023-32307: heap-over-flow and integer-overflow in stun_parse_attr_error_code and stun_parse_attr_uint32)

2023-05-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 May 2023 10:04:33 + with message-id and subject line Bug#1036847: fixed in sofia-sip 1.12.11+20110422.1+1e14eea~dfsg-6 has caused the Debian Bug report #1036847, regarding sofia-sip: CVE-2023-32307: heap-over-flow and integer-overflow in stun_parse_attr_error_code

Bug#1034943: marked as done (liblxqt1-dev: missing Breaks+Replaces for liblxqt0-dev when upgrading from bullseye)

2023-05-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 May 2023 07:49:16 + with message-id and subject line Bug#1034943: fixed in liblxqt 1.2.0-8 has caused the Debian Bug report #1034943, regarding liblxqt1-dev: missing Breaks+Replaces for liblxqt0-dev when upgrading from bullseye to be marked as done. This means