From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id ED8BD1381F3 for ; Sun, 6 Oct 2013 22:02:19 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3E5E6E0BA1; Sun, 6 Oct 2013 22:02:14 +0000 (UTC) Received: from cc-smtpout1.netcologne.de (cc-smtpout1.netcologne.de [89.1.8.211]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C5388E0B98 for ; Sun, 6 Oct 2013 22:02:12 +0000 (UTC) Received: from cc-smtpin2.netcologne.de (cc-smtpin2.netcologne.de [89.1.8.202]) by cc-smtpout1.netcologne.de (Postfix) with ESMTP id 05C9112046 for ; Mon, 7 Oct 2013 00:02:05 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by cc-smtpin2.netcologne.de (Postfix) with ESMTP id DD8CF11DFE for ; Mon, 7 Oct 2013 00:02:04 +0200 (CEST) Received: from [95.223.236.112] (helo=cc-smtpin2.netcologne.de) by localhost with ESMTP (eXpurgate 4.0.0) (envelope-from ) id 5251dddc-053f-7f0000012729-7f0000018a09-1 for ; Mon, 07 Oct 2013 00:02:04 +0200 Received: from weird.wonkology.org (ip-95-223-236-112.unitymediagroup.de [95.223.236.112]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by cc-smtpin2.netcologne.de (Postfix) with ESMTPSA for ; Mon, 7 Oct 2013 00:02:01 +0200 (CEST) Date: Mon, 7 Oct 2013 00:01:33 +0200 From: Alex Schuster To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Multiple package instances within a single package slot Message-ID: <20131007000133.34560e0a@weird.wonkology.org> In-Reply-To: <1381054199.5030.0@numa-i.igpm.rwth-aachen.de> References: <524E9D8B.4020301@wonkology.org> <524EABD5.4070200@fastmail.co.uk> <20131004174052.72b19be1@weird.wonkology.org> <524F1958.3030303@gmail.com> <20131005175952.0a4a3fd7@weird.wonkology.org> <20131005190218.3a3db9af@digimed.co.uk> <20131005203036.2e883e8a@weird.wonkology.org> <1381054199.5030.0@numa-i.igpm.rwth-aachen.de> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.20; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 4ac882ac-a433-40db-8694-0464d11c84f1 X-Archives-Hash: abe2cbbe9104c8ef115c13d890c58134 Helmut Jarausch writes: > You are not alone, Alex, please see > > https://bugs.gentoo.org/show_bug.cgi?id=486438 Thanks! Alan McKinnon writes: > On 05/10/2013 20:30, Alex Schuster wrote: > > Neil Bothwick writes: > >>> And whatever package I try to update, emerge wants to remerge > >>> libreoffice. Happens with all the packages I tried, which are > >>> adobe-flash, python, zsh, xterm. > >> > >> If portage believes LO needs to be rebuilt, it will try to do so > >> whichever packages you are emerging, just let it happen. > > > > I already did that, twice, when updating portage and chromium. emerge > > still wants to remerge libreoffice whenever I upgrade a package. > > > >> With a suitable > >> --jobs setting, portage will emerge all the other packages before LO > >> is done. > > > > No, at least with portage, the installation happened after > > libreoffice was installed. > > > > weird ~ # emerge -1uaj portage > > > > These are the packages that would be merged, in order: > > > > Calculating dependencies... done! > > [ebuild r U ] app-office/libreoffice-4.1.2.2-r1 [4.1.2.2] > > [ebuild U ] sys-apps/portage-2.2.7 [2.2.0_alpha188] > > [...] > >>>> Emerging (1 of 2) app-office/libreoffice-4.1.2.2-r1 > >>>> Emerging (2 of 2) sys-apps/portage-2.2.7 > >>>> Installing (1 of 2) app-office/libreoffice-4.1.2.2-r1 > >>>> Installing (2 of 2) sys-apps/portage-2.2.7 > >>>> Jobs: 2 of 2 complete Load avg: 3.06, 2.76, 2.63 > Now that you have upgraded portage, does this behaviour (always wanting > to rebuild LO) still happen? Yes. As I wrote, I upgraded portage (and LO), then claws (excluding LO this time), then chromium (along with LO). No more packages yet, but every upgrade would remerge LO. Downgrading to portage 2.2.6 does not help. Neil Bothwick writes: > On Sat, 5 Oct 2013 20:30:36 +0200, Alex Schuster wrote: > > > > If portage believes LO needs to be rebuilt, it will try to do so > > > whichever packages you are emerging, just let it happen. > > > > I already did that, twice, when updating portage and chromium. emerge > > still wants to remerge libreoffice whenever I upgrade a package. > > As a workround, you could remove LO from your world file, do your > updates but don't depclean, then put it back with > > emerge -n libreoffice > > It may be quicker than trying to track down the cause. I don't worry about this. I will add --exclude app-office/libreoffice to EMERGE_DEFAULTS_OPTS, and wait for the bug to be fixed by someone. Alex