Re: [gentoo-user] Multiple package instances within a single package slot

[Alex Schuster <wonko@wonkology.org>]

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