Bug#1092683: marked as done (lomiri-thumbnailer: FTBFS with taglib 2.0)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Mon, 13 Jan 2025 07:49:08 + with message-id and subject line Bug#1092683: fixed in lomiri-thumbnailer 3.0.4-2 has caused the Debian Bug report #1092683, regarding lomiri-thumbnailer: FTBFS with taglib 2.0 to be marked as done. This means that you claim that the problem has

Bug#1092533: jupyter-client: FTBFS: make[2]: *** [Makefile:55: html] Error 2

2025-01-12 Thread Stuart Prescott
Control: tags -1 + patch On 13/01/2025 12:59, Stuart Prescott wrote: The error «(SEVERE/4) Unexpected section title.» is about the Parameters and Returns headings that are inserted into the API docs (running sphinx with `-v -v -v` revealed that). There is on-the-fly manipulation of the docstr

Processed: Re: Bug#1092533: jupyter-client: FTBFS: make[2]: *** [Makefile:55: html] Error 2

2025-01-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1092533 [src:jupyter-client] jupyter-client: FTBFS: make[2]: *** [Makefile:55: html] Error 2 Added tag(s) patch. -- 1092533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092533 Debian Bug Tracking System Contact ow...@bugs.debian.org wit

Processed: Bug#1092683 marked as pending in lomiri-thumbnailer

2025-01-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1092683 [src:lomiri-thumbnailer] lomiri-thumbnailer: FTBFS with taglib 2.0 Added tag(s) pending. -- 1092683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092683 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1092683: marked as pending in lomiri-thumbnailer

2025-01-12 Thread Mike Gabriel
Control: tag -1 pending Hello, Bug #1092683 in lomiri-thumbnailer 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/ubports-team/lomiri-thumbnailer/-/commit/a97b9

Processed: Re: Bug#1092889: linux-image-6.1.0-29-arm64: oops in nft_rhash_gc

2025-01-12 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:linux Bug #1092889 [linux-image-6.1.0-29-arm64] linux-image-6.1.0-29-arm64: oops in nft_rhash_gc Bug reassigned from package 'linux-image-6.1.0-29-arm64' to 'src:linux'. No longer marked as found in versions linux-signed-arm64/6.1.123+1. Ignoring req

Bug#1064855: xfce4-power-manager: Display is shutdown despite activity

2025-01-12 Thread Phil Wyett
On Sun, 12 Jan 2025 16:55:17 +0100 =?ISO-8859-1?Q?J=F6rg_Frings-F=FCrst?= wrote: > severity 1064855 grave > thanks > > > Another problem is that the login credentials are required every time > the monitors go dark. > > Although locking is switched off. > > I therefore set the severity to Grave

Bug#1092773: marked as done (php-netscape-bookmark-parser: Depends on php-psr-log (<< 2~~))

2025-01-12 Thread Debian Bug Tracking System
Your message dated Mon, 13 Jan 2025 07:19:13 + with message-id and subject line Bug#1092773: fixed in php-netscape-bookmark-parser 4.0.0-4 has caused the Debian Bug report #1092773, regarding php-netscape-bookmark-parser: Depends on php-psr-log (<< 2~~) to be marked as done. This means that y

Processed: limit source to php-netscape-bookmark-parser, tagging 1092773

2025-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > limit source php-netscape-bookmark-parser Limiting to bugs with field 'source' containing at least one of 'php-netscape-bookmark-parser' Limit currently set to 'source':'php-netscape-bookmark-parser' > tags 1092773 + pending Bug #1092773 [src:ph

Processed: limit source to php-netscape-bookmark-parser, tagging 1092773

2025-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > limit source php-netscape-bookmark-parser Limiting to bugs with field 'source' containing at least one of 'php-netscape-bookmark-parser' Limit currently set to 'source':'php-netscape-bookmark-parser' > tags 1092773 + pending Bug #1092773 [src:ph

Bug#1092206: marked as done (libreoffice still b-d's on GCC 12 on i386, which should not be part of the trixie release)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Mon, 13 Jan 2025 06:15:02 + with message-id and subject line Bug#1092206: fixed in libreoffice 4:25.2.0~rc2-1 has caused the Debian Bug report #1092206, regarding libreoffice still b-d's on GCC 12 on i386, which should not be part of the trixie release to be marked as done.

Bug#1089192: golang-golang-x-net: FTBFS: FAIL: TestNumICANNRules

2025-01-12 Thread Otto Kekäläinen
Hi Maytham! I don't see any updates at https://salsa.debian.org/go-team/packages/golang-golang-x-net/-/commits/debian/sid since I posted my feedback, so I assume I should continue waiting? On Sun, 5 Jan 2025 at 11:51, Otto Kekäläinen wrote: > Hi! > > (I am cc'ing Anthony so he is aware that th

Bug#1092681: marked as done (deepin-music: FTBFS with taglib 2.0)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Mon, 13 Jan 2025 03:06:01 + with message-id and subject line Bug#1092681: fixed in deepin-music 6.2.40-1 has caused the Debian Bug report #1092681, regarding deepin-music: FTBFS with taglib 2.0 to be marked as done. This means that you claim that the problem has been dealt

Bug#1092533: jupyter-client: FTBFS: make[2]: *** [Makefile:55: html] Error 2

2025-01-12 Thread Stuart Prescott
The error «(SEVERE/4) Unexpected section title.» is about the Parameters and Returns headings that are inserted into the API docs (running sphinx with `-v -v -v` revealed that). There is on-the-fly manipulation of the docstrings in jupyter_client/client.py::reqrep - I was able to get the docs

Processed: tagging 1074913, found 1092330 in 3.0.1+ds-1, tagging 1092748, tagging 1092687, tagging 1030130 ...

2025-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1074913 + patch Bug #1074913 {Done: Debian FTP Masters } [src:directfb] directfb: ftbfs with GCC-14 Added tag(s) patch. > found 1092330 3.0.1+ds-1 Bug #1092330 [libmimalloc2.0] libmimalloc2.0: fails to provide libmimalloc.so.2.0 Ignoring re

Processed: closing 1092063

2025-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1092063 Bug #1092063 [src:kdevelop-python] kdevelop-python ftbfs with Python 3.13 as the default Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1092063: https://bugs.debian.org/cgi-bin/b

Bug#1089513: workaround

2025-01-12 Thread Ole Marggraf
On Sun, 12 Jan 2025 12:32:53 + junk mail wrote: I am on the testing release, and use KDE. linux: 6.12.6-1; nvidia-driver 535.216.03. The problem I was experiencing is that I couldn't change the display resolution nor refresh rate. These issues occurred after updating the Linux kernel, eve

Bug#1092072: marked as done (brian ftbfs with Python 3.13 as the default)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Mon, 13 Jan 2025 00:06:08 + with message-id and subject line Bug#1091403: fixed in brian 2.8.0-1 has caused the Debian Bug report #1091403, regarding brian ftbfs with Python 3.13 as the default to be marked as done. This means that you claim that the problem has been dealt

Bug#1091403: marked as done (brian FTBFS with Python 3.13 as default)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Mon, 13 Jan 2025 00:06:08 + with message-id and subject line Bug#1091403: fixed in brian 2.8.0-1 has caused the Debian Bug report #1091403, regarding brian FTBFS with Python 3.13 as default to be marked as done. This means that you claim that the problem has been dealt with

Bug#1092748: marked as done (Autopkgtests fail with Python 3.13: DeprecationWarning: 'maxsplit' is passed as positional argument)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Mon, 13 Jan 2025 00:06:17 + with message-id and subject line Bug#1092748: fixed in dnarrange 1.5.3-1.1 has caused the Debian Bug report #1092748, regarding Autopkgtests fail with Python 3.13: DeprecationWarning: 'maxsplit' is passed as positional argument to be marked as do

Bug#1092428: marked as done (tailspin: FTBFS: build-dependency not installable: librust-terminal-size-0.3+default-dev)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Mon, 13 Jan 2025 00:50:28 +0100 with message-id <173672582895.1248275.9138918350727703...@cairon.jones.dk> and subject line Re: Bug#1092428: tailspin: FTBFS: build-dependency not installable: librust-terminal-size-0.3+default-dev has caused the Debian Bug report #1092428, regard

Bug#1091399: marked as done (python3-beanprice has an undeclared file conflict on /usr/bin/bean-price)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jan 2025 23:49:25 + with message-id and subject line Bug#1091399: fixed in beanprice 1.2.1+git20240619-3 has caused the Debian Bug report #1091399, regarding python3-beanprice has an undeclared file conflict on /usr/bin/bean-price to be marked as done. This means t

Bug#1091311: marked as done (ario: FTBFS on armhf: preferences/ario-server-preferences.c:192:51: error: passing argument 1 of 'ctime' from incompatible pointer type [-Wincompatible-pointer-types])

2025-01-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jan 2025 23:49:17 + with message-id and subject line Bug#1091311: fixed in ario 1.6-1.3 has caused the Debian Bug report #1091311, regarding ario: FTBFS on armhf: preferences/ario-server-preferences.c:192:51: error: passing argument 1 of 'ctime' from incompatible po

Bug#1092748: marked as pending in dnarrange

2025-01-12 Thread Alexandre Detiste
Control: tag -1 pending Hello, Bug #1092748 in dnarrange 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/med-team/dnarrange/-/commit/fb3eb92c8eab0be0e4a1d4a61ff

Processed: Bug#1092748 marked as pending in dnarrange

2025-01-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1092748 [src:dnarrange] Autopkgtests fail with Python 3.13: DeprecationWarning: 'maxsplit' is passed as positional argument Added tag(s) pending. -- 1092748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092748 Debian Bug Tracking System C

Bug#1092519: ionit: FTBFS: AssertionError: Regex didn't match: "ERROR:ionit:Failed to read JSON from '[^']*config/invalid-json/invalid.json': Expecting property name enclosed in double quotes: line 3

2025-01-12 Thread Colin Watson
On Wed, Jan 08, 2025 at 08:34:02PM +0100, Lucas Nussbaum wrote: > > FAIL: test_invalid_json > > (tests.test_ionit.TestCollectContext.test_invalid_json) > > Test: Run collect_context(["tests/config/invalid-json"]) > > -- > > Traceb

Processed: tagging 1092519

2025-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1092519 + patch Bug #1092519 [src:ionit] ionit: FTBFS: AssertionError: Regex didn't match: "ERROR:ionit:Failed to read JSON from '[^']*config/invalid-json/invalid.json': Expecting property name enclosed in double quotes: line 3 column 1 \\(

Bug#1074854: brasero: FTBFS with gcc-14

2025-01-12 Thread Rebecca N. Palmer
On 12/01/2025, Simon McVittie wrote: Normally we keep the patch's upstream authorship when applying patches, So do I when using DEP-3 (Author:) tags, which is my more usual format. (because it looked like you've taken the patch directly from upstream rather than writing any code yourself).

Processed: tagging 1090225

2025-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1090225 + fixed-upstream Bug #1090225 [src:freezegun] freezegun: FTBFS: E AssertionError: FakeDate(2013, 4, 9) != datetime.datetime(2013, 4, 9, 0, 0) Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you n

Bug#1092748: Autopkgtests fail with Python 3.13: DeprecationWarning: 'maxsplit' is passed as positional argument

2025-01-12 Thread Colin Watson
Control: tag -1 patch On Sat, Jan 11, 2025 at 02:17:47PM +0500, Andrey Rakhmatullin wrote: > https://ci.debian.net/packages/d/dnarrange/testing/amd64/56310221/ > > I assume "/usr/bin/dnarrange:561: DeprecationWarning: 'maxsplit' is passed as > positional argument" is what causes the failure. I'v

Processed: Re: Bug#1092748: Autopkgtests fail with Python 3.13: DeprecationWarning: 'maxsplit' is passed as positional argument

2025-01-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 patch Bug #1092748 [src:dnarrange] Autopkgtests fail with Python 3.13: DeprecationWarning: 'maxsplit' is passed as positional argument Added tag(s) patch. -- 1092748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092748 Debian Bug Tracking System Conta

Bug#1064555: marked as done (faketime: FTBFS on 32 bit architectures: Test Suites summary: 3 succeeded, 1 failed)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jan 2025 23:19:14 + with message-id and subject line Bug#1064555: fixed in faketime 0.9.10-2.4~exp0.1 has caused the Debian Bug report #1064555, regarding faketime: FTBFS on 32 bit architectures: Test Suites summary: 3 succeeded, 1 failed to be marked as done. This

Bug#1079346: marked as done (src:faketime: fails to migrate to testing for too long: FTBFS on 32 bit archs)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jan 2025 23:19:14 + with message-id and subject line Bug#1079346: fixed in faketime 0.9.10-2.4~exp0.1 has caused the Debian Bug report #1079346, regarding src:faketime: fails to migrate to testing for too long: FTBFS on 32 bit archs to be marked as done. This means

Bug#1032177: marked as done (faketime doesn't fake time (on i386))

2025-01-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jan 2025 23:19:14 + with message-id and subject line Bug#1032177: fixed in faketime 0.9.10-2.4~exp0.1 has caused the Debian Bug report #1032177, regarding faketime doesn't fake time (on i386) to be marked as done. This means that you claim that the problem has been

Bug#1067016: marked as done (osslsigncode: FTBFS on arm{el,hf}: test failures)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jan 2025 23:19:14 + with message-id and subject line Bug#1032177: fixed in faketime 0.9.10-2.4~exp0.1 has caused the Debian Bug report #1032177, regarding osslsigncode: FTBFS on arm{el,hf}: test failures to be marked as done. This means that you claim that the probl

Bug#1086944: sauce: diff for NMU version 0.9.2+nmu1

2025-01-12 Thread Niels Thykier
Ian Jackson: Niels Thykier writes ("Bug#1086944: sauce: diff for NMU version 0.9.2+nmu1"): Since the bug has now become RC, I am rescheduling it to 5 days (down from its original delay). Thanks for taking care of this. You are welcome. :) This package needs some love - I have a branch of

Bug#1092745: opensysusers: DEP17 diversions may delete systemd's systemd-sysuser

2025-01-12 Thread Chris Hofstaedtler
On Sun, Jan 12, 2025 at 08:20:22PM +0100, tho...@goirand.fr wrote: > On Jan 11, 2025 10:09, Helmut Grohne wrote: > > [..] In trixie and > > later, sysusers implementations are no longer coinstallable but mutually > > exclusive. This simplifies the story a lot. I propose mirroring the > > confli

Processed: Bug#1092206 marked as pending in libreoffice

2025-01-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1092206 [src:libreoffice] libreoffice still b-d's on GCC 12 on i386, which should not be part of the trixie release Ignoring request to alter tags of bug #1092206 to the same tags previously set -- 1092206: https://bugs.debian.org/cgi-bin/bugre

Bug#1092206: marked as pending in libreoffice

2025-01-12 Thread Rene Engelhard
Control: tag -1 pending Hello, Bug #1092206 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/-/commit/14c

Processed: Re: lomiri-thumbnailer: FTBFS with taglib 2.0

2025-01-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1092683 [src:lomiri-thumbnailer] lomiri-thumbnailer: FTBFS with taglib 2.0 Added tag(s) patch. -- 1092683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092683 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1092683: lomiri-thumbnailer: FTBFS with taglib 2.0

2025-01-12 Thread Boyuan Yang
Control: tags -1 + patch X-Debbugs-CC: sunwea...@debian.org mariog...@debian.org Hi, On Fri, 10 Jan 2025 12:07:39 -0500 Boyuan Yang wrote: Source: lomiri-thumbnailer Version: 3.0.3-1 Severity: important User: debian-multime...@lists.debian.org Usertags: taglib2.0 The package fails to build wi

Bug#1064555: faketime on 32-bit: Preparing upload

2025-01-12 Thread Ian Jackson
Control: tags -1 patch pending Hi. Thanks, Helge, for those patches. With this message I'm tagging this bug "patch" to say there's a patch available. I'm doing some local testing, but so far, your patches seem to make the package pass its own build-time tests, at leaste. To the maintainer: I

Processed: faketime on 32-bit: Preparing upload

2025-01-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch pending Bug #1064555 [src:faketime] faketime: FTBFS on 32 bit architectures: Test Suites summary: 3 succeeded, 1 failed Added tag(s) patch and pending. -- 1064555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064555 Debian Bug Tracking System C

Bug#1074854: brasero: FTBFS with gcc-14

2025-01-12 Thread Simon McVittie
On Sun, 12 Jan 2025 at 12:28:10 +, Simon McVittie wrote: > I have a USB optical drive and some media, so I can at least do a > smoke-test on it to get this RC bug fixed, assuming my blank media > haven't completely delaminated by now. In fact it doesn't work: with the patch Rebecca found, it c

Bug#1092772: marked as done (linux-image-6.1.0-29-arm64: kernel OOPS when using nftables)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jan 2025 22:17:09 + with message-id and subject line Bug#1092772: fixed in linux 6.1.124-1 has caused the Debian Bug report #1092772, regarding linux-image-6.1.0-29-arm64: kernel OOPS when using nftables to be marked as done. This means that you claim that the probl

Bug#1092806: marked as done (linux-image-6.1.0-29-arm64: Oops: Unable to handle kernel paging request at virtual address ffff0000e1fb238c)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jan 2025 22:17:09 + with message-id and subject line Bug#1092772: fixed in linux 6.1.124-1 has caused the Debian Bug report #1092772, regarding linux-image-6.1.0-29-arm64: Oops: Unable to handle kernel paging request at virtual address e1fb238c to be marked

Bug#1092796: Autopkgtests fail with Python 3.13: OSError: [Errno 9] Bad file descriptor

2025-01-12 Thread Colin Watson
Control: tag -1 patch On Sat, Jan 11, 2025 at 10:38:55PM +0500, Andrey Rakhmatullin wrote: > https://ci.debian.net/packages/w/wireless-regdb/testing/amd64/56320878/ > > autopkgtest [09:10:13]: test check-signatures: [--- > Exception ignored in: <_io.BufferedReader name=3> > Tr

Processed: Re: Bug#1092796: Autopkgtests fail with Python 3.13: OSError: [Errno 9] Bad file descriptor

2025-01-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 patch Bug #1092796 [wireless-regdb] Autopkgtests fail with Python 3.13: OSError: [Errno 9] Bad file descriptor Added tag(s) patch. -- 1092796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092796 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1092890: mesa: regression in 24.3: software rendering crashes on ppc64el with segmentation fault

2025-01-12 Thread Dmitry Shachnev
Package: libglx-mesa0 Version: 24.3.0~rc1-1 Severity: serious Justification: makes other packages FTBFS Forwarded: https://gitlab.freedesktop.org/mesa/mesa/-/issues/12452 Dear Maintainer, When mesa was updated to 24.3 branch a few days ago, some packages of our Qt/KDE team started to FTBFS on ppc

Bug#1092206: marked as pending in libreoffice

2025-01-12 Thread Rene Engelhard
Control: tag -1 pending Hello, Bug #1092206 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/-/commit/14c

Processed: Bug#1092206 marked as pending in libreoffice

2025-01-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1092206 [src:libreoffice] libreoffice still b-d's on GCC 12 on i386, which should not be part of the trixie release Added tag(s) pending. -- 1092206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092206 Debian Bug Tracking System Contact o

Bug#1092888: marked as done (sioyek: FTBFS)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jan 2025 21:38:27 + with message-id and subject line Bug#1092888: fixed in sioyek 2.0.0+dfsg-5.1 has caused the Debian Bug report #1092888, regarding sioyek: FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not t

Bug#1092687: glasscoder: FTBFS with taglib 2.0

2025-01-12 Thread Boyuan Yang
Control: forwarded -1 https://github.com/ElvishArtisan/GlassCoder/issues/27 Control: tags -1 + patch On Fri, 10 Jan 2025 12:38:46 -0500 Boyuan Yang wrote: Source: glasscoder Version: 2.0.1-2 Severity: important User: debian-multime...@lists.debian.org Usertags: taglib2.0 The package fails to b

Processed: Re: glasscoder: FTBFS with taglib 2.0

2025-01-12 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/ElvishArtisan/GlassCoder/issues/27 Bug #1092687 [src:glasscoder] glasscoder: FTBFS with taglib 2.0 Set Bug forwarded-to-address to 'https://github.com/ElvishArtisan/GlassCoder/issues/27'. > tags -1 + patch Bug #1092687 [src:glasscoder

Bug#1092417: marked as done (userv: FTBFS: make[2]: *** [Makefile:80: install] Error 1)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jan 2025 21:22:00 + with message-id and subject line Bug#1092417: fixed in userv 1.2.1~beta5 has caused the Debian Bug report #1092417, regarding userv: FTBFS: make[2]: *** [Makefile:80: install] Error 1 to be marked as done. This means that you claim that the probl

Bug#1092888: sioyek: FTBFS

2025-01-12 Thread Bastian Germann
Please find a debdiff attached. I am uploading it as NMU.diff -Nru sioyek-2.0.0+dfsg/debian/changelog sioyek-2.0.0+dfsg/debian/changelog --- sioyek-2.0.0+dfsg/debian/changelog 2024-05-24 17:51:04.0 + +++ sioyek-2.0.0+dfsg/debian/changelog 2025-01-12 21:03:41.0 + @@ -1,3 +

Processed: Re: mixxx: FTBFS with taglib 2.0: test failed

2025-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1092707 mixxx/2.5.0+dfsg-2 Bug #1092707 [src:mixxx] mixxx: FTBFS with taglib 2.0: test failed No longer marked as found in versions mixxx/2.5.0+dfsg-2. > close 1092707 Bug #1092707 [src:mixxx] mixxx: FTBFS with taglib 2.0: test failed Mar

Bug#1092707: mixxx: FTBFS with taglib 2.0: test failed

2025-01-12 Thread Boyuan Yang
notfound 1092707 mixxx/2.5.0+dfsg-2 close 1092707 thanks It looks like the taglib 2.0.2 rebuild of mixxx actually passed. This bug report is no longer valid. Closing accordingly. Thanks, Boyuan Yang On Fri, 10 Jan 2025 13:51:22 -0500 Boyuan Yang wrote: Source: mixxx Version: 2.5.0+dfsg-2 Seve

Bug#1092417: userv: FTBFS: make[2]: *** [Makefile:80: install] Error 1

2025-01-12 Thread Ian Jackson
Ben Harris writes ("Bug#1092417: userv: FTBFS: make[2]: *** [Makefile:80: install] Error 1"): > I think using "binary-targets" is pretty much inevitable given that > /usr/bin/userv is setuid. Thanks for the verification. I am going to do as you suggest. Howeever, it may be possible to get this

Bug#1090285: marked as done (python-pyfakefs: FTBFS: INTERNALERROR> ValueError: '/<>' is not in the subpath of '/<>')

2025-01-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jan 2025 20:47:06 + with message-id and subject line Bug#1090285: fixed in python-pyfakefs 5.7.3-1 has caused the Debian Bug report #1090285, regarding python-pyfakefs: FTBFS: INTERNALERROR> ValueError: '/<>' is not in the subpath of '/<>' to be marked as done. Thi

Bug#1092434: marked as done (xscavenger: FTBFS: make: *** [debian/rules:99: stamp-binary] Error 1)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jan 2025 20:48:55 + with message-id and subject line Bug#1092434: fixed in xscavenger 1.4.5-9 has caused the Debian Bug report #1092434, regarding xscavenger: FTBFS: make: *** [debian/rules:99: stamp-binary] Error 1 to be marked as done. This means that you claim th

Bug#1091569: marked as done (receptor: FTBFS on i386: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.13 3.12" --name=receptorctl "--before-test=cp -r {dir}/tests/mesh-defin

2025-01-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jan 2025 20:48:24 + with message-id and subject line Bug#1091569: fixed in receptor 1.5.2-1 has caused the Debian Bug report #1091569, regarding receptor: FTBFS on i386: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.13 3.12" --name=recep

Bug#1092749: Autopkgtests fail with Python 3.13: ipdSummary output changed

2025-01-12 Thread Vladimir Petko
Package: kineticstools Version: 0.6.1+git20220223.1326a4d+dfsg-3 Followup-For: Bug #1092749 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu plucky ubuntu-patch Control: tags -1 patch Dear Maintainer, Would it be possible to consider removing the cram autopkgtest? cram only runs versi

Bug#1075485: marked as done (sa-exim: ftbfs with GCC-14)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jan 2025 20:48:33 + with message-id and subject line Bug#1075485: fixed in sa-exim 4.2.1-21 has caused the Debian Bug report #1075485, regarding sa-exim: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1092888: sioyek: FTBFS

2025-01-12 Thread Bastian Germann
Source: sioyek Version: 2.0.0+dfsg-4 Severity: serious The package does not build with current mupdf.

Processed: Re: Autopkgtests fail with Python 3.13: ipdSummary output changed

2025-01-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1092749 [src:kineticstools] Autopkgtests fail with Python 3.13: ipdSummary output changed Added tag(s) patch. -- 1092749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092749 Debian Bug Tracking System Contact ow...@bugs.debian.org with pro

Bug#1089303: marked as done (chiark-utils: Supporting rootless builds by default)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jan 2025 20:41:39 + with message-id and subject line Bug#1089303: fixed in chiark-utils 8.0.0 has caused the Debian Bug report #1089303, regarding chiark-utils: Supporting rootless builds by default to be marked as done. This means that you claim that the problem ha

Processed: tagging 1092881

2025-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1092881 + pending Bug #1092881 [libtevent0t64] libtevent0t64: breaks itself Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1092881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=109

Bug#1092881: [Pkg-samba-maint] Bug#1092881: libtevent0t64: breaks itself

2025-01-12 Thread Raphaël Halimi
On Sun, 12 Jan 2025 21:29:27 +0300 Michael Tokarev wrote: What do you mean by "vise-versa"? I mean that AFAIU it seems that the amd64 package breaks the i386 one, and the i386 package breaks the amd64 one. There's no libtevent0 package anymore, so it can't break anything. libtevent0t64 p

Bug#1092881: libtevent0t64: breaks itself

2025-01-12 Thread Michael Tokarev
Control: tag -1 = confirmed 12.01.2025 22:43, Michael Kümmling wrote: dpkg: dependency problems prevent configuration of libtevent0t64:amd64:  libtevent0t64:i386 (2:0.16.1+samba4.21.3+dfsg-5) breaks libtevent0 (<< 2:4.21.3+dfsg-5) and is unpacked but not configured. Aha. It is the version

Processed: Re: Bug#1092881: libtevent0t64: breaks itself

2025-01-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 = confirmed Bug #1092881 [libtevent0t64] libtevent0t64: breaks itself Added tag(s) confirmed; removed tag(s) moreinfo and unreproducible. -- 1092881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092881 Debian Bug Tracking System Contact ow...@bugs.debi

Bug#1089303: chiark-utils: Supporting rootless builds by default

2025-01-12 Thread Niels Thykier
Ian Jackson: tl;dr: TYVM. This is all great. I'll be uploading *with* your dh changes, fixed, shortly. Niels Thykier writes ("Bug#1089303: chiark-utils: Supporting rootless builds by default"): The final patch `dh-prototype.diff` is what I envisioned would be the final bit required to m

Bug#1092881: [Pkg-samba-maint] Bug#1092881: libtevent0t64: breaks itself

2025-01-12 Thread Michael Kümmling
On Sun, 12 Jan 2025 21:29:27 +0300 Michael Tokarev wrote: There's no libtevent0 package anymore, so it can't break anything. > I had to downgrade to previous version (4.21.3+dfsg-4 and 2.10.0+samba4.21.3+dfsg-4) of all those packages to repair the system. What's the error message you're getti

Bug#1030130: libgnome-bluetooth13: superseded version of gnome-bluetooth3, should be removed eventually

2025-01-12 Thread Simon McVittie
On Sun, 12 Jan 2025 at 20:36:25 +0100, Bastian Germann wrote: > On Fri, 6 Dec 2024 10:38:16 + Simon McVittie wrote: > > We should remove this unmaintained upstream code from Debian, but at the > > moment we cannot, because budgie-control-center (#1059485) and budgie-core > > in unstable (#10594

Processed: Re: libgnome-bluetooth13: superseded version of gnome-bluetooth3, should be removed eventually

2025-01-12 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1030130 [src:gnome-bluetooth] libgnome-bluetooth13: superseded version of gnome-bluetooth3, should be removed eventually Severity set to 'serious' from 'important' -- 1030130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030130 Debia

Bug#1091945: org-roam: FTBFS: error: (void-function emacsql-sqlite)

2025-01-12 Thread Sean Whitton
Hello, On Fri 10 Jan 2025 at 02:34pm -08, Xiyue Deng wrote: > Thanks for bringing up this. I checked the uscan manual and it said > that the default for "gitmode" is "shallow", so AIUI it shouldn't be > that costly, right? That didn't exist before, so yeah, not so bad. Still more than HTTP. -

Bug#1090285: marked as pending in python-pyfakefs

2025-01-12 Thread Colin Watson
Control: tag -1 pending Hello, Bug #1090285 in python-pyfakefs reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-pyfakefs/-/commit/1f9

Processed: Bug#1090285 marked as pending in python-pyfakefs

2025-01-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1090285 [src:python-pyfakefs] python-pyfakefs: FTBFS: INTERNALERROR> ValueError: '/<>' is not in the subpath of '/<>' Added tag(s) pending. -- 1090285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1090285 Debian Bug Tracking System Contact

Bug#1092745: opensysusers: DEP17 diversions may delete systemd's systemd-sysuser

2025-01-12 Thread thomas
On Jan 11, 2025 10:09, Helmut Grohne wrote: > > Source: opensysusers > Version: 0.7.3-4 > Severity: serious > Justification: loss of systemd files > Tags: patch > User: helm...@debian.org > Usertags: dep17 > > Hi, > > I'm sorry to tell you that I got the DEP17 mitigation for

Bug#1091069: marked as done (r-bioc-qtlizer: FTBFS: build-dependency not installable: r-api-bioc-3.20)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jan 2025 20:26:34 +0100 with message-id <77bac863-b27b-489a-849e-72b7acc22...@debian.org> and subject line Re: r-bioc-qtlizer: FTBFS: build-dependency not installable: r-api-bioc-3.20 has caused the Debian Bug report #1091069, regarding r-bioc-qtlizer: FTBFS: build-depen

Bug#1075069: the ubuntu version also works fine with python 3.13

2025-01-12 Thread Eric Valette
I tested the build with python 3.13 without problems. -- Eric Valette

Bug#1089303: chiark-utils: Supporting rootless builds by default

2025-01-12 Thread Ian Jackson
tl;dr: TYVM. This is all great. I'll be uploading *with* your dh changes, fixed, shortly. Niels Thykier writes ("Bug#1089303: chiark-utils: Supporting rootless builds by default"): > The final patch `dh-prototype.diff` is what I envisioned would be the > final bit required to move to `dh`.

Bug#1091873: marked as done (octave-statistics: flaky autopkgtest: seems to hang and times out)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jan 2025 18:52:03 + with message-id and subject line Bug#1091873: fixed in octave-statistics 1.7.0-3 has caused the Debian Bug report #1091873, regarding octave-statistics: flaky autopkgtest: seems to hang and times out to be marked as done. This means that you clai

Processed: Re: Bug#1089303: chiark-utils: Supporting rootless builds by default

2025-01-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #1089303 [src:chiark-utils] chiark-utils: Supporting rootless builds by default Added tag(s) pending. -- 1089303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1089303: chiark-utils: Supporting rootless builds by default

2025-01-12 Thread Ian Jackson
Control: tags -1 pending Hi. Thanks for all this. Superb work. I have reviewed the first three patches and their output and I have adopted them into my own mainline. I'll be uploading later today. First, though, I want to see if I can adopt the dh patch, or something like it. Regards, Ian.

Bug#1088523: Acknowledgement (oxigraph: FTBFS with librocksdb9.7-dev)

2025-01-12 Thread Jonas Smedegaard
Quoting Jonas Smedegaard (2025-01-12 19:26:12) > Quoting Otto Kekäläinen (2025-01-12 19:08:05) > > I can try importing latest upstream and run reverse builds for all > > dependants. > > Thanks, that sounds quite helpful. I have now adjusted to build routines for oxigraph to tolerate failures rela

Processed: tagging 1092881

2025-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1092881 + moreinfo unreproducible Bug #1092881 [libtevent0t64] libtevent0t64: breaks itself Added tag(s) unreproducible and moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1092881: https://bugs.debi

Bug#1092881: [Pkg-samba-maint] Bug#1092881: libtevent0t64: breaks itself

2025-01-12 Thread Michael Tokarev
Control: tag + moreinfo unreproducible 12.01.2025 21:07, Raphaël Halimi wrote: Package: libtevent0t64 Version: 2:0.16.1+samba4.21.3+dfsg-5 Severity: critical Dear fellow maintainers, libtevent0t64:i386 2:0.16.1+samba4.21.3+dfsg-5 breaks libtevent0:amd64 (<< 2:4.21.3+dfsg-5), and vice-versa, re

Bug#1092806: linux-image-6.1.0-29-arm64: Oops: Unable to handle kernel paging request at virtual address ffff0000e1fb238c

2025-01-12 Thread Salvatore Bonaccorso
Hi, On Sat, Jan 11, 2025 at 09:46:36PM +0100, Peter Gerber wrote: > Package: src:linux > Version: 6.1.123-1 > Severity: critical > Justification: breaks the whole system > X-Debbugs-Cc: pe...@arbitrary.ch > > Dear Maintainer, > > Ever since updating to linux-image-6.1.0-29-arm64 I've been seeing

Bug#1091873: marked as pending in octave-statistics

2025-01-12 Thread Sébastien Villemot
Control: tag -1 pending Hello, Bug #1091873 in octave-statistics 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-octave-team/octave-statistics/-/commit/380d

Processed: Bug#1091873 marked as pending in octave-statistics

2025-01-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1091873 [src:octave-statistics] octave-statistics: flaky autopkgtest: seems to hang and times out Added tag(s) pending. -- 1091873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091873 Debian Bug Tracking System Contact ow...@bugs.debian.o

Bug#1088523: Acknowledgement (oxigraph: FTBFS with librocksdb9.7-dev)

2025-01-12 Thread Jonas Smedegaard
Quoting Otto Kekäläinen (2025-01-12 19:08:05) > I can try importing latest upstream and run reverse builds for all > dependants. Thanks, that sounds quite helpful. > One challenge I have at the moment is that upstream is not responding on > GitHub PRs and ignoring fixes and also not publishing an

Processed: severity of 1092806 is serious, forcibly merging 1092772 1092806

2025-01-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1092806 serious Bug #1092806 [src:linux] linux-image-6.1.0-29-arm64: Oops: Unable to handle kernel paging request at virtual address e1fb238c Severity set to 'serious' from 'critical' > forcemerge 1092772 1092806 Bug #1092772 [sr

Bug#1078879: marked as done (python-webob: CVE-2024-42353)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jan 2025 18:05:49 + with message-id and subject line Bug#1078879: fixed in python-webob 1:1.8.9-1 has caused the Debian Bug report #1078879, regarding python-webob: CVE-2024-42353 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1092881: libtevent0t64: breaks itself

2025-01-12 Thread Raphaël Halimi
Package: libtevent0t64 Version: 2:0.16.1+samba4.21.3+dfsg-5 Severity: critical Dear fellow maintainers, libtevent0t64:i386 2:0.16.1+samba4.21.3+dfsg-5 breaks libtevent0:amd64 (<< 2:4.21.3+dfsg-5), and vice-versa, resulting in errors during upgrade for them and dependent packages (samba-libs, l

Bug#1088523: Acknowledgement (oxigraph: FTBFS with librocksdb9.7-dev)

2025-01-12 Thread Otto Kekäläinen
I can try importing latest upstream and run reverse builds for all dependants. One challenge I have at the moment is that upstream is not responding on GitHub PRs and ignoring fixes and also not publishing any policy of which RocksDB version is likely good for long-term maintenance. Thus there is

Bug#1092797: marked as done (Autopkgtests fail with Python 3.13)

2025-01-12 Thread Debian Bug Tracking System
Your message dated Sun, 12 Jan 2025 17:52:24 + with message-id and subject line Bug#1092797: fixed in xonsh 0.19.0+dfsg-1 has caused the Debian Bug report #1092797, regarding Autopkgtests fail with Python 3.13 to be marked as done. This means that you claim that the problem has been dealt wit

Processed: Bug#1078879 marked as pending in python-webob

2025-01-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1078879 [src:python-webob] python-webob: CVE-2024-42353 Added tag(s) pending. -- 1078879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078879 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1078879: marked as pending in python-webob

2025-01-12 Thread Colin Watson
Control: tag -1 pending Hello, Bug #1078879 in python-webob reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-webob/-/commit/d8b465218

Processed: phploc: not compatible with PHPUnit 11

2025-01-12 Thread Debian Bug Tracking System
Processing control commands: > block 1084894 by -1 Bug #1084894 [release.debian.org] transition: phpunit 1084894 was blocked by: 1039752 1039755 1039781 1039783 1039788 1039792 1039795 1039841 1039856 1070511 1070514 1070517 1070553 1070557 1070567 1070580 1070590 1070600 1070608 1070621 1070639

  1   2   >