Re: Problem w/apt-get dist-upgrade
On 8 Oct 1999, David Coe wrote:
> "Stephen R. Gore" <[EMAIL PROTECTED]> writes:
>
> > I'm trying to upgrade a fresh slink base-install to potato. I've upgraded
> > apt (0.3.7slink0), edited sources.list, did apt-get update, and apt-get
> > dist-upgrade. (I've done all this from scratch 3 times - it's repeatable).
> >
> > I get the following error:
> >
> > E: Problem executing scripts DPkg::Pre-Invoke 'mount -o remount,rw /usr'
I tracked this down here to the fact that I had installed
/usr/doc/apt-get/examples/apt.conf with appropriate changes for my site,
but I missed this bit:
// Auto re-mounting of a readonly /usr
Pre-Invoke {"mount -o remount,rw /usr";};
Post-Invoke {"mount -o remount,ro /usr";};
HTH
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Lindsay Allen <[EMAIL PROTECTED]> Perth, Western Australia
voice +61 8 9316 248632.0125S 115.8445E Debian Linux
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: Problem w/apt-get dist-upgrade
"Stephen R. Gore" <[EMAIL PROTECTED]> writes: > I found the problem. I happened to log in as a normal user on another vt, > and had a stack of mail from cron complaining about /bin/sh not existing. > Created the symlink to /bin/bash, and everything worked fine. > > How did this happen? (CCing this to devel for input) Ahh, yes, sorry I forgot about that problem. That was a bug in one of the bash packages, it could remove your /bin/sh link. It's either been or being fixed; maybe someone closer to that problem will tell you more. Glad you found the solution. Isn't unstable fun?
Re: Problem w/apt-get dist-upgrade
"Stephen R. Gore" <[EMAIL PROTECTED]> writes: > I'm trying to upgrade a fresh slink base-install to potato. I've upgraded > apt (0.3.7slink0), edited sources.list, did apt-get update, and apt-get > dist-upgrade. (I've done all this from scratch 3 times - it's repeatable). > > I get the following error: > > E: Problem executing scripts DPkg::Pre-Invoke 'mount -o remount,rw /usr' Just a guess: you have your /usr partition mounted read-only, and for some reason Dpkg was unable to remount it read-write. Try remounting it yourself and ensure it's writable before running apt-get dist-upgrade, and see if it then works. And, regardless, file a bug report containing the details. > > Also, if I try dpkg --configure -a: > > Setting up bsdutils (2.9w-3.1) ... > dpkg (subprocess): unable to execute post-installation script: No such file > or directory Hmmm, that means there's no bsdutils.postinst in /var/log/dpkg/info, where dpkg should have unpacked it. Maybe fallout from the above error?
Re: Problem w/apt-get dist-upgrade
Stephen R. Gore wrote: > I get the following error: > > E: Problem executing scripts DPkg::Pre-Invoke 'mount -o remount,rw /usr' > > Also, if I try dpkg --configure -a: > > Setting up bsdutils (2.9w-3.1) ... > dpkg (subprocess): unable to execute post-installation script: No such file > or directory > ---end quoted text--- I found the problem. I happened to log in as a normal user on another vt, and had a stack of mail from cron complaining about /bin/sh not existing. Created the symlink to /bin/bash, and everything worked fine. How did this happen? (CCing this to devel for input) -- Regards, Steve Debian GNU/Linux Because software support is free, timely, useful, technically accurate, and friendly. Reboots are for kernel and hardware upgrades.
Problem w/apt-get dist-upgrade
I'm trying to upgrade a fresh slink base-install to potato. I've upgraded apt (0.3.7slink0), edited sources.list, did apt-get update, and apt-get dist-upgrade. (I've done all this from scratch 3 times - it's repeatable). I get the following error: E: Problem executing scripts DPkg::Pre-Invoke 'mount -o remount,rw /usr' Also, if I try dpkg --configure -a: Setting up bsdutils (2.9w-3.1) ... dpkg (subprocess): unable to execute post-installation script: No such file or directory Any clues on what's happening here? I've done this upgrade at least a dozen times, and I've never seen this... -- Regards, Steve Debian GNU/Linux Because software support is free, timely, useful, technically accurate, and friendly. Reboots are for kernel and hardware upgrades.
