Bug#1106881: elinks: "double free or corruption (fasttop)" in Elinks bookmark manager: writes infinite temporary file

2025-06-07 Thread Johannes Schauer Marin Rodrigues
Control: notfound -1 0.18.0-1 Hi, thank you for your detailed bug report! Fortunately, it seems that this bug does not affect elinks in unstable (and testing). The bookmark directory also moved from ~/.elinks to ~/.config/elinks. I did not investigate which version between 0.13.2-1 and 0.18.0-1

Processed: Re: elinks: "double free or corruption (fasttop)" in Elinks bookmark manager: writes infinite temporary file

2025-06-07 Thread Debian Bug Tracking System
Processing control commands: > notfound -1 0.18.0-1 Bug #1106881 [elinks] elinks: "double free or corruption (fasttop)" in Elinks bookmark manager: writes infinite temporary file Ignoring request to alter found versions of bug #1106881 to the same values previously set -- 1106881: https://bugs

Bug#1099013: emacs-gtk: hangs compositor when used under Wayland

2025-06-07 Thread Paul Gevers
Control: close -1 4:6.3.5-1 On 06-06-2025 10:28, Aurélien COUDERC wrote: I’ve uploaded Plasma 6.3.5 + some further backported commits to unstable, aiming for trixie. Kwin 6.3.5 and upcoming 6.3.6 include a *lot* of fixes so maybe you could give it another try ? I've installed kwin-wayland a

Processed: Re: Bug#1099013: emacs-gtk: hangs compositor when used under Wayland

2025-06-07 Thread Debian Bug Tracking System
Processing control commands: > close -1 4:6.3.5-1 Bug #1099013 [kwin-wayland] emacs-gtk: hangs compositor when used under Wayland Marked as fixed in versions kwin/4:6.3.5-1. Bug #1099013 [kwin-wayland] emacs-gtk: hangs compositor when used under Wayland Marked Bug as done -- 1099013: https://bug

Bug#1104274: marked as done (mlmmj: FTBFS on all archs except amd64, mips64el: broken: Test case body timed out)

2025-06-07 Thread Debian Bug Tracking System
Your message dated Sun, 08 Jun 2025 04:04:16 + with message-id and subject line Bug#1104274: fixed in mlmmj 1.5.2-1 has caused the Debian Bug report #1104274, regarding mlmmj: FTBFS on all archs except amd64, mips64el: broken: Test case body timed out to be marked as done. This means that yo

Bug#1106691: marked as done (mlmmj-php-web-admin is incompatible with PHP 8+)

2025-06-07 Thread Debian Bug Tracking System
Your message dated Sun, 08 Jun 2025 04:04:16 + with message-id and subject line Bug#1106691: fixed in mlmmj 1.5.2-1 has caused the Debian Bug report #1106691, regarding mlmmj-php-web-admin is incompatible with PHP 8+ to be marked as done. This means that you claim that the problem has been de

Processed: pymatgen bugs

2025-06-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > owner 1106436 ! Bug #1106436 [src:pymatgen] pymatgen: FTBFS: TestInterfaceReaction.test_get_entry_energy fails Owner recorded as Santiago Vila . > owner 1107280 ! Bug #1107280 [src:pymatgen] pymatgen: FTBFS: Tries to access Internet during build

Bug#1106426: marked as done (lmfit-py: FTBFS: FAILURES: test_confidence_warnings)

2025-06-07 Thread Debian Bug Tracking System
Your message dated Sun, 08 Jun 2025 00:04:16 + with message-id and subject line Bug#1106426: fixed in lmfit-py 1.3.3-4 has caused the Debian Bug report #1106426, regarding lmfit-py: FTBFS: FAILURES: test_confidence_warnings to be marked as done. This means that you claim that the problem has

Bug#1106436: pymatgen: FTBFS: TestInterfaceReaction.test_get_entry_energy fails

2025-06-07 Thread Santiago Vila
tags 1106436 patch thanks Hi. I'm going to see if this upstream commit fixes the pymatgen issue. https://github.com/materialsproject/pymatgen/commit/22834931904cfd138206a57684fff20ba0469580 If it does, we probably don't need to revert uncertainties. Doing nothing and expect trixie to become st

Processed: pymatgen: FTBFS: TestInterfaceReaction.test_get_entry_energy fails

2025-06-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1106436 patch Bug #1106436 [src:pymatgen] pymatgen: FTBFS: TestInterfaceReaction.test_get_entry_energy fails Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1106436: https://bugs.debian.o

Bug#1103568: Pending auto removal of rsplib

2025-06-07 Thread Thomas Dreibholz
Hi, Den 01.06.2025 22:43, skrev Martin Hostettler: This mail will bump the autoremoval date a bit into the future, but please note that due to the current hard freeze status, removal from trixie will likely be permanent if it is going through. A upload to fix #1100891 was done. But for this to

Bug#1107453: src:megatools: fails to migrate to testing for too long

2025-06-07 Thread Paul Gevers
Source: megatools Version: 1.11.3-1 Severity: serious Control: close -1 1.11.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 as

Bug#1107452: src:gawk: fails to migrate to testing for too long

2025-06-07 Thread Paul Gevers
Source: gawk Version: 1:5.2.1-2 Severity: serious Control: close -1 1:5.3.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 ha

Bug#1106426: lmfit-py: FTBFS: FAILURES: test_confidence_warnings

2025-06-07 Thread Santiago Vila
El 7/6/25 a las 22:32, Santiago Vila escribió: Is this "debugging left over" related to the current failure of CI tests which I see here? https://tracker.debian.org/pkg/uncertainties I'll answer myself: No, the breakage between lmfit-py and uncertainties seems to happen because of this overly

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

2025-06-07 Thread Debian Bug Tracking System
Processing control commands: > close -1 2025.04.26-1 Bug #1107450 [src:quickjs] src:quickjs: fails to migrate to testing for too long Marked as fixed in versions quickjs/2025.04.26-1. Bug #1107450 [src:quickjs] src:quickjs: fails to migrate to testing for too long Marked Bug as done -- 1107450:

Processed: lmfit-py: FTBFS: FAILURES: test_confidence_warnings

2025-06-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 1106426 Bug #1106426 {Done: Santiago Vila } [src:lmfit-py] lmfit-py: FTBFS: FAILURES: test_confidence_warnings 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to

Bug#1106426: lmfit-py: FTBFS: FAILURES: test_confidence_warnings

2025-06-07 Thread Santiago Vila
reopen 1106426 thanks Hi. I'm going to reopen this as "not 100% fixed yet". Is this "debugging left over" related to the current failure of CI tests which I see here? https://tracker.debian.org/pkg/uncertainties In either case, if we decide to revert uncertainties, I'd like to fix this after w

Bug#1106281: marked as done (broken by ansible 12)

2025-06-07 Thread Debian Bug Tracking System
Your message dated Sat, 7 Jun 2025 20:20:40 + with message-id <27xpaxacdzeejdwlkmfazfizm2dsdqfwr7kfowvid6mucvic2d@nassr6fd4lfi> and subject line Re: Bug#1106281: broken by ansible 12 has caused the Debian Bug report #1106281, regarding broken by ansible 12 to be marked as done. This means tha

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

2025-06-07 Thread Debian Bug Tracking System
Processing control commands: > close -1 1:5.3.2-1 Bug #1107452 [src:gawk] src:gawk: fails to migrate to testing for too long Marked as fixed in versions gawk/1:5.3.2-1. Bug #1107452 [src:gawk] src:gawk: fails to migrate to testing for too long Marked Bug as done -- 1107452: https://bugs.debian.o

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

2025-06-07 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.11.4-1 Bug #1107453 [src:megatools] src:megatools: fails to migrate to testing for too long Marked as fixed in versions megatools/1.11.4-1. Bug #1107453 [src:megatools] src:megatools: fails to migrate to testing for too long Marked Bug as done -- 11074

Bug#1107451: src:lomiri-mediaplayer-app: fails to migrate to testing for too long: FTBFS on s390x

2025-06-07 Thread Paul Gevers
Source: lomiri-mediaplayer-app Version: 1.1.0+dfsg-3 Severity: serious Control: close -1 1.1.1+dfsg-1 Tags: sid trixie ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync User: debian-s...@lists.debian.org X-Debbugs-CC: debian-s...@lists.debian.org Dear maintainer(s), The Re

Processed: src:lomiri-mediaplayer-app: fails to migrate to testing for too long: FTBFS on s390x

2025-06-07 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.1.1+dfsg-1 Bug #1107451 [src:lomiri-mediaplayer-app] src:lomiri-mediaplayer-app: fails to migrate to testing for too long: FTBFS on s390x Marked as fixed in versions lomiri-mediaplayer-app/1.1.1+dfsg-1. Bug #1107451 [src:lomiri-mediaplayer-app] src:lomiri

Bug#1107450: src:quickjs: fails to migrate to testing for too long

2025-06-07 Thread Paul Gevers
Source: quickjs Version: 2024.01.13-5 Severity: serious Control: close -1 2025.04.26-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 d

Bug#1106281: broken by ansible 12

2025-06-07 Thread Marco d'Itri
On Jun 05, Stefano Rivera wrote: Please check if this is still reproducible with 0.3.25~a1-1? Now it works fine, except for this warning: [DEPRECATION WARNING]: 'ansible.parsing.utils.jsonify' is deprecated. This feature will be removed from ansible-core version 2.23. Call `json.dumps` dire

Bug#1107408: libs3: FTBFS: src/request.c:802:19: error: call to ‘_curl_easy_setopt_err_long’ declared with attribute warning: curl_easy_setopt expects a long argument [-Werror=attribute-warning]

2025-06-07 Thread Samuel Henrique
Hello Santiago, On Sat, 7 Jun 2025 at 10:51, Santiago Vila wrote: > > gcc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -Werror -Wshadow -Wextra -Iinc  -I/usr/i

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

2025-06-07 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.80.1-1 Bug #1107448 [src:zigpy] src:zigpy: fails to migrate to testing for too long Marked as fixed in versions zigpy/0.80.1-1. Bug #1107448 [src:zigpy] src:zigpy: fails to migrate to testing for too long Marked Bug as done -- 1107448: https://bugs.debia

Bug#1107448: src:zigpy: fails to migrate to testing for too long

2025-06-07 Thread Paul Gevers
Source: zigpy Version: 0.78.0-1 Severity: serious Control: close -1 0.80.1-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 hav

Bug#1105227: marked as done (nbdkit: CVE-2025-47711)

2025-06-07 Thread Debian Bug Tracking System
Your message dated Sat, 7 Jun 2025 20:45:47 +0200 with message-id and subject line Re: Accepted nbdkit 1.42.3-1 (source) into unstable has caused the Debian Bug report #1105227, regarding nbdkit: CVE-2025-47711 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1105228: marked as done (nbdkit: CVE-2025-47712)

2025-06-07 Thread Debian Bug Tracking System
Your message dated Sat, 7 Jun 2025 20:45:47 +0200 with message-id and subject line Re: Accepted nbdkit 1.42.3-1 (source) into unstable has caused the Debian Bug report #1105228, regarding nbdkit: CVE-2025-47712 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1105228: Accepted nbdkit 1.42.3-1 (source) into unstable

2025-06-07 Thread Salvatore Bonaccorso
Source: nbdkit Source-Version: 1.42.3-1 On Sun, May 25, 2025 at 03:34:21PM +, Debian FTP Masters wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Format: 1.8 > Date: Sun, 25 May 2025 14:48:44 +0200 > Source: nbdkit > Architecture: source > Version: 1.42.3-1 > Distribution: unsta

Processed: severity of 1105227 is grave, severity of 1105228 is grave

2025-06-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # should get fixed for trixie > severity 1105227 grave Bug #1105227 [src:nbdkit] nbdkit: CVE-2025-47711 Severity set to 'grave' from 'important' > # should get fixed for trixie > severity 1105228 grave Bug #1105228 [src:nbdkit] nbdkit: CVE-2025-47

Bug#1107412: [Pkg-rust-maintainers] Bug#1107412: rust-git-cinnabar: FTBFS: [git-cinnabar 0.7.2] http.patched.c:1037:17: error: call to ‘_curl_easy_setopt_err_long’ declared with attribute warning:

2025-06-07 Thread Peter Green
> During a rebuild of all packages in unstable, your package failed to build: It appears the function in question is a variadic function. The documentation for curl_easy_setopt says. "That parameter can be a long, a function pointer, an object pointer or a curl_off_t, depending on what the spe

Bug#1106121: isc-dhcp - EOL and not security supported

2025-06-07 Thread Martin-Éric Racine
On Mon, 2 Jun 2025 00:25:41 +0200 Lorenzo wrote: > What is the default replacement for the client? and for the server? client: dhcpcd-base relay: dnsmasq server: dnsmasq or kea Martin-Éric

Processed: src:bluetooth-sensor-state-data: fails to migrate to testing for too long

2025-06-07 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.9.0-1 Bug #1107431 [src:bluetooth-sensor-state-data] src:bluetooth-sensor-state-data: fails to migrate to testing for too long Marked as fixed in versions bluetooth-sensor-state-data/1.9.0-1. Bug #1107431 [src:bluetooth-sensor-state-data] src:bluetooth-se

Bug#1107431: src:bluetooth-sensor-state-data: fails to migrate to testing for too long

2025-06-07 Thread Paul Gevers
Source: bluetooth-sensor-state-data Version: 1.7.5-1 Severity: serious Control: close -1 1.9.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

Processed: tagging 1103568

2025-06-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1103568 + trixie-ignore Bug #1103568 {Done: Paul Gevers } [src:rsplib] src:rsplib: fails to migrate to testing for too long Added tag(s) trixie-ignore. > thanks Stopping processing here. Please contact me if you need assistance. -- 1103568

Processed: tagging 1106853

2025-06-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1106853 + trixie-ignore Bug #1106853 {Done: Paul Gevers } [src:mini-buildd] src:mini-buildd: fails to migrate to testing for too long Added tag(s) trixie-ignore. > thanks Stopping processing here. Please contact me if you need assistance. -

Bug#1107430: src:octave-mapping: fails to migrate to testing for too long: FTBFS on riscv64

2025-06-07 Thread Paul Gevers
Source: octave-mapping Version: 1.4.2-3 Severity: serious Control: close -1 1.4.3-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 3

Processed: src:octave-mapping: fails to migrate to testing for too long: FTBFS on riscv64

2025-06-07 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.4.3-1 Bug #1107430 [src:octave-mapping] src:octave-mapping: fails to migrate to testing for too long: FTBFS on riscv64 Marked as fixed in versions octave-mapping/1.4.3-1. Bug #1107430 [src:octave-mapping] src:octave-mapping: fails to migrate to testing f

Processed: tagging 1105960

2025-06-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1105960 + trixie-ignore Bug #1105960 {Done: Paul Gevers } [src:octave-video] src:octave-video: fails to migrate to testing for too long Added tag(s) trixie-ignore. > thanks Stopping processing here. Please contact me if you need assistance.

Bug#1107407: marked as done (collectd: FTBFS: src/curl.c:349:3: error: call to '_curl_easy_setopt_err_long' declared with attribute warning: curl_easy_setopt expects a long argument [-Werror=attribute

2025-06-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Jun 2025 14:34:35 + with message-id and subject line Bug#1107407: fixed in collectd 5.12.0-24 has caused the Debian Bug report #1107407, regarding collectd: FTBFS: src/curl.c:349:3: error: call to '_curl_easy_setopt_err_long' declared with attribute warning: curl_ea

Bug#1107304: python3.13 left out of toolchain packages list

2025-06-07 Thread Jeremy Bícha
On Sat, Jun 7, 2025 at 3:07 AM Sebastian Ramacher wrote: > On 2025-06-05 17:51:10 -0400, Jeremy Bícha wrote: > > Release Team, > > > > I noticed today while reading https://bugs.debian.org/1107304 that > > python3.13 was not included in the toolchain packages list [1]. My > > reading of the list i

Bug#1107409: numba: FTBFS: Fatal Python error: Segmentation fault

2025-06-07 Thread Santiago Vila
Package: src:numba Version: 0.61.2+dfsg-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean --wi

Bug#1107412: rust-git-cinnabar: FTBFS: [git-cinnabar 0.7.2] http.patched.c:1037:17: error: call to ‘_curl_easy_setopt_err_long’ declared with attribute warning: curl_easy_setopt expects a long arg

2025-06-07 Thread Santiago Vila
Package: src:rust-git-cinnabar Version: 0.7.2-1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [ note: CC to Samuel Henrique, as this seems related to the recent upload of curl ]

Bug#1107411: powerman: FTBFS: httppower.c:327:5: error: call to '_curl_easy_setopt_err_long' declared with attribute warning: curl_easy_setopt expects a long argument [-Werror=attribute-warning]

2025-06-07 Thread Santiago Vila
Package: src:powerman Version: 2.4.4-3 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [ note: CC to Samuel Henrique, as this seems related to the recent upload of curl ] -

Bug#1107410: python-covdefaults: FTBFS: E AttributeError: type object 'Plugins' has no attribute 'load_plugins'

2025-06-07 Thread Santiago Vila
Package: src:python-covdefaults Version: 2.3.0-2 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh cle

Bug#1107408: libs3: FTBFS: src/request.c:802:19: error: call to ‘_curl_easy_setopt_err_long’ declared with attribute warning: curl_easy_setopt expects a long argument [-Werror=attribute-warning]

2025-06-07 Thread Santiago Vila
Package: src:libs3 Version: 2.0-4.1 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [ note: CC to Samuel Henrique, as this seems related to the recent upload of curl ]

Bug#1107407: collectd: FTBFS: src/curl.c:349:3: error: call to '_curl_easy_setopt_err_long' declared with attribute warning: curl_easy_setopt expects a long argument [-Werror=attribute-warning]

2025-06-07 Thread Santiago Vila
Package: src:collectd Version: 5.12.0-23 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [ note: CC to Samuel Henrique, as this seems related to the recent upload of curl ] ---

Bug#1106786: git ftbfs on s390x (test failures)

2025-06-07 Thread Jonathan Nieder
Sebastian Andrzej Siewior wrote: > On 2025-06-07 10:38:12 [+0200], Jonathan Nieder wrote: >> Sebastian Andrzej Siewior wrote: >>> The patch you took was the top-most in the fix series, you also need the >>> few that were applied before that one. That last one depends on the >>> previous changes. I

Bug#1107403: gmtsar:FTBFS:build failed(gcc: error: unrecognized command-line option ‘-m64’)

2025-06-07 Thread Yue Gui
Source: gmtsar Version: 6.5+ds-3 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 Dear gmtsar maintainer, The package gmtsar build failed on riscv64 .The crucial buildd log below: ``` make[3]: Entering directory '/build/reproducible-path/gmtsar-6.5+ds/pre

Bug#1106786: git ftbfs on s390x (test failures)

2025-06-07 Thread Sebastian Andrzej Siewior
On 2025-06-07 10:38:12 [+0200], Jonathan Nieder wrote: > Hi Sebastian, Hi Jonathan, > Sebastian Andrzej Siewior wrote: > > >> Even after the fix from https://bugs.debian.org/1102106, git ftbfs on > >> s390x. Filing as a separate bug because this is a different failure. > > > > The patch you took

Bug#1106786: git ftbfs on s390x (test failures)

2025-06-07 Thread Jonathan Nieder
Jonathan Nieder wrote: > The other thing that surprised me was that experimental, which > includes all patches in "next", also continued to fail tests on 64-bit > big endian architectures, though now that I check again in the > experimental buildd logs that is yet another, different failure! Repr

Bug#1101611: Needed in Trixie?

2025-06-07 Thread Ivo De Decker
On Sat, Apr 19, 2025 at 10:23:13AM +0200, William Desportes wrote: >Does anyone have a fix for this? >Or is this package not needed In Trixie? Taffit (maintainer) on irc: < taffit> ivodd: indeed I know about #1101611. I’ve kept my mouth shut to not delay the removal: nothing in Trixie de

Bug#1106786: git ftbfs on s390x (test failures)

2025-06-07 Thread Jonathan Nieder
Hi Sebastian, Sebastian Andrzej Siewior wrote: >> Even after the fix from https://bugs.debian.org/1102106, git ftbfs on >> s390x. Filing as a separate bug because this is a different failure. > > The patch you took was the top-most in the fix series, you also need the > few that were applied befo

Bug#1074591: marked as pending in acct

2025-06-07 Thread Sven Geuer
Control: tag -1 pending Hello, Bug #1074591 in acct reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/pkg-security-team/acct/-/commit/6a5364ec5602326e65dc73f614f2

Bug#1074591: marked as pending in acct

2025-06-07 Thread Sven Geuer
Control: tag -1 pending Hello, Bug #1074591 in acct reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/pkg-security-team/acct/-/commit/74595c8039d0adc8a8b98d214b7c

Processed: Bug#1074591 marked as pending in acct

2025-06-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1074591 [acct] acct: cron job needs wtmpdb last and points it to wtmp file Added tag(s) pending. -- 1074591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug#1074591 marked as pending in acct

2025-06-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1074591 [acct] acct: cron job needs wtmpdb last and points it to wtmp file Ignoring request to alter tags of bug #1074591 to the same tags previously set -- 1074591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074591 Debian Bug Tracking S

Bug#1107126: is cross-gcc-dev still useful or can it be removed?

2025-06-07 Thread Dima Kogan
Hi. I'm pretty sure you (Helmut) were the only user of cross-gcc-dev. As you say, I haven't updated it for a while, and it hasn't been useful to you either. So I don't see a lot of reason to keep it in the archive, and removing it would be good. Thanks for all your work!

Bug#1107304: python3.13 left out of toolchain packages list

2025-06-07 Thread Sebastian Ramacher
Hi Jeremy On 2025-06-05 17:51:10 -0400, Jeremy Bícha wrote: > Release Team, > > I noticed today while reading https://bugs.debian.org/1107304 that > python3.13 was not included in the toolchain packages list [1]. My > reading of the list is that it was intended to be there. It is there. The list