Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 7831] Sorcery only protects /lib/ld.so.1 in excluded

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT bugs.sourcemage.org
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 7831] Sorcery only protects /lib/ld.so.1 in excluded
  • Date: Thu, 16 Dec 2004 22:35:54 -0800 (PST)

http://bugs.sourcemage.org/show_bug.cgi?id=7831





------- Additional Comments From acedit AT armory.com 2004-12-16 22:35 -------
You're right protecting it would also leave the stale version around...I still
think that the process used for installing/upgrading glibc should be revisted
and fully understood before we try and act on it.

Im wary of putting patches over patches over patches on a process we dont
fully
understand yet though. I havent seen anyone actually come up with a clear
understanding of how we upgrade glibc, why (exactly) our system has failed to
update it so badly, and a guarentee that we wont have problems in the future.

Sorry to be a stiff on this one but before I go and say we'll never track this
file, why dont we solve the glibc issue once and for all (in as simple a way
as
possible), document it, then implement. If this already happened please point
me to the docs...

I believe at least part of the problem is sorcery backing up libraries,
perhaps
it does this incorrectly for glibc or something else. Theres some weird magic
with glibc in prepare_install... I'd rather tame this giant rather than
sedate it :)

--
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.




Archive powered by MHonArc 2.6.24.

Top of Page