Processed: Re: Bug#1086999: pixman: Some tests take > 120 seconds to complete on some arches

2024-11-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1086999 serious Bug #1086999 [src:pixman] pixman: Some tests take > 120 seconds to complete on some arches Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 10869

Bug#1082379: marked as done (puma: CVE-2024-45614)

2024-11-07 Thread Debian Bug Tracking System
Your message dated Fri, 08 Nov 2024 07:04:24 + with message-id and subject line Bug#1082379: fixed in puma 6.4.3-1 has caused the Debian Bug report #1082379, regarding puma: CVE-2024-45614 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#1086462: marked as done (src:gcc-riscv64-unknown-elf: fails to migrate to testing for too long)

2024-11-07 Thread Debian Bug Tracking System
Your message dated Fri, 08 Nov 2024 07:04:04 + with message-id and subject line Bug#1086462: fixed in gcc-riscv64-unknown-elf 14 has caused the Debian Bug report #1086462, regarding src:gcc-riscv64-unknown-elf: fails to migrate to testing for too long to be marked as done. This means that you

Bug#1086670: src:tzdata: fails to migrate to testing for too long

2024-11-07 Thread Paul Gevers
Hi Santiago, On 08-11-2024 02:50, Santiago Vila wrote: So: Could some Release Manager evaluate if we really need Bug #1084190 at this point? My hint for tzdata [1], which is in place since 2024-11-02, implicitly defers this judgement call for now to the maintainers, which should be the first

Bug#1086936: marked as done (wand: build against imagemagick 7)

2024-11-07 Thread Debian Bug Tracking System
Your message dated Fri, 08 Nov 2024 06:19:29 + with message-id and subject line Bug#1086936: fixed in wand 0.6.11-5 has caused the Debian Bug report #1086936, regarding wand: build against imagemagick 7 to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#1082688: marked as done (node-shiny-server: FTBFS: TypeError: Cannot read properties of undefined (reading 'define'))

2024-11-07 Thread Debian Bug Tracking System
Your message dated Fri, 08 Nov 2024 05:48:58 + with message-id and subject line Bug#1082688: fixed in node-shiny-server 1.5.20.1002-3 has caused the Debian Bug report #1082688, regarding node-shiny-server: FTBFS: TypeError: Cannot read properties of undefined (reading 'define') to be marked a

Bug#1087010: prime-phylo:FTBFS:build failure (Imported target "MPI::MPI_Fortran" includes non-existent path )

2024-11-07 Thread Yue Gui
Source: prime-phylo Version: 1.0.11-13 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear prime-phylo Maintainer, The package prime-phylo build failed on all architectures except amd64. The crucial buildd log

Bug#1087008: raku-test-meta, raku-license-spdx: File conflict causes unpack failure

2024-11-07 Thread Guillem Jover
Package: raku-test-meta, raku-license-spdx Severity: serious Hi! These packages contain a pathname conflict which makes them fail to unpack. Here's what I got while upgrading rakudo today: ,--- Unpacking raku-test-meta (0.0.17-1+b3) over (0.0.17-1+b2) ... dpkg: error processing archive /t

Bug#1086670: src:tzdata: fails to migrate to testing for too long

2024-11-07 Thread Santiago Vila
Hello. One of the reasons tzdata will not migrate to testing is that it has an artificial bug preventing it from doing so: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084190 In my opinion (after reporting several tzdata-related bugs and also fixing some of them), the breakage introduced

Processed: golang-github-k0swe-wsjtx-go: FTBFS: randomly (failing tests)

2024-11-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1066758 golang-github-k0swe-wsjtx-go: FTBFS randomly (failing tests) Bug #1066758 [src:golang-github-k0swe-wsjtx-go] golang-github-k0swe-wsjtx-go: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/k0swe/wsjtx-g

Bug#1066758: golang-github-k0swe-wsjtx-go: FTBFS: randomly (failing tests)

2024-11-07 Thread Santiago Vila
retitle 1066758 golang-github-k0swe-wsjtx-go: FTBFS randomly (failing tests) severity 1066758 important thanks Hello. I can build this package quite reliably, but in my setup (using machines with 1 CPU and 2 CPUs). I don't have time right now to test in a machine with 8 CPUs, but I believe this

Bug#1086269: marked as done (golang-github-spf13-cast: FTBFS: FAIL: TestToTimeWithTimezones)

2024-11-07 Thread Debian Bug Tracking System
Your message dated Fri, 08 Nov 2024 00:05:57 + with message-id and subject line Bug#1086269: fixed in golang-github-spf13-cast 1.6.0-2 has caused the Debian Bug report #1086269, regarding golang-github-spf13-cast: FTBFS: FAIL: TestToTimeWithTimezones to be marked as done. This means that you

Bug#1082745: [Aptitude-devel] Bug#1082745: aptitude: information mismatch for package removal

2024-11-07 Thread Axel Beckert
Control: clone -1 -2 Control: retitle -1 aptitude: Marks some autoinstalled dependencies not immediately for removal if last reverse dependency is removed (but switching rev-dep from removal to purging helps) Control: severity -1 important Control: tag -1 + help Control: retitle -2 aptitude: TUI

Processed: Re: [Aptitude-devel] Bug#1082745: aptitude: information mismatch for package removal

2024-11-07 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 Bug #1082745 [aptitude] aptitude: removes a kernel package not requested to be removed Bug 1082745 cloned as bug 1087005 > retitle -1 aptitude: Marks some autoinstalled dependencies not immediately > for removal if last reverse dependency is removed (bu

Processed: Bug#1086269 marked as pending in golang-github-spf13-cast

2024-11-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1086269 [src:golang-github-spf13-cast] golang-github-spf13-cast: FTBFS: FAIL: TestToTimeWithTimezones Added tag(s) pending. -- 1086269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086269 Debian Bug Tracking System Contact ow...@bugs.debi

Bug#1086269: marked as pending in golang-github-spf13-cast

2024-11-07 Thread Santiago Vila
Control: tag -1 pending Hello, Bug #1086269 in golang-github-spf13-cast reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/golang-github-spf13-cas

Bug#1084262: marked as done (golang-github-vulcand-oxy: FTBFS: FAIL: TestParseRFC822Time/Sun,_31_Oct_2021_12:10_-5000 (0.00s))

2024-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2024 23:49:17 + with message-id and subject line Bug#1084262: fixed in golang-github-vulcand-oxy 2.0.0-2 has caused the Debian Bug report #1084262, regarding golang-github-vulcand-oxy: FTBFS: FAIL: TestParseRFC822Time/Sun,_31_Oct_2021_12:10_-5000 (0.00s) to be m

Processed: Bug#1084262 marked as pending in golang-github-vulcand-oxy

2024-11-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1084262 [src:golang-github-vulcand-oxy] golang-github-vulcand-oxy: FTBFS: FAIL: TestParseRFC822Time/Sun,_31_Oct_2021_12:10_-5000 (0.00s) Added tag(s) pending. -- 1084262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084262 Debian Bug Trac

Bug#1084262: marked as pending in golang-github-vulcand-oxy

2024-11-07 Thread Santiago Vila
Control: tag -1 pending Hello, Bug #1084262 in golang-github-vulcand-oxy reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/golang-github-vulcand-

Bug#1086266: marked as done (fop: FTBFS: ect fop-core: Compilation failure)

2024-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2024 23:19:25 + with message-id and subject line Bug#1086266: fixed in fop 1:2.10+dfsg-1 has caused the Debian Bug report #1086266, regarding fop: FTBFS: ect fop-core: Compilation failure to be marked as done. This means that you claim that the problem has been

Bug#1086270: marked as done (golang-github-teambition-rrule-go: FTBFS: FAIL github.com/teambition/rrule-go)

2024-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2024 23:04:12 + with message-id and subject line Bug#1086270: fixed in golang-github-teambition-rrule-go 1.8.1-2 has caused the Debian Bug report #1086270, regarding golang-github-teambition-rrule-go: FTBFS: FAIL github.com/teambition/rrule-go to be marked as do

Bug#1086270: golang-github-teambition-rrule-go: FTBFS: FAIL github.com/teambition/rrule-go

2024-11-07 Thread Santiago Vila
El 7/11/24 a las 22:37, Aurelien Jarno escribió: Santiago, would it be possible to do a team upload with this patch as you just did for reposurgeon? Done. Thanks a lot.

Bug#1086270: marked as pending in golang-github-teambition-rrule-go

2024-11-07 Thread Santiago Vila
Control: tag -1 pending Hello, Bug #1086270 in golang-github-teambition-rrule-go reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/golang-github

Processed: Bug#1086270 marked as pending in golang-github-teambition-rrule-go

2024-11-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1086270 [src:golang-github-teambition-rrule-go] golang-github-teambition-rrule-go: FTBFS: FAIL github.com/teambition/rrule-go Added tag(s) pending. -- 1086270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086270 Debian Bug Tracking System

Bug#1076172: marked as done (pixman: FTBFS on armhf: Error: garbage following instruction -- `bne 01f')

2024-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2024 23:15:45 +0100 with message-id <12594627.O9o76ZdvQC@bagend> and subject line Re: pixman: FTBFS on armhf: Error: garbage following instruction -- `bne 01f' has caused the Debian Bug report #1076172, regarding pixman: FTBFS on armhf: Error: garbage following instr

Bug#1086912: [Debian-med-packaging] Bug#1086912: phyml: depends on openmpi on 32-bit architectures

2024-11-07 Thread Étienne Mollier
Hi Emilio, po...@debian.org, on 2024-11-07: > phyml depends on openmpi on 32-bit architectures, which has been > removed in openmpi 5. Thus this package needs to stop depending on it > on those architectures. Thanks for the report, in the case of phyml, there is probably a bit of work involved.

Bug#1085354: closed by Debian FTP Masters (reply to Andrea Pappacoda ) (Bug#1085354: fixed in mbedtls 3.6.2-2)

2024-11-07 Thread Bastian Germann
On Wed, 6 Nov 2024 14:39:19 +0200 Adrian Bunk wrote: > Upstream might be qualified to determine whether this is an mbedtls or gcc bug. > > The easiest short-term workaround to unblock the transition is > export DEB_CFLAGS_MAINT_APPEND = -Wno-error=array-bounds This suggestion from my ori

Processed: Re: Bug#1086270: golang-github-teambition-rrule-go: FTBFS: FAIL github.com/teambition/rrule-go

2024-11-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + patch Bug #1086270 [src:golang-github-teambition-rrule-go] golang-github-teambition-rrule-go: FTBFS: FAIL github.com/teambition/rrule-go Added tag(s) patch. -- 1086270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086270 Debian Bug Tracking System C

Bug#1086290: Bug#695178: fixed in psutils 1.17.dfsg-5

2024-11-07 Thread Ian Jackson
Andreas Tille writes ("Bug#695178: fixed in psutils 1.17.dfsg-5"): > The only immediate fix for the FTBFS in log4c I can imagine would be to > revert the patch for psutils. If you agree I can easily do so ... or > you can do it as well since finally the package is in debian/ team > space. FTR: I

Bug#1085992: gtklock: fails to run "Your compositor doesn't support wlr-input-inhibitor"

2024-11-07 Thread Matthias Geiger
On Thu, 24 Oct 2024 14:13:30 +0200 Matthias Geiger wrote: Package: gtklock > Version: 2.1.0-1+b2 > Severity: grave > X-Debbugs-Cc: werdah...@debian.org > gtklock stopped working for me; it displays the following error: ** (gtklock:31406): CRITICAL **: 14:12:28.943: Your compositor doesn't su

Bug#1086270: golang-github-teambition-rrule-go: FTBFS: FAIL github.com/teambition/rrule-go

2024-11-07 Thread Aurelien Jarno
control: tag -1 + patch Hi, On 2024-10-29 19:26, Santiago Vila wrote: > Package: src:golang-github-teambition-rrule-go > Version: 1.8.1-1 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > During a rebuild of all packages in unstable, your package failed to build: > ... > === RUN T

Bug#1066603: hashcash: FTBFS: fastmint_library.c:92:17: error: implicit declaration of function ‘SHA1_Transform’; did you mean ‘SHA1_Xform’? [-Werror=implicit-function-declaration]

2024-11-07 Thread Bastian Germann
I see this is fixed in git with https://salsa.debian.org/skangas/hashcash/-/commit/8cc5e83f772c254ece85999e284e7e82ae0a65e1 Please upload a new revision.

Bug#1075201: marked as done (libre: ftbfs with GCC-14)

2024-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2024 20:43:34 + with message-id and subject line Bug#1075201: fixed in libre 2.0.1-3 has caused the Debian Bug report #1075201, regarding libre: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Processed: reassign 1077055 to src:rdkit, tagging 1086934, found 1086934 in 2.2.0-3, found 1086941 in 0.96.0-2 ...

2024-11-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1077055 src:rdkit Bug #1077055 [rdkit] postgresql-16-rdkit: inchi support not included in rdkit build Bug reassigned from package 'rdkit' to 'src:rdkit'. Ignoring request to alter found versions of bug #1077055 to the same values previo

Bug#1086932: jhead: build against imagemagick 7

2024-11-07 Thread pochu
Source: jhead Severity: serious Hi, jhead is still built against imagemagick 6, but we're transitioning to imagemagick 7, see [1]. Your package may be build-depending on imagemagick 6 binaries (e.g. libmagickwand-6.q16-dev), in which case it should switch to the new binary packages, or generic o

Processed: retitle 1078221 to unicon license issues

2024-11-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # fix typo > retitle 1078221 unicon license issues Bug #1078221 {Done: Boyuan Yang } [unicon] uniicon license issues Changed Bug title to 'unicon license issues' from 'uniicon license issues'. > thanks Stopping processing here. Please contact me

Bug#1078221: marked as done (uniicon license issues)

2024-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2024 19:52:57 + with message-id and subject line Bug#1078221: fixed in unicon 3.0.4+dfsg1-7 has caused the Debian Bug report #1078221, regarding uniicon license issues to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: update bug metadata

2024-11-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 1078221 Bug #1078221 {Done: Phil Wyett } [unicon] uniicon license issues Unarchived Bug 1078221 > reopen 1078221 Bug #1078221 {Done: Phil Wyett } [unicon] uniicon license issues Bug reopened Ignoring request to alter fixed versions of

Processed: closing 1082995

2024-11-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1082995 1.5.0~rc0-3 Bug #1082995 [src:postgresql-16-age] postgresql-16-age: FTBFS: pg_buildext: error: /usr/lib/postgresql/16/bin/pg_config does not exist Marked as fixed in versions postgresql-16-age/1.5.0~rc0-3. Bug #1082995 [src:postgres

Bug#1072401: marked as done (baresip: FTBFS with ffmpeg 7.0: modules/avformat/audio.c:104:49: error: ‘AVCodecContext’ has no member named ‘channels’)

2024-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2024 19:19:00 + with message-id and subject line Bug#1072401: fixed in baresip 1.1.0-2 has caused the Debian Bug report #1072401, regarding baresip: FTBFS with ffmpeg 7.0: modules/avformat/audio.c:104:49: error: ‘AVCodecContext’ has no member named ‘channels’ to

Bug#1086290: Bug#695178: fixed in psutils 1.17.dfsg-5

2024-11-07 Thread Andreas Tille
Hi, Am Thu, Nov 07, 2024 at 08:34:47AM +0100 schrieb Petter Reinholdtsen: > I suspect this fix to psnup caused the build problem in > https://bugs.debian.org/1086290 >. Do not know how or how to > fix it. > > The Makefile code in question is generated by Doxygen, so not straight > forward to fix

Bug#1086946: icewm FTBFS with the nocheck build profile: No rule to make target 'strtest'. Stop.

2024-11-07 Thread Helmut Grohne
Source: icewm Version: 3.6.0-1 Severity: serious Justification: nocheck ftbfs is rc since trixie Tags: ftbfs trixie sid Hi, icewm fails to build from source when enabling the nocheck build profile. A build ends as follows: | [100%] Linking CXX executable ../icewm | cd /<>/obj-x86_64-linux-gnu/sr

Bug#1075979: [Help] molds: FTBFS with mpich as default MPI provider: /usr/bin/ld: cannot find -lmpi_cxx: No such file or directory

2024-11-07 Thread Andreas Tille
Control: tags -1 help Thanks Hi, today molds (from Debichem team) came up as candidate for the Bug of the Day[1]. I considered bug #1075979 easy to fix by simply adding libopenmpi-dev to Build-Depends since $ apt-file search libmpi_cxx.so | grep -- -dev libopenmpi-dev: /usr/lib/x86_64-linux-gnu

Processed: [Help] molds: FTBFS with mpich as default MPI provider: /usr/bin/ld: cannot find -lmpi_cxx: No such file or directory

2024-11-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 help Bug #1075979 [src:molds] molds: FTBFS with mpich as default MPI provider: /usr/bin/ld: cannot find -lmpi_cxx: No such file or directory Added tag(s) help. -- 1075979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075979 Debian Bug Tracking System

Bug#1086934: kxstitch: build against imagemagick 7

2024-11-07 Thread pochu
Source: kxstitch Severity: serious Hi, kxstitch is still built against imagemagick 6, but we're transitioning to imagemagick 7, see [1]. Your package may be build-depending on imagemagick 6 binaries (e.g. libmagickwand-6.q16-dev), in which case it should switch to the new binary packages, or gen

Bug#1085704: Bug#1084230: xvfb: please consider disabling libunwind, at least on armhf

2024-11-07 Thread Simon McVittie
Control: tags -1 + patch On Sun, 06 Oct 2024 at 23:15:55 +0100, Simon McVittie wrote: > Until libunwind can be investigated and fixed (presumably by a porter?), > I think it would be better to disable this optional feature on armhf, > so that X11-related packages can rely on being able to use Xvfb

Processed: Re: Bug#1086934: kxstitch: build against imagemagick 7

2024-11-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + moreinfo Bug #1086934 [src:kxstitch] kxstitch: build against imagemagick 7 Added tag(s) moreinfo. -- 1086934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1074887: marked as done (clisp: ftbfs with GCC-14)

2024-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 7 Nov 2024 19:40:29 +0100 with message-id <3b551618-3e16-453e-9449-eb01b3d77...@debian.org> and subject line Re: clisp: ftbfs with GCC-14 has caused the Debian Bug report #1074887, regarding clisp: ftbfs with GCC-14 to be marked as done. This means that you claim that the p

Bug#1066652: marked as done (xjobs: FTBFS: xjobs.c:242:16: error: implicit declaration of function ‘gettimeofday’ [-Werror=implicit-function-declaration])

2024-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2024 18:49:26 + with message-id and subject line Bug#1066652: fixed in xjobs 20241010-1 has caused the Debian Bug report #1066652, regarding xjobs: FTBFS: xjobs.c:242:16: error: implicit declaration of function ‘gettimeofday’ [-Werror=implicit-function-declarati

Bug#1075291: [patch, pending] mpg321: ftbfs with GCC-14

2024-11-07 Thread Andreas Tille
Hi Andreas, Am Thu, Nov 07, 2024 at 07:32:52PM +0100 schrieb Andreas Metzler: > > Well, my motivation was a popcon (vote!) > 100 to think there are some > > users. I'm aware that upstream is dead but we have other packages > > with dead upstream in Debian with way less users (and way more effort

Bug#1075291: [patch, pending] mpg321: ftbfs with GCC-14

2024-11-07 Thread Andreas Metzler
On 2024-11-06 Andreas Tille wrote: > Am Wed, Nov 06, 2024 at 06:40:41PM +0100 schrieb Andreas Metzler: >> Are you really convinced we would not be better off dropping this >> from Debian instead? mpg321 is stone-dead upstream (last commit about 12 >> years ago), alternatives with active upstream e

Bug#1066274: marked as done (aa3d: FTBFS: aa3d.c:37:30: error: implicit declaration of function ‘strcmp’ [-Werror=implicit-function-declaration])

2024-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2024 18:04:06 + with message-id and subject line Bug#1066274: fixed in aa3d 1.0-8.3 has caused the Debian Bug report #1066274, regarding aa3d: FTBFS: aa3d.c:37:30: error: implicit declaration of function ‘strcmp’ [-Werror=implicit-function-declaration] to be mar

Bug#1000089: clisp: depends on obsolete pcre3 library

2024-11-07 Thread Bastian Germann
Hi Peter, If you want clisp to be released with trixie, you should make sure to migrate away from pcre3. With your recent uploads overriding my NMU, it is going to disappear from testing soon. Thanks, Bastian

Bug#1085459: marked as done (trippy - upcoming rust-nix update)

2024-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2024 18:13:30 + with message-id and subject line Bug#1085459: fixed in trippy 0.11.0+dfsg-4 has caused the Debian Bug report #1085459, regarding trippy - upcoming rust-nix update to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1085968: marked as done (nvidia-graphics-drivers: CVE-2024-0126)

2024-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2024 17:49:58 + with message-id and subject line Bug#1085968: fixed in nvidia-graphics-drivers 535.216.01-1 has caused the Debian Bug report #1085968, regarding nvidia-graphics-drivers: CVE-2024-0126 to be marked as done. This means that you claim that the probl

Processed: Re: Bug#1086934: kxstitch: build against imagemagick 7

2024-11-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + moreinfo Bug #1086934 [src:kxstitch] kxstitch: build against imagemagick 7 Ignoring request to alter tags of bug #1086934 to the same tags previously set -- 1086934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086934 Debian Bug Tracking System Cont

Bug#1086934: kxstitch: build against imagemagick 7

2024-11-07 Thread Aurélien COUDERC
control: tags -1 + moreinfo Dear Emilio, Le jeudi 7 novembre 2024, 12:29:12 UTC+1 po...@debian.org a écrit : > Source: kxstitch > Severity: serious > > Hi, > > kxstitch is still built against imagemagick 6, but we're transitioning > to imagemagick 7, see [1]. > > Your package may be build-depe

Bug#1086939: php-imagick: build against imagemagick 7

2024-11-07 Thread pochu
Source: php-imagick Severity: serious Hi, php-imagick is still built against imagemagick 6, but we're transitioning to imagemagick 7, see [1]. Your package may be build-depending on imagemagick 6 binaries (e.g. libmagickwand-6.q16-dev), in which case it should switch to the new binary packages,

Bug#1086551: marked as done (ansible-core: uninstallable in unstable: Depends: python3-resolvelib (< 1.1.0))

2024-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2024 17:04:27 + with message-id and subject line Bug#1086551: fixed in ansible-core 2.17.5-5 has caused the Debian Bug report #1086551, regarding ansible-core: uninstallable in unstable: Depends: python3-resolvelib (< 1.1.0) to be marked as done. This means tha

Processed: Re: xsimd: autopkgtest is failing on arm64

2024-11-07 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1086489 [src:xsimd] xsimd: autopkgtest is failing on arm64 Severity set to 'serious' from 'important' -- 1086489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086489 Debian Bug Tracking System Contact ow...@bugs.debian.org with proble

Bug#1086941: wmaker: build against imagemagick 7

2024-11-07 Thread pochu
Source: wmaker Severity: serious Hi, wmaker is still built against imagemagick 6, but we're transitioning to imagemagick 7, see [1]. Your package may be build-depending on imagemagick 6 binaries (e.g. libmagickwand-6.q16-dev), in which case it should switch to the new binary packages, or generic

Bug#1057611: marked as done (raku-meta6: FTBFS: failing tests)

2024-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2024 16:50:00 + with message-id and subject line Bug#1057611: fixed in raku-meta6 0.0.30-1 has caused the Debian Bug report #1057611, regarding raku-meta6: FTBFS: failing tests to be marked as done. This means that you claim that the problem has been dealt with.

Processed: unarchive

2024-11-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 189 Bug #189 {Done: Bastian Germann } [src:clisp] clisp: depends on obsolete pcre3 library Unarchived Bug 189 > reopen 189 Bug #189 {Done: Bastian Germann } [src:clisp] clisp: depends on obsolete pcre3 library 'reop

Bug#1082996: marked as done (postgresql-filedump: FTBFS: undefined reference to `pg_printf')

2024-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2024 16:19:11 + with message-id and subject line Bug#1082996: fixed in postgresql-filedump 17.1-1 has caused the Debian Bug report #1082996, regarding postgresql-filedump: FTBFS: undefined reference to `pg_printf' to be marked as done. This means that you claim

Processed: Re: Bug#1084230: xvfb: please consider disabling libunwind, at least on armhf

2024-11-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1085704 [xvfb] Xvfb: segfaults on armhf with libunwind8_1.7.2-1 Added tag(s) patch. -- 1085704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085704 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1081191: marked as done (knot-exporter: there must be no subdirectories in /usr/sbin)

2024-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 7 Nov 2024 14:42:57 +0100 with message-id <20241107134257.k27mexpnlpdofoyy@nicota> and subject line this is supposed to be closed but still blocks migration has caused the Debian Bug report #1081191, regarding knot-exporter: there must be no subdirectories in /usr/sbin to be

Bug#1086934: kxstitch: build against imagemagick 7

2024-11-07 Thread Emilio Pozuelo Monfort
On 07/11/2024 16:56, Emilio Pozuelo Monfort wrote: Control: tags -1 - moreinfo Hi, On 07/11/2024 14:00, Aurélien COUDERC wrote: control: tags -1 + moreinfo Dear Emilio, Le jeudi 7 novembre 2024, 12:29:12 UTC+1 po...@debian.org a écrit : Source: kxstitch Severity: serious Hi, kxstitch is s

Bug#1086941: wmaker: build against imagemagick 7

2024-11-07 Thread Jeremy Sowden
On 2024-11-07, at 12:29:12 +0100, po...@debian.org wrote: > wmaker is still built against imagemagick 6, but we're transitioning > to imagemagick 7, see [1]. > > Your package may be build-depending on imagemagick 6 binaries (e.g. > libmagickwand-6.q16-dev), in which case it should switch to the ne

Bug#1086934: kxstitch: build against imagemagick 7

2024-11-07 Thread Emilio Pozuelo Monfort
Control: tags -1 - moreinfo Hi, On 07/11/2024 14:00, Aurélien COUDERC wrote: control: tags -1 + moreinfo Dear Emilio, Le jeudi 7 novembre 2024, 12:29:12 UTC+1 po...@debian.org a écrit : Source: kxstitch Severity: serious Hi, kxstitch is still built against imagemagick 6, but we're transiti

Processed: Re: Bug#1086701: autopkgtest: Same package version considered downgrade

2024-11-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1086701 [autopkgtest] autopkgtest: Same package version considered downgrade Added tag(s) patch. -- 1086701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086701 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1086934: kxstitch: build against imagemagick 7

2024-11-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 - moreinfo Bug #1086934 [src:kxstitch] kxstitch: build against imagemagick 7 Ignoring request to alter tags of bug #1086934 to the same tags previously set -- 1086934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086934 Debian Bug Tracking System Cont

Processed: Re: Bug#1086934: kxstitch: build against imagemagick 7

2024-11-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 - moreinfo Bug #1086934 [src:kxstitch] kxstitch: build against imagemagick 7 Removed tag(s) moreinfo. -- 1086934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1086701: autopkgtest: Same package version considered downgrade

2024-11-07 Thread Paride Legovini
Control: tags -1 + patch Tentative patch: https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/476 -- Paride

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

2024-11-07 Thread Andreas Hasenack
Is d/t/ldap-user-group-krb5-auth also flaky? Because it uses the same expect script: d/t/ldap-user-group-krb5-auth: ... # tests begin here run_common_tests # login works with the kerberos password echo "The Kerberos principal can login on a terminal" kdestroy > /dev/null 2>&1 || /bin/true /usr/bi

Bug#1086967: bootp: Does not work with bootpc - inappropriate DST IP ADDR

2024-11-07 Thread Avram Dorfman
Package: bootp Version: 2.4.3-19.1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: dorf...@est.org Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? We tried to set up a bootpd/bootpc testbe

Bug#1086957: mfem: FTBFS on arm64: undefined reference to `ompi_mpi_cxx_op_intercept'

2024-11-07 Thread Emanuele Rocca
Source: mfem Version: 4.7+ds-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: debian-...@lists.debian.org Usertags: arm64 During a rebuild of all packages in sid, mfem failed to build on arm64 with the following error. On amd64 the package builds correctly. /usr/bin/ld: warni

Bug#1086936: wand: build against imagemagick 7

2024-11-07 Thread pochu
Source: wand Severity: serious Hi, wand is still built against imagemagick 6, but we're transitioning to imagemagick 7, see [1]. Your package may be build-depending on imagemagick 6 binaries (e.g. libmagickwand-6.q16-dev), in which case it should switch to the new binary packages, or generic one

Bug#1086937: pfstools: build against imagemagick 7

2024-11-07 Thread pochu
Source: pfstools Severity: serious Hi, pfstools is still built against imagemagick 6, but we're transitioning to imagemagick 7, see [1]. Your package may be build-depending on imagemagick 6 binaries (e.g. libmagickwand-6.q16-dev), in which case it should switch to the new binary packages, or gen

Bug#1086835: marked as done (groonga: FTBFS: cannot stat './html/_static/webpack-macros.html': No such file or directory)

2024-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2024 13:05:33 + with message-id and subject line Bug#1086835: fixed in groonga 14.0.5+dfsg-3 has caused the Debian Bug report #1086835, regarding groonga: FTBFS: cannot stat './html/_static/webpack-macros.html': No such file or directory to be marked as done. T

Bug#1086935: synfig: build against imagemagick 7

2024-11-07 Thread pochu
Source: synfig Severity: serious Hi, synfig is still built against imagemagick 6, but we're transitioning to imagemagick 7, see [1]. Your package may be build-depending on imagemagick 6 binaries (e.g. libmagickwand-6.q16-dev), in which case it should switch to the new binary packages, or generic

Processed: tagging 1085704, tagging 1084230 ...

2024-11-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1085704 + pending Bug #1085704 [xvfb] Xvfb: segfaults on armhf with libunwind8_1.7.2-1 Added tag(s) pending. > tags 1084230 + pending Bug #1084230 [xvfb] xvfb: please consider disabling libunwind, at least on armhf Bug #1082985 [xvfb] chatty:

Bug#1086938: odr-padenc: build against imagemagick 7

2024-11-07 Thread pochu
Source: odr-padenc Severity: serious Hi, odr-padenc is still built against imagemagick 6, but we're transitioning to imagemagick 7, see [1]. Your package may be build-depending on imagemagick 6 binaries (e.g. libmagickwand-6.q16-dev), in which case it should switch to the new binary packages, or

Processed: Re: trippy - upcoming rust-nix update

2024-11-07 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1085459 [trippy] trippy - upcoming rust-nix update Severity set to 'serious' from 'normal' > tags -1 +ftbfs Bug #1085459 [trippy] trippy - upcoming rust-nix update Added tag(s) ftbfs. -- 1085459: https://bugs.debian.org/cgi-bin/bugreport.cg

Bug#1086835: groonga: FTBFS: cannot stat './html/_static/webpack-macros.html': No such file or directory

2024-11-07 Thread Kentaro HAYASHI
> /usr/bin/install: cannot stat './html/_static/webpack-macros.html': > No such file or directory It seems that this error was caused by updating python3-pydata-sphinx-theme (0.15.4+dfsg-2). Regards,

Bug#1078531: marked as done (python-mp-api: new release requires unpackaged maggma package)

2024-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2024 11:50:32 + with message-id and subject line Bug#1078531: fixed in python-mp-api 0.43.0rc0-1 has caused the Debian Bug report #1078531, regarding python-mp-api: new release requires unpackaged maggma package to be marked as done. This means that you claim th

Bug#1086929: rtl8723bt-firmware: Do not release with trixie

2024-11-07 Thread Bastian Germann
Source: rtl8723bt-firmware Severity: serious This firmware is available with firmware-realtek now.

Bug#1086931: drawtiming: build against imagemagick 7

2024-11-07 Thread pochu
Source: drawtiming Severity: serious Hi, drawtiming is still built against imagemagick 6, but we're transitioning to imagemagick 7, see [1]. Your package may be build-depending on imagemagick 6 binaries (e.g. libmagickwand-6.q16-dev), in which case it should switch to the new binary packages, or

Bug#1086940: photoqt: build against imagemagick 7

2024-11-07 Thread pochu
Source: photoqt Severity: serious Hi, photoqt is still built against imagemagick 6, but we're transitioning to imagemagick 7, see [1]. Your package may be build-depending on imagemagick 6 binaries (e.g. libmagickwand-6.q16-dev), in which case it should switch to the new binary packages, or gener

Bug#1086930: dx: build against imagemagick 7

2024-11-07 Thread pochu
Source: dx Severity: serious Hi, dx is still built against imagemagick 6, but we're transitioning to imagemagick 7, see [1]. Your package may be build-depending on imagemagick 6 binaries (e.g. libmagickwand-6.q16-dev), in which case it should switch to the new binary packages, or generic ones if

Bug#1086933: libopenshot: build against imagemagick 7

2024-11-07 Thread pochu
Source: libopenshot Severity: serious Hi, libopenshot is still built against imagemagick 6, but we're transitioning to imagemagick 7, see [1]. Your package may be build-depending on imagemagick 6 binaries (e.g. libmagickwand-6.q16-dev), in which case it should switch to the new binary packages,

Bug#1086267: marked as done (golang-github-google-go-intervals: FTBFS: FAIL github.com/google/go-intervals/timespanset)

2024-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2024 11:04:50 + with message-id and subject line Bug#1086267: fixed in golang-github-google-go-intervals 0.0.2-3 has caused the Debian Bug report #1086267, regarding golang-github-google-go-intervals: FTBFS: FAIL github.com/google/go-intervals/timespanset to be

Bug#1086918: python-escript: depends on openmpi on 32-bit architectures

2024-11-07 Thread pochu
Source: python-escript Severity: serious Hi, python-escript depends on openmpi on 32-bit architectures, which has been removed in openmpi 5. Thus this package needs to stop depending on it on those architectures. There are a couple of options: - build-dep on mpi-default-dev instead of openmpi-de

Bug#1086913: sopt: depends on openmpi on 32-bit architectures

2024-11-07 Thread pochu
Source: sopt Severity: serious Hi, sopt depends on openmpi on 32-bit architectures, which has been removed in openmpi 5. Thus this package needs to stop depending on it on those architectures. There are a couple of options: - build-dep on mpi-default-dev instead of openmpi-dev, so that the MPI

Bug#1086908: murasaki: depends on openmpi on 32-bit architectures

2024-11-07 Thread pochu
Source: murasaki Severity: serious Hi, murasaki depends on openmpi on 32-bit architectures, which has been removed in openmpi 5. Thus this package needs to stop depending on it on those architectures. There are a couple of options: - build-dep on mpi-default-dev instead of openmpi-dev, so that t

Bug#1086909: examl: depends on openmpi on 32-bit architectures

2024-11-07 Thread pochu
Source: examl Severity: serious Hi, examl depends on openmpi on 32-bit architectures, which has been removed in openmpi 5. Thus this package needs to stop depending on it on those architectures. There are a couple of options: - build-dep on mpi-default-dev instead of openmpi-dev, so that the M

Bug#1086914: relion: depends on openmpi on 32-bit architectures

2024-11-07 Thread pochu
Source: relion Severity: serious Hi, relion depends on openmpi on 32-bit architectures, which has been removed in openmpi 5. Thus this package needs to stop depending on it on those architectures. There are a couple of options: - build-dep on mpi-default-dev instead of openmpi-dev, so that the

Bug#1086911: mfem: depends on openmpi on 32-bit architectures

2024-11-07 Thread pochu
Source: mfem Severity: serious Hi, mfem depends on openmpi on 32-bit architectures, which has been removed in openmpi 5. Thus this package needs to stop depending on it on those architectures. There are a couple of options: - build-dep on mpi-default-dev instead of openmpi-dev, so that the MPI

Bug#1086912: phyml: depends on openmpi on 32-bit architectures

2024-11-07 Thread pochu
Source: phyml Severity: serious Hi, phyml depends on openmpi on 32-bit architectures, which has been removed in openmpi 5. Thus this package needs to stop depending on it on those architectures. There are a couple of options: - build-dep on mpi-default-dev instead of openmpi-dev, so that the M

Bug#1086910: ffindex: depends on openmpi on 32-bit architectures

2024-11-07 Thread pochu
Source: ffindex Severity: serious Hi, ffindex depends on openmpi on 32-bit architectures, which has been removed in openmpi 5. Thus this package needs to stop depending on it on those architectures. There are a couple of options: - build-dep on mpi-default-dev instead of openmpi-dev, so that the

Bug#1086907: tree-puzzle: depends on openmpi on 32-bit architectures

2024-11-07 Thread pochu
Source: tree-puzzle Severity: serious Hi, tree-puzzle depends on openmpi on 32-bit architectures, which has been removed in openmpi 5. Thus this package needs to stop depending on it on those architectures. There are a couple of options: - build-dep on mpi-default-dev instead of openmpi-dev, so

  1   2   >