Your message dated Fri, 7 Aug 2009 09:20:16 +0300
with message-id <[email protected]>
and subject line Re: Bug#540017: Circular build dependency of
libemail-send-io-perl and libemail-send-perl
has caused the Debian Bug report #540017,
regarding Circular build dependency of libemail-send-io-perl and
libemail-send-perl
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 [email protected]
immediately.)
--
540017: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540017
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libemail-send-perl
Version: 2.192-3
In Lenny libemail-send-perl and libemail-send-io-perl have circular build
dependencies that prevent a build of these packages from scratch.
$ grep "Build-Depends-Indep:" libemail-send-perl_2.192-3.dsc
Build-Depends-Indep: perl (>= 5.8.0-7), ......., libemail-send-io-perl
$ grep "Build-Depends-Indep:" libemail-send-io-perl_2.200-1.dsc
Build-Depends-Indep: perl (>= 5.8.8-9), libemail-send-perl, .......
$
Greetings
Sönke
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
notfound 540017 2.192-3
thanks
-=| gregor herrmann, Fri, Aug 07, 2009 at 04:18:30AM +0200 |=-
> On Wed, 05 Aug 2009 09:19:19 +0200, Sönke Schwardt-Krummrich wrote:
> > In Lenny libemail-send-perl and libemail-send-io-perl have
> > circular build dependencies that prevent a build of these packages
> > from scratch.
> I agree that circular build dependencies are ugly, but at the moment
> I fail to see the actual problem; both packages build fine for me ...
The problem appears when none of the packages are available (for
example you are starting a new Debian derivative or somesuch).
What I'd suggest is dropping the appropriate B-D-I entry, build both,
make them available in the "from scratch" environment, then put the
B-D-I entry back and rebuild. You should be able to do this as
I suspect one of the B-D-I entries is used only for tests (which are
skipped if the module is not available).
Requires work, but since we don't actualy care about being able to
rebuild the archive from scratch, this is your only option.
I am closing the bug report.
--
dam
signature.asc
Description: Digital signature
--- End Message ---
