[gentoo-user] e2fsprogs and blocking

[gentoo-user] e2fsprogs and blocking

[Andrew Gaydenko]

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/e2fsprogs-1.41.0 [1.40.11] USE="nls (-static%)" 4,161 kB
[blocks B     ] <sys-fs/e2fsprogs-1.41 (is blocking sys-libs/e2fsprogs-libs-1.41.0)
[blocks B     ] sys-libs/ss (is blocking sys-libs/e2fsprogs-libs-1.41.0)
[blocks B     ] sys-libs/com_err (is blocking sys-libs/e2fsprogs-libs-1.41.0)

Re: [gentoo-user] e2fsprogs and blocking

[Heiko Wundram]

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-libs/com_err sys-fs/e2fsprogs
emerge --oneshot -v sys-fs/e2fsprogs

You might want to run a revdep-rebuild after emerging the new e2fsprogs, 
although the only thing that happened with libraries AFAICT is that 
sys-libs/ss and sys-libs/com_err now come combined in the 
sys-libs/e2fsprogs-libs package without any versioning change, and so 
revdep-rebuild should find nothing.

HTH!

--- Heiko.

Re: [gentoo-user] e2fsprogs and blocking

[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 conflict *safely*? I don't
> > want to experiment with fs-related packages :-)
>
> What worked fine for me:
>
> emerge --unmerge sys-libs/ss sys-libs/com_err sys-fs/e2fsprogs
> emerge --oneshot -v sys-fs/e2fsprogs

Heiko,

Why 'oneshot' option is used?


Andrew

>
> You might want to run a revdep-rebuild after emerging the new e2fsprogs,
> although the only thing that happened with libraries AFAICT is that
> sys-libs/ss and sys-libs/com_err now come combined in the
> sys-libs/e2fsprogs-libs package without any versioning change, and so
> revdep-rebuild should find nothing.
>
> HTH!
>
> --- Heiko.

Re: [gentoo-user] e2fsprogs and blocking

[Heiko Wundram]

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 conflict *safely*? I don't
> > > want to experiment with fs-related packages :-)
> >
> > What worked fine for me:
> >
> > emerge --unmerge sys-libs/ss sys-libs/com_err sys-fs/e2fsprogs
> > emerge --oneshot -v sys-fs/e2fsprogs
>
> 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 package, and that 
you'll potentially break your system), and I personally don't like 
unnecessary packages cluttering up my world set, so I always use --oneshot in 
cases like this.

But, if you leave it out, it does no harm, either.

--- Heiko.

Re: [gentoo-user] e2fsprogs and blocking

[Andrew Gaydenko]

======= 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 package, and
> that you'll potentially break your system), and I personally don't like
> unnecessary packages cluttering up my world set, so I always use
> --oneshot in cases like this.
>
> But, if you leave it out, it does no harm, either.
>
> --- Heiko.

Done. Thanks!


Andrew

Re: [gentoo-user] e2fsprogs and blocking

[Graham Murray]

Heiko Wundram <heiko@xencon.net> 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 packages (including
e2fsprogs-lib) if you follow the above instructions.  See bug
https://bugs.gentoo.org/show_bug.cgi?id=234907 for details and for a
safer workaround. 

Re: [gentoo-user] e2fsprogs and blocking

[Andrew Gaydenko]

======= On Sunday 17 August 2008, Graham Murray wrote: =======
> Heiko Wundram <heiko@xencon.net> 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 packages (including
> e2fsprogs-lib) if you follow the above instructions.  See bug
> https://bugs.gentoo.org/show_bug.cgi?id=234907 for details and for a
> safer workaround.

I see, thanks. Fortunately I always fetch all needed packages *before* any 
updating/installing.


Andrew

Re: [gentoo-user] e2fsprogs and blocking

[Heiko Wundram]

Am Sonntag, 17. August 2008 10:40:38 schrieb Graham Murray:
> Heiko Wundram <heiko@xencon.net> 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 packages (including
> e2fsprogs-lib) if you follow the above instructions.  See bug
> https://bugs.gentoo.org/show_bug.cgi?id=234907 for details and for a
> safer workaround.

I cannot reproduce this here:

modelnine@phoenix ~ % 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 (0xb7ee6000)
        libdl.so.2 => /lib/libdl.so.2 (0xb7ee2000)
        librt.so.1 => /lib/librt.so.1 (0xb7ed9000)
        libc.so.6 => /lib/libc.so.6 (0xb7d99000)
        /lib/ld-linux.so.2 (0xb8089000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xb7d81000)
modelnine@phoenix ~ %

None of the specified libraries indirectly references libcom_err, either, and 
running wget with libcom_err temporarily not present also works, and I did 
not download the packages before using the commands I noted. Possibly, 
there's a difference between the x86 wget and the ~x86 wget (I run the 
latter).

--- Heiko.

Re: [gentoo-user] e2fsprogs and blocking

[Graham Murray]

Heiko Wundram <heiko@xencon.net> writes:

> I cannot reproduce this here:
>
> modelnine@phoenix ~ % 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 (0xb7ee6000)
>         libdl.so.2 => /lib/libdl.so.2 (0xb7ee2000)
>         librt.so.1 => /lib/librt.so.1 (0xb7ed9000)
>         libc.so.6 => /lib/libc.so.6 (0xb7d99000)
>         /lib/ld-linux.so.2 (0xb8089000)
>         libpthread.so.0 => /lib/libpthread.so.0 (0xb7d81000)
> modelnine@phoenix ~ %
>
> None of the specified libraries indirectly references libcom_err, either, and 
> running wget with libcom_err temporarily not present also works, and I did 
> not download the packages before using the commands I noted. Possibly, 
> there's a difference between the x86 wget and the ~x86 wget (I run the 
> latter).

The difference is the kerberos USE flag which is set in
/usr/portage/profiles/targets/desktop/make.defaults

Re: [gentoo-user] e2fsprogs and blocking

[Chris Walters]

-----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
> 
> =========================
> 
> [ebuild  N    ] sys-libs/e2fsprogs-libs-1.41.0  USE="nls" 476 kB
> [ebuild     U ] sys-fs/e2fsprogs-1.41.0 [1.40.11] USE="nls (-static%)" 4,161 kB
> [blocks B     ] <sys-fs/e2fsprogs-1.41 (is blocking sys-libs/e2fsprogs-libs-1.41.0)
> [blocks B     ] sys-libs/ss (is blocking sys-libs/e2fsprogs-libs-1.41.0)
> [blocks B     ] sys-libs/com_err (is blocking sys-libs/e2fsprogs-libs-1.41.0)

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 is part of
e2fsprogs-libs in the 1.41.0 version.  Until the upstreams of these packages
update their packages, you can't use the new version, unless you're willing to
unmerge all of the affected packages.

Regards,
Chris
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJIqBSGAAoJEIAhA8M9p9DAzpkP/jK/Fb8oOpHuT4lb2VNzOlEd
fy/vFlqdJ+uMvpD2YtQCrwkBbzIEnyq4oqlYjixH2DWkq/vqNYxwHZEvsXW6dYEo
QpODtz2wb5bsyn3Mld9Ucp7jpZNNuRdJP7/wCdeGqwJlzer35nfW/2uAeXW9yoo3
+i2A29EZ/dlYHaJLGsU9RRICgbbR/pGIknsqUei6Ev+AZdPdINppN3/jHS2cn8Bs
FWS5gFL5Z+tKIOLsh6EdH6eWieSYzeIv5uVNy4AB9xL7QQO8XKC6s8coiPFODxie
Vh+K+Q/vZKO0MSdtRlyfy307YOwix+FdYsrr7FamWkWnZ6AgJqmIOrRwyAFVStDN
FfR3CIqm69ZLOaPJ8zavqRh4t1hREMSbBKoWQWJtpPhFl7YDD/PLs0d3F5vZzBQ/
rqk+JMrjpf2JZdnaFs2ynUAmB70VRPzfuw0XNjPXTUyFfdE73WjUxY6H/12g/Azg
aQFmh7WADSqz6T8ICn53x6eyOtAReJ4MdTjiqy8eBcxpHy28DEK62jPqm1YzFclY
c93pibJUC0r6TA5yBF87xHZMaEOpgMcvsB2QNht6idhA8l9kdJk6yFbDkTIH7TLd
dyBLvMY6x0TStmB5AbcEJSzji1O0aZgjMVRpP6m11OliivcuHrbca4K9Bi4prahr
V5oOwQkINaw1RdDYI/eQ
=7xzi
-----END PGP SIGNATURE-----

Re: [gentoo-user] e2fsprogs and blocking

[Albert Hopkins]

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 is part
> of
> e2fsprogs-libs in the 1.41.0 version.  Until the upstreams of these
> packages
> update their packages, you can't use the new version, unless you're
> willing to
> unmerge all of the affected packages.

Which is what you should do, as has been mentioned previously in this
thread.