Public SourceMage Discussion List

[Adam Clark <adamsgl AT dhbit.ca>]

Julian,

You are absolutely correct that a fresh install from any of the beta ISOs
(from the 1001 test ISO onward) won't have any problems with casting
glibc... at least, until the next glibc version upgrade.

The problem comes from *all* current systems that still haven't updated to
glibc 2.3.1.  Every single cast of glibc to try and get a system updated is
failing.  That's where the problem is.  In all honesty (and please don't
take this as attacking words, because they aren't), nobody gives a damn
where the problem lies, whether it's between linker versions, sorcery code,
whatever.  All anybody is going to know that if they cast glibc on a remote
system and it's the cast that attempts to move from 2.2.5 to 2.3.1, they
will break that system, and if they're not around to catch it, could wind up
severely farking their system.

The reason this is a problem is because there has always been some 'magic'
going on with the glibc casts, even during version upgrades (perhaps never
such incompatible version upgrades) where it just *worked*.  The version
upgrade happened seamlessly, the cast didn't puke on itself, and nobody
wound up with a borked system (okay, in reality that might be a little fairy
taleish).

Now, upgrades are barfing.  I've still got two systems left to go on the
glibc upgrade, and I don't want to do them until the spell upgrades
properly.  Whether this means that sorcery needs fixing, or the spell needs
tweaking, I really don't care.  I just hope *somebody* will take hold of the
reins and get the process fixed.

All that said, please let us know if there's an impossibility somewhere.  It
appears your stance on it is "The spell is fine", when to the rest of all of
us, it appears that it most certainly isn't.



On Tue, 19 Nov 2002 11:13:59 +0100
julian AT openit.de (Julian v. Bock) wrote:

> Hi
> 
> >>>>> "ES" == Eric Schabell <eschabell AT sourcemage.org> writes:
> 
> ES> Have faith, someone out there will fix it soon????? I can't see
> ES> going 1.0 like this....
> 
> Well, I do. All build problems come from either the 2.2.5 -> 2.3.1
> update, or resulting broken glibc installations. I told often enough
> that the probs resulted from the interaction between incompatible
> dynamic linkers and some sorcery code (which is otherwise ok).
> 
> I installed a box from the beta1 iso some time ago and the glibc
> build worked fine without interaction. So where is the 1.0 problem?
> 
> The glibc spell is *not* *broken*, so *all* I can do is to help people
> fixing their installations.
> 
> Julian
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss


-- 
Adam Clark, Chat Section Maintainer, ISO Forger
Grimoire Gurus Cardholding Member
a.k.a. Kinetix on #sourcemage, #grimoire-gurus
http://grimoire-gurus.org

Attachment: pgpWnoBdRDBep.pgp
Description: PGP signature