another upgrade, another disaster

Przemek Klosowski przemek.klosowski at
Tue May 29 21:14:16 UTC 2012

On 05/29/2012 04:42 PM, Neal Becker wrote:
> Basically the same kind of failure as the last several times I did updates.
> This time f16->f17.  Used preupgrade.
> It seems to have all gone wrong when cpio failed, because a python package had
> been installed using pip into the (default) system dirs.  The conflict IIRC
> happens because pip installs a dir where cpio expects a file (or vice-versa).
> I've since learned to use pip install --user instead - but there was still a
> leftover package.
> I was happy (temporarily) to see that I could still reboot the machine.  Remove
> the offending package.
> Then IIRC I restarted the upgrade.  It seemed to complete OK.  I was pleased to
> see it appear to continue from where it left off.
> On reboot, I found a huge mess.  Duplicate packages (f16/f17) all over.
> So,
> 1) Could I have actually recovered from this mess without a complete re-install?

I have an open install bug where a package blocks the install:

(an install-time error trips the install script into going interactive 
and hanging on commandline input)

I managed to find and solve that by going to the shell console 
(Ctrl-Alt-F2) and killing the postinstallation script for that package. 
It affected that package, but allowed the whole thing to finish.

More information about the devel mailing list