From: Philip Webb <purslow@ca.inter.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Q on portage's rational to re-emerge packages
Date: Fri, 27 Sep 2013 07:18:08 -0400 [thread overview]
Message-ID: <20130927111808.GA875@ca.inter.net> (raw)
In-Reply-To: <20130927104321.GC3105@TranscendTheRubicon.fritz.box>
130927 Hinnerk van Bruinehsen wrote:
> you are encountering a relatively new feature of portage
> that is supposed to make revdep-rebuild & emerge @preserve-rebuild obsolete.
> The logic is, that if you update a package, other packages
> depending on this package will automatically rebuild to prevent breakage.
> It seems that in your case portage "thinks" that one of that packages
> depends on zsh-completion and pulls that in for rebuild,
> which in turn, most likely via setuptools or PyQt4,
> pulls libreoffice to rebuild.
I have found sometimes that Portage wants to remerge LO or similar,
but in fact the existing installed version continues to work regardless.
Try remerging the other pkgs first & see if LO still functions as usual ;
only if it doesn't do you need to remerge it.
HTH
--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatchassdotutorontodotca
next prev parent reply other threads:[~2013-09-27 11:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 8:24 [gentoo-user] Q on portage's rational to re-emerge packages Helmut Jarausch
2013-09-27 9:09 ` Alan McKinnon
2013-09-27 9:28 ` Helmut Jarausch
2013-09-27 10:43 ` Hinnerk van Bruinehsen
2013-09-27 11:18 ` Philip Webb [this message]
2013-09-27 11:53 ` Neil Bothwick
2013-09-27 22:22 ` Alan McKinnon
2013-10-08 13:13 ` Stefan G. Weichinger
2013-10-08 14:04 ` Khumba
2013-10-08 19:11 ` Stefan G. Weichinger
2013-09-27 10:38 ` [gentoo-user] " Markus Trippelsdorf
2013-09-27 15:22 ` Bruce Hill
2013-10-08 20:47 ` [gentoo-user] " Markos Chandras
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=20130927111808.GA875@ca.inter.net \
--to=purslow@ca.inter.net \
--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