Your message dated Tue, 31 Jan 2023 13:23:39 +0100
with message-id <[email protected]>
and subject line libsoup2.4: FTBFS when built using sbuild in bullseye
has caused the Debian Bug report #1024992,
regarding libsoup2.4: FTBFS when built using sbuild in bullseye
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 [email protected]
immediately.)
--
1024992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024992
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:libsoup2.4
Version: 2.74.3-1
Tags: ftbfs
X-Debbugs-Cc: [email protected],[email protected]
Dear maintainer:
During a rebuild of all packages in bookworm I noticed that sbuild
(bullseye version) is unable to install the build-dependencies of
libsoup2.4:
Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
sbuild-build-depends-main-dummy : Depends: php-xmlrpc but it is not
installable
E: Unable to correct problems, you have held broken packages.
apt-get failed.
E: Package installation failed
Not removing build depends: cloned chroot in use
I think this would not happen if every build-dependency using "OR"
(there are several of them) was specified like this:
build-depends: real-package | virtual-package
which AFAIK has always been the standard for dependencies.
(I'm Cc:ing to Johannes Schauer (sbuild) in case he has any comments).
Thanks.
--- End Message ---
--- Begin Message ---
This seems fixed, as I can build this package again using the
sbuild program from bullseye (in a bookworm chroot).
Because the package itself has not changed, I assume this
is due to a change in the dependencies of one of its
build-dependencies.
If somebody knows for sure which package it was, feel free
to reassign and add affects src:libsoup2.4.
(Maybe it was php-xmlrpc, so I'm Cc:ing Ondřej)
If not, I don't think it's worth the effort to investigate
(the list of build-dependencies is too long).
In either case, thanks a lot to whoever fixed this.
--- End Message ---
