reassign 516870 acpid 1.0.8-1
retitle 516870 powerbtn.sh moved during upgrade despite user changes
thanks
On Tue, 24 Feb 2009, Ivan Jager wrote:
> I'm not really sure what severity to tag this with, as it resulted in an
> accidental shutdown.
>
> Anyways, I recently did an aptitude upgrade on my laptop. Sometime later,
> I pressed the power button which I had configured to hibernate. Instead,
> it caused a shutdown. Not good. (And, no, I hadn't said it was ok to
> replace /etc/acpi/powerbtn.sh. I'm not sure where the upgrade was at
> that point, but it may have been in the middle of asking me whether it
> was ok to replace. After the reboot I see there is a powerbtn.sh.dpkg-dist
> and my original script at powerbtn.sh.dpkg-bak.
acpi-support doesn't touch that file. However acpid does. Sometimes in the
lenny developement cycle, the maintainer decided to drop it and
acpi-support-base was created in response to ensure the functionnality
would remain available.
The .dpkg-bak is there so that you can retrieve your changes and put them
in place in the new configuration file (of the new package). You are not
expected to put it back in place, it has been moved away for a reason.
However, given that the new script has a fallback into the old script, it
might be good for acpid to simply keep the file if it has changes and only
unregister the events but not remove the config file.
> I'm guessing this is a funny interaction with the way dpkg handles
> config file changes combined with the check in powerbtn-acpi-support.sh
> and the existence of a new powerbtn.sh. It seems like a way to fix this
> problem would be to put the contents of the new powerbtn.sh into the
> fallback portion of powerbtn-acpi-support.sh. (After all that's what it's
> there for, isn't it?)
There is no new powerbtn.sh. The .dpkg-dist is an old copy kept here
because you modified the file and answered "no" to the "use
maintainer-supplied file" of dpkg.
> I was kind of expecting to be able to get dpkg to finish upgrading/configuring
> packages but none of {apt-get install, aptitude dist-upgrade, or dpkg
> --configure --pending} did anything, so I just moved my old script back by
> hand. Now I'm even starting to wonder whether the shutdown actually
> happened *during* the upgrade, or whether the upgrade finished and
> just left me without a powerbtn.sh.
The intent of the prerm script of acpid is really to remove the file (or
move its content away if it has been modified by the user).
> This may very well just be a fluke, but it would be good to provent it
> from happening again when people upgrade from lenny to squeeze.
Well, it will if you try to put it back but not if you modify its
new replacement: powerbtn-acpi-support.sh.
Cheers,
--
Raphaël Hertzog
Le best-seller français mis à jour pour Debian Etch :
http://www.ouaza.com/livre/admin-debian/
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
