| 1 |
On Donnerstag 06 November 2008, Dirk Heinrichs wrote: |
| 2 |
> Am Donnerstag 06 November 2008 08:21:26 schrieb ext KH: |
| 3 |
> > Well that's the point. You want to get rid of them. So you are unmerging |
| 4 |
> > them. The moment something fails after unmerging and before emerging the |
| 5 |
> > new packages, you will be very happy to have your old packages. You just |
| 6 |
> > put them pack in place and you have a running system again. It's a |
| 7 |
> > seatbelt. |
| 8 |
> |
| 9 |
> That's why |
| 10 |
> |
| 11 |
> 1) I use paludis, no seatbelts required. One can safely de-install com_err |
| 12 |
> and ss _after_ upgrading e2fsprogs and e2fsprogs-libs. |
| 13 |
> |
| 14 |
> 2) I outlined to first emerge -f e2fsprogs e2fsprogs. It's known that wget |
| 15 |
> will fail after unmerging com_err, so the new packages need to be fetched |
| 16 |
> first. That's all. No need to make the thing more complicated than it is. |
| 17 |
|
| 18 |
and both have nothing to do with the fact, that it is wise to have a backup of |
| 19 |
essintial files in case something goes horribly wrong. |
| 20 |
|
| 21 |
oh, and latest portage can 'break' blocks too.... |
Archives