Re: woody-to-sarge test upgrade
On Fri, Apr 29, 2005 at 07:48:00PM +0200, Bill Allombert wrote:
> I am performing semi-automatised woody-to-sarge upgrade of one
> server and I find the upgrade is more painful than what is necessary.
>
> apt-get dist-upgrade try to remove lots of the packages, and doing so
> trigger bugs.
> Can't locate File/Copy.pm in @INC (@INC contains: /usr/local/lib/perl/5.6.1 /usr/local/share/perl/5.6.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.6.1 /usr/share/perl/5.6.1 /usr/local/lib/site_perl .) at /usr/bin/defoma-app line 7.pty
> so not removed.
> Unregistering Postscript fonts...Can't locate File/Copy.pm in @INC (@INC contains: /usr/local/lib/perl/5.6.1 /usr/local/share/perl/5.6.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.6.1 /usr/share/perl/5.6.1 /usr/local/lib/site_perl .) at /usr/bin/defoma-font line 7.
> BEGIN failed--compilation aborted at /usr/bin/defoma-font line 7.
> dpkg: error processing gsfonts (--remove):
> subprocess post-removal script returned error exit status 2
> subprocess post-removal script returned error exit status 2
> dpkg: defoma: dependency problems, but removing anyway as you request:
> gs-common depends on defoma.
> gsfonts depends on defoma.
> Removing defoma ...
> dpkg - warning: while removing defoma, directory `/var/lib/defoma/scripts' not empty so not removed.
> Removing perl ...
> Errors were encountered while processing:
> gs-common
> gsfonts
sounds like you ran into perl-bug #279232
--
c u
henning
Reply to: