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

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

[Valmor de Almeida]

Hello,

I would appreciate help with this multiple-packages-in-a-single slot
problem. In the past I have unistalled packages and reinstalled on a
case-by-case basis and dealt with the fall out manually. I wonder
whether there is a more efficient way of doing it.

Thanks,

--
Valmor


-> USE="libkms cups apng minizip hwdb" emerge -vp --newuse --tree
--update --deep system

[snip]

[blocks B      ]  <sys-apps/sysvinit-2.88-r4
("<sys-apps/sysvinit-2.88-r4" is blocking sys-apps/util-linux-2.22.2)
[blocks B      ] <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking
sys-fs/udev-init-scripts-23)
[blocks B      ] <sys-fs/lvm2-2.02.97-r1 ("<sys-fs/lvm2-2.02.97-r1" is
blocking sys-fs/udev-197-r8)

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

x11-base/xorg-server:0

  (x11-base/xorg-server-1.12.4::gentoo, installed) pulled in by
    <x11-base/xorg-server-1.12.99[-minimal] required by
(x11-drivers/xf86-video-virtualbox-4.1.22::gentoo, installed)
    (and 1 more with the same problem)

  (x11-base/xorg-server-1.13.1::gentoo, ebuild scheduled for merge) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

virtual/udev:0

  (virtual/udev-171::gentoo, installed) pulled in by
    <virtual/udev-196 required by (sys-fs/lvm2-2.02.88::gentoo, installed)

  (virtual/udev-197-r1::gentoo, ebuild scheduled for merge) pulled in by
    >=virtual/udev-197-r1 required by (sys-fs/udev-197-r8::gentoo,
ebuild scheduled for merge)
    =virtual/udev-197-r1 required by
(sys-apps/util-linux-2.22.2::gentoo, ebuild scheduled for merge)
    (and 11 more with the same problems)

sys-fs/udev:0

  (sys-fs/udev-171-r9::gentoo, installed) pulled in by
    ~sys-fs/udev-171[gudev?,hwdb?,introspection?,keymap?,selinux?]
required by (virtual/udev-171::gentoo, installed)

  (sys-fs/udev-197-r8::gentoo, ebuild scheduled for merge) pulled in by
    >=sys-fs/udev-197-r8[gudev?,hwdb?,introspection?,keymap?,kmod?,selinux?,static-libs?]
required by (virtual/udev-197-r1::gentoo, ebuild scheduled for merge)

x11-drivers/xf86-video-virtualbox:0

  (x11-drivers/xf86-video-virtualbox-4.1.24::gentoo, ebuild scheduled
for merge) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (x11-drivers/xf86-video-virtualbox-4.1.22::gentoo, installed) pulled in by
    ~x11-drivers/xf86-video-virtualbox-4.1.22 required by
(app-emulation/virtualbox-guest-additions-4.1.22::gentoo, installed)

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

[Matt Joyce]

[-- Attachment #1: Type: text/plain, Size: 3550 bytes --]

On 05/03/13 23:21, Valmor de Almeida wrote:
> Hello,
>
> I would appreciate help with this multiple-packages-in-a-single slot
> problem. In the past I have unistalled packages and reinstalled on a
> case-by-case basis and dealt with the fall out manually. I wonder
> whether there is a more efficient way of doing it.
>
> Thanks,
>
> --
> Valmor
>
>
> -> USE="libkms cups apng minizip hwdb" emerge -vp --newuse --tree
> --update --deep system
>
> [snip]
>
> [blocks B      ]  <sys-apps/sysvinit-2.88-r4
> ("<sys-apps/sysvinit-2.88-r4" is blocking sys-apps/util-linux-2.22.2)
> [blocks B      ] <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking
> sys-fs/udev-init-scripts-23)
> [blocks B      ] <sys-fs/lvm2-2.02.97-r1 ("<sys-fs/lvm2-2.02.97-r1" is
> blocking sys-fs/udev-197-r8)
>
> !!! Multiple package instances within a single package slot have been pulled
> !!! into the dependency graph, resulting in a slot conflict:
>
> x11-base/xorg-server:0
>
>   (x11-base/xorg-server-1.12.4::gentoo, installed) pulled in by
>     <x11-base/xorg-server-1.12.99[-minimal] required by
> (x11-drivers/xf86-video-virtualbox-4.1.22::gentoo, installed)
>     (and 1 more with the same problem)
>
>   (x11-base/xorg-server-1.13.1::gentoo, ebuild scheduled for merge) pulled in by
>     (no parents that aren't satisfied by other packages in this slot)
>
> virtual/udev:0
>
>   (virtual/udev-171::gentoo, installed) pulled in by
>     <virtual/udev-196 required by (sys-fs/lvm2-2.02.88::gentoo, installed)
>
>   (virtual/udev-197-r1::gentoo, ebuild scheduled for merge) pulled in by
>     >=virtual/udev-197-r1 required by (sys-fs/udev-197-r8::gentoo,
> ebuild scheduled for merge)
>     =virtual/udev-197-r1 required by
> (sys-apps/util-linux-2.22.2::gentoo, ebuild scheduled for merge)
>     (and 11 more with the same problems)
>
> sys-fs/udev:0
>
>   (sys-fs/udev-171-r9::gentoo, installed) pulled in by
>     ~sys-fs/udev-171[gudev?,hwdb?,introspection?,keymap?,selinux?]
> required by (virtual/udev-171::gentoo, installed)
>
>   (sys-fs/udev-197-r8::gentoo, ebuild scheduled for merge) pulled in by
>     >=sys-fs/udev-197-r8[gudev?,hwdb?,introspection?,keymap?,kmod?,selinux?,static-libs?]
> required by (virtual/udev-197-r1::gentoo, ebuild scheduled for merge)
>
> x11-drivers/xf86-video-virtualbox:0
>
>   (x11-drivers/xf86-video-virtualbox-4.1.24::gentoo, ebuild scheduled
> for merge) pulled in by
>     (no parents that aren't satisfied by other packages in this slot)
>
>   (x11-drivers/xf86-video-virtualbox-4.1.22::gentoo, installed) pulled in by
>     ~x11-drivers/xf86-video-virtualbox-4.1.22 required by
> (app-emulation/virtualbox-guest-additions-4.1.22::gentoo, installed)
>
I'm fairly new to Gentoo so might not be the best to help here but from
my experience when two versions of one package are involved and it says
no parents arn't satisfied by others on several occasions specifying
that package explicitly on the command line has worked for me, I suspect
it might work in the other case here also as it's a virtual package
having an issue.  It seems to get more fun when two "real" packages
decide they want different and mutually incompatible versions of a
package then sometimes masking a specified version temporarily seems to
work for some I had one recently that simply didn't want to resolve
until I decided enough was enough and opted not to bother with the one
package triggering a dependency that it liked and half the rest of the
system didn't.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 295 bytes --]

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

[Walter Dnes]

On Tue, Mar 05, 2013 at 06:21:12PM -0500, Valmor de Almeida wrote
> Hello,
> 
> I would appreciate help with this multiple-packages-in-a-single slot
> problem. In the past I have unistalled packages and reinstalled on a
> case-by-case basis and dealt with the fall out manually. I wonder
> whether there is a more efficient way of doing it.

  I had a similar problem during a recent installation when I converted
from udev to eudev.  "emerge --update --newuse --deep world" spewed out
those error messages.  However, "emerge world" (no options) ran OK.
Then I was able to unmerge udev and emerge eudev, the command...
"emerge --update --newuse --deep world" ran OK after that.  Reminds me
of the joke about insanity... doing the same thing and expecting a
different result.  In this case, I assume that "emerge world" resolved
some issues, and got the system back into a sane state.

  To repeat...
Step 1) "emerge world"
Step 2) "emerge --update --newuse --deep world"

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

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

[Alan McKinnon]

On 06/03/2013 01:21, Valmor de Almeida wrote:
> Hello,
> 
> I would appreciate help with this multiple-packages-in-a-single slot
> problem. In the past I have unistalled packages and reinstalled on a
> case-by-case basis and dealt with the fall out manually. I wonder
> whether there is a more efficient way of doing it.
> 
> Thanks,
> 
> --
> Valmor
> 
> 
> -> USE="libkms cups apng minizip hwdb" emerge -vp --newuse --tree
> --update --deep system

                  ^^^^^^

Don't do that, rather run it on world; or you could do "emerge -pv
@system" Modern portage versions deal with these blockers automatically,
but they need the whole dependency graph to do it. There's no much point
in trying to deal with system and world independently anyway, system
isn't something magical, it's nothing more than a minimum collection of
packages that Gentoo can still run on, a mere list.

-ND to rebuild system doesn't get you anything extra and usually wants
to evaluate half of world as well (usually due to USE=X)

You update system if you want to guarantee yourself a consistent
toolchain after a gcc or glibc update, or just prior to emerge -e world



> 
> [snip]
> 
> [blocks B      ]  <sys-apps/sysvinit-2.88-r4
> ("<sys-apps/sysvinit-2.88-r4" is blocking sys-apps/util-linux-2.22.2)
> [blocks B      ] <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking
> sys-fs/udev-init-scripts-23)
> [blocks B      ] <sys-fs/lvm2-2.02.97-r1 ("<sys-fs/lvm2-2.02.97-r1" is
> blocking sys-fs/udev-197-r8)
> 
> !!! Multiple package instances within a single package slot have been pulled
> !!! into the dependency graph, resulting in a slot conflict:
> 
> x11-base/xorg-server:0
> 
>   (x11-base/xorg-server-1.12.4::gentoo, installed) pulled in by
>     <x11-base/xorg-server-1.12.99[-minimal] required by
> (x11-drivers/xf86-video-virtualbox-4.1.22::gentoo, installed)
>     (and 1 more with the same problem)
> 
>   (x11-base/xorg-server-1.13.1::gentoo, ebuild scheduled for merge) pulled in by
>     (no parents that aren't satisfied by other packages in this slot)
> 
> virtual/udev:0
> 
>   (virtual/udev-171::gentoo, installed) pulled in by
>     <virtual/udev-196 required by (sys-fs/lvm2-2.02.88::gentoo, installed)
> 
>   (virtual/udev-197-r1::gentoo, ebuild scheduled for merge) pulled in by
>     >=virtual/udev-197-r1 required by (sys-fs/udev-197-r8::gentoo,
> ebuild scheduled for merge)
>     =virtual/udev-197-r1 required by
> (sys-apps/util-linux-2.22.2::gentoo, ebuild scheduled for merge)
>     (and 11 more with the same problems)
> 
> sys-fs/udev:0
> 
>   (sys-fs/udev-171-r9::gentoo, installed) pulled in by
>     ~sys-fs/udev-171[gudev?,hwdb?,introspection?,keymap?,selinux?]
> required by (virtual/udev-171::gentoo, installed)
> 
>   (sys-fs/udev-197-r8::gentoo, ebuild scheduled for merge) pulled in by
>     >=sys-fs/udev-197-r8[gudev?,hwdb?,introspection?,keymap?,kmod?,selinux?,static-libs?]
> required by (virtual/udev-197-r1::gentoo, ebuild scheduled for merge)
> 
> x11-drivers/xf86-video-virtualbox:0
> 
>   (x11-drivers/xf86-video-virtualbox-4.1.24::gentoo, ebuild scheduled
> for merge) pulled in by
>     (no parents that aren't satisfied by other packages in this slot)
> 
>   (x11-drivers/xf86-video-virtualbox-4.1.22::gentoo, installed) pulled in by
>     ~x11-drivers/xf86-video-virtualbox-4.1.22 required by
> (app-emulation/virtualbox-guest-additions-4.1.22::gentoo, installed)
> 


-- 
Alan McKinnon
alan.mckinnon@gmail.com

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

[Valmor de Almeida]

On Wed, Mar 6, 2013 at 1:39 AM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On 06/03/2013 01:21, Valmor de Almeida wrote:
>> Hello,
>>
>> I would appreciate help with this multiple-packages-in-a-single slot
>> problem. In the past I have unistalled packages and reinstalled on a
>> case-by-case basis and dealt with the fall out manually. I wonder
>> whether there is a more efficient way of doing it.
>>
>> Thanks,
>>
>> --
>> Valmor
>>
>>
>> -> USE="libkms cups apng minizip hwdb" emerge -vp --newuse --tree
>> --update --deep system
>
>                   ^^^^^^
>
> Don't do that, rather run it on world; or you could do "emerge -pv
> @system" Modern portage versions deal with these blockers automatically,
> but they need the whole dependency graph to do it. There's no much point
> in trying to deal with system and world independently anyway, system
> isn't something magical, it's nothing more than a minimum collection of
> packages that Gentoo can still run on, a mere list.

Thanks for the info. Did it on world and got

-------------------------
-> USE="pulseaudio sqlite libkms cups apng minizip hwdb" emerge -vp
--newuse --tree --update --deep world

These are the packages that would be merged, in reverse order:

[snip]

[blocks B      ]  <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking
sys-fs/udev-init-scripts-23)
[blocks B      ]  <sys-apps/sysvinit-2.88-r4
("<sys-apps/sysvinit-2.88-r4" is blocking sys-apps/util-linux-2.22.2)

Total: 126 packages (91 upgrades, 12 new, 6 in new slots, 17
reinstalls, 1 uninstall), Size of downloads: 989,597 kB
Conflict: 7 blocks
------------------------

I have udev-171 at the moment and I have read and followed the
instructions in the eselect news for the udev upgrade. I would
appreciate any pointers on how to deal with this particular blocking.

Thanks,

--
Valmor

>
> -ND to rebuild system doesn't get you anything extra and usually wants
> to evaluate half of world as well (usually due to USE=X)
>
> You update system if you want to guarantee yourself a consistent
> toolchain after a gcc or glibc update, or just prior to emerge -e world
>
>
>
>>
>> [snip]
>>
>> [blocks B      ]  <sys-apps/sysvinit-2.88-r4
>> ("<sys-apps/sysvinit-2.88-r4" is blocking sys-apps/util-linux-2.22.2)
>> [blocks B      ] <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking
>> sys-fs/udev-init-scripts-23)
>> [blocks B      ] <sys-fs/lvm2-2.02.97-r1 ("<sys-fs/lvm2-2.02.97-r1" is
>> blocking sys-fs/udev-197-r8)
>>
>> !!! Multiple package instances within a single package slot have been pulled
>> !!! into the dependency graph, resulting in a slot conflict:
>>
>> x11-base/xorg-server:0
>>
>>   (x11-base/xorg-server-1.12.4::gentoo, installed) pulled in by
>>     <x11-base/xorg-server-1.12.99[-minimal] required by
>> (x11-drivers/xf86-video-virtualbox-4.1.22::gentoo, installed)
>>     (and 1 more with the same problem)
>>
>>   (x11-base/xorg-server-1.13.1::gentoo, ebuild scheduled for merge) pulled in by
>>     (no parents that aren't satisfied by other packages in this slot)
>>
>> virtual/udev:0
>>
>>   (virtual/udev-171::gentoo, installed) pulled in by
>>     <virtual/udev-196 required by (sys-fs/lvm2-2.02.88::gentoo, installed)
>>
>>   (virtual/udev-197-r1::gentoo, ebuild scheduled for merge) pulled in by
>>     >=virtual/udev-197-r1 required by (sys-fs/udev-197-r8::gentoo,
>> ebuild scheduled for merge)
>>     =virtual/udev-197-r1 required by
>> (sys-apps/util-linux-2.22.2::gentoo, ebuild scheduled for merge)
>>     (and 11 more with the same problems)
>>
>> sys-fs/udev:0
>>
>>   (sys-fs/udev-171-r9::gentoo, installed) pulled in by
>>     ~sys-fs/udev-171[gudev?,hwdb?,introspection?,keymap?,selinux?]
>> required by (virtual/udev-171::gentoo, installed)
>>
>>   (sys-fs/udev-197-r8::gentoo, ebuild scheduled for merge) pulled in by
>>     >=sys-fs/udev-197-r8[gudev?,hwdb?,introspection?,keymap?,kmod?,selinux?,static-libs?]
>> required by (virtual/udev-197-r1::gentoo, ebuild scheduled for merge)
>>
>> x11-drivers/xf86-video-virtualbox:0
>>
>>   (x11-drivers/xf86-video-virtualbox-4.1.24::gentoo, ebuild scheduled
>> for merge) pulled in by
>>     (no parents that aren't satisfied by other packages in this slot)
>>
>>   (x11-drivers/xf86-video-virtualbox-4.1.22::gentoo, installed) pulled in by
>>     ~x11-drivers/xf86-video-virtualbox-4.1.22 required by
>> (app-emulation/virtualbox-guest-additions-4.1.22::gentoo, installed)
>>
>
>
> --
> Alan McKinnon
> alan.mckinnon@gmail.com
>
>

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

[Alan McKinnon]

On 06/03/2013 22:25, Valmor de Almeida wrote:
> On Wed, Mar 6, 2013 at 1:39 AM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
>> On 06/03/2013 01:21, Valmor de Almeida wrote:
>>> Hello,
>>>
>>> I would appreciate help with this multiple-packages-in-a-single slot
>>> problem. In the past I have unistalled packages and reinstalled on a
>>> case-by-case basis and dealt with the fall out manually. I wonder
>>> whether there is a more efficient way of doing it.
>>>
>>> Thanks,
>>>
>>> --
>>> Valmor
>>>
>>>
>>> -> USE="libkms cups apng minizip hwdb" emerge -vp --newuse --tree
>>> --update --deep system
>>
>>                   ^^^^^^
>>
>> Don't do that, rather run it on world; or you could do "emerge -pv
>> @system" Modern portage versions deal with these blockers automatically,
>> but they need the whole dependency graph to do it. There's no much point
>> in trying to deal with system and world independently anyway, system
>> isn't something magical, it's nothing more than a minimum collection of
>> packages that Gentoo can still run on, a mere list.
> 
> Thanks for the info. Did it on world and got
> 
> -------------------------
> -> USE="pulseaudio sqlite libkms cups apng minizip hwdb" emerge -vp
> --newuse --tree --update --deep world
> 
> These are the packages that would be merged, in reverse order:
> 
> [snip]
> 
> [blocks B      ]  <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking
> sys-fs/udev-init-scripts-23)
> [blocks B      ]  <sys-apps/sysvinit-2.88-r4
> ("<sys-apps/sysvinit-2.88-r4" is blocking sys-apps/util-linux-2.22.2)
> 
> Total: 126 packages (91 upgrades, 12 new, 6 in new slots, 17
> reinstalls, 1 uninstall), Size of downloads: 989,597 kB
> Conflict: 7 blocks
> ------------------------
> 
> I have udev-171 at the moment and I have read and followed the
> instructions in the eselect news for the udev upgrade. I would
> appreciate any pointers on how to deal with this particular blocking.

First of all, don't put USE on the command line for emerge. It is not
stored and when you do the real emerge the results will be different if
you omit the USE. If you leave it in then portage doesn't know you did
it and complains bitterly with the next emerge claiming that flags
changed. Use make.conf like it is supposed to be used, don't try
second-guess portage.

Secondly, udev and sysvinit have higher versions marked stable. Portage
should just update them but apparently is not. I suspect you have masked
them in package.mask to avoid all the recefuss about udev, meaning you
have caused your own problem.

If you are happy moving to recent udev, then let portage do it.
If not, then you are on your own and have to figure out the masking
yourself. It will involve masking every new version of software that
shows up as a blocker like udev-init-scripts and util-linux. Eventually
you will run into an unsolveable conflict, maybe we are even already there


> nt 
> Thanks,
> 
> --
> Valmor
> 
>>
>> -ND to rebuild system doesn't get you anything extra and usually wants
>> to evaluate half of world as well (usually due to USE=X)
>>
>> You update system if you want to guarantee yourself a consistent
>> toolchain after a gcc or glibc update, or just prior to emerge -e world
>>
>>
>>
>>>
>>> [snip]
>>>
>>> [blocks B      ]  <sys-apps/sysvinit-2.88-r4
>>> ("<sys-apps/sysvinit-2.88-r4" is blocking sys-apps/util-linux-2.22.2)
>>> [blocks B      ] <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking
>>> sys-fs/udev-init-scripts-23)
>>> [blocks B      ] <sys-fs/lvm2-2.02.97-r1 ("<sys-fs/lvm2-2.02.97-r1" is
>>> blocking sys-fs/udev-197-r8)
>>>
>>> !!! Multiple package instances within a single package slot have been pulled
>>> !!! into the dependency graph, resulting in a slot conflict:
>>>
>>> x11-base/xorg-server:0
>>>
>>>   (x11-base/xorg-server-1.12.4::gentoo, installed) pulled in by
>>>     <x11-base/xorg-server-1.12.99[-minimal] required by
>>> (x11-drivers/xf86-video-virtualbox-4.1.22::gentoo, installed)
>>>     (and 1 more with the same problem)
>>>
>>>   (x11-base/xorg-server-1.13.1::gentoo, ebuild scheduled for merge) pulled in by
>>>     (no parents that aren't satisfied by other packages in this slot)
>>>
>>> virtual/udev:0
>>>
>>>   (virtual/udev-171::gentoo, installed) pulled in by
>>>     <virtual/udev-196 required by (sys-fs/lvm2-2.02.88::gentoo, installed)
>>>
>>>   (virtual/udev-197-r1::gentoo, ebuild scheduled for merge) pulled in by
>>>     >=virtual/udev-197-r1 required by (sys-fs/udev-197-r8::gentoo,
>>> ebuild scheduled for merge)
>>>     =virtual/udev-197-r1 required by
>>> (sys-apps/util-linux-2.22.2::gentoo, ebuild scheduled for merge)
>>>     (and 11 more with the same problems)
>>>
>>> sys-fs/udev:0
>>>
>>>   (sys-fs/udev-171-r9::gentoo, installed) pulled in by
>>>     ~sys-fs/udev-171[gudev?,hwdb?,introspection?,keymap?,selinux?]
>>> required by (virtual/udev-171::gentoo, installed)
>>>
>>>   (sys-fs/udev-197-r8::gentoo, ebuild scheduled for merge) pulled in by
>>>     >=sys-fs/udev-197-r8[gudev?,hwdb?,introspection?,keymap?,kmod?,selinux?,static-libs?]
>>> required by (virtual/udev-197-r1::gentoo, ebuild scheduled for merge)
>>>
>>> x11-drivers/xf86-video-virtualbox:0
>>>
>>>   (x11-drivers/xf86-video-virtualbox-4.1.24::gentoo, ebuild scheduled
>>> for merge) pulled in by
>>>     (no parents that aren't satisfied by other packages in this slot)
>>>
>>>   (x11-drivers/xf86-video-virtualbox-4.1.22::gentoo, installed) pulled in by
>>>     ~x11-drivers/xf86-video-virtualbox-4.1.22 required by
>>> (app-emulation/virtualbox-guest-additions-4.1.22::gentoo, installed)
>>>
>>
>>
>> --
>> Alan McKinnon
>> alan.mckinnon@gmail.com
>>
>>
> 


-- 
Alan McKinnon
alan.mckinnon@gmail.com

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

[Alex Schuster]

Hi there!

Some may remember me from posting here often. But since a year, I have a
new life, and much less time for sitting at my computer. Sigh. And my
beloved Gentoo got a little outdated.

So, a @world update does not work. I thought I give emerge -e @world a
try, this should sort out the problems, but this also does not go well.

I don't want to bother you with the whole lot of output emerge gives me,
and just ask a specific question at the moment. I get the 'Multiple
package instances within a single package slot have been pulled into the
dependency graph, resulting in a slot conflict' message, and several
affected packages. One example is claws:

mail-client/claws-mail:0

   (mail-client/claws-mail-3.9.0-r1::gentoo, ebuild scheduled for merge)
   pulled in by ~mail-client/claws-mail-3.9.0 required by
   (mail-client/claws-mail-address_keeper-1.0.7::gentoo, ebuild scheduled
   for merge)

   (mail-client/claws-mail-3.9.2::gentoo, ebuild scheduled for merge)
   pulled in by (no parents that aren't satisfied by other packages in
   this slot)

Looking at the ebuild, I see that claws-mail-address_keeper rdepends on
claws-mail-3.9.0. But being on ~amd86, 3.9.2 would be current.

I can solve this by masking versions greater than 3.9.0. Two questions:

Why can't portage deal with this itself, and simply install the highest
version that fulfills all requirements?

And how do I notice an update to claws-mail-address_keeper that would
allow a newer version of claws-mail? Other than remembering those masks
and go through them once in a while?

Similar problems happen with sys-boot/syslinux, pulled in by
sys-boot/unetbootin, media-sound/jack-audio-connection-kit, pulled in by
app-emulation/emul-linux-x86-soundlibs, and all dev-qt packages, where I
did not yet figure out what to do.

I am running portage 2.2.7.

	Alex

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

[Alan McKinnon]

On 04/10/2013 12:50, Alex Schuster wrote:
> Hi there!
> 
> Some may remember me from posting here often. But since a year, I have a
> new life, and much less time for sitting at my computer. Sigh. And my
> beloved Gentoo got a little outdated.
> 
> So, a @world update does not work. I thought I give emerge -e @world a
> try, this should sort out the problems, but this also does not go well.
> 
> I don't want to bother you with the whole lot of output emerge gives me,
> and just ask a specific question at the moment. I get the 'Multiple
> package instances within a single package slot have been pulled into the
> dependency graph, resulting in a slot conflict' message, and several
> affected packages. One example is claws:
> 
> mail-client/claws-mail:0
> 
>   (mail-client/claws-mail-3.9.0-r1::gentoo, ebuild scheduled for merge)
>   pulled in by ~mail-client/claws-mail-3.9.0 required by
>   (mail-client/claws-mail-address_keeper-1.0.7::gentoo, ebuild scheduled
>   for merge)
> 
>   (mail-client/claws-mail-3.9.2::gentoo, ebuild scheduled for merge)
>   pulled in by (no parents that aren't satisfied by other packages in
>   this slot)
> 
> Looking at the ebuild, I see that claws-mail-address_keeper rdepends on
> claws-mail-3.9.0. But being on ~amd86, 3.9.2 would be current.

No, that is not the right assumption.

Portage doesn't guess what versions are dependencies, it reads the
ebuild and does exactly what the ebuild says.

The ebuild for claws-mail-address_keeper say it depends on
~claws-mail-3.9.0, that means any revision of 3.9.0.

Portage *must not* decide to use 3.9.1 or 3.9.2, because the ebuild has
clearly told it not to.

The solution is to get the maintainer to bump the DEPENDS for that
plugin, or to use claws-mail-3.9.0, or to stop using that plugin.


emerge output is confusing. The last line you quoted is just portage
telling you that 3.9.2 would normally be the choice it would make, but
the lines above it says it's going to pick 3.9.0 instead,a nd why


> 
> I can solve this by masking versions greater than 3.9.0. Two questions:

No you can't. That will just produce different blockers

> 
> Why can't portage deal with this itself, and simply install the highest
> version that fulfills all requirements?


See above. It could deal with it if the ebuild didn't tell it something
different


> 
> And how do I notice an update to claws-mail-address_keeper that would
> allow a newer version of claws-mail? Other than remembering those masks
> and go through them once in a while?

emerge -avuND world

will tell you when updates are available


> 
> Similar problems happen with sys-boot/syslinux, pulled in by
> sys-boot/unetbootin, media-sound/jack-audio-connection-kit, pulled in by
> app-emulation/emul-linux-x86-soundlibs, and all dev-qt packages, where I
> did not yet figure out what to do.


Often with a box that is a while out of date, it is easier to just
unmerge blocking packages and add them back in. I've had this with Qt
more than once.



> 
> I am running portage 2.2.7.
> 
>     Alex
> 


-- 
Alan McKinnon
alan.mckinnon@gmail.com

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

[Kerin Millar]

On 04/10/2013 11:50, Alex Schuster wrote:
> Hi there!
>
> Some may remember me from posting here often. But since a year, I have a
> new life, and much less time for sitting at my computer. Sigh. And my
> beloved Gentoo got a little outdated.
>
> So, a @world update does not work. I thought I give emerge -e @world a
> try, this should sort out the problems, but this also does not go well.
>
> I don't want to bother you with the whole lot of output emerge gives me,
> and just ask a specific question at the moment. I get the 'Multiple
> package instances within a single package slot have been pulled into the
> dependency graph, resulting in a slot conflict' message, and several
> affected packages. One example is claws:
>
> mail-client/claws-mail:0
>
>    (mail-client/claws-mail-3.9.0-r1::gentoo, ebuild scheduled for merge)
>    pulled in by ~mail-client/claws-mail-3.9.0 required by
>    (mail-client/claws-mail-address_keeper-1.0.7::gentoo, ebuild scheduled
>    for merge)
>
>    (mail-client/claws-mail-3.9.2::gentoo, ebuild scheduled for merge)
>    pulled in by (no parents that aren't satisfied by other packages in
>    this slot)
>
> Looking at the ebuild, I see that claws-mail-address_keeper rdepends on
> claws-mail-3.9.0. But being on ~amd86, 3.9.2 would be current.
>
> I can solve this by masking versions greater than 3.9.0. Two questions:
>
> Why can't portage deal with this itself, and simply install the highest
> version that fulfills all requirements?

Your use of --emptytree makes it slightly harder to determine from the 
above output, because the conflict messages will not correctly 
distinguish merged (installed) packages from those that are yet to be 
merged.

Do you have mail-client/claws-mail-address_keeper in your world file? If 
so, that would mandate its installation as part of the @world set (no if 
or buts). In turn, that would exhibit a hard dependency on 
claws-mail-3.9.0, which obviously cannot co-exist with 3.9.2, even if 
you have unmasked it.

Try removing the entry from the world file if it's there, then seeing 
whether the conflict is handled any differently.

>
> And how do I notice an update to claws-mail-address_keeper that would
> allow a newer version of claws-mail? Other than remembering those masks
> and go through them once in a while?

As of the 3.9.1 ebuild, there is a comment above the collection of 
blocks that states:

"Plugins are all integrated or dropped since 3.9.1"

Further, from the 3.9.1 release notes:

"All plugins previously packaged as 'Extra Plugins' are now contained 
within the Claws Mail package."

Thus, it's possible that the address_keeper plugin has been folded into 
the core. In turn, that would explain why it must block the plugin as a 
separate package.

>
> Similar problems happen with sys-boot/syslinux, pulled in by
> sys-boot/unetbootin, media-sound/jack-audio-connection-kit, pulled in by
> app-emulation/emul-linux-x86-soundlibs, and all dev-qt packages, where I
> did not yet figure out what to do.
>
> I am running portage 2.2.7.
>
>      Alex
>

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

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 965 bytes --]

On Fri, 04 Oct 2013 12:50:51 +0200, Alex Schuster wrote:

> mail-client/claws-mail:0
> 
>    (mail-client/claws-mail-3.9.0-r1::gentoo, ebuild scheduled for merge)
>    pulled in by ~mail-client/claws-mail-3.9.0 required by
>    (mail-client/claws-mail-address_keeper-1.0.7::gentoo, ebuild
> scheduled for merge)
> 
>    (mail-client/claws-mail-3.9.2::gentoo, ebuild scheduled for merge)
>    pulled in by (no parents that aren't satisfied by other packages in
>    this slot)
> 
> Looking at the ebuild, I see that claws-mail-address_keeper rdepends on
> claws-mail-3.9.0. But being on ~amd86, 3.9.2 would be current.

Claws Mail plugins are now part of the main ebuild, upstream moved them
into the main tarball with their building handled by ./configure. If you
unmerge all plugins, claws-mail should update and build whichever plugins
your USE flags desire.


-- 
Neil Bothwick

I am Speedy Gonzales of Borg: Prepare to be accelerated!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

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

[Alex Schuster]

Kerin Millar writes:

> On 04/10/2013 11:50, Alex Schuster wrote:

[...]

> >    (mail-client/claws-mail-3.9.0-r1::gentoo, ebuild scheduled for
> > merge) pulled in by ~mail-client/claws-mail-3.9.0 required by
> >    (mail-client/claws-mail-address_keeper-1.0.7::gentoo, ebuild
> > scheduled for merge)
> >
> >    (mail-client/claws-mail-3.9.2::gentoo, ebuild scheduled for merge)
> >    pulled in by (no parents that aren't satisfied by other packages in
> >    this slot)
> >
> > Looking at the ebuild, I see that claws-mail-address_keeper rdepends
> > on claws-mail-3.9.0. But being on ~amd86, 3.9.2 would be current.
> >
> > I can solve this by masking versions greater than 3.9.0. Two
> > questions:
> >
> > Why can't portage deal with this itself, and simply install the
> > highest version that fulfills all requirements?
> 
> Your use of --emptytree makes it slightly harder to determine from the 
> above output, because the conflict messages will not correctly 
> distinguish merged (installed) packages from those that are yet to be 
> merged.

I get some more errors without --emptytree (media-libs/x264,
dev-libs/icu, dev-libs/boost, app-text/poppler, dev-util/boost-build,
dev-lang/ocaml, x11-base/xorg-server), so I gave -e a try.

> Do you have mail-client/claws-mail-address_keeper in your world file?

Sure.

> If so, that would mandate its installation as part of the @world set
> (no if or buts). In turn, that would exhibit a hard dependency on 
> claws-mail-3.9.0, which obviously cannot co-exist with 3.9.2, even if 
> you have unmasked it.

Right. 

> Try removing the entry from the world file if it's there, then seeing 
> whether the conflict is handled any differently.

I guess this would install 3.9.2, as there's no reason not to do this.

> > And how do I notice an update to claws-mail-address_keeper that would
> > allow a newer version of claws-mail? Other than remembering those
> > masks and go through them once in a while?
> 
> As of the 3.9.1 ebuild, there is a comment above the collection of 
> blocks that states:
> 
> "Plugins are all integrated or dropped since 3.9.1"
> 
> Further, from the 3.9.1 release notes:
> 
> "All plugins previously packaged as 'Extra Plugins' are now contained 
> within the Claws Mail package."
> 
> Thus, it's possible that the address_keeper plugin has been folded into 
> the core. In turn, that would explain why it must block the plugin as a 
> separate package.

Good catch! Thanks, also to Neil. I unmerged this plugin, and claws
updates just fine.

Well. Sort of. Emerge also wanted to re-merge libreoffice, I have no idea
why. The same happened yesterday when I upgraded portage. Whatever :) This
time, I used --exclude app-office/libreoffice to avoid this.

	Alex

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

[Alan McKinnon]

On 04/10/2013 17:40, Alex Schuster wrote:
> Well. Sort of. Emerge also wanted to re-merge libreoffice, I have no idea
> why. The same happened yesterday when I upgraded portage. Whatever :) This
> time, I used --exclude app-office/libreoffice to avoid this.


probably a poppler or icu or java update, or any one of the many things
libreoffice uses that changes ABI at the drop of a hat.

Recent portage with subslot support triggers a libreoffice rebuild when
that happens, it is seldom an error. You can leave it out of the world
emerge to speed things up, but revdep-rebuild is probably going to also
find it and want to do the same

-- 
Alan McKinnon
alan.mckinnon@gmail.com

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

[Alex Schuster]

Alan McKinnon writes:

> On 04/10/2013 17:40, Alex Schuster wrote:
> > Well. Sort of. Emerge also wanted to re-merge libreoffice, I have no
> > idea why. The same happened yesterday when I upgraded portage.
> > Whatever :) This time, I used --exclude app-office/libreoffice to
> > avoid this.
> 
> probably a poppler or icu or java update, or any one of the many things
> libreoffice uses that changes ABI at the drop of a hat.
> 
> Recent portage with subslot support triggers a libreoffice rebuild when
> that happens, it is seldom an error. You can leave it out of the world
> emerge to speed things up, but revdep-rebuild is probably going to also
> find it and want to do the same

No, there is something wrong here. When I updated portage, it also
remerged libreoffice. Upgrading claws-mail updated dev-libs/libdbusmenu
and dev-libs/libindicate, and wanted to remerge libreoffice, which I
avoided.
Next, I updated chromium, which also remerged libreoffice. Again.

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.

	Alex

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

[Bruce Hill]

On Sat, Oct 05, 2013 at 05:59:52PM +0200, Alex Schuster wrote:
> 
> No, there is something wrong here. When I updated portage, it also
> remerged libreoffice. Upgrading claws-mail updated dev-libs/libdbusmenu
> and dev-libs/libindicate, and wanted to remerge libreoffice, which I
> avoided.
> Next, I updated chromium, which also remerged libreoffice. Again.
> 
> 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.

Please run:

emerge wgetpaste && emerge -Djptuv --changed-use @world |& wgetpaste

If you already have wgetpaste just run:

emerge -Djptuv --changed-use @world |& wgetpaste

and post the link it outputs.
-- 
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting

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

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 834 bytes --]

On Sat, 5 Oct 2013 17:59:52 +0200, Alex Schuster wrote:

> No, there is something wrong here. When I updated portage, it also
> remerged libreoffice. Upgrading claws-mail updated dev-libs/libdbusmenu
> and dev-libs/libindicate, and wanted to remerge libreoffice, which I
> avoided.
> Next, I updated chromium, which also remerged libreoffice. Again.
> 
> 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. With a suitable
--jobs setting, portage will emerge all the other packages before LO is
done.


-- 
Neil Bothwick

Windows Multitasking - screwing up several things at once

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

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

[Alex Schuster]

Neil Bothwick writes:

> On Sat, 5 Oct 2013 17:59:52 +0200, Alex Schuster wrote:
> 
> > No, there is something wrong here. When I updated portage, it also
> > remerged libreoffice. Upgrading claws-mail updated
> > dev-libs/libdbusmenu and dev-libs/libindicate, and wanted to remerge
> > libreoffice, which I avoided.
> > Next, I updated chromium, which also remerged libreoffice. Again.
> > 
> > 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

	Alex

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

[Alan McKinnon]

On 05/10/2013 18:22, Bruce Hill wrote:
> On Sat, Oct 05, 2013 at 05:59:52PM +0200, Alex Schuster wrote:
>>
>> No, there is something wrong here. When I updated portage, it also
>> remerged libreoffice. Upgrading claws-mail updated dev-libs/libdbusmenu
>> and dev-libs/libindicate, and wanted to remerge libreoffice, which I
>> avoided.
>> Next, I updated chromium, which also remerged libreoffice. Again.
>>
>> 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.
> 
> Please run:
> 
> emerge wgetpaste && emerge -Djptuv --changed-use @world |& wgetpaste
> 
> If you already have wgetpaste just run:
> 
> emerge -Djptuv --changed-use @world |& wgetpaste
> 
> and post the link it outputs.
> 



Please don't use pastebins

Posts here are archived forever, pastebins are not. The information in
them is lost forever. Rather just stick the output in the body of a mail
where it can be directly read by the person who needs to read it.

1994 went by a long time ago, we no longer care about 80k worth of email
body



-- 
Alan McKinnon
alan.mckinnon@gmail.com

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

[Alan McKinnon]

On 05/10/2013 20:30, Alex Schuster wrote:
> Neil Bothwick writes:
> 
>> On Sat, 5 Oct 2013 17:59:52 +0200, Alex Schuster wrote:
>>
>>> No, there is something wrong here. When I updated portage, it also
>>> remerged libreoffice. Upgrading claws-mail updated
>>> dev-libs/libdbusmenu and dev-libs/libindicate, and wanted to remerge
>>> libreoffice, which I avoided.
>>> Next, I updated chromium, which also remerged libreoffice. Again.
>>>
>>> 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
> 
> 	Alex
> 


Now that you have upgraded portage, does this behaviour (always wanting
to rebuild LO) still happen?



-- 
Alan McKinnon
alan.mckinnon@gmail.com

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

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 680 bytes --]

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.


-- 
Neil Bothwick

Do you realize how many holes there could be if people would just take
the time to take the dirt out of them?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

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

[Helmut Jarausch]

On 10/05/2013 08:30:36 PM, Alex Schuster wrote:
> Neil Bothwick writes:
> 
> > On Sat, 5 Oct 2013 17:59:52 +0200, Alex Schuster wrote:
> >
> > > No, there is something wrong here. When I updated portage, it also
> > > remerged libreoffice. Upgrading claws-mail updated
> > > dev-libs/libdbusmenu and dev-libs/libindicate, and wanted to  
> remerge
> > > libreoffice, which I avoided.
> > > Next, I updated chromium, which also remerged libreoffice. Again.
> > >
> > > 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
> 

You are not alone, Alex, please see

https://bugs.gentoo.org/show_bug.cgi?id=486438

Helmut

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

[Alex Schuster]

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

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

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 644 bytes --]

On Mon, 7 Oct 2013 00:01:33 +0200, Alex Schuster wrote:

> > 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.

Ah yes, I forgot about that option. A simpler way of doing the same
thing. I'd use a specific version so that you don't miss out on updates.


-- 
Neil Bothwick

In space, no one can hear you fart.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]