Re: dist-upgrade problem (was Re: /etc/modutils/0keep: line 9: keep: command not found)
On Sun, Jan 20, 2008 at 11:20:03 -0800, tom arnall wrote:
> i attempted the distr-upgrade and after i rebooted did:
>
> kloro@debian:~$ uname -r
> 2.6.16.4
I think you should follow the Sarge->Etch upgrade notes, adapting them
to your somewhat different situation. There are a couple of issues to be
aware of, and even though most of them might not apply to you, it is
better to know about all of them. (However, also see my remarks below.)
> so i did the distr-upgrade again. following is the session output. '31 not
> fully installed or removed.' is where it gets interesting:
>
> kloro@debian:~$ sudo apt-get dist-upgrade
> Reading package lists... Done
> Building dependency tree... Done
> Calculating upgrade... Done
> The following packages have been kept back:
> gdk-imlib1 gnome-cups-manager gnome-system-monitor
> 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
> 31 not fully installed or removed.
> Need to get 0B/118kB of archives.
> After unpacking 0B of additional disk space will be used.
> Do you want to continue [Y/n]?
> Reading package fields... Done
> Reading package status... Done
> Retrieving bug reports... Done
> Parsing Found/Fixed information... Done
> (Reading database ... 203060 files and directories currently installed.)
> Preparing to replace linux-wlan-ng 0.2.5+dfsg+prism2dl-1etch1
> (using .../linux-wlan-ng_0.2.5+dfsg+prism2dl-1etch1_i386.deb) ...
> Unpacking replacement linux-wlan-ng ...
> /etc/modutils/0keep: line 9: keep: command not found
> Error while executing /etc/modutils/0keep, aborting
> Note: If /etc/modutils/0keep should not be an executable script, please ensure
> it does not have execute permission
> dpkg: warning - old post-removal script returned error exit status 1
> dpkg - trying script from the new package instead ...
[...]
> E: Sub-process /usr/bin/dpkg returned an error code (1)
You have to change the permissions of /etc/modutils/0keep; it is not
supposed to be executable. AFAICT, the "keep" in line 9 is meant as a
directive for modutils, not as a command in a shell script. (There is a
"keep" executable, which is part of the KDE auto-backup package with the
same name, but this has nothing to do with modutils.) Your package
manager will be more or less blocked until this issue is fixed.
Taking a look at the bigger picture, you have to realize that your
earlier sweeping change of permissions will probably cause many more
such small (or not so small) breakages in unexpected places. If this
machine is your "playground" to experiment and learn about Debian then
this might not be such a bad thing, although I would bet that there are
better ways to learn than to start from an ill-defined configuration.
On the other hand, if you want to get any serious work done with this
computer anytime soon then you might want to consider putting an Etch
installer CD into its drive and let the installer do its work (after
backing up your important personal files, of course).
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
Reply to: