On Fri, Dec 10, 2010 at 08:18:33AM +1000, Russell Dickenson <[email protected]> wrote: > I'm hoping you're still awake. Last night, when I was already very > tired, I decided to try the systemd repo. Now my installation of > 'current' won't boot.
Ugh, didn't we way it will kill your mother and eat your cat? The recommended way to test it is to install current on a separate partition (or in a virtual machine) and play with it there. Or at least make a backup before you break your system. > In reading the pacman-g2 man page I believe I can use the "--root" > parameter, also the parameter which allows me to use an alternate > database to correct this problem. I want to reinstall some 'current' > packages from a 1.3 'stable' installation, so I can't simply reinstall > 'stable' packages. For the list of packages, I'm guessing I need to > reinstall all those in the systemd repo. Of course I won't actually > uninstall the systemd packages themselves, so symlinks etc that they > created will remain in the file system. Check /var/log/pacman-g2.log, you'll see there what packages where removed, upgraded and installed. Given that you use current, the best is to boot a netinstall cd, mount your partition on tty2, then run pacman -S <pkg> -r /mnt/target for each package which was removed or upgraded. Also run pacman -R for the installed packages. This may work if the install cd is for 1.4pre1 or 1.4pre2 where the install cd has pacman configured for current, so pacman -S will install packages from the current repo. And don't install anything from stable, that will just make things harder. (IIRC you have some custom kernel, you can ignore that here since systemd repo did not touch your kernel.) > Does this sound like it might work? It may. Of course it's totally unsupported. :)
pgptyfcstGqfv.pgp
Description: PGP signature
_______________________________________________ Frugalware-devel mailing list [email protected] http://frugalware.org/mailman/listinfo/frugalware-devel
