Henning Glawe wrote:
you are right... sorry for the sloppy research :S... think it must have been
the perl-base-perl-modules version mismatch. I'll try to reproduce this
immediately.
Yes, I think this is the issue.
I wrote an ugly script to reproduce from a almost pristine etch chroot[1]
On Wed, Aug 13, 2008 at 09:12:03PM +0300, Niko Tyni wrote:
BTW, I think there must be something wrong with your description:
/usr/bin/perl is in perl-base, and it certainly should find the modules
in perl-base itself...
ok, did the update starting from my system-backup; error-messages in the
Hi,
On Sat, Aug 16, 2008 at 02:16:58PM +0200, Henning Glawe wrote:
On Wed, Aug 13, 2008 at 09:12:03PM +0300, Niko Tyni wrote:
BTW, I think there must be something wrong with your description:
/usr/bin/perl is in perl-base, and it certainly should find the modules
in perl-base itself...
Henning Glawe wrote:
i worked around this by installing perl-base from lenny using dpkg.
which also failed due to the dependency loop between perl and perl-base.
dpkg --configure perl perl-base perl-modules
then put the perl back to a usable state (as dependency loops are fine, as
long as dpkg
Moin,
seems like in the dist-upgrade from etch to lenny is one very annoying (and
old, AFAIR I hit it already in woody-sarge and sarge-etch) problem: perl is
in an unusable state during the upgrade and causes maintainer scripts to
fail.
I was following way:
- update from etch and etch-security
-
On Wed, Aug 13, 2008 at 03:40:15PM +0200, Henning Glawe wrote:
seems like in the dist-upgrade from etch to lenny is one very annoying (and
old, AFAIR I hit it already in woody-sarge and sarge-etch) problem: perl is
in an unusable state during the upgrade and causes maintainer scripts to
fail.
6 matches
Mail list logo
