Re: circular build-dependency in debconf
- To: firstname.lastname@example.org
- Cc: email@example.com
- Subject: Re: circular build-dependency in debconf
- From: Steve Bowman <firstname.lastname@example.org>
- Date: Tue, 17 Oct 2000 21:27:17 -0700
- Message-id: <20001017212717.A937@frostwork.net>
- In-reply-to: <20001017200952.A5440@frostwork.net>; from email@example.com on Tue, Oct 17, 2000 at 08:09:52PM -0700
- References: <firstname.lastname@example.org> <20001017114346.B6911@x8b4e516e.dhcp.okstate.edu> <20001018050812.A21050@azure.humbug.org.au> <20001017130607.A14868@kitenet.net> <20001017200952.A5440@frostwork.net>
Sorry to reply to myself but...
On Tue, Oct 17, 2000 at 08:09:52PM -0700, Steve Bowman wrote:
> What I'm wondering about is why debconf hasn't made it into hurd-i386.
> With the number of packages available for the hurd, I'm guessing there's
> an autobuilder running somewhere. Since debconf-utils is available and
> the other build dependencies seem to be met, I'd have thought debconf
> would have been built by now. Am I wrong about the autobuilder or is
> there something else keeping debconf from autobuilding on hurd-i386?
I think I just answered my own question. After purging debconf and
debconf-utils, I found that I had to use --force-depends to install
debconf-utils. After that, debconf built fine (with the same warnings
already reported on debian-hurd). Setting PATH is not needed as
previously reported on d-h.
Steve Bowman <email@example.com> (preferred)
Buckeye, AZ <firstname.lastname@example.org> <email@example.com>
Powered by Debian GNU/Linux and GNU/Hurd <http://www.debian.org>