Bug#1057947: marked as done (hp48cc: missing error trapping in Makefile)

Your message dated Fri, 22 Dec 2023 07:50:13 + with message-id and subject line Bug#1057947: fixed in hp48cc 1.3-7 has caused the Debian Bug report #1057947, regarding hp48cc: missing error trapping in Makefile to be marked as done. This means that you claim that the problem has been dealt

Bug#1058177: marked as done (sphinxtesters: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)

Your message dated Fri, 22 Dec 2023 07:34:49 + with message-id and subject line Bug#1058177: fixed in sphinxtesters 0.2.3-3 has caused the Debian Bug report #1058177, regarding sphinxtesters: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean:

Processed: severity of 1059163 is important

Processing commands for cont...@bugs.debian.org: > severity 1059163 important Bug #1059163 {Done: Anibal Monsalve Salazar } [cpio] cpio: Path traversal vulnerability Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#1059163: marked as done (cpio: Path traversal vulnerability)

Your message dated Fri, 22 Dec 2023 06:19:25 + with message-id and subject line Bug#1059163: fixed in cpio 2.14+dfsg-1 has caused the Debian Bug report #1059163, regarding cpio: Path traversal vulnerability to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1036869: O: ghostscript -- interpreter for the PostScript language and for PDF

On Mon, 24 Oct 2022 15:17:20 +0200 Jonas Smedegaard wrote: > I have orphaned the ghostscript package, due to lack of time. I'm willing to take on -- and hopefully, share -- the ghostscript maintenance. If anyone wants to team up, let me know! -Steve signature.asc Description: This is a

Bug#1059249: designer-qt6: Segmentation fault in /usr/lib/qt6/bin/designer at launch

Package: designer-qt6 Version: 6.6.1-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: mlukow...@sdf.org Hey, Designer segfaults on launch; seems the bug might be with qt6 xcb integration. Valgrind reports the following output: matt@pancakehut:~$ valgrind

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

* Sébastien Villemot [2023-12-21 15:23]: Le jeudi 21 décembre 2023 à 08:49 +0100, Rafael Laboissière a écrit : * Santiago Vila [2023-12-20 22:03]: El 20/12/23 a las 21:08, Rafael Laboissière escribió: HOME := $(shell mktemp -d) so that the same directory is never used twice between

Bug#1059163: cpio: Path traversal vulnerability

On Wed, 2023-12-20 19:55:30 +0100, Ingo Brückl wrote: > Package: cpio > Version: 2.13+dfsg-7.1 > Severity: grave > > The patch "revert-CVE-2015-1197-handling" (to close bugs #946267 and #946469) > re-enables path traversal vulnerability with maliciously crafted cpio > archives. Hello Ingo, I

Bug#1059245: gdm3: GDM3 fails to start on Wayland, maybe due to org.freedesktop.systemd1 failing to activate

Package: gdm3 Version: 45.0.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, GDM3 doesn't seem to be able to start a Wayland session (nor a fallback Xorg session, but I'm less concerned about this, and this seems to be a separate permission issue). This seems to be

Bug#1057421: marked as done (sysstat: FTBFS: dh_install: warning: Cannot find (any matches for) "debian/tmp/lib/systemd/" (tried in ., debian/tmp))

Your message dated Fri, 22 Dec 2023 01:22:18 + with message-id and subject line Bug#1057421: fixed in sysstat 12.6.1-1.1 has caused the Debian Bug report #1057421, regarding sysstat: FTBFS: dh_install: warning: Cannot find (any matches for) "debian/tmp/lib/systemd/" (tried in ., debian/tmp)

Bug#999937: marked as done (tup: depends on obsolete pcre3 library)

Your message dated Fri, 22 Dec 2023 00:38:13 + with message-id and subject line Bug#37: fixed in tup 0.7.11-4 has caused the Debian Bug report #37, regarding tup: depends on obsolete pcre3 library to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1058318: flask-login: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

Hi Carsten, I can see that 3.0.1 is currently in experimental, but it would be enough to upgrade to the latest 2.x to fix this issue. this makes not really sense to me. Flask 3.0.0 and Werkzeug 3.0.0 was released on 09-30-2023, so almost three months before. Putting energy into Flask 2.3.5

Bug#1055733: marked as done (pytango ftbfs with Python 3.12 (test failures))

Your message dated Thu, 21 Dec 2023 22:10:36 + with message-id and subject line Bug#1055733: fixed in pytango 9.5.0-1~exp1 has caused the Debian Bug report #1055733, regarding pytango ftbfs with Python 3.12 (test failures) to be marked as done. This means that you claim that the problem has

Bug#1057862: marked as done (pytango ftbfs with Python 3.12)

Your message dated Thu, 21 Dec 2023 22:10:36 + with message-id and subject line Bug#1055733: fixed in pytango 9.5.0-1~exp1 has caused the Debian Bug report #1055733, regarding pytango ftbfs with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1000010: marked as done (ohcount: depends on obsolete pcre3 library)

Your message dated Thu, 21 Dec 2023 22:09:28 + with message-id and subject line Bug#110: fixed in ohcount 4.0.0-4 has caused the Debian Bug report #110, regarding ohcount: depends on obsolete pcre3 library to be marked as done. This means that you claim that the problem has been

Bug#1056080: marked as done (flightcrew: FTBFS: boost1.83 transition)

Your message dated Thu, 21 Dec 2023 22:05:13 + with message-id and subject line Bug#1056080: fixed in flightcrew 0.9.3+dfsg-2 has caused the Debian Bug report #1056080, regarding flightcrew: FTBFS: boost1.83 transition to be marked as done. This means that you claim that the problem has been

Bug#1058937: /usr-move: Do we support upgrades without apt?

On Thu, Dec 21, 2023 at 02:42:56PM +, Matthew Vernon wrote: > On 21/12/2023 09:41, Helmut Grohne wrote: > > Is it ok to call upgrade scenarios failures that cannot be reproduced > > using apt unsupported until we no longer deal with aliasing? > > I incline towards "no"; if an upgrade has

Bug#1000010: ohcount: depends on obsolete pcre3 library

oh, cool, thanks :) I will upload it /i/n a second Le 21/12/2023 à 21:33, Yavor Doganov a écrit : Control: tags -1 + patch Please find a patch attached.

Bug#1058937: /usr-move: Do we support upgrades without apt?

On Thu, Dec 21, 2023 at 03:31:55PM +0100, Marc Haber wrote: > On Thu, Dec 21, 2023 at 11:19:48AM -0300, Antonio Terceiro wrote: > > On Thu, Dec 21, 2023 at 10:41:57AM +0100, Helmut Grohne wrote: > > > Is it ok to call upgrade scenarios failures that cannot be reproduced > > > using apt unsupported

Bug#1000010: ohcount: depends on obsolete pcre3 library

Control: tags -1 + patch Please find a patch attached. Description: Port to PCRE2. Bug-Debian: https://bugs.debian.org/110 Author: Yavor Doganov Forwarded: no Last-Update: 2023-12-21 --- --- ohcount-4.0.0.orig/build +++ ohcount-4.0.0/build @@ -31,7 +31,7 @@ # You shouldn't have to change

Processed: Re: Bug#1000010: ohcount: depends on obsolete pcre3 library

Processing control commands: > tags -1 + patch Bug #110 [src:ohcount] ohcount: depends on obsolete pcre3 library Added tag(s) patch. -- 110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1058937: /usr-move: Do we support upgrades without apt?

Am 21.12.23 um 11:50 schrieb Christoph Berg: Re: Helmut Grohne Is it ok to call upgrade scenarios failures that cannot be reproduced using apt unsupported until we no longer deal with aliasing? If the answer is yes here, we'll close #1058937 (Ben's libnfsidmap1 bug) with no action calling the

Bug#1054485: marked as done (postfix: installs a systemd unit twice when dh_installsystemd installs below /usr)

Your message dated Thu, 21 Dec 2023 19:21:31 + with message-id and subject line Bug#1054485: fixed in postfix 3.8.3-1 has caused the Debian Bug report #1054485, regarding postfix: installs a systemd unit twice when dh_installsystemd installs below /usr to be marked as done. This means that

Bug#1058318: flask-login: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

Hello Gregor, Am Thu, Dec 21, 2023 at 02:00:40PM +0100 schrieb Gregor Riepl: > I don't see any other errors in the log except for the ast.Str deprecation > warnings, and they all come from python-werkezug and not this package. > > Reassiging the bug. > Upstream has already fixed this in in

Bug#1056247: marked as done (flask's autopkg tests fail with Python 3.12)

Your message dated Thu, 21 Dec 2023 19:05:18 + with message-id and subject line Bug#1056247: fixed in flask 3.0.0-1 has caused the Debian Bug report #1056247, regarding flask's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt

Bug#1054485: postfix: diff for NMU version 3.8.2-1.1

On Monday, December 18, 2023 7:31:47 PM EST Chris Hofstaedtler wrote: > Control: tags 1054485 + patch > Control: tags 1054485 + pending > > Dear maintainer, > > I've prepared an NMU for postfix (versioned as 3.8.2-1.1) and > uploaded it to DELAYED/7. Please feel free to tell me if I > should

Bug#999921: xymon: depends on obsolete pcre3 library

Hi Yavor, Yavor Doganov wrote: > Please find a patch which I've been testing for a while with no ill > effects AFAICT. However, I'm not familiar at all with this package so > it's possible that I've missed something. I also couldn't test all > available functionality. Thanks a lot also for

Processed: tagging 1000053

Processing commands for cont...@bugs.debian.org: > tags 153 + fixed-upstream Bug #153 [src:courier] courier: depends on obsolete pcre3 library Bug #154 [src:courier] courier: depends on obsolete pcre3 library Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. > thanks Stopping

Bug#1058815: marked as done (calcium: FTBFS: /usr/include/fmpz_extras.h:208:1: error: static declaration of ‘fmpz_ui_pow_ui’ follows non-static declaration)

Your message dated Thu, 21 Dec 2023 17:49:37 + with message-id and subject line Bug#1058916: Removed package(s) from unstable has caused the Debian Bug report #1058815, regarding calcium: FTBFS: /usr/include/fmpz_extras.h:208:1: error: static declaration of ‘fmpz_ui_pow_ui’ follows

Bug#999937: tup: depends on obsolete pcre3 library

On Tue, Aug 29, 2023 at 03:18:26PM +0200, Bastian Germann wrote: > On Tue, 31 Jan 2023 21:36:46 +0800 Bo YU wrote: > > The upstream has tried to switch pcre2[0], but the backporting is > > not easy, so maybe waiting a new release is good iead. > > I have started a backport in git but there is at

Bug#999921: xymon: depends on obsolete pcre3 library

Control: tags -1 + patch Please find a patch which I've been testing for a while with no ill effects AFAICT. However, I'm not familiar at all with this package so it's possible that I've missed something. I also couldn't test all available functionality. Unfortunately the patch does not apply

Processed: Re: Bug#999921: xymon: depends on obsolete pcre3 library

Processing control commands: > tags -1 + patch Bug #21 [src:xymon] xymon: depends on obsolete pcre3 library Added tag(s) patch. -- 21: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=21 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1058937: /usr-move: Do we support upgrades without apt?

On Thu, 21 Dec 2023 at 15:31:55 +0100, Marc Haber wrote: > Do those GUI frontends that work via packagekit or other frameworks > count as "using apt"? Managing apt/dpkg packages via packagekit uses libapt-pkg6.0 (via /usr/lib/*/packagekit-backend/libpk_backend_apt.so). I don't know whether that's

Bug#1057580: nfstrace: FTBFS: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’}

Control: tags -1 + patch On 2023-12-05 23:07 +0100, Santiago Vila wrote: > Package: src:nfstrace > Version: 0.4.3.2+git20200805+b220d04-2.2 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > During a rebuild of all packages in unstable, your package failed to build: > >

Processed: Re: Bug#1057580: nfstrace: FTBFS: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’}

Processing control commands: > tags -1 + patch Bug #1057580 [src:nfstrace] nfstrace: FTBFS: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’} Added tag(s) patch. -- 1057580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057580 Debian Bug Tracking System Contact

Bug#1059140: [Debian-med-packaging] Bug#1059140: sight: FTBFS: error: ‘void* __builtin_memcpy(void*, const void*, long unsigned int) ’ forming offset [32, 34] is out of the bounds [0, 32] of object ‘

Dear Andreas, Thank you for the notice. It looks like a optimizer compiler bug... Anyway, I managed to patch it using a different syntax. I pushed it in the repository. Please have a look and upload it if that's good enough. Cheers. *Dr. Flavien BRIDAULT* Director of Software Development

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

Your message dated Thu, 21 Dec 2023 16:19:02 + with message-id and subject line Bug#1052856: fixed in httpbin 0.10.1+dfsg-2 has caused the Debian Bug report #1052856, regarding httpcore: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

Processed: Bug#1052856 marked as pending in httpbin

Processing control commands: > tag -1 pending Bug #1052856 [src:httpcore] httpcore: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13 Added tag(s) pending. -- 1052856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052856 Debian Bug

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

Your message dated Thu, 21 Dec 2023 16:54:41 +0100 with message-id <20231221165441.5fae1...@debian.org> and subject line 1058126 has caused the Debian Bug report #1058126, regarding tkcalendar: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13 to

Bug#1052856: marked as pending in httpbin

Control: tag -1 pending Hello, Bug #1052856 in httpbin 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:

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

Your message dated Thu, 21 Dec 2023 15:35:35 + with message-id and subject line Bug#1058302: fixed in patsy 0.5.4-1 has caused the Debian Bug report #1058302, regarding patsy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 to

Bug#1058904: marked as done (python3-apt: apt_pkg.TagFile segfaults on files with comments)

Your message dated Thu, 21 Dec 2023 15:20:03 + with message-id and subject line Bug#1058904: fixed in python-apt 2.7.3 has caused the Debian Bug report #1058904, regarding python3-apt: apt_pkg.TagFile segfaults on files with comments to be marked as done. This means that you claim that the

Bug#1058657: marked as done (python3-apt: undefined symbol: PyAptWarning)

Your message dated Thu, 21 Dec 2023 15:20:03 + with message-id and subject line Bug#1058657: fixed in python-apt 2.7.3 has caused the Debian Bug report #1058657, regarding python3-apt: undefined symbol: PyAptWarning to be marked as done. This means that you claim that the problem has been

Bug#1058657: marked as pending in python-apt

Control: tag -1 pending Hello, Bug #1058657 in python-apt 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:

Processed: Bug#1058657 marked as pending in python-apt

Processing control commands: > tag -1 pending Bug #1058657 [python3-apt] python3-apt: undefined symbol: PyAptWarning Added tag(s) pending. -- 1058657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1058876: marked as done (libopenmpi-dev: paths missing /usr/include...(for fortran mpi.mod))

Your message dated Thu, 21 Dec 2023 14:50:15 + with message-id and subject line Bug#1058876: fixed in openmpi 4.1.6-3 has caused the Debian Bug report #1058876, regarding libopenmpi-dev: paths missing /usr/include...(for fortran mpi.mod) to be marked as done. This means that you claim that

Processed: Bug#1058904 marked as pending in python-apt

Processing control commands: > tag -1 pending Bug #1058904 [python3-apt] python3-apt: apt_pkg.TagFile segfaults on files with comments Added tag(s) pending. -- 1058904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058904 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1058904: marked as pending in python-apt

Control: tag -1 pending Hello, Bug #1058904 in python-apt 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:

Bug#1058937: /usr-move: Do we support upgrades without apt?

Hi, On 21/12/2023 09:41, Helmut Grohne wrote: Is it ok to call upgrade scenarios failures that cannot be reproduced using apt unsupported until we no longer deal with aliasing? I incline towards "no"; if an upgrade has failed part-way (as does happen), people may then reasonably use dpkg

Bug#1058216: marked as done (pygopherd: FTBFS: ModuleNotFoundError: No module named 'imp')

Your message dated Thu, 21 Dec 2023 14:37:58 + with message-id and subject line Bug#1058216: fixed in pygopherd 3.0.0~git20221126.02c65d60-5 has caused the Debian Bug report #1058216, regarding pygopherd: FTBFS: ModuleNotFoundError: No module named 'imp' to be marked as done. This means that

Bug#1057931: marked as done (greetd: FTBFS: failed to select a version for the requirement `rpassword = "^6.0"`)

Your message dated Thu, 21 Dec 2023 14:35:34 + with message-id and subject line Bug#1057931: fixed in greetd 0.9.0-6 has caused the Debian Bug report #1057931, regarding greetd: FTBFS: failed to select a version for the requirement `rpassword = "^6.0"` to be marked as done. This means that

Bug#1058937: /usr-move: Do we support upgrades without apt?

On Thu, Dec 21, 2023 at 11:19:48AM -0300, Antonio Terceiro wrote: > On Thu, Dec 21, 2023 at 10:41:57AM +0100, Helmut Grohne wrote: > > Is it ok to call upgrade scenarios failures that cannot be reproduced > > using apt unsupported until we no longer deal with aliasing? > > I think so, yes. I

Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386

On Thu, 21 Dec 2023 at 14:57, Paul Gevers wrote: > The Release Team considers packages that are out-of-sync between testing > and unstable for more than 30 days as having a Release Critical bug in > testing [1]. Your package src:meson has been trying to migrate for 31 > days [2]. Hence, I am

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

Le jeudi 21 décembre 2023 à 08:49 +0100, Rafael Laboissière a écrit : > * Santiago Vila [2023-12-20 22:03]: > > > El 20/12/23 a las 21:08, Rafael Laboissière escribió: > > > > HOME := $(shell mktemp -d) > > > > > > > > so that the same directory is never used twice between consecutive > > > >

Bug#1058937: /usr-move: Do we support upgrades without apt?

On Thu, Dec 21, 2023 at 10:41:57AM +0100, Helmut Grohne wrote: > ## Upgrading using dpkg directly? > > We already have quite a number of packages that use Conflicts to prevent > file loss in upgrades in a very similar way to #1058937 (Ben's > libnfsidmap1 bug) even in released versions of Debian.

Bug#1058096: Test suite issues with new version of python3-antlr4 (Was: python3-antlr4: FTBFS: AttributeError: 'TestIntervalSet' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

On Thu, 21 Dec 2023 14:30:34 +0100 Andreas Tille wrote: > Control: tags -1 pending > > Hi, > > I intended to fix bug #1058096. Since I realised there is a new > upstream version I was considering an upgrade which I pushed to Salsa. > Unfortunately there are other test suite errors as you can see

Bug#1058096: Test suite issues with new version of python3-antlr4 (Was: python3-antlr4: FTBFS: AttributeError: 'TestIntervalSet' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

Control: tags -1 pending Hi, I intended to fix bug #1058096. Since I realised there is a new upstream version I was considering an upgrade which I pushed to Salsa. Unfortunately there are other test suite errors as you can see in Salsa CI[1]:

Processed: Bug#1058258 marked as pending in networking-sfc

Processing control commands: > tag -1 pending Bug #1058258 [src:networking-sfc] networking-sfc: FTBFS: KeyError: slice(1, None, None) Added tag(s) pending. -- 1058258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058258 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1058258: marked as pending in networking-sfc

Control: tag -1 pending Hello, Bug #1058258 in networking-sfc 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:

Processed: Test suite issues with new version of python3-antlr4 (Was: python3-antlr4: FTBFS: AttributeError: 'TestIntervalSet' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

Processing control commands: > tags -1 pending Bug #1058096 [src:python3-antlr4] python3-antlr4: FTBFS: AttributeError: 'TestIntervalSet' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? Ignoring request to alter tags of bug #1058096 to the same tags previously set --

Processed: Bug#1058096 marked as pending in python3-antlr4

Processing control commands: > tag -1 pending Bug #1058096 [src:python3-antlr4] python3-antlr4: FTBFS: AttributeError: 'TestIntervalSet' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? Added tag(s) pending. -- 1058096:

Bug#1058096: marked as pending in python3-antlr4

Control: tag -1 pending Hello, Bug #1058096 in python3-antlr4 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:

Processed: Re: Bug#1056460: python-bytecode's autopkg tests fail with Python 3.12 (armhf)

Processing commands for cont...@bugs.debian.org: > severity 1056460 important Bug #1056460 [src:python-bytecode] python-bytecode's autopkg tests fail with Python 3.12 (armhf) Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance.

Bug#1056460: python-bytecode's autopkg tests fail with Python 3.12 (armhf)

severity 1056460 important thanks On Wed, Nov 22, 2023 at 02:29:47PM +0100, Matthias Klose wrote: > Package: src:python-bytecode > Version: 0.15.1-1 > Severity: important > Tags: sid trixie > User: debian-pyt...@lists.debian.org > Usertags: python3.12 > > python-bytecode's autopkg tests fail

Processed: your mail

Processing commands for cont...@bugs.debian.org: > forwarded 1058318 https://github.com/pallets/werkzeug/issues/2704 Bug #1058318 [src:python-werkzeug] flask-login: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 Set Bug

Bug#1058318: flask-login: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

I don't see any other errors in the log except for the ast.Str deprecation warnings, and they all come from python-werkezug and not this package. Reassiging the bug. Upstream has already fixed this in in 2.3.5, by the way: https://github.com/pallets/werkzeug/issues/2704 I can see that 3.0.1

Bug#1058142: marked as done (pysmi: FTBFS: ModuleNotFoundError: No module named 'imp')

Your message dated Thu, 21 Dec 2023 13:55:07 +0100 with message-id <75352fc4-6e33-4c0b-a671-66e563a0a...@debian.org> and subject line Re: r4d is marked for autoremoval from testing has caused the Debian Bug report #1058142, regarding pysmi: FTBFS: ModuleNotFoundError: No module named 'imp' to be

Processed (with 1 error): your mail

Processing commands for cont...@bugs.debian.org: > reassign 1058318 src:python-werkzeug Bug #1058318 [src:flask-login] flask-login: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 Bug reassigned from package 'src:flask-login' to

Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386

Source: meson Version: 1.2.3-1 Severity: serious Control: close -1 1.3.0-2 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

Processed: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386

Processing control commands: > close -1 1.3.0-2 Bug #1059223 [src:meson] src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386 Marked as fixed in versions meson/1.3.0-2. Bug #1059223 [src:meson] src:meson: fails to migrate to testing for too long: fails

Bug#1059222: src:pv: fails to migrate to testing for too long: FTBFS on armhf

Source: pv Version: 1.8.0-3 Severity: serious Control: close -1 1.8.5-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 days as

Processed: src:pv: fails to migrate to testing for too long: FTBFS on armhf

Processing control commands: > close -1 1.8.5-1 Bug #1059222 [src:pv] src:pv: fails to migrate to testing for too long: FTBFS on armhf Marked as fixed in versions pv/1.8.5-1. Bug #1059222 [src:pv] src:pv: fails to migrate to testing for too long: FTBFS on armhf Marked Bug as done -- 1059222:

Bug#1059220: src:restic: fails to migrate to testing for too long: new Build-Depends is no migration candidate

Source: restic Version: 0.16.0-1 Severity: serious Control: close -1 0.16.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

Processed: src:restic: fails to migrate to testing for too long: new Build-Depends is no migration candidate

Processing control commands: > close -1 0.16.2-1 Bug #1059220 [src:restic] src:restic: fails to migrate to testing for too long: new Build-Depends is no migration candidate Marked as fixed in versions restic/0.16.2-1. Bug #1059220 [src:restic] src:restic: fails to migrate to testing for too

Bug#1059154: marked as done (gem2deb: autopkgtest failures [PATCH])

Your message dated Thu, 21 Dec 2023 12:49:01 + with message-id and subject line Bug#1059154: fixed in gem2deb 2.2.1 has caused the Debian Bug report #1059154, regarding gem2deb: autopkgtest failures [PATCH] to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1056279: Bug#1057220: Looks like the systemctl links are gone but not the pm-utils ones

On Mon, Dec 18, 2023 at 10:09:10AM +0100, Marc Haber wrote: > Thanks for the work, I was never able to fully grasp the issue and the > inner workings of the solution, and thank you for allowing me to remain > silent during the process of finding and implementing the solution. I'd like to report

Bug#1058937: /usr-move: Do we support upgrades without apt?

Re: Helmut Grohne > Is it ok to call upgrade scenarios failures that cannot be reproduced > using apt unsupported until we no longer deal with aliasing? > > If the answer is yes here, we'll close #1058937 (Ben's libnfsidmap1 bug) > with no action calling the scenario unsupported. I think we

Bug#1058937: /usr-move: Do we support upgrades without apt?

Hi, this installment serves a dual purpose. Let me first give an update of the status quo and then pose a consensus question on how we want to deal with a particular problem. I Cc d-release@l.d.o as upgrades are an integral part of releases. I Cc d-ctte@l.d.o for advisory feedback with

Processed: Re: Bug#1059165: src:zlib: fails to migrate to testing for too long: triggers autopkgtest issues

Processing commands for cont...@bugs.debian.org: > retitle 1059168 flaky autopkgtest Bug #1059168 [nodejs] autopkgtest failures on i386 Changed Bug title to 'flaky autopkgtest' from 'autopkgtest failures on i386'. > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was

Bug#1059168: Bug#1059165: src:zlib: fails to migrate to testing for too long: triggers autopkgtest issues

retitle 1059168 flaky autopkgtest user debian...@lists.debian.org usertag 1059168 flaky thanks BCC: control@b.d.o Hi, On 21-12-2023 10:04, Jérémy Lal wrote: Thank you for https://bugs.debian.org/1059168 I noticed "Marked as found in versions

Bug#1059165: [Pkg-javascript-devel] Bug#1059165: src:zlib: fails to migrate to testing for too long: triggers autopkgtest issues

Le jeu. 21 déc. 2023 à 08:59, Paul Gevers a écrit : > Hi, > > On 20-12-2023 23:08, Jérémy Lal wrote: > > I did the one for burp. > > Thanks for that. > > > Dolfin has active maintainers, though. > > I think I need to file a "flaky autopkgtest" bug report against dolfin. Thank you for

Bug#1056457: [Debichem-devel] Bug#1056457: python-ase's autopkg tests fail with Python 3.12

Hi, On Thu, 21 Dec 2023 08:39:54 +0200 Andrius Merkys wrote: > Is there a way to ignore DeprecationWarnings, but leave them in to the > output? They are quite helpful to see, but not worth failing the build > at the time being. > You're right, deprecation outputs are useful. I've just tried by

Bug#1058373: marked as done (python-oslotest: FTBFS: failed tests)

Your message dated Thu, 21 Dec 2023 08:40:26 + with message-id and subject line Bug#1058373: fixed in python-oslotest 1:4.5.0-5 has caused the Debian Bug report #1058373, regarding python-oslotest: FTBFS: failed tests to be marked as done. This means that you claim that the problem has been

Processed: Bug#1058531 marked as pending in heat

Processing control commands: > tag -1 pending Bug #1058531 [src:heat] heat: FTBFS: AttributeError: 'FileFinder' object has no attribute 'find_module' Added tag(s) pending. -- 1058531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058531 Debian Bug Tracking System Contact

Bug#1058531: marked as pending in heat

Control: tag -1 pending Hello, Bug #1058531 in heat 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:

Processed: Bug#1058373 marked as pending in python-oslotest

Processing control commands: > tag -1 pending Bug #1058373 [src:python-oslotest] python-oslotest: FTBFS: failed tests Added tag(s) pending. -- 1058373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1058373: marked as pending in python-oslotest

Control: tag -1 pending Hello, Bug #1058373 in python-oslotest 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:

Bug#1059165: [Pkg-javascript-devel] Bug#1059165: src:zlib: fails to migrate to testing for too long: triggers autopkgtest issues

Hi, On 20-12-2023 23:08, Jérémy Lal wrote: I did the one for burp. Thanks for that. Dolfin has active maintainers, though. I think I need to file a "flaky autopkgtest" bug report against dolfin. Paul OpenPGP_signature.asc Description: OpenPGP digital signature