Bug#1084066: amdgcn-tools: Please upgrade build-dep to llvm/clang 18 or 19

On 28.04.25 11:39, Arnout Vandecappelle wrote:  This leads to the following bug report in GCC [1] - conclusion is that it's fixed in GCC 14 by commits [2] and [3]. the "fixes" are the removal to support this hardware.  So it seems to me that the options for trixie are: - Keep LLVM 17 suppo

Bug#1104272: libgcobol-15-dev and libgcobol-15-dev-amd64-cross have an undeclared file conflict on /usr/share/man/man3/x86_64-linux-gnu-gcobol-io-15.3.gz

#1103019 On 30.04.25 07:12, Helmut Grohne wrote: Hi Matthias, On Wed, Apr 30, 2025 at 06:04:44AM +0200, Matthias Klose wrote: closing, why are you filing duplicates? which bug - in your opinion - is being duplicated here? Possible candidates: * #1101749 is about ga68-15 vs ga68-15-doc *

Bug#1101613: Bug#1100250: Bug#1101420: pgpainless still waiting for bouncycastle

On Tue, Apr 29, 2025 at 04:54:34PM +, tony mancill wrote: > On Sun, Apr 27, 2025 at 06:27:51PM +0200, Chris Hofstaedtler wrote: > > On Sat, Apr 26, 2025 at 06:08:20PM +, tony mancill wrote: > > > On Fri, Apr 25, 2025 at 11:15:03PM +0200, Martin Hostettler wrote: > > > > Bump to avoid auto r

Bug#1104435: php-pear: pear: /usr/bin/php: No such file or directory

Source: php-pear Version: 1:1.10.16+submodules+notgz-2 Severity: serious Executing php-pear fails on a fresh install. This also breaks autopktests of various packages, as can be seen on: https://tracker.debian.org/pkg/php-pear and thus prevents migration of php-pear to testing. Failure as obse

Bug#1104434: php-imagick: autopkgtest failure on all archs

Source: php-imagick Version: 3.8.0-1 Severity: serious php-imagick's autopkgtests fail on all archs. Example log from amd64: https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-imagick/60308706/log.gz 34s autopkgtest [06:09:59]: test command1: cd imagick-$(xml2 < package.xml | sed -ne

Processed (with 1 error): Pdsh bug updates

Processing commands for cont...@bugs.debian.org: > forcemerge 1102958 1094108 Bug #1102958 {Done: Brian Pellin } [src:pdsh] pdsh: FTBFS in testing: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 Bug #1094108 {Done: Brian Pellin } [src:pdsh] pdsh

Bug#1104272: libgcobol-15-dev and libgcobol-15-dev-amd64-cross have an undeclared file conflict on /usr/share/man/man3/x86_64-linux-gnu-gcobol-io-15.3.gz

Hi Matthias, On Wed, Apr 30, 2025 at 06:04:44AM +0200, Matthias Klose wrote: > closing, why are you filing duplicates? which bug - in your opinion - is being duplicated here? Possible candidates: * #1101749 is about ga68-15 vs ga68-15-doc * #1102279 is about lib32* vs libn32* I see no further

Bug#1104364: marked as done (snek: FTBFS: ./arm-none-eabi/../../../newlib/libc/tinystdio/puts.c:63:(.text.puts+0x3c): undefined reference to `stdout')

ource: snek Version: 1.11-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/lib/gcc/arm-none-eab

Bug#1102958: marked as done (pdsh: FTBFS in testing: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)

Your message dated Wed, 30 Apr 2025 05:04:40 + with message-id and subject line Bug#1102958: fixed in pdsh 2.35-2 has caused the Debian Bug report #1102958, regarding pdsh: FTBFS in testing: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 to b

Bug#1104272: marked as done (libgcobol-15-dev and libgcobol-15-dev-amd64-cross have an undeclared file conflict on /usr/share/man/man3/x86_64-linux-gnu-gcobol-io-15.3.gz)

Your message dated Wed, 30 Apr 2025 06:04:44 +0200 with message-id <8aaacb00-7f49-434c-9de1-2ff7856a8...@debian.org> and subject line Re: Bug#1104272: libgcobol-15-dev and libgcobol-15-dev-amd64-cross have an undeclared file conflict on /usr/share/man/man3/x86_64-linux-gnu-gcobol-io-15.3.gz has c

Bug#1101870: Please autorm

Just a mail to please the AUTORM to let the new version migrate.

Bug#1104139: marked as done (fltk1.4-games has an undeclared file conflict on /usr/share/man/man6/sudoku.6.gz)

Your message dated Wed, 30 Apr 2025 01:34:16 + with message-id and subject line Bug#1104139: fixed in fltk1.4 1.4.3-1 has caused the Debian Bug report #1104139, regarding fltk1.4-games has an undeclared file conflict on /usr/share/man/man6/sudoku.6.gz to be marked as done. This means that yo

Processed: qtcontacts-sqlite: FTBFS randomly: dh_auto_test: error: make -j1 check returned exit code 2

Processing commands for cont...@bugs.debian.org: > severity 1104383 serious Bug #1104383 [src:qtcontacts-sqlite] qtcontacts-sqlite: FTBFS randomly: dh_auto_test: error: make -j1 check returned exit code 2 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contac

Bug#1103577: FTBFS: breezy.tests.fixtures.TimeoutException: 6000

Hello. In my setup (amd64), this package FTBFS... 100% of the time on machines with 1 CPU 50% of the time on machines with 2 CPUs So, it does not seem to be architecture-specific (s390x). I suggest trying GRUB_CMDLINE_LINUX="nr_cpus=1" since that's what apparently makes the failure rate to be h

Bug#1103418: openssh-server irregularly crashing since 10.0p1 upgrade

Hello, Same problem here since 1:10.0p1-2 was migrated to testing yesterday. sshd-session crashes with SIGSEGV at "random" intervals (but many times in a row, sometimes) I've tried logging from different systems and openssh versions (Debian testing, stable, Mint 22.1, Connectbot on Android),

Bug#1103981: proftpd-core: Does not start with default configuration (unknown configuration directive 'ShowSymlinks')

On 28.04.25 David Prévot (da...@tilapin.org) wrote: > On 28/04/2025 00:02, Hilmar Preusse wrote: Hello David, > > I built the proftpd-core_1.3.8.c+dfsg-3 for Debian stable, then > > purged the proftpd installation on my server and installed the custom > > packages. The server process starts up fi

Bug#1104411: gsasl: autopkgtests fail with dovecot 2.4

On Tue, Apr 29, 2025 at 10:48:24PM +0200, Simon Josefsson wrote: > Okay that would help to confirm if this is a dovecot problem or gsasl > problem. You could try increasing the dovecot debug logging during the > gsasl test, the generic error in dovecot must be caused by something > and understandin

Bug#1103089: jnr-ffi: FTBFS

Hello. In addition to what Lucas reported, this package fails to build for me on amd64: 82% of the time on machines with 1 CPU 6% of the time on machines with 2 CPUs so maybe the issue is not about amd64/i386 but about overall speed. I suggest that you try on your normal amd64 system using GR

Bug#1104425: softhsm2: tries to load rdrand engine

Source: softhsm2 Version: 2.6.1-2.2 Severity: serious I've been told that it ties to load rdrand: But we don't have the rdrand engine in Debian. Kurt

Bug#1103089: jnr-ffi: FTBFS in testing/i386: dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmave

> Source: jnr-ffi > Version: 2.2.15-2 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20250414 ftbfs-trixie > > Hi, > > During a rebuild of all packages in testing (trixie), your package failed > to build on i386. Interestingly, althou

Bug#1104411: gsasl: autopkgtests fail with dovecot 2.4

Okay that would help to confirm if this is a dovecot problem or gsasl problem. You could try increasing the dovecot debug logging during the gsasl test, the generic error in dovecot must be caused by something and understanding what could explain things a bit. Maybe some file ownership/permissi

Bug#1104424: request-tracker4: CVE-2025-2545 CVE-2025-30087

On Tue, Apr 29, 2025 at 10:41:37PM +0200, Salvatore Bonaccorso wrote: > Source: request-tracker4 > Version: 4.4.7+dfsg-4 > Severity: grave > Tags: security upstream > X-Debbugs-Cc: car...@debian.org, Debian Security Team > > > Hi, > > The following vulnerabilities were published for request-tra

Bug#1104424: request-tracker4: CVE-2025-2545 CVE-2025-30087

Source: request-tracker4 Version: 4.4.7+dfsg-4 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for request-tracker4. Making them RC severity as they should be fixed for the trixie release before relea

Bug#1104422: request-tracker5: CVE-2025-31500 CVE-2025-31501 CVE-2025-2545 CVE-2025-30087

Source: request-tracker5 Version: 5.0.7+dfsg-2 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for request-tracker5. These should be fixed for the trixie release before release, so making them RC leve

Bug#1104411: gsasl: autopkgtests fail with dovecot 2.4

On Tue, Apr 29, 2025 at 10:22:21PM +0200, Simon Josefsson wrote: >Thanks for report!  Did you confirm that your new dovecot version has >working GSSAPI support, with some other client?  Or is this gsasl >autopkgtest the only one that test that functionality? Gsasl (and libgssglue) test

Bug#1104411: gsasl: autopkgtests fail with dovecot 2.4

Thanks for report! Did you confirm that your new dovecot version has working GSSAPI support, with some other client? Or is this gsasl autopkgtest the only one that test that functionality? I think the relevant dovecot errors are the one below, but the error reporting is not that great. Since

Bug#1101956: snap applications doesn't work after installation of gnome desktop environment

Hi, [Release Team member hat on] On Thu, 3 Apr 2025 11:40:39 +0200 Zygmunt Krynicki wrote: Since you have filed a bug both here and on launchpad, at https://bugs.launchpad.net/snapd/+bug/2105766, I have sent some more updates there. To my untrained eyes (I've never used snaps), this looks

Bug#1101534: marked as done (libxfce4ui-2-0: Suspend with screen lock does not work)

Your message dated Tue, 29 Apr 2025 22:14:05 +0200 with message-id <2ddd5528-9188-459a-965a-48f4a08ab...@debian.org> and subject line Re: libxfce4ui-2-0: Suspend with screen lock does not work has caused the Debian Bug report #1101534, regarding libxfce4ui-2-0: Suspend with screen lock does not wor

Processed: Re: libxfce4ui-2-0: Suspend with screen lock does not work

Processing commands for cont...@bugs.debian.org: > forwarded 1101534 https://gitlab.xfce.org/xfce/libxfce4ui/-/issues/131 Bug #1101534 [libxfce4ui-2-0] libxfce4ui-2-0: Suspend with screen lock does not work Set Bug forwarded-to-address to 'https://gitlab.xfce.org/xfce/libxfce4ui/-/issues/131'. >

Processed: tagging 1104351

Processing commands for cont...@bugs.debian.org: > tags 1104351 + upstream Bug #1104351 {Done: Chris Hofstaedtler } [src:dnsdist] dnsdist: CVE-2025-30194 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1104351: https://bugs.debian.org/cgi-b

Bug#1104413: labplot-2.12.0: segfaults on startup

Package: labplot Version: 2.12.0-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: volko...@crys.ras.ru Dear Maintainer, After upgrading LabPlot to version 2.12, the application cannot be launched anymore. Attempting to launch it from the command line leads to the instant

Bug#1103153: marked as done (linux-image-6.1.0-33-amd64: kernel fails to boot in xen DomU with pci-passthrough)

Your message dated Tue, 29 Apr 2025 19:32:09 + with message-id and subject line Bug#1102914: fixed in linux 6.1.135-1 has caused the Debian Bug report #1102914, regarding linux-image-6.1.0-33-amd64: kernel fails to boot in xen DomU with pci-passthrough to be marked as done. This means that y

Bug#1102889: marked as done (linux-image-6.1.0-33-amd64: KVM GPU passthrough broken)

Your message dated Tue, 29 Apr 2025 19:32:09 + with message-id and subject line Bug#1102914: fixed in linux 6.1.135-1 has caused the Debian Bug report #1102914, regarding linux-image-6.1.0-33-amd64: KVM GPU passthrough broken to be marked as done. This means that you claim that the problem ha

Bug#1102914: marked as done (VMs don't start up when being passed through a PCI device)

Your message dated Tue, 29 Apr 2025 19:32:09 + with message-id and subject line Bug#1102914: fixed in linux 6.1.135-1 has caused the Debian Bug report #1102914, regarding VMs don't start up when being passed through a PCI device to be marked as done. This means that you claim that the problem

Bug#1104411: gsasl: autopkgtests fail with dovecot 2.4

Source: gsasl Version: 2.2.0-1 Severity: serious Justification: autopkgtest regression Dovecot 2.4 is currently in unstable and trying to migrate to testing. It's currently blocked because its configuration file format changes introduce regressions in autopkgtests for some packages, including gsa

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

Hi, On 24-04-2025 11:24, Paul Gevers wrote: 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

Bug#1104325: esys-particle: missing builds on armel, armhf, i386 (BD-Uninstallable)

El 29/4/25 a las 15:19, Chris Hofstaedtler escribió: Can this be fixed by asking ftpmasters to drop the now unbuildable binaries, or does it require more uploads? (there are no reverse build-depends). Without knowing anything about the package in question, this seems correct. The only r-deps sh

Bug#1103348: marked as done (jcal: Change the souce code repo)

Your message dated Tue, 29 Apr 2025 18:00:10 + with message-id and subject line Bug#1103348: fixed in jcal 0.5.1-0.1 has caused the Debian Bug report #1103348, regarding jcal: Change the souce code repo to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#1103377: marked as done (java3d: FTBFS in testing/armel: [exec] /usr/bin/ld: cannot find -ljvm: No such file or directory)

Your message dated Tue, 29 Apr 2025 19:50:18 +0200 with message-id and subject line Re: java3d: FTBFS in testing/armel: [exec] /usr/bin/ld: cannot find -ljvm: No such file or directory has caused the Debian Bug report #1103377, regarding java3d: FTBFS in testing/armel: [exec] /usr/bin/ld: ca

Bug#1065719: marked as done (Useless in Debian nowadays)

Your message dated Tue, 29 Apr 2025 17:46:34 + with message-id and subject line Bug#1104301: Removed package(s) from unstable has caused the Debian Bug report #1065719, regarding Useless in Debian nowadays to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#1050580: marked as done (ruby-roxml: broken by ruby-nokogiri 1.15.4)

Your message dated Tue, 29 Apr 2025 17:45:30 + with message-id and subject line Bug#1104284: Removed package(s) from unstable has caused the Debian Bug report #1050580, regarding ruby-roxml: broken by ruby-nokogiri 1.15.4 to be marked as done. This means that you claim that the problem has be

Bug#1094549: marked as done (ruby-omniauth-shibboleth-redux: FTBFS: ERROR: Test "ruby3.3" failed.)

Your message dated Tue, 29 Apr 2025 17:41:41 + with message-id and subject line Bug#1104248: Removed package(s) from unstable has caused the Debian Bug report #1094549, regarding ruby-omniauth-shibboleth-redux: FTBFS: ERROR: Test "ruby3.3" failed. to be marked as done. This means that you cla

Bug#1094561: marked as done (ruby-vcr: FTBFS: ERROR: Test "ruby3.3" failed: cannot load such file -- rack/handler/webrick)

Your message dated Tue, 29 Apr 2025 17:40:14 + with message-id and subject line Bug#1104155: Removed package(s) from unstable has caused the Debian Bug report #1094561, regarding ruby-vcr: FTBFS: ERROR: Test "ruby3.3" failed: cannot load such file -- rack/handler/webrick to be marked as don

Bug#1103092: marked as done (ruby-ffi-libarchive: FTBFS in testing/i386: ERROR: Test "ruby3.3" failed.)

Your message dated Tue, 29 Apr 2025 17:40:44 + with message-id and subject line Bug#1104175: Removed package(s) from unstable has caused the Debian Bug report #1103092, regarding ruby-ffi-libarchive: FTBFS in testing/i386: ERROR: Test "ruby3.3" failed. to be marked as done. This means that y

Bug#1084365: marked as done (ruby-redis-rack: FTBFS: Expected /127.0.0.1:6379 against DB 0$/ to match "Redis Client connected to localhost:6379 against DB 0".)

Your message dated Tue, 29 Apr 2025 17:39:46 + with message-id and subject line Bug#1104153: Removed package(s) from unstable has caused the Debian Bug report #1084365, regarding ruby-redis-rack: FTBFS: Expected /127.0.0.1:6379 against DB 0$/ to match "Redis Client connected to localhost:6379

Bug#1102288: marked as done (ruby-integration: FTBFS: Expected pending 'GSL not available' to fail. No error was raised.)

Your message dated Tue, 29 Apr 2025 17:41:14 + with message-id and subject line Bug#1104196: Removed package(s) from unstable has caused the Debian Bug report #1102288, regarding ruby-integration: FTBFS: Expected pending 'GSL not available' to fail. No error was raised. to be marked as done.

Bug#1103118: marked as done (r-cran-timechange: should depend on R>=4.5)

Your message dated Tue, 29 Apr 2025 17:23:00 + with message-id and subject line Bug#1103118: fixed in r-cran-timechange 0.3.0-2 has caused the Debian Bug report #1103118, regarding r-cran-timechange: should depend on R>=4.5 to be marked as done. This means that you claim that the problem has

Bug#1103369: marked as done (r-cran-webgestaltr: FTBFS in testing/armhf: make: *** [debian/rules:4: binary-arch] Error 25)

Your message dated Tue, 29 Apr 2025 17:22:53 + with message-id and subject line Bug#1103369: fixed in r-cran-svglite 2.1.3-2 has caused the Debian Bug report #1103369, regarding r-cran-webgestaltr: FTBFS in testing/armhf: make: *** [debian/rules:4: binary-arch] Error 25 to be marked as done.

Bug#1104338: marked as done (r-cran-plotly: test-Depends on r-cran-dendextend which is not in testing)

Your message dated Tue, 29 Apr 2025 17:22:35 + with message-id and subject line Bug#1104338: fixed in r-cran-plotly 4.10.4+dfsg-3 has caused the Debian Bug report #1104338, regarding r-cran-plotly: test-Depends on r-cran-dendextend which is not in testing to be marked as done. This means tha

Bug#1102591: marked as done (src:r-cran-units: fails to migrate to testing for too long)

Your message dated Tue, 29 Apr 2025 17:23:08 + with message-id and subject line Bug#1102591: fixed in r-cran-units 0.8-7+dfsg-2 has caused the Debian Bug report #1102591, regarding src:r-cran-units: fails to migrate to testing for too long to be marked as done. This means that you claim that

Bug#1100250: Bug#1101420: pgpainless still waiting for bouncycastle

On Sun, Apr 27, 2025 at 06:27:51PM +0200, Chris Hofstaedtler wrote: > Hi, > > On Sat, Apr 26, 2025 at 06:08:20PM +, tony mancill wrote: > > On Fri, Apr 25, 2025 at 11:15:03PM +0200, Martin Hostettler wrote: > > > Bump to avoid auto removal due to unsolved RC bug in key package > > > bouncycas

Bug#1104045: marked as done (ipython3: ipython3 crashes on startup)

Your message dated Tue, 29 Apr 2025 09:39:13 -0700 with message-id <87frhqhqha@secretsauce.net> and subject line Re: Bug#1104045: ipython3 crash has caused the Debian Bug report #1104045, regarding ipython3: ipython3 crashes on startup to be marked as done. This means that you claim that the p

Bug#1104042: android-udev-rules: wrong version number in breaks/replaces for g-a-platform-tools-installer

Hello Andrea, Thanks for your reply. I won't be of big help, I'm not a DD, not even a DM. Hopefully you can find some to fix & upload this. Regards Fab Le mardi 29 avril 2025 18:06:31 CEST, vous avez écrit : > Hi Fab, I'm a bit short on time. Feel free to upload the fix yourself, the > package

Bug#1104042: android-udev-rules: wrong version number in breaks/replaces for g-a-platform-tools-installer

Hi Fab, I'm a bit short on time. Feel free to upload the fix yourself, the package is team maintained and I'm in the LowThresholdNMU list! Bye :) Il 29 aprile 2025 08:32:41 CEST, Fab Stz ha scritto: >control: severity -1 serious > >Hello Andrea, > >Could you please fix this bug affecting the c

Bug#1104351: marked as done (dnsdist: CVE-2025-30194)

Your message dated Tue, 29 Apr 2025 17:14:32 +0200 with message-id and subject line Accepted dnsdist 1.9.9-1 (source) into unstable has caused the Debian Bug report #1104351, regarding dnsdist: CVE-2025-30194 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#1104376: marked as done (code: Crash at extensions menu rendering)

Your message dated Tue, 29 Apr 2025 17:04:41 +0200 with message-id and subject line Re: Bug#1104376: code: Crash at extensions menu rendering has caused the Debian Bug report #1104376, regarding code: Crash at extensions menu rendering to be marked as done. This means that you claim that the pro

Bug#1103118: r-cran-timechange: should depend on R>=4.5

* Chris Hofstaedtler [250429 17:24]: * Rebecca N. Palmer [250429 17:21]: This isn't a 32-bit problem as such - it's another package that picked up the R_getVar symbol (new in R 4.5) when it was binNMUd on some architectures. (The other known one is r-cran-svglite #1103369. Like that one, t

Bug#1103282: marked as done (hwloc-contrib: FTBFS hwloc_type_sscanf: hwloc_type_sscanf.c:40: _check: Assertion `depth == (int) obj->depth' failed.)

Your message dated Tue, 29 Apr 2025 17:23:42 +0200 with message-id and subject line Re: Bug#1103282: hwloc-contrib: FTBFS hwloc_type_sscanf: hwloc_type_sscanf.c:40: _check: Assertion `depth == (int) obj->depth' failed. has caused the Debian Bug report #1103282, regarding hwloc-contrib: FTBFS hwlo

Bug#1103118: r-cran-timechange: should depend on R>=4.5

* Rebecca N. Palmer [250429 17:21]: This isn't a 32-bit problem as such - it's another package that picked up the R_getVar symbol (new in R 4.5) when it was binNMUd on some architectures. (The other known one is r-cran-svglite #1103369. Like that one, the best we can do after the fact is to

Processed: severity of 1067828 is important

Processing commands for cont...@bugs.debian.org: > severity 1067828 important Bug #1067828 [src:tlog] tlog: FTBFS on arm{el,hf}: FAIL: 3 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1067828: https://bugs.debian.org/cg

Processed: severity of 1066825 is important

Processing commands for cont...@bugs.debian.org: > severity 1066825 important Bug #1066825 [src:alsa-oss] alsa-oss: FTBFS on arm{el,hf}: error: ‘__open’ aliased to undefined symbol ‘open’ Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need

Processed: r-cran-timechange: should depend on R>=4.5

Processing control commands: > reopen -1 Bug #1103118 {Done: Charles Plessy } [src:r-cran-caret] r-cran-caret: FTBFS in testing/i386: make: *** [debian/rules:4: binary] Error 25 Bug reopened Ignoring request to alter fixed versions of bug #1103118 to the same values previously set > retitle -1 r

Bug#1103118: r-cran-timechange: should depend on R>=4.5

Control: reopen -1 Control: retitle -1 r-cran-timechange: should depend on R>=4.5 Control: reassign -1 r-cran-timechange Control: affects -1 r-cran-caret r-cran-dbitest r-cran-epir Control: affects -1 + r-cran-lubridate r-cran-recipes Control: affects -1 + r-cran-themis r-cran-tidyverse This isn'

Processed: affects 1104374

Processing commands for cont...@bugs.debian.org: > affects 1104374 + eztrace Bug #1104374 [mpich] fails to run basic ping test Added indication that 1104374 affects eztrace > thanks Stopping processing here. Please contact me if you need assistance. -- 1104374: https://bugs.debian.org/cgi-bin/bu

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

Pinging on this bug in hopes of resetting the RM counter. I will upload with tests on s390x disabled if FTP master does not remove it from s90x by May 4 as req in #1103595 Thanks, Nilesh

Bug#1104363: marked as done (rdkit: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.)

rce: rdkit Version: 202503.1-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules clean > pg_build

Processed: Re: Bug#1104374: eztrace: FTBFS: 2: [OTF2] src/otf2_archive_int.c:3948: error: File does already exist: Could not create archive trace directory!

Processing control commands: > reassign -1 mpich Bug #1104374 [src:eztrace] eztrace: FTBFS: 2: [OTF2] src/otf2_archive_int.c:3948: error: File does already exist: Could not create archive trace directory! Bug reassigned from package 'src:eztrace' to 'mpich'. No longer marked as found in versions

Bug#1104374: eztrace: FTBFS: 2: [OTF2] src/otf2_archive_int.c:3948: error: File does already exist: Could not create archive trace directory!

Control: reassign -1 mpich Control: retitle -1 fails to run basic ping test Hello, Lucas Nussbaum, le mar. 29 avril 2025 14:48:49 +0200, a ecrit: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): The real reason is just before tha

Bug#1104376: code: Crash at extensions menu rendering

Package: code Version: 1.99.3-1744761595 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: fritzmat...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Using ms reppo

Bug#1104367: rtpengine: FTBFS: make[2]: *** [../lib/common.Makefile:62: dtmf_rx_fillin.h] Error 1

: rtpengine Version: 12.5.1.30-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[3]: Entering directory

Bug#1104271: sm has an undeclared file conflict on /usr/share/man/man1/sm.1.gz

On 28 April 2025 at 16:09, Helmut Grohne wrote: | Hi Dirk, | | On Mon, Apr 28, 2025 at 08:46:12AM -0500, Dirk Eddelbuettel wrote: | > On 28 April 2025 at 06:00, Helmut Grohne wrote: | > | Package: sm | > | Version: 0.29-1 | | > You once again filed against the wrong (source) package sm with bin

Processed: fixed 1104351 in 1.9.9-1

Processing commands for cont...@bugs.debian.org: > fixed 1104351 1.9.9-1 Bug #1104351 [src:dnsdist] dnsdist: CVE-2025-30194 The source 'dnsdist' and version '1.9.9-1' do not appear to match any binary packages Marked as fixed in versions dnsdist/1.9.9-1. > thanks Stopping processing here. Please

Processed: found 1104351 in 1.9.8-1

Processing commands for cont...@bugs.debian.org: > found 1104351 1.9.8-1 Bug #1104351 [src:dnsdist] dnsdist: CVE-2025-30194 Marked as found in versions dnsdist/1.9.8-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1104351: https://bugs.debian.org/cgi-bin/bugrep

debian-bugs-rc@lists.debian.org

Source: fiat-ecmwf Version: 1.4.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /build/reproduci

Bug#1104368: compyle: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.13 returned exit code 13

Source: compyle Version: 0.8.1-10 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules bin

Bug#1104371: dovecot-antispam: FTBFS: dovecot-version.h:17:49: fatal error: antispam-storage-2.4.c: No such file or directory

Source: dovecot-antispam Version: 2.0+20171229-1.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): >

Bug#1104370: ruby-spy: FTBFS: unsatisfiable build-dependency: pry (< 0.15) but 0.15.2-1 is to be installed

Source: ruby-spy Version: 1.0.1-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#1104369: email-reminder: FTBFS: PermissionError: [Errno 13] Permission denied: 'debian/email-reminder/usr/bin/email-reminder-editor'

Source: email-reminder Version: 0.8.3-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Enter

Bug#1104366: rtorrent: FTBFS: configure: error: Could not compile XMLRPC-C test.

Source: rtorrent Version: 0.9.8-1.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for work

Bug#1104367: rtpengine: FTBFS: make[2]: *** [../lib/common.Makefile:62: dtmf_rx_fillin.h] Error 1

Source: rtpengine Version: 12.5.1.30-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Enter

Bug#1104360: perlimports: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2

Source: perlimports Version: 0.56-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Enter

Bug#1104364: snek: FTBFS: ./arm-none-eabi/../../../newlib/libc/tinystdio/puts.c:63:(.text.puts+0x3c): undefined reference to `stdout'

Source: snek Version: 1.11-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/lib/gcc/arm-none-e

Bug#1104362: flowgrind: FTBFS: ld: cannot find -lxmlrpc_xmlparse: No such file or directory

Source: flowgrind Version: 0.8.2-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cc -Wall -Wex

Bug#1104365: metview: FTBFS: MeshCache.cc:24:49: error: 'Resource' is not a member of 'eckit'

Source: metview Version: 5.25.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /build/reproduci

Bug#1104363: rdkit: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.

Source: rdkit Version: 202503.1-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules cl

Bug#1104361: ecmwflibs: FTBFS: ImportError: /lib/x86_64-linux-gnu/libodccore.so.0d: undefined symbol: _ZN5eckit14NotImplementedC1ERKNS_12CodeLocationE

Source: ecmwflibs Version: 2:0.6.3-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules bin

Bug#1104359: ruby-android-key-attestation: FTBFS: unsatisfiable build-dependency: pry (< 0.15) but 0.15.2-1 is to be installed

Source: ruby-android-key-attestation Version: 0.3.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#1104353: libsys-cpuload-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2

Source: libsys-cpuload-perl Version: 0.32-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > mak

Bug#1104358: ectrans: FTBFS: collect2: error: ld returned 1 exit status

Source: ectrans Version: 1.6.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: /lib/x86

debian-bugs-rc@lists.debian.org

Source: metkit Version: 1.13.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /build/reproduci

Bug#1104356: xmlgraphics-commons: FTBFS: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.maven.plugins:maven-project-info-reports-plugin:jar:2

Source: xmlgraphics-commons Version: 2.10-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/ru

Bug#1104357: lvm2: FTBFS: PermissionError: [Errno 13] Permission denied: 'debian/lvm2-dbusd/usr/sbin/lvmdbusd'

Source: lvm2 Version: 2.03.31-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Enter

debian-bugs-rc@lists.debian.org

Source: fdb Version: 5.15.12-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250429 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /build/reproducible-p

Bug#1104325: esys-particle: missing builds on armel, armhf, i386 (BD-Uninstallable)

On Tue, Apr 29, 2025 at 02:07:56PM +0200, Santiago Vila wrote: > Thanks for the report, I was actually thinking about reporting this myself > to get some help. > > El 29/4/25 a las 3:09, Chris Hofstaedtler escribió: > > esys-particle previously built on all archs, but now cannot build on armel, >

Bug#1104351: dnsdist: CVE-2025-30194

Source: dnsdist X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for dnsdist. CVE-2025-30194[0]: | When DNSdist is configured to provide DoH via the nghttp2 provider, | an attacker can cause a denial of service by crafting a DoH

Bug#1101992: ping

Tracker currently says: Marked for autoremoval on 03 May: #1101992, #946206 This ping is just to see if it postpones the autoremoval for some days, as I'm still unsure about how the current problems should be fixed. Thanks.

Bug#1104325: esys-particle: missing builds on armel, armhf, i386 (BD-Uninstallable)

Hi. Thanks for the report, I was actually thinking about reporting this myself to get some help. El 29/4/25 a las 3:09, Chris Hofstaedtler escribió: Source: esys-particle Version: 2.3.5+dfsg2-10 Severity: serious Tags: ftbfs X-Debbugs-CC: sanv...@debian.org (CCing Santiago as the last Uploader.

Processed: automake-1.17: autopkgtests time out on armel

Processing commands for cont...@bugs.debian.org: > severity 1104245 important Bug #1104245 [src:automake-1.17] automake-1.17: autopkgtests time out on armel Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1104245: https:/

Bug#1104245: automake-1.17: autopkgtests time out on armel

severity 1104245 important thanks Not happening anymore apparently, but not confident enough that it's fixed to close the bug. Thanks.

Bug#1104081: hiki: does not work for Trixie with Ruby 3.3

On Fri, 25 Apr 2025 12:03:46 +0200 William Desportes wrote: Package: hiki Version: 1.0.0-2.1 Severity: serious Tags: sid, trixie Found: 1.0.0-2 Ruby 3.2 removed taint and untaint methods: https://bugs.ruby-lang.org/issues/16131#note-3 I installed hiki today, and it outputs this in the browser

  1   2   >