Hi!
After last syncing 'emerge -pvDuN world' ends with messages
shown below. How to resolve this conflict *safely*? I don't
want to experiment with fs-related packages :-)
Andrew
=
[ebuild N] sys-libs/e2fsprogs-libs-1.41.0 USE="nls" 476 kB
[ebuild U ] sys-fs/e
Am Sonntag, 17. August 2008 09:52:57 schrieb Andrew Gaydenko:
> After last syncing 'emerge -pvDuN world' ends with messages
> shown below. How to resolve this conflict *safely*? I don't
> want to experiment with fs-related packages :-)
What worked fine for me:
emerge --unmerge sys-libs/ss sys-lib
=== On Sunday 17 August 2008, Heiko Wundram wrote: ===
> Am Sonntag, 17. August 2008 09:52:57 schrieb Andrew Gaydenko:
> > After last syncing 'emerge -pvDuN world' ends with messages
> > shown below. How to resolve this conflict *safely*? I don't
> > want to experiment with fs-related packa
Am Sonntag, 17. August 2008 10:08:46 schrieb Andrew Gaydenko:
> === On Sunday 17 August 2008, Heiko Wundram wrote: ===
>
> > Am Sonntag, 17. August 2008 09:52:57 schrieb Andrew Gaydenko:
> > > After last syncing 'emerge -pvDuN world' ends with messages
> > > shown below. How to resolve this
Heiko Wundram <[EMAIL PROTECTED]> writes:
> What worked fine for me:
>
> emerge --unmerge sys-libs/ss sys-libs/com_err sys-fs/e2fsprogs
> emerge --oneshot -v sys-fs/e2fsprogs
Be *very* careful about doing that. wget (amongst other packages) uses
libcom_err, so you will not be able to fetch any pa
=== On Sunday 17 August 2008, Heiko Wundram wrote: ===
...
> > Why 'oneshot' option is used?
>
> So that you don't record sys-fs/e2fsprogs in the world set.
>
> It's pulled in as a dependency from the system set anyway (that's why
> the --unmerge will tell you that you're unmerging a system
=== On Sunday 17 August 2008, Graham Murray wrote: ===
> Heiko Wundram <[EMAIL PROTECTED]> writes:
> > What worked fine for me:
> >
> > emerge --unmerge sys-libs/ss sys-libs/com_err sys-fs/e2fsprogs
> > emerge --oneshot -v sys-fs/e2fsprogs
>
> Be *very* careful about doing that. wget (among
Am Sonntag, 17. August 2008 10:40:38 schrieb Graham Murray:
> Heiko Wundram <[EMAIL PROTECTED]> writes:
> > What worked fine for me:
> >
> > emerge --unmerge sys-libs/ss sys-libs/com_err sys-fs/e2fsprogs
> > emerge --oneshot -v sys-fs/e2fsprogs
>
> Be *very* careful about doing that. wget (amongst
Heiko Wundram <[EMAIL PROTECTED]> writes:
> I cannot reproduce this here:
>
> [EMAIL PROTECTED] ~ % ldd /usr/bin/wget
> linux-gate.so.1 => (0xb8088000)
> libssl.so.0.9.8 => /usr/lib/libssl.so.0.9.8 (0xb8025000)
> libcrypto.so.0.9.8 => /usr/lib/libcrypto.so.0.9.8 (0xb7ee600
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Andrew Gaydenko wrote:
> Hi!
>
> After last syncing 'emerge -pvDuN world' ends with messages
> shown below. How to resolve this conflict *safely*? I don't
> want to experiment with fs-related packages :-)
>
>
> Andrew
>
>
On Sun, 2008-08-17 at 08:07 -0400, Chris Walters wrote:
> The best way to resolve this, I've found is to put the following into
> your
> /etc/portage/package.mask file.
>
> =sys-libs/e2fsprogs-libs-1.41.0
> =sys-fs/e2fsprogs-1.41.0
>
> I masked them because some things depend on com_err, and that
11 matches
Mail list logo