Your message dated Wed, 20 Apr 2011 09:55:55 +0300
with message-id <BANLkTi=mAyFrfSUmRi=oetigmaxkja+...@mail.gmail.com>
and subject line Closing libbsd-dev bugs for armhf.
has caused the Debian Bug report #623347,
regarding FTBFS: please add libbsd-dev to the build deps
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.)
--
623347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libapache2-mod-perl2
Version: 2.0.5-1
Severity: serious
The package fails to build from source if the buildd does not have
libbsd-dev already installed:
http://buildd.debian-ports.org/status/fetch.php?pkg=libapache2-mod-perl2&arch=armhf&ver=2.0.5-1&stamp=1303207503
libbsd-dev is an optional package, some buildds might have it, but
it's not a requirement.
Please add it in the build dependencies.
Thanks
Konstantinos
--- End Message ---
--- Begin Message ---
On Tue, Apr 19, 2011 at 06:17:05PM +0200, Dominique Dumont wrote:
> I believe this is a bug in perl that I happend to fix recently in
> 5.12.3-3/experimental after noticing a Ubuntu deviation:
>
> * debian/config.debian: never use <libutil.h>, even if libbsd-dev is
> installed. Inspired by a similar Ubuntu change.
>
> The problem is that if perl is compiled with libbsd-dev installed,
> the headers require <libutil.h> for all other packages too.
>
> I'll fix it for the next sid upload too, but in the meanwhile, binNMUing
> perl on armhf without libbsd-dev should fix the immediate problem.
This is exactly what I did, apparently the previous perl build for armhf was
done with libbsd-dev installed, so what you suggested happened, once
I decided to clean up the buildds from redundant packages.
All problematic packages were then rebuilt with the newer perl and there
was no error.
So I am closing the bugs as false alarms. Sorry for the fuss eveyone...
Thanks
Konstantinos
--- End Message ---
