Bug#1073481: pydantic-core: FTBFS: make[1]: *** [debian/rules:15: execute_before_dh_auto_build] Error 101

On Sun, Sep 01, 2024 at 08:09:33PM +0100, Colin Watson wrote: > [...] > I've uploaded new versions of: > > rust-datetime > rust-enum-dispatch > rust-iso8601 > rust-num-bigint > rust-python3-dll-a > rust-smallvec > rust-speedate > rust-version-check > > ... and also uploaded rust-j

Bug#1053068: marked as done (openhft-affinity: FTBFS with default Java 21)

Your message dated Tue, 03 Sep 2024 03:34:56 + with message-id and subject line Bug#1053068: fixed in openhft-affinity 3.23.3-1 has caused the Debian Bug report #1053068, regarding openhft-affinity: FTBFS with default Java 21 to be marked as done. This means that you claim that the problem ha

Bug#1077398: xcur2png: diff for NMU version 0.7.1-1.1

On Mon, 02 Sep 2024 18:57:44 -0400 Boyuan Yang wrote: > Dear maintainer, > > I've prepared an NMU for xcur2png (versioned as 0.7.1-1.1) and > uploaded it to DELAYED/5. Please feel free to tell me if I > should delay it longer. LGTM, feel free to upload it now and remove it from the delayed queue

Processed: metadata

Processing commands for cont...@bugs.debian.org: > tags 1079648 + ftbfs Bug #1079648 [src:lvm2] lvm2: Build fixes and improvements Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1079648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=107964

Bug#1073001: fixed upstream

On Mon, Sep 02, 2024 at 07:15:44PM +0200, Alexandre Detiste wrote: > Le lun. 2 sept. 2024 à 18:56, Colin Watson a écrit : > > On Thu, Jul 18, 2024 at 02:08:32PM +0200, Hans-Christoph Steiner wrote: > > > It is fixed upstream: > > > https://github.com/buildbot/buildbot/commit/291df50dc3f27adb47a001

Processed: Bug#1073001 marked as pending in buildbot

Processing control commands: > tag -1 pending Bug #1073001 [src:buildbot] buildbot FTBFS: python3-sqlalchemy (<< 1.5) no longer satisfiable Added tag(s) pending. -- 1073001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073001 Debian Bug Tracking System Contact ow...@bugs.debian.org with p

Bug#1073001: marked as pending in buildbot

Control: tag -1 pending Hello, Bug #1073001 in buildbot 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/buildbot/-/commit/85a3a35f865359c1f

Processed: version tracking

Processing commands for cont...@bugs.debian.org: > notfound 1053015 0.6.0-1.1 Bug #1053015 [src:cava] cava: FTBFS with OpenJDK 21 due to new compiler warnings No longer marked as found in versions cava/0.6.0-1.1. > found 1053015 0.6.0-1.1 Bug #1053015 [src:cava] cava: FTBFS with OpenJDK 21 due to

Processed: xcur2png: diff for NMU version 0.7.1-1.1

Processing control commands: > tags 1077398 + patch Bug #1077398 [src:xcur2png] xcur2png: FTBFS: xcur2png.c:674:10: error: type defaults to ‘int’ in declaration of ‘dry_run’ [-Wimplicit-int] Added tag(s) patch. > tags 1077398 + pending Bug #1077398 [src:xcur2png] xcur2png: FTBFS: xcur2png.c:674:1

Bug#1077398: xcur2png: diff for NMU version 0.7.1-1.1

Control: tags 1077398 + patch Control: tags 1077398 + pending Dear maintainer, I've prepared an NMU for xcur2png (versioned as 0.7.1-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru xcur2png-0.7.1/debian/changelog xcur2png-0.7.1/debi

Bug#1080323: marked as done (gnome-snapshot: FTBFS on armel, armhf: LLVM runs out of memory)

Your message dated Mon, 02 Sep 2024 22:19:16 + with message-id and subject line Bug#1080323: fixed in gnome-snapshot 47~beta-2 has caused the Debian Bug report #1080323, regarding gnome-snapshot: FTBFS on armel, armhf: LLVM runs out of memory to be marked as done. This means that you claim th

Processed: merging 1053077 1071806

Processing commands for cont...@bugs.debian.org: > merge 1053077 1071806 Bug #1053077 [src:powermock] powermock: FTBFS with default Java 21 in unstable Bug #1053077 [src:powermock] powermock: FTBFS with default Java 21 in unstable Marked as found in versions powermock/1.6.6-1. Bug #1071806 [src:po

Bug#1075109: kbd: ftbfs with GCC-14

Control: tags -1 upstream fixed-upstream patch On Sun, Aug 18, 2024 at 01:58:12AM +0200, Andreas Henriksson wrote: > forwarded 1075109 https://github.com/legionus/kbd/pull/119 Just confirmed: this patch fixes the FTBFS. It was already merged upstream. Thus now tagging accordingly. Cheers, Flo

Processed: Re: Bug#1075109: kbd: ftbfs with GCC-14

Processing control commands: > tags -1 upstream fixed-upstream patch Bug #1075109 [src:kbd] kbd: ftbfs with GCC-14 Added tag(s) patch, upstream, and fixed-upstream. -- 1075109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075109 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: Re: Bug#1074915: discount: ftbfs with GCC-14

Processing control commands: > tags -1 patch Bug #1074915 [src:discount] discount: ftbfs with GCC-14 Added tag(s) patch. -- 1074915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1074915: discount: ftbfs with GCC-14

Control: tags -1 patch On Wed, Jul 03, 2024 at 12:25:19PM +, Matthias Klose wrote: > [...] > The package fails to build in a test rebuild on at least amd64 with > gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The > severity of this report will be raised before the trixie release. >

Bug#1075157: libcddb: ftbfs with GCC-14

Control: tags -1 patch On Wed, Jul 03, 2024 at 12:32:51PM +, Matthias Klose wrote: > [...] > The package fails to build in a test rebuild on at least amd64 with > gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The > severity of this report will be raised before the trixie release. >

Processed: Re: Bug#1075157: libcddb: ftbfs with GCC-14

Processing control commands: > tags -1 patch Bug #1075157 [src:libcddb] libcddb: ftbfs with GCC-14 Added tag(s) patch. -- 1075157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075157 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1075188: libmpc: ftbfs with GCC-14

Control: tag -1 patch On Wed, Jul 03, 2024 at 12:33:50PM +, Matthias Klose wrote: > [...] > The package fails to build in a test rebuild on at least amd64 with > gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The > severity of this report will be raised before the trixie release. >

Processed: Re: Bug#1075188: libmpc: ftbfs with GCC-14

Processing control commands: > tag -1 patch Bug #1075188 [src:libmpc] libmpc: ftbfs with GCC-14 Added tag(s) patch. -- 1075188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1075676: marked as done (xoscope: ftbfs with GCC-14)

Your message dated Mon, 02 Sep 2024 18:37:17 + with message-id and subject line Bug#1075676: fixed in xoscope 2.3-2 has caused the Debian Bug report #1075676, regarding xoscope: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1075269: mhash: ftbfs with GCC-14

Control: tag -1 patch On Wed, Jul 03, 2024 at 12:36:24PM +, Matthias Klose wrote: > [...] > The package fails to build in a test rebuild on at least amd64 with > gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The > severity of this report will be raised before the trixie release. >

Processed: Re: Bug#1075269: mhash: ftbfs with GCC-14

Processing control commands: > tag -1 patch Bug #1075269 [src:mhash] mhash: ftbfs with GCC-14 Added tag(s) patch. -- 1075269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075269 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1010445: marked as done (mono-complete: Mono package in Debian is very outdated (6.8 but should be 6.12))

Your message dated Mon, 02 Sep 2024 18:00:36 + with message-id and subject line Bug#1010445: fixed in mono 6.12.0.199+dfsg-1 has caused the Debian Bug report #1010445, regarding mono-complete: Mono package in Debian is very outdated (6.8 but should be 6.12) to be marked as done. This means t

Bug#1075284: marked as done (mono: ftbfs with GCC-14)

Your message dated Mon, 02 Sep 2024 18:00:36 + with message-id and subject line Bug#1075284: fixed in mono 6.12.0.199+dfsg-1 has caused the Debian Bug report #1075284, regarding mono: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1074355: libmina-sshd-java: FTBFS more than 50% of the time

Note: It is possible and likely that the reason it fails for me is different than the reason in the original report, i.e. java.io.IOException: Mount point not found. For simplicity I decided to raise this one because it FTBFS consistently for me. I will be happy to provide more feedback if a part

Processed: libmina-sshd-java: FTBFS more than 50% of the time

Processing commands for cont...@bugs.debian.org: > severity 1074355 serious Bug #1074355 [src:libmina-sshd-java] libmina-sshd-java: FTBFS: Build-time tests fails in some chroots Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance

Bug#1073001: fixed upstream

Le lun. 2 sept. 2024 à 18:56, Colin Watson a écrit : > On Thu, Jul 18, 2024 at 02:08:32PM +0200, Hans-Christoph Steiner wrote: > > It is fixed upstream: > > https://github.com/buildbot/buildbot/commit/291df50dc3f27adb47a001fc154cf4c55490687e > > Thanks. > And then I noticed that Alexandre committe

Bug#1073001: fixed upstream

On Thu, Jul 18, 2024 at 02:08:32PM +0200, Hans-Christoph Steiner wrote: > It is fixed upstream: > https://github.com/buildbot/buildbot/commit/291df50dc3f27adb47a001fc154cf4c55490687e Thanks. I was going to try to work on this bug, but I found that `gbp pq import` in the current repository doesn't

Bug#1079757: marked as done (setuptools test command is removed)

Your message dated Mon, 02 Sep 2024 16:06:31 + with message-id and subject line Bug#1079757: fixed in supervisor 4.2.5-2 has caused the Debian Bug report #1079757, regarding setuptools test command is removed to be marked as done. This means that you claim that the problem has been dealt with

Bug#1056435: Patch added

On Fri, Jun 07, 2024 at 06:12:31PM +0100, Jelmer Vernooij wrote: > I've patched the git repo to mark python 3.12 as supported. > > However, there are several test failures with python 3.12 that need to be > fixed: > > == > ERROR:

Processed: Re: Bug#1079842: Should debbugs be removed from unstable?

Processing control commands: > severity -1 normal Bug #1079842 [src:debbugs] Should debbugs be removed from unstable? Severity set to 'normal' from 'serious' -- 1079842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079842 Debian Bug Tracking System Contact ow...@bugs.debian.org with proble

Bug#1079842: Should debbugs be removed from unstable?

Control: severity -1 normal On Wed, 28 Aug 2024, Helmut Grohne wrote: > In case the package should be kept in unstable, please evaluate each of the > RC-bugs listed above. The existing RC bugs are correct, and keeping this package in unstable is useful because it tracks issues which are specific

Processed: Update liquidsoap

Processing commands for cont...@bugs.debian.org: > # Rebuilds blocked by FTBFS > block 1077110 by 1064128 Bug #1077110 [src:liquidsoap] liquidsoap: needs rebuild against dh-elpa >=2.1.5 1077110 was not blocked by any bugs. 1077110 was not blocking any bugs. Added blocking bug(s) of 1077110: 106412

Processed: Bug#1079757 marked as pending in supervisor

Processing control commands: > tag -1 pending Bug #1079757 [src:supervisor] setuptools test command is removed Added tag(s) pending. -- 1079757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1079757: marked as pending in supervisor

Control: tag -1 pending Hello, Bug #1079757 in supervisor 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/supervisor/-/commit/ea8be48cf0094

Bug#1080323: gnome-snapshot: FTBFS on armel, armhf: LLVM runs out of memory

02.09.2024 10:57:26 Simon McVittie : > Source: gnome-snapshot > Version: 47~beta-1 > Severity: serious > Tags: experimental ftbfs > Justification: fails to build from source (but built successfully in the past) > User: debian-...@lists.debian.org > Usertags: armel armhf > X-Debbugs-CC: debian-...@

Bug#1080330: coreutils: who no longer works

severity 1080330 normal stop On Mon, Sep 02, 2024 at 01:07:59PM +0200, Vincent Lefevre wrote: Package: coreutils Version: 9.4-3.1 Severity: grave Justification: renders package unusable That's a ridiculous severity/rationale

Bug#1073483: Intent to NMU apt-src to fix its trivial FTBFS bug

Hello László, Am Sun, Sep 01, 2024 at 09:19:32PM +0200 schrieb László Böszörményi (GCS): > On Sun, Sep 1, 2024 at 8:46 PM Helge Kreutzmann wrote: > > apt-src_0.25.4.dsc: > > dscverify: apt-src_0.25.4.dsc failed signature check: > > gpg: no valid OpenPGP data found. > Yup, I don't sign half or eve

Bug#1070962: ruby2.7: FTBFS: failing tests

Control: fixed -1 2.7.4-1+deb11u2 thanks

Processed: Re: ruby2.7: FTBFS: failing tests

Processing control commands: > fixed -1 2.7.4-1+deb11u2 Bug #1070962 {Done: Santiago Vila } [src:ruby2.7] ruby2.7: FTBFS: failing tests The source 'ruby2.7' and version '2.7.4-1+deb11u2' do not appear to match any binary packages Marked as fixed in versions ruby2.7/2.7.4-1+deb11u2. -- 1070962:

Bug#1080064: marked as done (nfs-ganesha: /usr-move got reverted)

Your message dated Mon, 02 Sep 2024 14:52:17 + with message-id and subject line Bug#1080064: fixed in nfs-ganesha 5.9-4 has caused the Debian Bug report #1080064, regarding nfs-ganesha: /usr-move got reverted to be marked as done. This means that you claim that the problem has been dealt with

Bug#1080118: marked as done (netavark: FTBFS: error: failed to select a version for the requirement `clap = "~4.4.8"`)

Your message dated Mon, 02 Sep 2024 13:51:28 + with message-id and subject line Bug#1080118: fixed in netavark 1.12.1-2 has caused the Debian Bug report #1080118, regarding netavark: FTBFS: error: failed to select a version for the requirement `clap = "~4.4.8"` to be marked as done. This mea

Bug#1078454: marked as done (golang-tags.cncf-container-device-interface-dev: missing Breaks+Replaces: golang-github-container-orchestrated-devices-container-device-interface-dev (<< 0.8.0-4))

Your message dated Mon, 02 Sep 2024 13:33:57 + with message-id and subject line Bug#1078454: fixed in golang-tags.cncf-container-device-interface 0.8.0-5 has caused the Debian Bug report #1078454, regarding golang-tags.cncf-container-device-interface-dev: missing Breaks+Replaces: golang-git

Processed: Bug#1078454 marked as pending in golang-github-container-orchestrated-devices-container-device-interface

Processing control commands: > tag -1 pending Bug #1078454 [golang-tags.cncf-container-device-interface-dev] golang-tags.cncf-container-device-interface-dev: missing Breaks+Replaces: golang-github-container-orchestrated-devices-container-device-interface-dev (<< 0.8.0-4) Added tag(s) pending.

Bug#1078454: marked as pending in golang-github-container-orchestrated-devices-container-device-interface

Control: tag -1 pending Hello, Bug #1078454 in golang-github-container-orchestrated-devices-container-device-interface 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.de

Bug#1080064: nfs-ganesha: /usr-move got reverted

Hi Helmut, thanks for checking this. I am working on a fix. Christoph Am 30.08.24 um 09:34 schrieb Helmut Grohne: we filed #1071916 about moving systemd units from aliased locations to /usr earlier and you fixed it in 4.3-11. Now with version 5.9-3, aliased units are reintroduced: OpenPGP_

Bug#1080249: marked as done (python3-autodocsumm has an undeclared file conflict on /usr/lib/python3/dist-packages/conftest.py)

Your message dated Mon, 02 Sep 2024 13:05:13 + with message-id and subject line Bug#1080249: fixed in python-autodocsumm 0.2.13-3 has caused the Debian Bug report #1080249, regarding python3-autodocsumm has an undeclared file conflict on /usr/lib/python3/dist-packages/conftest.py to be marked

Bug#1080337: gst-plugins-base1.0: Fails to build with mesa 24.2

Source: mesa Version: 24.2.1-3 Severity: serious Tags: ftbfs Control: affects -1 src:gst-plugins-base1.0 The new version of mesa is causing gst-plugins-base1.0 to fail to build on amd64 because of failing build tests. (Build test failures are currently ignored on other architectures.) See also ht

Processed: gst-plugins-base1.0: Fails to build with mesa 24.2

Processing control commands: > affects -1 src:gst-plugins-base1.0 Bug #1080337 [src:mesa] gst-plugins-base1.0: Fails to build with mesa 24.2 Added indication that 1080337 affects src:gst-plugins-base1.0 -- 1080337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080337 Debian Bug Tracking Sys

Bug#1079345: src:pydantic: fails to migrate to testing for too long: Build-Depends on pydantic-core

On Thu, Aug 22, 2024 at 04:09:07PM +0200, Paul Gevers wrote: > The Release Team considers packages that are out-of-sync between testing and > unstable for more than 30 days as having a Release Critical bug in testing > [1]. Your package src:pydantic has been trying to migrate for 33 days [2]. > Hen

Bug#1054372: marked as done (python3-django-macaddress: incompatible with python3-django in bookworm)

Your message dated Mon, 02 Sep 2024 12:34:18 + with message-id and subject line Bug#1054372: fixed in django-macaddress 1.8.0-1 has caused the Debian Bug report #1054372, regarding python3-django-macaddress: incompatible with python3-django in bookworm to be marked as done. This means that y

Processed: tagging 1054372

Processing commands for cont...@bugs.debian.org: > tags 1054372 + bookworm Bug #1054372 [python3-django-macaddress] python3-django-macaddress: incompatible with python3-django in bookworm Added tag(s) bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1054

Bug#1075034: marked as pending in goocanvas-2.0

Control: tag -1 pending Hello, Bug #1075034 in goocanvas-2.0 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/debian/goocanvas-2.0/-/commit/968bf29cfb95598ee5820

Processed: Bug#1075034 marked as pending in goocanvas-2.0

Processing control commands: > tag -1 pending Bug #1075034 [src:goocanvas-2.0] goocanvas-2.0: ftbfs with GCC-14 Added tag(s) pending. -- 1075034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1080325: libadwaita-1: FTBFS on i386: segfault in test-bottom-sheet

Processing control commands: > forwarded -1 https://gitlab.gnome.org/GNOME/libadwaita/-/issues/913 Bug #1080325 [src:libadwaita-1] libadwaita-1: FTBFS on i386: segfault in test-bottom-sheet Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/libadwaita/-/issues/913'. -- 1080325: ht

Bug#1080325: libadwaita-1: FTBFS on i386: segfault in test-bottom-sheet

Control: forwarded -1 https://gitlab.gnome.org/GNOME/libadwaita/-/issues/913 On Mon, Sep 2, 2024 at 5:12 AM Simon McVittie wrote: > libadwaita-1 since 1.6~beta-1 failed to build from source on the i386 buildd, > with a test failure that does not seem to occur on any other architecture: I reporte

Bug#1067709: marked as done (FTBFS in armel/armhf: some symbols disappeared)

control: reopen -1 control: found -1 1.4.3+dfsg-2 Argh, apparently it still fails. Investigating. G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org pe...@morpheusly.com PGP key:https://www.ringlet.net/roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E

Processed: Re: Bug#1067709: marked as done (FTBFS in armel/armhf: some symbols disappeared)

Processing control commands: > reopen -1 Bug #1067709 {Done: Peter Pentchev } [src:dante] FTBFS in armel/armhf: some symbols disappeared '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 lo

Bug#1080330: coreutils: who no longer works

BTW, note that the "w" utility from procps still works, but according to strace, it doesn't seem to use wtmpdb. However, though the w(1) and who(1) man pages are similar ("show who is logged on"), w misses some information. -- Vincent Lefèvre - Web: 100% accessible vali

Processed: Re: coreutils: who no longer works

Processing control commands: > retitle -1 coreutils: "who" no longer works with systemd 256.5-2 (utmp is now > disabled, use wtmpdb instead) Bug #1080330 [coreutils] coreutils: who no longer works Changed Bug title to 'coreutils: "who" no longer works with systemd 256.5-2 (utmp is now disabled,

Bug#1080330: coreutils: who no longer works

Control: retitle -1 coreutils: "who" no longer works with systemd 256.5-2 (utmp is now disabled, use wtmpdb instead) (title with more details) -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer

Bug#1080126: marked as done (python-applicationinsights: FTBFS: ModuleNotFoundError: No module named 'django')

Your message dated Mon, 02 Sep 2024 11:04:25 + with message-id and subject line Bug#1080126: fixed in python-applicationinsights 0.11.10-2 has caused the Debian Bug report #1080126, regarding python-applicationinsights: FTBFS: ModuleNotFoundError: No module named 'django' to be marked as done

Bug#1080330: coreutils: who no longer works

Package: coreutils Version: 9.4-3.1 Severity: grave Justification: renders package unusable Though the whole package is not unusable, an important utility is now unusable because coreutils still hasn't switched to wtmpdb. This must be fixed before the next Debian release. With systemd 256.5-2, "w

Bug#1080126: marked as pending in python-applicationinsights

Control: tag -1 pending Hello, Bug #1080126 in python-applicationinsights 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-applicatio

Processed: Bug#1080126 marked as pending in python-applicationinsights

Processing control commands: > tag -1 pending Bug #1080126 [src:python-applicationinsights] python-applicationinsights: FTBFS: ModuleNotFoundError: No module named 'django' Ignoring request to alter tags of bug #1080126 to the same tags previously set -- 1080126: https://bugs.debian.org/cgi-bin

Bug#1079842: Should debbugs be removed from unstable

Hi, I thing that when someone tries to "sell" it's product it should at least eat it's own dog food. On a more practical note, this is a native package. The bugs belong here, if package is RM'ed all theses bugs will be automatically closed. Where should else they go ? They could be reassign b

Bug#1080126: marked as pending in python-applicationinsights

Control: tag -1 pending Hello, Bug #1080126 in python-applicationinsights 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-applicatio

Processed: Bug#1080126 marked as pending in python-applicationinsights

Processing control commands: > tag -1 pending Bug #1080126 [src:python-applicationinsights] python-applicationinsights: FTBFS: ModuleNotFoundError: No module named 'django' Added tag(s) pending. -- 1080126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080126 Debian Bug Tracking System Con

Processed: tagging 1080130

Processing commands for cont...@bugs.debian.org: > tags 1080130 + wontfix Bug #1080130 [src:python-funcsigs] python-funcsigs: FTBFS: ERROR: test_readme (tests.test_funcsigs.TestFunctionSignatures) Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance.

Bug#1080325: libadwaita-1: FTBFS on i386: segfault in test-bottom-sheet

Source: libadwaita-1 Version: 1.6~beta-1 Severity: serious Tags: experimental ftbfs Justification: fails to build from source (but built successfully in the past) User: debian...@lists.debian.org Usertags: i386 X-Debbugs-Cc: b...@debian.org libadwaita-1 since 1.6~beta-1 failed to build from source

Bug#1080324: libadwaita-1: FTBFS on s390x: test_adw_bottom_sheet_align: assertion failed (adw_bottom_sheet_get_align (sheet) == 0 (+/- 0.005)): (0.0078125 == 0)

Source: libadwaita-1 Version: 1.6~rc-1 Severity: serious Tags: experimental ftbfs Justification: fails to build from source (but built successfully in the past) User: debian-s...@lists.debian.org Usertags: s390x X-Debbugs-Cc: debian-s...@lists.debian.org libadwaita-1_1.6~rc-1 failed to build from

Bug#1079757: setuptools test command is removed

Dear Maintainers, Would it be possible to consider the merge proposal[1] as the solution for this issue. Best Regards, Vladimir. [1] https://salsa.debian.org/python-team/packages/supervisor/-/merge_requests/2

Bug#1080323: gnome-snapshot: FTBFS on armel, armhf: LLVM runs out of memory

Source: gnome-snapshot Version: 47~beta-1 Severity: serious Tags: experimental ftbfs Justification: fails to build from source (but built successfully in the past) User: debian-...@lists.debian.org Usertags: armel armhf X-Debbugs-CC: debian-...@lists.debian.org, debian-r...@lists.debian.org The ne

Bug#1080144: marked as done (xbyak: FTBFS: failing tests)

Your message dated Mon, 02 Sep 2024 08:39:54 + with message-id and subject line Bug#1080144: fixed in xbyak 7.07.1-1 has caused the Debian Bug report #1080144, regarding xbyak: FTBFS: failing tests to be marked as done. This means that you claim that the problem has been dealt with. If this i

Processed: Re: heaptrack: ftbfs with GCC-14

Processing commands for cont...@bugs.debian.org: > tags 1075065 + fixed-upstream patch Bug #1075065 [src:heaptrack] heaptrack: ftbfs with GCC-14 Added tag(s) fixed-upstream and patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1075065: https://bugs.debian.org

Bug#1075065: heaptrack: ftbfs with GCC-14

tags 1075065 + fixed-upstream patch thanks On Wed, 03 Jul 2024 12:30:02 + Matthias Klose wrote: The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release.

Bug#1079842: Should debbugs be removed from unstable

On Thu, 29 Aug 2024 08:42:41 +0200 Alexandre Detiste wrote: > I know of one single other instance > at https://debbugs.gnu.org/ There are a few more Debbugs instances: * Debian: https://bugs.debian.org/ * GNU: https://debbugs.gnu.org/ * Emacs: https://debbugs.juix.org/ * x2go: https://bugs.x

Bug#1075569: marked as done (tgif: ftbfs with GCC-14)

Your message dated Mon, 02 Sep 2024 07:07:34 + with message-id and subject line Bug#1075569: fixed in tgif 1:4.2.5-2 has caused the Debian Bug report #1075569, regarding tgif: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is no