Bug#1100726: marked as done (kodi: Segmentation fault at startup)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 18 Mar 2025 06:49:59 + with message-id and subject line Bug#1100726: fixed in kodi 2:21.2+dfsg-2 has caused the Debian Bug report #1100726, regarding kodi: Segmentation fault at startup to be marked as done. This means that you claim that the problem has been dealt wit

Processed: Bug#1100726 marked as pending in kodi

2025-03-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1100726 [kodi] kodi: Segmentation fault at startup Added tag(s) pending. -- 1100726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1100094: marked as pending in kodi

2025-03-17 Thread Vasyl Gello
Control: tag -1 pending Hello, Bug #1100094 in kodi 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/multimedia-team/kodi-media-center/kodi/-/commit/fb38c4a11dd3

Processed: Bug#1100094 marked as pending in kodi

2025-03-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1100094 [kodi] kodi: Kodi fails to build with pipewire 1.4.0 Added tag(s) pending. -- 1100094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1100748: segfault when using get_text() on arm64

2025-03-17 Thread Johannes Schauer Marin Rodrigues
Package: python3-pymupdf Version: 1.25.0+ds1-2 Severity: serious Hi, the autopkgtest of pymupdf currently segfaults on arm64, ppc64el and riscv64. In an attempt to get to the bottom of this I found a minimal reproducer: python3 -c "import pymupdf,sys; doc=pymupdf,sys; doc=pymupdf.open(sys.argv[

Bug#1100726: kodi: Segmentation fault at startup

2025-03-17 Thread Vasyl Gello
The bug is caused by stack corruption in new tinyxml2 library which migrated yesterday: #0 0x753cac71 in tinyxml2::XMLDocument::XMLDocument (this=this@entry=0x7fffdf50, processEntities=processEntities@entry=true, whitespaceMode=whitespaceMode@entry=tinyxml2::PRESERVE_WHITESPAC

Bug#1100544: reopening, c-t-b-mipsen is still unfixed

2025-03-17 Thread Aurelien Jarno
control: tag -1 + patch On 2025-03-17 19:06, Aurelien Jarno wrote: control: reassign -1 cross-toolchain-base-mipsen On 2025-03-17 02:55, Matthias Klose wrote: Control: reopen -1 reopening, c-t-b-mipsen is still unfixed. I'm fine to drop the intermediate patch in c-t-b and c-t-b-ports. c-t-

Processed: Re: Bug#1100544: reopening, c-t-b-mipsen is still unfixed

2025-03-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + patch Bug #1100544 [cross-toolchain-base-mipsen] glibc adds some conflicts letting gcc-14-cross ftbfs Added tag(s) patch. -- 1100544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100544 Debian Bug Tracking System Contact ow...@bugs.debian.org with p

Processed: reassign 1100320 to qt6-pdf-dev ..., affects 1100320

2025-03-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1100320 qt6-pdf-dev qt6-webengine/6.8.2+dfsg-3 Bug #1100320 [src:skanpage] skanpage: FTBFS: Could NOT find Cups (missing: CUPS_LIBRARIES CUPS_INCLUDE_DIR) Bug reassigned from package 'src:skanpage' to 'qt6-pdf-dev'. No longer marked as f

Bug#1081196: Crowdsec

2025-03-17 Thread Mathias Gibbens
On Wed, 2025-03-12 at 18:09 +, Martin Dosch wrote: > Dear all, > > I'd like to see crowdsec in trixie, as I am using it myself. > Is there any chance to get [1081196] fixed by delivering upstreams > sshd-logs.yaml? This file is not in the repo and I failed to figure out > how it is created.

Bug#1100094: kodi: Kodi fails to build with pipewire 1.4.0

2025-03-17 Thread Yue Gui
Hi, this issue may have been solved upstream in the latest version. reference: https://github.com/xbmc/xbmc/commit/269053ebbfd3cc4a3156a511f54ab7f08a09a730 Gui-Yue Best regards

Bug#1098521: marked as done (apparmor 4.x breaks systemd user namespacing in lxc containers)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Tue, 18 Mar 2025 01:05:06 + with message-id and subject line Bug#1098521: fixed in lxc 1:6.0.3-2 has caused the Debian Bug report #1098521, regarding apparmor 4.x breaks systemd user namespacing in lxc containers to be marked as done. This means that you claim that the prob

Processed: Re: Bug#1099935: dnspython: autopkgtest regression on s390x: bad request

2025-03-17 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 python3-pylsqpack 0.3.18-1 Bug #1099935 [src:dnspython] dnspython: autopkgtest regression on s390x: bad request Bug reassigned from package 'src:dnspython' to 'python3-pylsqpack'. No longer marked as found in versions dnspython/2.7.0-1. Ignoring request

Bug#1093368: marked as done (yosys: FTBFS: LaTeX error)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 22:38:52 + with message-id and subject line Bug#1093368: fixed in yosys 0.49-1 has caused the Debian Bug report #1093368, regarding yosys: FTBFS: LaTeX error to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Processed: Re: Bug#1099195: elpa-doom-themes: Rendering issue in Emacs 30, Invalid :style none :box properties

2025-03-17 Thread Debian Bug Tracking System
Processing control commands: > severity -1 grave Bug #1099195 [elpa-doom-themes] elpa-doom-themes: Rendering issue in Emacs 30, Invalid :style none :box properties Severity set to 'grave' from 'important' > tags -1 +confirmed +pending Bug #1099195 [elpa-doom-themes] elpa-doom-themes: Rendering is

Bug#1080844: marked as done (Missing Build-Depends on python3-setuptools)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 22:38:52 + with message-id and subject line Bug#1080844: fixed in yosys 0.49-1 has caused the Debian Bug report #1080844, regarding Missing Build-Depends on python3-setuptools to be marked as done. This means that you claim that the problem has been dealt w

Bug#1052292: marked as done (inkscape: missing Breaks+Replaces: inkscape-open-symbols (<< 1.3))

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 18:17:03 -0400 with message-id and subject line Re: inkscape: missing Breaks+Replaces: inkscape-open-symbols (<< 1.3) has caused the Debian Bug report #1052292, regarding inkscape: missing Breaks+Replaces: inkscape-open-symbols (<< 1.3) to be marked as done.

Processed: Re: Bug#1099195: elpa-doom-themes: Rendering issue in Emacs 30, Invalid :style none :box properties

2025-03-17 Thread Debian Bug Tracking System
Processing control commands: > severity -1 grave Bug #1099195 [elpa-doom-themes] elpa-doom-themes: Rendering issue in Emacs 30, Invalid :style none :box properties Ignoring request to change severity of Bug 1099195 to the same value. > tags -1 +confirmed +pending Bug #1099195 [elpa-doom-themes] e

Bug#1099195: elpa-doom-themes: Rendering issue in Emacs 30, Invalid :style none :box properties

2025-03-17 Thread Xiyue Deng
Control: severity -1 grave Control: tags -1 +confirmed +pending Justification: activating any doom theme results in error, rendering the package unusable for users. Confirmed. The fix is cherrypicked and pushed to Salsa. Would still need a sponsor. -- Regards, Xiyue Deng signature.asc Des

Bug#1100726: kodi: Segmentation fault at startup

2025-03-17 Thread tv.debian
Hello, I am seeing the same on two Sid systems, one long time running Kodi, one tried fresh as a test. For me it was concomitant with a recent libc6 update in Sid. Crash log as follows: ## Kodi CRASH LOG ### SYSTEM INFO Date: Mon Mar

Bug#1100604: PANIC: assert failed at source3/smbd/smb2_oplock.c(156): sconn->oplocks.exclusive_open>=0

2025-03-17 Thread Timo van Roermund
On Mon, 17 Mar 2025 20:11:47 + Etienne Dechamps wrote: > Some additional information: > > Excerpt from my smb.conf: > > unix extensions = no > wide links = yes > kernel oplocks = yes > use sendfile = yes > ea support = no > > Notably, `kernel oplocks = yes` is not the default, which may expl

Bug#1099520: marked as done (yubikey-manager-qt: ImportError: cannot import name '_PrepareUploadFailed' from 'ykman.otp' - Qt application is EOL and uses outdated ykman API)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 21:02:49 + with message-id and subject line Bug#1099520: fixed in yubikey-manager-qt 1.2.5-2 has caused the Debian Bug report #1099520, regarding yubikey-manager-qt: ImportError: cannot import name '_PrepareUploadFailed' from 'ykman.otp' - Qt application is

Processed: Re: python-pysnmp4: deprecation of Python libraries asyncore and asynchat

2025-03-17 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1040085 [src:python-pysnmp4] python-pysnmp4: deprecation of Python libraries asyncore and asynchat Severity set to 'serious' from 'important' > tags -1 + patch Bug #1040085 [src:python-pysnmp4] python-pysnmp4: deprecation of Python librarie

Bug#1100726: kodi: Segmentation fault at startup

2025-03-17 Thread Mathieu
Package: kodi Version: 2:21.2+dfsg-1 Severity: grave Justification: renders package unusable Hi, Since last upgrade on Friday, kodi crashes right at startup (segfault). I tried with a brand new profile too, without any success. Unfortunately, neither the stack trace nor the debug log helped me pi

Bug#1099520: [Pkg-auth-maintainers] Bug#1099520: yubikey-manager-qt: ImportError: cannot import name '_PrepareUploadFailed' from 'ykman.otp' - Qt application is EOL and uses outdated ykman API

2025-03-17 Thread Florian Schlichting
Hi Sébastien, On Sun, Mar 16, 2025 at 04:45:05PM +0100, Sébastien Noel wrote: > Please find in attachment a patch that you can drop in the debian/patches/ > directory to fix compatibility with ykman 5.5 thank you for working on this! > Please don't remove yubikey-manager-qt even if it's upstream

Bug#1100640: Acknowledgement (database corrupted somehow)

2025-03-17 Thread Harald Dunkel
Still weird. Sample session below. Using reprepro version 5.4.6+really5.3.2-1, just to show: dpkg@tweety:/local/home/dpkg$ reprepro list sid | grep iproute2 sid|main|amd64: iproute2-dbgsym|6.13.0-1.1 6.13.0-1.1 sid|main|amd64: iproute2|6.13.0-1.1 6.13.0-1.1 sid|main|source: iproute2|6.13.0-1.1

Bug#1100604: PANIC: assert failed at source3/smbd/smb2_oplock.c(156): sconn->oplocks.exclusive_open>=0

2025-03-17 Thread Etienne Dechamps
Some additional information: Excerpt from my smb.conf: unix extensions = no wide links = yes kernel oplocks = yes use sendfile = yes ea support = no Notably, `kernel oplocks = yes` is not the default, which may explain why only some people appear to be affected by this issue. Running Debian ker

Bug#1100704: libtree-sitter0.22: trying to overwrite .../libtree-sitter.so.0.22, which is also in package libtree-sitter0 (0.22.6-4)

2025-03-17 Thread Vincent Lefevre
On 2025-03-17 14:56:42 -0400, James McCoy wrote: > Then maybe aptitude isn't presenting information clearly. You have > experimental enabled in your sources and that version is only available > in experimental: I track unstable. aptitude is supposed to give a warning when upgrading a package to ex

Bug#1085947: sphinx-book-theme: generate_nav_html no longer exists

2025-03-17 Thread Christian BAYLE
I confirm the version 1.1.4 is fixing this bug for both doxysphinx and sphinx-external-toc Please upload to trixie/unstable Cheers Christian

Bug#1100566: marked as done (libxslt: CVE-2025-24855: Use-after-free due to xsltEvalXPathStringNs leaking xpathCtxt->node)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 14:53:21 + with message-id and subject line Bug#1100566: fixed in libxslt 1.1.35-1.2 has caused the Debian Bug report #1100566, regarding libxslt: CVE-2025-24855: Use-after-free due to xsltEvalXPathStringNs leaking xpathCtxt->node to be marked as done. Thi

Bug#1100194: marked as done (astroplan: FTBFS: ModuleNotFoundError: No module named 'pytz')

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 19:34:19 + with message-id and subject line Bug#1100194: fixed in astroplan 0.10.1-2 has caused the Debian Bug report #1100194, regarding astroplan: FTBFS: ModuleNotFoundError: No module named 'pytz' to be marked as done. This means that you claim that the

Bug#1099988: marked as done (cantor: FTBFS on i386: Target "cantorlibs" links to: Poppler::Qt6 but the target was not found)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 20:27:50 +0100 with message-id <5869837.DvuYhMxLoT@treadstone-71> and subject line has caused the Debian Bug report #1099988, regarding cantor: FTBFS on i386: Target "cantorlibs" links to: Poppler::Qt6 but the target was not found to be marked as done. This me

Bug#1099935: dnspython: autopkgtest regression on s390x: bad request

2025-03-17 Thread Colin Watson
Control: reassign -1 python3-pylsqpack 0.3.18-1 Control: affects -1 src:dnspython On Mon, Mar 17, 2025 at 05:03:56PM +, Colin Watson wrote: On Sun, Mar 16, 2025 at 12:12:08PM +, Pranav P wrote: I am still continuing my search on the issue. It seems that the issue is rising from pylsqpac

Processed: PANIC: assert failed at source3/smbd/smb2_oplock.c(156): sconn->oplocks.exclusive_open>=0

2025-03-17 Thread Debian Bug Tracking System
Processing control commands: > severity -1 grave Bug #1100604 [samba] PANIC: assert failed at source3/smbd/smb2_oplock.c(156): sconn->oplocks.exclusive_open>=0 Severity set to 'grave' from 'important' > found -1 2:4.22.0+dfsg-1+b1 Bug #1100604 [samba] PANIC: assert failed at source3/smbd/smb2_opl

Bug#1099419: marked as done (gimp 3.0 crash on startup due to incorrect dependency on librsvg2)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 19:05:46 + with message-id and subject line Bug#1099419: fixed in gimp 3.0.0-2 has caused the Debian Bug report #1099419, regarding gimp 3.0 crash on startup due to incorrect dependency on librsvg2 to be marked as done. This means that you claim that the pr

Bug#1100558: marked as done (php8.2: FTBFS: error: ‘is_convertible_v’ is not a member of ‘std’)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 18:22:53 + with message-id and subject line Bug#1100561: Removed package(s) from unstable has caused the Debian Bug report #1100558, regarding php8.2: FTBFS: error: ‘is_convertible_v’ is not a member of ‘std’ to be marked as done. This means that you claim

Bug#1100704: libtree-sitter0.22: trying to overwrite .../libtree-sitter.so.0.22, which is also in package libtree-sitter0 (0.22.6-4)

2025-03-17 Thread James McCoy
On Mon, Mar 17, 2025 at 07:50:43PM +0100, Vincent Lefevre wrote: On 2025-03-17 14:35:47 -0400, James McCoy wrote: Not sure why you're upgrading to the version from experimental, when there's a newer version in unstable that already fixed this problem. No, experimental was not involved. And the

Bug#1100704: libtree-sitter0.22: trying to overwrite .../libtree-sitter.so.0.22, which is also in package libtree-sitter0 (0.22.6-4)

2025-03-17 Thread Vincent Lefevre
On 2025-03-17 14:35:47 -0400, James McCoy wrote: > Not sure why you're upgrading to the version from experimental, when > there's a newer version in unstable that already fixed this problem. No, experimental was not involved. And the new version was not available yet, since I followed what aptitud

Bug#1099419: marked as pending in gimp

2025-03-17 Thread Jeremy Bícha
Control: tag -1 pending Hello, Bug #1099419 in gimp 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/gnome-team/gimp/-/commit/33d1efc8d8515e3684c2d160f0bca2a0215

Processed: Bug#1099419 marked as pending in gimp

2025-03-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1099419 [gimp] gimp 3.0 crash on startup due to incorrect dependency on librsvg2 Added tag(s) pending. -- 1099419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1100704: marked as done (libtree-sitter0.22: trying to overwrite .../libtree-sitter.so.0.22, which is also in package libtree-sitter0 (0.22.6-4))

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 14:35:47 -0400 with message-id and subject line Re: Bug#1100704: libtree-sitter0.22: trying to overwrite .../libtree-sitter.so.0.22, which is also in package libtree-sitter0 (0.22.6-4) has caused the Debian Bug report #1100704, regarding libtree-sitter0.22: tr

Bug#961834: marked as done (clearlooks-phenix-theme: Theme look distorted possibly due to recent GTK3 upgrade)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 18:20:22 + with message-id and subject line Bug#1099984: Removed package(s) from unstable has caused the Debian Bug report #961834, regarding clearlooks-phenix-theme: Theme look distorted possibly due to recent GTK3 upgrade to be marked as done. This means

Bug#1088400: marked as done (libept: do not ship in trixie [ftbfs + RoM])

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 18:21:00 + with message-id and subject line Bug#1100178: Removed package(s) from unstable has caused the Debian Bug report #1088400, regarding libept: do not ship in trixie [ftbfs + RoM] to be marked as done. This means that you claim that the problem has b

Bug#1067173: marked as done (clearlooks-phenix-theme: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 18:20:22 + with message-id and subject line Bug#1099984: Removed package(s) from unstable has caused the Debian Bug report #1067173, regarding clearlooks-phenix-theme: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf to be marked

Bug#1094513: marked as done (ruby-omniauth-ultraauth: FTBFS: ERROR: Test "ruby3.3" failed.)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 18:12:44 + with message-id and subject line Bug#1100518: Removed package(s) from unstable has caused the Debian Bug report #1094513, regarding ruby-omniauth-ultraauth: FTBFS: ERROR: Test "ruby3.3" failed. to be marked as done. This means that you claim that

Bug#1053637: marked as done (rust-arrayvec-0.5: Obsolete version of rust-arrayvec)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 18:13:41 + with message-id and subject line Bug#1100528: Removed package(s) from unstable has caused the Debian Bug report #1053637, regarding rust-arrayvec-0.5: Obsolete version of rust-arrayvec to be marked as done. This means that you claim that the prob

Processed: Re: Bug#1100544: reopening, c-t-b-mipsen is still unfixed

2025-03-17 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 cross-toolchain-base-mipsen Bug #1100544 [libc6-dev-i386] glibc adds some conflicts letting gcc-14-cross ftbfs Bug reassigned from package 'libc6-dev-i386' to 'cross-toolchain-base-mipsen'. Ignoring request to alter found versions of bug #1100544 to the

Bug#1100544: reopening, c-t-b-mipsen is still unfixed

2025-03-17 Thread Aurelien Jarno
control: reassign -1 cross-toolchain-base-mipsen On 2025-03-17 02:55, Matthias Klose wrote: Control: reopen -1 reopening, c-t-b-mipsen is still unfixed. I'm fine to drop the intermediate patch in c-t-b and c-t-b-ports. c-t-b-mipsen needs an upload anyway. Given the toolchain is frozen alrea

Bug#1089675: marked as done (inkscape 1.2.2.6 contains file in another package without declaring conflict)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 17:39:32 + with message-id and subject line Bug#1089675: fixed in inkscape 1.4-6 has caused the Debian Bug report #1089675, regarding inkscape 1.2.2.6 contains file in another package without declaring conflict to be marked as done. This means that you cla

Processed: [bts-link] source package src:obs-advanced-scene-switcher

2025-03-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package > src:obs-advanced-scene-switcher > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l.

Bug#1073348: marked as done (inkscape: FTBFS: uri.cpp:86:9: error: ‘xmlFree’ was not declared in this scope; did you mean ‘xmlFreeURI’?)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 13:18:09 -0400 with message-id and subject line Re: inkscape: FTBFS: uri.cpp:86:9: error: ‘xmlFree’ was not declared in this scope; did you mean ‘xmlFreeURI’? has caused the Debian Bug report #1073348, regarding inkscape: FTBFS: uri.cpp:86:9: error: ‘xmlFree’

Processed: Bug#1089675 marked as pending in inkscape

2025-03-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1089675 [inkscape] inkscape 1.2.2.6 contains file in another package without declaring conflict Added tag(s) pending. -- 1089675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089675 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1089675: marked as pending in inkscape

2025-03-17 Thread Jeremy Bícha
Control: tag -1 pending Hello, Bug #1089675 in inkscape 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/multimedia-team/inkscape/-/commit/aad609a7d33e942f32f172

Bug#1086464: marked as done (mate-desktop FTBFS on 32-bit with 64-bit time_t with gcc 14)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 17:08:35 + with message-id and subject line Bug#1086464: fixed in mate-desktop 1.26.2-1.2 has caused the Debian Bug report #1086464, regarding mate-desktop FTBFS on 32-bit with 64-bit time_t with gcc 14 to be marked as done. This means that you claim that t

Bug#1099935: dnspython: autopkgtest regression on s390x: bad request

2025-03-17 Thread Colin Watson
On Sun, Mar 16, 2025 at 12:12:08PM +, Pranav P wrote: I am still continuing my search on the issue. It seems that the issue is rising from pylsqpack. When the value field in the packet header for HTTP3 GET request contains long strings there are problems while encoding (Only in s390x). Due to

Bug#1053245: marked as done (fluidsynth: Fluidsynth starts at boot and blocks the sound device, no obvious way to disable it)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 16:51:21 + with message-id and subject line Bug#1053245: fixed in fluidsynth 2.4.4+dfsg-1 has caused the Debian Bug report #1053245, regarding fluidsynth: Fluidsynth starts at boot and blocks the sound device, no obvious way to disable it to be marked as do

Processed: Re: Bug#1089675: inkscape 1.2.2.6 contains file in another package without declaring conflict

2025-03-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was hel...@subdivi.de). > usertags 1089675 + fileconflict There were no usertags set. Usertags are now: fileconflict. > severity 1089675 serious Bug #1089675 [inkscape] in

Bug#1099838: bacon has an undeclared file conflict on /usr/bin/bacon

2025-03-17 Thread Antonio Terceiro
On Sun, Mar 16, 2025 at 05:30:21PM +, Blair Noctis wrote: > On 14/03/2025 15:34, Antonio Terceiro wrote: > > On Thu, Mar 13, 2025 at 02:49:31PM +, Blair Noctis wrote: > > > Thus I suggest: > > > > > > 1. Update d/control of ruby-faraday, ruby-rack, ruby-em-spec, > > > ruby-temple to remove

Bug#1100704: libtree-sitter0.22: trying to overwrite .../libtree-sitter.so.0.22, which is also in package libtree-sitter0 (0.22.6-4)

2025-03-17 Thread Vincent Lefevre
Package: libtree-sitter0.22 Version: 0.22.6-5 Severity: serious When upgrading: [...] Preparing to unpack .../libtree-sitter0.22_0.22.6-5_amd64.deb ... Unpacking libtree-sitter0.22:amd64 (0.22.6-5) ... dpkg: error processing archive /var/cache/apt/archives/libtree-sitter0.22_0.22.6-5_amd64.deb (

Processed: NMU: mate-desktop FTBFS on 32-bit with 64-bit time_t with gcc 14

2025-03-17 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1086464 [src:mate-desktop] mate-desktop FTBFS on 32-bit with 64-bit time_t with gcc 14 Added tag(s) patch. -- 1086464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086464 Debian Bug Tracking System Contact ow...@bugs.debian.org with proble

Bug#1086464: NMU: mate-desktop FTBFS on 32-bit with 64-bit time_t with gcc 14

2025-03-17 Thread Bastian Germann
Control: tags -1 patch I am uploading a NMU to fix this. Please find the debdiff attached. diff -Nru mate-desktop-1.26.2/debian/changelog mate-desktop-1.26.2/debian/changelog --- mate-desktop-1.26.2/debian/changelog2024-02-29 13:11:12.0 +0100 +++ mate-desktop-1.26.2/debian/change

Bug#1100678: marked as done (crack and crack-common have an undeclared file conflict on /usr/share/Crack/conf)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 16:20:23 + with message-id and subject line Bug#1100678: fixed in crack 5.0a-17 has caused the Debian Bug report #1100678, regarding crack and crack-common have an undeclared file conflict on /usr/share/Crack/conf to be marked as done. This means that you

Bug#1100548: marked as done (bellesip-data/trixie fails to upgrade from libbellesip1/bookworm)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 16:20:12 + with message-id and subject line Bug#1100548: fixed in belle-sip 5.3.105+dfsg-4 has caused the Debian Bug report #1100548, regarding bellesip-data/trixie fails to upgrade from libbellesip1/bookworm to be marked as done. This means that you claim

Bug#1069959: marked as done (libcbor FTBFS on hppa and mips to due different NaN encoding)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 17:22:06 +0100 with message-id and subject line libcbor FTBFS on hppa and mips to due different NaN encoding has caused the Debian Bug report #1069959, regarding libcbor FTBFS on hppa and mips to due different NaN encoding to be marked as done. This means that

Bug#1077340: marked as done (libcbor fails to build on mips64el: testsuite failures)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 17:22:06 +0100 with message-id and subject line libcbor FTBFS on hppa and mips to due different NaN encoding has caused the Debian Bug report #1069959, regarding libcbor fails to build on mips64el: testsuite failures to be marked as done. This means that you c

Bug#1095399: marked as done (vitables: FTBFS: E AttributeError: module 'numpy' has no attribute 'VisibleDeprecationWarning')

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 15:33:51 + with message-id and subject line Bug#1095399: fixed in vitables 3.1.0-1 has caused the Debian Bug report #1095399, regarding vitables: FTBFS: E AttributeError: module 'numpy' has no attribute 'VisibleDeprecationWarning' to be marked as done. T

Bug#1100143: marked as done (belcard-data has an undeclared file conflict with libbelcard1)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 15:49:32 + with message-id and subject line Bug#1100143: fixed in belcard 5.3.105-3 has caused the Debian Bug report #1100143, regarding belcard-data has an undeclared file conflict with libbelcard1 to be marked as done. This means that you claim that the p

Bug#1100379: libopentelemetry-proto-dev and opentelemetry-cpp-dev fail to coinstall

2025-03-17 Thread Santiago Ruano Rincón
(Adding Thomas to the loop) El 13/03/25 a las 08:13, Helmut Grohne escribió: > Package: libopentelemetry-proto-dev,opentelemetry-cpp-dev > Severity: serious > Tags: trixie sid > User: debian...@lists.debian.org > Usertags: fileconflict > > The packages libopentelemetry-proto-dev and opentelemetry

Bug#1099591: marked as done (linux-image-6.12.12-amd64: crash in netfs module when copying (large) directory from smb share)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 08:00:11 + with message-id and subject line Bug#1098698: fixed in linux 6.12.19-1 has caused the Debian Bug report #1098698, regarding linux-image-6.12.12-amd64: crash in netfs module when copying (large) directory from smb share to be marked as done. This

Bug#1100565: marked as done (libxslt: CVE-2024-55549: Use-after-free related to excluded result prefixes)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 14:53:21 + with message-id and subject line Bug#1100565: fixed in libxslt 1.1.35-1.2 has caused the Debian Bug report #1100565, regarding libxslt: CVE-2024-55549: Use-after-free related to excluded result prefixes to be marked as done. This means that you

Processed: Re: screen: hardcopy and screen-exchange are insecure by default

2025-03-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1100699 security Bug #1100699 [screen] screen: hardcopy and screen-exchange are insecure by default Added tag(s) security. > End of message, stopping processing here. Please contact me if you need assistance. -- 1100699: https://bugs.debia

Bug#1095344: marked as done (gimp-help: FTBFS: dh_autoreconf: error: ./autogen.sh returned exit code 1)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 14:51:44 + with message-id and subject line Bug#1095344: fixed in gimp-help 3.0.0-1 has caused the Debian Bug report #1095344, regarding gimp-help: FTBFS: dh_autoreconf: error: ./autogen.sh returned exit code 1 to be marked as done. This means that you cla

Bug#1093720: marked as done (gimp-help: doesn't work with gimp 3)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 14:51:44 + with message-id and subject line Bug#1093720: fixed in gimp-help 3.0.0-1 has caused the Debian Bug report #1093720, regarding gimp-help: doesn't work with gimp 3 to be marked as done. This means that you claim that the problem has been dealt with

Bug#1098521: apparmor 4.x breaks systemd user namespacing in lxc containers

2025-03-17 Thread Mathias Gibbens
In my testing I needed to make one additional change to the base lxc apparmor profile, and I've replied to the upstream bug report asking for feedback, since I'm not an apparmor expert. Once I get an ACK on that I'll update the lxc package for Debian. Mathias signature.asc Description: This is

Bug#1100699: screen: hardcopy and screen-exchange are insecure by default

2025-03-17 Thread Vincent Lefevre
Package: screen Version: 4.9.1-1 Severity: grave Justification: user security hole + possible data loss via a symlink attack The hardcopy (C-a h) in screen works in the following way: │ hardcopydir directory │ │ Defines a directory where hardcopy files will be placed. If unset, │ hardcopys are d

Processed: Bug#1100678 marked as pending in crack

2025-03-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1100678 [crack,crack-common] crack and crack-common have an undeclared file conflict on /usr/share/Crack/conf Added tag(s) pending. -- 1100678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100678 Debian Bug Tracking System Contact ow...@b

Bug#1100678: marked as pending in crack

2025-03-17 Thread Sven Geuer
Control: tag -1 pending Hello, Bug #1100678 in crack 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/pkg-security-team/crack/-/commit/0dd07189c69541142bb532571e

Processed: tagging 1096133

2025-03-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1096133 + fixed Bug #1096133 {Done: Matheus Polkorny } [src:visp] visp: FTBFS on arm64: /build/reproducible-path/visp-3.6.0/modules/tracker/mbt/src/depth/vpMbtFaceDepthDense.cpp:521:34: error: no match for ‘operator*’ (operand types are ‘c

Bug#1093197: wine: FTBFS on arm*

2025-03-17 Thread Martin Storsjö
On Thu, 16 Jan 2025, Paul Gevers wrote: The latest version of wine failed to build on the three arm architectures. It seems the root cause is different though depending on the architecture. The root cause is actually the same in all of them; Wine requires Clang for building on ARM (initially

Bug#1096208: marked as done (dipy: fails tests with scipy 1.15)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 13:20:30 + with message-id and subject line Bug#1096208: fixed in dipy 1.11.0-1 has caused the Debian Bug report #1096208, regarding dipy: fails tests with scipy 1.15 to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#1099655: initramfs-tools 146 generates incorrect initramfs : does not boot, does not find root fs

2025-03-17 Thread Ben Hutchings
Control: tag -1 moreinfo unreproducible On Sat, 2025-03-08 at 12:29 +0100, Eric Valette wrote: > On Fri, 7 Mar 2025 20:43:08 +0100 Marc Haber > wrote: > > On Fri, Mar 07, 2025 at 05:44:00PM +0100, Eric Valette wrote: > > > CONFIG_MODULE_DECOMPRESS=y > > So the culprit is there. It is not set i

Bug#1100695: wine: Wine hangs on startup on arm64

2025-03-17 Thread Martin Storsjö
Package: wine Version: 9.0~repack-7 Severity: grave Justification: renders package unusable X-Debbugs-Cc: debian-...@lists.debian.org, mar...@martin.st User: debian-...@lists.debian.org Usertags: arm64 Dear Maintainer, When starting Wine (9.0~repack-7) on Debian Trixie, e.g. with a simple command

Bug#1100679: [Debian-lego-team] Bug#1100679: brickos-doc/trixie misses Breaks+Replaces for brickos/bookworm

2025-03-17 Thread Nicolas Schodet
* Helmut Grohne [2025-03-17 08:00]: > brickos-doc/trixie takes over the files > - /usr/share/doc/brickos/NEWS.gz > - /usr/share/doc/brickos/README > - /usr/share/doc/brickos/README.usb > - /usr/share/doc/brickos/VERSION > from brickos/bookworm. It therefore must declare Breaks and Replaces. A

Bug#1100640: database corrupted somehow

2025-03-17 Thread Bastian Germann
Please switch to experimental reprepro if you experience this bug.

Bug#1100640: database corrupted somehow

2025-03-17 Thread Andrew Sayers
Package: reprepro Version: 5.4.6+really5.3.2-1 Followup-For: Bug #1100640 I get the same thing: BDB1015 references: duplicate sort specified but not supported in database db_open(./db/references.db:references)[22]: Invalid argument There have been errors! This is new since I upgraded yesterday f

Bug#1100221: marked as done (gnome-connections: FTBFS: error: implicit declaration of function 'freerdp_shall_disconnect')

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 07:54:34 -0400 with message-id and subject line Re: Bug#1100221: gnome-connections: FTBFS: error: implicit declaration of function 'freerdp_shall_disconnect' has caused the Debian Bug report #1100221, regarding gnome-connections: FTBFS: error: implicit declara

Bug#1100640: marked as done (database corrupted somehow)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 11:55:58 + with message-id and subject line Bug#1100640: fixed in reprepro 5.4.7-1 has caused the Debian Bug report #1100640, regarding database corrupted somehow to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1098558: golang-github-lucas-clemente-quic-go: FTBFS: FAIL github.com/quic-go/quic-go/internal/handshake [build failed]

2025-03-17 Thread Jérémy Lal
Source: golang-github-lucas-clemente-quic-go Version: 0.46.0-2 Followup-For: Bug #1098558 Control: tags -1 ftbfs Upgrading to version 0.50.0 fixes that test. However, ./integrationtests/tools/proxy/proxy_test.go tests fail with that version, in a systematic way. Should I skip that test and upgr

Bug#1100663: marked as done (ns3: Not built on buildd: arch all binaries uploaded by mquinson, a new source-only upload is needed to allow migration)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 11:26:29 + with message-id and subject line Bug#1100663: fixed in ns3 3.43-2 has caused the Debian Bug report #1100663, regarding ns3: Not built on buildd: arch all binaries uploaded by mquinson, a new source-only upload is needed to allow migration to be m

Bug#1100688: pytorch-cuda: rebuild for cpp-httplib transition

2025-03-17 Thread Emilio Pozuelo Monfort
Package: pytorch-cuda Version: 2.6.0+dfsg-5 Severity: serious Hi, Your package is part of the cpp-httplib transition, and needs a manual rebuild against the new libcpp-httplib0.18 package. Cheers, Emilio

Processed: Re: vuos FTBFS with fuse3/3.17.1

2025-03-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1098735 ftbfs Bug #1098735 [src:vuos] vuos FTBFS with fuse3/3.17.1 Ignoring request to alter tags of bug #1098735 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1098735: https

Processed: your mail

2025-03-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 903272 important Bug #903272 [dl10n] dl10n: probably needs a dependency on liblocale-codes-perl Severity set to 'important' from 'critical' > severity 805378 important Bug #805378 [dl10n] dl10n-check: Can't locate Debian/Pkg/DebSrc.pm in

Bug#1093881: marked as done (mysql-connector-python: CVE-2025-21548)

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 10:50:33 + with message-id and subject line Bug#1093881: fixed in mysql-connector-python 9.2.0-1 has caused the Debian Bug report #1093881, regarding mysql-connector-python: CVE-2025-21548 to be marked as done. This means that you claim that the problem has

Processed: Re: golang-github-lucas-clemente-quic-go: FTBFS: FAIL github.com/quic-go/quic-go/internal/handshake [build failed]

2025-03-17 Thread Debian Bug Tracking System
Processing control commands: > tags -1 ftbfs Bug #1098558 [src:golang-github-lucas-clemente-quic-go] golang-github-lucas-clemente-quic-go: FTBFS: FAIL github.com/quic-go/quic-go/internal/handshake [build failed] Ignoring request to alter tags of bug #1098558 to the same tags previously set -

Processed: Bug#1093881 marked as pending in mysql-connector-python

2025-03-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1093881 [src:mysql-connector-python] mysql-connector-python: CVE-2025-21548 Added tag(s) pending. -- 1093881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093881 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1093881: marked as pending in mysql-connector-python

2025-03-17 Thread Colin Watson
Control: tag -1 pending Hello, Bug #1093881 in mysql-connector-python 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/python-team/packages/mysql-connector-pytho

Bug#1088041: marked as done (lavacli: FTBFS: E assert 'usage: lavac...te, update)n' == "usage: lavac..., 'update')n")

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 09:53:50 + with message-id and subject line Bug#1088041: fixed in lavacli 2.2.0-1 has caused the Debian Bug report #1088041, regarding lavacli: FTBFS: E assert 'usage: lavac...te, update)n' == "usage: lavac..., 'update')n" to be marked as done. This means

Bug#1096242: marked as done (golang-k8s-kube-openapi: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 k8s.io/kube-openapi/cmd/openapi-gen [...] k8s.io/kube-openapi/test/integration/t

2025-03-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Mar 2025 09:53:23 + with message-id and subject line Bug#1096242: fixed in golang-k8s-kube-openapi 0.0~git20241212.2c72e55-1 has caused the Debian Bug report #1096242, regarding golang-k8s-kube-openapi: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -

Bug#1075323: Uploaded NMU of nstreams to delayed=15

2025-03-17 Thread Andreas Tille
Control: tags -1 pending Thanks Hi Jörg, while I originally filed an ITS bug report it turned out that nobody from the Salvage team intended to add the own ID to the Uploaders field which is a requirement for the salvage process. So I moved the package to the Debian team on Salsa[1] and left all

Bug#1100678: crack and crack-common have an undeclared file conflict on /usr/share/Crack/conf

2025-03-17 Thread Helmut Grohne
Package: crack,crack-common Version: 5.0a-13 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict crack and crack-common both install /usr/share/Crack/conf. This does not presently seem to cause practical problems, because dpkg does not track file types. As both are installed

  1   2   >