Your message dated Sun, 20 Apr 2008 20:55:16 +0300
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#146985: console-common: package installation fails
has caused the Debian Bug report #146985,
regarding console-common: package installation fails
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.)
--
146985: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=146985
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: console-common
Version: 0.7.14
see error message below
# dpkg -i console-common_0.7.14_all.deb
(Reading database ... 212034 files and directories currently installed.)
Preparing to replace console-common 0.7.12 (using
console-common_0.7.14_all.deb) ...
"Debconf::Client::ConfModule" is not exported by the
Debconf::Client::ConfModule module at /var/lib/dpkg/tmp.ci/config line 33
":all" is not exported by the Debconf::Client::ConfModule module at
/var/lib/dpkg/tmp.ci/config line 33
Can't continue after import errors at /var/lib/dpkg/tmp.ci/config line 33
BEGIN failed--compilation aborted at /var/lib/dpkg/tmp.ci/config line 33.
dpkg: error processing console-common_0.7.14_all.deb (--install):
subprocess pre-installation script returned error exit status 255
Errors were encountered while processing:
console-common_0.7.14_all.deb
***********************
-- System Information
Debian Release: 3.0
Kernel Version: Linux druid 2.4.18 #1 SMP Mon Apr 8 15:18:08 PDT 2002
i686
unknown
Versions of the packages console-common depends on:
ii debconf 1.0.32 Debian configuration management system
--- End Message ---
--- Begin Message ---
On Thu, May 16, 2002 at 12:58:39PM -0700, Herman wrote:
> On Thu, 16 May 2002, Martin Michlmayr wrote:
> > * Herman <[EMAIL PROTECTED]> [20020516 08:23]:
> > > "Debconf::Client::ConfModule" is not exported by the
> > > Debconf::Client::ConfModule module at ./test.pl line 5
> > I'm baffled. This should not happen (and doesn't happen on my
> > system). I'm reassiging this bug to debconf; perhaps its maintainer
> > has an idea what's going on. Or it might be a Perl problem.
>
> I was just able to solve the problem (which affected several other
> packages as well) based on that hint. There was an old Exporter.pm module
> file, which did not belong to any installed package, in the /usr/lib/perl5
> directory, which was being used because it comes earlier in the include
> path than /usr/share/perl/5.6.1/, where the proper version resides. I am
> not sure where that old version came from, but this may be considered a
> bug of the perl package, in the sense that it sometimes doesn't use the
> proper module files by default.
This is a commonly used feature, not a bug. Vendor modules in
/usr/lib/perl5 override core modules in /usr/share/perl/<version>
so that newer module versions can be included in Debian as separate
packages without having to update them in the perl package.
More information can be found in the Debian Perl policy at
http://www.debian.org/doc/packaging-manuals/perl-policy/
As the original problem was solved by removing the stray Exporter.pm,
I'm closing this. There's certainly no way to tell where the file came
from anymore.
Cheers,
--
Niko Tyni [EMAIL PROTECTED]
--- End Message ---
