Argl, I'm blind ... [EMAIL PROTECTED] (Gai Sum) writes:
> [EMAIL PROTECTED] (Robert Bihlmeyer) wrote in message news:<[EMAIL
> PROTECTED]>...
> > [EMAIL PROTECTED] (Gai Sum) writes:
> >
> > > [EMAIL PROTECTED] (Robert Bihlmeyer) wrote in message news:<[EMAIL
> > > PROTECTED]>...
> > > > Well, debconf 0.2.80.17 (which is the current potato version, AFAIK)
> > > > has "/usr/lib/perl5/Debian/DebConf/Client/ConfModule.pm" [...]
^^^^^^
> > /usr/lib/perl5/Debconf/Client/ConfModule.pm should be found since
/^\
> $ perl -MDebconf::Client::ConfModule -e42
> Can't locate Debconf/Client/ConfModule.pm in @INC (@INC contains:
> /usr/lib/perl5/5.005/i386-linux /usr/lib/perl5/5.005
> /usr/local/lib/site_perl/i386-linux /usr/local/lib/site_perl
> /usr/lib/perl5 .).
> BEGIN failed--compilation aborted.
Makes perfect sense.
> Let me say also that for now, I've worked around the problem by:
>
> echo "" > debian/config # The file that has the 'use ConfModule'
> # sorry, I guess I didn't mention that.
You could also try to replace "use Debconf::Client::ConfModule" by
"use Debian::Debconf::Client::ConfModule". But since this thing was
obviously never tested with such old a debconf version, there may be
other catches as well.
> It's icky, I know, but I've tested it out and it works. I just miss
> out on some of the configuration stuff at install time. I'd really
> like to know how to do this right, though.
Well, the "right" way is probably to just upgrade debconf (with the
mass of perl upgrade it generates). All others naturally include some
hacking.
BTW, if you feel like it, you may report a bug on postfix. It should
depend on a newer debconf. Just mentioning "debconf" in its
dependencies means that it works with all versions, which is obviously
not the case.
--
Robbe
signature.ng
Description: PGP signature
