Bug#1070492: mixxx: Tries to use the network during build

Hi, Am 04.07.2024 08:01, schrieb Gianfranco Costamagna: Also this patch is needed to adapt build dependencies with the t64 renamed ones diff -Nru mixxx-2.4.0+dfsg/debian/control mixxx-2.4.0+dfsg/debian/control --- mixxx-2.4.0+dfsg/debian/control 2024-03-12 00:14:18.0 +0100 +++ mi

Bug#1073423: url-normalize: diff for NMU version 1.4.3-3.1

Dear maintainer, I've prepared an NMU for url-normalize (versioned as 1.4.3-3.1) and uploaded. Here is the nmudiff. I did broke this package in a very indirrect way by uploading urrlib3 2.x Before this upload, python3-six was pulled in by this long and unexpected dependency chain: -> python3-py

Bug#1070492: mixxx: Tries to use the network during build

Hello, looks like we need an additional build dependency currently in new queue https://ftp-master.debian.org/new/libdjinterop_0.21.0+ds-1.html when that library is not found, the system tries to build from source by downloading it. Also this patch is needed to adapt build dependencies with the

Bug#1071355: In how far are several packages affected by bug #1071355 of maptools

Hi, there was a series of testing removals due to bug #1071355 of r-cran-maptools. Since maptools was removed from CRAN[1] we intend to remove this package. However, before doing so I would like to understand why packages like r-cran-factominer, r-cran-ggpubr, r-cran-vim, r-cran-systemfit, r-cra

Bug#1073423: marked as done (url-normalize: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

Your message dated Thu, 04 Jul 2024 05:42:12 + with message-id and subject line Bug#1073423: fixed in url-normalize 1.4.3-3.1 has caused the Debian Bug report #1073423, regarding url-normalize: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned

Bug#1074602: marked as done (xz-utils versioned dependency on liblzma5 is too weak)

Your message dated Thu, 04 Jul 2024 05:43:48 + with message-id and subject line Bug#1074602: fixed in xz-utils 5.6.2-2 has caused the Debian Bug report #1074602, regarding xz-utils versioned dependency on liblzma5 is too weak to be marked as done. This means that you claim that the problem ha

Bug#1073107: marked as done (tools-namespace-clojure: replace to-be-removed markdown build-dependency)

Your message dated Thu, 04 Jul 2024 05:41:52 + with message-id and subject line Bug#1073107: fixed in tools-namespace-clojure 1.3.0-2 has caused the Debian Bug report #1073107, regarding tools-namespace-clojure: replace to-be-removed markdown build-dependency to be marked as done. This means

Bug#1073106: marked as done (swarm-cluster: replace to-be-removed markdown build-dependency)

Your message dated Thu, 04 Jul 2024 05:40:20 + with message-id and subject line Bug#1073106: fixed in swarm-cluster 3.1.5+dfsg-2 has caused the Debian Bug report #1073106, regarding swarm-cluster: replace to-be-removed markdown build-dependency to be marked as done. This means that you claim

Bug#1074754: marked as done (rust-breezyshim: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101)

Your message dated Thu, 04 Jul 2024 05:37:37 + with message-id and subject line Bug#1074754: fixed in rust-pyo3-filelike 0.2.0-2 has caused the Debian Bug report #1074754, regarding rust-breezyshim: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101 to be mark

Bug#1074701: marked as done (rust-pyo3-filelike: FTBFS: make: *** [debian/rules:3: clean] Error 25)

Your message dated Thu, 04 Jul 2024 05:37:37 + with message-id and subject line Bug#1074701: fixed in rust-pyo3-filelike 0.2.0-2 has caused the Debian Bug report #1074701, regarding rust-pyo3-filelike: FTBFS: make: *** [debian/rules:3: clean] Error 25 to be marked as done. This means that you

Bug#1073152: marked as done (ruby-xmlrpc 0.3.3-1 has a file conflict with conserver-client)

Your message dated Thu, 04 Jul 2024 05:36:19 + with message-id and subject line Bug#1073152: fixed in ruby-xmlrpc 0.3.3-2 has caused the Debian Bug report #1073152, regarding ruby-xmlrpc 0.3.3-1 has a file conflict with conserver-client to be marked as done. This means that you claim that the

Bug#1073244: marked as done (ruby-xmlrpc has an undeclared file conflict on /usr/bin/console)

Your message dated Thu, 04 Jul 2024 05:36:19 + with message-id and subject line Bug#1073244: fixed in ruby-xmlrpc 0.3.3-2 has caused the Debian Bug report #1073244, regarding ruby-xmlrpc has an undeclared file conflict on /usr/bin/console to be marked as done. This means that you claim that t

Bug#1073100: marked as done (math-combinatorics-clojure: replace to-be-removed markdown build-dependency)

Your message dated Thu, 04 Jul 2024 05:20:50 + with message-id and subject line Bug#1073100: fixed in math-combinatorics-clojure 0.1.4-2 has caused the Debian Bug report #1073100, regarding math-combinatorics-clojure: replace to-be-removed markdown build-dependency to be marked as done. This

Bug#1063648: marked as done (krb5: FTBFS on IPv6-only buildds: "Can't resolve hostname" in dh_auto_test)

Your message dated Thu, 04 Jul 2024 05:19:45 + with message-id and subject line Bug#1063648: fixed in krb5 1.21.3-2 has caused the Debian Bug report #1063648, regarding krb5: FTBFS on IPv6-only buildds: "Can't resolve hostname" in dh_auto_test to be marked as done. This means that you claim

Bug#1074529: Bug#1074529: r-cran-dimred: autopkgtest regression with r-base 4.4.1 (i386)

Hi Charles, Am Tue, Jul 02, 2024 at 08:29:13AM +0900 schrieb Charles Plessy: > > For what it is worth version 0.2.6 is in good standing at CRAN with tests > > using "r-release" (ie now 4.4.1) as well as "r-devel" and "r-oldrel", see > > https://cran.r-project.org/web/checks/check_results_dimRed.ht

Bug#1069621: rust-event-listener: no-default-features autopkgtest fails

Quoting Jonas Smedegaard (2024-06-18 22:58:59) > It seems these packages still need to be updated as well: Here is the current status: DONE in unstable: * async-fs * v2.1.2 accepts async-lock v2+3 in unstable * v2.1.2 succeeds build-time testsuite and autopkgtests in unstable * blocking *

Processed: reassign bug before closing.

Processing commands for cont...@bugs.debian.org: > reassign 1074754 rust-pyo3-filelike Bug #1074754 [src:rust-breezyshim] rust-breezyshim: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101 Bug reassigned from package 'src:rust-breezyshim' to 'rust-pyo3-filelike'.

Bug#1072708: openafs: src/rx[gen] contains SUN RPC code under the original license

On Thu, Jul 04, 2024 at 12:23:11AM +0200, Bastian Germann wrote: > Am 03.07.24 um 23:56 schrieb Benjamin Kaduk: > > On Wed, Jul 03, 2024 at 11:27:50PM +0200, Bastian Germann wrote: > > > Am 03.07.24 um 05:23 schrieb Benjamin Kaduk: > > > > I do not see how it would be possible to replace this code

Bug#1072708: openafs: src/rx[gen] contains SUN RPC code under the original license

Am 04.07.24 um 00:28 schrieb Benjamin Kaduk: Sounds like we might want to add this bug to the 'blocks' list for that one, then? Then you should change its title, too.

Bug#1072708: openafs: src/rx[gen] contains SUN RPC code under the original license

Am 03.07.24 um 23:56 schrieb Benjamin Kaduk: On Wed, Jul 03, 2024 at 11:27:50PM +0200, Bastian Germann wrote: Am 03.07.24 um 05:23 schrieb Benjamin Kaduk: I do not see how it would be possible to replace this code in Debian before upstream can do so; this code is a core part of the functionalit

Bug#1072708: openafs: src/rx[gen] contains SUN RPC code under the original license

On Wed, Jul 03, 2024 at 11:27:50PM +0200, Bastian Germann wrote: > Am 03.07.24 um 05:23 schrieb Benjamin Kaduk: > > I do not see how it would be possible to replace this code in Debian before > > upstream can do so; this code is a core part of the functionality of the > > software and the files can

Bug#1072708: openafs: src/rx[gen] contains SUN RPC code under the original license

Am 03.07.24 um 05:23 schrieb Benjamin Kaduk: I do not see how it would be possible to replace this code in Debian before upstream can do so; this code is a core part of the functionality of the software and the files cannot be relicensed without the permission of all copyright holders. Upstream

Processed: znc: CVE-2024-39844

Processing control commands: > found -1 1.8.2-2 Bug #1075729 [src:znc] znc: CVE-2024-39844 Marked as found in versions znc/1.8.2-2. > found -1 1.8.2-3.1 Bug #1075729 [src:znc] znc: CVE-2024-39844 Marked as found in versions znc/1.8.2-3.1. > fixed -1 1.8.2-2+deb11u1 Bug #1075729 [src:znc] znc: CVE-

Bug#1075729: znc: CVE-2024-39844

Source: znc Version: 1.9.0-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 1.8.2-2 Control: found -1 1.8.2-3.1 Control: fixed -1 1.8.2-2+deb11u1 Control: fixed -1 1.8.2-3.1+deb12u1 Hi, The followi

Bug#1005961: nq,fq: trying to overwrite '/usr/bin/fq', which is also in package nq 0.3.1-4

Stephen Gelman writes: > Great, that would be perfect if you’re willing to do so! Just let me know > when that’s done and I can work with the nq debian maintainer to get that > uploaded. nq 1.0 has been release without conflicting names. -- Leah Neukirchenhttps://leahneukirchen.org

Bug#1075603: debugpy: incompatible with new pydevd

On Wed, Jul 03, 2024 at 02:52:00PM +0200, Gianfranco Costamagna wrote: > Source: debugpy > Version: 1.8.0+ds-4 > Severity: serious > > Hello, the debugpy can't build anymore from source > sbuild-build-depends-main-dummy : Depends: python3-pydevd (< 2.11) but > 3.1.0+ds-2 is to be installed > >

Processed: Re: Bug#1074633: qt6-base: upgrading libqt6core6t64 removes qpdfview and wireshark instead of upgrading them

Processing control commands: > reassign -1 apt Bug #1074633 [src:qt6-base] qt6-base: upgrading libqt6core6t64 removes qpdfview and wireshark instead of upgrading them Bug reassigned from package 'src:qt6-base' to 'apt'. No longer marked as found in versions qt6-base/6.6.2+dfsg-8. Ignoring request

Bug#1074633: qt6-base: upgrading libqt6core6t64 removes qpdfview and wireshark instead of upgrading them

Control: reassign -1 apt Control: retitle -1 When installing a package, apt should always upgrade rather than remove packages to satisfy dependencies Control: severity -1 normal Control: found -1 2.6.1 Control: found -1 2.9.5 Control: found -1 2.9.6 Note: In the initial test, I had done "apt inst

debian-bugs-rc@lists.debian.org

Hi Patrick, I do not want to put too much burden on the Qt/KDE team. I've seen in the past weeks Qt6, then KF6 and now Plasma6 steadily being packaged and uploaded into experimental, making it easier and easier for me to test the plasma-mobile_6.x packaging. I know it's a big effort, so big th

Bug#1073107: marked as pending in tools-namespace-clojure

Control: tag -1 pending Hello, Bug #1073107 in tools-namespace-clojure 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/clojure-team/tools-namespace-clojure/-/co

Processed: Bug#1073107 marked as pending in tools-namespace-clojure

Processing control commands: > tag -1 pending Bug #1073107 [src:tools-namespace-clojure] tools-namespace-clojure: replace to-be-removed markdown build-dependency Added tag(s) pending. -- 1073107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073107 Debian Bug Tracking System Contact ow...@

Bug#1073191: marked as done (awscli: ImportError: cannot import name DEFAULT_CIPHERS from urllib3.util.ssl_)

Your message dated Wed, 03 Jul 2024 17:34:57 + with message-id and subject line Bug#1073189: fixed in awscli 2.17.3-1 has caused the Debian Bug report #1073189, regarding awscli: ImportError: cannot import name DEFAULT_CIPHERS from urllib3.util.ssl_ to be marked as done. This means that you

Bug#1073178: marked as done (awscli: please update awsci and/or botocore to support urllib3 2.x)

Your message dated Wed, 03 Jul 2024 17:34:57 + with message-id and subject line Bug#1073189: fixed in awscli 2.17.3-1 has caused the Debian Bug report #1073189, regarding awscli: please update awsci and/or botocore to support urllib3 2.x to be marked as done. This means that you claim that th

Bug#1073189: marked as done (awscli: ImportError: cannot import name DEFAULT_CIPHERS from urllib3.util.ssl_)

Your message dated Wed, 03 Jul 2024 17:34:57 + with message-id and subject line Bug#1073189: fixed in awscli 2.17.3-1 has caused the Debian Bug report #1073189, regarding awscli: ImportError: cannot import name DEFAULT_CIPHERS from urllib3.util.ssl_ to be marked as done. This means that you

Bug#1064307: marked as done (awscli ftbfs with Python 3.12 as the default)

Your message dated Wed, 03 Jul 2024 17:34:57 + with message-id and subject line Bug#1064307: fixed in awscli 2.17.3-1 has caused the Debian Bug report #1064307, regarding awscli ftbfs with Python 3.12 as the default to be marked as done. This means that you claim that the problem has been dea

Processed: Bug#1064307 marked as pending in awscli

Processing control commands: > tag -1 pending Bug #1064307 [src:awscli] awscli ftbfs with Python 3.12 as the default Added tag(s) pending. -- 1064307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug#1073189 marked as pending in awscli

Processing control commands: > tag -1 pending Bug #1073189 [src:awscli] awscli: ImportError: cannot import name DEFAULT_CIPHERS from urllib3.util.ssl_ Bug #1073178 [src:awscli] awscli: please update awsci and/or botocore to support urllib3 2.x Bug #1073191 [src:awscli] awscli: ImportError: canno

Bug#1073189: marked as pending in awscli

Control: tag -1 pending Hello, Bug #1073189 in awscli 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/cloud-team/awscli/-/commit/7f5dd73b698a9fac17aea202f8ffbfd

Bug#1064307: marked as pending in awscli

Control: tag -1 pending Hello, Bug #1064307 in awscli 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/cloud-team/awscli/-/commit/7f5dd73b698a9fac17aea202f8ffbfd

Bug#1074633: qt6-base: upgrading libqt6core6t64 removes qpdfview and wireshark instead of upgrading them

Hej Vincent, Am Mittwoch, 3. Juli 2024, 01:02:28 CEST schrieb Vincent Lefevre: [...] > In particular, "apt install libqt6core6t64" wants to remove > qt6-wayland, but if I try "apt install libqt6core6t64 qt6-wayland", > then the upgrade is fine. So there seems to be really something > wrong with th

Bug#1071523: r-cran-spatstat.geom: autopkgtest regression in testing

Hi Andreas On Wed, 3 Jul 2024 at 05:18, Andreas Tille wrote: > Well, sure. But our tooling will add this for the next upstream version > again and if the problem is not solved otherwise it will re-appear. I > will upload this change but I would prefer understanding the issue and > provide a rea

Bug#1073090: marked as done (alter-sequence-alignment: replace to-be-removed markdown build-dependency)

Your message dated Wed, 3 Jul 2024 18:16:28 +0200 with message-id and subject line Re: alter-sequence-alignment: replace to-be-removed markdown build-dependency has caused the Debian Bug report #1073090, regarding alter-sequence-alignment: replace to-be-removed markdown build-dependency to be ma

Bug#1073100: marked as pending in math-combinatorics-clojure

Control: tag -1 pending Hello, Bug #1073100 in math-combinatorics-clojure 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/clojure-team/math-combinatorics-clojur

Processed: Bug#1073100 marked as pending in math-combinatorics-clojure

Processing control commands: > tag -1 pending Bug #1073100 [src:math-combinatorics-clojure] math-combinatorics-clojure: replace to-be-removed markdown build-dependency Added tag(s) pending. -- 1073100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073100 Debian Bug Tracking System Contact

Bug#1060532: marked as done (rust-zram-generator: Please switch Build-Depends to systemd-dev)

Your message dated Wed, 03 Jul 2024 13:21:24 + with message-id and subject line Bug#1060532: fixed in rust-zram-generator 1.1.2-4 has caused the Debian Bug report #1060532, regarding rust-zram-generator: Please switch Build-Depends to systemd-dev to be marked as done. This means that you clai

Bug#1073205: docker-compose: new python3-requests dependency brokes docker-compose

> This appears to be a duplicate of bug #1073196 in python3-docker. I was > able to reproduce this problem with version 6.1.3-0.1 of that package > but can no longer reproduce after updating that package to 6.1.3-0.2. I can confirm that the upgrade of python3-docker to version 6.1.3-0.2 fixes this

Bug#1075712: graphite-carbon: daemon does not start

Package: graphite-carbon Version: 1.1.7-1.2 Severity: grave Tags: patch upstream Justification: renders package unusable Dear Maintainer, The daemon fails to start with the following traceback. -- systemd[1]: Starting carbon-cache.service - Graphite Carbon Cache... carbon-cache[262]: Traceback (

Bug#1075603: debugpy: incompatible with new pydevd

Source: debugpy Version: 1.8.0+ds-4 Severity: serious Hello, the debugpy can't build anymore from source sbuild-build-depends-main-dummy : Depends: python3-pydevd (< 2.11) but 3.1.0+ds-2 is to be installed Looks like 1.8.2 is out, but I'm unsure about the compatibility with pydevd 3.1.0 G.

Bug#1074797: FTBFS on i386, armel, armhf

Source: bcachefs-tools Version: 1:1.9.1-1 Severity: serious bcachefs-tools 1:1.7.0-1 & 1:1.9.1-1 FTBFS on i386, while 1:1.9.1-1 also FTBFS on armel and armhf. As a result, bcachefs-tools has not reentered testing since it was removed back in April. The 1:1.9.1-1 upload happened in the meantime ab

Bug#1074796: gnome-shell: Silently applies pending package updates on shutdown

Package: gnome-shell Version: 43.9-0+deb12u2 Severity: serious [This bug is probably misfiled, I have no idea which GNOME component is responsible for the actual behaviour so this is a guess based on the fact that I interact with the UI to trigger it.] When I select "Power off" from the power men

Bug#1073105: marked as done (ssake: replace to-be-removed markdown build-dependency)

Your message dated Wed, 03 Jul 2024 12:04:18 + with message-id and subject line Bug#1073105: fixed in ssake 4.0.1-2 has caused the Debian Bug report #1073105, regarding ssake: replace to-be-removed markdown build-dependency to be marked as done. This means that you claim that the problem has

Bug#1071769: marked as done (golang-github-google-cel-go: FTBFS: FAIL: TestTimestampGetDayOfMonth)

Your message dated Wed, 03 Jul 2024 11:19:41 + with message-id and subject line Bug#1071769: fixed in golang-github-google-cel-go 0.12.5+ds-6 has caused the Debian Bug report #1071769, regarding golang-github-google-cel-go: FTBFS: FAIL: TestTimestampGetDayOfMonth to be marked as done. This me

Processed: Re: golang-github-google-cel-go: FTBFS: panic: interface conversion: ref.Val is *types.Err, not types.Bool

Processing commands for cont...@bugs.debian.org: > retitle 1071769 golang-github-google-cel-go: FTBFS: FAIL: > TestTimestampGetDayOfMonth Bug #1071769 {Done: Reinhard Tartler } [src:golang-github-google-cel-go] golang-github-google-cel-go: FTBFS: panic: interface conversion: ref.Val is *types.E

Bug#1071769: golang-github-google-cel-go: FTBFS: panic: interface conversion: ref.Val is *types.Err, not types.Bool

retitle 1071769 golang-github-google-cel-go: FTBFS: FAIL: TestTimestampGetDayOfMonth thanks I'm putting the test which failed in the subject to avoid confusion. Thanks.

Bug#1071769: golang-github-google-cel-go: FTBFS: panic: interface conversion: ref.Val is *types.Err, not types.Bool

Ok, I've just fixed this myself in 0.12.5+ds-6 via team upload. The problem was that tzdata is not build-essential. While some autobuilders still have it installed by default, the default debootstrap in trixie/sid does not install it anymore in the buildd profile, so it is just a matter of time t

Bug#1074691: marked as done (virtnbdbackup: FTBFS: ModuleNotFoundError: No module named 'libnbdmod')

Your message dated Wed, 03 Jul 2024 11:04:14 + with message-id and subject line Bug#1074691: fixed in virtnbdbackup 2.10-2 has caused the Debian Bug report #1074691, regarding virtnbdbackup: FTBFS: ModuleNotFoundError: No module named 'libnbdmod' to be marked as done. This means that you clai

Bug#1074633: qt6-base: upgrading libqt6core6t64 removes qpdfview and wireshark instead of upgrading them

In case this can be useful, I've attached the output of apt-get install libqt6core6t64 -s -o Debug::pkgProblemResolver=true -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC

Bug#1074430: adminer: CVE-2023-45196 CVE-2023-45195

Hi, > > It seems adminer is dead upstream and adminerevo picked up development, > > so most likely Debian should follow the new upstream? > > I have not been able to find[1] a sponsor for adminerevo although the > packaging > as a separate source package is done. > > I can easily switch src:adm

Processed: golang-github-google-cel-go: FTBFS: panic: interface conversion: ref.Val is *types.Err, not types.Bool

Processing commands for cont...@bugs.debian.org: > found 1071769 0.12.5+ds-5 Bug #1071769 {Done: Reinhard Tartler } [src:golang-github-google-cel-go] golang-github-google-cel-go: FTBFS: panic: interface conversion: ref.Val is *types.Err, not types.Bool Marked as found in versions golang-github-g

Bug#1071769: golang-github-google-cel-go: FTBFS: panic: interface conversion: ref.Val is *types.Err, not types.Bool

found 1071769 0.12.5+ds-5 thanks Hi. For some reason, this is still happening in the current version, see attach. It also fails in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-google-cel-go.html If you can't reproduce it, my offer for a

Bug#1074633: qt6-base: upgrading libqt6core6t64 removes qpdfview and wireshark instead of upgrading them

Note that as noted in its changelog, there was a regression in apt 2.9.5. However, apt 2.9.6 yields the same behavior. And to be sure that there wasn't any other regression, I downgraded apt to stable and installed libapt-pkg6.0 from stable (replacing the libapt-pkg6.0t64 package from the t64 trans

Bug#1074686: marked as done (starjava-datanode: FTBFS: [javac] /<>/src/main/uk/ac/starlink/oldfits/MappedFile.java:42: error: MappedFile is not abstract and does not override abstract

Your message dated Wed, 03 Jul 2024 09:21:50 + with message-id and subject line Bug#1074686: fixed in starjava-datanode 1.0+2023.01.18-3 has caused the Debian Bug report #1074686, regarding starjava-datanode: FTBFS: [javac] /<>/src/main/uk/ac/starlink/oldfits/MappedFile.java:42: error: M

Bug#1074224: marked as done (crossfire FTBFS with Python 3.12 as default)

Your message dated Wed, 03 Jul 2024 09:19:02 + with message-id and subject line Bug#1074224: fixed in crossfire 1.75.0-7 has caused the Debian Bug report #1074224, regarding crossfire FTBFS with Python 3.12 as default to be marked as done. This means that you claim that the problem has been d

Bug#1074663: marked as done (skyview: FTBFS: ./skyview/survey/HipsImage.java:385: error: cannot find symbol)

Your message dated Wed, 03 Jul 2024 08:28:49 + with message-id and subject line Bug#1074663: fixed in skyview 3.5.7+repack-3 has caused the Debian Bug report #1074663, regarding skyview: FTBFS: ./skyview/survey/HipsImage.java:385: error: cannot find symbol to be marked as done. This means th

Bug#1071523: marked as done (r-cran-spatstat.geom: autopkgtest regression in testing)

Your message dated Wed, 03 Jul 2024 08:28:10 + with message-id and subject line Bug#1071523: fixed in r-cran-spatstat.geom 3.2-9-2 has caused the Debian Bug report #1071523, regarding r-cran-spatstat.geom: autopkgtest regression in testing to be marked as done. This means that you claim that