On 09/25/2013 03:24 PM, gottl...@nyu.edu wrote:
> I want to downgrade systemd from 207-r2 to 204 (highest stable).
>
> I currently have virtual/udev-206-r2 installed, which prevents
> systemd-204.
>
> OK. So I need to downgrade virtual/udev to 200.
>
> I thought
> emerge -1 =virtual/udev-200 =sys-apps/systemd-204
> would do it. But this failed (see below) and suggested masking
> might help.
>
> So I added package.mask/systemd, which contains
> >=virtual/udev-201
> >=sys-apps/systemd-205
> and then issued the same emerge as above.
> But this also failed (see below).
> What incantation do I need?
>
> thanks,
> allan
> [blocks B ] sys-apps/systemd ("sys-apps/systemd" is blocking
> sys-fs/udev-207)
> [blocks B ] sys-fs/udev ("sys-fs/udev" is blocking
> sys-apps/systemd-207-r2, sys-apps/systemd-204)
These conflicts are often so confusing that I emerge -C both of the
blocking packages and then re-run the emerge that I really want.
In your particular case, if you actually remove both of those packages
your machine will not be bootable until you successfully emerge the
older versions (obviously) so I strongly recommend using quickpkg to
save both packages before removing them.
Then, if the worst happens and you can't install the older versions
you can re-install the saved binary packages with emerge -K.
Another officially unapproved workaround I use when really frustrated
is to bypass "emerge" completely and do this instead:
#ebuild /usr/portage/sys-apps/systemd/systemd-204.ebuild merge
Sometimes it works :)
