Bug#1106313: streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed

2025-05-26 Thread Santiago Vila
El 27/5/25 a las 7:31, Lucas Nussbaum escribió: What is a bit painful here is that we would need to check binaries on all architectures. Maybe it's easier to just bin-NMU them all... Not in my name... I've done apt-get source on all the above 18 packages and I found this: - Only two packages

Bug#1104152: Ping

2025-05-26 Thread Alexandre Detiste
Ping

Bug#1106313: streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed

2025-05-26 Thread Lucas Nussbaum
On 27/05/25 at 00:59 +0200, Santiago Vila wrote: > > Could these be selected with UDD for all uploads between two dates > > (then and now). > > Ok, here is a list of packages meeting the following conditions: > > - build-depends on cdbs > - last uploaded between 2025-04-08 and 2025-05-27 > > 202

Processed: tagging 1104758

2025-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1104758 + help upstream confirmed Bug #1104758 [src:freetds] freetds: FTBFS on armel, armhf, mips64el: FAIL: convert_bounds Added tag(s) confirmed, help, and upstream. > thanks Stopping processing here. Please contact me if you need assista

Processed: bug 1104758 is forwarded to https://github.com/FreeTDS/freetds/issues/656

2025-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1104758 https://github.com/FreeTDS/freetds/issues/656 Bug #1104758 [src:freetds] freetds: FTBFS on armel, armhf, mips64el: FAIL: convert_bounds Set Bug forwarded-to-address to 'https://github.com/FreeTDS/freetds/issues/656'. > thanks St

Bug#1105883: Bug#1105885: Helping to fix CVE-2025-4817{4,5} on bookworm

2025-05-26 Thread Carlos Henrique Lima Melara
Hi Multimedia Maintainers and Boyuan, On Mon, May 26, 2025 at 10:17:53PM -0300, Carlos Henrique Lima Melara wrote: > Hi, > > On Sun, May 25, 2025 at 08:42:30PM +0200, Salvatore Bonaccorso wrote: > > Attached are the patches we aim to use for bookworm. > > > > The first one, is very similar to yo

Bug#1105883: Bug#1105885: Helping to fix CVE-2025-4817{4,5} on bookworm

2025-05-26 Thread Carlos Henrique Lima Melara
Hi, On Sun, May 25, 2025 at 08:42:30PM +0200, Salvatore Bonaccorso wrote: > On Sun, May 25, 2025 at 05:03:59PM +0200, Salvatore Bonaccorso wrote: > > On Sun, May 25, 2025 at 07:24:00AM +0200, Salvatore Bonaccorso wrote: > > > Charles, thanks for the offer. I'm indeed on it and I'm in contact > > >

Bug#1106313: streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed

2025-05-26 Thread Sergio Durigan Junior
On Monday, May 26 2025, Santiago Vila wrote: > El 26/5/25 a las 11:08, Lucas Nussbaum escribió: >> ijs was fixed by Sergio (Cced) with the following patch: >> diff -Nru ijs-0.35/debian/rules ijs-0.35/debian/rules >> --- ijs-0.35/debian/rules2025-02-19 17:59:38.0 +0100 >> +++ ijs-0.35/d

Bug#1106313: streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed

2025-05-26 Thread Santiago Vila
Could these be selected with UDD for all uploads between two dates (then and now). Ok, here is a list of packages meeting the following conditions: - build-depends on cdbs - last uploaded between 2025-04-08 and 2025-05-27 2025-04-09 libiptcdata 1.0.5-2.4 2025-04-09 vim-scripts 20210124.4 2025-

Bug#1106599: exult and exult-studio have an undeclared file conflict on /usr/share/games/icons/hicolor/scalable/apps/info.exult.exult.studio.svg

2025-05-26 Thread Helmut Grohne
Package: exult-studio,exult Version: 1.12.0-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict exult and exult-studio have an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/share/games/icons/hicolor/scalable/apps/info.exult.exult.stu

Bug#1106313: streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed

2025-05-26 Thread Alexandre Detiste
Thank you Santiago for the fast handling. Le lun. 26 mai 2025 à 13:17, Santiago Vila a écrit : > ifeq (,$(shell grep -xi 'Package: autotools-dev' debian/control)) Ho I misread the boolean logic here. I thought this whole blurb only applied for autotools-dev. I did a lot of tests but never with a

Bug#1106237: marked as done (fragments: unusable due to serde error)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 21:04:43 + with message-id and subject line Bug#1106237: fixed in rust-transmission-client 0.1.5-2 has caused the Debian Bug report #1106237, regarding fragments: unusable due to serde error to be marked as done. This means that you claim that the problem h

Processed: bts

2025-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1098586 Bug #1098586 [python3-tqdm] orange-canvas-core: FTBFS: Segmentation fault Marked Bug as done > notfound 1098586 4.67.1-3 Bug #1098586 {Done: Daniel Baumann } [python3-tqdm] orange-canvas-core: FTBFS: Segmentation fault No longer mar

Bug#1084293: Bug#1105976: mariadb: CVE-2025-30722 CVE-2025-30693

2025-05-26 Thread Salvatore Bonaccorso
Hi, On Sun, May 25, 2025 at 08:24:53PM -0700, Otto Kekäläinen wrote: > > > MariaDB 11.10.13 is now out and ready for upload in MR!119. > > > > > > Should we make this a security upload or put into stable-updates? > > > Does the security team have a preference? > > > > > > I am fine either way. > >

Processed: Re: Bug#1098586: orange-canvas-core: FTBFS: Segmentation fault

2025-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unmerge 1101839 Bug #1101839 [python3-tqdm] python3-tqdm: segmentation fault in destructor method Bug #1098586 [python3-tqdm] orange-canvas-core: FTBFS: Segmentation fault Disconnected #1101839 from all other report(s). > close 1101839 Bug #11018

Bug#1098586: orange-canvas-core: FTBFS: Segmentation fault

2025-05-26 Thread Daniel Baumann
unmerge 1101839 close 1101839 thanks Hi Santiago, On 5/26/25 19:09, Santiago Vila wrote: I can't reproduce this anymore while building the orange-canvas-core package. thanks for the update. Not changing the severity, because apparently other people can reproduce it, but I will not be able t

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

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 18:19:20 + with message-id and subject line Bug#1106426: fixed in lmfit-py 1.3.3-3 has caused the Debian Bug report #1106426, regarding lmfit-py: FTBFS: FAILURES: test_confidence_warnings to be marked as done. This means that you claim that the problem has

Processed: Re: src:jool: fails to migrate to testing for too long

2025-05-26 Thread Debian Bug Tracking System
Processing control commands: > tags -1 trixie-ignore Bug #1106183 {Done: Paul Gevers } [src:jool] src:jool: fails to migrate to testing for too long Added tag(s) trixie-ignore. -- 1106183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106183 Debian Bug Tracking System Contact ow...@bugs.de

Bug#1106183: src:jool: fails to migrate to testing for too long

2025-05-26 Thread Paul Gevers
Control: tags -1 trixie-ignore Hi, On 26-05-2025 01:01, Santiago Vila wrote: There was a bug in debian/rules which made the package not to build ok in the arch:all autobuilders (see Bug #1103714). This is now fixed. That's the risk of uploading during the freeze. I've just told Alberto (the

Processed: lmfit-py: FTBFS: FAILURES: test_confidence_warnings,version graph

2025-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1106426 https://github.com/lmfit/lmfit-py/issues/999 Bug #1106426 [src:lmfit-py] lmfit-py: FTBFS: FAILURES: test_confidence_warnings Set Bug forwarded-to-address to 'https://github.com/lmfit/lmfit-py/issues/999'. > owner 1106426 ! Bug #1

Bug#1106426: lmfit-py: FTBFS: FAILURES: test_confidence_warnings,version graph

2025-05-26 Thread Santiago Vila
forwarded 1106426 https://github.com/lmfit/lmfit-py/issues/999 owner 1106426 ! thanks This is apparently fixed upstream. I'm going to see if the fix works. Thanks.

Bug#1106311: git: FTBFS: Files COPYING and /usr/share/common-licenses/GPL-2 differ

2025-05-26 Thread Santiago Vila
tags 1106311 patch thanks I propose the attached patch so that this does not happen again. Thanks.--- a/debian/git.links +++ b/debian/git.links @@ -1,6 +1,5 @@ usr/share/bash-completion/completions/git usr/share/bash-completion/completions/gitk usr/share/gitweb/gitweb.cgi usr/share/gitweb/ind

Processed: git: FTBFS: Files COPYING and /usr/share/common-licenses/GPL-2 differ

2025-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1106311 patch Bug #1106311 [src:git] git: FTBFS: Files COPYING and /usr/share/common-licenses/GPL-2 differ Bug #1106424 [src:git] git: FTBFS: Files COPYING and /usr/share/common-licenses/GPL-2 differ Added tag(s) patch. Added tag(s) patch.

Processed: [bts-link] source package snapd

2025-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package snapd > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting u

Processed: [bts-link] source package src:cctbx

2025-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:cctbx > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setti

Bug#1106421: marked as pending in beautifulsoup4

2025-05-26 Thread Stefano Rivera
Control: tag -1 pending Hello, Bug #1106421 in beautifulsoup4 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/beautifulsoup4/-/commit/f00db

Processed: Bug#1106421 marked as pending in beautifulsoup4

2025-05-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1106421 [src:beautifulsoup4] beautifulsoup4: FTBFS: E Failed: DID NOT RAISE Added tag(s) pending. -- 1106421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1104839: octave-iso2mesh: FTBFS: /usr/include/superlu/slu_ddefs.h:264:13: error: conflicting types for 'dcopy_'

2025-05-26 Thread Santiago Vila
Hello. I don't know how to fix this, but I know that Markus Blatt fixed a similar problem in dune-istl in this way: https://salsa.debian.org/science-team/dune-istl/-/commit/03f81f26ab7e3f91b209ca5c22c0ffcca36ade7b Thanks.

Bug#1098586: orange-canvas-core: FTBFS: Segmentation fault

2025-05-26 Thread Santiago Vila
Hello. I can't reproduce this anymore while building the orange-canvas-core package. Not changing the severity, because apparently other people can reproduce it, but I will not be able to offer any VM to reproduce it as I promised, sorry. Thanks.

Processed: git: FTBFS: Files COPYING and /usr/share/common-licenses/GPL-2 differ

2025-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1106311 git: FTBFS: Files COPYING and > /usr/share/common-licenses/GPL-2 differ Bug #1106311 [src:git] git: FTBFS in testing/i386: error: invalid value for 'extensions.refstorage': 'garbage' Changed Bug title to 'git: FTBFS: Files COPYIN

Processed: octave-iso2mesh: FTBFS: /usr/include/superlu/slu_ddefs.h:264:13: error: conflicting types for 'dcopy_'

2025-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # sorry for the broken utf8 > retitle 1104839 octave-iso2mesh: FTBFS: > /usr/include/superlu/slu_ddefs.h:264:13: error: conflicting types for 'dcopy_' Bug #1104839 [src:octave-iso2mesh] octave-iso2mesh: FTBFS: /usr/include/superlu/slu_ddefs.h:26

Bug#1106311: git: FTBFS: Files COPYING and /usr/share/common-licenses/GPL-2 differ

2025-05-26 Thread Santiago Vila
retitle 1106311 git: FTBFS: Files COPYING and /usr/share/common-licenses/GPL-2 differ forcemerge 1106311 1106424 thanks Hello Lucas. The old title said error: invalid value for 'extensions.refstorage': 'garbage' but this was actually a test which expects such specific error: -

Bug#1101305: marked as done (libfuse3-4: regression in 3.17.1-1 for gvfsd-fuse: "both 'want' and 'want_ext' are set")

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 15:19:20 + with message-id and subject line Bug#1101305: fixed in fuse3 3.17.2-2 has caused the Debian Bug report #1101305, regarding libfuse3-4: regression in 3.17.1-1 for gvfsd-fuse: "both 'want' and 'want_ext' are set" to be marked as done. This means t

Bug#1105099: marked as done (fuse3: wrong Build-Depends-Package field in libfuse3-4.symbols)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 15:19:21 + with message-id and subject line Bug#1105099: fixed in fuse3 3.17.2-2 has caused the Debian Bug report #1105099, regarding fuse3: wrong Build-Depends-Package field in libfuse3-4.symbols to be marked as done. This means that you claim that the pro

Bug#1105917: marked as done (freerdp3: CVE-2025-4478)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 13:04:28 + with message-id and subject line Bug#1105917: fixed in freerdp3 3.15.0+dfsg-2.1 has caused the Debian Bug report #1105917, regarding freerdp3: CVE-2025-4478 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1106440: marked as done (python-mechanize: FTBFS: FAIL: test_missing_name (test.test_cookies.CookieTests.test_missing_name))

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 12:34:01 + with message-id and subject line Bug#1106440: fixed in python-mechanize 1:0.4.10+ds-4 has caused the Debian Bug report #1106440, regarding python-mechanize: FTBFS: FAIL: test_missing_name (test.test_cookies.CookieTests.test_missing_name) to be ma

Bug#1105917: debdiff

2025-05-26 Thread Daniel Baumann
Hi, I've cherry-picked the upstream commit as a patch and did a non-maintainer upload of it, the debdiff is attached. Regards, Danieldiff -Nru freerdp3-3.15.0+dfsg/debian/changelog freerdp3-3.15.0+dfsg/debian/changelog --- freerdp3-3.15.0+dfsg/debian/changelog 2025-04-24 09:18:41.0 +00

Bug#1106313: streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed

2025-05-26 Thread Michael Ablassmeier
hi there, On Mon, May 26, 2025 at 10:20:38AM +0200, Santiago Vila wrote: > El 26/5/25 a las 9:47, Michael Ablassmeier escribió: > > hm, this seems to be depending on the build system used, it actually built > > here: > > > > > > https://buildd.debian.org/status/logs.php?pkg=streamripper&ver=1.

Processed: Bug#1106440 marked as pending in python-mechanize

2025-05-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1106440 [src:python-mechanize] python-mechanize: FTBFS: FAIL: test_missing_name (test.test_cookies.CookieTests.test_missing_name) Added tag(s) pending. -- 1106440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106440 Debian Bug Tracking Sy

Bug#1106440: marked as pending in python-mechanize

2025-05-26 Thread Colin Watson
Control: tag -1 pending Hello, Bug #1106440 in python-mechanize 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-mechanize/-/commit/b

Bug#1106313: marked as done (streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106315: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106315, regarding streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done.

Bug#1106318: marked as done (ijs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106315: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106315, regarding ijs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. This me

Bug#1056708: node-wikibase-cli: Using internet during tests

2025-05-26 Thread Andrius Merkys
Hi Santiago, Thanks a lot for attempting rescuing node-wikibase-cli. On 2025-05-23 20:14, Santiago Vila wrote: I naively tried to disable the remaining five tests still using the network by applying the attached patch (in quilt format), but then I get 50 failures instead of five. 😱 I'm attachi

Bug#1106314: marked as done (hasciicam: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106319: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106319, regarding hasciicam: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. T

Bug#1106313: marked as done (streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106318: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106318, regarding streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done.

Bug#1106317: marked as done (pidgin-extprefs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106318: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106318, regarding pidgin-extprefs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as do

Bug#1106314: marked as done (hasciicam: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106315: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106315, regarding hasciicam: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. T

Bug#1106319: marked as done (madplay: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106314: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106314, regarding madplay: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. Thi

Bug#1106317: marked as done (pidgin-extprefs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106319: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106319, regarding pidgin-extprefs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as do

Bug#1106318: marked as done (ijs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106319: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106319, regarding ijs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. This me

Bug#1106313: marked as done (streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106319: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106319, regarding streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done.

Bug#1106315: marked as done (lwipv6: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106319: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106319, regarding lwipv6: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. This

Bug#1106319: marked as done (madplay: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106318: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106318, regarding madplay: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. Thi

Bug#1106319: marked as done (madplay: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106319: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106319, regarding madplay: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. Thi

Bug#1106315: marked as done (lwipv6: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106318: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106318, regarding lwipv6: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. This

Bug#1106314: marked as done (hasciicam: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106318: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106318, regarding hasciicam: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. T

Bug#1106318: marked as done (ijs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106318: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106318, regarding ijs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. This me

Bug#1106318: marked as done (ijs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106317: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106317, regarding ijs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. This me

Bug#1106319: marked as done (madplay: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106317: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106317, regarding madplay: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. Thi

Bug#1106315: marked as done (lwipv6: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106317: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106317, regarding lwipv6: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. This

Bug#1106313: marked as done (streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106317: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106317, regarding streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done.

Bug#1106314: marked as done (hasciicam: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106317: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106317, regarding hasciicam: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. T

Bug#1106317: marked as done (pidgin-extprefs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106317: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106317, regarding pidgin-extprefs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as do

Bug#1106319: marked as done (madplay: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106315: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106315, regarding madplay: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. Thi

Bug#1106317: marked as done (pidgin-extprefs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106315: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106315, regarding pidgin-extprefs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as do

Bug#1106318: marked as done (ijs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106314: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106314, regarding ijs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. This me

Bug#1106317: marked as done (pidgin-extprefs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106314: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106314, regarding pidgin-extprefs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as do

Bug#1106314: marked as done (hasciicam: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106314: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106314, regarding hasciicam: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. T

Bug#1106315: marked as done (lwipv6: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106315: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106315, regarding lwipv6: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. This

Bug#1106315: marked as done (lwipv6: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106314: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106314, regarding lwipv6: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. This

Bug#1106313: marked as done (streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106314: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106314, regarding streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done.

Bug#1106319: marked as done (madplay: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106313: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106313, regarding madplay: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. Thi

Bug#1106317: marked as done (pidgin-extprefs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106313: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106313, regarding pidgin-extprefs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as do

Bug#1106318: marked as done (ijs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106313: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106313, regarding ijs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. This me

Bug#1106315: marked as done (lwipv6: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106313: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106313, regarding lwipv6: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. This

Bug#1106313: marked as done (streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106313: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106313, regarding streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done.

Bug#1106314: marked as done (hasciicam: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:49:18 + with message-id and subject line Bug#1106313: fixed in cdbs 0.4.173 has caused the Debian Bug report #1106313, regarding hasciicam: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be marked as done. T

Processed: tidy up

2025-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1106313 cdbs Bug #1106313 [src:streamripper] streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed Bug reassigned from package 'src:streamripper' to 'cdbs'. No longer marked as found in v

Bug#1106317: marked as done (pidgin-extprefs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 11:18:54 + with message-id and subject line Bug#1106317: fixed in pidgin-extprefs 0.7-5 has caused the Debian Bug report #1106317, regarding pidgin-extprefs: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed to be mar

Bug#1106314: Bug#1106313: streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed

2025-05-26 Thread Santiago Vila
El 26/5/25 a las 12:52, Lucas Nussbaum escribió: Looking at cdbs' changes history between those two releases, this sounds relevant: https://salsa.debian.org/debian/cdbs/-/commit/5efba11b142b73ffbfa61fff09cdacc3d6db52b9 but I don't understand the change itself. I "sort of" understand the change

Bug#1106313: streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed

2025-05-26 Thread Lucas Nussbaum
On 26/05/25 at 12:07 +0200, Santiago Vila wrote: > El 26/5/25 a las 11:08, Lucas Nussbaum escribió: > > ijs was fixed by Sergio (Cced) with the following patch: > > > > diff -Nru ijs-0.35/debian/rules ijs-0.35/debian/rules > > --- ijs-0.35/debian/rules 2025-02-19 17:59:38.0 +0100 > > +++

Bug#1106313: streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed

2025-05-26 Thread Michael Ablassmeier
hi again, On Mon, May 26, 2025 at 12:39:41PM +0200, Michael Ablassmeier wrote: > hi, > > On Mon, May 26, 2025 at 12:07:08PM +0200, Santiago Vila wrote: > > El 26/5/25 a las 11:08, Lucas Nussbaum escribió: > > > ijs was fixed by Sergio (Cced) with the following patch: > > > > > > diff -Nru ijs-0.

Bug#1106313: streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed

2025-05-26 Thread Michael Ablassmeier
hi, On Mon, May 26, 2025 at 12:07:08PM +0200, Santiago Vila wrote: > El 26/5/25 a las 11:08, Lucas Nussbaum escribió: > > ijs was fixed by Sergio (Cced) with the following patch: > > > > diff -Nru ijs-0.35/debian/rules ijs-0.35/debian/rules > > --- ijs-0.35/debian/rules 2025-02-19 17:59:38.

Bug#1106314: Bug#1106313: streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed

2025-05-26 Thread Santiago Vila
El 26/5/25 a las 11:08, Lucas Nussbaum escribió: ijs was fixed by Sergio (Cced) with the following patch: diff -Nru ijs-0.35/debian/rules ijs-0.35/debian/rules --- ijs-0.35/debian/rules 2025-02-19 17:59:38.0 +0100 +++ ijs-0.35/debian/rules 2025-05-25 00:47:55.0 +0200

Bug#1106313: streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed

2025-05-26 Thread Lucas Nussbaum
On 26/05/25 at 10:46 +0200, Michael Ablassmeier wrote: > hi there, > > On Mon, May 26, 2025 at 10:20:38AM +0200, Santiago Vila wrote: > > El 26/5/25 a las 9:47, Michael Ablassmeier escribió: > > > hm, this seems to be depending on the build system used, it actually built > > > here: > > > > > >

Bug#1106445: marked as done (swift: FTBFS: FAIL: test.unit.common.utils.test_logs.TestUtilsLogs.test_LoggerFileObject_recursion)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 07:49:16 + with message-id and subject line Bug#1106445: fixed in swift 2.35.0-3 has caused the Debian Bug report #1106445, regarding swift: FTBFS: FAIL: test.unit.common.utils.test_logs.TestUtilsLogs.test_LoggerFileObject_recursion to be marked as done. T

Bug#1106070: Raising the severity?

2025-05-26 Thread Chris Hofstaedtler
On Sun, May 25, 2025 at 08:32:20PM +0200, Salvatore Bonaccorso wrote: > Control: severity -1 serious > > Hi Roland, hi Cyril, > > On Sun, May 25, 2025 at 05:44:42PM +0200, Roland Clobus wrote: > > Hello, > > > > On 25/05/2025 17:00, Cyril Brulebois wrote: > > > To be honest, I almost asked what

Bug#1106313: streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed

2025-05-26 Thread Santiago Vila
El 26/5/25 a las 9:47, Michael Ablassmeier escribió: hm, this seems to be depending on the build system used, it actually built here: https://buildd.debian.org/status/logs.php?pkg=streamripper&ver=1.64.6-2&arch=arm64 getbuildlog streamripper 1.64.6-2 arm64 > checking whether mbrtowc and

Processed: closing 1101611

2025-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1101611 1.32.0-1 Bug #1101611 [src:php-symfony-polyfill] php-symfony-polyfill: FTBFS: make[1]: *** [debian/rules:52: override_dh_auto_test] Error 1 Marked as fixed in versions php-symfony-polyfill/1.32.0-1. Bug #1101611 [src:php-symfony-pol

Processed: reassign 1106525 to src:libhyprcursor

2025-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1106525 src:libhyprcursor Bug #1106525 [hyprcursor] hyprcursor: Prevent hyprcursor from being promoted to stable Warning: Unknown package 'hyprcursor' Bug reassigned from package 'hyprcursor' to 'src:libhyprcursor'. No longer marked as f

Bug#1106446: xeus-gp: FTBFS: Could not find a configuration file for package "nlohmann_json" that exactly matches requested version "3.11.3".

2025-05-26 Thread Santiago Vila
El 26/5/25 a las 9:19, Bill Allombert escribió: I would really like to see the buildlog for xeus itself, if you have it. Ok, yes, I have it. It was successful, I've just put it here as well: https://people.debian.org/~sanvila/build-logs/202505/ Thanks.

Bug#1106313: streamripper: FTBFS in testing/arm64: configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed

2025-05-26 Thread Michael Ablassmeier
hi, On Thu, May 22, 2025 at 08:57:44PM +0200, Lucas Nussbaum wrote: > Source: streamripper > Version: 1.64.6-2 > > During a rebuild of all packages in testing (trixie), your package failed > to build on arm64. > > > Relevant part (hopefully): > > checking for wchar_t... yes > > checking for iswc

Bug#1105809: closed by Debian FTP Masters (reply to Bastian Germann ) (Bug#1105809: fixed in magics++ 4.16.0+really4.15.5-1)

2025-05-26 Thread Chris Hofstaedtler
On Mon, May 26, 2025 at 07:59:10AM +0100, Julian Gilbey wrote: > Hi Bastian, > > Thanks for this! > > Strangely, this version doesn't build on several architectures that > 4.15.5-1 did, as there is now a build-dependency (perhaps recursive) > on architecture-is-64-bit. 4.13.0-2 is the last magi

Bug#1104576: marked as done (mon: preinst fails, calls adduser without Pre-Depend-ing on it)

2025-05-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 May 2025 07:33:57 + with message-id and subject line Bug#1104576: fixed in etbemon 1.4.1-2 has caused the Debian Bug report #1104576, regarding mon: preinst fails, calls adduser without Pre-Depend-ing on it to be marked as done. This means that you claim that the pr

Processed: Bug#1106445 marked as pending in swift

2025-05-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1106445 [src:swift] swift: FTBFS: FAIL: test.unit.common.utils.test_logs.TestUtilsLogs.test_LoggerFileObject_recursion Added tag(s) pending. -- 1106445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106445 Debian Bug Tracking System Contac

Processed: Lower rabbitmq upgrade severity

2025-05-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1100165 important Bug #1100165 [rabbitmq-server] rabbitmq-server: fails to upgrade from bookworm Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 1100165

Bug#1106446: xeus-gp: FTBFS: Could not find a configuration file for package "nlohmann_json" that exactly matches requested version "3.11.3".

2025-05-26 Thread Bill Allombert
On Sat, May 24, 2025 at 04:40:30PM +, Santiago Vila wrote: > Package: src:xeus-gp > Version: 0.1.0-1 > Severity: serious > Tags: ftbfs trixie sid > > Dear maintainer: > > During a rebuild of all packages in unstable, your package failed to build: > > -

Bug#1106445: marked as pending in swift

2025-05-26 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #1106445 in swift 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/openstack-team/services/swift/-/commit/bfe1f2a83563076e72de

Bug#1103040: Resolve test failure of finalcif in TestCheckCifInterface

2025-05-26 Thread Andrius Merkys
Hi Rong Fu, On 2025-04-14 10:12, Fu, Rong (CN) wrote: I'd like to submit a patch for the finalcif package that fixes a failing test “test_checkcif.TestCheckCifInterface”. Thanks a lot for investigating the failure and coming up with a patch for it! I have just applied it. This should be in ti

Bug#1105809: closed by Debian FTP Masters (reply to Bastian Germann ) (Bug#1105809: fixed in magics++ 4.16.0+really4.15.5-1)

2025-05-26 Thread Julian Gilbey
Hi Bastian, Thanks for this! Strangely, this version doesn't build on several architectures that 4.15.5-1 did, as there is now a build-dependency (perhaps recursive) on architecture-is-64-bit. Probably worth doing a debdiff between 4.15.5-1 and 4.16.0+really4.15.5-1 to see what the difference is

  1   2   >