Bug#1024992: libsoup2.4: FTBFS when built using sbuild in bullseye
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.
Bug#1024992: libsoup2.4: FTBFS when built using sbuild in bullseye
Package: src:libsoup2.4 Version: 2.74.3-1 Tags: ftbfs X-Debbugs-Cc: sanv...@debian.org,jo...@debian.org 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.
