rawhide glibc problems?

[Joshua Legbandt]

Since I upgraded my glibc to the latest rawhide rpms (glibc-2.3.2-71),
I've been having problems with yum, up2date and the rhn-applet.

yum returns the following when run:
Traceback (most recent call last):
  File "/usr/bin/yum", line 22, in ?
    import yummain
  File "yummain.py", line 21, in ?
  File "clientStuff.py", line 18, in ?
ImportError: /usr/lib/librt.so.1: symbol __librt_disable_asynccancel,
version GLIBC_PRIVATE not defined in file libc.so.6 with link time
reference

both up2date and the rhn-applet core.

I'd file a bugzilla report, but I am unclear as how to file it since
there is no entry for rawhide versions other than 1.0. How should these
be filed?

-Josh

--
Joshua Legbandt

[seth vidal]

On Sat, 2003-08-23 at 01:55, Joshua Legbandt wrote:
> Since I upgraded my glibc to the latest rawhide rpms (glibc-2.3.2-71),
> I've been having problems with yum, up2date and the rhn-applet.
>
> yum returns the following when run:
> Traceback (most recent call last):
>   File "/usr/bin/yum", line 22, in ?
>     import yummain
>   File "yummain.py", line 21, in ?
>   File "clientStuff.py", line 18, in ?
> ImportError: /usr/lib/librt.so.1: symbol __librt_disable_asynccancel,
> version GLIBC_PRIVATE not defined in file libc.so.6 with link time
> reference
>
> both up2date and the rhn-applet core.
>
> I'd file a bugzilla report, but I am unclear as how to file it since
> there is no entry for rawhide versions other than 1.0. How should these
> be filed?

I'd say file it under rawhide 1.0 (rawhide is always 1.0) and the python
component.

-sv

[Joshua Legbandt]

On Fri, 2003-08-22 at 23:35, seth vidal wrote:
> On Sat, 2003-08-23 at 01:55, Joshua Legbandt wrote:
> > Since I upgraded my glibc to the latest rawhide rpms (glibc-2.3.2-71),
> > I've been having problems with yum, up2date and the rhn-applet.
> >
> > yum returns the following when run:
> > Traceback (most recent call last):
> >   File "/usr/bin/yum", line 22, in ?
> >     import yummain
> >   File "yummain.py", line 21, in ?
> >   File "clientStuff.py", line 18, in ?
> > ImportError: /usr/lib/librt.so.1: symbol __librt_disable_asynccancel,
> > version GLIBC_PRIVATE not defined in file libc.so.6 with link time
> > reference
> >
> > both up2date and the rhn-applet core.
> >
> > I'd file a bugzilla report, but I am unclear as how to file it since
> > there is no entry for rawhide versions other than 1.0. How should these
> > be filed?
>
> I'd say file it under rawhide 1.0 (rawhide is always 1.0) and the python
> component.
>
> -sv

actually, I think I'm gonna file it under the glibc component. I was
digging around bugzilla and discovered bug 90755 for glibc breaking
java, which reminded my of the LD_ASSUME_KERNEL setting. After doing the
following:
% unset LANG
% export LD_ASSUME_KERNEL=2.2.5

I was able to run yum, up2date and the rhn-applet...

Thanks for the input!

-josh

[M A Young]

On Fri, 22 Aug 2003, Joshua Legbandt wrote:
> Since I upgraded my glibc to the latest rawhide rpms (glibc-2.3.2-71),
> I've been having problems with yum, up2date and the rhn-applet.
>
> yum returns the following when run:
> Traceback (most recent call last):
>   File "/usr/bin/yum", line 22, in ?
>     import yummain
>   File "yummain.py", line 21, in ?
>   File "clientStuff.py", line 18, in ?
> ImportError: /usr/lib/librt.so.1: symbol __librt_disable_asynccancel,
> version GLIBC_PRIVATE not defined in file libc.so.6 with link time
> reference
>
> both up2date and the rhn-applet core.

Try installing glibc-devel. I saw somewhere, probably in bugzilla, which
suggested that they put a library file in the wrong package.

Michael Young

[M A Young]

On Sat, 23 Aug 2003, M A Young wrote:
> On Fri, 22 Aug 2003, Joshua Legbandt wrote:
> > Since I upgraded my glibc to the latest rawhide rpms (glibc-2.3.2-71),
> > I've been having problems with yum, up2date and the rhn-applet.
> >
> > yum returns the following when run:
> > Traceback (most recent call last):
> >   File "/usr/bin/yum", line 22, in ?
> >     import yummain
> >   File "yummain.py", line 21, in ?
> >   File "clientStuff.py", line 18, in ?
> > ImportError: /usr/lib/librt.so.1: symbol __librt_disable_asynccancel,
> > version GLIBC_PRIVATE not defined in file libc.so.6 with link time
> > reference
> >
> > both up2date and the rhn-applet core.
>
> Try installing glibc-devel. I saw somewhere, probably in bugzilla, which
> suggested that they put a library file in the wrong package.

Actually ignore this, I hadn't read the bugs
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=102853
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=102879
carefully enough - a link was introduced in glibc-devel that messes up the
library search order and it ends up trying to mix tls and non-tls
libraries.

Michael Young

[Joshua Legbandt]

On Sat, 2003-08-23 at 09:22, M A Young wrote:
> On Sat, 23 Aug 2003, M A Young wrote:
> > On Fri, 22 Aug 2003, Joshua Legbandt wrote:
> > > Since I upgraded my glibc to the latest rawhide rpms (glibc-2.3.2-71),
> > > I've been having problems with yum, up2date and the rhn-applet.
> > >
> > > yum returns the following when run:
> > > Traceback (most recent call last):
> > >   File "/usr/bin/yum", line 22, in ?
> > >     import yummain
> > >   File "yummain.py", line 21, in ?
> > >   File "clientStuff.py", line 18, in ?
> > > ImportError: /usr/lib/librt.so.1: symbol __librt_disable_asynccancel,
> > > version GLIBC_PRIVATE not defined in file libc.so.6 with link time
> > > reference
> > >
> > > both up2date and the rhn-applet core.
> >
> > Try installing glibc-devel. I saw somewhere, probably in bugzilla, which
> > suggested that they put a library file in the wrong package.
>
> Actually ignore this, I hadn't read the bugs
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=102853
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=102879
> carefully enough - a link was introduced in glibc-devel that messes up the
> library search order and it ends up trying to mix tls and non-tls
> libraries.
>
> Michael Young

I think it is fixed, after I was able to run yum again, I did another
update and everything works now...

Thanks for the help!
-josh