Bug#1042356: rapid-photo-downloader: FTBFS: make: *** [debian/rules:8: clean] Error 25
Control: tags -1 +patch There's a patch posted in this thread for this bug: https://discuss.pixls.us/t/patch-for-newer-python-setuptools/36593 Actual link to the patch on Arch: https://build.opensuse.org/request/show/1078462 -- The odds are greatly against you being immensely smarter than everyone else in the field. If your analysis says your terminal velocity is twice the speed of light, you may have invented warp drive, but the chances are a lot better that you've screwed up. - Akin's Laws of Spacecraft Design
Processed: Re: Bug#1042356: rapid-photo-downloader: FTBFS: make: *** [debian/rules:8: clean] Error 25
Processing control commands: > tags -1 +patch Bug #1042356 [src:rapid-photo-downloader] rapid-photo-downloader: FTBFS: make: *** [debian/rules:8: clean] Error 25 Added tag(s) patch. -- 1042356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 1053686 1054940
Processing commands for cont...@bugs.debian.org: > forcemerge 1053686 1054940 Bug #1053686 [src:pandoc] pandoc: cannot fulfill the build dependencies Bug #1053686 [src:pandoc] pandoc: cannot fulfill the build dependencies Added tag(s) sid and trixie. Bug #1054940 [src:pandoc] pandoc: FTBFS: unsatisfiable build-dependencies: libghc-aeson-dev (< 2.1), libghc-citeproc-dev (< 0.7), libghc-doclayout-dev (< 0.4), libghc-doctemplates-dev (< 0.11), libghc-haddock-library-dev (< 1.11), libghc-hslua-dev (< 2.2), libghc-hslua-aeson-dev (< 2.2), libghc-hslua-marshalling-dev (< 2.2), libghc-hslua-module-path-dev (< 1.1), libghc-hslua-module-system-dev (< 1.1), libghc-hslua-module-text-dev (< 1.1), libghc-hslua-module-version-dev (< 1.1), libghc-jira-wiki-markup-dev (< 1.5), libghc-pandoc-lua-marshal-dev (< 0.2), libghc-pandoc-types-dev (< 1.23), libghc-skylighting-dev (< 0.13), libghc-skylighting-core-dev (< 0.13), libghc-texmath-dev (< 0.12.5), libghc-tasty-lua-dev (< 1.1), libghc-hsyaml-doc Merged 1053686 1054940 > thanks Stopping processing here. Please contact me if you need assistance. -- 1053686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053686 1054940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055862: node-http-proxy-agent: missing Breaks+Replaces: node-https-proxy-agent (<< 7)
Package: node-http-proxy-agent Version: 7.0.0~0~2023071921-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. This error may also be triggered by having a predecessor package from 'sid' installed while installing the package from 'experimental'. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../node-http-proxy-agent_7.0.0~0~2023071921-1_all.deb ... Unpacking node-http-proxy-agent (7.0.0~0~2023071921-1) ... dpkg: error processing archive /var/cache/apt/archives/node-http-proxy-agent_7.0.0~0~2023071921-1_all.deb (--unpack): trying to overwrite '/usr/share/nodejs/http-proxy-agent/dist/index.d.ts', which is also in package node-https-proxy-agent 5.0.1+~cs8.0.0-3 Errors were encountered while processing: /var/cache/apt/archives/node-http-proxy-agent_7.0.0~0~2023071921-1_all.deb The following files have moved to a new package: usr/share/nodejs/http-proxy-agent/dist/index.d.ts usr/share/nodejs/http-proxy-agent/dist/index.js usr/share/nodejs/http-proxy-agent/dist/index.js.map usr/share/nodejs/http-proxy-agent/package.json cheers, Andreas node-https-proxy-agent=5.0.1+~cs8.0.0-3_node-http-proxy-agent=7.0.0~0~2023071921-1.log.gz Description: application/gzip
Bug#1036256: marked as done (golang-github-pin-tftp: FTBFS in testing: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/pin/tftp github.com/pin/tftp/netascii returned exit code 1)
Your message dated Mon, 13 Nov 2023 01:18:59 +
with message-id
and subject line Bug#1036256: fixed in golang-github-pin-tftp 3.1.0-1
has caused the Debian Bug report #1036256,
regarding golang-github-pin-tftp: FTBFS in testing: dh_auto_test: error: cd
_build && go test -vet=off -v -p 8 github.com/pin/tftp
github.com/pin/tftp/netascii returned exit code 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1036256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-pin-tftp
Version: 2.2.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230517 ftbfs-bookworm
Hi,
During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --builddirectory=_build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang
>dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_build -O--builddirectory=_build -O--buildsystem=golang
> cd _build && go install -trimpath -v -p 8 github.com/pin/tftp
> github.com/pin/tftp/netascii
> internal/goarch
> internal/race
> internal/unsafeheader
> internal/goexperiment
> internal/goos
> internal/cpu
> runtime/internal/syscall
> sync/atomic
> runtime/internal/atomic
> runtime/internal/math
> internal/abi
> unicode
> runtime/internal/sys
> unicode/utf8
> math/bits
> internal/itoa
> golang.org/x/net/internal/iana
> internal/nettrace
> internal/bytealg
> math
> runtime
> internal/reflectlite
> sync
> internal/testlog
> internal/singleflight
> math/rand
> runtime/cgo
> errors
> sort
> internal/oserror
> internal/safefilepath
> io
> path
> vendor/golang.org/x/net/dns/dnsmessage
> strconv
> syscall
> github.com/pin/tftp/netascii
> bytes
> strings
> reflect
> internal/syscall/execenv
> internal/syscall/unix
> time
> context
> io/fs
> internal/poll
> os
> internal/fmtsort
> encoding/binary
> golang.org/x/sys/unix
> internal/godebug
> fmt
> internal/intern
> net/netip
> net
> golang.org/x/net/bpf
> golang.org/x/net/internal/socket
> golang.org/x/net/ipv4
> golang.org/x/net/ipv6
> github.com/pin/tftp
>dh_auto_test -O--builddirectory=_build -O--buildsystem=golang
> cd _build && go test -vet=off -v -p 8 github.com/pin/tftp
> github.com/pin/tftp/netascii
> === RUN TestZeroLengthSinglePort
> --- PASS: TestZeroLengthSinglePort (0.00s)
> === RUN TestSendReceiveSinglePortWithBlockSize
> panic: test timed out after 10m0s
>
> goroutine 1643 [running]:
> testing.(*M).startAlarm.func1()
> /usr/lib/go-1.19/src/testing/testing.go:2036 +0x8e
> created by time.goFunc
> /usr/lib/go-1.19/src/time/sleep.go:176 +0x32
>
> goroutine 1 [chan receive, 10 minutes]:
> testing.(*T).Run(0xc000107520, {0x6315de?, 0x4d8ce5?}, 0x6517c8)
> /usr/lib/go-1.19/src/testing/testing.go:1494 +0x37a
> testing.runTests.func1(0xc000117710?)
> /usr/lib/go-1.19/src/testing/testing.go:1846 +0x6e
> testing.tRunner(0xc000107520, 0xc000179cd8)
> /usr/lib/go-1.19/src/testing/testing.go:1446 +0x10b
> testing.runTests(0xc000133360?, {0x796d40, 0x1b, 0x1b}, {0x7fbf08f3ba68?,
> 0x40?, 0x7cb9a0?})
> /usr/lib/go-1.19/src/testing/testing.go:1844 +0x456
> testing.(*M).Run(0xc000133360)
> /usr/lib/go-1.19/src/testing/testing.go:1726 +0x5d9
> main.main()
> _testmain.go:99 +0x1aa
>
> goroutine 36 [chan send, 9 minutes]:
> github.com/pin/tftp.(*Server).Shutdown(0xcd8000)
> /<>/_build/src/github.com/pin/tftp/server.go:310 +0x65
> github.com/pin/tftp.TestSendReceiveSinglePortWithBlockSize(0xe?)
> /<>/_build/src/github.com/pin/tftp/single_port_test.go:20
> +0xa9
> testing.tRunner(0xc8a4e0, 0x6517c8)
> /usr/lib/go-1.19/src/testing/testing.go:1446 +0x10b
> created by testing.(*T).Run
> /usr/lib/go-1.19/src/testing/testing.go:1493 +0x35f
>
> goroutine 22 [chan receive, 10 minutes]:
> github.com/pin/tftp.(*Server).internalGC(0xc0001a6000)
> /<>/_build/src/github.com/pin/tftp/single_port.go:121 +0x70
> created by github.com/pin/tftp.(*Server).EnableSinglePort
> /<>/_build/src/github.com/pin/tftp/server.go:129 +0x185
>
> goroutine 38 [IO wait, 9 minutes]:
> internal/poll.runtime_pollWait(0x7fbee00cef68, 0x72)
> /usr/lib/go-1.19/src/runtime/netpoll.go:305 +0x89
> internal/poll.(*pollDesc).wait(0xca0180?, 0xc000b2d800?, 0x0)
>
Bug#1054449: marked as done (pesign: Missing Pre-Depends on passwd)
Your message dated Sun, 12 Nov 2023 21:49:41 +
with message-id
and subject line Bug#1054449: fixed in pesign 116-6
has caused the Debian Bug report #1054449,
regarding pesign: Missing Pre-Depends on passwd
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1054449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pesign
Version: 0.112-6
Severity: serious
Tags: patch
Dear maintainer:
When installing this package on a minimal chroot, this is what happens:
Preparing to unpack .../26-pesign_0.112-6_amd64.deb ...
/var/lib/dpkg/tmp.ci/preinst: 19: groupadd: not found
dpkg: error processing archive
/tmp/apt-dpkg-install-4UpEBk/26-pesign_0.112-6_amd64.deb (--unpack):
new pesign package pre-installation script subprocess returned error exit
status 127
This is because the package should have a Pre-Depends on "passwd",
which is not essential.
Trivial patch attached.
Thanks.--- a/debian/control
+++ b/debian/control
@@ -13,6 +13,7 @@ Package: pesign
Architecture: amd64 i386 armhf arm64 armel
Multi-Arch: foreign
Depends: ${shlibs:Depends}, ${misc:Depends}, libnss3-tools, coolkey, opensc
+Pre-Depends: passwd
Description: Signing utility for UEFI binaries
This package contains the pesign utility for signing UEFI binaries (PE-COFF
format) as well as other associated tools. It is meant to follow the PE and
--- End Message ---
--- Begin Message ---
Source: pesign
Source-Version: 116-6
Done: Steve McIntyre <93...@debian.org>
We believe that the bug you reported is fixed in the latest version of
pesign, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Steve McIntyre <93...@debian.org> (supplier of updated pesign package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 12 Nov 2023 21:32:02 +
Source: pesign
Architecture: source
Version: 116-6
Distribution: unstable
Urgency: medium
Maintainer: Debian UEFI maintainers
Changed-By: Steve McIntyre <93...@debian.org>
Closes: 1054449
Changes:
pesign (116-6) unstable; urgency=medium
.
* Move passwd from Build-Depends to Depends, Closes: #1054449
Doh!
Checksums-Sha1:
388255b465783b7dd5b7d9e18d78562c46278bb5 2085 pesign_116-6.dsc
d89de6869ae662b995474984e23669d02617c8a4 11688 pesign_116-6.debian.tar.xz
f3b2c8c06b75c5b0d9f4ff228359a8f6c8d8140d 6866 pesign_116-6_source.buildinfo
Checksums-Sha256:
c6f9bce391cb5edaf322820884fc898c4d1a041859218b4e05cf990785c6c6db 2085
pesign_116-6.dsc
f5c86a698b22b2458e363af72489899faa1032685326322c7ed4e1e170d531fa 11688
pesign_116-6.debian.tar.xz
2f71e69e95003f25689c196c53556eb203d30b742ebee74025672893b50b806d 6866
pesign_116-6_source.buildinfo
Files:
5b05b3131a5f02948719456feef186d7 2085 devel optional pesign_116-6.dsc
c40f55078794e4a969e96543c16c0358 11688 devel optional
pesign_116-6.debian.tar.xz
d8d249f188baa31adec15161d40b8972 6866 devel optional
pesign_116-6_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEEzrtSMB1hfpEDkP4WWHl5VzRCaE4FAmVRRXQRHDkzc2FtQGRl
Ymlhbi5vcmcACgkQWHl5VzRCaE4ZjRAAgjVsr64Q5A62YDSkuw2RabDZHgwGCq+9
PuAhSvTTicDGJU/jzcb17xGQj+HxbmElIW/VXBGW8EiNplaPyf0o0pogeFNSKT3t
m9Py+H6I9e2N24HxHK4wa3Lcv6vUQw1UYB+JjRhe3G/8Q82NZJGjw9l9rdwdn3c7
kmL2JzWR3AkkqrI+zjd+LyVadu3raLjIXBqUIT7ALCmz5sVcxPdPkS2uF6KoknM2
n+A274S/F+JlrZxpyiTmeJ/n5LnWE0AaJDjLkWKAzk0El/1/POO/218h6jY8IVCn
oHmm601ulP/WLHy/qf9ghrDOsL1o0Z10pc0tXLWhN6d3V0HM5kpk8EWui0W3p75a
N1k4dZf3Oi19V6FY5BV/jzUyUGJ7s2nYkhEkl8lpfTUD7xTtO/bHJp8ZNEgmdlCI
WSmRrQDyu7rpMj82Cqf6B6KdwiI7g6+/9iN+1yyXi+YlEkHDiqJJhq7J10MXpsUt
k+mnEW0QUamfW+lJnO41wm2HYJ0LCKLCvuywtPLKAfvqkUijNiQ4gBDWvco6KGAH
2mPRn6kapAr1wr4GaUxrfCBgJX2AIIHf2gk60pTK0LMQGg84dSJcNF/SjLl7vf3o
Os8uMHYLh+HEk5cHdA+EcqhV/u62zhk6pV9ysD0v/jX91o41yjEuyAzdwOjuYeAP
Y8LkJZCvV3E=
=16bm
-END PGP SIGNATURE End Message ---
Bug#1054449: pesign: Missing Depends on passwd
On Sun, Nov 12, 2023 at 10:16:01PM +0100, Santiago Vila wrote: >found 1054449 116-1 >found 1054449 116-5 >affects 1054449 src:shim >thanks > >Hi. In commit e38e2a8af632a660d3c01a936796622fce186020 >it looks that you added passwd to the Build-Depends. > >The bug (after preinst moved to postinst) was about adding it >to the Depends field. > >In fact, the changelog was correct for what it had to be done, >just not for what it was actually done. > >(note: shim FTBFS in a clean chroot because of this bug) Oh, gah. :-/ Thanks for the prod, fixing now! -- Steve McIntyre, Cambridge, UK.st...@einval.com "I used to be the first kid on the block wanting a cranial implant, now I want to be the first with a cranial firewall. " -- Charlie Stross
Processed: Re: pesign: Missing Depends on passwd
Processing commands for cont...@bugs.debian.org:
> found 1054449 116-1
Bug #1054449 {Done: Steve McIntyre <93...@debian.org>} [pesign] pesign: Missing
Pre-Depends on passwd
There is no source info for the package 'pesign' at version '116-1' with
architecture ''
Unable to make a source version for version '116-1'
Marked as found in versions 116-1; no longer marked as fixed in versions
pesign/116-1 and reopened.
> found 1054449 116-5
Bug #1054449 [pesign] pesign: Missing Pre-Depends on passwd
Marked as found in versions pesign/116-5.
> affects 1054449 src:shim
Bug #1054449 [pesign] pesign: Missing Pre-Depends on passwd
Added indication that 1054449 affects src:shim
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1054449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1054449: pesign: Missing Depends on passwd
found 1054449 116-1 found 1054449 116-5 affects 1054449 src:shim thanks Hi. In commit e38e2a8af632a660d3c01a936796622fce186020 it looks that you added passwd to the Build-Depends. The bug (after preinst moved to postinst) was about adding it to the Depends field. In fact, the changelog was correct for what it had to be done, just not for what it was actually done. (note: shim FTBFS in a clean chroot because of this bug) Thanks.
Bug#1055833: marked as done (charliecloud: autopkgtest fails in unstable, blocks other packages migration)
Your message dated Sun, 12 Nov 2023 20:48:59 + with message-id and subject line Bug#1055833: fixed in charliecloud 0.35-6 has caused the Debian Bug report #1055833, regarding charliecloud: autopkgtest fails in unstable, blocks other packages migration to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1055833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: charliecloud Version: 0.35-4 Severity: important charliecloud's autopkgtest is failing in unstable, and it is blocking iproute2's migration as they are tested together: https://ci.debian.net/data/autopkgtest/testing/s390x/c/charliecloud/39798421/log.gz -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: charliecloud Source-Version: 0.35-6 Done: Peter Wienemann We believe that the bug you reported is fixed in the latest version of charliecloud, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Wienemann (supplier of updated charliecloud package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 12 Nov 2023 21:08:58 +0100 Source: charliecloud Architecture: source Version: 0.35-6 Distribution: unstable Urgency: medium Maintainer: Debian HPC Team Changed-By: Peter Wienemann Closes: 1055833 Changes: charliecloud (0.35-6) unstable; urgency=medium . * d/tests/control: Skip autopkgtest on s390x (Closes: #1055833) Checksums-Sha1: ef8f471af7510879c15e049f60bdef42b30d3d85 2652 charliecloud_0.35-6.dsc 22a2ba6081ca55d123e65fd9e859ee8ab2c074bb 13704 charliecloud_0.35-6.debian.tar.xz 39f12be0d07c11f9462eeff7ec85af993a8fca75 10371 charliecloud_0.35-6_amd64.buildinfo Checksums-Sha256: 9b38acc764089fbeee148d04d2f840e378fd8da0782f513e1971b63d51ba021d 2652 charliecloud_0.35-6.dsc 2c718f47904fca5c3db1790f5a8ed92cc7d6671f7329184f82fd97b9fc2f416c 13704 charliecloud_0.35-6.debian.tar.xz e7a1f0011307810e7b3b26b181ce5546c81ccd7910a8f7225c083cb844c2197f 10371 charliecloud_0.35-6_amd64.buildinfo Files: 55428b15919e24e96398cf61bc1fc051 2652 admin optional charliecloud_0.35-6.dsc 530b412811faca76712a140647f2e886 13704 admin optional charliecloud_0.35-6.debian.tar.xz 4987420c8baecf36ec159882cfd35212 10371 admin optional charliecloud_0.35-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEBrYs08CqJ6RHEajlAuXO5wyFLHsFAmVRMmxfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDA2 QjYyQ0QzQzBBQTI3QTQ0NzExQThFNTAyRTVDRUU3MEM4NTJDN0IACgkQAuXO5wyF LHsP8A/+OTpx4drUx9DVsj9mmKZHvk9zYdvtlNwYOJW0SkQmNkn7mKbfxom0Qiiq tecTFV/nX9XxVxoreXkhfrQ/zCn+O6PoDmXXi0a7Eq8ZjzxL0JvEZn+Z7IAyzGxo tFbmPwH9ziMtyWvbl1LW0q8K9/DUixsG/d0BacJGShycRl6dgSSg0HNCb5MIZPot fBicD1PJEsJY/NaQn93Km16UlGVFlZhoIPtP6D7VEhpE33IB/8OviI7f0pPv7hxH 5YKhvHVKT9rKponM8v2x4uooRYDoRe0SS2ZJMst3CrZFc2MU7Z2d45otJCEp1Rqr ZMy18ez72f7JHN8sJDKHeD9uHvvY/E0O45mueVrhYmeVkJG+jm1vxik2SOZuhXz/ /M6burtYpHt/fNRfMvnpvH/zGdbJT0Rpso8dzSEvpBW5DZkVtSd5v+2Zn0/lfVKI 0/AuWBW7GmG7UlcBMjLi9t16FZe6AT9KJHcSDX9WTLN3PN2xUucbJyER+6NsKXOa wcRXHW2J+3vCHOpupNIIndkgxtNwJj8Fuccq1LET6e9flKjnc9SQJag0954q2Urx A1BkSq93cYMO4dCM2RhdIgQUSZDZQWftACQbcvDaH8z6vHVuNFs677X7oBd+TSAc SI7Mp0Cb59RnH2FCC6IGR8G4HggluMM2xVcWbw0Ff/7HtexCDUQ= =IVOt -END PGP SIGNATURE End Message ---
Processed: Bug#1055833 marked as pending in charliecloud
Processing control commands: > tag -1 pending Bug #1055833 [src:charliecloud] charliecloud: autopkgtest fails in unstable, blocks other packages migration Added tag(s) pending. -- 1055833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055833: marked as pending in charliecloud
Control: tag -1 pending Hello, Bug #1055833 in charliecloud 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/hpc-team/charliecloud/-/commit/80969006f62d9d5450bdfb8237512baba4d891d9 d/t/control: Skip autopkgtest on s390x (Closes: #1055833) This is a workaround for upstream issue https://github.com/hpc/charliecloud/issues/1773 (this message was generated automatically) -- Greetings https://bugs.debian.org/1055833
Processed: tagging 1055817, tagging 1055070, tagging 1054894
Processing commands for cont...@bugs.debian.org: > tags 1055817 + pending Bug #1055817 [ghc-doc] ghc-doc: piuparts regression Added tag(s) pending. > tags 1055070 + pending Bug #1055070 [ghc-doc] /usr/share/doc/ghc-doc/html/libraries/index.html missing boot libraries Added tag(s) pending. > tags 1054894 + pending Bug #1054894 [ghc] haskell-bytestring-lexing: FTBFS on ppc64el: unrecognized opcode: `clrrhi' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1054894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054894 1055070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055070 1055817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1055833: charliecloud: autopkgtest fails in unstable, blocks other packages migration
Processing control commands: > severity -1 serious Bug #1055833 [src:charliecloud] charliecloud: autopkgtest fails in unstable, blocks other packages migration Severity set to 'serious' from 'important' -- 1055833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054790: marked as done (rdkit: FTBFS: make[1]: *** [debian/rules:88: override_dh_auto_configure] Error 2)
Your message dated Sun, 12 Nov 2023 19:50:37 + with message-id and subject line Bug#1054790: fixed in rdkit 202309.2-1 has caused the Debian Bug report #1054790, regarding rdkit: FTBFS: make[1]: *** [debian/rules:88: override_dh_auto_configure] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rdkit Version: 202303.3-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- -DCMAKE_BUILD_TYPE=None -DCMAKE_SKIP_RPATH=ON > -DRDK_INSTALL_INTREE=OFF -DRDK_INSTALL_STATIC_LIBS=OFF > -DRDK_BUILD_THREADSAFE_SSS=ON -DRDK_BUILD_PYTHON_WRAPPERS=ON > -DRDK_OPTIMIZE_POPCNT=OFF -DRDK_USE_URF=OFF -DRDK_INSTALL_COMIC_FONTS=OFF > -DRDK_BUILD_CAIRO_SUPPORT=ON -DBoost_NO_BOOST_CMAKE=TRUE > -DCMAKE_INSTALL_PREFIX=/usr -DCATCH_DIR=/usr/include/catch2 > -DPYTHON_EXECUTABLE=/usr/bin/python3.11 ../ > cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake > -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None > -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var > -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu > -DCMAKE_BUILD_TYPE=None -DCMAKE_SKIP_RPATH=ON -DRDK_INSTALL_INTREE=OFF > -DRDK_INSTALL_STATIC_LIBS=OFF -DRDK_BUILD_THREADSAFE_SSS=ON > -DRDK_BUILD_PYTHON_WRAPPERS=ON -DRDK_OPTIMIZE_POPCNT=OFF -DRDK_USE_URF=OFF > -DRDK_INSTALL_COMIC_FONTS=OFF -DRDK_BUILD_CAIRO_SUPPORT=ON > -DBoost_NO_BOOST_CMAKE=TRUE -DCMAKE_INSTALL_PREFIX=/usr > -DCATCH_DIR=/usr/include/catch2 -DPYTHON_EXECUTABLE=/usr/bin/python3.11 ../ .. > -- The C compiler identification is GNU 13.2.0 > -- The CXX compiler identification is GNU 13.2.0 > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- Catch not found in /usr/include/catch2 > Downloading https://github.com/catchorg/Catch2/archive/v2.13.8.tar.gz... > CMake Error at External/catch/CMakeLists.txt:22 (file): > file RENAME failed to rename > > /<>/External/catch/Catch2-2.13.8 > > to > > /usr/include/catch2 > > because: Invalid cross-device link > > > > CATCH: /usr/include/catch2/single_include/catch2 > CMake Warning (dev) at CMakeLists.txt:276 (find_package): > Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs modules > are removed. Run "cmake --help-policy CMP0148" for policy details. Use > the cmake_policy command to set the policy and suppress this warning. > > This warning is for project developers. Use -Wno-dev to suppress it. > > -- Found PythonInterp: /usr/bin/python3.11 (found version "3.11.6") > CMake Warning (dev) at CMakeLists.txt:285 (find_package): > Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs modules > are removed. Run "cmake --help-policy CMP0148" for policy details. Use > the cmake_policy command to set the policy and suppress this warning. > > This warning is for project developers. Use -Wno-dev to suppress it. > > -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.11.so (found > version "3.11.6") > CMake Warning (dev) at Code/cmake/Modules/FindNumPy.cmake:10 (find_package): > Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs modules > are removed. Run "cmake --help-policy CMP0148" for policy details. Use > the cmake_policy command to set the policy and suppress this warning. > > Call Stack (most recent call first): > CMakeLists.txt:300 (find_package) > This warning is for project developers. Use -Wno-dev to suppress it. > > CMake Warning at /usr/share/cmake-3.27/Modules/FindBoost.cmake:2233 (message): > No header defined for python-py311; skipping header check (note: >
Processed: tagging 1055852, tagging 1055853, tagging 1055854
Processing commands for cont...@bugs.debian.org: > tags 1055852 + upstream Bug #1055852 [src:frr] frr: CVE-2023-38407 CVE-2023-41361 CVE-2023-46752 CVE-2023-46753 CVE-2023-47234 CVE-2023-47235 Added tag(s) upstream. > tags 1055853 + upstream Bug #1055853 [src:jgit] jgit: CVE-2023-4759 Added tag(s) upstream. > tags 1055854 + upstream Bug #1055854 [src:radare2] radare2: CVE-2023-5686 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1055852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055852 1055853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055853 1055854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055852: frr: CVE-2023-38407 CVE-2023-41361 CVE-2023-46752 CVE-2023-46753 CVE-2023-47234 CVE-2023-47235
Source: frr X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for frr. CVE-2023-38407[0]: | bgpd/bgp_label.c in FRRouting (FRR) before 8.5 attempts to read | beyond the end of the stream during labeled unicast parsing. https://github.com/FRRouting/frr/pull/12951 https://github.com/FRRouting/frr/commit/7404a914b0cafe046703c8381903a80d3def8f8b (base_9.0) https://github.com/FRRouting/frr/pull/12956 https://github.com/FRRouting/frr/commit/ab362eae68edec12c175d9bc488bcc3f8b73d36f (frr-8.5) CVE-2023-41361[1]: | An issue was discovered in FRRouting FRR 9.0. bgpd/bgp_open.c does | not check for an overly large length of the rcv software version. https://github.com/FRRouting/frr/pull/14241 Fixed by: https://github.com/FRRouting/frr/commit/b4d09af9194d20a7f9f16995a062f5d8e3d32840 Backport for 9.0 branch: https://github.com/FRRouting/frr/pull/14250 Fixed by: https://github.com/FRRouting/frr/commit/73ad93a83f18564bb7bff4659872f7ec1a64b05e CVE-2023-46752[2]: | An issue was discovered in FRRouting FRR through 9.0.1. It | mishandles malformed MP_REACH_NLRI data, leading to a crash. Fixed by: https://github.com/FRRouting/frr/commit/b08afc81c60607a4f736f418f2e3eb06087f1a35 (master) Fixed by: https://github.com/FRRouting/frr/commit/30b5c2a434d25981e16792f6f50162beb517ae4d (stable/8.5 branch) CVE-2023-46753[3]: | An issue was discovered in FRRouting FRR through 9.0.1. A crash can | occur for a crafted BGP UPDATE message without mandatory attributes, | e.g., one with only an unknown transit attribute. Fixed by: https://github.com/FRRouting/frr/commit/d8482bf011cb2b173e85b65b4bf3d5061250cdb9 (master) Fixed by: https://github.com/FRRouting/frr/commit/21418d64af11553c402f932b0311c812d98ac3e4 (stable/8.5 branch) CVE-2023-47234[4]: | An issue was discovered in FRRouting FRR through 9.0.1. A crash can | occur when processing a crafted BGP UPDATE message with a | MP_UNREACH_NLRI attribute and additional NLRI data (that lacks | mandatory path attributes). https://github.com/FRRouting/frr/commit/c37119df45bbf4ef713bc10475af2ee06e12f3bf CVE-2023-47235[5]: | An issue was discovered in FRRouting FRR through 9.0.1. A crash can | occur when a malformed BGP UPDATE message with an EOR is processed, | because the presence of EOR does not lead to a treat-as-withdraw | outcome. https://github.com/FRRouting/frr/commit/6814f2e0138a6ea5e1f83bdd9085d9a7700b If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-38407 https://www.cve.org/CVERecord?id=CVE-2023-38407 [1] https://security-tracker.debian.org/tracker/CVE-2023-41361 https://www.cve.org/CVERecord?id=CVE-2023-41361 [2] https://security-tracker.debian.org/tracker/CVE-2023-46752 https://www.cve.org/CVERecord?id=CVE-2023-46752 [3] https://security-tracker.debian.org/tracker/CVE-2023-46753 https://www.cve.org/CVERecord?id=CVE-2023-46753 [4] https://security-tracker.debian.org/tracker/CVE-2023-47234 https://www.cve.org/CVERecord?id=CVE-2023-47234 [5] https://security-tracker.debian.org/tracker/CVE-2023-47235 https://www.cve.org/CVERecord?id=CVE-2023-47235 Please adjust the affected versions in the BTS as needed.
Bug#1054945: marked as done (haskell-yi-frontend-vty: FTBFS: unsatisfiable build-dependencies: libghc-array-dev-0.5.4.0-0b6fa, libghc-attoparsec-dev-0.14.4-9b901, libghc-base-dev-4.15.1.0-6a406, libgh
Your message dated Sun, 12 Nov 2023 15:51:13 + with message-id and subject line Bug#1054945: fixed in haskell-yi-frontend-vty 0.19.0-3 has caused the Debian Bug report #1054945, regarding haskell-yi-frontend-vty: FTBFS: unsatisfiable build-dependencies: libghc-array-dev-0.5.4.0-0b6fa, libghc-attoparsec-dev-0.14.4-9b901, libghc-base-dev-4.15.1.0-6a406, libghc-binary-dev-0.8.8.0-507cc, libghc-bytestring-dev-0.10.12.1-ced9a, libghc-containers-dev-0.6.4.1-31c3b, libghc-data-default-dev-0.7.1.1-6d3b3, libghc-directory-dev-1.3.6.2-311c9, libghc-dlist-dev-1.0-366f6, libghc-dynamic-state-dev-0.3.1-d49ee, libghc-exceptions-dev-0.10.4-c14ff, libghc-filepath-dev-1.4.2.1-4459f, libghc-hashable-dev-1.3.5.0-3fad8, libghc-listlike-dev-4.7.7-58f6d, libghc-microlens-platform-dev-0.4.2.1-8c955, libghc-mtl-dev-2.2.2-e3bae, libghc-old-locale-dev-1.0.0.7-60e52, libghc-oo-prototypes-dev-0.1.0.0-9dda4, libghc-parsec-dev-3.1.14.0-377f0, libghc-pointedlist-dev-0.6.1-f22c9, libghc-process-dev-1.6.13.2-9f25f, libghc-process-extras-dev-0.7.4-d5396, libghc-split-dev-0.2.3.5-0c13f, libghc-text-dev-1.2.5.0-8553e, libghc-time-dev-1.9.3-bda76, libghc-transformers-base-dev-0.4.6-a0a78, libghc-unix-compat-dev-0.5.4-1f010, libghc-unix-dev-2.7.2.2-bdab4, libghc-unordered-containers-dev-0.2.17.0-1d16d, libghc-xdg-basedir-dev-0.2.2-01215, libghc-yi-language-dev-0.19.0-ac372, libghc-yi-rope-dev-0.11-1df98, haddock-interface-38, libghc-array-prof-0.5.4.0-0b6fa, libghc-attoparsec-prof-0.14.4-9b901, libghc-base-prof-4.15.1.0-6a406, libghc-binary-prof-0.8.8.0-507cc, libghc-bytestring-prof-0.10.12.1-ced9a, libghc-containers-prof-0.6.4.1-31c3b, libghc-data-default-prof-0.7.1.1-6d3b3, libghc-directory-prof-1.3.6.2-311c9, libghc-dlist-prof-1.0-366f6, libghc-dynamic-state-prof-0.3.1-d49ee, libghc-exceptions-prof-0.10.4-c14ff, libghc-filepath-prof-1.4.2.1-4459f, libghc-hashable-prof-1.3.5.0-3fad8, libghc-listlike-prof-4.7.7-58f6d, libghc-microlens-platform-prof-0.4.2.1-8c955, libghc-mtl-prof-2.2.2-e3bae, libghc-old-locale-prof-1.0.0.7-60e52, libghc-oo-prototypes-prof-0.1.0.0-9dda4, libghc-parsec-prof-3.1.14.0-377f0, libghc-pointedlist-prof-0.6.1-f22c9, libghc-process-extras-prof-0.7.4-d5396, libghc-process-prof-1.6.13.2-9f25f, libghc-split-prof-0.2.3.5-0c13f, libghc-text-prof-1.2.5.0-8553e, libghc-time-prof-1.9.3-bda76, libghc-transformers-base-prof-0.4.6-a0a78, libghc-unix-compat-prof-0.5.4-1f010, libghc-unix-prof-2.7.2.2-bdab4, libghc-unordered-containers-prof-0.2.17.0-1d16d, libghc-xdg-basedir-prof-0.2.2-01215, libghc-yi-language-prof-0.19.0-ac372, libghc-yi-rope-prof-0.11-1df98 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054945 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-yi-frontend-vty Version: 0.19.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231028 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 10), haskell-devscripts-minimal | > haskell-devscripts (>= 0.9), cdbs, ghc (>= 8.4.3), ghc-prof, > libghc-data-default-dev, libghc-data-default-prof, libghc-dlist-dev, > libghc-dlist-prof, libghc-microlens-platform-dev, > libghc-microlens-platform-prof, libghc-pointedlist-dev, > libghc-pointedlist-prof, libghc-vty-dev (>= 5.4), libghc-vty-prof, > libghc-yi-core-dev (>= 0.19), libghc-yi-core-prof, libghc-yi-language-dev (>= > 0.19), libghc-yi-language-prof, libghc-yi-rope-dev (>= 0.10), > libghc-yi-rope-prof, build-essential, fakeroot, ghc-doc, > libghc-data-default-doc, libghc-dlist-doc, libghc-microlens-platform-doc, > libghc-pointedlist-doc, libghc-vty-doc, libghc-yi-core-doc, > libghc-yi-language-doc, libghc-yi-rope-doc > Filtered Build-Depends: debhelper (>= 10), haskell-devscripts-minimal, cdbs, > ghc (>= 8.4.3), ghc-prof, libghc-data-default-dev, libghc-data-default-prof, > libghc-dlist-dev, libghc-dlist-prof, libghc-microlens-platform-dev, > libghc-microlens-platform-prof, libghc-pointedlist-dev, > libghc-pointedlist-prof, libghc-vty-dev (>= 5.4), libghc-vty-prof, > libghc-yi-core-dev (>= 0.19), libghc-yi-core-prof,
Bug#1055843: marked as done (python-pyproj: Build-Depends on python3-xarray which is not in testing)
Your message dated Sun, 12 Nov 2023 15:37:18 + with message-id and subject line Bug#1055843: fixed in python-pyproj 3.6.1-2 has caused the Debian Bug report #1055843, regarding python-pyproj: Build-Depends on python3-xarray which is not in testing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1055843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pyproj Version: 3.6.1-1 Severity: serious Tags: ftbfs Hi Maintainer python-pyproj has a build-dependency on python3-xarray which is no longer in testing. Please drop this build-dependency or help get python3-xarray back into testing. Regards Graham --- End Message --- --- Begin Message --- Source: python-pyproj Source-Version: 3.6.1-2 Done: Bas Couwenberg We believe that the bug you reported is fixed in the latest version of python-pyproj, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bas Couwenberg (supplier of updated python-pyproj package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 12 Nov 2023 16:16:37 +0100 Source: python-pyproj Architecture: source Version: 3.6.1-2 Distribution: unstable Urgency: medium Maintainer: Debian GIS Project Changed-By: Bas Couwenberg Closes: 1055843 Changes: python-pyproj (3.6.1-2) unstable; urgency=medium . * Drop RC-buggy python3-xarray from build dependencies. (closes: #1055843) Checksums-Sha1: b806061fe690d774f8a44a8efef0ad93d80b3882 2344 python-pyproj_3.6.1-2.dsc 1feab2802c9b1b8106e7be9959e5bf2c0c0b6a61 8340 python-pyproj_3.6.1-2.debian.tar.xz 10cba734b56a02d5a14f0698a094f780a6252188 10890 python-pyproj_3.6.1-2_amd64.buildinfo Checksums-Sha256: 25c09f3d0a4bdbfd6e7d6e6c24a57585311de015e5bf540d7f64384d752f97a6 2344 python-pyproj_3.6.1-2.dsc f90bf31e67e6e538122330155d9d90b715afed10160e3f28fa90696524d8f831 8340 python-pyproj_3.6.1-2.debian.tar.xz 7200289fcec366c7ce7599b760c00ce4fce5b98a089d2c0037aaae0636dca346 10890 python-pyproj_3.6.1-2_amd64.buildinfo Files: 1ac52c5422cfd8c1b9b06066cc667155 2344 python optional python-pyproj_3.6.1-2.dsc 857718a9fbc57a32df2bdf91152698da 8340 python optional python-pyproj_3.6.1-2.debian.tar.xz c8472f7c3889219bb7b53b1ee10adf18 10890 python optional python-pyproj_3.6.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmVQ7X4ACgkQZ1DxCuiN SvENmQ//bjIXycV29xxSpFImlMbo9k7DdPCbJVX0Sx5bfSHr880nebgxvsaXYEId V4S9Xhv3F4My3OB3anqakFTU1CsCO5CeJeU7i+3+vHXC67UHwOsrt4g/cVDRJm// UNXO1fweYsu9l3FIdm2hwRc2yOA04ag0kaCIhttdpdvsN3PP1rWm+N6jPA6Vnz3C jAMtA24yzoLMoTjNLklRJJK4M+XeyTKCEExCS8G/qby+gCxu7jOcNZMfXHMSoWEm bBOhewnNjSoDdnuGC9ADyMTjH0TmYP9QSko25RWS9Xov+tN3JGvxlwbX4m18tUH5 Vg4RDii8qsR2HUz2JnvAE+AcvffMHkN7gr1WbTuTyCbmrQ6LWPRTvBNp+xnnk4Z9 /d7NuGpV0d7SX81H+dpvx7llBT4ruHsWYNRud8XWYeBe4Wa5GM0h799Tl1yVi9Ax 87cZeOUPj/74avpMNACvF4t7eZ34o+pcUEFIgqPVc6rGxWxmprGNv8aB2XKTVD/u yaxISFusGJ/cyDvmnAEFDE6XgkMGRHXqyLWrpSs9OI6WZ4zV6bUgB8EN7sUV+eXo ARiamm7hyYrJqLpVVjHkXwJZ2l3+bKdx7py0A7xDn8I3APdyKBdNCjnZjppeyify A0kq3TTJZ5wk2HpKBWgtTwIxxgr0fqA4C3ALK76YhJpZGXGt7eA= =RHq9 -END PGP SIGNATURE End Message ---
Bug#1055848: cfgrib: autopkgtest regression
Source: cfgrib
Version: 0.9.10.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
The upload of cfgrib 0.9.10.4-2 is failing its own autopkgtest [1].
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/c/cfgrib/testing/amd64/
80s autopkgtest [21:14:56]: test tryload: [---
80s Traceback (most recent call last):
80s File
"/tmp/autopkgtest-lxc.uvkmlxxf/downtmp/build.Qw6/src/debian/tests/tryload",
line 3, in
80s import cfgrib
80s File "/usr/lib/python3/dist-packages/cfgrib/__init__.py", line
20, in
80s from .cfmessage import COMPUTED_KEYS
80s File "/usr/lib/python3/dist-packages/cfgrib/cfmessage.py", line
29, in
80s from . import abc, messages
80s File "/usr/lib/python3/dist-packages/cfgrib/messages.py", line
28, in
80s import eccodes # type: ignore
80s ^^
80s File "/usr/lib/python3/dist-packages/eccodes/__init__.py", line
13, in
80s from .eccodes import * # noqa
80s ^^
80s File "/usr/lib/python3/dist-packages/eccodes/eccodes.py", line
12, in
80s from gribapi import (
80s File "/usr/lib/python3/dist-packages/gribapi/__init__.py", line
13, in
80s from .gribapi import * # noqa
80s ^^
80s File "/usr/lib/python3/dist-packages/gribapi/gribapi.py", line
34, in
80s from gribapi.errors import GribInternalError
80s File "/usr/lib/python3/dist-packages/gribapi/errors.py", line
16, in
80s from .bindings import ENC, ffi, lib
80s File "/usr/lib/python3/dist-packages/gribapi/bindings.py", line
35, in
80s raise RuntimeError("Cannot find the ecCodes library")
80s RuntimeError: Cannot find the ecCodes library
Bug#1055847: python-sparse: autopkgtest regression on arm64 and s390x
Source: python-sparse Version: 0.14.0-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer The upload of python-sparse 0.14.0-1 is failing its own autopkgtest on arm64 and s390x [1][2]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/p/python-sparse/testing/arm64/ [2] https://ci.debian.net/packages/p/python-sparse/testing/s390x/ 60s autopkgtest [15:18:15]: test command1: set -e ; cp -r sparse/tests "$AUTOPKGTEST_TMP" ; for py in $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -m pytest -v ; done 60s autopkgtest [15:18:15]: test command1: [--- 60s Testing with python3.11: 60s = test session starts == 60s platform linux -- Python 3.11.6, pytest-7.4.3, pluggy-1.3.0 -- /usr/bin/python3.11 60s cachedir: .pytest_cache 60s rootdir: /tmp/autopkgtest-lxc.ia_llwxf/downtmp/autopkgtest_tmp 63s collecting ... collected 5496 items 63s 67s tests/test_array_function.py::test_unary[mean] Fatal Python error: Segmentation fault
Bug#1055843: python-pyproj: Build-Depends on python3-xarray which is not in testing
On 11/12/23 15:46, Graham Inggs wrote: python-pyproj has a build-dependency on python3-xarray which is no longer in testing. xarray is required for test/test_utils.py. Please drop this build-dependency or help get python3-xarray back into testing. I already provided a patch for python-xarray in #1050854, but I'm not willing to NMU the package. Alastair doesn't push his changes to Salsa far too often. I'd be willing to do a team upload if it was a properly team maintained package, but Alastair's packages aren't. By providing the patch in #1050854, I've already done what I can to fix the xarray mess, now it's up to someone else to resolve the outstanding issues with that badly maintained package. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1054946: marked as done (distro-info: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2)
Your message dated Sun, 12 Nov 2023 15:02:26 + with message-id and subject line Bug#1054946: fixed in distro-info 1.0+deb11u1 has caused the Debian Bug report #1054946, regarding distro-info: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054946 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: distro-info Version: 1.6 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231028 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > ./test-debian-distro-info > cd perl && ./test.pl > testAlias > testAll > py3versions: no X-Python3-Version in control file, using supported versions > testDevel > cd python && python3.11 setup.py test > 1..35 > ok 1 - unique: Matching lists > ok 2 - symmetric_difference: Matching lists > ok 3 - unique: 1 Unique Item > ok 4 - unique: 1 Unique Item in the haystack > ok 5 - symmetric_difference: 1 Unique Item > ok 6 - Debian all > ok 7 - Debian devel > ok 8 - Debian oldstable > ok 9 - Debian stable > ok 10 - Debian testing > ok 11 - Debian valid > ok 12 - Debian valid > ok 13 - Debian invalid > ok 14 - Debian supported > ok 15 - Debian LTS > ok 16 - Debian ELTS > ok 17 - Debian unsupported > ok 18 - Debian codename, invalid > ok 19 - Debian codename > ok 20 - Debian version, invalid > ok 21 - Debian version > testOldstable > ok 22 - Ubuntu all > ok 23 - Ubuntu version > ok 24 - Ubuntu LTS version > ok 25 - Ubuntu devel > ok 26 - Ubuntu LTS > ok 27 - Ubuntu stable > ok 28 - Ubuntu valid > ok 29 - Ubuntu invalid > ok 30 - Ubuntu is_lts > ok 31 - Ubuntu !is_lts > ok 32 - Ubuntu !is_lts > ok 33 - Ubuntu supported > ok 34 - Ubuntu ESM > ok 35 - Ubuntu unsupported > testStable > testSupported > testLTS > testELTS > testUnsupported > testTesting > testFullname > running test > WARNING: Testing via this command is deprecated and will be removed in a > future version. Users looking for a generic test entry point independent of > test runner are encouraged to use tox. > /usr/lib/python3/dist-packages/setuptools/command/test.py:193: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > ir_d = dist.fetch_build_eggs(dist.install_requires) > WARNING: The wheel package is not available. > /usr/lib/python3/dist-packages/setuptools/command/test.py:194: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > tr_d = dist.fetch_build_eggs(dist.tests_require or []) > WARNING: The wheel package is not available. > /usr/lib/python3/dist-packages/setuptools/command/test.py:195: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > er_d = dist.fetch_build_eggs( > WARNING: The wheel package is not available. > running egg_info > creating distro_info.egg-info > writing distro_info.egg-info/PKG-INFO > writing dependency_links to distro_info.egg-info/dependency_links.txt > writing top-level names to distro_info.egg-info/top_level.txt > writing manifest file 'distro_info.egg-info/SOURCES.txt' > testRelease > reading manifest file 'distro_info.egg-info/SOURCES.txt' > writing manifest file 'distro_info.egg-info/SOURCES.txt' > running build_ext > testSeries > testCombinedShortform > test_flake8 (distro_info_test.test_flake8.Flake8TestCase.test_flake8) > Test: Run flake8 on Python source
Bug#1055845: matplotlib: Build-Depends on python3-xarray which is not in testing
Source: matplotlib Version: 3.6.3-1 Severity: serious Tags: ftbfs Hi Maintainer matplotlib has a build-dependency on python3-xarray which is no longer in testing. Please drop this build-dependency or help get python3-xarray back into testing. Regards Graham
Bug#1055844: pandas: Build-Depends on python3-xarray which is not in testing
Source: pandas Version: 1.5.3+dfsg-6 Severity: serious Tags: ftbfs Hi Maintainer pandas has a build-dependency on python3-xarray which is no longer in testing. Please drop this build-dependency or help get python3-xarray back into testing. Regards Graham
Bug#1055843: python-pyproj: Build-Depends on python3-xarray which is not in testing
Source: python-pyproj Version: 3.6.1-1 Severity: serious Tags: ftbfs Hi Maintainer python-pyproj has a build-dependency on python3-xarray which is no longer in testing. Please drop this build-dependency or help get python3-xarray back into testing. Regards Graham
Bug#1055841: spyder-kernels: Build-Depends on python3-xarray which is not in testing
Source: spyder-kernels Version: 2.4.4-2 Severity: serious Tags: ftbfs Hi Maintainer spyder-kernels has a build-dependency on python3-xarray which is no longer in testing. Please drop this build-dependency or help get python3-xarray back into testing. Regards Graham
Bug#1055643: marked as done (mutter 45.1 not installable from experimental)
Your message dated Sun, 12 Nov 2023 12:03:36 +0100 with message-id and subject line Re: Bug#1055643: Acknowledgement (mutter 45.1 not installable from experimental) has caused the Debian Bug report #1055643, regarding mutter 45.1 not installable from experimental to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1055643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055643 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mutter Version: 45.1-1 Severity: normal Dear Maintainer, * What led up to the situation? sudo apt install mutter -t experimental Die folgenden Pakete haben unerfüllte Abhängigkeiten: mutter : Hängt ab von: mutter-common (>= 45.1-1) aber 45.0-3 soll installiert werden E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene defekte Pakete. * What exactly did you do (or not do) that was effective (or ineffective)? cannot do anything about it * What was the outcome of this action? NA * What outcome did you expect instead? mutter-common 45.1 seems to be missing in experimental -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-4-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mutter depends on: ii adwaita-icon-theme45.0-1 ii gnome-settings-daemon-common 45.0-1 ii gsettings-desktop-schemas 45.0-1 ii libc6 2.37-12 ii libgles2 1.7.0-1 ii libglib2.0-0 2.78.1-2 ii libmutter-13-045.0-3 ii libwayland-client01.22.0-2.1 ii mutter-common 45.0-3 ii zenity3.44.2-1 mutter recommends no packages. Versions of packages mutter suggests: ii gnome-control-center 1:45.1-1 ii xdg-user-dirs 0.18-1 -- no debconf information --- End Message --- --- Begin Message --- Am Donnerstag, dem 09.11.2023 um 14:06 + schrieb Debian Bug Tracking System: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 1055643: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055643. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due > course. > > Your message has been sent to the package maintainer(s): > Debian GNOME Maintainers > > > If you wish to submit further information on this problem, please > send it to 1055...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > -- Grüße / Regards Christian visit http://www.lauinger-clan.de Realität ist, wenn Du's nicht mit der Maus wegklicken kannst.--- End Message ---
Bug#1055818: marked as done (lazygal: autogtest failures with ffmpeg 6.1)
Your message dated Sun, 12 Nov 2023 10:37:15 + with message-id and subject line Bug#1055818: fixed in lazygal 0.10.8-1 has caused the Debian Bug report #1055818, regarding lazygal: autogtest failures with ffmpeg 6.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1055818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lazygal Version: 0.10.7-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org >From >https://ci.debian.net/data/autopkgtest/testing/amd64/l/lazygal/39801395/log.gz: 40s running sample_album 40s [Entering %ALBUMROOT%/beers] 40s DUMPJSON index.json 40s MKDIR %WEBALBUMROOT%/beers 40s BREAKING web gallery into multiple pages 40s RESIZE kilkenny_small.jpg 40s RESIZE kilkenny_medium.jpg 40s RESIZE kilkenny_thumb.jpg 40s RESIZE guinness_small.jpg 40s RESIZE guinness_medium.jpg 40s RESIZE guinness_thumb.jpg 40s JSONWEBASSETS webassets.json 40s SORTING pics and subdirs 40s XHTML kilkenny.html 40s XHTML guinness.html 40s XHTML index.html 40s XHTML kilkenny_medium.html 40s XHTML guinness_medium.html 40s XHTML index_medium.html 40s DIRPIC index.png 40s [Leaving %ALBUMROOT%/beers] 40s [Entering %ALBUMROOT%/flower] 40s DUMPJSON index.json 40s MKDIR %WEBALBUMROOT%/flower 40s BREAKING web gallery into multiple pages 40s TRANSCODE nature_video.webm 41s VIDEOTHUMB nature_thumb.jpg 41s not enough values to unpack (expected 3, got 1) 41s autopkgtest [15:15:21]: test smoke: ---] ffmpeg's output on stdout changed and VideoProcessor.parse_output needs to be changed accordingly. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: lazygal Source-Version: 0.10.8-1 Done: Alexandre Rossi We believe that the bug you reported is fixed in the latest version of lazygal, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Rossi (supplier of updated lazygal package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 12 Nov 2023 11:14:35 +0100 Source: lazygal Architecture: source Version: 0.10.8-1 Distribution: unstable Urgency: medium Maintainer: Michal Čihař Changed-By: Alexandre Rossi Closes: 1046272 1055818 Changes: lazygal (0.10.8-1) unstable; urgency=medium . * properly clean build artifacts (Closes: #1046272) * New upstream version 0.10.8 (Closes: #1055818) Checksums-Sha1: 967cb8a91445dfc3ddcc4fb6c36a2c61b8782049 2116 lazygal_0.10.8-1.dsc 451867431d2df0a4c4d18608edfdf7b319f1d06c 818024 lazygal_0.10.8.orig.tar.bz2 acb3338aba822a3ec821326d04abb9183dcf2d91 5076 lazygal_0.10.8-1.debian.tar.xz 60a65beded7b600f4941e14d59a0ec4c3973a894 7089 lazygal_0.10.8-1_amd64.buildinfo Checksums-Sha256: ccb6a5afc3f573f1d9fee09a5155a35771a275996a97fc52c6f3213fc8550557 2116 lazygal_0.10.8-1.dsc 96120babdab25a36f5d81d068b7f41e39ef92072322d674f0c6bb484e2c151b0 818024 lazygal_0.10.8.orig.tar.bz2 7106e7bbfd754f5707244dd4b893bdf85381e63c7267866039be1e2fdf9117ab 5076 lazygal_0.10.8-1.debian.tar.xz d50398280cea3f2a4621594d3ab3f17c9701464642c799650d574dcff6ec00ee 7089 lazygal_0.10.8-1_amd64.buildinfo Files: 0dede41bae1818762bbf88062bc7f0d5 2116 graphics optional lazygal_0.10.8-1.dsc d6dd13f9b639748db2bbb9e5f3f7894f 818024 graphics optional lazygal_0.10.8.orig.tar.bz2 0a1aea58f8202cf9ca45b0a8144f342d 5076 graphics optional lazygal_0.10.8-1.debian.tar.xz 3c7df2411af38168a11124cb75622335 7089 graphics optional lazygal_0.10.8-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEqURFrS/GV/h4cdpsWI+eupOKFo8FAmVQpm8ACgkQWI+eupOK Fo/hshAAtyl31kcGezs0h9T3YD/k7mFPQpoHxmyAwU1sMq9MxKxIjzniGbJSaepH 0hG8huhFOs2ipwFX6WQ1Qrk4gG5de7Y26mh/GvtCJu3Tl+ewjNP91cwNiENSqdsC J/kBubMsXn2TWhktru0lzFSgmvfF/WXDhujS4B04JNG7qalraRQRrKY0Cdg+Xb2W e0vbbVmpwizkteCYFbcMkQaurLo4Xir5mYY3dFrCLBXk/pJJxkTpd1oEnJYuNr0T EJo6jr9RCnJruLUJ/JjOpKGTfjPCX8RR6bWxTkpmbj6wyNroVW1vBTjFZ4/vCSxk F2PBWeHmM6dRvqz0XveKYj+hCrA3DGtgKs5yveu98TW3XvD2o35+SRoo7Potdd9Y
Processed: reassign 1054894 to ghc, severity of 1054894 is important, affects 1054894
Processing commands for cont...@bugs.debian.org: > reassign 1054894 ghc 9.4.7-1 Bug #1054894 [src:haskell-bytestring-lexing] haskell-bytestring-lexing: FTBFS on ppc64el: unrecognized opcode: `clrrhi' Bug reassigned from package 'src:haskell-bytestring-lexing' to 'ghc'. No longer marked as found in versions haskell-bytestring-lexing/0.5.0.10-1. Ignoring request to alter fixed versions of bug #1054894 to the same values previously set Bug #1054894 [ghc] haskell-bytestring-lexing: FTBFS on ppc64el: unrecognized opcode: `clrrhi' Marked as found in versions ghc/9.4.7-1. > severity 1054894 important Bug #1054894 [ghc] haskell-bytestring-lexing: FTBFS on ppc64el: unrecognized opcode: `clrrhi' Severity set to 'important' from 'serious' > affects 1054894 haskell-bytestring-lexing Bug #1054894 [ghc] haskell-bytestring-lexing: FTBFS on ppc64el: unrecognized opcode: `clrrhi' Added indication that 1054894 affects haskell-bytestring-lexing > thanks Stopping processing here. Please contact me if you need assistance. -- 1054894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 1055828 in qxmpp/1.5.5-0.2~exp1, closing 1055828
Processing commands for cont...@bugs.debian.org: > fixed 1055828 qxmpp/1.5.5-0.2~exp1 Bug #1055828 [libqxmppqt5-dev] libqxmppqt5-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/pkgconfig/qxmpp.pc Marked as fixed in versions qxmpp/1.5.5-0.2~exp1. > close 1055828 Bug #1055828 [libqxmppqt5-dev] libqxmppqt5-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/pkgconfig/qxmpp.pc Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1055828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libqxmppqt5-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/pkgconfig/qxmpp.pc
Processing control commands: > affects -1 + libqxmpp-dev Bug #1055828 [libqxmppqt5-dev] libqxmppqt5-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/pkgconfig/qxmpp.pc Added indication that 1055828 affects libqxmpp-dev -- 1055828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055828: libqxmppqt5-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/pkgconfig/qxmpp.pc
Package: libqxmppqt5-dev Version: 1.5.5-0.1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libqxmpp-dev libqxmppqt5-dev has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/x86_64-linux-gnu/pkgconfig/qxmpp.pc is contained in the packages * libqxmpp-dev * 1.3.2-2 as present in bullseye * 1.4.0-2 as present in bookworm|trixie|unstable * 1.4.0-2~bpo11+1 as present in bullseye-backports * libqxmppqt5-dev/1.5.5-0.1~exp1 as present in experimental These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected file. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance.
