Your message dated Mon, 19 Dec 2016 20:04:18 -0800
with message-id
<CAMzhQmMciW5k5T=vj9g_QUyK8Rg9oT=towv_hfizc_zp5sz...@mail.gmail.com>
and subject line Re: Bug#844829: mahimahi: FTBFS: build-dependency not
installable: apache2-dev
has caused the Debian Bug report #844829,
regarding mahimahi: FTBFS: build-dependency not installable: apache2-dev
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.)
--
844829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mahimahi
Version: 0.95-1
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), autotools-dev, dh-autoreconf,
> iptables, protobuf-compiler, libprotobuf-dev, pkg-config, libssl-dev,
> dnsmasq-base, ssl-cert, libxcb-present-dev, libcairo2-dev, libpango1.0-dev,
> iproute2, apache2-dev, apache2-bin
> Filtered Build-Depends: debhelper (>= 9), autotools-dev, dh-autoreconf,
> iptables, protobuf-compiler, libprotobuf-dev, pkg-config, libssl-dev,
> dnsmasq-base, ssl-cert, libxcb-present-dev, libcairo2-dev, libpango1.0-dev,
> iproute2, apache2-dev, apache2-bin
> dpkg-deb: building package 'sbuild-build-depends-mahimahi-dummy' in
> '/<<BUILDDIR>>/resolver-UmDOUz/apt_archive/sbuild-build-depends-mahimahi-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override
> file:
> dpkg-scanpackages: warning: sbuild-build-depends-mahimahi-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<<BUILDDIR>>/resolver-UmDOUz/apt_archive ./ InRelease
> Get:2 copy:/<<BUILDDIR>>/resolver-UmDOUz/apt_archive ./ Release [957 B]
> Ign:3 copy:/<<BUILDDIR>>/resolver-UmDOUz/apt_archive ./ Release.gpg
> Get:4 copy:/<<BUILDDIR>>/resolver-UmDOUz/apt_archive ./ Sources [450 B]
> Get:5 copy:/<<BUILDDIR>>/resolver-UmDOUz/apt_archive ./ Packages [542 B]
> Fetched 1949 B in 0s (181 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
>
> Install mahimahi 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-mahimahi-dummy : Depends: apache2-dev 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/mahimahi_0.95-1_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.
--- End Message ---
--- Begin Message ---
We have been unable to reproduce this bug ("Depends: apache2-dev but it is
not going to be installed"). It seems to have been a glitch in the system
that auto-generated it.
mahimahi 0.95-1 was a source-only upload and built successfully on the
buildds. We just uploaded mahimahi 0.96-1 as a source-only upload (without
change to the build-dependencies), and it also built successfully on the
buildds.
There don't seem to have been any relevant changes in the way that apache2
builds the apache2-dev package. The logs in the link do not provide enough
detail to see why it thought apache2-dev was uninstallable.
Conclusion: We think the bug is invalid, but please feel free to reopen if
you have information to the contrary.
On Fri, Nov 18, 2016 at 10:25 PM, Lucas Nussbaum <lu...@debian.org> wrote:
> Source: mahimahi
> Version: 0.95-1
> 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), autotools-dev, dh-autoreconf,
> iptables, protobuf-compiler, libprotobuf-dev, pkg-config, libssl-dev,
> dnsmasq-base, ssl-cert, libxcb-present-dev, libcairo2-dev, libpango1.0-dev,
> iproute2, apache2-dev, apache2-bin
> > Filtered Build-Depends: debhelper (>= 9), autotools-dev, dh-autoreconf,
> iptables, protobuf-compiler, libprotobuf-dev, pkg-config, libssl-dev,
> dnsmasq-base, ssl-cert, libxcb-present-dev, libcairo2-dev, libpango1.0-dev,
> iproute2, apache2-dev, apache2-bin
> > dpkg-deb: building package 'sbuild-build-depends-mahimahi-dummy' in
> '/<<BUILDDIR>>/resolver-UmDOUz/apt_archive/sbuild-build-
> depends-mahimahi-dummy.deb'.
> > dpkg-scanpackages: warning: Packages in archive but missing from
> override file:
> > dpkg-scanpackages: warning: sbuild-build-depends-mahimahi-dummy
> > dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> > Ign:1 copy:/<<BUILDDIR>>/resolver-UmDOUz/apt_archive ./ InRelease
> > Get:2 copy:/<<BUILDDIR>>/resolver-UmDOUz/apt_archive ./ Release [957 B]
> > Ign:3 copy:/<<BUILDDIR>>/resolver-UmDOUz/apt_archive ./ Release.gpg
> > Get:4 copy:/<<BUILDDIR>>/resolver-UmDOUz/apt_archive ./ Sources [450 B]
> > Get:5 copy:/<<BUILDDIR>>/resolver-UmDOUz/apt_archive ./ Packages [542 B]
> > Fetched 1949 B in 0s (181 kB/s)
> > Reading package lists...
> > W: No sandbox user '_apt' on the system, can not drop privileges
> > Reading package lists...
> >
> > Install mahimahi 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-mahimahi-dummy : Depends: apache2-dev 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/mahimahi_0.95-1_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.
>
--- End Message ---
