Processed: closing 1089180

2025-01-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1089180 7.9.2-0.1 Bug #1089180 [src:guzzle] guzzle: Failing tests with PHP 8.4 Marked as fixed in versions guzzle/7.9.2-0.1. Bug #1089180 [src:guzzle] guzzle: Failing tests with PHP 8.4 Marked Bug as done > thanks Stopping processing here.

Processed: affects 1093826

2025-01-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1093826 src:lazygal Bug #1093826 [python3-pil] python3-pil: basic import fails Added indication that 1093826 affects src:lazygal > thanks Stopping processing here. Please contact me if you need assistance. -- 1093826: https://bugs.debian

Processed: why3 has an undeclared file conflict on /usr/lib/ocaml/why3

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + libwhy3-ocaml-dev why3-coq Bug #1093827 [why3] why3 has an undeclared file conflict on /usr/lib/ocaml/why3 Added indication that 1093827 affects libwhy3-ocaml-dev and why3-coq -- 1093827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093827 Debian

Bug#1089580: marked as done (visualvm: JVM crashes with StackOverflowError at startup)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Thu, 23 Jan 2025 06:36:46 + with message-id and subject line Bug#1089580: fixed in visualvm 2.1.10-1 has caused the Debian Bug report #1089580, regarding visualvm: JVM crashes with StackOverflowError at startup to be marked as done. This means that you claim that the proble

Bug#1093828: libllhttp9.2 has an undeclared file conflict

2025-01-22 Thread Helmut Grohne
Package: libllhttp9.2 Version: 9.2.1~7.2.3+dfsg1+~cs24.12.11-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libllhttp9.1 libllhttp9.2 has an undeclared file conflict. This may result in an unpack error from dpkg. The files * /usr/lib/x86_64-linu

Processed: libllhttp9.2 has an undeclared file conflict

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + libllhttp9.1 Bug #1093828 [libllhttp9.2] libllhttp9.2 has an undeclared file conflict Added indication that 1093828 affects libllhttp9.1 -- 1093828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093828 Debian Bug Tracking System Contact ow...@bugs

Bug#1093827: why3 has an undeclared file conflict on /usr/lib/ocaml/why3

2025-01-22 Thread Helmut Grohne
Package: why3 Version: 1.8.0-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libwhy3-ocaml-dev why3-coq why3 has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/ocaml/why3 is contained in the packages

Bug#1093826: python3-pil: basic import fails

2025-01-22 Thread Alexandre Rossi
Package: python3-pil Version: 11.1.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, The basic import that most use from PIL fails: $ python3 Python 3.13.1 (main, Jan 3 2025, 10:26:34) [GCC 14.2.0] on linux Type "help", "copyright", "credits" or "license" for more inf

Processed: reassign 1093821 to network-manager, reassign 1071498 to src:libquotient, fixed 1071498 in 0.8.2-1 ...

2025-01-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1093821 network-manager 1.50.1-1 Bug #1093821 [network-maager] Networking broken after suspend/resume on machine with multiple interfaces Warning: Unknown package 'network-maager' Bug reassigned from package 'network-maager' to 'network-

Bug#1091662: marked as done (ruby-mixlib-log: FTBFS with ruby3.3: ERROR: Test "ruby3.3" failed: NoMethodError:)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Thu, 23 Jan 2025 02:39:36 + with message-id and subject line Bug#1091662: fixed in ruby-mixlib-log 3.1.2-1 has caused the Debian Bug report #1091662, regarding ruby-mixlib-log: FTBFS with ruby3.3: ERROR: Test "ruby3.3" failed: NoMethodError: to be marked as done. This

Bug#1084968: marked as done (libunwind8: amd64 and i386 versions are out of sync)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Thu, 23 Jan 2025 00:22:15 + with message-id and subject line Re: Bug#1082282: libunwind: FTBFS on i386: passing argument 1 of '_Ux86_sigreturn' from incompatible pointer type has caused the Debian Bug report #1082282, regarding libunwind8: amd64 and i386 versions are out of

Bug#1090386: marked as done (cannot install wine32:i386: Depends: libunwind8:i386 but it is not going to be installed)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Thu, 23 Jan 2025 00:22:15 + with message-id and subject line Re: Bug#1082282: libunwind: FTBFS on i386: passing argument 1 of '_Ux86_sigreturn' from incompatible pointer type has caused the Debian Bug report #1082282, regarding cannot install wine32:i386: Depends: libunwind

Bug#1082282: marked as done (libunwind: FTBFS on i386: passing argument 1 of '_Ux86_sigreturn' from incompatible pointer type)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Thu, 23 Jan 2025 00:22:15 + with message-id and subject line Re: Bug#1082282: libunwind: FTBFS on i386: passing argument 1 of '_Ux86_sigreturn' from incompatible pointer type has caused the Debian Bug report #1082282, regarding libunwind: FTBFS on i386: passing argument 1 o

Bug#1093654: kmail: After upgrade, all emails are missing their date

2025-01-22 Thread Soren Stoutner
Control: severity -1 normal On Wednesday, January 22, 2025 2:51:27 PM MST Patrick Franz wrote: > It could be, but I have to admit that I don't know the inner workings of > kmail in that regard. It seems though thAT you're not the only one > suffering from this bug: https://bugs.kde.org/show_bug.cg

Processed: Re: Bug#1093654: kmail: After upgrade, all emails are missing their date

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #1093654 [kmail] kmail: After upgrade, all emails are missing their date Severity set to 'normal' from 'grave' -- 1093654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093654 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1092749: marked as done (Autopkgtests fail with Python 3.13: ipdSummary output changed)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jan 2025 23:50:23 + with message-id and subject line Bug#1092749: fixed in kineticstools 0.6.1+git20220223.1326a4d+dfsg-5 has caused the Debian Bug report #1092749, regarding Autopkgtests fail with Python 3.13: ipdSummary output changed to be marked as done. This m

Bug#1093698: marked as done (thrift: Build-Depends on php-codesniffer that is unfit for release)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jan 2025 23:53:27 + with message-id and subject line Bug#1093698: fixed in thrift 0.19.0-3 has caused the Debian Bug report #1093698, regarding thrift: Build-Depends on php-codesniffer that is unfit for release to be marked as done. This means that you claim that th

Bug#1087611: marked as done (FTBFS on ppc64el: FAIL: TestNoHangDuringStopFromClientNoDataSendDuringAcceptLoop)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jan 2025 23:53:27 + with message-id and subject line Bug#1087611: fixed in thrift 0.19.0-3 has caused the Debian Bug report #1087611, regarding FTBFS on ppc64el: FAIL: TestNoHangDuringStopFromClientNoDataSendDuringAcceptLoop to be marked as done. This means that yo

Bug#1092063: marked as done (kdevelop-python ftbfs with Python 3.13 as the default)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jan 2025 23:50:05 + with message-id and subject line Bug#1092063: fixed in kdevelop-python 24.12.1-1 has caused the Debian Bug report #1092063, regarding kdevelop-python ftbfs with Python 3.13 as the default to be marked as done. This means that you claim that the p

Processed: yosys: Patch

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1093368 [src:yosys] yosys: FTBFS: LaTeX error Added tag(s) patch. -- 1093368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1093368: yosys: Patch

2025-01-22 Thread Hilmar Preusse
Source: yosys Followup-For: Bug #1093368 Control: tags -1 + patch Dear Maintainer, the problematic code is in PRESENTATION_ExAdv.tex \hfil\begin{tikzpicture} \node at (1,-1.7) {\begin{lstlisting}[linewidth=5.5cm, frame=single, basicstyle=\ttfamily\fontsize{8pt}{10pt}\selectfont, langua ge=ys]

Bug#1092749: marked as pending in kineticstools

2025-01-22 Thread Emmanuel Arias
Control: tag -1 pending Hello, Bug #1092749 in kineticstools 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/med-team/kineticstools/-/commit/7fadeeada4bd5a6070c

Processed: Bug#1092749 marked as pending in kineticstools

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1092749 [src:kineticstools] Autopkgtests fail with Python 3.13: ipdSummary output changed Added tag(s) pending. -- 1092749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092749 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: Bug#1092749 marked as pending in kineticstools

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1092749 [src:kineticstools] Autopkgtests fail with Python 3.13: ipdSummary output changed Ignoring request to alter tags of bug #1092749 to the same tags previously set -- 1092749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092749 Debia

Bug#1093734: nfs-kernel-server: fails to complete setup during upgrade (stuck while restarting nfs-kernel-server.service)

2025-01-22 Thread Francesco Poli
On Thu, 23 Jan 2025 00:02:37 +0100 Francesco Poli wrote: [...] > Hello Salvatore, > thanks for following up. [...] By the way, I am also experiencing a huge performance hit on the I/O through the NFS shares. Please let me explain. On the host where the NFS server runs (let's call it "$server"),

Bug#1092749: marked as pending in kineticstools

2025-01-22 Thread Emmanuel Arias
Control: tag -1 pending Hello, Bug #1092749 in kineticstools 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/med-team/kineticstools/-/commit/7fadeeada4bd5a6070c

Bug#1093734: nfs-kernel-server: fails to complete setup during upgrade (stuck while restarting nfs-kernel-server.service)

2025-01-22 Thread Francesco Poli
On Wed, 22 Jan 2025 09:56:26 +0100 Salvatore Bonaccorso wrote: [...] > So I'm not able to reproduce this on a current Debian unstable system > mimicking the upgrade. *But* it is possible we have some races > somehwere as recently discussed at our regular kernel team meeting. > > We need first to

Bug#1038839: ganeti-instance-debootstrap: transition from /etc/timezone to /etc/localtime

2025-01-22 Thread Sascha Lucas
Hi, upstream[1] has released version 0.17[2] where all references to /etc/timezone should be removed. How can we further support re-inclusion in Testing/Trixie? Thanks, Sascha. [1] https://github.com/ganeti/instance-debootstrap [2] https://github.com/ganeti/instance-debootstrap/releases/tag/v0.

Bug#981937: dh-sysuser: Reduce negative impact and assess overall utility

2025-01-22 Thread Andrew Bower
Hi everyone, On Wed, Jul 17, 2024 at 12:06:43PM +0100, Luca Boccassi wrote: > Having competing packaging APIs is confusing and detrimental to the > project. The standard interface the project has adopted for declarative > user/group creation is dh_installsysusers provided by debhelper. Having > a

Bug#1061689: marked as done (kdevelop512-libs: identified for time_t transition but no ABI in shlibs)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jan 2025 23:35:01 +0100 with message-id <7763240.EvYhyI6sBW@grummly> and subject line has caused the Debian Bug report #1061689, regarding kdevelop512-libs: identified for time_t transition but no ABI in shlibs to be marked as done. This means that you claim that the p

Bug#1061689: (no subject)

2025-01-22 Thread Aurélien COUDERC
control: fixed -1 4:24.12.0-1 With the Qt6 port shipped in 4:24.12.0-1 all the libraries got a soname bump so I’m closing this bug. Thanks, -- Aurélien

Bug#1093640: marked as done (golang-github-google-certificate-transparency: Missing B-D/D causing FTBFS)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jan 2025 22:23:07 + with message-id and subject line Bug#1093640: fixed in sigstore-go 0.6.2-3 has caused the Debian Bug report #1093640, regarding golang-github-google-certificate-transparency: Missing B-D/D causing FTBFS to be marked as done. This means that you

Processed: RM: kjsembed -- RoQA; Obsolete

2025-01-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 1091224 -1 Bug #1091224 [src:kjsembed] RM: kjsembed -- RoQA; Obsolete Bug 1091224 cloned as bug 1093814 > severity -1 normal Bug #1093814 [src:kjsembed] RM: kjsembed -- RoQA; Obsolete Severity set to 'normal' from 'serious' > reassign -1 ftp

Bug#1082284: marked as done (libunwind: FTBFS on arm64: expected 'unw_tdep_context_t *' but argument is of type 'ucontext_t *')

2025-01-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jan 2025 21:56:37 + with message-id and subject line Bug#1082284: fixed in libunwind 1.8.1-0.1 has caused the Debian Bug report #1082284, regarding libunwind: FTBFS on arm64: expected 'unw_tdep_context_t *' but argument is of type 'ucontext_t *' to be marked as done

Processed: Bug#1093640 marked as pending in sigstore-go

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1093640 [src:golang-github-google-certificate-transparency] golang-github-google-certificate-transparency: Missing B-D/D causing FTBFS Added tag(s) pending. -- 1093640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093640 Debian Bug Tracki

Bug#1093640: marked as pending in sigstore-go

2025-01-22 Thread Simon Josefsson
Control: tag -1 pending Hello, Bug #1093640 in sigstore-go 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/go-team/packages/sigstore-go/-/commit/2ec12dceb0d5b9f

Bug#1082659: marked as done (libunwind8: 1.7 regression: Xvfb segfaults on armhf)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jan 2025 21:56:37 + with message-id and subject line Bug#1082659: fixed in libunwind 1.8.1-0.1 has caused the Debian Bug report #1082659, regarding libunwind8: 1.7 regression: Xvfb segfaults on armhf to be marked as done. This means that you claim that the problem h

Bug#1091302: marked as done (libunwind does not produce stack trace information on armhf)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jan 2025 21:56:37 + with message-id and subject line Bug#1091302: fixed in libunwind 1.8.1-0.1 has caused the Debian Bug report #1091302, regarding libunwind does not produce stack trace information on armhf to be marked as done. This means that you claim that the p

Bug#1093278: paraview needs a stricter python dependency

2025-01-22 Thread Adrian Bunk
On Sun, Jan 19, 2025 at 03:23:50PM +0100, Drew Parsons wrote: > On 2025-01-19 14:44, Colin Watson wrote: > > > > You can achieve that with: > > PY3VERS=$(PY3DEF) > > +PY3RANGE=$(shell echo $(PY3DEF) | awk 'BEGIN { FS="." }; { print $$1 > > "." $$2 "-" $$1 "." $$2 + 1 }') > > > > + dh_python3 -

Bug#1093654: kmail: After upgrade, all emails are missing their date

2025-01-22 Thread Patrick Franz
Hej Jacob, Am Mittwoch, 22. Januar 2025, 13:31:21 MEZ schrieb Jacob Kanev: > Hi Patrick, thanks for your reply! > > On Tuesday 21 January 2025 18:45:47 CET Patrick Franz wrote: > > Hej Jacob, > > [---] > > Have you tried changing the view/design of both your list view and > > your message header

Bug#1080122: marked as done (powerline: FTBFS: ModuleNotFoundError: No module named 'zsh')

2025-01-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jan 2025 21:20:14 + with message-id and subject line Bug#1080122: fixed in powerline 2.8.4-1 has caused the Debian Bug report #1080122, regarding powerline: FTBFS: ModuleNotFoundError: No module named 'zsh' to be marked as done. This means that you claim that the pr

Processed: Re: Bug#1087970: pep8: old version of pycodestyle

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > affects 1087970 + src:pep8 Bug #1087970 [ftp.debian.org] RM: pep8 -- ROM; was renamed pycodestyle many years ago Added indication that 1087970 affects src:pep8 > affects 1087970 - flake8-polyfill Bug #1087970 [ftp.debian.org] RM: pep8 -- ROM; was renamed pycodestyle

Bug#1093809: runsnakerun: runsnake fails to start

2025-01-22 Thread Sudip Mukherjee
Source: runsnakerun Version: 2.0.5-3 Severity: serious X-Debbugs-Cc: sudipm.mukher...@gmail.com Dear Maintainer, runsnake fails to execute and immediately crashes with the following trace: $ runsnake Traceback (most recent call last): File "/usr/bin/runsnake", line 33, in sys.exit(load_en

Bug#1093605: marked as done (patroni: autopkgtest failure with Python 3.13)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jan 2025 21:05:58 + with message-id and subject line Bug#1093605: fixed in patroni 4.0.4-5 has caused the Debian Bug report #1093605, regarding patroni: autopkgtest failure with Python 3.13 to be marked as done. This means that you claim that the problem has been de

Processed: notepadqq: Unnecessary Build-Depends: libqt5webkit5-dev

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > block 1069574 by -1 Bug #1069574 [libqt5webkit5] age-old and insecure webkit package 1069574 was blocked by: 929253 1074331 1091821 1093372 1093523 1093526 1093527 1093528 1093534 1093539 1093549 1093550 1093551 1093552 1093691 1093725 1093726 1093727 1093728 10937

Processed: libqtpas: Unnecessary Build-Depends: libqt5webkit5-dev

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > block 1069574 by -1 Bug #1069574 [libqt5webkit5] age-old and insecure webkit package 1069574 was blocked by: 929253 1074331 1091821 1093372 1093523 1093526 1093527 1093528 1093534 1093539 1093549 1093550 1093551 1093552 1093691 1093725 1093726 1093727 1093728 10937

Bug#1091024: dojo needs a rebuild against the new rhino

2025-01-22 Thread Adrien Nader
Hi, After some trial and error, I found out that if dojo is rebuilt, the tests pass. I don't know what changed in rhino and the upstream changelog for the new version is pretty long with lots of things specific to its API which I'm not familiar with. Anyway, a no-change rebuild should be enough.

Bug#1087970: pep8: old version of pycodestyle

2025-01-22 Thread Chris Hofstaedtler
Control: affects 1087970 + src:pep8 Control: affects 1087970 - flake8-polyfill On Tue, Jan 14, 2025 at 10:12:58PM +0100, Alexandre Detiste wrote: > I fixed more packages, filled two bugs and > will fill a third one to ask for removal of > python3-django-setuptest tomorrow. Current list: Checking

Processed: scribus: Unnecessary Build-Depends: libqt5webkit5-dev

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > block 1069574 by -1 Bug #1069574 [libqt5webkit5] age-old and insecure webkit package 1069574 was blocked by: 929253 1074331 1091821 1093372 1093523 1093526 1093527 1093528 1093534 1093539 1093549 1093550 1093551 1093552 1093691 1093725 1093726 1093727 1093728 10937

Processed: no longer affects

2025-01-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1087970 - cloud-init dirspec pytest-pep8 django-setuptest Bug #1087970 [ftp.debian.org] RM: pep8 -- ROM; was renamed pycodestyle many years ago Removed indication that 1087970 affects cloud-init, dirspec, pytest-pep8, and django-setuptes

Processed: fixup sev

2025-01-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1093285 serious Bug #1093285 [src:custodia] custodia: please remove the dependency on to-be-removed python3-pep8 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: Bug#1093605 marked as pending in patroni

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1093605 [src:patroni] patroni: autopkgtest failure with Python 3.13 Added tag(s) pending. -- 1093605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093605 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1093605: marked as pending in patroni

2025-01-22 Thread Michael Banck
Control: tag -1 pending Hello, Bug #1093605 in patroni 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/postgresql/patroni/-/commit/77d5121db125615b5d321cb6047d0

Bug#1093157: fails to import with 'GreenSocket' has no attribute 'sendmsg'

2025-01-22 Thread Antoine Beaupré
Control: reassign -1 python3-keystoneauth1 Control: affects -1 cumin I've struggled to get a backtrace from cumin because it catches all exceptions in its main() function. But by removing that handler, I could see a backtrace.. Mysteriously, the entry point in cumin is actually: -> from keystone

Processed: fails to import with 'GreenSocket' has no attribute 'sendmsg'

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 python3-keystoneauth1 Bug #1093157 [cumin] cumin fails to start with 'GreenSocket' has no attribute 'sendmsg' Bug reassigned from package 'cumin' to 'python3-keystoneauth1'. No longer marked as found in versions cumin/4.2.0-1. Ignoring request to alter f

Bug#1093243: linux-image-6.1.0-29-amd64 causes mariadb hangs

2025-01-22 Thread Salvatore Bonaccorso
Control: forwarded -1 https://jira.mariadb.org/projects/MDEV/issues/MDEV-35886 Hi, On Tue, Jan 21, 2025 at 08:06:18PM +0100, Bernhard Schmidt wrote: > Control: affects -1 src:mariadb > Control: tags -1 + confirmed > Control: severity -1 critical > > Seeing this too. We have two standalone systems

Bug#1093338: libbio-eutilities-perl: FTBFS: Failed 8/20 test programs. 0/174 subtests failed.

2025-01-22 Thread Étienne Mollier
Hi David, David Miguel Susano Pinto, on 2025-01-22: > I've tried to reproduce it on a container of Debian Trixie but all > tests are OK. Can you help me reproduce this bug? Again, thanks for your thoughts on the issue, as discussed in the issue tracker upstream, this turns out to be a Debian sp

Bug#1093564: libsoup3: FTBFS on riscv64: server-test fails

2025-01-22 Thread Jeremy Bícha
On Sun, Jan 19, 2025 at 5:54 PM Aurelien Jarno wrote: > libsoup3 fails to build from source on riscv64. It seems to be a mix of > flaky tests like on other architectures and a riscv64 specific way of > failing: > > | Summary of Failures: > | > | 25/38 server-test ERROR60.9

Processed: basic256: Unnecessary Build-Depends: libqt5webkit5-dev

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > block 1069574 by -1 Bug #1069574 [libqt5webkit5] age-old and insecure webkit package 1069574 was blocked by: 929253 1074331 1091821 1093372 1093523 1093526 1093527 1093528 1093534 1093539 1093549 1093550 1093551 1093552 1093691 1093725 1093726 1093727 1093728 10937

Bug#1092458: marked as done (FTBFS with Python 3.13: FAIL: breezy.tests.test_symbol_versioning.TestDeprecationWarnings.test_deprecated_method)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jan 2025 19:49:20 + with message-id and subject line Bug#1092458: fixed in breezy 3.3.9-2 has caused the Debian Bug report #1092458, regarding FTBFS with Python 3.13: FAIL: breezy.tests.test_symbol_versioning.TestDeprecationWarnings.test_deprecated_method to be mark

Processed: Re: Bug#1093243: linux-image-6.1.0-29-amd64 causes mariadb hangs

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://jira.mariadb.org/projects/MDEV/issues/MDEV-35886 Bug #1093243 [src:linux] linux-image-6.1.0-29-amd64 causes mariadb hangs Set Bug forwarded-to-address to 'https://jira.mariadb.org/projects/MDEV/issues/MDEV-35886'. -- 1093243: https://bugs.debi

Bug#1092796: marked as done (Autopkgtests fail with Python 3.13: OSError: [Errno 9] Bad file descriptor)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jan 2025 19:20:40 + with message-id and subject line Bug#1092796: fixed in wireless-regdb 2024.10.07-2 has caused the Debian Bug report #1092796, regarding Autopkgtests fail with Python 3.13: OSError: [Errno 9] Bad file descriptor to be marked as done. This means t

Bug#1089814: marked as done (libigdfcl2-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/pkgconfig/igc-opencl.pc)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jan 2025 19:00:11 + with message-id and subject line Bug#1089814: fixed in intel-graphics-compiler2 2.3.1-3 has caused the Debian Bug report #1089814, regarding libigdfcl2-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/pkgconfig/igc-opencl.pc to be

Bug#1093790: src:os-autoinst: fails to migrate to testing for too long: FTBFS on ppc64el

2025-01-22 Thread Paul Gevers
Source: os-autoinst Version: 4.6.1712854180.1bf07142-4 Severity: serious Control: close -1 4.6.1731418769.97d9a7fd-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync User: debian-powe...@lists.debian.org Usertags: ppc64el Dear maintainer(s), The Release Team co

Bug#1087038: marked as done (libpango-1.0-0: Pango 1.52+ API+ABI breakage (affecting gnuplot in particular))

2025-01-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jan 2025 13:59:35 -0500 with message-id and subject line Re: Bug#1087038: libpango-1.0-0: Pango 1.52+ API+ABI breakage (affecting gnuplot in particular) has caused the Debian Bug report #1087038, regarding libpango-1.0-0: Pango 1.52+ API+ABI breakage (affecting gnuplot

Processed: src:tokodon: fails to migrate to testing for too long

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > close -1 24.12.0-1 Bug #1093788 [src:tokodon] src:tokodon: fails to migrate to testing for too long Marked as fixed in versions tokodon/24.12.0-1. Bug #1093788 [src:tokodon] src:tokodon: fails to migrate to testing for too long Marked Bug as done -- 1093788: https:

Processed: src:maven: fails to migrate to testing for too long

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > close -1 3.9.9-1 Bug #1093791 [src:maven] src:maven: fails to migrate to testing for too long Marked as fixed in versions maven/3.9.9-1. Bug #1093791 [src:maven] src:maven: fails to migrate to testing for too long Marked Bug as done -- 1093791: https://bugs.debian.

Bug#1093791: src:maven: fails to migrate to testing for too long

2025-01-22 Thread Paul Gevers
Source: maven Version: 3.8.8-2 Severity: serious Control: close -1 3.9.9-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as havin

Processed: src:os-autoinst: fails to migrate to testing for too long: FTBFS on ppc64el

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > close -1 4.6.1731418769.97d9a7fd-1 Bug #1093790 [src:os-autoinst] src:os-autoinst: fails to migrate to testing for too long: FTBFS on ppc64el Marked as fixed in versions os-autoinst/4.6.1731418769.97d9a7fd-1. Bug #1093790 [src:os-autoinst] src:os-autoinst: fails to

Processed: src:maven-install-plugin: fails to migrate to testing for too long

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > close -1 3.1.3-1 Bug #1093787 [src:maven-install-plugin] src:maven-install-plugin: fails to migrate to testing for too long Marked as fixed in versions maven-install-plugin/3.1.3-1. Bug #1093787 [src:maven-install-plugin] src:maven-install-plugin: fails to migrate

Bug#1093788: src:tokodon: fails to migrate to testing for too long

2025-01-22 Thread Paul Gevers
Source: tokodon Version: 23.04.2-2 Severity: serious Control: close -1 24.12.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as

Bug#1093789: src:rust-safe-arch: fails to migrate to testing for too long

2025-01-22 Thread Paul Gevers
Source: rust-safe-arch Version: 0.7.2-2 Severity: serious Control: close -1 0.7.4-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days

Processed: wkhtmltopdf: Upstream project seems dead, plan for eventual removal?

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1091821 [wkhtmltopdf] wkhtmltopdf: Upstream project seems dead, plan for eventual removal? Severity set to 'serious' from 'normal' -- 1091821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091821 Debian Bug Tracking System Contact ow.

Processed: src:rust-safe-arch: fails to migrate to testing for too long

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.7.4-1 Bug #1093789 [src:rust-safe-arch] src:rust-safe-arch: fails to migrate to testing for too long The source 'rust-safe-arch' and version '0.7.4-1' do not appear to match any binary packages Marked as fixed in versions rust-safe-arch/0.7.4-1. Bug #109

Bug#1093786: src:ruby-vips: fails to migrate to testing for too long

2025-01-22 Thread Paul Gevers
Source: ruby-vips Version: 2.1.4-1.1 Severity: serious Control: close -1 2.2.2-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as

Bug#1093787: src:maven-install-plugin: fails to migrate to testing for too long

2025-01-22 Thread Paul Gevers
Source: maven-install-plugin Version: 3.1.1-1 Severity: serious Control: close -1 3.1.3-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 3

Processed: src:tryton-meta: fails to migrate to testing for too long

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > close -1 56 Bug #1093785 [src:tryton-meta] src:tryton-meta: fails to migrate to testing for too long Marked as fixed in versions tryton-meta/56. Bug #1093785 [src:tryton-meta] src:tryton-meta: fails to migrate to testing for too long Marked Bug as done -- 1093785

Processed: src:ruby-vips: fails to migrate to testing for too long

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.2.2-1 Bug #1093786 [src:ruby-vips] src:ruby-vips: fails to migrate to testing for too long Marked as fixed in versions ruby-vips/2.2.2-1. Bug #1093786 [src:ruby-vips] src:ruby-vips: fails to migrate to testing for too long Marked Bug as done -- 1093786

Bug#1093785: src:tryton-meta: fails to migrate to testing for too long

2025-01-22 Thread Paul Gevers
Source: tryton-meta Version: 55 Severity: serious Control: close -1 56 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a

Bug#1087038: libpango-1.0-0: Pango 1.52+ API+ABI breakage (affecting gnuplot in particular)

2025-01-22 Thread Vincent Lefevre
On 2025-01-22 13:37:10 -0500, Jeremy Bícha wrote: > It doesn't look like pango will be changing upstream as a result of > your bug report. We're not going to do a downstream library transition > for a widely used library like pango, just because of a small behavior > change that apparently broke on

Bug#1093784: src:itinerary: unsatisfied build dependency in testing: libkpimpkpass-dev

2025-01-22 Thread Paul Gevers
Source: itinerary Version: 24.12.0-2 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed

Bug#1091861: closed by Debian FTP Masters (reply to Santiago Ruano Rincón ) (Bug#1091861: fixed in pytango 10.0.0-3)

2025-01-22 Thread Paul Gevers
Hi Santiago, Thanks for working on a fix, ... On 22-01-2025 14:27, Santiago Ruano Rincón wrote: Control: reopen -1 At least, one more test if failing (triggered by migration-reference/0): https://ci.debian.net/packages/p/pytango/unstable/amd64/56790990/ so this will still block the gcc-14 migr

Bug#1068745: fixed in coinutils 2.11.11+ds-3

2025-01-22 Thread Håvard F . Aasen
On Wed, 22 Jan 2025 10:11:33 + Debian FTP Masters wrote: > Source: coinutils > Source-Version: 2.11.11+ds-3 > Done: Michael R. Crusoe > > We believe that the bug you reported is fixed in the latest version of > coinutils, which is due to be installed in the Debian FTP archive. > [...] >

Bug#1093564: marked as done (libsoup3: FTBFS on riscv64: server-test fails)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jan 2025 18:37:21 + with message-id and subject line Bug#1093564: fixed in libsoup3 3.6.4-2 has caused the Debian Bug report #1093564, regarding libsoup3: FTBFS on riscv64: server-test fails to be marked as done. This means that you claim that the problem has been d

Bug#1087038: libpango-1.0-0: Pango 1.52+ API+ABI breakage (affecting gnuplot in particular)

2025-01-22 Thread Jeremy Bícha
Vincent, I think we could close this Debian bug now. gnuplot has been fixed in Debian Testing. It doesn't look like pango will be changing upstream as a result of your bug report. We're not going to do a downstream library transition for a widely used library like pango, just because of a small b

Processed: Bug#1093564 marked as pending in libsoup3

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1093564 [src:libsoup3] libsoup3: FTBFS on riscv64: server-test fails Added tag(s) pending. -- 1093564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093564 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1093564: marked as pending in libsoup3

2025-01-22 Thread Jeremy Bícha
Control: tag -1 pending Hello, Bug #1093564 in libsoup3 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/libsoup3/-/commit/fbd0e632136aa378026e912bf62

Bug#1084539: marked as done (scribus: removal of Python standard libraries in Python 3.13)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jan 2025 12:40:25 -0500 with message-id and subject line Re: scribus: removal of Python standard libraries in Python 3.13 has caused the Debian Bug report #1084539, regarding scribus: removal of Python standard libraries in Python 3.13 to be marked as done. This means

Bug#1093777: Autopkgtests fail on riscv64: hypothesis.errors.FailedHealthCheck: Data generation is extremely slow

2025-01-22 Thread Andrey Rakhmatullin
Source: python-returns Version: 0.24.0-1 Severity: serious https://ci.debian.net/packages/p/python-returns/testing/riscv64/56800351/ Lots of "hypothesis.errors.FailedHealthCheck: Data generation is extremely slow: Only produced 8 valid examples in 1.02 seconds (0 invalid ones and 0 exceeded maxim

Bug#1093774: yubikey-manager: 5.5.1-1 breaks yubioath-desktop

2025-01-22 Thread Mathias Gibbens
Source: yubikey-manager Version: 5.5.1-1 Severity: serious Justification: Renders yubioath-desktop unusable python3-ykman 5.5.1-1 recently migrated to testing, and it appears to be incompatible with yubioath-desktop 5.1.0-3, rendering it totally unusable as it no longer recognizes my yubikeys. M

Bug#1093771: lomiri-teleports-app:FTBFS:build failed ( error: cannot find library libtdjson.so.1.8.38)

2025-01-22 Thread Yue Gui
Source: lomiri-teleports-app Version: 1.20-2+b1 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear lomiri-teleports-app maintainer, The package lomiri-teleports-app build failed on all arch.The crucial buildd

Bug#1093350: marked as done (poetry: FTBFS: AttributeError: 'Application' object has no attribute 'set_solution_provider_repository')

2025-01-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jan 2025 15:11:03 + with message-id and subject line Bug#1093350: fixed in poetry 2.0.1+dfsg-1 has caused the Debian Bug report #1093350, regarding poetry: FTBFS: AttributeError: 'Application' object has no attribute 'set_solution_provider_repository' to be marked a

Bug#1093338: libbio-eutilities-perl: FTBFS: Failed 8/20 test programs. 0/174 subtests failed.

2025-01-22 Thread David Miguel Susano Pinto
Package: libbio-eutilities-perl Followup-For: Bug #1093338 X-Debbugs-Cc: carandraug+...@gmail.com I'm an upstream developer of Bio::EUtilities. As you remark, this bug is weird because nothing seems to have changed. I've tried to reproduce it on a container of Debian Trixie but all tests are OK.

Bug#1093765: marked as done (gitsign: binary-all FTBFS)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jan 2025 15:04:45 + with message-id and subject line Bug#1093765: fixed in gitsign 0.12.0-3 has caused the Debian Bug report #1093765, regarding gitsign: binary-all FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this i

Processed: Re: coinor-symphony: FTBFS with coinutils 2.11.10

2025-01-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1068745 coinor-symphony/5.6.17+dfsg-1 Bug #1068745 {Done: Michael R. Crusoe } [src:coinor-symphony] coinor-symphony: FTBFS with coinutils 2.11.10 No longer marked as found in versions coinor-symphony/5.6.17+dfsg-1. > End of message, stop

Bug#1093765: marked as pending in gitsign

2025-01-22 Thread Simon Josefsson
Control: tag -1 pending Hello, Bug #1093765 in gitsign 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/go-team/packages/gitsign/-/commit/99275c17875bbe49588fa7b

Bug#1093253: marked as done (openjdk-21: endless loop in armhf build)

2025-01-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jan 2025 14:53:58 +0100 with message-id and subject line Fixed has caused the Debian Bug report #1093253, regarding openjdk-21: endless loop in armhf build to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it i

Processed: Bug#1093765 marked as pending in gitsign

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1093765 [src:gitsign] gitsign: binary-all FTBFS Added tag(s) pending. -- 1093765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1091861: closed by Debian FTP Masters (reply to Santiago Ruano Rincón ) (Bug#1091861: fixed in pytango 10.0.0-3)

2025-01-22 Thread Santiago Ruano Rincón
Control: reopen -1 At least, one more test if failing (triggered by migration-reference/0): https://ci.debian.net/packages/p/pytango/unstable/amd64/56790990/ so this will still block the gcc-14 migration. I will work to fix this. Cheers, -- Santiago signature.asc Description: PGP signature

Processed: Re: Bug#1091861 closed by Debian FTP Masters (reply to Santiago Ruano Rincón ) (Bug#1091861: fixed in pytango 10.0.0-3)

2025-01-22 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1091861 {Done: Santiago Ruano Rincón } [src:pytango] pytango: flaky autopkgtest: Timeout, waiting for event 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. B

  1   2   >