Bug#1052570: marked as done (jlapack: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7)

Your message dated Sat, 07 Sep 2024 06:04:00 + with message-id and subject line Bug#1052570: fixed in jlapack 0.8~dfsg-6 has caused the Debian Bug report #1052570, regarding jlapack: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7 to be marked as done. This means that yo

Bug#1080096: fail to build with kernel 6.10.6+bpo-amd64 - implicit declaration of function ‘follow_pfn’

Thank you very much for the backport. I didn't know Sid and bookworm/backport provided the same version of Nvidia drivers (plus I try to avoid Sid because 'it's dangerous ' ;) ) I am doing some stuff with docker/Nvidia and I have a little issue with software which don't seem to see the HW properl

Processed: Bug#1052570 marked as pending in jlapack

Processing control commands: > tag -1 pending Bug #1052570 [src:jlapack] jlapack: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7 Added tag(s) pending. -- 1052570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052570 Debian Bug Tracking System Contact ow...@bugs.debian

Bug#1052570: marked as pending in jlapack

Control: tag -1 pending Hello, Bug #1052570 in jlapack 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/java-team/jlapack/-/commit/6b857687a30951b64daea3bada0b77

Processed: gimplensfun: diff for NMU version 0.2.4-1.2

Processing control commands: > tags 1081026 + pending Bug #1081026 [src:gimplensfun] gimplensfun: FTBFS with exiv2 0.28 Added tag(s) pending. -- 1081026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1081026: gimplensfun: diff for NMU version 0.2.4-1.2

Control: tags 1081026 + pending Dear maintainer, I've prepared an NMU for gimplensfun (versioned as 0.2.4-1.2) and uploaded it to DELAYED/11. Please feel free to tell me if I should delay it longer. Regards. diff -Nru gimplensfun-0.2.4/debian/changelog gimplensfun-0.2.4/debian/changelog --- gi

Processed: severity of 1081026 is serious

Processing commands for cont...@bugs.debian.org: > severity 1081026 serious Bug #1081026 [src:gimplensfun] gimplensfun: FTBFS with exiv2 0.28 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1081026: https://bugs.debian.or

Bug#1081027: src:sssd: flaky autopkgtest: spawn id exp3 not open

Source: sssd Version: 2.9.5-3 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package. I noticed that it regularly fails. Because the unstable-to-testing migration software now blocks on regressions in t

Processed: Bug#1080122 marked as pending in powerline

Processing control commands: > tag -1 pending Bug #1080122 [src:powerline] powerline: FTBFS: ModuleNotFoundError: No module named 'zsh' Added tag(s) pending. -- 1080122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080122 Debian Bug Tracking System Contact ow...@bugs.debian.org with probl

Bug#1080122: marked as pending in powerline

Control: tag -1 pending Hello, Bug #1080122 in powerline 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/powerline/-/commit/81cf7f5d763ad46

Processed: Remove gandi-cli from Debian

Processing control commands: > retitle 1010138 O: gandi-cli -- command-line interface for Gandi service Bug #1010138 [wnpp] RFA: gandi-cli -- command-line interface for Gandi service Changed Bug title to 'O: gandi-cli -- command-line interface for Gandi service' from 'RFA: gandi-cli -- command-li

Bug#1080122: Fallout from setuptools dropping the test command

On Sat, 31 Aug 2024 16:32:40 + Stefano Rivera wrote: FWIW: I think these bugs were all caused by setuptools v72 dropping support for the "test" command, so dh-python has fallen back to distutils / other test plugins. If you're trying to figure out how to fix the bug, look at the implementat

Processed: Re: Bug#1081025: epoptes: implicit dependency on removed python3-distutils

Processing control commands: > forwarded 1081025 https://github.com/epoptes/epoptes/issues/193 Bug #1081025 [epoptes] epoptes: implicit dependency on removed python3-distutils Set Bug forwarded-to-address to 'https://github.com/epoptes/epoptes/issues/193'. -- 1081025: https://bugs.debian.org/cgi

Bug#1081025: epoptes: implicit dependency on removed python3-distutils

Control: forwarded 1081025 https://github.com/epoptes/epoptes/issues/193 On 2024-09-06, Vagrant Cascadian wrote: > Running epoptes on debian trixie results in: > > $ epoptes > Traceback (most recent call last): > File "/usr/bin/epoptes", line 20, in > from epoptes.ui import gui >

Bug#1080480: marked as done (rust-merge: most autopkgtests fail)

Your message dated Sat, 07 Sep 2024 02:38:13 + with message-id and subject line Bug#1080480: fixed in rust-merge 0.1.0-2 has caused the Debian Bug report #1080480, regarding rust-merge: most autopkgtests fail to be marked as done. This means that you claim that the problem has been dealt with

Bug#1081025: epoptes: implicit dependency on removed python3-distutils

Package: epoptes Version: 23.08-1 Severity: serious X-Debbugs-Cc: vagr...@debian.org Running epoptes on debian trixie results in: $ epoptes Traceback (most recent call last): File "/usr/bin/epoptes", line 20, in from epoptes.ui import gui File "/usr/lib/python3/dist-packages/ep

Bug#1071119: snapd: move files to /usr for DEP17

Am 06.09.24 um 11:32 schrieb Zygmunt Krynicki: Wiadomość napisana przez Michael Biebl w dniu 3 wrz 2024, o godz. 16:51: Control: tags -1 + Am 03.09.24 um 15:19 schrieb Zygmunt Krynicki: If you have time do NMU, I will unclude the changes in the next upstream release. Apologies for droppi

Processed: Re: knot: FTBFS on armel: insufficient atomics

Processing control commands: > found -1 3.4.0-2 Bug #1080514 {Done: Jakub Ružička } [src:knot] knot: FTBFS on armel: insufficient atomics Marked as found in versions knot/3.4.0-2; no longer marked as fixed in versions knot/3.4.0-2 and reopened. -- 1080514: https://bugs.debian.org/cgi-bin/bugre

Processed: closing 1075522, closing 1071119

Processing commands for cont...@bugs.debian.org: > close 1075522 2.65.1-1 Bug #1075522 [src:snapd] snapd: ftbfs with GCC-14 Marked as fixed in versions snapd/2.65.1-1. Bug #1075522 [src:snapd] snapd: ftbfs with GCC-14 Marked Bug as done > close 1071119 2.65.1-1 Bug #1071119 [snapd] snapd: move fil

Bug#1080514: knot: FTBFS on armel: insufficient atomics

Control: found -1 3.4.0-2 Unfortunately still fails with the same error on armel for 3.4.0-2 Thus reopening https://buildd.debian.org/status/fetch.php?pkg=knot&arch=armel&ver=3.4.0-2&stamp=1725652479&raw=0 On Thu, 05 Sep 2024 10:52:03 +0200 Emilio Pozuelo Monfort wrote: Source: knot Version:

Bug#1077037: marked as done (pbuilder: missing dependency on non-essential package mount)

Your message dated Fri, 06 Sep 2024 22:34:15 + with message-id and subject line Bug#1077037: fixed in pbuilder 0.231.1 has caused the Debian Bug report #1077037, regarding pbuilder: missing dependency on non-essential package mount to be marked as done. This means that you claim that the prob

Bug#1081016: mutter: keybindings autopkgtest fails because it needs compiled org.gnome.mutter.test gsettings schema

I have now fixed the other autopkgtest failures in Salsa. Thank you, Jeremy Bícha

Processed: Re: Bug#1072512: debci: mutter fails tests

Processing control commands: > severity -1 serious Bug #1072512 [src:mutter] debci: mutter fails tests Severity set to 'serious' from 'important' > retitle -1 mutter: flaky autopgktest Bug #1072512 [src:mutter] debci: mutter fails tests Changed Bug title to 'mutter: flaky autopgktest' from 'debci:

Bug#993849: marked as done (gnome-authenticator: Depends on deprecated libhandy version 0)

Your message dated Fri, 06 Sep 2024 21:33:46 + with message-id and subject line Bug#993849: fixed in gnome-authenticator 4.5.0-1 has caused the Debian Bug report #993849, regarding gnome-authenticator: Depends on deprecated libhandy version 0 to be marked as done. This means that you claim th

Bug#1075273: marked as done (mindthegap: ftbfs with GCC-14)

Your message dated Fri, 06 Sep 2024 20:53:55 + with message-id and subject line Bug#1075273: fixed in mindthegap 2.3.0-4 has caused the Debian Bug report #1075273, regarding mindthegap: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#838137: Tags pending in Git

Control: tags -1 pending Thanks These bugs are fixed in Git but not uploaded since bug #756997 is not fixed which seems to make such an upload not sensible. Kind regards Andreas. -- https://fam-tille.de

Processed: Tags pending in Git

Processing control commands: > tags -1 pending Bug #838137 [src:critterding] critterding: FTBFS in experimental: be_command_system.cpp:13:94: error: '_1' was not declared in this scope Added tag(s) pending. -- 838137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838137 Debian Bug Tracking

Bug#1081016: mutter: keybindings autopkgtest fails because it needs compiled org.gnome.mutter.test gsettings schema

Source: mutter Version: 47~rc-1 Severity: serious mutter added new installed tests in 47~rc that we then run as autopkgtests. They asked me before and I said it was ok. One of the new tests is a keybindings test that depends on a gsettings schema org.gnome.mutter.test . That schema is installed b

Bug#1081015: wcc: Built-Using field incorrectly used

Source: wcc Version: 0.0.2+dfsg-4.4 Severity: serious Justification: Policy violation Dear Maintainer, as a consequence of #949601 the Built-Using field was introduced for wcc. Unfortunately it is not used in accordance with Debian Policy Section 7.8 (I think the license requirements mentioned in

Bug#1081014: Should python3-zipp be dropped in trixie?

Package: python3-zipp Version: 3.20.1-1 Severity: serious Looking at CVE-2024-5569 and the potential of future CVEs, I wonder whether there is any reason why reverse dependencies still need this package or whether they could use the version vendored in src:python3.* If there is a reason, feel fre

Bug#1080117: marked as done (nauty: FTBFS: ./nauty/nauty.h:64:23: error: operator '==' has no left operand)

Your message dated Fri, 6 Sep 2024 20:21:29 + with message-id <87y144jzxz@piedmont.edu> and subject line Re: Bug#1080117: nauty: FTBFS: ./nauty/nauty.h:64:23: error: operator '==' has no left operand has caused the Debian Bug report #1080117, regarding nauty: FTBFS: ./nauty/nauty.h:64:23:

Processed: notfound 1076955 in 1.1.0, found 1076955 in 1.1.0~git20220701.1d4e111-0.5, closing 1076955 ...

Processing commands for cont...@bugs.debian.org: > notfound 1076955 1.1.0 Bug #1076955 [pam-python] pam-python in latest Debian is vulnerable to CVE-2019-16729 again There is no source info for the package 'pam-python' at version '1.1.0' with architecture '' Unable to make a source version for v

Bug#1076955: notfound 1076955 in 1.1.0, found 1076955 in 1.1.0~git20220701.1d4e111-0.5, closing 1076955 ...

notfound 1076955 1.1.0 found 1076955 1.1.0~git20220701.1d4e111-0.5 close 1076955 1.1.0~git20220701.1d4e111-1 tags 1076955 + security thanks

Bug#1080514: marked as done (knot: FTBFS on armel: insufficient atomics)

Your message dated Fri, 06 Sep 2024 19:10:12 + with message-id and subject line Bug#1080514: fixed in knot 3.4.0-2 has caused the Debian Bug report #1080514, regarding knot: FTBFS on armel: insufficient atomics to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1080499: marked as done (t64 suffix should be dropped after bumping the soname)

Your message dated Fri, 06 Sep 2024 19:10:12 + with message-id and subject line Bug#1080499: fixed in knot 3.4.0-2 has caused the Debian Bug report #1080499, regarding t64 suffix should be dropped after bumping the soname to be marked as done. This means that you claim that the problem has be

Processed: tag peding

Processing commands for cont...@bugs.debian.org: > tags 1080220 + pending Bug #1080220 [src:gdebi] FTBFS: error: invalid command 'test' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1080220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug

Bug#1075282: marked as done (moarvm: ftbfs with GCC-14)

Your message dated Fri, 06 Sep 2024 17:19:12 + with message-id and subject line Bug#1077392: fixed in moarvm 2022.12+dfsg-2 has caused the Debian Bug report #1077392, regarding moarvm: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#1077392: marked as done (moarvm: FTBFS: src/6model/containers.c:117:5: error: initialization of ‘void (*)(MVMThreadContext *, MVMObject *, MVMuint64)’ {aka ‘void (*)(MVMThreadContext *, MVMObject

Your message dated Fri, 06 Sep 2024 17:19:12 + with message-id and subject line Bug#1077392: fixed in moarvm 2022.12+dfsg-2 has caused the Debian Bug report #1077392, regarding moarvm: FTBFS: src/6model/containers.c:117:5: error: initialization of ‘void (*)(MVMThreadContext *, MVMObject *, MV

Bug#1078825: [Debian-med-packaging] Bug#1078825: src:ncbi-tools6: unsatisfied build dependency in testing: libpcre3-dev

Hi Aaron, Aaron M. Ucko, on 2024-09-04: > Unless I've missed something, there should be no need for any porting > here, just a small build system change, either to stop building > PCRE-based binaries (which weren't getting installed anyway) […] Thanks for the ideas, I would favor that option over

Processed: boost1.83: Autopkgtests fail on armhf due to OpenMPI changes

Processing control commands: > severity -1 serious Bug #1079106 [boost1.83] boost1.83: Autopkgtests fail on armhf due to OpenMPI changes Severity set to 'serious' from 'normal' -- 1079106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079106 Debian Bug Tracking System Contact ow...@bugs.de

Bug#1031046: Backport to bookworm

Quoting José Miguel Gonçalves (2024-09-06 18:38:28) > On 06/09/24 17:27, Jonas Smedegaard wrote: > > Please subscribe to our mailinglist and discuss more there, and please > > join our Salsa team - see details athttps://wiki.debian.org/Teams/VoIP/ > > I'm a long time subscriber from your mailingli

Bug#1031046: Backport to bookworm

On 06/09/24 17:27, Jonas Smedegaard wrote: Please subscribe to our mailinglist and discuss more there, and please join our Salsa team - see details athttps://wiki.debian.org/Teams/VoIP/ I'm a long time subscriber from your mailinglist... and I've just applied for a Salsa account.

Bug#1031046: Backport to bookworm

Quoting José Miguel Gonçalves (2024-09-06 18:11:57) > On 06/09/24 16:35, Jonas Smedegaard wrote: > > I can do the task of releasing patches-applied updates, so you need not > > be an official Debian developer to help. All you need is dedication to > > keep an eye on stable and oldstable branches o

Bug#1031046: Backport to bookworm

On 06/09/24 16:35, Jonas Smedegaard wrote: I can do the task of releasing patches-applied updates, so you need not be an official Debian developer to help. All you need is dedication to keep an eye on stable and oldstable branches of Debian, and the ability to*try* to apply patches. If you not

Bug#1080988: src:r-cran-pbkrtest: fails to migrate to testing for too long: new Build-Depends not ready to migrate

Hi Paul, On 6 September 2024 at 17:24, Paul Gevers wrote: | Hi Dirk, | | On 06-09-2024 15:19, Dirk Eddelbuettel wrote: | > If you think there is anything I could or should do let me know. I packaged | > the newest upstream version, and looked after its dependencies. | | You could check the exc

Bug#1031046: Backport to bookworm

Quoting José Miguel Gonçalves (2024-09-06 16:37:28) > I was thinking that it would be possible to go directly from unstable to > backports. Quoting from https://backports.debian.org/: "(In a few cases, > usually for security updates, backports are also created from the Debian > unstable distribu

Bug#1080096: fail to build with kernel 6.10.6+bpo-amd64 - implicit declaration of function ‘follow_pfn’

On Fri, Sep 06, 2024 at 05:21:36PM +0200, Andreas Beckmann wrote: > src:nvidia-graphics-drivers for bookworm-backports is in BACKPORTS-NEW. Awesome, thank you. > Just curious: Why didn't you simply rebuild the package from sid for > bookworm instead of digging for patches on the internet? I only

Bug#1080988: src:r-cran-pbkrtest: fails to migrate to testing for too long: new Build-Depends not ready to migrate

Hi Dirk, On 06-09-2024 15:19, Dirk Eddelbuettel wrote: If you think there is anything I could or should do let me know. I packaged the newest upstream version, and looked after its dependencies. You could check the excuses, which say: """ Issues preventing migration: Build-Depends(-Arch):

Processed: Re: Bug#1080096: fail to build with kernel 6.10.6+bpo-amd64 - implicit declaration of function ‘follow_pfn’

Processing control commands: > tag -1 pending Bug #1080096 [nvidia-kernel-dkms] fail to build with kernel 6.10.6+bpo-amd64 - implicit declaration of function ‘follow_pfn’ Added tag(s) pending. -- 1080096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080096 Debian Bug Tracking System Conta

Bug#1080096: fail to build with kernel 6.10.6+bpo-amd64 - implicit declaration of function ‘follow_pfn’

Control: tag -1 pending src:nvidia-graphics-drivers for bookworm-backports is in BACKPORTS-NEW. On 9/4/24 17:15, Stefano Zacchiroli wrote: On Tue, Sep 03, 2024 at 06:35:06PM +0200, fr.hame...@gmail.com wrote: To solve it have applied the patches given by nvidia the 21 of July here : https://fo

Bug#1079499: marked as done (gjs: autopkgtest regression in experimental: cannot find typelib for GjsTestTools, Regress, etc.)

Your message dated Fri, 06 Sep 2024 15:00:25 + with message-id and subject line Bug#1079499: fixed in gjs 1.81.90-1 has caused the Debian Bug report #1079499, regarding gjs: autopkgtest regression in experimental: cannot find typelib for GjsTestTools, Regress, etc. to be marked as done. This

Bug#1031046: Backport to bookworm

Hi Jonas, I was thinking that it would be possible to go directly from unstable to backports. Quoting from https://backports.debian.org/: "(In a few cases, usually for security updates, backports are also created from the Debian unstable distribution.)". If Asterisk does not fit in that catego

Bug#1072131: marked as done (swiftlang FTBFS with glibc 2.38)

Your message dated Fri, 06 Sep 2024 14:06:52 + with message-id and subject line Bug#1072131: fixed in swiftlang 5.7.3-1 has caused the Debian Bug report #1072131, regarding swiftlang FTBFS with glibc 2.38 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1080998: gthumb FTBFS on 32 bit architectures with 64 bit time_t with gcc 14

Source: gthumb Version: 3:3.12.6-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=gthumb&ver=3%3A3.12.6-1%2Bb3 ... ../gthumb/main-migrate-catalogs.c: In function ‘migration_for_each_file’: ../gthumb/main-migrate-catalogs.c:316:57: error: passing argument 1 of ‘localt

Bug#1031046: Backport to bookworm

Quoting José Miguel Gonçalves (2024-09-06 15:29:12) > Thank you for your quick response. > Please do not consider my questions as I was demanding anything. I did not. In fact, I appreciate knowing that others benefit from my maintenance work, even if it only reaches unstable Debian. > Going to

Bug#1080477: gtk4: FTBFS on mips64el with Mesa 24.2.x: GALLIUM_DRIVER=softpipe no longer works

Also verified working at https://buildd.debian.org/status/package.php?p=gtk4&suite=experimental Jeremy

Bug#1031046: Backport to bookworm

Hi Jonas, Thank you for your quick response. Please do not consider my questions as I was demanding anything. I just wanted a confirmation that Asterisk was still going to be packaged in Debian in the near future (at least, during the life of Asterisk 20). I only have appreciations for the Debi

Bug#1080988: src:r-cran-pbkrtest: fails to migrate to testing for too long: new Build-Depends not ready to migrate

On 6 September 2024 at 14:36, Paul Gevers wrote: | Source: r-cran-pbkrtest | Version: 0.5.2-2 | Severity: serious | Control: close -1 0.5.3-1 | Tags: sid trixie | User: release.debian@packages.debian.org | Usertags: out-of-sync | | Dear maintainer(s), | | The Release Team considers packages

Bug#1080515: marked as done (ddcutil: FTBFS on arm{el,hf}: passing argument 2 of 'str_to_long' from incompatible pointer type)

Your message dated Fri, 6 Sep 2024 16:13:26 +0300 with message-id and subject line Fixed in 2.1.4-3 has caused the Debian Bug report #1080515, regarding ddcutil: FTBFS on arm{el,hf}: passing argument 2 of 'str_to_long' from incompatible pointer type to be marked as done. This means that you clai

Bug#1031046: Backport to bookworm

Hi José, Quoting José Miguel Gonçalves (2024-09-06 13:14:26) > I was wondering, what is the current maintenance status of Asterisk on > Debian? Nothing has changed since my older responses in this bugreport, so please read my other posts here and ask more specifically if there is something you d

Bug#1080996: src:opendmarc: unsatisfied build dependency in testing: miltertest

Source: opendmarc Version: 1.4.2-5 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed f

Bug#1080995: src:libdap: unsatisfied build dependency in testing: libpth-dev

Source: libdap Version: 3.21.0-1.1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed f

Bug#1080994: src:grads: unsatisfied build dependency in testing: libsx-dev (>= 2.08)

Source: grads Version: 3:2.2.1-7 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed fro

Bug#1080993: src:mesa: fails to migrate to testing for too long: triggers autopkgtest issues

Source: mesa Version: 24.1.3-2 Severity: serious Control: close -1 24.2.1-4 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as havi

Processed: src:mesa: fails to migrate to testing for too long: triggers autopkgtest issues

Processing control commands: > close -1 24.2.1-4 Bug #1080993 [src:mesa] src:mesa: fails to migrate to testing for too long: triggers autopkgtest issues Marked as fixed in versions mesa/24.2.1-4. Bug #1080993 [src:mesa] src:mesa: fails to migrate to testing for too long: triggers autopkgtest iss

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

Your message dated Fri, 06 Sep 2024 12:51:43 + with message-id and subject line Bug#1079763: fixed in python-svg.path 6.3-3 has caused the Debian Bug report #1079763, regarding setuptools test command is removed to be marked as done. This means that you claim that the problem has been dealt w

Processed: src:python-pyqtgraph: fails to migrate to testing for too long: new Build-Depends not ready to migate

Processing control commands: > close -1 0.13.7-4 Bug #1080992 [src:python-pyqtgraph] src:python-pyqtgraph: fails to migrate to testing for too long: new Build-Depends not ready to migate Marked as fixed in versions python-pyqtgraph/0.13.7-4. Bug #1080992 [src:python-pyqtgraph] src:python-pyqtgrap

Processed: src:rust-num-traits: fails to migrate to testing for too long: triggers autopkgtest issues

Processing control commands: > close -1 0.2.19-2 Bug #1080991 [src:rust-num-traits] src:rust-num-traits: fails to migrate to testing for too long: triggers autopkgtest issues Marked as fixed in versions rust-num-traits/0.2.19-2. Bug #1080991 [src:rust-num-traits] src:rust-num-traits: fails to mig

Bug#1080991: src:rust-num-traits: fails to migrate to testing for too long: triggers autopkgtest issues

Source: rust-num-traits Version: 0.2.15-1 Severity: serious Control: close -1 0.2.19-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 d

Bug#1080992: src:python-pyqtgraph: fails to migrate to testing for too long: new Build-Depends not ready to migate

Source: python-pyqtgraph Version: 0.13.7-1 Severity: serious Control: close -1 0.13.7-4 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30

Bug#1080990: src:ruby-optimist: fails to migrate to testing for too long: triggers autopkgtest issues

Source: ruby-optimist Version: 3.0.0-2 Severity: serious Control: close -1 3.1.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days

Processed: src:ruby-optimist: fails to migrate to testing for too long: triggers autopkgtest issues

Processing control commands: > close -1 3.1.0-1 Bug #1080990 [src:ruby-optimist] src:ruby-optimist: fails to migrate to testing for too long: triggers autopkgtest issues Marked as fixed in versions ruby-optimist/3.1.0-1. Bug #1080990 [src:ruby-optimist] src:ruby-optimist: fails to migrate to test

Processed: src:rust-target: fails to migrate to testing for too long: autopkgtest regression except on amd64

Processing control commands: > close -1 2.1.0-1 Bug #1080989 [src:rust-target] src:rust-target: fails to migrate to testing for too long: autopkgtest regression except on amd64 Marked as fixed in versions rust-target/2.1.0-1. Bug #1080989 [src:rust-target] src:rust-target: fails to migrate to tes

Bug#1080989: src:rust-target: fails to migrate to testing for too long: autopkgtest regression except on amd64

Source: rust-target Version: 2.0.0-1 Severity: serious Control: close -1 2.1.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as

Processed: src:r-cran-pbkrtest: fails to migrate to testing for too long: new Build-Depends not ready to migrate

Processing control commands: > close -1 0.5.3-1 Bug #1080988 [src:r-cran-pbkrtest] src:r-cran-pbkrtest: fails to migrate to testing for too long: new Build-Depends not ready to migrate Marked as fixed in versions r-cran-pbkrtest/0.5.3-1. Bug #1080988 [src:r-cran-pbkrtest] src:r-cran-pbkrtest: fai

Bug#1080988: src:r-cran-pbkrtest: fails to migrate to testing for too long: new Build-Depends not ready to migrate

Source: r-cran-pbkrtest Version: 0.5.2-2 Severity: serious Control: close -1 0.5.3-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 day

Processed: src:pageedit: fails to migrate to testing for too long: Build-Depends not available on mips64el

Processing control commands: > close -1 2.2.0+dfsg-1 Bug #1080987 [src:pageedit] src:pageedit: fails to migrate to testing for too long: Build-Depends not available on mips64el Marked as fixed in versions pageedit/2.2.0+dfsg-1. Bug #1080987 [src:pageedit] src:pageedit: fails to migrate to testing

Bug#1080987: src:pageedit: fails to migrate to testing for too long: Build-Depends not available on mips64el

Source: pageedit Version: 2.0.0+dfsg-1 Severity: serious Control: close -1 2.2.0+dfsg-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30

Processed: src:sigil: fails to migrate to testing for too long: Build-Depends not available on mips64el

Processing control commands: > close -1 2.2.1+dfsg-1 Bug #1080986 [src:sigil] src:sigil: fails to migrate to testing for too long: Build-Depends not available on mips64el Marked as fixed in versions sigil/2.2.1+dfsg-1. Bug #1080986 [src:sigil] src:sigil: fails to migrate to testing for too long:

Bug#1080986: src:sigil: fails to migrate to testing for too long: Build-Depends not available on mips64el

Source: sigil Version: 2.0.1+dfsg1-1 Severity: serious Control: close -1 2.2.1+dfsg-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 da

Processed: set severity

Processing commands for cont...@bugs.debian.org: > severity 1074781 serious Bug #1074781 [request-tracker5] request-tracker5/4: tests occasionally fail in CI Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1074781: https

Bug#1079763: marked as pending in python-svg.path

Control: tag -1 pending Hello, Bug #1079763 in python-svg.path 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-svg.path/-/commit/558

Processed: Bug#1079763 marked as pending in python-svg.path

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

Bug#1080959: marked as done (Does not support PostgreSQL 17)

Your message dated Fri, 06 Sep 2024 12:22:43 + with message-id and subject line Bug#1080959: fixed in pygresql 1:6.0.1-2 has caused the Debian Bug report #1080959, regarding Does not support PostgreSQL 17 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: Re: vstream-client: ftbfs with GCC-14

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

Bug#1075628: vstream-client: ftbfs with GCC-14

Package: vstream-client Version: 1.2-7 Followup-For: Bug #1075628 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu oracular ubuntu-patch Control: tags -1 patch Dear Maintainer, In Ubuntu, the attached patch was applied to fix the implicit declarations. * d/p: fix implicit declaratio

Processed: Bug#1079499 marked as pending in gjs

Processing control commands: > tag -1 pending Bug #1079499 [src:gjs] gjs: autopkgtest regression in experimental: cannot find typelib for GjsTestTools, Regress, etc. Added tag(s) pending. -- 1079499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079499 Debian Bug Tracking System Contact ow

Bug#1079499: marked as pending in gjs

Control: tag -1 pending Hello, Bug #1079499 in gjs 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/gnome-team/gjs/-/commit/49026d25724bd476b95e682895401bcd37bbf

Bug#1031046: Backport to bookworm

Hi all, I was wondering, what is the current maintenance status of Asterisk on Debian? I see that there are packages published on unstable, but the current version has a reported security vulnerability (CVE-2024-42365 ) since August 1

Bug#1080220: FTBFS: error: invalid command 'test'

Uploaded with 10 day delay, as mentioned. best /Andreas gus...@debian.org

Bug#1071119: snapd: move files to /usr for DEP17

> Wiadomość napisana przez Michael Biebl w dniu 3 wrz 2024, > o godz. 16:51: > > Control: tags -1 + > Am 03.09.24 um 15:19 schrieb Zygmunt Krynicki: > >> If you have time do NMU, I will unclude the changes in the next upstream >> release. Apologies for dropping the ball on this. > > I'm ha