Bug#1066024: dbconfig-common: Link error from https://www.debian.org/doc/manuals/dbconfig-common/dbconfig-common-design.html

Hi webmasters, The bug below was reported against dbconfig-common. dbconfig-common ships files in its package that are also (on my request) shown on the manuals page. However, while the link in the html works as-installed on users' systems, it doesn't work on the Debian web site. Any idea how

Bug#1104114: unblock: rustc/1.85.0+dfsg3-1

Control: tags -1 confirmed On 25-04-2025 21:28, Fabian Grünbichler wrote: Please unblock package rustc I appreciate this is a pre-approval request. Please go ahead. Paul OpenPGP_signature.asc Description: OpenPGP digital signature

Bug#1100698: Bug#1101757: unblock: dovecot/1:2.4.1+dfsg1-1

Hi Noah, On 26-04-2025 10:03, Paul Gevers wrote: For the record of this bug, there's a piuparts issue (tagged pending): 1104047. Please also help the reverse dependencies to fix their autopkgtests (filing bugs and/or providing patches). It seems that the new dovecot requires an upda

Bug#1104159: r-cran-testthat breaks r-cran-rcmdcheck autopkgtest

Source: r-cran-testthat, r-cran-rcmdcheck Control: found -1 r-cran-testthat/3.2.3-1 Control: found -1 r-cran-rcmdcheck/1.4.0-3 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of r-cran-testthat the autopkg

Bug#1104158: r-cran-testthat breaks r-cran-hdf5r autopkgtest

Source: r-cran-testthat, r-cran-hdf5r Control: found -1 r-cran-testthat/3.2.3-1 Control: found -1 r-cran-hdf5r/1.3.12+dfsg-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of r-cran-testthat the autopkgte

Bug#1104160: r-cran-testthat breaks r-cran-s2 autopkgtest on i386

Source: r-cran-testthat, r-cran-s2 Control: found -1 r-cran-testthat/3.2.3-1 Control: found -1 r-cran-s2/1.1.7-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of r-cran-testthat the autopkgtest of r-cran

Bug#1103835: unblock: libcap2/1:2.75-7

Control: tags -1 confirmed On 25-04-2025 11:53, Helmut Grohne wrote: As a result, I argue that the risk of causing regressions here is quite low. Please go ahead. Paul OpenPGP_signature.asc Description: OpenPGP digital signature

Bug#1103995: unblock: rust-debcargo/2.7.8-4

Control: tags -1 moreinfo Hi, On 25-04-2025 17:28, Fabian Grünbichler wrote: I agree with that in principle, but would still like RT's input on that given the amount of packages (many of which would otherwise not see another upload, except maybe a final binNMU to pick up changes in (transitive)

Bug#1103973: unblock: hueplusplus/1.2.0+ds-1

Hi On 23-04-2025 11:22, Ahmad Khalifa wrote: hueplusplus is a small library needed for openrgb, which is also blocked (separate bug being submitted). I'm sorry, I'm not seeing a reason for an exception. We have to draw the line somewhere and it missed the deadline. Paul OpenPGP_signatur

Bug#1103529: xapian-core: libxapian unexpectedly changed soname and package name

Hi Sven, On Fri, 18 Apr 2025 20:34:25 +0200 Sven Joachim wrote: In the latest upload of xapian-core, libxapian changed its soname from 30 to 29 and a new binary package libxapian29 appeared out of nowhere. If this were intended, the package would have needed to go threw NEW, but since the packa

Bug#1100698: Bug#1101757: unblock: dovecot/1:2.4.1+dfsg1-1

Hi On 24-04-2025 18:20, Paul Gevers wrote: With both of the issues out of the way, go ahead. For the record of this bug, there's a piuparts issue (tagged pending): 1104047. Paul OpenPGP_signature.asc Description: OpenPGP digital signature

Bug#1081879: Next investigation steps

Hi, On Sat, 12 Apr 2025 16:18:51 +0200 Margarita Manterola wrote: Particularly interesting is the last one, target-cpu=native. I looked around, trying to find where that is coming from, and found that upstream's .cargo/config.toml file says this: To ensure consistency while building on Debi

Bug#1104152: src:python-xiaomi-ble: fails to migrate to testing for too long

Source: python-xiaomi-ble Version: 0.30.2-3 Severity: serious Control: close -1 0.36.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1103588 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing

Bug#1103588: python-xiaomi-ble: autopktest failure on s390x: test_Xiaomi_MS1BB_MI_obj4a08 test_Xiaomi_HS1BB_illuminanca_and_motion test_Xiaomi_XMPIRO2SXS

Dear s390x porters, This bug has your user tag already, but it wasn't X-Debbugs-CC to you, you might want to help out. (Start of report below, full report from https://bugs.debian.org/1103588) Paul On Sat, 19 Apr 2025 13:40:01 +0200 Chris Hofstaedtler wrote: Source: python-xiaomi-ble Vers

Bug#1104151: src:python-xarray: fails to migrate to testing for too long

Source: python-xarray Version: 2025.01.2-1 Severity: serious Control: close -1 2025.03.1-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

Bug#1104150: src:python-djvulibre: fails to migrate to testing for too long

Source: python-djvulibre Version: 0.9.0-7 Severity: serious Control: close -1 0.9.1-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: blocked -1 by 1103593 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing a

Bug#1104110: RM: phog/0.1.7-1

Control: tags -1 moreinfo Hi Guido, On 25-04-2025 20:47, Guido Günther wrote: phog (which is hard tox maintain due to an embeded code copy) has been replaced by phrog (which uses a shared library provided by phosh thus avoiding code dupliation). It sounds like you want to have it removed fro

Bug#1104147: setup-testbed doesn't configure qemu console unless it detects serial ports

Hi On 26-04-2025 00:15, Stefano Rivera wrote: the host's serial devices are... whatever they are. If I read the code correctly, the services loop over the devices they know and use the first one they find. So I think more is needed than just installing. Paul OpenPGP_signature.asc Descr

Bug#1103965: unblock: jetty12/12.0.17-3

Control: tags -1 moreinfo On 24-04-2025 18:17, Emmanuel Bourg wrote: I agree it's too late for a full transition to Jetty 12, but several packages only use jetty9 to run unit tests or for minor features. The idea is to leave them as-is for Trixie, remove the jetty9 server package but keep the

Bug#1100698: Bug#1101757: unblock: dovecot/1:2.4.1+dfsg1-1

Control: tags -1 confirmed Hi, On 24-04-2025 18:13, Noah Meyerhans wrote: It's likely my fault for not highlighting the unusual nature of dovecot when filing the bug. I could have asked earlier. I did notify the maintainer privately, before realizing that they seem MIA, but didn't follow u

Bug#1104036: ruby-shoulda-context: autopkgtest failure: cannot load such file -- /tmp/autopkgtest-lxc.1_v7v5ha/downtmp/build.yEW/src/lib/shoulda/context

Source: ruby-shoulda-context Version: 2.0.0-3 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), [As aligned in bug 1102618, I'll make this bug non-blocking for migration to testing.] With a recent upload of ruby-shoulda-context the autopkgtest of rub

Bug#1102618: [DRE-maint] ruby-pry-byebug: Does not install in unstable

Hi, On 24-04-2025 15:35, Lucas Nussbaum wrote: On 24/04/25 at 14:38 +0200, Paul Gevers wrote: Hi, On 24-04-2025 13:56, Lucas Nussbaum wrote: ruby-shoulda-context was updated and no longer build-depends on ruby-pry-byebug. So ruby-pry-byebug could be removed (once ruby-shoulda-context

Bug#1103965: unblock: jetty12/12.0.17-3

Control: tags -1 moreinfo On 23-04-2025 10:17, Emmanuel Bourg wrote: This package is intended to replace jetty9 which was EOLed in January [1]. I believe it is too late to replace jetty9 in trixie as it has quite some reverse dependencies. We prefer not to have multiple versions of the same

Bug#1103871: unblock: vala-panel/24.05-3

Control: tags -1 moreinfo Hi Mike, I'm not really impressed by all your unblock requests. It leaves the impression that you started too late preparing for trixie. On 22-04-2025 11:11, Mike Gabriel wrote: I attempted fixing vala-panel and vala-panel-appmenu in time for the soft freeze deadlin

Bug#1103835: unblock: libcap2/1:2.75-7

Control: tags -1 moreinfo On 21-04-2025 20:57, Christian Kastner wrote: I'd like to ask for pre-approval up an upload of libcap2/1:2.75-7. Helmut discovered that recent upload introducing a go package introduced a FTCBFS, and submitted a patch for it. This looks OK, but both this bug and bug

Bug#1103401: unblock: kleidiai/1.6.0+ds-2

Control: tags -1 moreinfo Hi, On 17-04-2025 08:43, Shengqi Chen wrote: kleidiai is a new source package. I uploaded it on 13 Mar and it cleared NEW on 12 Apr, right before the soft freeze. The changelog says 12 April, not 13 March. Care to fill in the missing pieces? Paul OpenPGP_signa

Bug#1099927: r-cran-testthat does not actually break other packages

Hi, On Wed, 23 Apr 2025 12:23:10 +0100 "Rebecca N. Palmer" wrote: Anything that involves partial removals also needs permission to ignore some arch:all packages (i.e. their reverse dependencies) becoming uninstallable on 32-bit architectures. (By default, arch:all packages are expected to b

Bug#1102618: [DRE-maint] ruby-pry-byebug: Does not install in unstable

Hi, On 24-04-2025 13:56, Lucas Nussbaum wrote: ruby-shoulda-context was updated and no longer build-depends on ruby-pry-byebug. So ruby-pry-byebug could be removed (once ruby-shoulda-context migrates). ruby-shoulda-context fails its own autopkgtest everywhere. Paul OpenPGP_signature.asc D

Bug#1103162: nmu: coot_1.1.15+dfsg-1

Hi, On Mon, 21 Apr 2025 12:50:15 +0200 Sebastian Ramacher wrote: > Right. But coot is the only reverse-depdency, and I think it is ok to > rebuild it for trixie and then re-assess the situation post-trixie. E.g. > we could remove the shared library. It is not ideal, but scheduled the rebuild.

Bug#1103579: coot: autopkgtest regression: ImportError

Hi, On 22-04-2025 13:44, Chris Hofstaedtler wrote: * Andrius Merkys [250422 09:27]: coot/1.1.15+dfsg-1+b1 (in unstable) was a rebuild against rdkit/202503.1-2 (in unstable). coot/1.1.15+dfsg-1 (in testing) is built to work with rdkit/202409.6-2 (in testing). Mixing versions from stable and u

Bug#1101757: unblock: dovecot/1:2.4.1+dfsg1-1

Hi Noah, Sorry taking so long to reply. I assumed because you filed a transition bug that there was a regular SONAME bump involved. I see that the dovecot-core ships libraries, but it looks like they didn't bump SONAME. So how is this supposed to work in the dovecot ecosystem? Isn't the packa

Bug#1102618: ruby-pry-byebug: Does not install in unstable

Hi, On Sat, 12 Apr 2025 00:58:12 +0530 Pirate Praveen wrote: > Since ruby-shoulda-context Build-Depends ruby-pry-byebug this also > affects #1054740. I tried to update to new upstream version which has a fix for this, but this needs ruby-byebug updated from 11 to 12. What's the progress he

Bug#1102928: mpich: mpi-defaults autopkgtest regressions on 32-bit

Hi, On 24-04-2025 10:32, Alastair McKinstry wrote: My perference was to leave 4.3.0. in unstable, but given the valgrind issue, it looks like an upload 4.3.0_really4.2.1 is needed. Anyone think differently? I agree that a 4.3.0_really4.2.1 looks best at this moment. Paul OpenPGP_signatur

Bug#1103595: Bug#1103423: src:kitty: fails to migrate to testing for too long: FTBFS on s390x

Hi, Looping in Pranav, On 24-04-2025 00:18, Chris Hofstaedtler wrote: * Nilesh Patra [250423 20:54]: Upstream has explicitly denied to provide any support for s390x see[1]. And I don't think I have the interest, time and energy to support a port this for big endian arch myself. That's OK.

Bug#1103954: src:dcmtk: fails to migrate to testing for too long

Source: dcmtk Version: 3.6.9-4 Severity: serious Control: close -1 3.6.9-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 than 30 days as havin

Bug#1103955: src:python-mastodon: fails to migrate to testing for too long

Source: python-mastodon Version: 2.0.0-2 Severity: serious Control: close -1 2.0.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 day

Bug#1103307: rsyslog-pgsql fails to configure after debconf database is lost

Hi, On 22-04-2025 17:50, Kim-Alexander Brodowski wrote: Unfortunately, I can't. No question is ever asked, not even when reinstalling. I can't see any obvious calls to debconf's INPUT either. Can you check the content of /etc/dbconfig-common/rsyslog-pgsql.conf ? I assume it has (or something

Bug#1099499: requires pyarrow

Hi, On 21-04-2025 13:15, Daniel Baumann wrote: I though filling the RC bug against harlequin right after it left NEW would be enough to never let harlequin-* migrate, seems not. Sorry about the confusion it caused. harlequin-* in testing don't depend on harlequin, so blocking harlequin didn'

Bug#1099499: requires pyarrow

Hi, On 21-04-2025 11:58, Daniel Baumann wrote: harlequin-* are the database connection plugins and useless without harelquin itself. So they should have never made it to testing. The autoremoval is correct (which was my intention with their depends to harlequin, so that they in turn also do

Bug#1099927: Ping bug to reset testing removal timer

On Sat, 19 Apr 2025 07:29:29 +0200 Andreas Tille wrote: If r-cran-testthat would be removed a lot of tests of R packages become broken. I assume you're working on fixing the issues and that bugs have been filed against the packages that need to adapt. It is probably worth it to block this bu

Bug#1102612: mpich 4.3 not initialising multiple processes

Hi, On Sun, 20 Apr 2025 16:45:34 +0200 Drew Parsons wrote: Package: mpich Version: 4.3.0-5 Followup-For: Bug #1102612 Control: found -1 4.3.0-5 Control: fixed -1 4.3.0-6 Updating tags (the fixed version is in experimental, the version in unstable is not yet updated). https://qa.debian.org/e

Bug#1099499: requires pyarrow

Hi Daniel, On 21-04-2025 10:09, Daniel Baumann wrote: On Sat, 12 Apr 2025 10:22:02 +0200 Paul Gevers wrote: > Do you mean it depends on it, but it doesn't Depends on it? yes - harlequin depends on the python parts of apache arrow which is not packaged for Debian yet. I didn

Bug#1103615: [Pkg-javascript-devel] Bug#1103615: node-dompurify: please update to latest version

Hi Jérémy, Thanks for the reply. On 20-04-2025 13:21, Jérémy Lal wrote: Good question ! The answer is that it's not needed: nodejs 20.19.0 can "require(esm)" [1] so a CJS module is no longer locked out using ESM modules. The other way around (import a CJS module form an ES module) has always

Bug#1103615: node-dompurify: please update to latest version

Hi, On Sat, 19 Apr 2025 19:28:11 +0200 Paul Gevers wrote: I was struggling to package the latest version of `liferea` because I didn't want to use the upstream vendored purify (and handlebars). It turns out that the Debian version of node-dompurify is too old. Is it reasonable to up

Bug#1103569: [Debian-med-packaging] Bug#1103569: src:orthanc-wsi: fails to migrate to testing for too long

Hi, In my previous reply I may have gotten some details wrong, as I hadn't read the bug about dcmtk yet. On 19-04-2025 20:01, Sébastien Jodogne wrote: If I read that other bug correctly, the changed path in dcmtk broke orthanc. So, the right binary package of src:dcmtk should declare that wit

Bug#1095174: autopkgtest 5.43: regression while testing debian-edu-doc: build times out and fails with tmpfail

Hi, On 18-04-2025 11:13, Wolfgang Schweer wrote: This timeout is supposed to have been caused by a (now fixed) debian-edu-doc bug, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102925 Thanks for connecting dots. But the fact that autopkgtest tmpfails in this case is still a prob

Bug#1103615: node-dompurify: please update to latest version

Source: node-dompurify Version: 3.1.7+dfsg+~3.0.5-1 Severity: normal Hi, I was struggling to package the latest version of `liferea` because I didn't want to use the upstream vendored purify (and handlebars). It turns out that the Debian version of node-dompurify is too old. Is it reasonable

Bug#1102160: upgrade-reports: Bookworm to Trixie [amd64][EFI] initramfs unpacking failed invalid magic at start of compressed archive

Hi Martin-Éric On 19-04-2025 10:19, Martin-Éric Racine wrote: And what do you expect from the Release Team? A simple question: Will the release team publish Trixie fully knowing that btrtfs hosts will no longer be bootable via UEFI? I hope you made a joke when you said "simple", because it

Bug#1103569: [Debian-med-packaging] Bug#1103569: src:orthanc-wsi: fails to migrate to testing for too long

Hi Sébastien, On 19-04-2025 10:48, Sébastien Jodogne wrote: This is a duplicate of #1103505 [1]. Close, but not really. That bug is about the failing test, which applies to unstable, this bug is about it not migrating, which is an RC bug against the version in testing. Unfortunately, I c

Bug#1103569: src:orthanc-wsi: fails to migrate to testing for too long

Source: orthanc-wsi Version: 3.0+dfsg-1 Severity: serious Control: close -1 3.2+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 d

Bug#1103568: src:rsplib: fails to migrate to testing for too long

Source: rsplib Version: 3.4.4-1.1 Severity: serious Control: close -1 3.5.1-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 as

Bug#1102160: upgrade-reports: Bookworm to Trixie [amd64][EFI] initramfs unpacking failed invalid magic at start of compressed archive

Hi Martin-Eric, On 18-04-2025 18:10, Martin-Éric Racine wrote: I would really hope the release team to step in on this one. And what do you expect from the Release Team? Paul OpenPGP_signature.asc Description: OpenPGP digital signature

Bug#1095247: ruby-dalli: autopkgtest regression on armel and armhf

Control: retitle -1 ruby-dalli potential issue with 64b time_t on arm* On Wed, 9 Apr 2025 16:10:54 +0200 Lucas Nussbaum wrote: The problem here is that the packing of seconds, microseconds into a struct timeval is architecture-dependent, and cannot be assumed to be solved by pack('l_2'). For

Bug#1103420: [Pkg-electronics-devel] Bug#1103420: src:sch-rnd: fails to migrate to testing for too long

Hi Bdale, On 18-04-2025 02:40, Bdale Garbee wrote: I assumed that the closure of #1101065 would allow sch-rnd to be promoted to testing, since the i386 build failure in the new version was the only excuse listed at the time. That bug was apparently closed on 8 Apr, but rmadison is still showing

Bug#1103307: rsyslog-pgsql fails to configure after debconf database is lost

Hi Michael, Thanks for reaching out. It's been a long time since I looked at dbconfig-common (and I'm not the author), so things are extremely rusty. On 17-04-2025 20:28, Michael Biebl wrote: kim.iserv.dev ~ # LC_ALL=C dpkg --configure -a Setting up rsyslog-pgsql (8.2302.0-1+deb12u1

Bug#1103427: pymatgen: autopkgtest regression: exit code 5

Source: pymatgen Version: 2025.2.18+dfsg1-4 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails in testing since very recently. Can you please investigate the situation and fix it? I copied some o

Bug#1103406: ogdi-dfsg: flaky autopkgtest on arm64

Hi, On 17-04-2025 12:49, Sebastiaan Couwenberg wrote: On 4/17/25 12:16 PM, Paul Gevers wrote: To avoid having to do this on the package side, I (ci.d.n maintainer hat on) could add your package to the ci.d.n reject_list That doesn't sound like a good idea because then two people need

Bug#1103423: src:kitty: fails to migrate to testing for too long: FTBFS on s390x

Source: kitty Version: 0.39.1-1 Severity: serious Control: close -1 0.40.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync X-Debbugs-CC: debian-s...@lists.debian.org User: debian-s...@lists.debian.org Usertag: s390x Dear maintainer(s), The Release Team consi

Bug#1103422: src:git: fails to migrate to testing for too long

Source: git Version: 1:2.47.2-0.1 Severity: serious Control: close -1 1:2.49.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1102106 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unst

Bug#1102106: git ftbfs on s390x (test failures)

user debian-s...@lists.debian.org usertag 1102106 s390x thanks Dear s390x porters, Can you please have a look at bug 1102106? (Copied in full below for your convenience) Paul On Sat, 5 Apr 2025 07:20:13 +0200 Matthias Klose wrote: Package: src:git Version: 1:2.49.0-1 Severity: serious Tags

Bug#1103421: src:libfabric: fails to migrate to testing for too long

Source: libfabric Version: 1.17.0-3.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 a

Bug#1103420: src:sch-rnd: fails to migrate to testing for too long

Source: sch-rnd Version: 1.0.7-1 Severity: serious Control: close -1 1.0.8-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 days as hav

Bug#1103419: src:mpich: fails to migrate to testing for too long

Source: mpich Version: 4.2.1-5 Severity: serious Control: close -1 4.3.0-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 than 30 days as havin

Bug#1103406: ogdi-dfsg: flaky autopkgtest on arm64

Hi Bas, On 17-04-2025 10:53, Sebastiaan Couwenberg wrote: Runner with unreliable network should not satisfy the needs-internet requirement. I agree with you on this, the problem is of course how to define unreliable network and where the border should be. I've made the wget and tar command

Bug#962710: libedit2: undocumented change to upstream's SONAME

Hi, On Thu, 23 Jan 2025 11:44:39 +1000 Matt Jolly wrote: With the trixie freeze dates being announced today I just wanted to touch base on this one and see how the ticket is progressing. For all those following this bug or stubling upon it, if this is done, don't do it close to or during the

Bug#1103113: on filing FTBFS due to out-of-memory on i386

Hi Lucas, Thanks for the reply, much appreciated. On 17-04-2025 09:58, Lucas Nussbaum wrote: In general: when mass-filing bugs, I try hard to find the right balance between the time spent filing bugs, and the amount of errors I make. I totally recognize that as I'm also filing a huge amount

Bug#1103406: ogdi-dfsg: flaky autopkgtest on arm64

Source: ogdi-dfsg Version: 4.1.1+ds-5 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 on arm64, while other architectures seem fine. Unfortunately, the test does

Bug#1084069: update tags for hipify: Please upgrade build-dep to llvm/clang 18 or 19

Control: tag 1084069 sid trixie-ignore Hi I have marked bug 1084089 as trixie-ignore [1], so this bug can be ignored for trixie too. If it can be done within the freeze policy constraints, fixing this is still on the table and doesn't need to wait. Paul [1] https://bugs.debian.org/cgi-bin/b

Bug#1103113: on filing FTBFS due to out-of-memory on i386

Control: tags -1 moreinfo Hi Lucas, [Release Team member hat on] I always appreciate your QA work on rebuilding Debian, but I'm wondering what the value is of filing out-of-memory FTBFS bugs on a 32 bit architecture for source packages that only builds arch:all binaries. arch:all binaries in

Bug#1103133: simulate-event.js: FTBFS in testing/i386: make: *** [debian/rules:8: binary] Error 2

Control: reassign -1 node-browserify Control: affects -1 src:simulate-event.js Control: retitle -1 browserify segfaults building i386/simulate-event.js On Mon, 14 Apr 2025 13:41:39 +0200 Lucas Nussbaum wrote: During a rebuild of all packages in testing (trixie), your package failed to build on

Bug#1103130: rust-wide: FTBFS in testing/i386: dh_auto_test: error: /usr/share/dh-rust/bin/cargo test returned exit code 101

Control: severity -1 important Control: block -1 by 1095862 On Mon, 14 Apr 2025 13:41:30 +0200 Lucas Nussbaum wrote: Source: rust-wide > cargo:warning=Compiling optimized code on Debian non-SSE2 i686 architecture leads to unsound code. Build will be aborted. > warning: build failed, waiti

Bug#1103260: pyopencl: regression in reproducibility

Source: pyopencl Version: 2025.1-1 Severity: important Hi, With the upload of version 2025.1-1, reproducible-builds.d.n reports your package as no longer reproducible. The diff seems to be in file properties as installed. Paul https://tests.reproducible-builds.org/debian/rb-pkg/pyopencl.htm

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

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#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#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#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

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#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#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#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#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#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#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#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#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#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#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

  1   2   3   4   5   6   7   8   9   10   >