| 1 |
======= On Sunday 17 August 2008, Heiko Wundram wrote: ======= |
| 2 |
> Am Sonntag, 17. August 2008 09:52:57 schrieb Andrew Gaydenko: |
| 3 |
> > After last syncing 'emerge -pvDuN world' ends with messages |
| 4 |
> > shown below. How to resolve this conflict *safely*? I don't |
| 5 |
> > want to experiment with fs-related packages :-) |
| 6 |
> |
| 7 |
> What worked fine for me: |
| 8 |
> |
| 9 |
> emerge --unmerge sys-libs/ss sys-libs/com_err sys-fs/e2fsprogs |
| 10 |
> emerge --oneshot -v sys-fs/e2fsprogs |
| 11 |
|
| 12 |
Heiko, |
| 13 |
|
| 14 |
Why 'oneshot' option is used? |
| 15 |
|
| 16 |
|
| 17 |
Andrew |
| 18 |
|
| 19 |
> |
| 20 |
> You might want to run a revdep-rebuild after emerging the new e2fsprogs, |
| 21 |
> although the only thing that happened with libraries AFAICT is that |
| 22 |
> sys-libs/ss and sys-libs/com_err now come combined in the |
| 23 |
> sys-libs/e2fsprogs-libs package without any versioning change, and so |
| 24 |
> revdep-rebuild should find nothing. |
| 25 |
> |
| 26 |
> HTH! |
| 27 |
> |
| 28 |
> --- Heiko. |
Archives