On 28/06/2010 14:58, maximilian attems wrote: > On Mon, Jun 28, 2010 at 02:59:28PM +0200, Yves-Alexis Perez wrote: >> On 28/06/2010 14:25, maximilian attems wrote: >>> Preparing to replace evolution 2.22.3.1-1 (using >>> .../evolution_2.30.1.2-3_amd64.deb) ... >>> Evolution is still running, aborting... >>> dpkg: error processing >>> /var/cache/apt/archives/evolution_2.30.1.2-3_amd64.deb (--unpack): >>> subprocess new pre-installation script returned error exit status 1 >>> >> Could you explain how you did the upgrade? Especially, did you see the >> debconf note about stopping all evolution processes? > > the current upgrade from lenny to squeeze is quite borked due to > a) apt-get wanting to nuke all xorg > b) udev beeing again a pain in the arse. > > so I don't remember when aboves happened in the myriad of > dpkg --configure -a > apt-get -f install > aptitude --full-upgrade > > but i didn't get a debconf note, no. > hmm checking the root mail account, I see lots of mails telling me to: > evolution --force-shutdown > why can't that be done by hand,
As said on irc, we can't kill an user process, that'd definitely be a bad behavior. note that evolution was not actively > used on that workstation. It came with gnome. Maybe, but there's no way we can know, and running the above command would have solved this. > > debconf was set to Noninteractive and critical priority. > Well, I'm not sure there's a nice solution to this. We can't upgrade if evolution is running, and we can't kill it unconditionally. Cheers, -- Yves-Alexis -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
