Mailinglist Archive: opensuse-factory (626 mails)

["Rajko M." <rmatov101@xxxxxxxxxxx>]

On Saturday 08 March 2008 10:55:35 am reinhard schwab wrote:
> Rajko M. schrieb:
> > On Saturday 08 March 2008 08:04:12 am reinhard schwab wrote:
> > > Marcus Meissner schrieb:
> > > > On Sat, Mar 08, 2008 at 02:18:47PM +0100, reinhard schwab wrote:
> > > > > is it possible that i update glibc on opensuse 10.2 to the glibc
> > > > > factory packages?
> > > >
> > > > It should work, but just might break your system.
> > > >
> > > > Why do you want that
> > >
> > > just for trying out some of the packages in factory.
> > > yast wants to install glibc if i try an update to some of the factory
> > > packages.
> > >
> > > what can be broken and (how) can i prevent a break?
> >
> > So far I know everything is compiled against glibc, including kernel.
> >
> > Replacing glibc with newer is like changing building base with a
> > different one. It is small chance that building will fit 100% to the new
> > base and that will cause some parts of it to break.
> >
> > What can you do to prevent?
> > Not much. You can make backup so if something breaks it will not sink
> > your data and settings too.
> >
> > You best bet to try out packages from Factory is installation in virtual
> > machine or separate installation of Factory.
>
> but if it claims to be ABI compatible with previous versions, nothing
> should break?
> i have searched the libc mailing list archives for any release notes in
> regard to glibc 2.7 release,
> but not found.
> i have only found one message in regard to 2.6.1 release.
> http://sources.redhat.com/ml/libc-announce/2007/msg00001.html
>
> BINARY COMPATIBILITY NOTE:
> The version 2.6 release had a bug in the `malloc_set_state'
> function that broke ABI compatibility with previous versions.
> For any program using this function, a binary built against
> version 2.5 or earlier would be broken when running with a
> version 2.6 shared library.  This may have been worked around
> by recompiling against the version 2.6 library, however this
> created a binary depending on the binary-incompatible bug.
> System distributions using version 2.6 fixed this problem in
> their released shared libraries, so most users will not have
> been affected by version 2.6's misbehavior.  This bug is now
> fixed in version 2.6.1, so that a 2.6.1 shared library is
> compatible with old binaries built with version 2.5 or earlier.
> However, this means that any binaries rebuilt against an
> unmodified 2.6 shared library had this 2.6 bug built in and are
> thus incompatible with a 2.6.1 shared library.
>
>
> an update from 2.5 to 2.6.1 should be possible without breaking the system?
>
> regards
> reinhard

Current factory has glibc-2.7. 
The 2.6.1 was in openSUSE 10.3 and possibly right after the release of 10.3 in 
Factory. I haven't looked in glibc package as I really don't know much about, 
but if I would be in your position, I would use virtual machine (VirtualBox 
is really simple), or create small partition for Alpha 2 installation and 
test newer applications there. Though, you know your hardware.

One thing that you should consider, 2 openSUSE developers told you that it can 
turn bad. While I just guess, they for sure know why. 

-- 
Regards, Rajko.
See http://en.opensuse.org/Portal
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx