Bug#844822: xymon: FTBFS: build-dependency not installable: libssl-dev (>= 1.0.2d-2~)
Control: unblock -1 by 828236 Control: reassign -1 apache2-dev Control: forcemerge 845033 -1 Hi, Axel Beckert wrote: > Lucas Nussbaum wrote: > > > Merged Build-Depends: debhelper (>= 9~), dh-apache2, dpkg-dev (>= > > > 1.16.1~), imagemagick, libc-ares-dev, libldap2-dev (>= 2.4.25-2~), > > > libpcre3-dev (>= 8.12-4~), librrd-dev, libssl-dev (>= 1.0.2d-2~), > > > po-debconf, procps > > > Filtered Build-Depends: debhelper (>= 9~), dh-apache2, dpkg-dev (>= > > > 1.16.1~), imagemagick, libc-ares-dev, libldap2-dev (>= 2.4.25-2~), > > > libpcre3-dev (>= 8.12-4~), librrd-dev, libssl-dev (>= 1.0.2d-2~), > > > po-debconf, procps > [...] > > > The following packages have unmet dependencies: > > > sbuild-build-depends-xymon-dummy : Depends: libssl-dev (>= 1.0.2d-2~) > > > but it is not going to be installed > > This is because apache2-dev (which provides dh-apache2) depends on > "libssl1.0-dev | libssl-dev (<< 1.1)". So the reason are conflicting > build-dependencies because some build-dependencies are ready for > OpenSSL 1.1 and others are not. > > I'm not sure if this is really an issue of xymon. It could be > workarounded by using "libssl1.0-dev | libssl-dev" in xymon, but then > xymon in Debian needlessly would be build against OpenSSL 1.0.x which > I at most consider a temporary solution. This has been fixed in the apache2 source package by splitting off an apache2-ssl-dev package from apache2-dev. Merging this bug report with #845033 (https://bugs.debian.org/845033) as it has been done with the according FTBFS bug report against cgit. Regards, Axel -- ,''`. | Axel Beckert, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#844822: xymon: FTBFS: build-dependency not installable: libssl-dev (>= 1.0.2d-2~)
Control: tag -1 + moreinfo Control: block -1 by 828236 Hi, Lucas Nussbaum wrote: > > Merged Build-Depends: debhelper (>= 9~), dh-apache2, dpkg-dev (>= 1.16.1~), > > imagemagick, libc-ares-dev, libldap2-dev (>= 2.4.25-2~), libpcre3-dev (>= > > 8.12-4~), librrd-dev, libssl-dev (>= 1.0.2d-2~), po-debconf, procps > > Filtered Build-Depends: debhelper (>= 9~), dh-apache2, dpkg-dev (>= > > 1.16.1~), imagemagick, libc-ares-dev, libldap2-dev (>= 2.4.25-2~), > > libpcre3-dev (>= 8.12-4~), librrd-dev, libssl-dev (>= 1.0.2d-2~), > > po-debconf, procps [...] > > The following packages have unmet dependencies: > > sbuild-build-depends-xymon-dummy : Depends: libssl-dev (>= 1.0.2d-2~) but > > it is not going to be installed This is because apache2-dev (which provides dh-apache2) depends on "libssl1.0-dev | libssl-dev (<< 1.1)". So the reason are conflicting build-dependencies because some build-dependencies are ready for OpenSSL 1.1 and others are not. I'm not sure if this is really an issue of xymon. It could be workarounded by using "libssl1.0-dev | libssl-dev" in xymon, but then xymon in Debian needlessly would be build against OpenSSL 1.0.x which I at most consider a temporary solution. Please advise how to proceed. Regards, Axel -- ,''`. | Axel Beckert, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#844822: xymon: FTBFS: build-dependency not installable: libssl-dev (>= 1.0.2d-2~)
Source: xymon Version: 4.3.27-3 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161118 qa-ftbfs Justification: FTBFS on amd64 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 (>= 9~), dh-apache2, dpkg-dev (>= 1.16.1~), > imagemagick, libc-ares-dev, libldap2-dev (>= 2.4.25-2~), libpcre3-dev (>= > 8.12-4~), librrd-dev, libssl-dev (>= 1.0.2d-2~), po-debconf, procps > Filtered Build-Depends: debhelper (>= 9~), dh-apache2, dpkg-dev (>= 1.16.1~), > imagemagick, libc-ares-dev, libldap2-dev (>= 2.4.25-2~), libpcre3-dev (>= > 8.12-4~), librrd-dev, libssl-dev (>= 1.0.2d-2~), po-debconf, procps > dpkg-deb: building package 'sbuild-build-depends-xymon-dummy' in > '/<>/resolver-3Yu5nv/apt_archive/sbuild-build-depends-xymon-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-xymon-dummy > dpkg-scanpackages: info: Wrote 1 entries to output Packages file. > Ign:1 copy:/<>/resolver-3Yu5nv/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-3Yu5nv/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/resolver-3Yu5nv/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-3Yu5nv/apt_archive ./ Sources [435 B] > Get:5 copy:/<>/resolver-3Yu5nv/apt_archive ./ Packages [523 B] > Fetched 1915 B in 0s (0 B/s) > Reading package lists... > W: No sandbox user '_apt' on the system, can not drop privileges > Reading package lists... > > Install xymon build dependencies (apt-based resolver) > - > > 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-xymon-dummy : Depends: libssl-dev (>= 1.0.2d-2~) but it > is not going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2016/11/18/xymon_4.3.27-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.