Processed: tagging 968997

2023-03-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 968997 + bullseye Bug #968997 {Done: Laurent Bigonville } [shim] fwupdmgr: "Successfully" updates BIOS firmware, no effect on reboot Bug #990447 {Done: Laurent Bigonville } [shim] fwupdmgr: Unable to install new updates Added tag(s)

Processed: fixed 968997 in 15.7-1

2023-03-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 968997 15.7-1 Bug #968997 {Done: Laurent Bigonville } [shim] fwupdmgr: "Successfully" updates BIOS firmware, no effect on reboot Bug #990447 {Done: Laurent Bigonville } [shim] fwupdmgr: Unable to install new updates There is no source

Processed: closing 968997, tagging 968997

2023-03-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 968997 Bug #968997 [shim] fwupdmgr: "Successfully" updates BIOS firmware, no effect on reboot Bug #990447 [shim] fwupdmgr: Unable to install new updates Marked Bug as done Marked Bug as done > tags 968997 + sid bookworm Bug #968997 {Done:

Bug#1032822: liferea: CVE-2023-1350: RCE vulnerability on feed enrichment

2023-03-11 Thread Salvatore Bonaccorso
Source: liferea Version: 1.14.0-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for liferea. CVE-2023-1350[0]: | A vulnerability was found in liferea. It has been

Bug#1032706: [pkg-lxc-devel] Bug#1032706: lxc-snapshot cannot restore containers with loop storage backend

2023-03-11 Thread Sperl, Mario
Hi Mathias, I submitted an issue on github: https://github.com/lxc/lxc/issues/4289 Step-by-step is explained there. Thank you, Mario On 3/11/23 17:59, Mathias Gibbens wrote: Hi Mario, I'm currently on travel with not-so-great network connectivity, so I haven't been able to reproduce

Processed: Forwarded upstream

2023-03-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 upstream Bug #1031580 [src:pigx-rnaseq] pigx-rnaseq: FTBFS in testing: E: Build killed with signal TERM after 150 minutes of inactivity Added tag(s) upstream. > forwarded -1 https://github.com/COMBINE-lab/salmon/issues/835 Bug #1031580 [src:pigx-rnaseq]

Bug#1031580: Forwarded upstream

2023-03-11 Thread Andreas Tille
Control: tags -1 upstream Control: forwarded -1 https://github.com/COMBINE-lab/salmon/issues/835

Bug#1032120: Upload of new upstream version before fix has migrated to testing (Was: Re: Bug#1032120: tiledb: uses atomic operations, but is not linked to libatomic)

2023-03-11 Thread Nilesh Patra
Dirk - Ping on this? If you do not have the time, let me know. I'll do a NMU for tiledb to revert to prev version and also file an unblock request. On 3/10/23 20:53, Nilesh Patra wrote: Quoting Andreas Tille: your recent upload of tiledb 2.15.0-1 into unstable is quite unfortunate in freeze

Bug#1032655: psi-plus segfaults

2023-03-11 Thread Stefan Kropp
On Fri, Mar 10, 2023 at 03:45:38PM +0100, Lee Garrett wrote: > psi-plus currently simply segfaults on a stock bookworm installation: > > $ psi-plus > [20230310 15:43:12] W:libpng warning: iCCP: known incorrect sRGB profile > (unknown:0, unknown) > [20230310 15:43:12] W:libpng warning: iCCP:

Bug#1032168: marked as done (meson: autopkgtest fills disk completely)

2023-03-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Mar 2023 22:11:09 + with message-id and subject line Bug#1032168: fixed in meson 1.0.1-5 has caused the Debian Bug report #1032168, regarding meson: autopkgtest fills disk completely to be marked as done. This means that you claim that the problem has been dealt

Bug#1032235: closing 1032235

2023-03-11 Thread Guilhem Moulin
close 1032235 thanks Closing this now, cryptsetup 2:2.6.1-2 and libargon2 0~20190702-0.1 should be able to enter testing together.

Processed: closing 1032235

2023-03-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1032235 Bug #1032235 [libargon2-1] cryptsetup: libgcc_s.so.1 must be installed for pthread_exit to work Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1032235:

Bug#1027954: cppad: binary-all FTBFS

2023-03-11 Thread s3v
Dear Maintainer, I think debian/libcppad-doc.docs needs to be adjusted to reflect changes in documentation file names: - doc.omh was renamed to doc.xrst [1] which was then renamed tocppad.xrst [2] which   was then renamed to user_guide.xrst [3] - omh directory was renamed to xrst [1] Kind

Bug#1032734: OOM when unlocking encrypted root in initramfs

2023-03-11 Thread Guilhem Moulin
Control: tag -1 - moreinfo Control: severity -1 important Control: retitle -1 Argon2 memory cost is not future proof and might OOM on dist-upgrade on memory-constrained systems On Sat, 11 Mar 2023 at 14:53:37 -0500, Jérôme Charaoui wrote: >> Jérôme, what memory cost is the keyslot using? (Paste

Processed: Re: Bug#1032734: OOM when unlocking encrypted root in initramfs

2023-03-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 - moreinfo Bug #1032734 [cryptsetup-bin] OOM when unlocking encrypted root in initramfs Removed tag(s) moreinfo. > severity -1 important Bug #1032734 [cryptsetup-bin] OOM when unlocking encrypted root in initramfs Severity set to 'important' from 'serious' >

Bug#1032168: meson: autopkgtest fills disk completely

2023-03-11 Thread Jussi Pakkanen
On Thu, 9 Mar 2023 at 13:54, Paul Gevers wrote: > Of course I expect you can also just use a porterbox which are there for > this reason: https://wiki.debian.org/PorterBoxHowToUse I have requested access to those but nothing has happened as of yet and I have no idea how long that processing is

Bug#1032734: OOM when unlocking encrypted root in initramfs

2023-03-11 Thread Jérôme Charaoui
Tagging ‘moreinfo’ then. I can definitely see how one can reproduce this theoretically (and possibly in the future when the kernel's memory requirement increase high enough), and mentioned that in the upstream bug, but I'm unable to find a reproducer after dist-upgrading bullseye systems to

Bug#1032734: OOM when unlocking encrypted root in initramfs

2023-03-11 Thread Guilhem Moulin
Control: found -1 2:2.1.0-5+deb10u2 Control: tag -1 moreinfo Hi kibi, On Sat, 11 Mar 2023 at 15:16:01 +0100, Cyril Brulebois wrote: > Guilhem Moulin (2023-03-11): >> On Sat, 11 Mar 2023 at 08:26:27 -0500, Jérôme Charaoui wrote: >>> Today I upgraded a small KVM machine with a LUKS2 encrypted

Processed: Re: Bug#1032734: OOM when unlocking encrypted root in initramfs

2023-03-11 Thread Debian Bug Tracking System
Processing control commands: > found -1 2:2.1.0-5+deb10u2 Bug #1032734 [cryptsetup-bin] OOM when unlocking encrypted root in initramfs Marked as found in versions cryptsetup/2:2.1.0-5+deb10u2. > tag -1 moreinfo Bug #1032734 [cryptsetup-bin] OOM when unlocking encrypted root in initramfs Added

Bug#1030205: marked as done (scilab: Could not find Java package '/usr/share/java/batik-all-1.14.jar')

2023-03-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Mar 2023 18:29:20 + with message-id and subject line Bug#1030205: fixed in scilab 6.1.1+dfsg2-5 has caused the Debian Bug report #1030205, regarding scilab: Could not find Java package '/usr/share/java/batik-all-1.14.jar' to be marked as done. This means that you

Bug#1012099: marked as done (scilab: FTBFS with OpenJDK 17: no scilocalization in java.library.path)

2023-03-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Mar 2023 18:29:20 + with message-id and subject line Bug#1012099: fixed in scilab 6.1.1+dfsg2-5 has caused the Debian Bug report #1012099, regarding scilab: FTBFS with OpenJDK 17: no scilocalization in java.library.path to be marked as done. This means that you

Processed: Merge kded crasher bugs

2023-03-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1026062 1028208 Bug #1026062 {Done: Matthias Klumpp } [libpackagekitqt5-1] packagekit-qt: use-after-free in PackageKit::Transaction Bug #1027326 {Done: Matthias Klumpp } [libpackagekitqt5-1] kde-plasma-desktop: Process 1465 (kded5)

Bug#1032706: [pkg-lxc-devel] Bug#1032706: lxc-snapshot cannot restore containers with loop storage backend

2023-03-11 Thread Mathias Gibbens
Hi Mario, I'm currently on travel with not-so-great network connectivity, so I haven't been able to reproduce this on my travel laptop, but will attempt to do so when I'm back from my trip. I expect that this issue will have to be forwarded to the lxc developers; if you want to do so you can

Processed: reassign 1032731 to python3-trezor

2023-03-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1032731 python3-trezor 0.12.4-1 Bug #1032731 [python-trezor] Fails to start: AttributeError: 'TrezorctlGroup' object has no attribute 'resultcallback' Bug reassigned from package 'python-trezor' to 'python3-trezor'. No longer marked as

Processed: Merge kded crasher bugs

2023-03-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1026062 1030854 Bug #1026062 {Done: Matthias Klumpp } [libpackagekitqt5-1] packagekit-qt: use-after-free in PackageKit::Transaction Bug #1027326 {Done: Matthias Klumpp } [libpackagekitqt5-1] kde-plasma-desktop: Process 1465 (kded5)

Processed: Merge kded crasher bugs

2023-03-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1026062 1027326 Bug #1026062 {Done: Matthias Klumpp } [libpackagekitqt5-1] packagekit-qt: use-after-free in PackageKit::Transaction Bug #1027326 {Done: Matthias Klumpp } [libpackagekitqt5-1] kde-plasma-desktop: Process 1465 (kded5)

Processed: your mail

2023-03-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1026062 serious Bug #1026062 {Done: Matthias Klumpp } [libpackagekitqt5-1] packagekit-qt: use-after-free in PackageKit::Transaction Severity set to 'serious' from 'normal' > severity 1027831 serious Bug #1027831 {Done: Matthias Klumpp }

Bug#1028780: python-libzim: FTBFS: libzim/libwrapper.h:161:29: error: ‘class zim::Archive’ has no member named ‘getMediaCount’

2023-03-11 Thread Emmanuel Engelhart
I have just learned about this ticket and have opened a ticket upstream: https://github.com/openzim/python-libzim/issues/160 Like I said there, this version of python-libzim requires libzim-8.1.0 so: * either there is a problem in getMediaCount() declaration in libzim headers OR * Debian

Processed: reassign 1032731 to python-trezor

2023-03-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1032731 python-trezor 0.12.4-1 Bug #1032731 [trezor] Fails to start: AttributeError: 'TrezorctlGroup' object has no attribute 'resultcallback' Bug reassigned from package 'trezor' to 'python-trezor'. No longer marked as found in

Bug#919058: its-tools: crashes when freeing xmlDocs

2023-03-11 Thread s3v
Dear Maintainer, This issue fixed in libxml2 seems to be related [1] Kind Regards [1] https://gitlab.gnome.org/GNOME/libxml2/-/issues/64

Bug#1032544: pylint: FTBFS in testing: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2023-03-11 Thread Andrey Rakhmatullin
This may be related, or just a duplicate, to #1032043, fixed in the newer version which is already in testing.

Bug#1032553: magic-wormhole: FTBFS in testing: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13

2023-03-11 Thread Andrey Rakhmatullin
On Wed, Mar 08, 2023 at 09:30:04PM +0100, Lucas Nussbaum wrote: > > == > > FAIL: test_welcome (wormhole.test.test_wormhole.Wormholes.test_welcome) > > test_welcome > >

Processed (with 1 error): reassign 1032731 to python-trezor/0.12.4-1, affects 1032731, tagging 1032731

2023-03-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1032731 python-trezor/0.12.4-1 Unknown command or malformed arguments to command. > affects 1032731 trezor Bug #1032731 [trezor] Fails to start: AttributeError: 'TrezorctlGroup' object has no attribute 'resultcallback' Added indication

Processed: Re: Bug#1032734: OOM when unlocking encrypted root in initramfs

2023-03-11 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1032734 [cryptsetup-bin] OOM when unlocking encrypted root in initramfs Severity set to 'serious' from 'important' -- 1032734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032734 Debian Bug Tracking System Contact

Bug#1032734: OOM when unlocking encrypted root in initramfs

2023-03-11 Thread Guilhem Moulin
Control: reassign -1 cryptsetup-bin 2:2.6.1-2 Control: severity -1 important Control: tag -1 upstream Control: forwarded -1 https://gitlab.com/cryptsetup/cryptsetup/-/issues/802#note_1287298872 Hi, On Sat, 11 Mar 2023 at 08:26:27 -0500, Jérôme Charaoui wrote: > Today I upgraded a small KVM

Processed: Re: Bug#1032734: OOM when unlocking encrypted root in initramfs

2023-03-11 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 cryptsetup-bin 2:2.6.1-2 Bug #1032734 [cryptsetup] OOM when unlocking encrypted root in initramfs Bug reassigned from package 'cryptsetup' to 'cryptsetup-bin'. No longer marked as found in versions cryptsetup/2:2.6.1-1. Ignoring request to alter fixed

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-03-11 Thread Thorsten Glaser
James Addison dixit: >Based on what I've learned about this bug, I believe that architecture-specific >behaviour related to stack sizes is inherent in the V8 library vendored by >upstream NodeJS. Yes, but the v8 library’s defaults are targetting a browser, and one whose uses are much wider, e.g.

Bug#1032734: OOM when unlocking encrypted root in initramfs

2023-03-11 Thread Jérôme Charaoui
Package: cryptsetup Version: 2:2.6.1-1 Severity: critical Dear maintainer, Today I upgraded a small KVM machine with a LUKS2 encrypted root and 1GiB of RAM to bookworm, and was very surprised to be confronted with an OOM immediately upon entering my LUKS password in the initramfs prompt:

Processed: Re: Bug#1032174: xfishtank does nothing

2023-03-11 Thread Debian Bug Tracking System
Processing control commands: > severity 1032174 important Bug #1032174 [xfishtank] xfishtank does nothing Severity set to 'important' from 'grave' > retitle 1032174 xfishtank does not work on modern desktop Bug #1032174 [xfishtank] xfishtank does nothing Changed Bug title to 'xfishtank does not

Bug#1032174: xfishtank does nothing

2023-03-11 Thread Marius Gavrilescu
Control: severity 1032174 important Control: retitle 1032174 xfishtank does not work on modern desktop environments Control: tags 1032174 upstream Thanks for your bug report Martin, xfishtank is implemented by drawing on the root window, which does not work on modern desktop environments

Bug#1018023: marked as done (eterm: FTBFS with imlib2 1.9.1)

2023-03-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Mar 2023 11:33:58 + with message-id and subject line Bug#1018023: fixed in eterm 0.9.6-7 has caused the Debian Bug report #1018023, regarding eterm: FTBFS with imlib2 1.9.1 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-03-11 Thread James Addison
Package: nodejs Followup-For: Bug #1030284 X-Debbugs-Cc: t...@mirbsd.de On Thu, 02 Feb 2023 01:56:10 +, Thorsten wrote: > I consider this an architecture-specific release-critical bug. Maybe > having a reproducer and access to a porterbox will allow a nodejs > maintainer to track this down.

Bug#1032733: gcc-10-doc should not be shipped in bookworm

2023-03-11 Thread Dmitry Baryshkov
Source: gcc-10-doc Version: 10.4.0-1 Severity: serious Control: block -1 by 1023666 Following gcc-10 removal, gcc-10-doc should not be shipped in bookworm release. -- System Information: Debian Release: bookworm/sid APT prefers testing-security APT policy: (500, 'testing-security'), (500,

Bug#1018023: Update on this bug?

2023-03-11 Thread Matthew Vernon
Hi, On 10/03/2023 23:12, Jose Antonio Jimenez Madrid wrote: I have just uploaded to mentors a new version of the package fixing this bug. I will made other improvements after Bookworm is released as we are very close to the full freeze. The new package can be found here:

Processed: gcc-10-doc should not be shipped in bookworm

2023-03-11 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 1023666 Bug #1032733 [src:gcc-10-doc] gcc-10-doc should not be shipped in bookworm 1032733 was not blocked by any bugs. 1032733 was not blocking any bugs. Added blocking bug(s) of 1032733: 1023666 -- 1032733:

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-03-11 Thread James Addison
Package: nodejs Followup-For: Bug #1030284 X-Debbugs-Cc: t...@debian.org Guidance received from the V8 project (a vendored dependency in the upstream NodeJS codebase) on the v8-dev mailing list is, in summary/interpretation: * It is not yet safe to increase the stack size limit on ARM64

Bug#1032647: Testing with official Nvidia driver 530.30.02

2023-03-11 Thread julienbenjamin
Good morning, Quick update: in a moment of despair, I tried what felt like the last resort, which was installing the latest driver, from the Nvidia website. (I know, I know) Long story short, I stopped the X server, unloaded Nouveau, and ran the installation wizard ; it almost ran without

Bug#1032731: Fails to start: AttributeError: 'TrezorctlGroup' object has no attribute 'resultcallback'

2023-03-11 Thread Jonathan McDowell
Package: trezor Version: 0.12.4-1 Severity: grave X-Debbugs-Cc: nood...@earth.li Control: forwarded -1 https://github.com/trezor/trezor-firmware/issues/2199 Installed trezor and tried to run it, got a traceback: $ trezorctl Traceback (most recent call last): File "/usr/bin/trezorctl", line

Processed: Fails to start: AttributeError: 'TrezorctlGroup' object has no attribute 'resultcallback'

2023-03-11 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/trezor/trezor-firmware/issues/2199 Bug #1032731 [trezor] Fails to start: AttributeError: 'TrezorctlGroup' object has no attribute 'resultcallback' Set Bug forwarded-to-address to

Processed: Re: cdimage.debian.org: bookworm net-install CD hangs on "Detecting Network Hardware"

2023-03-11 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 debian-cd Bug #1005886 [cdimage.debian.org] cdimage.debian.org: bookworm net-install CD hangs on "Detecting Network Hardware" Bug reassigned from package 'cdimage.debian.org' to 'debian-cd'. Ignoring request to alter found versions of bug #1005886 to

Bug#1005886: cdimage.debian.org: bookworm net-install CD hangs on "Detecting Network Hardware"

2023-03-11 Thread James Addison
Followup-For: Bug #1005886 Control: reassign -1 debian-cd Control: retitle -1 debian-cd: bookworm net-install CD hangs on "Detecting Network Hardware"

Bug#1032724: swift-im: should not be shipped with bookworm (RoM)

2023-03-11 Thread Tobias Frost
Source: swift-im Severity: serious Justification: RoM I've packaged swift-im for spectrum2, which has determined to be (currently) not suitable for inclusion to Debian due to a license incompatibilty. Therefore it currently makes no sense to have this huge library in a stable release, which is

Bug#1032706: lxc-snapshot cannot restore containers with loop storage backend

2023-03-11 Thread Sperl, Mario
Package: lxc Version: 1:5.0.2-1 Severity: grave Justification: causes data loss Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I tried to generate a snapshot with lxc-snapshot for a test container that is more