public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] PANIC !!!!
Date: Sat, 22 Oct 2005 02:21:28 +0200	[thread overview]
Message-ID: <200510220221.28470.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <4359836D.5010609@asmallpond.org>

On Saturday 22 October 2005 02:10, Richard Fish wrote:
> Hemmann, Volker Armin wrote:
> >On Friday 21 October 2005 22:13, Jeff Smelser wrote:
> >>On Friday 21 October 2005 02:24 pm, Hemmann, Volker Armin wrote:
> >>>what do you mean 'crashed'?
> >>>
> >>>does revdep-rebuilt still works?
> >>>
> >>>but at least now you know why you should not use --deep.
> >>
> >>Why not? I use it here and I never get crashes.. One doesnt mean the
> >> other.
> >
> >because some apps (like, for example xine) doesn't like it, when some of
> > their dependencies get upgraded with a --deep world (like ffmpeg or
> > transcode), while themselves are not recombiled.
> >
> >xine will not crash - but some video-filters will be gone.
> >
> >It is just not wise:
> >App X linked against library L.
> >Now you do an --update --deep world.
> >lib L gets a new version L.1.1.
> >But X does not recompiled, and funny things can happen now.
>
> revdep-rebuild

which a) does not catch all the cases
and b) would not be needed at all, if you don't do '--deep' updates.
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-10-22  0:38 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-21 19:11 [gentoo-user] PANIC !!!! Allan Spagnol Comar
2005-10-21 19:24 ` Hemmann, Volker Armin
2005-10-21 20:13   ` Jeff Smelser
2005-10-21 20:30     ` Allan Spagnol Comar
2005-10-21 21:32       ` Jeff Smelser
2005-10-21 22:03       ` Dmitry S. Makovey
2005-10-22  1:35       ` Michael Crute
2005-10-21 22:45     ` Hemmann, Volker Armin
2005-10-22  0:10       ` Richard Fish
2005-10-22  0:21         ` Hemmann, Volker Armin [this message]
2005-10-22  1:20           ` Jeff Smelser
2005-10-22  1:37             ` Michael Crute
2005-10-22  3:05             ` Hemmann, Volker Armin
2005-10-22 10:40       ` Patrick Börjesson
2005-10-22 11:30         ` brullo nulla
2005-10-22  0:37   ` Rafael Fernández López
2005-10-22  3:12     ` Hemmann, Volker Armin
2005-10-22 12:26       ` Eddie Mihalow Jr
2005-10-22 13:50         ` Hemmann, Volker Armin
2005-10-22 14:17           ` Holly Bostick
2005-10-22 16:01             ` Allan Spagnol Comar
2005-10-22 16:37               ` Rumen Yotov
2005-10-27 14:44           ` Tamas Sarga
2005-10-21 19:27 ` Peter Gordon
2005-10-21 19:44   ` Allan Spagnol Comar
2005-10-21 19:47     ` Allan Spagnol Comar
2005-10-21 19:48       ` Allan Spagnol Comar
2005-10-22 12:35         ` Matan Peled
2005-10-21 19:27 ` Michael Crute
2005-10-21 19:30 ` Daniel da Veiga
2005-10-21 19:35 ` Roy Wright
2005-10-21 19:51   ` Allan Spagnol Comar
2005-10-21 20:09     ` Allan Spagnol Comar
2005-10-21 20:05   ` Dave Nebinger
2005-10-21 20:13     ` Allan Spagnol Comar
  -- strict thread matches above, loose matches on Subject: below --
2005-10-22 20:31 Keats
2005-10-22 20:47 ` Petteri Räty

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=200510220221.28470.volker.armin.hemmann@tu-clausthal.de \
    --to=volker.armin.hemmann@tu-clausthal.de \
    --cc=gentoo-user@lists.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