woody-to-sarge test upgrade
Hello Debian developers,
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.
The following packages will be REMOVED:
apache apache-common autoconf autoconf2.13 automake console-tools-libs
debhelper defoma devscripts dpkg-cross dpkg-dev eperl ferm gs gs-common
gsfonts kernel-package latex2html libdigest-md5-perl libfltk1-dev libgd-dev
libhtml-clean-perl libimage-size-perl libmailtools-perl libnet-perl
libterm-readkey-perl libtimedate-perl lists-archives mailtools mhonarc
mnogosearch-local patchutils perl perl-modules slice spamassassin tetex-bin
tetex-extra weblint wml xbase-clients xlibmesa-dev xlibs-dev
The following NEW packages will be installed:
apache2-utils aptitude coreutils cpp-3.3 dash debconf-i18n dselect e2fslibs
emacs20 emacsen-common g++-3.3 gcc-3.3 gcc-3.3-base gcc-3.4-base initscripts
libacl1 libapr0 libattr1 libblkid1 libcomerr2 libconsole libdb1-compat
libdb4.1 libdb4.2 libdb4.3 libdns16 libgcrypt11 libgd1-noxpm libgd2-noxpm
libgdbm3 libgnutls11 libgpg-error0 libidn11 libisc7 liblocale-gettext-perl
liblzo1 libmagic1 libmysqlclient12 libncursesw5 libnetpbm10 libnewt0.51
libopencdk8 libpaper-utils libpaper1 libparted1.6-12 libpcap0.7 libperl5.8
libpng10-0 libpng10-dev libpng12-0 libsasl2 libsigc++-1.2-5c102 libss2
libssl0.9.7 libstdc++5 libstdc++5-3.3-dev libstdc++6 libt1-5 libtasn1-2
libtext-charwidth-perl libtext-iconv-perl libtext-wrapi18n-perl libtidy0
libtiff4 libuuid1 libwww0 libxv1 linux-kernel-headers mingw32-binutils
mnogosearch-mysql mysql-common pm-dev python2.3 render-dev slang1a-utf8
spamc sysv-rc tcl8.4 ucf vim-common x-dev xlibmesa-dri xlibmesa-gl
xlibmesa-glu
...
Removing gs ...
Removing gs-common ...
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
Before I do more testing, I would like to make sure I know the proper
procedure:
1) What is the recommend way to perform such upgrade ?
2) How can I produce useful problem report ?
Fixing such problems is usually just a matter of using apt-get install
manually, but preventing them to happen in the first place would be
nice.
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
Reply to: