Upgrading Grml-Small0.4 HD install
Hi,
Ever since I did 'apt-get upgrade' in my Grml-Small v0.4 HD install, I can't use 'shutdown now' or 'reboot' properly any more. E.g., reboot will complain that '/etc/init.d/grml-reboot' not found.
I looked into the problem, learned that /etc/init.d/grml-reboot is from grml-etc, but I have grml-etc installed.
Finally I found that somehow the 'apt-get upgrade' installed the '/etc/init.d/grml-reboot' file as '/etc/init.d/grml-reboot.dpkg-new'.
I don't understand why apt-get/dpkg is doing this, ie, deliberately breaking my working system. I remember lots of packages have been updated, I don't know how many those .dpkg-new files are out there breaking my system. So,
- how to fix the problem? - how to prevent it from happening again?
thx a lot
* - Tong - mlist4suntong@yahoo.com [20070812 14:44]:
Ever since I did 'apt-get upgrade' in my Grml-Small v0.4 HD install, I can't use 'shutdown now' or 'reboot' properly any more. E.g., reboot will complain that '/etc/init.d/grml-reboot' not found.
I looked into the problem, learned that /etc/init.d/grml-reboot is from grml-etc, but I have grml-etc installed.
Finally I found that somehow the 'apt-get upgrade' installed the '/etc/init.d/grml-reboot' file as '/etc/init.d/grml-reboot.dpkg-new'.
I don't understand why apt-get/dpkg is doing this, ie, deliberately breaking my working system. I remember lots of packages have been updated, I don't know how many those .dpkg-new files are out there breaking my system. So,
- how to fix the problem?
mv /etc/init.d/grml-reboot.dpkg-new /etc/init.d/grml-reboot
- how to prevent it from happening again?
Make sure you check the files where you are asked questions like:
| What would you like to do about it ? Your options are: | Y or I : install the package maintainer’s version | N or O : keep your currently-installed version | D : show the differences between the versions | Z : start a new shell to examine the situation | The default action is to keep your current version.
So by default you won't accept the new file (unless you choose 'I') but instead use the old file and a .dpkg-new will be generated for further actions.
According to your specific problem: looks like something changed /etc/init.d/grml-reboot on your system (so the hashsum of the file stored in package management and the one of current /etc/init.d/grml-reboot don't match). Assuming that it wasn't you who changed the file on your own I'll check that out on my own so it won't happen with the next grml-small version.
regards, -mika-
Thanks for the reply mika,
On Sun, 12 Aug 2007 15:45:33 +0200, Michael Prokop wrote:
- how to prevent it from happening again?
Make sure you check the files where you are asked questions like:
| What would you like to do about it ? Your options are: | Y or I : install the package maintainer's version | N or O : keep your currently-installed version | D : show the differences between the versions | Z : start a new shell to examine the situation | The default action is to keep your current version.
So by default you won't accept the new file (unless you choose 'I') but instead use the old file and a .dpkg-new will be generated for further actions.
Strange, I thought I chose 'Y', ie, 'I'. What's even more strange is that, there is /etc/init.d/grml-reboot.dpkg-new file in my system but no /etc/init.d/grml-reboot. All the .dpkg-new files are like this. If I've chosen N or O, I'd have a /etc/init.d/grml-reboot left, correct?
According to your specific problem: looks like something changed /etc/init.d/grml-reboot on your system (so the hashsum of the file stored in package management and the one of current /etc/init.d/grml-reboot don't match). Assuming that it wasn't you who changed the file on your own I'll check that out on my own so it won't happen with the next grml-small version.
Oh, I thought that they were upgraded because they were out-dated. Thanks for the info, I'll look closely next time. FYI, this behavior is not grml-package specify, here is a list of all my .dpkg-new files:
/etc/X11/windowlab/windowlab.menurc.dpkg-new /etc/X11/xorg.conf.vmware.dpkg-new /etc/X11/xorg.conf.example.dpkg-new /etc/zsh/zshrc.original.dpkg-new /etc/zsh/zlogin.original.dpkg-new /etc/zsh/completion.d/_grml-x.dpkg-new /etc/zsh/zshenv.original.dpkg-new /etc/zsh/zlogout.original.dpkg-new /etc/zsh/zprofile.original.dpkg-new /etc/grml/language-functions.dpkg-new /etc/grml/modules.dpkg-new /etc/grml/autoconfig.functions.dpkg-new /etc/grml/autoconfig.small.dpkg-new /etc/grml/autoconfig.dpkg-new /etc/grml/partconf.dpkg-new /etc/skel/.w3m/config.dpkg-new /etc/skel/.centericq/external.dpkg-new /etc/skel/.asoundrc.example.dpkg-new /etc/skel/.a2ps/a2psrc.dpkg-new /etc/skel/.kshrc.dpkg-new [...rest ignored...]
* - Tong - mlist4suntong@yahoo.com [20070812 16:17]:
On Sun, 12 Aug 2007 15:45:33 +0200, Michael Prokop wrote:
So by default you won't accept the new file (unless you choose 'I') but instead use the old file and a .dpkg-new will be generated for further actions.
Strange, I thought I chose 'Y', ie, 'I'. What's even more strange is that, there is /etc/init.d/grml-reboot.dpkg-new file in my system but no /etc/init.d/grml-reboot. All the .dpkg-new files are like this. If I've chosen N or O, I'd have a /etc/init.d/grml-reboot left, correct?
Yes. no files should be lost.
That's very strange, I'll try to reproduce that on my own.
According to your specific problem: looks like something changed /etc/init.d/grml-reboot on your system (so the hashsum of the file stored in package management and the one of current /etc/init.d/grml-reboot don't match). Assuming that it wasn't you who changed the file on your own I'll check that out on my own so it won't happen with the next grml-small version.
Oh, I thought that they were upgraded because they were out-dated. Thanks for the info, I'll look closely next time. FYI, this behavior is not grml-package specify, here is a list of all my .dpkg-new files:
/etc/X11/windowlab/windowlab.menurc.dpkg-new /etc/X11/xorg.conf.vmware.dpkg-new /etc/X11/xorg.conf.example.dpkg-new /etc/zsh/zshrc.original.dpkg-new /etc/zsh/zlogin.original.dpkg-new /etc/zsh/completion.d/_grml-x.dpkg-new /etc/zsh/zshenv.original.dpkg-new /etc/zsh/zlogout.original.dpkg-new /etc/zsh/zprofile.original.dpkg-new /etc/grml/language-functions.dpkg-new /etc/grml/modules.dpkg-new /etc/grml/autoconfig.functions.dpkg-new /etc/grml/autoconfig.small.dpkg-new /etc/grml/autoconfig.dpkg-new /etc/grml/partconf.dpkg-new /etc/skel/.w3m/config.dpkg-new /etc/skel/.centericq/external.dpkg-new /etc/skel/.asoundrc.example.dpkg-new /etc/skel/.a2ps/a2psrc.dpkg-new /etc/skel/.kshrc.dpkg-new [...rest ignored...]
That's grml specific at least as far as that all those files are shipped by grml packages. :)
Don't care too much about it (unless you experience problems of course ;-)). The 'config file handling via dpkg-divert' isn't really supported in Debian - though I'm wondering what's happening on your system here. Getting some .original.dpkg-new and .dpkg-old files in /etc is "normal", but above is something I never experienced so far. Again, I'll try reproduce it with grml-small 0.4.
regards, -mika-
participants (2)
-
- Tong - -
Michael Prokop