Bug#1071007:

Hi Samuel! I hope you are well! I'm sorry for responding so late. I had a problem with my laptop keyboard. I just pushed a new version of shelock with a fix for the problem in the "master" branch. If that's ok, I'll do a merge. https://salsa.debian.org/pkg-security-team/sherlock/-/tree/master?ref

Bug#1071552: marked as done (GnuPG 2.2.42+ breaks emacs' EasyPG)

Your message dated Sat, 01 Jun 2024 00:19:14 + with message-id and subject line Bug#1071552: fixed in gnupg2 2.2.43-7 has caused the Debian Bug report #1071552, regarding GnuPG 2.2.42+ breaks emacs' EasyPG to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#1071552: [pkg-gnupg-maint] Bug#1071552: Bug#1071552: gnupg: Please upgrade GnuPG >= 2.4.4, current GnuPG break Emacs's EasyPG

On Thu 2024-05-30 18:34:13 +0200, Andreas Metzler wrote: > the issue report refers to two patches, one of these is already part of > 2.2.43. The other one[1] seemed pretty straightforward to backport > (functions moved to other files and cipher_filter_ocb instead of > cipher_filter_aead). I would a

Bug#1057598: marked as done (python-pynndescent: FTBFS: ImportError: Numba could not be imported.)

Your message dated Fri, 31 May 2024 23:19:43 + with message-id and subject line Bug#1057598: fixed in python-pynndescent 0.5.11-1 has caused the Debian Bug report #1057598, regarding python-pynndescent: FTBFS: ImportError: Numba could not be imported. to be marked as done. This means that you

Bug#1067303: marked as done (trash-cli: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)

Your message dated Fri, 31 May 2024 22:38:54 + with message-id and subject line Bug#1067303: fixed in trash-cli 0.24.5.26-0.1 has caused the Debian Bug report #1067303, regarding trash-cli: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code

Bug#1063647: sysconfig: missing required debian/rules targets build-arch and/or build-indep

I am uploading a NMU to DELAYED/10 in order to fix this.diff -Nru sysconfig-0.0.14/debian/changelog sysconfig-0.0.14+nmu1/debian/changelog --- sysconfig-0.0.14/debian/changelog 2020-12-06 22:13:54.0 + +++ sysconfig-0.0.14+nmu1/debian/changelog 2024-05-31 22:22:45.0 +00

Bug#1072175: marked as done (texlive-lang-japanese: missing Breaks+Replaces: texlive-binaries (<< 2024))

Your message dated Sat, 1 Jun 2024 00:07:22 +0200 with message-id <85a980e0-6587-44b4-8e46-29ec45d50...@web.de> and subject line Re: Bug#1072175: texlive-lang-japanese: missing Breaks+Replaces: texlive-binaries (<< 2024) has caused the Debian Bug report #1072175, regarding texlive-lang-japanese: m

Processed: tagging 1071182

Processing commands for cont...@bugs.debian.org: > tags 1071182 + pending Bug #1071182 [src:dracut] dracut: requires changes for systemd 256; boot fails otherwise Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1071182: https://bugs.debian.o

Processed: your mail

Processing commands for cont...@bugs.debian.org: > fixed 1070910 1:18.1.6-1 Bug #1070910 [src:llvm-toolchain-18] llvm-toolchain-18: autopkgtest fails on amd64 Marked as fixed in versions llvm-toolchain-18/1:18.1.6-1. > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: azure-cli: autopkgtest regression with pytest 8.2

Processing control commands: > forwarded -1 https://github.com/Azure/azure-cli/issues/28848 Bug #1072312 [src:azure-cli] azure-cli: autopkgtest regression with pytest 8.2 Set Bug forwarded-to-address to 'https://github.com/Azure/azure-cli/issues/28848'. -- 1072312: https://bugs.debian.org/cgi-b

Bug#1072312: azure-cli: autopkgtest regression with pytest 8.2

Source: azure-cli Version: 2.61.0-1 Severity: serious Tags: upstream Control: forwarded -1 https://github.com/Azure/azure-cli/issues/28848 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, the azure-cli package misuses the __init__ method in unittest.TestCase subclasses to setup

Bug#1059223: marked as done (src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386)

Your message dated Fri, 31 May 2024 22:26:47 +0200 with message-id and subject line Re: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386 has caused the Debian Bug report #1059223, regarding src:meson: fails to migrate to testing for too long: fails autopkg

Bug#1072310: nheko: FTBFS on armhf: virtual memory exhausted: Cannot allocate memory

Source: nheko Version: 0.11.3+~0.9.2+~1.0.0+~0.3.0-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=nheko&arch=armhf&ver=0.11.3%2B%7E0.9.2%2B%7E1.0.0%2B%7

Bug#1072309: neochat: Depends: qml-module-org-kde-kirigami-addons-delegates but it is not installable

Package: neochat Version: 23.08.5-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org The dependencies of neochat cannot be satisfied: $ apt install neochat ... Unsatisfied dependencies: neochat : Depends: qml-module-org-kde-kirigami-addons-delegates but it is not installable Depe

Processed: src:coq: fails to migrate to testing for too long: autopkgtest issues due to dependencies

Processing control commands: > close -1 8.19.1+dfsg-1 Bug #1072308 [src:coq] src:coq: fails to migrate to testing for too long: autopkgtest issues due to dependencies Marked as fixed in versions coq/8.19.1+dfsg-1. Bug #1072308 [src:coq] src:coq: fails to migrate to testing for too long: autopkgt

Bug#1072308: src:coq: fails to migrate to testing for too long: autopkgtest issues due to dependencies

Source: coq Version: 8.18.0+dfsg-1 Severity: serious Control: close -1 8.19.1+dfsg-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 day

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tags #1064720 pending Bug #1064720 [src:ruby-capybara] ruby-capybara: FTBFS: ERROR: Test "ruby3.1" failed: NoMethodError: Added tag(s) pending. > tags #1045929 pending Bug #1045929 [src:ruby-capybara] ruby-capybara: Fails to build source after s

Processed: src:r-cran-rcppparallel: fails to migrate to testing for too long: autopkgtest regression

Processing control commands: > close -1 5.1.7+dfsg-4 Bug #1072306 [src:r-cran-rcppparallel] src:r-cran-rcppparallel: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions r-cran-rcppparallel/5.1.7+dfsg-4. Bug #1072306 [src:r-cran-rcppparallel] src:r-cran-rcp

Processed: src:nvptx-tools: fails to migrate to testing for too long: BD on llvm-toolchain-18 binaries

Processing control commands: > close -1 0.20240423-1 Bug #1072307 [src:nvptx-tools] src:nvptx-tools: fails to migrate to testing for too long: BD on llvm-toolchain-18 binaries Marked as fixed in versions nvptx-tools/0.20240423-1. Bug #1072307 [src:nvptx-tools] src:nvptx-tools: fails to migrate to

Bug#1072307: src:nvptx-tools: fails to migrate to testing for too long: BD on llvm-toolchain-18 binaries

Source: nvptx-tools Version: 0.20230904-1 Severity: serious Control: close -1 0.20240423-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

Bug#1072306: src:r-cran-rcppparallel: fails to migrate to testing for too long: autopkgtest regression

Source: r-cran-rcppparallel Version: 5.1.7+dfsg-3 Severity: serious Control: close -1 5.1.7+dfsg-4 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 mo

Processed: src:culmus-fancy: fails to migrate to testing for too long: uploader built arch:all binaries

Processing control commands: > close -1 0.0.20240129 Bug #1072305 [src:culmus-fancy] src:culmus-fancy: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions culmus-fancy/0.0.20240129. Bug #1072305 [src:culmus-fancy] src:culmus-fancy: fails to migra

Bug#1072305: src:culmus-fancy: fails to migrate to testing for too long: uploader built arch:all binaries

Source: culmus-fancy Version: 0.0.20140315-1 Severity: serious Control: close -1 0.0.20240129 Tags: sid trixie pending 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

Processed: src:gnome-shell-extension-appindicator: fails to migrate to testing for too long: versioned dependency not in unstable

Processing control commands: > close -1 58-1 Bug #1072304 [src:gnome-shell-extension-appindicator] src:gnome-shell-extension-appindicator: fails to migrate to testing for too long: versioned dependency not in unstable Marked as fixed in versions gnome-shell-extension-appindicator/58-1. Bug #1072

Bug#1072304: src:gnome-shell-extension-appindicator: fails to migrate to testing for too long: versioned dependency not in unstable

Source: gnome-shell-extension-appindicator Version: 53-2 Severity: serious Control: close -1 58-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1071926 Dear maintainer(s), The Release Team considers packages that are out-of-sync between

Processed: src:libmaus2: fails to migrate to testing for too long: FTBFS on arm64

Processing control commands: > close -1 2.0.813+ds-3 Bug #1072303 [src:libmaus2] src:libmaus2: fails to migrate to testing for too long: FTBFS on arm64 Marked as fixed in versions libmaus2/2.0.813+ds-3. Bug #1072303 [src:libmaus2] src:libmaus2: fails to migrate to testing for too long: FTBFS on

Bug#1072303: src:libmaus2: fails to migrate to testing for too long: FTBFS on arm64

Source: libmaus2 Version: 2.0.813+ds-1 Severity: serious Control: close -1 2.0.813+ds-3 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1069691 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing a

Processed: src:gnome-shell-mailnag: fails to migrate to testing for too long: versioned dependency not yet in unstable

Processing control commands: > close -1 40.0-7 Bug #1072302 [src:gnome-shell-mailnag] src:gnome-shell-mailnag: fails to migrate to testing for too long: versioned dependency not yet in unstable Marked as fixed in versions gnome-shell-mailnag/40.0-7. Bug #1072302 [src:gnome-shell-mailnag] src:gnom

Bug#1072302: src:gnome-shell-mailnag: fails to migrate to testing for too long: versioned dependency not yet in unstable

Source: gnome-shell-mailnag Version: 40.0-5 Severity: serious Control: close -1 40.0-7 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 d

Processed: found 1037068 in 2.0.53-6.1, found 1072073 in 1.23.0-1, found 1072073 in 0.4.8-1 ...

Processing commands for cont...@bugs.debian.org: > found 1037068 2.0.53-6.1 Bug #1037068 [sysrepo] sysrepo: world-writable /etc/sysrepo/* after upgrade from 1.4.70-4 in bullseye Marked as found in versions sysrepo/2.0.53-6.1. > found 1072073 1.23.0-1 Bug #1072073 [python3-proto-plus,nanopb] pytho

Bug#1066342: marked as done (eterm: FTBFS: libscream.c:3231:16: error: implicit declaration of function ‘safe_print_string’ [-Werror=implicit-function-declaration])

Your message dated Fri, 31 May 2024 18:49:11 + with message-id and subject line Bug#1066342: fixed in eterm 0.9.6-7.2 has caused the Debian Bug report #1066342, regarding eterm: FTBFS: libscream.c:3231:16: error: implicit declaration of function ‘safe_print_string’ [-Werror=implicit-function-

Bug#1060623: marked as done (pacemaker: Please switch Build-Depends to systemd-dev)

Your message dated Fri, 31 May 2024 18:28:23 + with message-id and subject line Bug#1060623: fixed in pacemaker 2.1.8~rc1-1 has caused the Debian Bug report #1060623, regarding pacemaker: Please switch Build-Depends to systemd-dev to be marked as done. This means that you claim that the probl

Bug#1072012: libxml-libxml-perl: new upstream release 2.0210, addressing test failures with libxml2 >= 2.11

On Wed, 29 May 2024 23:15:10 +0300, Niko Tyni wrote: > But I think we should add dependency metadata so that the release team, > britney, debci etc. can see the need for a rebuild when we have a > "broken" combination, and then hint the "correct" versions for testing > migration together. Updatin

Bug#1066575: marked as done (kakasi: FTBFS: configure: error: can not use EUC-JP or UTF-8 encoding on iconv)

Your message dated Fri, 31 May 2024 18:02:18 + with message-id and subject line Bug#1066575: fixed in kakasi 2.3.6-4.2 has caused the Debian Bug report #1066575, regarding kakasi: FTBFS: configure: error: can not use EUC-JP or UTF-8 encoding on iconv to be marked as done. This means that you

Bug#1072283: marked as done (chromium: Chromium FTBFS Depends: rustc-web but it is not installable)

Your message dated Fri, 31 May 2024 13:24:18 -0400 with message-id <470a5fc4-a955-4399-8709-0dfb558f7...@queued.net> and subject line Re: Bug#1072283: chromium: Chromium FTBFS Depends: rustc-web but it is not installable has caused the Debian Bug report #1072283, regarding chromium: Chromium FTBFS

Bug#1065633: marked as done (openldap: FTBFS on hppa - implicit declaration of function ‘kadm5_s_init_with_password_ctx’)

Your message dated Fri, 31 May 2024 15:05:20 + with message-id and subject line Bug#1065633: fixed in openldap 2.6.8+dfsg-1~exp1 has caused the Debian Bug report #1065633, regarding openldap: FTBFS on hppa - implicit declaration of function ‘kadm5_s_init_with_password_ctx’ to be marked as don

Bug#1072290: systemd prevent system to boot if /etc/fstab as an /tmp entry

Control: severity -1 minor Control: tags -1 moreinfo On Fri, 31 May 2024 16:42:38 +0200 eric wrote: > Package: systemd > Version: 256~rc3-6 > Severity: critical > Justification: breaks the whole system > > > if I let this entry in /etc/fstab > UUID=x /tmp    ext4    defaults,discard

Processed: Re: systemd prevent system to boot if /etc/fstab as an /tmp entry

Processing control commands: > severity -1 minor Bug #1072290 [systemd] systemd prevent system to boot if /etc/fstab as an /tmp entry Severity set to 'minor' from 'critical' > tags -1 moreinfo Bug #1072290 [systemd] systemd prevent system to boot if /etc/fstab as an /tmp entry Added tag(s) morei

Bug#1072290: systemd prevent system to boot if /etc/fstab as an /tmp entry

Package: systemd Version: 256~rc3-6 Severity: critical Justification: breaks the whole system if I let this entry in /etc/fstab UUID=x /tmpext4defaults,discard,noatime,nodiratime 0 2 System does not boot -- Package-specific info: -- System Information: Debian Release: tr

Bug#1071336: psensor: FTBFS: FAIL test-cppcheck.sh

Thanks Gianfranco Thanks Santiago I had upload to: https://mentors.debian.net/package/psensor/ Welcome to review and upload. Regards, 在 2024/5/31 20:49, Gianfranco Costamagna 写道: At the end I think I also fixed with upstream merge_request 31 the failure So, changes (attached) are: 1) add u

Processed: severity of 1072280 is serious

Processing commands for cont...@bugs.debian.org: > # The libmatio transition has started > severity 1072280 serious Bug #1072280 [src:labplot] FTBFS against libmatio 1.5.27 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#1026222: marked as done (golang-google-genproto: switch B-D to golang-github-golang-protobuf-1-5-dev)

Your message dated Fri, 31 May 2024 13:19:19 + with message-id and subject line Bug#1026222: fixed in golang-google-genproto 0.0~git20210726.e7812ac-2 has caused the Debian Bug report #1026222, regarding golang-google-genproto: switch B-D to golang-github-golang-protobuf-1-5-dev to be marked

Bug#1072115: marked as done (ERROR:: Failure to read or parse /usr/share/coot/ui/coot-gtk4.ui)

Your message dated Fri, 31 May 2024 12:49:25 + with message-id and subject line Bug#1072115: fixed in coot 1.1.08+dfsg-3 has caused the Debian Bug report #1072115, regarding ERROR:: Failure to read or parse /usr/share/coot/ui/coot-gtk4.ui to be marked as done. This means that you claim that t

Bug#1071336: psensor: FTBFS: FAIL test-cppcheck.sh

At the end I think I also fixed with upstream merge_request 31 the failure So, changes (attached) are: 1) add unity integration B-D 2) add 30.patch proposed upstream to fix FTBFS when building twice 3) add 31.patch proposed upstream to fix FTBFS with parallel builds. G. diff Description: Bina

Bug#1071336: psensor: FTBFS: FAIL test-cppcheck.sh

Also please consider making it build twice with this simple patch deleting the manpages https://gitlab.com/jeanfi/psensor/-/merge_requests/30 Fixing bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045882 Il venerdì 31 maggio 2024 alle ore 14:20:33 CEST, Gianfranco Costamagna ha scri

Processed: clone 1072115

Processing commands for cont...@bugs.debian.org: > clone 1072115 -1 Bug #1072115 [coot] ERROR:: Failure to read or parse /usr/share/coot/ui/coot-gtk4.ui Bug 1072115 cloned as bug 1072286 > retitle -1 coot: add autopkgtest for coot executable Bug #1072286 [coot] ERROR:: Failure to read or parse /

Bug#1071336: psensor: FTBFS: FAIL test-cppcheck.sh

Disabling lto, forcing parallel=1 and adding libunity-dev made it build on every architecture on Ubuntu :) G. Il venerdì 31 maggio 2024 alle ore 14:10:43 CEST, Santiago Vila ha scritto: El 31/5/24 a las 13:41, xiao sheng wen(肖盛文) escribió: > Hi Santiago, > >      Would you report a

Bug#1071319: marked as done (libapache2-mod-auth-openidc: FTBFS: test/test fails)

Your message dated Fri, 31 May 2024 12:19:18 + with message-id and subject line Bug#1071319: fixed in libapache2-mod-auth-openidc 2.4.15.7-2 has caused the Debian Bug report #1071319, regarding libapache2-mod-auth-openidc: FTBFS: test/test fails to be marked as done. This means that you claim

Bug#1071336: psensor: FTBFS: FAIL test-cppcheck.sh

El 31/5/24 a las 13:41, xiao sheng wen(肖盛文) escribió: Hi Santiago,     Would you report a new bug about this FTBFS on arm64 arch? As Bug#1071336 is closed now. Well, don't worry, it was not my intention to mix two problems in the same report, only to make you aware of the build failure. The

Bug#1071336: psensor: FTBFS: FAIL test-cppcheck.sh

Hello, I checked in Ubuntu, we fail due to lto being enabled (gcc crashes) and in Debian arch:all and arch:arm64. To me looks like some concurrent issue https://launchpad.net/ubuntu/+source/psensor/1.2.1-1ubuntu1 In ubuntu the same failures happens on more archs, so maybe this isn't deterministic

Processed: Bug#1071319 marked as pending in libapache2-mod-auth-openidc

Processing control commands: > tag -1 pending Bug #1071319 [src:libapache2-mod-auth-openidc] libapache2-mod-auth-openidc: FTBFS: test/test fails Added tag(s) pending. -- 1071319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071319 Debian Bug Tracking System Contact ow...@bugs.debian.org w

Processed: reassign 1071319 to src:libapache2-mod-auth-openidc

Processing commands for cont...@bugs.debian.org: > reassign 1071319 src:libapache2-mod-auth-openidc Bug #1071319 [src:cjose] libapache2-mod-auth-openidc: FTBFS: test/test fails Bug reassigned from package 'src:cjose' to 'src:libapache2-mod-auth-openidc'. No longer marked as found in versions cjose

Bug#1071319: marked as pending in libapache2-mod-auth-openidc

Control: tag -1 pending Hello, Bug #1071319 in libapache2-mod-auth-openidc 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/debian/libapache2-mod-auth-openidc/-

Bug#1071336: psensor: FTBFS: FAIL test-cppcheck.sh

Hi Santiago,     Would you report a new bug about this FTBFS on arm64 arch? As Bug#1071336 is closed now. Cc to Debian arm ports maillist debian-...@lists.debian.org is also ok. This build failed only take palace under arm64 arch. I has a arm64 box, I'll try build later. Thanks! 在 2024/5/31

Bug#1071893: marked as done (sagetex: FTBFS: unsatisfiable build-dependencies)

Your message dated Fri, 31 May 2024 11:34:28 + with message-id and subject line Bug#1071893: fixed in ipywidgets 8.1.2-3 has caused the Debian Bug report #1071893, regarding sagetex: FTBFS: unsatisfiable build-dependencies to be marked as done. This means that you claim that the problem has b

Bug#1069859: marked as pending in aide

Control: tag -1 pending Hello, Bug #1069859 in aide 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/debian/atop/-/commit/4528eb00760386573500673c22455c6145e2c11

Processed: Bug#1069859 marked as pending in aide

Processing control commands: > tag -1 pending Bug #1069859 [atop] atop: Fix atop for 64-bit time_t on arm Added tag(s) pending. -- 1069859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069859 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1072244: marked as done (Segmentation fault on startup)

Your message dated Fri, 31 May 2024 11:22:50 + with message-id and subject line Bug#1072244: fixed in wxglade 1.1.0a3+repack-1 has caused the Debian Bug report #1072244, regarding Segmentation fault on startup to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1070256: marked as done (libcxx-serial FTBFS with the nocheck build profile)

Your message dated Fri, 31 May 2024 11:21:59 + with message-id and subject line Bug#1070256: fixed in libcxx-serial 1.2.1-8 has caused the Debian Bug report #1070256, regarding libcxx-serial FTBFS with the nocheck build profile to be marked as done. This means that you claim that the problem

Processed: Bug#1071893 marked as pending in ipywidgets

Processing control commands: > tag -1 pending Bug #1071893 [python3-ipywidgets] sagetex: FTBFS: unsatisfiable build-dependencies Added tag(s) pending. -- 1071893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071893 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1071893: marked as pending in ipywidgets

Control: tag -1 pending Hello, Bug #1071893 in ipywidgets 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/ipywidgets/-/commit/05c8043c28609

Bug#1072163: marked as done (libxmlrpc-core-c3-dev: Missing dependency on libxmlrpc-util-dev)

Your message dated Fri, 31 May 2024 11:05:59 + with message-id and subject line Bug#1072163: fixed in xmlrpc-c 1.59.03-4 has caused the Debian Bug report #1072163, regarding libxmlrpc-core-c3-dev: Missing dependency on libxmlrpc-util-dev to be marked as done. This means that you claim that th

Bug#1072283: chromium: Chromium FTBFS Depends: rustc-web but it is not installable

Package: chromium Version: 125.0.6422.112-1~deb12u1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, * What led up to the situation? Tried to build chromium * What exactly did you do (or not do) that was effectiv

Processed: Re: adios4dolfinx: FTBFS: failing tests

Processing control commands: > severity 1071722 important Bug #1071722 [src:adios4dolfinx] adios4dolfinx: FTBFS: failing tests Severity set to 'important' from 'serious' -- 1071722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071722 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1071722: adios4dolfinx: FTBFS: failing tests

Source: adios4dolfinx Followup-For: Bug #1071722 Control: severity 1071722 important This bug appears to arise from how openmpi needs to be invoked on a specific system. It doesn't affect all systems, and doesn't affect debian buildds or debci, so downgrading severity.

Bug#1071397: marked as done (src:ngspetsc: unsatisfied build dependency in testing: fenicsx)

Your message dated Fri, 31 May 2024 12:21:09 +0200 with message-id <19189d438aeedc6d7a594af2ba6de...@debian.org> and subject line Re: Bug#1071397 src:ngspetsc: unsatisfied build dependency in testing: fenicsx has caused the Debian Bug report #1071397, regarding src:ngspetsc: unsatisfied build depe

Bug#1071336: psensor: FTBFS: FAIL test-cppcheck.sh

I fixed bug in salsa: https://salsa.debian.org/atzlinux-guest/psensor/-/commit/8da335a77089e65b265f09e39732bc60005c6f15 Reuploaded: https://mentors.debian.net/package/psensor/ Thanks a lot. I built it in my test machine (only once) and now it didn't fail. Now you might want to look at this:

Bug#1060522: marked as done (onedrive: Please switch Build-Depends to systemd-dev)

Your message dated Fri, 31 May 2024 10:03:56 + with message-id and subject line Bug#1060522: fixed in onedrive 2.4.25-2 has caused the Debian Bug report #1060522, regarding onedrive: Please switch Build-Depends to systemd-dev to be marked as done. This means that you claim that the problem ha

Bug#1071829: marked as done (fail2ban: spurious ">" character in paths-debian.conf)

Your message dated Fri, 31 May 2024 10:41:18 +0100 with message-id and subject line Re: Bug#1071829: fail2ban: spurious ">" character in paths-debian.conf has caused the Debian Bug report #1071829, regarding fail2ban: spurious ">" character in paths-debian.conf to be marked as done. This means t

Bug#1060569: marked as done (fail2ban: Please switch Build-Depends to systemd-dev)

Your message dated Fri, 31 May 2024 10:35:05 +0100 with message-id and subject line Re: Bug#1060569: fail2ban: Please switch Build-Depends to systemd-dev has caused the Debian Bug report #1060569, regarding fail2ban: Please switch Build-Depends to systemd-dev to be marked as done. This means tha

Bug#1069027: Fixed upstream

This is fixed upstream in Jupyter Notebook 6.5.6 per https://github.com/jupyter/notebook/issues/7054 Best regards Thomas

Bug#1072241: src:manpages: fails to migrate to testing for too long: RC bug and B-D not in testing

Am 30.05.24 um 22:30 schrieb Paul Gevers: Source: manpages Version: 6.05.01-1 Severity: serious Control: close -1 6.8-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1072158 Dear maintainer(s), The Release Team considers packages that a

Processed: severity of 1071988 is important

Processing commands for cont...@bugs.debian.org: > severity 1071988 important Bug #1071988 [radicale] radicale: After upgrade, radicale fails to serve calendar: An exception occurred during GET request Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me

Processed: Re: Bug#1071988: radicale: After upgrade, radicale fails to serve calendar: An exception occurred during GET request

Processing control commands: > forwarded -1 https://github.com/Kozea/Radicale/issues/1498 Bug #1071988 [radicale] radicale: After upgrade, radicale fails to serve calendar: An exception occurred during GET request Set Bug forwarded-to-address to 'https://github.com/Kozea/Radicale/issues/1498'. -

Bug#1071988: radicale: After upgrade, radicale fails to serve calendar: An exception occurred during GET request

Control: forwarded -1 https://github.com/Kozea/Radicale/issues/1498 Quoting Ralf Jung (2024-05-31 09:08:30) > Yeah I reported this upstream in the mean time: > Thanks for confirming. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt

Bug#1072201: marked as done (rtags: autopkgtest failure due to missing depends on emacs)

Your message dated Fri, 31 May 2024 07:19:27 + with message-id and subject line Bug#1072201: fixed in rtags 2.38-11 has caused the Debian Bug report #1072201, regarding rtags: autopkgtest failure due to missing depends on emacs to be marked as done. This means that you claim that the problem

Bug#1071988: radicale: After upgrade, radicale fails to serve calendar: An exception occurred during GET request

Dear Jonas, Thanks for taking a look! Yeah I reported this upstream in the mean time: Kind regards, Ralf

Bug#1072012: libxml-libxml-perl: new upstream release 2.0210, addressing test failures with libxml2 >= 2.11

Hi, On Thu, May 30, 2024 at 4:15 AM Niko Tyni wrote: > > On Wed, May 29, 2024 at 02:16:47PM +0800, Aron Xu wrote: > > On Wed, May 29, 2024 at 12:16 AM gregor herrmann wrote: > > > > Warning: program compiled against libxml 212 using older 209 > > > > > > and this comes from libxml: > > > > > > h

Bug#1071336: marked as done (psensor: FTBFS: FAIL test-cppcheck.sh)

Your message dated Fri, 31 May 2024 07:05:01 + with message-id and subject line Bug#1071336: fixed in psensor 1.2.1-1 has caused the Debian Bug report #1071336, regarding psensor: FTBFS: FAIL test-cppcheck.sh to be marked as done. This means that you claim that the problem has been dealt with

Processed: Re: dracut: requires changes for systemd 256; boot fails otherwise

Processing control commands: > reopen -1 Bug #1071182 {Done: Thomas Lange } [src:dracut] dracut: requires changes for systemd 256; boot fails otherwise Bug reopened Ignoring request to alter fixed versions of bug #1071182 to the same values previously set > tags -1 patch Bug #1071182 [src:dracut

Bug#1071182: dracut: requires changes for systemd 256; boot fails otherwise

Control: reopen -1 Control: tags -1 patch Just to clarify, the original report mentiones two changes required for systemd 256: | 1. systemd 256 makes /usr read-only in initrd: |- https://github.com/systemd/systemd/issues/32511 |- https://github.com/dracut-ng/dracut-ng/issues/253 | | 2

Processed: src:skimage: fails to migrate to testing for too long: FTBFS on mips64el

Processing control commands: > close -1 0.23.2-1 Bug #1072271 [src:skimage] src:skimage: fails to migrate to testing for too long: FTBFS on mips64el Marked as fixed in versions skimage/0.23.2-1. Bug #1072271 [src:skimage] src:skimage: fails to migrate to testing for too long: FTBFS on mips64el M

Bug#1072271: src:skimage: fails to migrate to testing for too long: FTBFS on mips64el

Source: skimage Version: 0.22.0-3 Severity: serious Control: close -1 0.23.2-1 Tags: sid trixie ftbfs 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 day