| 1 |
On Tuesday 08 December 2009 14:08:47 Dale wrote: |
| 2 |
> >> I have the same problem, but the "emerge -av1 util-linux" has blocking |
| 3 |
> >> issues with sys-fs/e2fsprogs. Whenever I remove sys-fs stuff I usually |
| 4 |
> >> regret it. |
| 5 |
> >> |
| 6 |
> > |
| 7 |
> > You must remove the e2fsprogs* packages, emerge util-linux and re-emerge |
| 8 |
> > e2fsprogs* |
| 9 |
> > |
| 10 |
> > This is safe as long as you don't log out, reboot, kill bash or do other |
| 11 |
> > weird and wonderful things that require a working e2fsprogs. |
| 12 |
> > |
| 13 |
> > Think of it this way: |
| 14 |
> > |
| 15 |
> > delete your kernel image in /boot, do all kinds of stuff and put back a |
| 16 |
> > different kernel image named the same as the original. Nothing will go |
| 17 |
> > wrong unless you reboot|restart. Same with e2fprogs. |
| 18 |
> > |
| 19 |
> |
| 20 |
> Is this the one where you need to fetch the files first, then un-emerge |
| 21 |
> and emerge? I recall one being that way but not sure if it is this one. |
| 22 |
|
| 23 |
No, that was a while ago. This is simply a conflict involving e2fsprogs-libs |
| 24 |
|
| 25 |
Doesn't remove wget |
| 26 |
|
| 27 |
-- |
| 28 |
alan dot mckinnon at gmail dot com |
Archives