Bug#1057621: valgrind should not drop valgrind-dbg

Hi Chris, It's a bit moot as the bug is already solved On 13-04-2025 23:06, Chris Hofstaedtler wrote: > I think you are implying a finer detail that is lost on me. Let me try again. The other bug is about valgrind Recommends a package that doesn't exist. That's clearly RC, it can be fixed

Bug#1057621: valgrind should not drop valgrind-dbg

Hi Chris, It's a bit moot as the bug is already solved On 13-04-2025 23:06, Chris Hofstaedtler wrote: > I think you are implying a finer detail that is lost on me. Let me try again. The other bug is about valgrind Recommends a package that doesn't exist. That's clearly RC, it can be fixed

Bug#1057621: valgrind should not drop valgrind-dbg

Hi zeha, On 13-04-2025 11:23, Chris Hofstaedtler wrote: Do you agree with the submitter of this bug that the lack of debug symbols available via Recommends is a release critical bug? I'm not an experienced valgrind user, but with my Release Team member hat on, this looks a bit exaggerated. (I

Re: MBF: Packages which break with nocheck

Hi, On 13-04-2025 17:12, Helmut Grohne wrote: That said, Emilio explicitly asked them not to be filed as rc on irc. That feels like RT is not internally consistent here. How about filing them as rc now and tagging them trixie-ignore later if we deem the effort too big? What I think he means,

Re: MBF: Packages which break with nocheck

Hi, On 13-04-2025 17:12, Helmut Grohne wrote: That said, Emilio explicitly asked them not to be filed as rc on irc. That feels like RT is not internally consistent here. How about filing them as rc now and tagging them trixie-ignore later if we deem the effort too big? What I think he means,

Bug#1057621: valgrind should not drop valgrind-dbg

Hi zeha, On 13-04-2025 11:23, Chris Hofstaedtler wrote: Do you agree with the submitter of this bug that the lack of debug symbols available via Recommends is a release critical bug? I'm not an experienced valgrind user, but with my Release Team member hat on, this looks a bit exaggerated. (I

Bug#1084074: Bug#1084072: rocm-compilersupport: Please upgrade build-dep to llvm/clang 18 or 19

Control: tags -1 trixie-ignore Hi all, On Fri, 6 Dec 2024 11:36:22 +0100 Emilio Pozuelo Monfort wrote: Thanks for the update. After your email, I asked ftp-masters about rocm-llvm, and it got accepted. With that done, how's the update to 6.1 coming along? Do you think it can happen soon? I

Bug#1084074: Bug#1084072: rocm-compilersupport: Please upgrade build-dep to llvm/clang 18 or 19

Control: tags -1 trixie-ignore Hi all, On Fri, 6 Dec 2024 11:36:22 +0100 Emilio Pozuelo Monfort wrote: Thanks for the update. After your email, I asked ftp-masters about rocm-llvm, and it got accepted. With that done, how's the update to 6.1 coming along? Do you think it can happen soon? I

Bug#1087869: rocm-hipamd: autopkgtest regression due to new CMake deprecation warning

e35bd44d61766251efc6bbd011634769fe464805 Mon Sep 17 00:00:00 2001 From: Paul Gevers Date: Sat, 12 Apr 2025 12:44:31 +0200 Subject: [PATCH 1/2] tests: allow deprecation warnings via allow-stderr restriction Closes: #1087869 --- debian/tests/control | 2 +- 1 file changed, 1 insertion(+), 1 deletion

Bug#1087869: rocm-hipamd: autopkgtest regression due to new CMake deprecation warning

e35bd44d61766251efc6bbd011634769fe464805 Mon Sep 17 00:00:00 2001 From: Paul Gevers Date: Sat, 12 Apr 2025 12:44:31 +0200 Subject: [PATCH 1/2] tests: allow deprecation warnings via allow-stderr restriction Closes: #1087869 --- debian/tests/control | 2 +- 1 file changed, 1 insertion(+), 1 deletion

Re: Help to understand version tracking

Hi Santiago, On 12-04-2025 17:48, Santiago Vila wrote: I'd like to know if there is any special way to report a bug so that version tracking works. See this for example: https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=uglifyjs Normally a bug also shows the version history of in the top rig

Bug#1086645: dbus-test-runner: autopkgtest regression: test depends on obsolete package bustle

Hi, On 11-04-2025 15:19, Jeremy Bícha wrote: We have now uploaded bustle to Unstable. I didn't notice that bustle wasn't in Testing so I did another upload today. Please consider hinting bustle in faster since I'm not sure whether there are 5 days left before the Soft Freeze. Note that bustle i

Bug#1086645: dbus-test-runner: autopkgtest regression: test depends on obsolete package bustle

Hi, On 11-04-2025 15:19, Jeremy Bícha wrote: We have now uploaded bustle to Unstable. I didn't notice that bustle wasn't in Testing so I did another upload today. Please consider hinting bustle in faster since I'm not sure whether there are 5 days left before the Soft Freeze. Note that bustle i

Bug#1089276: win32-loader: FTBFS with make 4.4.1

Hi Holger, On 12-04-2025 13:31, Holger Wansing wrote: It has already been removed from the d-i builds 2 years ago with And what about e.g. https://salsa.debian.org/installer-team/debian-install

Bug#1089276: win32-loader: FTBFS with make 4.4.1

Hi Holger, On 12-04-2025 13:31, Holger Wansing wrote: It has already been removed from the d-i builds 2 years ago with And what about e.g. https://salsa.debian.org/installer-team/debian-install

Bug#1089276: win32-loader: FTBFS with make 4.4.1

Hi Holger, On 12-04-2025 13:31, Holger Wansing wrote: It has already been removed from the d-i builds 2 years ago with And what about e.g. https://salsa.debian.org/installer-team/debian-install

Bug#1102724: RM: win32-loader -- RoQA; not considered worthwhile to maintain further

Package: ftp.debian.org Severity: normal Tags: moreinfo X-Debbugs-Cc: win32-loa...@packages.debian.org Control: affects -1 + src:win32-loader User: ftp.debian@packages.debian.org Usertags: remove Hi ftp-master, [Added the moreinfo tag as d-i needs adaptation first and because of the followi

Bug#1102724: RM: win32-loader -- RoQA; not considered worthwhile to maintain further

Package: ftp.debian.org Severity: normal Tags: moreinfo X-Debbugs-Cc: win32-loa...@packages.debian.org Control: affects -1 + src:win32-loader User: ftp.debian@packages.debian.org Usertags: remove Hi ftp-master, [Added the moreinfo tag as d-i needs adaptation first and because of the followi

Bug#1089276: win32-loader: FTBFS with make 4.4.1

Hi, On 12-04-2025 12:54, Cyril Brulebois wrote: Paul Gevers (2025-04-12): Do you speak on behalf of all maintainers here? Do you want me to find out what needs to be done to remove win32-loader from trixie? I'm not aware of anyone wanting to keep win32-loader around, so yeah, looking

Bug#1089276: win32-loader: FTBFS with make 4.4.1

Hi, On 12-04-2025 12:54, Cyril Brulebois wrote: Paul Gevers (2025-04-12): Do you speak on behalf of all maintainers here? Do you want me to find out what needs to be done to remove win32-loader from trixie? I'm not aware of anyone wanting to keep win32-loader around, so yeah, looking

Bug#1089276: win32-loader: FTBFS with make 4.4.1

Hi, On 12-04-2025 12:54, Cyril Brulebois wrote: Paul Gevers (2025-04-12): Do you speak on behalf of all maintainers here? Do you want me to find out what needs to be done to remove win32-loader from trixie? I'm not aware of anyone wanting to keep win32-loader around, so yeah, looking

Bug#1102599: Is a self-contained upgrade considered large/disruptive? (was Re: Bug#1102599: rust-tonic: please upgrade to 0.13 with upcoming upgrade of rust-prost 0.13)

Hi Blair, On 11-04-2025 17:14, Blair Noctis wrote: So: If all packages affected are handled ("self-contained"), This is indeed good. the blast radius is rather small, In transition context, we generally consider "small" when numbers are in the low single digit. Otherwise we'd want to be

Bug#1089276: win32-loader: FTBFS with make 4.4.1

Hi, On 27-03-2025 19:57, Holger Wansing wrote: Am 27. März 2025 15:25:09 MEZ schrieb Paul Gevers : I've seen multiple times that win32-loader was mentioned during a stable point release IRC discussion and I am under the impression that "we" want to remove it at some point. I

Re: Is a self-contained upgrade considered large/disruptive? (was Re: Bug#1102599: rust-tonic: please upgrade to 0.13 with upcoming upgrade of rust-prost 0.13)

Hi Blair, On 11-04-2025 17:14, Blair Noctis wrote: So: If all packages affected are handled ("self-contained"), This is indeed good. the blast radius is rather small, In transition context, we generally consider "small" when numbers are in the low single digit. Otherwise we'd want to be

Bug#1089276: win32-loader: FTBFS with make 4.4.1

Hi, On 27-03-2025 19:57, Holger Wansing wrote: Am 27. März 2025 15:25:09 MEZ schrieb Paul Gevers : I've seen multiple times that win32-loader was mentioned during a stable point release IRC discussion and I am under the impression that "we" want to remove it at some point. I

Bug#1089276: win32-loader: FTBFS with make 4.4.1

Hi, On 27-03-2025 19:57, Holger Wansing wrote: Am 27. März 2025 15:25:09 MEZ schrieb Paul Gevers : I've seen multiple times that win32-loader was mentioned during a stable point release IRC discussion and I am under the impression that "we" want to remove it at some point. I

Re: testing migration for Essential packages

Hi, On 12-04-2025 10:58, Bastian Blank wrote: On Sat, Apr 12, 2025 at 09:56:02AM +0200, Paul Gevers wrote: What we can already do is ask packages that depend on Essential packages, to add a hint-testsuite-triggers [1] test. That way we would at least know which packages to test for. People

Bug#1099499: requires pyarrow

On Tue, 4 Mar 2025 07:25:13 +0100 Daniel Baumann wrote: this is a reminder/blocker bug, that harlequin depends on pyarrow which isn't yet in Debian.. but I'm working on it. Do you mean it depends on it, but it doesn't Depends on it? I don't see it being blocked by a dependency not in testing.

Bug#1102694: src:harlequin-odbc: fails to migrate to testing for too long

Source: harlequin-odbc Version: 0.3.0-1 Severity: serious Control: close -1 0.3.1-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

Bug#1102696: src:petsc4py: fails to migrate to testing for too long

Source: petsc4py Version: 3.22.3-1 Severity: serious Control: close -1 3.22.4-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

Bug#1102697: src:sundials: fails to migrate to testing for too long

Source: sundials Version: 7.1.1+dfsg1-8 Severity: serious Control: close -1 7.1.1+dfsg1-10 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

Bug#1102697: src:sundials: fails to migrate to testing for too long

Source: sundials Version: 7.1.1+dfsg1-8 Severity: serious Control: close -1 7.1.1+dfsg1-10 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

Bug#1099499: requires pyarrow

On Tue, 4 Mar 2025 07:25:13 +0100 Daniel Baumann wrote: this is a reminder/blocker bug, that harlequin depends on pyarrow which isn't yet in Debian.. but I'm working on it. Do you mean it depends on it, but it doesn't Depends on it? I don't see it being blocked by a dependency not in testing.

Bug#1102696: src:petsc4py: fails to migrate to testing for too long

Source: petsc4py Version: 3.22.3-1 Severity: serious Control: close -1 3.22.4-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

Bug#1102697: src:sundials: fails to migrate to testing for too long

Source: sundials Version: 7.1.1+dfsg1-8 Severity: serious Control: close -1 7.1.1+dfsg1-10 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

Bug#1102695: src:harlequin-postgres: fails to migrate to testing for too long

Source: harlequin-postgres Version: 1.2.0-1 Severity: serious Control: close -1 1.2.0-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

Bug#1102694: src:harlequin-odbc: fails to migrate to testing for too long

Source: harlequin-odbc Version: 0.3.0-1 Severity: serious Control: close -1 0.3.1-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

Bug#1102695: src:harlequin-postgres: fails to migrate to testing for too long

Source: harlequin-postgres Version: 1.2.0-1 Severity: serious Control: close -1 1.2.0-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

Bug#1102696: src:petsc4py: fails to migrate to testing for too long

Source: petsc4py Version: 3.22.3-1 Severity: serious Control: close -1 3.22.4-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

Bug#1102693: src:frr: fails to migrate to testing for too long: FTBFS on s390x

Source: frr Version: 10.2.1-6 Severity: serious Control: close -1 10.3-1 Tags: sid trixie ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync X-Debbugs-CC: debian-s...@lists.debian.org User: debian-s...@lists.debian.org Usertags: s390x Dear maintainer(s), The Release Team co

Bug#1102693: src:frr: fails to migrate to testing for too long: FTBFS on s390x

Source: frr Version: 10.2.1-6 Severity: serious Control: close -1 10.3-1 Tags: sid trixie ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync X-Debbugs-CC: debian-s390@lists.debian.org User: debian-s390@lists.debian.org Usertags: s390x Dear maintainer(s), The Release Team co

Bug#1102693: src:frr: fails to migrate to testing for too long: FTBFS on s390x

Source: frr Version: 10.2.1-6 Severity: serious Control: close -1 10.3-1 Tags: sid trixie ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync X-Debbugs-CC: debian-s...@lists.debian.org User: debian-s...@lists.debian.org Usertags: s390x Dear maintainer(s), The Release Team co

Re: testing migration for Essential packages

Hi, On 12-04-2025 08:34, Marc Haber wrote: Otoh, Essential packages can break many other packages without having an explicit reverse dependency listed since they are assumed always present and since it's a bug to explicitly list a dependency on an Essential package. Conform 3.5: "Packages a

Bug#1102465: petsc: PETSc was configured with one MPICH/Open MPI mpi.h version but now appears to be compiling using an older version

Hi Drew, On Fri, 11 Apr 2025 12:23:45 +0200 Drew Parsons wrote: Two alternative actions could be taken. 1) We could remove upstream's mpich version check, as you suggested. I'm reluctant to take this step, however. Upstream is careful with their code, I imagine they put the version check there

Bug#1102465: petsc: PETSc was configured with one MPICH/Open MPI mpi.h version but now appears to be compiling using an older version

Hi Drew, On Fri, 11 Apr 2025 12:23:45 +0200 Drew Parsons wrote: Two alternative actions could be taken. 1) We could remove upstream's mpich version check, as you suggested. I'm reluctant to take this step, however. Upstream is careful with their code, I imagine they put the version check there

Bug#1102664: src:petsc: fails to migrate to testing for too long

Source: petsc Version: 3.22.3+dfsg1-1 Severity: serious Control: close -1 3.22.5+dfsg1-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

Bug#1102664: src:petsc: fails to migrate to testing for too long

Source: petsc Version: 3.22.3+dfsg1-1 Severity: serious Control: close -1 3.22.5+dfsg1-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

Bug#1102664: src:petsc: fails to migrate to testing for too long

Source: petsc Version: 3.22.3+dfsg1-1 Severity: serious Control: close -1 3.22.5+dfsg1-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

Bug#1084089: llvm-toolchain-17: do not release with trixie

Hi, On 10-04-2025 10:46, Paul Gevers wrote: On Sun, 23 Mar 2025 20:14:34 +0100 Sylvestre Ledru Do you want me to bump them? Hmm, we should have done that at least 3 months ago. I consider it a bit too late now as there are both key and non-key package involved. This reply had been

Bug#1086645: dbus-test-runner: autopkgtest regression: test depends on obsolete package bustle

Control: tags -1 patch pending Hi, On Sat, 2 Nov 2024 21:46:10 +0100 Paul Gevers wrote: Your package has an autopkgtest, great. However, it fails in testing, because on of the test dependencies is no longer available. The maintainer of bustle wants to remove the package, see bug #1084512

Bug#1102348: src:cl-closer-mop: fails to migrate to testing for too long

Source: cl-closer-mop Version: 2:20241031.git875f4b7-1 Severity: serious Control: close -1 2:20250303.git53221de-1 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between test

Bug#1102348: src:cl-closer-mop: fails to migrate to testing for too long

Source: cl-closer-mop Version: 2:20241031.git875f4b7-1 Severity: serious Control: close -1 2:20250303.git53221de-1 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between test

Bug#1102347: src:cl-nibbles: fails to migrate to testing for too long

Source: cl-nibbles Version: 20240607.gitc054c32-2 Severity: serious Control: close -1 20250305.gitc1ecd02-1 Tags: sid trixie pending 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 an

Bug#1102586: src:fonts-jetbrains-mono: fails to migrate to testing for too long

Source: fonts-jetbrains-mono Version: 2.304+ds-4 Severity: serious Control: close -1 2.304+ds-5 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

Bug#1102589: src:r-cran-broom.helpers: fails to migrate to testing for too long

Source: r-cran-broom.helpers Version: 1.14.0-3 Severity: serious Control: close -1 1.20.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

Bug#1102592: src:lsp-plugins: fails to migrate to testing for too long

Source: lsp-plugins Version: 1.2.16-1 Severity: serious Control: close -1 1.2.21-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

Bug#1102591: src:r-cran-units: fails to migrate to testing for too long

Source: r-cran-units Version: 0.8-5+dfsg-1 Severity: serious Control: close -1 0.8-7+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

Bug#1102588: src:golang-github-apptainer-container-library-client: fails to migrate to testing for too long

Source: golang-github-apptainer-container-library-client Version: 1.2.2-2 Severity: serious Control: close -1 1.4.10-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

Bug#1102592: src:lsp-plugins: fails to migrate to testing for too long

Source: lsp-plugins Version: 1.2.16-1 Severity: serious Control: close -1 1.2.21-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

Bug#1102590: src:r-cran-fansi: fails to migrate to testing for too long

Source: r-cran-fansi Version: 1.0.5-1 Severity: serious Control: close -1 1.0.6-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 a

Bug#1102590: src:r-cran-fansi: fails to migrate to testing for too long

Source: r-cran-fansi Version: 1.0.5-1 Severity: serious Control: close -1 1.0.6-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 a

Bug#1102591: src:r-cran-units: fails to migrate to testing for too long

Source: r-cran-units Version: 0.8-5+dfsg-1 Severity: serious Control: close -1 0.8-7+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

Bug#1102592: src:lsp-plugins: fails to migrate to testing for too long

Source: lsp-plugins Version: 1.2.16-1 Severity: serious Control: close -1 1.2.21-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

Bug#1102588: src:golang-github-apptainer-container-library-client: fails to migrate to testing for too long

Source: golang-github-apptainer-container-library-client Version: 1.2.2-2 Severity: serious Control: close -1 1.4.10-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

Bug#1102587: src:gitlabracadabra: fails to migrate to testing for too long

Source: gitlabracadabra Version: 2.5.1 Severity: serious Control: close -1 2.7.0 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

Bug#1102589: src:r-cran-broom.helpers: fails to migrate to testing for too long

Source: r-cran-broom.helpers Version: 1.14.0-3 Severity: serious Control: close -1 1.20.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

Bug#1102587: src:gitlabracadabra: fails to migrate to testing for too long

Source: gitlabracadabra Version: 2.5.1 Severity: serious Control: close -1 2.7.0 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

Bug#1102586: src:fonts-jetbrains-mono: fails to migrate to testing for too long

Source: fonts-jetbrains-mono Version: 2.304+ds-4 Severity: serious Control: close -1 2.304+ds-5 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

Bug#1102346: src:trivial-features: fails to migrate to testing for too long

Source: trivial-features Version: 20230607.gitd249a62-1 Severity: serious Control: close -1 20250129.git18a5cfa-1 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testi

Bug#1102345: src:r-cran-survminer: fails to migrate to testing for too long

Source: r-cran-survminer Version: 0.4.9+dfsg-1 Severity: serious Control: close -1 0.5.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

Bug#1102346: src:trivial-features: fails to migrate to testing for too long

Source: trivial-features Version: 20230607.gitd249a62-1 Severity: serious Control: close -1 20250129.git18a5cfa-1 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testi

Bug#1084512: Removal notice: obsolete

Hi Ilias, On Mon, 7 Oct 2024 16:49:28 +0300 Ilias Tsitsimpis wrote: I intend to remove this package: * It has no rev dependencies * It FTBFS with GHC 9.6 * It's not part of the latest Stackage LTS * The Haskell version is abandoned, and the project has been rewritten in Rust If you b

Bug#1057621: valgrind should not drop valgrind-dbg

Dear maintainer, On Wed, 06 Dec 2023 02:05:07 +0200 Adrian Bunk wrote: For the usual case where debug symbols are only used when debugging in a debugger this is no problem, but valgrind-dbg is (like libc6-dbg) an exception: Package: valgrind Recommends: valgrind-dbg, gdb https://sources.debia

Bug#1095863: release.debian.org: Raising the i386 baseline for Trixie to include SSE2/MMX

Hi, Sorry for the long wait, somehow I thought we replied. On 13-02-2025 17:32, Simon McVittie wrote: - Officially keep current baseline, intentionally violate the baseline in rustc (and maybe LLVM?) so that rustc produces working code, and have the release team announce that the resultin

Bug#1095863: release.debian.org: Raising the i386 baseline for Trixie to include SSE2/MMX

Hi, Sorry for the long wait, somehow I thought we replied. On 13-02-2025 17:32, Simon McVittie wrote: - Officially keep current baseline, intentionally violate the baseline in rustc (and maybe LLVM?) so that rustc produces working code, and have the release team announce that the resultin

Bug#1057621: valgrind should not drop valgrind-dbg

Dear maintainer, On Wed, 06 Dec 2023 02:05:07 +0200 Adrian Bunk wrote: For the usual case where debug symbols are only used when debugging in a debugger this is no problem, but valgrind-dbg is (like libc6-dbg) an exception: Package: valgrind Recommends: valgrind-dbg, gdb https://sources.debia

Bug#1086645: dbus-test-runner: autopkgtest regression: test depends on obsolete package bustle

Hi, On 10-04-2025 16:19, Paul Gevers wrote: On Sat, 2 Nov 2024 21:46:10 +0100 Paul Gevers wrote: Your package has an autopkgtest, great. However, it fails in testing, because on of the test dependencies is no longer available. The maintainer of bustle wants to remove the package, see bug

Bug#1086645: dbus-test-runner: autopkgtest regression: test depends on obsolete package bustle

Hi, On 10-04-2025 16:19, Paul Gevers wrote: On Sat, 2 Nov 2024 21:46:10 +0100 Paul Gevers wrote: Your package has an autopkgtest, great. However, it fails in testing, because on of the test dependencies is no longer available. The maintainer of bustle wants to remove the package, see bug

Bug#1086645: dbus-test-runner: autopkgtest regression: test depends on obsolete package bustle

Control: tags -1 patch pending Hi, On Sat, 2 Nov 2024 21:46:10 +0100 Paul Gevers wrote: Your package has an autopkgtest, great. However, it fails in testing, because on of the test dependencies is no longer available. The maintainer of bustle wants to remove the package, see bug #1084512

Bug#1084512: Removal notice: obsolete

Hi Ilias, On Mon, 7 Oct 2024 16:49:28 +0300 Ilias Tsitsimpis wrote: I intend to remove this package: * It has no rev dependencies * It FTBFS with GHC 9.6 * It's not part of the latest Stackage LTS * The Haskell version is abandoned, and the project has been rewritten in Rust If you b

Bug#1084512: Removal notice: obsolete

Hi Ilias, On Mon, 7 Oct 2024 16:49:28 +0300 Ilias Tsitsimpis wrote: I intend to remove this package: * It has no rev dependencies * It FTBFS with GHC 9.6 * It's not part of the latest Stackage LTS * The Haskell version is abandoned, and the project has been rewritten in Rust If you b

Bug#1040771: no need to keep it out of testing until the freeze

Control: severity -1 serious On Sat, 10 Aug 2024 10:05:19 +0200 Matthias Klose wrote: there is no need to keep it out of testing until the freeze. The freeze is now. Paul OpenPGP_signature.asc Description: OpenPGP digital signature

Bug#1078198: no need to keep it out of testing until the freeze

Control: severity -1 serious On Sat, 10 Aug 2024 10:05:28 +0200 Matthias Klose wrote: there is no need to keep it out of testing until the freeze. The freeze is now. Paul OpenPGP_signature.asc Description: OpenPGP digital signature

Bug#1078199: no need to keep it out of testing until the freeze

Control: severity -1 serious On Sat, 10 Aug 2024 10:05:36 +0200 Matthias Klose wrote: there is no need to keep it out of testing until the freeze. The freeze is now. Paul OpenPGP_signature.asc Description: OpenPGP digital signature

Bug#1099013: emacs-gtk: hangs compositor when used under Wayland

Control: found -1 4:6.3.4-2 Hi, On 15-03-2025 08:53, Paul Gevers wrote: PS on IRC coucouf already pointed out https://bugs.kde.org/show_bug.cgi? id=501073 which may or may not be related. I have subscribed to that bug a while ago, and lots of people confirmed that restarting plasma

Bug#1099013: emacs-gtk: hangs compositor when used under Wayland

Control: found -1 4:6.3.4-2 Hi, On 15-03-2025 08:53, Paul Gevers wrote: PS on IRC coucouf already pointed out https://bugs.kde.org/show_bug.cgi? id=501073 which may or may not be related. I have subscribed to that bug a while ago, and lots of people confirmed that restarting plasma

Bug#1099013: emacs-gtk: hangs compositor when used under Wayland

Control: found -1 4:6.3.4-2 Hi, On 15-03-2025 08:53, Paul Gevers wrote: PS on IRC coucouf already pointed out https://bugs.kde.org/show_bug.cgi? id=501073 which may or may not be related. I have subscribed to that bug a while ago, and lots of people confirmed that restarting plasma

Bug#1102538: unblock: glib2.0 blocked by openjdk-25 autopkgtest on riscv64

Hi On 10-04-2025 10:49, Simon McVittie wrote: (glib2.0's excuses entry cites a piuparts regression as the reason for not migrating, but I think that might not really be true, because https://piuparts.debian.org/sid/source/g/glib2.0.html doesn't list any unsuccessful tests. Perhaps the machinery

Bug#1102538: unblock: glib2.0 blocked by openjdk-25 autopkgtest on riscv64

Hi On 10-04-2025 10:49, Simon McVittie wrote: (glib2.0's excuses entry cites a piuparts regression as the reason for not migrating, but I think that might not really be true, because https://piuparts.debian.org/sid/source/g/glib2.0.html doesn't list any unsuccessful tests. Perhaps the machinery

Bug#1084089: llvm-toolchain-17: do not release with trixie

Hi, On 10-04-2025 10:46, Paul Gevers wrote: On Sun, 23 Mar 2025 20:14:34 +0100 Sylvestre Ledru Do you want me to bump them? Hmm, we should have done that at least 3 months ago. I consider it a bit too late now as there are both key and non-key package involved. This reply had been

Bug#1084089: llvm-toolchain-17: do not release with trixie

Control: retitle -1 llvm-toolchain-17: do not release with stable Control: tags -1 trixie-ignore Hi, On Sun, 23 Mar 2025 20:14:34 +0100 Sylvestre Ledru wrote: Le 23/03/2025 à 00:42, Jeremy Bícha a écrit : > If https://bugs.debian.org/1084089 is RC, then shouldn't all the > blocking bugs for h

Bug#1084089: llvm-toolchain-17: do not release with trixie

Control: retitle -1 llvm-toolchain-17: do not release with stable Control: tags -1 trixie-ignore Hi, On Sun, 23 Mar 2025 20:14:34 +0100 Sylvestre Ledru wrote: Le 23/03/2025 à 00:42, Jeremy Bícha a écrit : > If https://bugs.debian.org/1084089 is RC, then shouldn't all the > blocking bugs for h

Re: Bug#1057562: Some severities to reconsider due to flaky tests

Hi, On 09-04-2025 21:42, Jeremy Bícha wrote: On Wed, Apr 9, 2025 at 1:33 PM Paul Gevers wrote: My personal standard (but with Release Team hat in mind) is that I file RC bugs about flakiness if a test fails more than about 1 out of 6 times (on a particular architecture if it's archite

Bug#1057562: Some severities to reconsider due to flaky tests

Hi, On 09-04-2025 21:42, Jeremy Bícha wrote: On Wed, Apr 9, 2025 at 1:33 PM Paul Gevers wrote: My personal standard (but with Release Team hat in mind) is that I file RC bugs about flakiness if a test fails more than about 1 out of 6 times (on a particular architecture if it's archite

Re: Question for a package if can be in trixie

Hi Leopold, On 07-04-2025 23:24, Leopold Palomo-Avellaneda wrote: I'm the main in charge of the package ompl [1]. The package has a library but no package outside the sources use it. Right, so this doesn't need a transition. In December, it was a Team upload with a new upstream version. Last

Bug#1057562: Some severities to reconsider due to flaky tests

Hi all, On 09-04-2025 14:26, Jeremy Bícha wrote: "flaky" is vague and until there is a specific standard for failure rate, this is going to be subject to maintainer discretion to some degree. My personal standard (but with Release Team hat in mind) is that I file RC bugs about flakiness if a

Re: Some severities to reconsider due to flaky tests

Hi all, On 09-04-2025 14:26, Jeremy Bícha wrote: "flaky" is vague and until there is a specific standard for failure rate, this is going to be subject to maintainer discretion to some degree. My personal standard (but with Release Team hat in mind) is that I file RC bugs about flakiness if a

Bug#1102406: mame: regression in reproducibility

Source: mame Version: 0.276+dfsg.1-1 Severity: important Dear maintainers, With the upload of version 0.276+dfsg.1-1 of your package, the reproducible-build project [1] reports your package as no longer reproducible. Paul ./usr/share/doc/mame/examples/default.plugin.ini Ordering differences

Bug#1102362: chemps2: riscv64 autopkgtest is flaky

Hi, On Tue, 08 Apr 2025 10:34:43 +0200 =?utf-8?q?Timo_R=C3=B6hling?= wrote: the autopkgtest on riscv64 sometimes segfaults [1]. Currently, this prevents cmake from migrating to testing. Please also check bugs #1008802 and #1017710. They might be duplicates, so it's not only riscv64. Paul

Bug#1102362: chemps2: riscv64 autopkgtest is flaky

Hi, On Tue, 08 Apr 2025 10:34:43 +0200 =?utf-8?q?Timo_R=C3=B6hling?= wrote: the autopkgtest on riscv64 sometimes segfaults [1]. Currently, this prevents cmake from migrating to testing. Please also check bugs #1008802 and #1017710. They might be duplicates, so it's not only riscv64. Paul

  1   2   3   4   5   6   7   8   9   10   >