Bug#1061660: liblwp-protocol-https-perl: Fail to verify certificates

2024-01-28 Thread Christian Marillat
On 28 janv. 2024 19:03, gregor herrmann wrote: > On Sun, 28 Jan 2024 18:44:02 +0100, Christian Marillat wrote: > >> > Does it work for you if you downgrade liblwp-protocol-https-perl to 6.11-1 >> > from testing? If yes, which of the two hunks from [0] is causing the >> > problem? >> This issue

Bug#1058752: bug#62572: Bug#1058752: bug#62572: cp --no-clobber behavior has changed

2024-01-28 Thread Paul Eggert
On 2024-01-28 05:22, Pádraig Brady wrote: At this stage it seems best for us go back to the original Linux behiavor (use case 3), and to silently deprecate -n in docs to document the portability issues with it. I'm not sure reverting would be best. It would introduce more confusion, and

Processed: Reopen

2024-01-28 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1044055 {Done: Andreas Tille } [src:mirtop] mirtop: test failure with pandas 2.0 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer

Processed: src:obs-studio: fails to migrate to testing for too long: FTBFS on ppc64el

2024-01-28 Thread Debian Bug Tracking System
Processing control commands: > close -1 30.0.2+dfsg-2 Bug #1061723 [src:obs-studio] src:obs-studio: fails to migrate to testing for too long: FTBFS on ppc64el Marked as fixed in versions obs-studio/30.0.2+dfsg-2. Bug #1061723 [src:obs-studio] src:obs-studio: fails to migrate to testing for too

Bug#1044055: Reopen

2024-01-28 Thread Andreas Tille
Control: reopen -1 I wrongly assumed that this issue has vanished. Thus reopening the bug. -- http://fam-tille.de

Bug#1061723: src:obs-studio: fails to migrate to testing for too long: FTBFS on ppc64el

2024-01-28 Thread Paul Gevers
Source: obs-studio Version: 29.1.3+dfsg-2 Severity: serious Control: close -1 30.0.2+dfsg-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1061420 Dear maintainer(s), The Release Team considers packages that are out-of-sync between

Bug#1061722: src:graph-tool: fails to migrate to testing for too long: FTBFS on ppc64el

2024-01-28 Thread Paul Gevers
Source: graph-tool Version: 2.58+ds-1 Severity: serious Control: close -1 2.59+ds-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1060786 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and

Processed: src:graph-tool: fails to migrate to testing for too long: FTBFS on ppc64el

2024-01-28 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.59+ds-1 Bug #1061722 [src:graph-tool] src:graph-tool: fails to migrate to testing for too long: FTBFS on ppc64el Marked as fixed in versions graph-tool/2.59+ds-1. Bug #1061722 [src:graph-tool] src:graph-tool: fails to migrate to testing for too long:

Processed: Re: Bug#1061421: Fails to start after an upgrade

2024-01-28 Thread Debian Bug Tracking System
Processing control commands: > tag -1 +help Bug #1061421 [wlgreet] Fails to start after an upgrade Ignoring request to alter tags of bug #1061421 to the same tags previously set -- 1061421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061421 Debian Bug Tracking System Contact

Bug#1061421: Fails to start after an upgrade

2024-01-28 Thread duck
Control: tag -1 +help Quack, On 2024-01-24 19:04, Arto Jantunen wrote: After a semi-recent upgrade (I'm not sure which one, as I don't reboot or restart my session after each one) of testing wlgreet no longer starts. Here is what I get when trying to start it under a manually launched sway

Processed: Re: Bug#1061421: Fails to start after an upgrade

2024-01-28 Thread Debian Bug Tracking System
Processing control commands: > tag -1 +help Bug #1061421 [wlgreet] Fails to start after an upgrade Added tag(s) help. -- 1061421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1061721: src:fortunes-it: fails to migrate to testing for too long: uploader built arch:all binaries

2024-01-28 Thread Paul Gevers
Source: fortunes-it Version: 2.2-1 Severity: serious Control: close -1 2.2-2 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 more than 30

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

2024-01-28 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.2-2 Bug #1061721 [src:fortunes-it] src:fortunes-it: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions fortunes-it/2.2-2. Bug #1061721 [src:fortunes-it] src:fortunes-it: fails to migrate to testing for

Bug#1061203: Ardour - GTK2 removal

2024-01-28 Thread Robin Gareus
Upcoming Ardour 8.3 no longer depends on GTK[mm]2.4. It still depends on glibmm-2.4 (>=2.32.0) which is available in trixie. We hope to release Ardour 8.3 (https://git.ardour.org/ardour/ardour) sometime mid February 2023, and it would be nice if DDs could check feasibility of packaging it

Bug#1061717: 4ti2: NMU diff for 64-bit time_t transition

2024-01-28 Thread Steve Langasek
Source: 4ti2 Version: 1.6.10+ds-1.1 Severity: serious Tags: patch pending Justification: library ABI skew on upgrade User: debian-...@lists.debian.org Usertags: time-t Dear maintainer, As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond

Processed: Re: Bug#1061692: chirp fails to start with 'No module named 'chirp.stock_configs'

2024-01-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 1061692 +patch Bug #1061692 [chirp] chirp fails to start with 'No module named 'chirp.stock_configs' Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1061692:

Bug#1061692: chirp fails to start with 'No module named 'chirp.stock_configs'

2024-01-28 Thread Harlan Lieberman-Berg
tag 1061692 +patch thanks I've tested it, and it seems that manually adding the path to d/install fixes the problem fine. Patch attached. Sincerely, -- Harlan Lieberman-Berg ~hlieberman From 9d9fc8e0a1b46af0c9bf13e7ff982af1b9e15c07 Mon Sep 17 00:00:00 2001 From: Harlan Lieberman-Berg Date:

Bug#1052866: python-plaster: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2024-01-28 Thread Scott Talbert
On Sun, 28 Jan 2024, Andreas Tille wrote: Hi, I upgraded python-plaster to latest upstream - but this did not changed the test suite error. I suspect the issue is because dh-python is clobbering the *.egg-info directories in the tests directory during the 'clean' target. While this is

Bug#1061015: pygame-sdl2: FTBFS: Cannot assign type 'Sint64 (SDL_RWops *) except? -1 nogil' to 'Sint64 (*)(SDL_RWops *) noexcept'

2024-01-28 Thread Simon McVittie
On Sun, 28 Jan 2024 at 22:49:37 +0100, Alexandre Detiste wrote: > Le jeu. 25 janv. 2024 à 11:15, Simon McVittie a écrit : > > I also don't understand where these new upstream releases are coming from, > > because https://github.com/renpy/pygame_sdl2 only has tags for 8.1.0, > > and there don't

Processed: your mail

2024-01-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 1060848 Bug #1060848 {Done: Jonas Smedegaard } [src:rust-isahc] rust-isahc: Autopkgtest failures 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them.

Bug#1060848: (no subject)

2024-01-28 Thread Matthias Geiger
reopen 1060848 thanks still present in the latest upload. -- Matthias Geiger Debian Maintainer "Freiheit ist immer Freiheit des anders Denkenden" -- Rosa Luxemburg OpenPGP_0x18BD106B3B6C5475.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital

Processed: merging 1056852 1056462 1055710

2024-01-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 1056852 1056462 1055710 Bug #1056852 [src:python-cassandra-driver] python-cassandra-driver: ftbfs with cython 3.0.x Bug #1056852 [src:python-cassandra-driver] python-cassandra-driver: ftbfs with cython 3.0.x Added tag(s) ftbfs. Bug

Bug#1038426: marked as done (renpy: Uncaught exception occurred when attempting to start)

2024-01-28 Thread Debian Bug Tracking System
Your message dated Sun, 28 Jan 2024 21:50:28 + with message-id and subject line Bug#1038426: fixed in renpy 8.1.3+dfsg-1 has caused the Debian Bug report #1038426, regarding renpy: Uncaught exception occurred when attempting to start to be marked as done. This means that you claim that the

Bug#1061451: marked as done (renpy: remove dependency on python3-future)

2024-01-28 Thread Debian Bug Tracking System
Your message dated Sun, 28 Jan 2024 21:50:28 + with message-id and subject line Bug#1061451: fixed in renpy 8.1.3+dfsg-1 has caused the Debian Bug report #1061451, regarding renpy: remove dependency on python3-future to be marked as done. This means that you claim that the problem has been

Bug#1056883: marked as done (renpy: ftbfs with cython 3.0.x)

2024-01-28 Thread Debian Bug Tracking System
Your message dated Sun, 28 Jan 2024 21:50:28 + with message-id and subject line Bug#1056883: fixed in renpy 8.1.3+dfsg-1 has caused the Debian Bug report #1056883, regarding renpy: ftbfs with cython 3.0.x to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1055736: marked as done (renpy b-d's on python3-all-dev, but only builds for the default python version)

2024-01-28 Thread Debian Bug Tracking System
Your message dated Sun, 28 Jan 2024 21:50:28 + with message-id and subject line Bug#1055736: fixed in renpy 8.1.3+dfsg-1 has caused the Debian Bug report #1055736, regarding renpy b-d's on python3-all-dev, but only builds for the default python version to be marked as done. This means that

Bug#1061015: pygame-sdl2: FTBFS: Cannot assign type 'Sint64 (SDL_RWops *) except? -1 nogil' to 'Sint64 (*)(SDL_RWops *) noexcept'

2024-01-28 Thread Alexandre Detiste
Le jeu. 25 janv. 2024 à 11:15, Simon McVittie a écrit : > > Control: affects -1 + src:renpy > > On Tue, 16 Jan 2024 at 20:43:34 +0100, Lucas Nussbaum wrote: > > During a rebuild of all packages in sid, your package failed to build > > on amd64. > > > > > src/pygame_sdl2/rwobject.pyx:336:22:

Bug#1056852: python-cassandra-driver: ftbfs with cython 3.0.x

2024-01-28 Thread Emmanuel Arias
Hi! Thanks for your work. I forgot push my last changes. I have already fixed the two tests. One of them is that upstream is using a deprecated method in tests [0]. The other issue was that they still use asyncore [1]. Now I will upload python-cassandra-driver soon. [0]

Bug#1044055: marked as done (mirtop: test failure with pandas 2.0)

2024-01-28 Thread Debian Bug Tracking System
Your message dated Sun, 28 Jan 2024 21:33:20 + with message-id and subject line Bug#1044055: fixed in mirtop 0.4.25-4 has caused the Debian Bug report #1044055, regarding mirtop: test failure with pandas 2.0 to be marked as done. This means that you claim that the problem has been dealt

Bug#1061659: Fwd: Bug#1061659: src:golang-github-hanwen-go-fuse: fails to migrate to testing for too long: i386 autopkgtest regression

2024-01-28 Thread Nilesh Patra
+Maytha who prepared the upload. On Sun, Jan 28, 2024 at 05:05:55PM +, Julian Gilbey wrote: > Hi Nilesh, > > You did the last upload of this package - do you have any idea about > this bug? I've been trying to track it down for the past hour but I don't have a fix that I am confident

Bug#1061703: gnome-characters nocheck FTBFS: ../meson.build:47:14: ERROR: Program '/usr/bin/gjs-console' not found or not executable

2024-01-28 Thread Helmut Grohne
Source: gnome-characters Version: 45.0-2 Severity: serious Tags: ftbfs Hi, gnome-characters fails to build from source when built with the nocheck build profile. A build ends with: | Run-time dependency gjs-1.0 found: YES 1.78.1 | env[PKG_CONFIG_PATH]: | env[PKG_CONFIG]:

Processed: Bug#1061451 marked as pending in renpy

2024-01-28 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1061451 [renpy] renpy: remove dependency on python3-future Added tag(s) pending. -- 1061451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1061451: marked as pending in renpy

2024-01-28 Thread Alexandre Detiste
Control: tag -1 pending Hello, Bug #1061451 in renpy 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#1061659: Fwd: Bug#1061659: src:golang-github-hanwen-go-fuse: fails to migrate to testing for too long: i386 autopkgtest regression

2024-01-28 Thread Shengjing Zhu
Control: forwarded -1 https://github.com/hanwen/go-fuse/issues/502 On Mon, Jan 29, 2024 at 1:42 AM Julian Gilbey wrote: > > Hi Nilesh, > > You did the last upload of this package - do you have any idea about > this bug? > See https://github.com/hanwen/go-fuse/issues/502 -- Shengjing Zhu

Processed: Re: Bug#1061659: Fwd: Bug#1061659: src:golang-github-hanwen-go-fuse: fails to migrate to testing for too long: i386 autopkgtest regression

2024-01-28 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/hanwen/go-fuse/issues/502 Bug #1061659 {Done: Paul Gevers } [src:golang-github-hanwen-go-fuse] src:golang-github-hanwen-go-fuse: fails to migrate to testing for too long: i386 autopkgtest regression Set Bug forwarded-to-address to

Processed: Re: Bug#1060705: grub-pc: Symbol grub_env_get not found

2024-01-28 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1060705 [grub-pc] grub-pc: Symbol grub_env_get not found Severity set to 'important' from 'grave' -- 1060705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060705 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1060705: grub-pc: Symbol grub_env_get not found

2024-01-28 Thread Bastian Germann
Control: severity -1 important Am 23.01.24 um 14:21 schrieb Julian Andres Klode: If I don't hear other reports this week I'll have to assume that's a fluke on your end - weird things happen sometimes - and close it. Unfortunately, I did not have any time for this during this week - the i386

Bug#1052826: Broken entrypoints package: actually a pybuild issue?

2024-01-28 Thread Andreas Tille
Am Sun, Jan 28, 2024 at 08:13:01PM +0100 schrieb julien.pu...@gmail.com: > > > > upstream page[1] says: > > > >   This package is in maintenance-only mode. New code should use the > >   importlib.metadata module in the Python standard library to find > > and load entry points. > > > > So it

Bug#1061696: gnome-video-arcade: Remove unmaintained package?

2024-01-28 Thread Jeremy Bícha
Source: gnome-video-arcade Version: 0.8.8-5 Severity: serious X-Debbugs-CC: jo...@debian.org Jordi, what do you think about removing gnome-video-arcade from Debian? See https://bugs.debian.org/1061694 Thank you, Jeremy Bícha

Bug#1052826: Broken entrypoints package: actually a pybuild issue?

2024-01-28 Thread julien . puydt
Hi, Le dimanche 28 janvier 2024 à 08:17 +0100, Andreas Tille a écrit : > Hi Jullien, > > upstream page[1] says: > >   This package is in maintenance-only mode. New code should use the >   importlib.metadata module in the Python standard library to find > and load entry points. > > So it seems

Bug#1061694: gnome-video-arcade: Please stop using libsoup2.4

2024-01-28 Thread Jeremy Bícha
Source: gnome-video-arcade Version: 0.8.8-5 Severity: serious Tags: trixie sid We would like to stop building libsoup2.4 and only use libsoup3 instead. gnome-video-arcade has been archived which means no bug reports, merge requests, or code fixes are being accepted. Maybe we should do like

Bug#983507: marked as done (mame FTBFS on armel and mipsel: Cannot allocate memory (armel) / ar failure (mipsel))

2024-01-28 Thread Debian Bug Tracking System
Your message dated Sun, 28 Jan 2024 14:02:00 -0500 with message-id and subject line Re: mame FTBFS on armel and mipsel: Cannot allocate memory (armel) / ar failure (mipsel) has caused the Debian Bug report #983507, regarding mame FTBFS on armel and mipsel: Cannot allocate memory (armel) / ar

Bug#1061692: chirp fails to start with 'No module named 'chirp.stock_configs'

2024-01-28 Thread Harlan Lieberman-Berg
Package: chirp Version: 1:20240122-1 Severity: grave X-Debbugs-Cc: deb...@jouellet.net, hlieber...@debian.org Hello Dave, all, Thank you for updating chirp! Unfortunately, it seems that pybuild may have failed to pick up one of the necessary directories that contains the stock configurations.

Bug#1061690: marked as done (python3-setuptools-gettext 0.1.10-1 makes breezy FTBFS)

2024-01-28 Thread Debian Bug Tracking System
Your message dated Sun, 28 Jan 2024 18:12:39 + with message-id and subject line Fixed in 0.1.10-2 has caused the Debian Bug report #1061690, regarding python3-setuptools-gettext 0.1.10-1 makes breezy FTBFS to be marked as done. This means that you claim that the problem has been dealt with.

Processed: python3-setuptools-gettext 0.1.10-1 makes breezy FTBFS

2024-01-28 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:breezy Bug #1061690 [python3-setuptools-gettext] python3-setuptools-gettext 0.1.10-1 makes breezy FTBFS Added indication that 1061690 affects src:breezy -- 1061690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061690 Debian Bug Tracking

Bug#1061690: python3-setuptools-gettext 0.1.10-1 makes breezy FTBFS

2024-01-28 Thread Adrian Bunk
Package: python3-setuptools-gettext Version: 0.1.10-1 Severity: serious Tags: ftbfs Control: affects -1 src:breezy https://buildd.debian.org/status/logs.php?pkg=breezy=3.3.5-2 ... running build_mo Traceback (most recent call last): File "/<>/setup.py", line 225, in setup( File

Bug#1061689: kdevelop512-libs: identified for time_t transition but no ABI in shlibs

2024-01-28 Thread Steve Langasek
Package: kdevelop512-libs Version: 4:23.08.1-2 Severity: serious User: debian-...@lists.debian.org Usertags: time-t Hi Pino, Analysis of the archive for the 64-bit time_t transition[0][1] identifies kdevelop512-libs as an affected package, on the basis that the headers could not be compiled and

Bug#1061660: liblwp-protocol-https-perl: Fail to verify certificates

2024-01-28 Thread gregor herrmann
On Sun, 28 Jan 2024 18:44:02 +0100, Christian Marillat wrote: > > Does it work for you if you downgrade liblwp-protocol-https-perl to 6.11-1 > > from testing? If yes, which of the two hunks from [0] is causing the > > problem? > This issue doesn't exist with 6.11-1. I've seen this bug when 6.12

Processed: raise pandas 2.x severity to RC

2024-01-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1053943 serious Bug #1053943 [src:q2-taxa] q2-taxa: test failure with pandas 2.1 Severity set to 'serious' from 'normal' > severity 1053939 serious Bug #1053939 [src:pymatgen] pymatgen: test failure with pandas 2.1 Severity set to

Processed: Re: tqdm and pandas 2.1 / python 3.12

2024-01-28 Thread Debian Bug Tracking System
Processing control commands: > retitle 1058160 tqdm: tests failing/hanging in Python 3.12 Bug #1058160 [src:tqdm] tqdm: tests failing/hanging in Python 3.12 Ignoring request to change the title of bug#1058160 to the same title -- 1058160:

Bug#1058160: tqdm and pandas 2.1 / python 3.12

2024-01-28 Thread Rebecca N. Palmer
Control: retitle 1058160 tqdm: tests failing/hanging in Python 3.12 That works for #1053946 (pandas 2.x), but #1058160 (python 3.12) is more than a single hanging test, and it's not immediately obvious what should be done. Attempted fix (caution, currently just skips the hanging test) and

Processed: Re: tqdm and pandas 2.1 / python 3.12

2024-01-28 Thread Debian Bug Tracking System
Processing control commands: > retitle 1058160 tqdm: tests failing/hanging in Python 3.12 Bug #1058160 [src:tqdm] tqdm: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Changed Bug title to 'tqdm: tests failing/hanging in Python 3.12' from 'tqdm: FTBFS: E: Build killed

Bug#1061660: liblwp-protocol-https-perl: Fail to verify certificates

2024-01-28 Thread Christian Marillat
On 28 janv. 2024 18:17, gregor herrmann wrote: [...] > Does it work for you if you downgrade liblwp-protocol-https-perl to 6.11-1 > from testing? If yes, which of the two hunks from [0] is causing the > problem? This issue doesn't exist with 6.11-1. I've seen this bug when 6.12 has been

Bug#1061659: Fwd: Bug#1061659: src:golang-github-hanwen-go-fuse: fails to migrate to testing for too long: i386 autopkgtest regression

2024-01-28 Thread Julian Gilbey
Hi Nilesh, You did the last upload of this package - do you have any idea about this bug? Best wishes, Julian - Forwarded message from Paul Gevers - Date: Sun, 28 Jan 2024 08:50:51 +0100 From: Paul Gevers Subject: Bug#1061659: src:golang-github-hanwen-go-fuse: fails to migrate to

Bug#1061660: liblwp-protocol-https-perl: Fail to verify certificates

2024-01-28 Thread gregor herrmann
Control: tag -1 + unreproducible On Sun, 28 Jan 2024 09:07:00 +0100, Christian Marillat wrote: > uscan from devscipts package fail to verify certificates afetr upgrading > to liblwp-protocol-https-perl 6.12-1 Thanks for your bug report. > , > | uscan warn: In watchfile debian/watch,

Processed: Re: Bug#1061660: liblwp-protocol-https-perl: Fail to verify certificates

2024-01-28 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + unreproducible Bug #1061660 [liblwp-protocol-https-perl] liblwp-protocol-https-perl: Fail to verify certificates Added tag(s) unreproducible. -- 1061660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061660 Debian Bug Tracking System Contact

Bug#1061341: cyrus-common: identified for time_t transition but no ABI in shlibs

2024-01-28 Thread Steve Langasek
On Tue, Jan 23, 2024 at 08:32:18AM +0400, Yadd wrote: > Control: tags -1 + moreinfo > On 1/23/24 00:43, Steve Langasek wrote: > > Package: cyrus-common > > Version: 3.8.1-1 > > Severity: serious > > User: debian-...@lists.debian.org > > Usertags: time-t > > Dear maintainers, > > Analysis of the

Processed: tagging 1061341

2024-01-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1061341 - moreinfo Bug #1061341 [cyrus-common] cyrus-common: identified for time_t transition but no ABI in shlibs Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1061341:

Processed: bug 1061667 is forwarded to bry...@giraffe-data.com

2024-01-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # mail sent > forwarded 1061667 bry...@giraffe-data.com Bug #1061667 [netpbm] netpbm: ppmtowinicon crash makes kcemu FTBFS Set Bug forwarded-to-address to 'bry...@giraffe-data.com'. > thanks Stopping processing here. Please contact me if you

Bug#1061335: marked as done (python3-breezy: ships files in `/build`)

2024-01-28 Thread Debian Bug Tracking System
Your message dated Sun, 28 Jan 2024 15:04:37 + with message-id and subject line Bug#1061335: fixed in breezy 3.3.5-2 has caused the Debian Bug report #1061335, regarding python3-breezy: ships files in `/build` to be marked as done. This means that you claim that the problem has been dealt

Bug#1051166: marked as done (FTBFS with doxygen 1.9.8)

2024-01-28 Thread Debian Bug Tracking System
Your message dated Sun, 28 Jan 2024 15:04:21 + with message-id and subject line Bug#1051166: fixed in breathe 4.35.0-3 has caused the Debian Bug report #1051166, regarding FTBFS with doxygen 1.9.8 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1061301: marked as done (breezy fails autopkg tests (missing dependency) and accessing the net during the build)

2024-01-28 Thread Debian Bug Tracking System
Your message dated Sun, 28 Jan 2024 15:04:37 + with message-id and subject line Bug#1061301: fixed in breezy 3.3.5-2 has caused the Debian Bug report #1061301, regarding breezy fails autopkg tests (missing dependency) and accessing the net during the build to be marked as done. This means

Bug#1061655: wine: FTBFS with error: unknown conversion type character ‘I’ in format [-Werror=format=]

2024-01-28 Thread Petter Reinholdtsen
I asked on #debian-arm for input, and got this suggestions: pere: 32-bit architectures failing., trying to format a 64-bit value? But from my reading of the format specifier `0x%0*I64x` it doesn't match the docs; I think it ought to be

Bug#1061667: netpbm: ppmtowinicon crash makes kcemu FTBFS

2024-01-28 Thread Andreas Metzler
On 2024-01-28 Adrian Bunk wrote: > ppmtowinicon -andpgms \ > kcemu-winicon_16x16.ppm kcemu-winicon_16x16.alpha.pgm \ > kcemu-winicon_32x32.ppm kcemu-winicon_32x32.alpha.pgm \ > kcemu-winicon_48x48.ppm kcemu-winicon_48x48.alpha.pgm \ > > kcemu-winicon.ico > malloc():

Bug#1051166: marked as pending in breathe

2024-01-28 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1051166 in breathe 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#1051166 marked as pending in breathe

2024-01-28 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1051166 [breathe-doc] FTBFS with doxygen 1.9.8 Added tag(s) pending. -- 1051166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051166 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1060794: marked as done (ccdproc fails tests, missing dependency)

2024-01-28 Thread Debian Bug Tracking System
Your message dated Sun, 28 Jan 2024 14:34:20 + with message-id and subject line Bug#1060794: fixed in ccdproc 2.4.1-2 has caused the Debian Bug report #1060794, regarding ccdproc fails tests, missing dependency to be marked as done. This means that you claim that the problem has been dealt

Bug#1061621: marked as done (filament: FTBFS: too few arguments to function call, expected 3, have 2)

2024-01-28 Thread Debian Bug Tracking System
Your message dated Sun, 28 Jan 2024 14:36:28 + with message-id and subject line Bug#1061621: fixed in filament 1.9.25+dfsg2-13 has caused the Debian Bug report #1061621, regarding filament: FTBFS: too few arguments to function call, expected 3, have 2 to be marked as done. This means that

Bug#1057617: marked as done (tracker-miners: FTBFS: tests failed)

2024-01-28 Thread Debian Bug Tracking System
Your message dated Sun, 28 Jan 2024 13:29:41 + with message-id and subject line Bug#1057617: fixed in tracker-miners 3.4.6-3 has caused the Debian Bug report #1057617, regarding tracker-miners: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been

Bug#1061542: marked as done (tracker-miners: FTBFS on amd64, arm64, loong64 and so on)

2024-01-28 Thread Debian Bug Tracking System
Your message dated Sun, 28 Jan 2024 13:29:41 + with message-id and subject line Bug#1057617: fixed in tracker-miners 3.4.6-3 has caused the Debian Bug report #1057617, regarding tracker-miners: FTBFS on amd64, arm64, loong64 and so on to be marked as done. This means that you claim that the

Processed: netpbm: ppmtowinicon crash makes kcemu FTBFS

2024-01-28 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:kcemu Bug #1061667 [netpbm] netpbm: ppmtowinicon crash makes kcemu FTBFS Added indication that 1061667 affects src:kcemu -- 1061667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061667 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1061667: netpbm: ppmtowinicon crash makes kcemu FTBFS

2024-01-28 Thread Adrian Bunk
Package: netpbm Version: 2:11.05.01-3 Severity: serious Tags: ftbfs Control: affects -1 src:kcemu https://buildd.debian.org/status/fetch.php?pkg=kcemu=riscv64=0.5.2%2Bdfsg-1%2Bb1=1706435423=0 ... ppmtowinicon -andpgms \ kcemu-winicon_16x16.ppm kcemu-winicon_16x16.alpha.pgm \

Bug#1061362: marked as done (kitty: multi-key sequences do not abort when pressing an unknown key, waits indefinitely)

2024-01-28 Thread Debian Bug Tracking System
Your message dated Sun, 28 Jan 2024 13:18:05 + with message-id and subject line Bug#1061362: fixed in kitty 0.32.1-1 has caused the Debian Bug report #1061362, regarding kitty: multi-key sequences do not abort when pressing an unknown key, waits indefinitely to be marked as done. This means

Bug#1058253: marked as done (python-spake2: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)

2024-01-28 Thread Debian Bug Tracking System
Your message dated Sun, 28 Jan 2024 13:19:09 + with message-id and subject line Bug#1058253: fixed in python-spake2 0.8-2.1 has caused the Debian Bug report #1058253, regarding python-spake2: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean:

Bug#1060310: marked as done (nsis-pluginapi: missing Breaks+Replaces: nsis-doc (<< 3.09-2))

2024-01-28 Thread Debian Bug Tracking System
Your message dated Sun, 28 Jan 2024 13:18:40 + with message-id and subject line Bug#1060310: fixed in nsis 3.09-3 has caused the Debian Bug report #1060310, regarding nsis-pluginapi: missing Breaks+Replaces: nsis-doc (<< 3.09-2) to be marked as done. This means that you claim that the

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

2024-01-28 Thread Debian Bug Tracking System
Your message dated Sun, 28 Jan 2024 12:45:09 +0100 with message-id and subject line done has caused the Debian Bug report #1052771, regarding pypuppetdb: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13 to be marked as done. This means

Bug#1058335: python-apt: FTBFS: AssertionError: pyflakes failed with: 1

2024-01-28 Thread s3v
Hi, I guess the change in pyflakes is intended, please see [1][2]. The FTBFS for src:python-apt 1.7.0 downloaded from shanpshot.d.o [3] vanishes after rebuilding with this commit reverted [4] (attached for saving your time and for double-checking purpose). Kind Regards [1]

Processed: forcibly merging 1057617 1061542

2024-01-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1057617 1061542 Bug #1057617 [src:tracker-miners] tracker-miners: FTBFS: tests failed Bug #1057617 [src:tracker-miners] tracker-miners: FTBFS: tests failed Marked as found in versions tracker-miners/3.4.6-2. Added tag(s) patch. Bug

Bug#1058720: slurm-wlm: CVE-2023-49933 CVE-2023-49935 CVE-2023-49936 CVE-2023-49937 CVE-2023-49938

2024-01-28 Thread Salvatore Bonaccorso
Hi Gennaro, On Sat, Dec 30, 2023 at 10:55:32PM +0100, Gennaro Oliva wrote: > Dear Salvatore, > I prepared an updated version of the slurm-wlm package for bookworm in > response to CVE-2023-49933/49935/49936/49937/49938 > > The package can be found here: > >

Processed: block 1058428 with 1032208

2024-01-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1058428 with 1032208 Bug #1058428 [src:python-twilio] python-twilio: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 1058428 was not blocked by any bugs. 1058428 was not

Bug#1061660: liblwp-protocol-https-perl: Fail to verify certificates

2024-01-28 Thread Christian Marillat
Package: liblwp-protocol-https-perl Version: 6.12-1 Severity: serious Dear Maintainer, uscan from devscipts package fail to verify certificates afetr upgrading to liblwp-protocol-https-perl 6.12-1 , | uscan warn: In watchfile debian/watch, reading webpage |