Bug#1079842: Should debbugs be removed from unstable

2024-08-28 Thread Alexandre Detiste
Hi, This mostly automated email made me smile, knowing that debbugs is the thing running https://bugs.debian.org/ and processing this very email. I know of one single other instance at https://debbugs.gnu.org/ Greetings

Bug#1079968: Should zeek-aux be removed from unstable?

2024-08-28 Thread Helmut Grohne
Source: zeek-aux Severity: serious Justification: grab attention of maintainer User: helm...@debian.org Usertags: sidremove Dear maintainer, I suggest removing zeek-aux from Debian for the following reasons: * It accumulated one RC-bug: + #985522: zeek-aux: broken symlink: /usr/bin/bro-cut ->

Bug#1064126: [Pkg-libvirt-maintainers] Bug#1064126: libvirt: install NSS modules into /usr

2024-08-28 Thread Helmut Grohne
Hi Andrea, On Wed, Aug 28, 2024 at 12:17:05AM +0200, Andrea Bolognani wrote: > I read up a bit on the various problems and mitigations documented as > part of DEP17 yesterday and figured that our changes would probably > hit P1. I hoped that M7 might be enough to take care of that, but I > trust y

Bug#1079966: Should gigedit be removed from unstable?

2024-08-28 Thread Helmut Grohne
Source: gigedit Severity: serious Justification: grab attention of maintainer User: helm...@debian.org Usertags: sidremove Dear maintainer, I suggest removing gigedit from Debian for the following reasons: * It accumulated one RC-bug: + #997203: gigedit: FTBFS: ../compat.h:194:21: error: ‘c

Bug#1079965: Should golang-github-coreos-go-tspi be removed from unstable?

2024-08-28 Thread Helmut Grohne
Source: golang-github-coreos-go-tspi Severity: serious Justification: grab attention of maintainer User: helm...@debian.org Usertags: sidremove Dear maintainer, I suggest removing golang-github-coreos-go-tspi from Debian for the following reasons: * It accumulated one RC-bug: + #849665: gola

Bug#1079964: Should guacamole-server be removed from unstable?

2024-08-28 Thread Helmut Grohne
Source: guacamole-server Severity: serious Justification: grab attention of maintainer User: helm...@debian.org Usertags: sidremove Dear maintainer, I suggest removing guacamole-server from Debian for the following reasons: * It accumulated one RC-bug: + #1005154: guacamole-server: frequent t

Bug#1079963: Should hydroffice.bag be removed from unstable?

2024-08-28 Thread Helmut Grohne
Source: hydroffice.bag Severity: serious Justification: grab attention of maintainer User: helm...@debian.org Usertags: sidremove Dear maintainer, I suggest removing hydroffice.bag from Debian for the following reasons: * It accumulated one RC-bug: + #993003: hydroffice.bag: tests fail with h

Bug#1079962: Should gr-dab be removed from unstable?

2024-08-28 Thread Helmut Grohne
Source: gr-dab Severity: serious Justification: grab attention of maintainer User: helm...@debian.org Usertags: sidremove Dear maintainer, I suggest removing gr-dab from Debian for the following reasons: * It accumulated one RC-bug: + #1002106: gr-dab: FTBFS: ./obj-x86_64-linux-gnu/CMakeFile

Bug#1079961: Should leap-archive-keyring be removed from unstable?

2024-08-28 Thread Helmut Grohne
Source: leap-archive-keyring Severity: serious Justification: grab attention of maintainer User: helm...@debian.org Usertags: sidremove Dear maintainer, I suggest removing leap-archive-keyring from Debian for the following reasons: * It accumulated one RC-bug: + #880220: should not install a

Bug#1079960: Should fruit be removed from unstable?

2024-08-28 Thread Helmut Grohne
Source: fruit Severity: serious Justification: grab attention of maintainer User: helm...@debian.org Usertags: sidremove Dear maintainer, I suggest removing fruit from Debian for the following reasons: * It accumulated one RC-bug: + #1014187: fruit: Binary file without a source code Last

Bug#1079959: Should imdbpy be removed from unstable?

2024-08-28 Thread Helmut Grohne
Source: imdbpy Severity: serious Justification: grab attention of maintainer User: helm...@debian.org Usertags: sidremove Dear maintainer, I suggest removing imdbpy from Debian for the following reasons: * It accumulated one RC-bug: + #1017747: imdbpy: autopkgtest regression: KeyError: 'top 1

Bug#1079958: Should epigrass be removed from unstable?

2024-08-28 Thread Helmut Grohne
Source: epigrass Severity: serious Justification: grab attention of maintainer User: helm...@debian.org Usertags: sidremove Dear maintainer, I suggest removing epigrass from Debian for the following reasons: * It accumulated 2 RC-bugs: + #995966: epigrass: epirunner and epidash fail to run du

Bug#1077928: The fix has been packaged

2024-08-28 Thread Matija Nalis
The fix has been packaged in 0.4.0-7; currently waiting in #1079957 for some sponsor to upload it. -- Opinions above are GNU-copylefted.

Bug#1037882: vart: ftbfs with GCC-13

2024-08-28 Thread Petter Reinholdtsen
Is there something wrong with this patch? It seem to solve a RC problem and has been lingering in BTS for a year. -- Happy hacking Petter Reinholdtsen

Bug#1074951: marked as done (fenics-dolfinx: ftbfs with GCC-14)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Aug 2024 05:04:13 + with message-id and subject line Bug#1074951: fixed in fenics-dolfinx 1:0.8.0-11 has caused the Debian Bug report #1074951, regarding fenics-dolfinx: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been deal

Bug#1077452: picolibc: FTBFS: make[1]: *** [debian/rules:134: override_dh_auto_test] Error 104

2024-08-28 Thread Michael Tokarev
I'm not an arm guru, my knowledge of arm is near non-existent. The commit in qemu which I bisected this to yesterday, apparently, is a bugfix, - previously qemu allowed an unaligned access here, while real hardware does not. Now qemu behavior matches that of the hardware. So it might as well be

Bug#1075039: marked as done (gramophone2: ftbfs with GCC-14)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Aug 2024 03:04:54 + with message-id and subject line Bug#1075039: fixed in gramophone2 0.8.13a-3.4 has caused the Debian Bug report #1075039, regarding gramophone2: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1052105: gnome-shell-extension-no-annoyance: needs update for GNOME Shell 46

2024-08-28 Thread Hank Knox
Hi Andres, I submitted a merge request for the first step, the updated files from the new upstream source. This is my first attempt at a Debian package, so forgive me when I make errors in the debian/ files. I will review what I have before I push those changes through. Would you be able to

Processed: Re: Bug#1079938: sbuild-createchroot creates unmerged /usr for bookworm by default

2024-08-28 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #1079938 [sbuild] sbuild-createchroot creates unmerged /usr for bookworm by default Severity set to 'normal' from 'serious' -- 1079938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079938 Debian Bug Tracking System Contact ow...@bugs.d

Bug#1079938: sbuild-createchroot creates unmerged /usr for bookworm by default

2024-08-28 Thread Chris Hofstaedtler
Control: severity -1 normal On Wed, Aug 28, 2024 at 08:35:06PM +0200, Lee Garrett wrote: > when creating a bookworm schroot e.g. with > sbuild-createchroot --merged-usr bookworm > /var/lib/schroot/schroots/bookworm-amd64-sbuild > http://localhost:3142/deb.debian.org/debian/ > > the resulting sc

Bug#1077493: marked as done (finit-sysv: ineffectively diverted by bookworm packages (DEP17))

2024-08-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Aug 2024 00:04:03 + with message-id and subject line Bug#1077493: fixed in finit 4.7-3 has caused the Debian Bug report #1077493, regarding finit-sysv: ineffectively diverted by bookworm packages (DEP17) to be marked as done. This means that you claim that the probl

Bug#1072447: marked as done (qtox: FTBFS with ffmpeg 7.0: cameradevice.cpp:293:21: error: ‘const struct AVInputFormat’ has no member named ‘priv_data_size’)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 23:52:27 + with message-id and subject line Bug#1072447: fixed in qtox 1.17.6-1 has caused the Debian Bug report #1072447, regarding qtox: FTBFS with ffmpeg 7.0: cameradevice.cpp:293:21: error: ‘const struct AVInputFormat’ has no member named ‘priv_data_siz

Bug#1077407: marked as done (galternatives: FTBFS: setuptools.extern.packaging.version.InvalidVersion: Invalid version: 'git')

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 23:34:03 + with message-id and subject line Bug#1077407: fixed in galternatives 1.0.10 has caused the Debian Bug report #1077407, regarding galternatives: FTBFS: setuptools.extern.packaging.version.InvalidVersion: Invalid version: 'git' to be marked as done

Bug#1069027: marked as pending in jupyter-notebook

2024-08-28 Thread Diane Trout
Control: tag -1 pending Hello, Bug #1069027 in jupyter-notebook 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/jupyter-notebook/-/commit/4

Processed: Bug#1069027 marked as pending in jupyter-notebook

2024-08-28 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1069027 [jupyter-notebook] python3-notebook: Jupyter Notebook fails to start - wrong call to traitlets.warn Added tag(s) pending. -- 1069027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069027 Debian Bug Tracking System Contact ow...@bug

Bug#1079950: chafa: Fails to build on some architectures with glibc 2.40

2024-08-28 Thread Jeremy Bícha
Source: chafa Version: 1.14.2-1 Severity: serious Tags: ftbfs Based on the Ubuntu build logs, I suspect that chafa fails to build on some architectures with glibc 2.40. Note that although chafa was uploaded a few days ago, the new version of glibc was uploaded to Unstable for the first time after

Bug#1053016: marked as done (cheshire-clojure: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 20:34:39 + with message-id and subject line Bug#1053016: fixed in cheshire-clojure 5.11.0-4 has caused the Debian Bug report #1053016, regarding cheshire-clojure: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7 to be marked as done. Th

Processed: Re: RM: unarr -- RoQA; leaf package

2024-08-28 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1079916 [src:unarr] RM: unarr -- RoQA; leaf package Severity set to 'serious' from 'normal' > retitle -1 unarr: Keep the package out of trixie Bug #1079916 [src:unarr] RM: unarr -- RoQA; leaf package Changed Bug title to 'unarr: Keep the pack

Processed: severity of 1079394 is grave

2024-08-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1079394 grave Bug #1079394 [src:linux] linux-image-6.10.6-amd64: causes cifs regression, flatpak & ostree signature corruption Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need ass

Bug#1079938: sbuild-createchroot creates unmerged /usr for bookworm by default

2024-08-28 Thread Lee Garrett
Package: sbuild Version: 0.85.0 Severity: serious X-Debbugs-Cc: deb...@rocketjump.eu Hi, when creating a bookworm schroot e.g. with sbuild-createchroot --merged-usr bookworm /var/lib/schroot/schroots/bookworm-amd64-sbuild http://localhost:3142/deb.debian.org/debian/ the resulting schroot has a

Bug#1079744: marked as done (rustc-web has an undeclared file conflict)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 18:17:08 + with message-id and subject line Bug#1079744: fixed in rustc-web 1.78.0+dfsg1-2~deb12u3 has caused the Debian Bug report #1079744, regarding rustc-web has an undeclared file conflict to be marked as done. This means that you claim that the proble

Bug#1079653: marked as done (rustc-web and cargo-web have an undeclared file conflict with rustup)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 18:17:08 + with message-id and subject line Bug#1079653: fixed in rustc-web 1.78.0+dfsg1-2~deb12u3 has caused the Debian Bug report #1079653, regarding rustc-web and cargo-web have an undeclared file conflict with rustup to be marked as done. This means tha

Bug#1052583: marked as done (com-hypirion-io-clojure: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 18:19:14 + with message-id and subject line Bug#1052583: fixed in com-hypirion-io-clojure 0.3.1-5 has caused the Debian Bug report #1052583, regarding com-hypirion-io-clojure: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7 to be marked

Bug#1076683: marked as done (rust-web-doc: missing Conflicts: rust-mozilla-doc)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 18:17:08 + with message-id and subject line Bug#1076683: fixed in rustc-web 1.78.0+dfsg1-2~deb12u3 has caused the Debian Bug report #1076683, regarding rust-web-doc: missing Conflicts: rust-mozilla-doc to be marked as done. This means that you claim that th

Bug#1064126: [Pkg-libvirt-maintainers] Bug#1064126: libvirt: install NSS modules into /usr

2024-08-28 Thread Andrea Bolognani
On Wed, Aug 28, 2024 at 12:17:05AM +0200, Andrea Bolognani wrote: > +#BEGIN CREATE_PROTECTIVE_DIVERSION > +create_protective_diversion() { > +local usrfile="$1" > +local firstver="$2" > + > +if [ "$2" != "--" ]; then This should be "$3" for things to work. Same in the other snippet. -

Bug#1079744: marked as done (rustc-web has an undeclared file conflict)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 17:17:27 + with message-id and subject line Bug#1079744: fixed in rustc-web 1.78.0+dfsg1-2~deb11u3 has caused the Debian Bug report #1079744, regarding rustc-web has an undeclared file conflict to be marked as done. This means that you claim that the proble

Bug#1079653: marked as done (rustc-web and cargo-web have an undeclared file conflict with rustup)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 17:17:27 + with message-id and subject line Bug#1079653: fixed in rustc-web 1.78.0+dfsg1-2~deb11u3 has caused the Debian Bug report #1079653, regarding rustc-web and cargo-web have an undeclared file conflict with rustup to be marked as done. This means tha

Bug#1076683: marked as done (rust-web-doc: missing Conflicts: rust-mozilla-doc)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 17:17:27 + with message-id and subject line Bug#1076683: fixed in rustc-web 1.78.0+dfsg1-2~deb11u3 has caused the Debian Bug report #1076683, regarding rust-web-doc: missing Conflicts: rust-mozilla-doc to be marked as done. This means that you claim that th

Bug#1079928: gpgme1.0: FTFBFS with python3-setuptools 73.0.1-1

2024-08-28 Thread Andreas Metzler
Source: gpgme1.0 Version: 1.18.0-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: python3-setupto...@packages.debian.org, ametz...@debian.org Hello, gpgme1.0 has recently started to FTBFS on current sid while it build suc

Bug#1079477: plasma-mobile: FTBFS

2024-08-28 Thread Marco Mattiolo
Hi Patrick, thank you for the note. I'm answering to the shell's bug, but the topic is similar for the other 5 bugs of the packages I'm maintaining, as well. I'm quite inclined to let it broken and then fix it with the Plasma6 upload to sid, if that will be possible in a reasonable amount of

Bug#1077528: marked as done (getfem: FTBFS: getfem_python_c.c:142:5: error: initialization of ‘PyAsyncMethods *’ from incompatible pointer type ‘int (*)(PyGetfemObject *, PyGetfemObject *)’ [-Wincompa

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 16:49:05 + with message-id and subject line Bug#1077528: fixed in getfem 5.4.2+dfsg1-5 has caused the Debian Bug report #1077528, regarding getfem: FTBFS: getfem_python_c.c:142:5: error: initialization of ‘PyAsyncMethods *’ from incompatible pointer type ‘i

Bug#1077513: marked as done (netgen FTBFS on i386 with gcc 14)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 16:49:22 + with message-id and subject line Bug#1077513: fixed in netgen 6.2.2401+dfsg1-3 has caused the Debian Bug report #1077513, regarding netgen FTBFS on i386 with gcc 14 to be marked as done. This means that you claim that the problem has been dealt w

Bug#1075333: marked as done (onednn: ftbfs with GCC-14)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 16:49:51 + with message-id and subject line Bug#1075333: fixed in onednn 3.5.3-1 has caused the Debian Bug report #1075333, regarding onednn: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1079924: marked as done (python-lesscpy: undeclared runtime dependency on python3-six which caused a FTBFS in prewikka)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 16:34:33 + with message-id and subject line Bug#1079924: fixed in python-lesscpy 0.15.1-0.2 has caused the Debian Bug report #1079924, regarding python-lesscpy: undeclared runtime dependency on python3-six which caused a FTBFS in prewikka to be marked as do

Bug#1079924: python-lesscpy: undeclared runtime dependency on python3-six which caused a FTBFS in prewikka

2024-08-28 Thread Alexandre Detiste
Le mer. 28 août 2024 à 17:48, Chris Hofstaedtler a écrit : > Right. Will you NMU both python-lesscpy and prewikka? > > Chris Ok, I will do that in two 6hours / dinstall locksteps & I'll be carefull to keep the good half of your NMU. Greetings

Processed: severity of 1071455 is serious, tagging 1071455

2024-08-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1071455 serious Bug #1071455 [python-html-sanitizer] python-html-sanitizer: python3-lxml-html-clean is now a separate package Severity set to 'serious' from 'normal' > tags 1071455 + ftbfs Bug #1071455 [python-html-sanitizer] python-html

Bug#1079924: python-lesscpy: undeclared runtime dependency on python3-six which caused a FTBFS in prewikka

2024-08-28 Thread Chris Hofstaedtler
Hi, * Alexandre Detiste [240828 17:39]: > The problem still exists and could affect any other user of python-lesscpy. > > When lesscpy, the 5.2.0-2.1 NMU should be reverted: > prewikka itself do not use python3-six at all, > and python3-six is a legacy helper that should > be removed from Debian

Bug#1079924: python-lesscpy: undeclared runtime dependency on python3-six which caused a FTBFS in prewikka

2024-08-28 Thread Alexandre Detiste
Source: python-lesscpy Version: 0.15.1-0.1 Severity: serious Tags: ftbfs Justification: Policy 7.2 X-Debbugs-Cc: Chris Hofstaedtler , Hans Joachim Desserud , Pierre Chifflier Dear Maintainers, After a carefull reread of the bug report of prewikka #1060985, it appears that the root cause lies i

Bug#1026729: marked as done (python-opentracing: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 15:07:58 + with message-id and subject line Bug#1026729: fixed in python-opentracing 2.4.0-2 has caused the Debian Bug report #1026729, regarding python-opentracing: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10"

Processed: Bug#1026729 marked as pending in python-opentracing

2024-08-28 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1026729 [src:python-opentracing] python-opentracing: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13 Added tag(s) pending. -- 1026729: https://bugs.debian.org/cgi-bin/bugreport.c

Bug#1026729: marked as pending in python-opentracing

2024-08-28 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #1026729 in python-opentracing 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/python-opentracing/-/comm

Bug#1079332: marked as done (reform-setup-wizard: upcoming rust-gtk4 update)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 14:37:13 + with message-id and subject line Bug#1079332: fixed in reform-setup-wizard 1.0-12 has caused the Debian Bug report #1079332, regarding reform-setup-wizard: upcoming rust-gtk4 update to be marked as done. This means that you claim that the problem

Bug#1079702: marked as done (reform-setup-wizard: autopkgtest "test_with_chroot" is flaky)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 14:37:13 + with message-id and subject line Bug#1079702: fixed in reform-setup-wizard 1.0-12 has caused the Debian Bug report #1079702, regarding reform-setup-wizard: autopkgtest "test_with_chroot" is flaky to be marked as done. This means that you claim th

Bug#1042614: marked as done (libsass-python: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 14:35:53 + with message-id and subject line Bug#1042614: fixed in libsass-python 0.23.0-0.1 has caused the Debian Bug report #1042614, regarding libsass-python: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string forma

Bug#1058362: marked as done (libsass-python: FTBFS: TypeError: not all arguments converted during string formatting)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 14:35:53 + with message-id and subject line Bug#1058362: fixed in libsass-python 0.23.0-0.1 has caused the Debian Bug report #1058362, regarding libsass-python: FTBFS: TypeError: not all arguments converted during string formatting to be marked as done. Th

Bug#1079702: Both autopkgtest are flaky

2024-08-28 Thread Johannes Schauer Marin Rodrigues
Hi Jeremy, Quoting Jeremy Bícha (2024-08-28 14:56:56) > On Wed, Aug 28, 2024 at 8:51 AM Johannes Schauer Marin Rodrigues > wrote: > > That would be odd because the autopkgtest runs just fine and reliable on > > salsa > > ci. But I have to find a better way to automate testing of gtk4 application

Processed: Re: Bug#978012: xsddiagram: No diagram is shown

2024-08-28 Thread Debian Bug Tracking System
Processing control commands: > severity -1 grave Bug #978012 [xsddiagram] xsddiagram: No diagram is shown Severity set to 'grave' from 'important' -- 978012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed (with 2 errors): Re: #1079901: RM: libwcat1 -- RoQA; dead upstream, obsolete

2024-08-28 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 RM: libwcat1 -- RoQA; dead upstream, obsolete Bug #1079901 [src:libapache2-mod-watchcat] RM: libwcat1 -- RoQA; dead upstream, obsolete Ignoring request to change the title of bug#1079901 to the same title > reassign -1 ftp.debian.org Bug #1079901 [src:lib

Bug#1079901: #1079901: RM: libwcat1 -- RoQA; dead upstream, obsolete

2024-08-28 Thread Chris Hofstaedtler
Control: retitle -1 RM: libwcat1 -- RoQA; dead upstream, obsolete Control: reassign -1 ftp.debian.org Control: user ftp.debian@packages.debian.org Control: usertag -1 + remove Dear ftpmasters, please remove libwcat1 which is apparently useless without watchcatd (RM bug #1074225) Thanks, Chri

Processed (with 2 errors): Re: #1079900: RM: libapache2-mod-watchcat -- RoQA; dead upstream, obsolete

2024-08-28 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 ftp.debian.org Bug #1079900 [src:libapache2-mod-watchcat] RM: libapache2-mod-watchcat -- RoQA; dead upstream, obsolete Bug reassigned from package 'src:libapache2-mod-watchcat' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #1079900

Bug#1079900: #1079900: RM: libapache2-mod-watchcat -- RoQA; dead upstream, obsolete

2024-08-28 Thread Chris Hofstaedtler
Control: reassign -1 ftp.debian.org Control: user ftp.debian@packages.debian.org Control: usertag -1 + remove Dear ftpmasters, please remove libapache2-mod-watchcat which is apparently useless without watchcatd (RM bug #1074225) Thanks, Chris

Processed: rm libapache2-mod-watchcat

2024-08-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 1078461 -2 Bug #1078461 [src:libapache2-mod-watchcat] libapache2-mod-watchcat: depends on to be removed watchcatd Bug 1078461 cloned as bug 1079900 1074225 was blocked by: 1078461 1074225 was not blocking any bugs. Added blocking bug(s) of

Bug#1069399: marked as done (ruby3.1: FTBFS on arm64: Errno::EADDRINUSE: Address already in use - listen(2))

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 13:35:47 + with message-id and subject line Bug#1069399: fixed in ruby3.1 3.1.2-8.4 has caused the Debian Bug report #1069399, regarding ruby3.1: FTBFS on arm64: Errno::EADDRINUSE: Address already in use - listen(2) to be marked as done. This means that yo

Bug#1075922: marked as done (ruby3.1: FTBFS with openssl 3.3)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 13:35:47 + with message-id and subject line Bug#1075922: fixed in ruby3.1 3.1.2-8.4 has caused the Debian Bug report #1075922, regarding ruby3.1: FTBFS with openssl 3.3 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1078461: libapache2-mod-watchcat: depends on to be removed watchcatd

2024-08-28 Thread наб
On Sat, Aug 10, 2024 at 10:55:27PM +0200, Chris Hofstaedtler wrote: > Source: libapache2-mod-watchcat > > watchcatd is supposed to be removed, see #1074225. In that case, there's a case to be made for removing src:libwcat1 as well, since that library exists solely to talk to watchcatd (and it looks

Bug#1079702: Both autopkgtest are flaky

2024-08-28 Thread Jeremy Bícha
On Wed, Aug 28, 2024 at 8:51 AM Johannes Schauer Marin Rodrigues wrote: > That would be odd because the autopkgtest runs just fine and reliable on salsa > ci. But I have to find a better way to automate testing of gtk4 applications > before I tackle this problem again. Taking screenshots via VNC a

Bug#1079702: autopkgtest 'test_without_chroot' is flaky

2024-08-28 Thread Johannes Schauer Marin Rodrigues
Quoting Jeremy Bícha (2024-08-27 22:26:39) > gtk4 has more failing build tests than other architectures. > Unfortunately, we are forced to ignore them because our understanding > is that it's currently required for desktop tasks to be installable on > all release architectures. (Or I guess someone

Bug#1079702: Both autopkgtest are flaky

2024-08-28 Thread Johannes Schauer Marin Rodrigues
Quoting Reinhard Tartler (2024-08-28 13:43:30) > Seems I made a mistake in my previous report. It is actually the test > 'test_without_chroot' that is flaky. Also, I noticed this comment in > https://sources.debian.org/src/reform-setup-wizard/1.0-11/debian/tests/control/#L7-L25: > > # Since this t

Bug#1079891: gbrainy: remove from unstable?

2024-08-28 Thread Andrey Rakhmatullin
On Wed, Aug 28, 2024 at 02:15:43PM +0200, Chris Hofstaedtler wrote: > Source: gbrainy > Version: 1:2.4.6-1 > Severity: serious > Justification: get attention of maintainers for removal > X-Debbugs-Cc: Jeremy Bícha , w...@debian.org > > Hi, > > gbrainy cannot migrate to testing for various issues,

Bug#1079891: gbrainy: remove from unstable?

2024-08-28 Thread Chris Hofstaedtler
Source: gbrainy Version: 1:2.4.6-1 Severity: serious Justification: get attention of maintainers for removal X-Debbugs-Cc: Jeremy Bícha , w...@debian.org Hi, gbrainy cannot migrate to testing for various issues, including it using gtk-sharp3, which itself is rc-buggy und unmaintained. In #105104

Processed: retitle 1079702 to reform-setup-wizard: autopkgtest "test_with_chroot" is flaky

2024-08-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1079702 reform-setup-wizard: autopkgtest "test_with_chroot" is flaky Bug #1079702 [reform-setup-wizard] autopkgtest 'test_without_chroot' is flaky Changed Bug title to 'reform-setup-wizard: autopkgtest "test_with_chroot" is flaky' from 'a

Processed: gdcm: please drop mono support

2024-08-28 Thread Debian Bug Tracking System
Processing control commands: > block 1010445 by -1 Bug #1010445 [mono-complete] mono-complete: Mono package in Debian is very outdated (6.8 but should be 6.12) 1010445 was blocked by: 1079881 1079882 1079883 1010445 was blocking: 1033828 Added blocking bug(s) of 1010445: 1079884 -- 1010445: htt

Bug#1079702: Both autopkgtest are flaky

2024-08-28 Thread Reinhard Tartler
retitle -1 test_with_chroot is flaky Hi, Seems I made a mistake in my previous report. It is actually the test 'test_without_chroot' that is flaky. Also, I noticed this comment in https://sources.debian.org/src/reform-setup-wizard/1.0-11/debian/tests/control/#L7-L25: # Since this test is ski

Processed: kamailio: please drop mono support

2024-08-28 Thread Debian Bug Tracking System
Processing control commands: > block 1010445 by -1 Bug #1010445 [mono-complete] mono-complete: Mono package in Debian is very outdated (6.8 but should be 6.12) 1010445 was blocked by: 1079881 1010445 was blocking: 1033828 Added blocking bug(s) of 1010445: 1079882 -- 1010445: https://bugs.debian

Processed: libsbml: please drop mono support

2024-08-28 Thread Debian Bug Tracking System
Processing control commands: > block 1010445 by -1 Bug #1010445 [mono-complete] mono-complete: Mono package in Debian is very outdated (6.8 but should be 6.12) 1010445 was blocked by: 1079881 1079882 1010445 was blocking: 1033828 Added blocking bug(s) of 1010445: 1079883 -- 1010445: https://bug

Processed: uwsgi: please drop mono support

2024-08-28 Thread Debian Bug Tracking System
Processing control commands: > block 1010445 by -1 Bug #1010445 [mono-complete] mono-complete: Mono package in Debian is very outdated (6.8 but should be 6.12) 1010445 was not blocked by any bugs. 1010445 was blocking: 1033828 Added blocking bug(s) of 1010445: 1079881 -- 1010445: https://bugs.d

Bug#1079874: valgrind: FTBFS with mpich instead of openmpi

2024-08-28 Thread Graham Inggs
Source: valgrind Version: 1:3.20.0-2.1 Severity: serious Tags: ftbfs Hi Maintainer Since the upload of mpi-defaults 1.17, switching the default MPI on 32-bit architectures, valgrind FTBFS [1][2]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.

Bug#1079604: epics-base:FTBFS:build failure (not support riscv64)

2024-08-28 Thread Andrius Merkys
Hi Yue, On 2024-08-25 08:24, Yue Gui wrote: Dear epics-base Maintainer, The package epics-base build failed on arch riscv64.The crucial buildd log below: [snip] My solution to this issue: Add riscv64 support for this package. I have completed the development of the patch for supporting the

Bug#1010445: mono-complete: Mono package in Debian is very outdated (6.8 but should be 6.12)

2024-08-28 Thread Andrey Rakhmatullin
On Wed, Aug 28, 2024 at 12:59:42PM +0200, Chris Hofstaedtler wrote: > > > > If mono should be removed > > > That's the question that needs to be answered somehow, first. > > > It got another FTBFS bug (#1075284) recently. I've just tried to check > > which packages need mono, with `reverse-depends

Bug#1010445: mono-complete: Mono package in Debian is very outdated (6.8 but should be 6.12)

2024-08-28 Thread Chris Hofstaedtler
* Andrey Rakhmatullin [240828 11:54]: > On Thu, Jul 18, 2024 at 07:22:03PM +0200, Chris Hofstaedtler wrote: > > On Thu, Jul 18, 2024 at 06:55:03PM +0200, Paul Gevers wrote: > > > If mono should be removed > > That's the question that needs to be answered somehow, first. > It got another FTBFS bug

Bug#1073390: marked as done (python-docxcompose: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" --test-pytest returned exit code 13)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 09:35:09 + with message-id and subject line Bug#1073390: fixed in python-docxcompose 1.4.0-2 has caused the Debian Bug report #1073390, regarding python-docxcompose: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11"

Bug#1079522: marked as done (software-properties: FTBFS in unstable (setuptools 73?): invalid command 'test')

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 10:34:19 +0100 with message-id and subject line Re: Bug#1079522: software-properties: FTBFS in unstable (setuptools 73?): invalid command 'test' has caused the Debian Bug report #1079522, regarding software-properties: FTBFS in unstable (setuptools 73?): invali

Bug#1010445: mono-complete: Mono package in Debian is very outdated (6.8 but should be 6.12)

2024-08-28 Thread Andrey Rakhmatullin
On Thu, Jul 18, 2024 at 07:22:03PM +0200, Chris Hofstaedtler wrote: > On Thu, Jul 18, 2024 at 06:55:03PM +0200, Paul Gevers wrote: > > Release Team member here. mono is a key package [1], meaning it's hard to > > remove. I note that src:mono is at least needed for src:gdcm which is at > > least nee

Processed: reassign 1079852 to ruby-google-protobuf

2024-08-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1079852 ruby-google-protobuf 3.25.4-1 Bug #1079852 [ruby-google-prorobuf] ruby-google-protobuf: no longer builds protobuf_c.so Warning: Unknown package 'ruby-google-prorobuf' Bug reassigned from package 'ruby-google-prorobuf' to 'ruby-go

Bug#915072: marked as done (keysafe: build-depends on many no longer available libghc-*-dev versions)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 11:28:34 +0200 with message-id <20240828092834.qgwxs2j5sy33k...@jwilk.net> and subject line Re: Bug#915072: keysafe: build-depends on many no longer available libghc-*-dev versions has caused the Debian Bug report #915072, regarding keysafe: build-depends on man

Bug#1078248: marked as done ("sequoia-octopus: rnp_identifier_iterator_create: parameter "ctx" is null" with thunderbird 115.13.0-1)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 09:24:55 + with message-id and subject line Bug#1078248: fixed in rust-sequoia-octopus-librnp 1.10.0-1 has caused the Debian Bug report #1078248, regarding "sequoia-octopus: rnp_identifier_iterator_create: parameter "ctx" is null" with thunderbird 115.13.0-

Processed: Bug#1073390 marked as pending in python-docxcompose

2024-08-28 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1073390 [src:python-docxcompose] python-docxcompose: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" --test-pytest returned exit code 13 Added tag(s) pending. -- 1073390: https://bugs.debian.org/cgi-b

Bug#1073390: marked as pending in python-docxcompose

2024-08-28 Thread Andrius Merkys
Control: tag -1 pending Hello, Bug #1073390 in python-docxcompose 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/python-docxcompose/-/comm

Bug#1077522: marked as done (crossfire: FTBFS: cfpython_archetype.c:136:5: error: initialization of 'long int' from 'void *' makes integer from pointer without a cast [-Wint-conversion])

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 09:04:04 + with message-id and subject line Bug#1077522: fixed in crossfire 1.75.0-8 has caused the Debian Bug report #1077522, regarding crossfire: FTBFS: cfpython_archetype.c:136:5: error: initialization of 'long int' from 'void *' makes integer from poin

Bug#1079845: Should vagrant-bindfs be removed from unstable?

2024-08-28 Thread Jonas Meurer
Control: severity -1 normal Control: retitle -1 RM: vagrant-bindfs -- RoM; rc-buggy Control: reassign -1 ftp.debian.org Thanks Helmut for bringing this up. Helmut Grohne wrote: Source: vagrant-bindfs Severity: serious Justification: grab attention of maintainer User: helm...@debian.org Usertags

Processed: Re: Bug#1079845: Should vagrant-bindfs be removed from unstable?

2024-08-28 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #1079845 [src:vagrant-bindfs] Should vagrant-bindfs be removed from unstable? Severity set to 'normal' from 'serious' > retitle -1 RM: vagrant-bindfs -- RoM; rc-buggy Bug #1079845 [src:vagrant-bindfs] Should vagrant-bindfs be removed from uns

Bug#1079719: marked as done (python-ipywidgets-doc: uninstallable; depends on unpackaged node-jupyter-widgets-html-manager)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 08:10:13 + with message-id and subject line Bug#1079719: fixed in node-ipydatagrid 1.3.2+~cs14.21.116-1 has caused the Debian Bug report #1079719, regarding python-ipywidgets-doc: uninstallable; depends on unpackaged node-jupyter-widgets-html-manager to be

Bug#1075460: marked as done (ruby-gnome: ftbfs with GCC-14)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 08:10:17 + with message-id and subject line Bug#1075460: fixed in ruby-gnome 4.2.2-1 has caused the Debian Bug report #1075460, regarding ruby-gnome: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1079840: marked as done (unsatisfied build dependency in testing: python3-ruff)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 07:34:39 + with message-id and subject line Bug#1079840: fixed in python-aiounifi 79-3 has caused the Debian Bug report #1079840, regarding unsatisfied build dependency in testing: python3-ruff to be marked as done. This means that you claim that the proble

Bug#1079840: marked as done (unsatisfied build dependency in testing: python3-ruff)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 07:34:05 + with message-id and subject line Bug#1079840: fixed in python-aioairq 0.4.2-3 has caused the Debian Bug report #1079840, regarding unsatisfied build dependency in testing: python3-ruff to be marked as done. This means that you claim that the prob

Bug#1079839: marked as done (unsatisfied build dependency in testing: python3-ruff)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 07:34:13 + with message-id and subject line Bug#1079839: fixed in python-aioairzone-cloud 0.6.1-3 has caused the Debian Bug report #1079839, regarding unsatisfied build dependency in testing: python3-ruff to be marked as done. This means that you claim that

Bug#1079837: marked as done (unsatisfied build dependency in testing: python3-ruff)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 07:34:31 + with message-id and subject line Bug#1079837: fixed in python-aiohue 4.7.2-3 has caused the Debian Bug report #1079837, regarding unsatisfied build dependency in testing: python3-ruff to be marked as done. This means that you claim that the probl

Bug#1079838: marked as done (unsatisfied build dependency in testing: python3-ruff)

2024-08-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Aug 2024 07:34:22 + with message-id and subject line Bug#1079838: fixed in python-aioambient 2024.1.0-3 has caused the Debian Bug report #1079838, regarding unsatisfied build dependency in testing: python3-ruff to be marked as done. This means that you claim that th

Bug#1064024: juce: FTBFS on mips64el: Failed to build juceaide

2024-08-28 Thread Andrius Merkys
Hello, It seems that the global offset table gets exceeded for mips64el even with -mxgot. As the trixie freeze is drawing near I would suggest RMing juce binaries (and their reverse dependencies) for mips64el for the time being. Andrius