From: Aron Griffis <agriffis@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] glibc ebuilds
Date: Mon Nov 12 21:01:01 2001 [thread overview]
Message-ID: <20011112220036.B27543@yde.flatmonk.org> (raw)
In-Reply-To: <1005575857.25833.2.camel@silica>
Tod M. Neidt wrote: [Mon Nov 12 2001, 09:37:36AM EST]
> I recently, updated several gnome-apps to the current versions (I'm
> composing this in evo 0.99, thanks hallski!). While updating, I ran
> into a couple situations where I hosed my gnome-session out from under
> myself. Normally, you can safely emerge a gnome-app while running a
> gnome-session. However, if the app emerge triggers an update of one of
> the underlying libs through a dependency you will promptly shoot
> yourself in the foot. This happened to me when imlib and gdk-pixbuf
> were updated while emerging the new evolution and gnumeric. It would be
> nice if *critical* gnome-libs ebuilds would check to make sure you are
> not running a gnome-session before merging, and ask you to drop down
> into console mode to do the merge.
Normally it should not be a problem to install a new version of
a library even when programs are currently loaded that are using the
older version. The problem here is actually that Portage is overwriting
the library without unlinking it first. Since the library is mmap'd, it
results in offsets being all wrong, so the application (gnome-session in
this case) segfaults.
Aron
prev parent reply other threads:[~2001-11-13 4:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-03 18:25 [gentoo-dev] glibc ebuilds Collins Richey
2001-11-03 19:42 ` Tod M. Neidt
2001-11-03 21:33 ` Martin Schlemmer
2001-11-04 9:45 ` Tod M. Neidt
2001-11-04 10:31 ` Tod M. Neidt
2001-11-04 12:51 ` Collins Richey
2001-11-11 9:46 ` Karl Trygve Kalleberg
2001-11-12 8:36 ` Tod M. Neidt
2001-11-12 21:01 ` Aron Griffis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011112220036.B27543@yde.flatmonk.org \
--to=agriffis@gentoo.org \
--cc=gentoo-dev@cvs.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox