| 1 |
On 09/25/2013 03:24 PM, gottlieb@×××.edu wrote: |
| 2 |
> I want to downgrade systemd from 207-r2 to 204 (highest stable). |
| 3 |
> |
| 4 |
> I currently have virtual/udev-206-r2 installed, which prevents |
| 5 |
> systemd-204. |
| 6 |
> |
| 7 |
> OK. So I need to downgrade virtual/udev to 200. |
| 8 |
> |
| 9 |
> I thought |
| 10 |
> emerge -1 =virtual/udev-200 =sys-apps/systemd-204 |
| 11 |
> would do it. But this failed (see below) and suggested masking |
| 12 |
> might help. |
| 13 |
> |
| 14 |
> So I added package.mask/systemd, which contains |
| 15 |
> >=virtual/udev-201 |
| 16 |
> >=sys-apps/systemd-205 |
| 17 |
> and then issued the same emerge as above. |
| 18 |
> But this also failed (see below). |
| 19 |
> What incantation do I need? |
| 20 |
> |
| 21 |
> thanks, |
| 22 |
> allan |
| 23 |
|
| 24 |
> [blocks B ] sys-apps/systemd ("sys-apps/systemd" is blocking sys-fs/udev-207) |
| 25 |
> [blocks B ] sys-fs/udev ("sys-fs/udev" is blocking sys-apps/systemd-207-r2, sys-apps/systemd-204) |
| 26 |
|
| 27 |
These conflicts are often so confusing that I emerge -C both of the |
| 28 |
blocking packages and then re-run the emerge that I really want. |
| 29 |
|
| 30 |
In your particular case, if you actually remove both of those packages |
| 31 |
your machine will not be bootable until you successfully emerge the |
| 32 |
older versions (obviously) so I strongly recommend using quickpkg to |
| 33 |
save both packages before removing them. |
| 34 |
|
| 35 |
Then, if the worst happens and you can't install the older versions |
| 36 |
you can re-install the saved binary packages with emerge -K. |
| 37 |
|
| 38 |
Another officially unapproved workaround I use when really frustrated |
| 39 |
is to bypass "emerge" completely and do this instead: |
| 40 |
|
| 41 |
#ebuild /usr/portage/sys-apps/systemd/systemd-204.ebuild merge |
| 42 |
|
| 43 |
Sometimes it works :) |
Archives