Your message dated Mon, 02 Sep 2013 18:18:27 +0200
with message-id <6929814.usOo0msph1@sephirot>
and subject line Re: Bug#720806: openvpn: FTBFS: configure: error: lzo enabled
but missing
has caused the Debian Bug report #720806,
regarding openvpn: FTBFS: configure: error: lzo enabled but missing
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.)
--
720806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720806
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openvpn
Version: 2.3.2-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130825 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):
> checking for ssl_init in -lpolarssl... no
> checking for aes_crypt_cbc in -lpolarssl... no
> checking for lzo1x_1_15_compress in -llzo2... no
> checking for lzo1x_1_15_compress in -llzo... no
> checking git checkout... no
> configure: error: lzo enabled but missing
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/08/25/openvpn_2.3.2-4_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 ---
Hola Alberto,
> tags 720806 + unreproducible
> thanks
>
> Hi, I cannot reproduce this on a clean & updated env. This bug may
> have been triggered by this other one [1].
>
> [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720749
Uhm, yep is caused by [1] (now builds ok). Sorry for that :)
I'm simply closing this bug because [1] is fixed too.
Thanks
David
--- End Message ---