Bug 628450 – app-eselect/eselect-wine: wacky results when emerging app-emulation/wine-*

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description Greg Turner 2017-08-21 00:13:20 UTC]

I have fully figured out what's going on, but as things stand, I notice that after emerging app-emulation/wine-* packages, a "random" version of wine gets selected.

If I had to guess (without investigating), I'd say maybe the ordering of the list is shuffled by emerging, but maybe the app-emulation/wine-* packages just preserve the active list-index when merging a new package.

Why I think so:

I had these installed:

app-emulation/wine-d3d9-2.12:2.12::gentoo
app-emulation/wine-staging-2.12:2.12::gentoo
app-emulation/wine-vanilla-2.13:2.13::gentoo
app-eselect/eselect-wine-1.1:0::gentoo

with -staging active.

I observed that emerging -staging "automatically" moved me from -staging to -vanilla, and I'm pretty sure -- but not positive -- that the ordering of the list was altered.

[Comment 1 Greg Turner 2017-08-21 00:13:52 UTC]

(In reply to Greg Turner from comment #0)
> I have fully figured out what's going on

correction: have /not/ fully figured out what's going on :)

[Comment 2 Jeroen Roovers (RETIRED) 2017-08-26 12:12:08 UTC]

(In reply to Greg Turner from comment #1)
> correction: have /not/ fully figured out what's going on :)

Please reopen this bug report when you at least figure out what you think the bug is you're reporting. Because "wacky results" doesn't sufficiently describe it.

[Comment 3 Greg Turner 2017-09-20 18:13:35 UTC]

(In reply to Jeroen Roovers from comment #2)
> (In reply to Greg Turner from comment #1)
> > correction: have /not/ fully figured out what's going on :)
> 
> Please reopen this bug report when you at least figure out what you think
> the bug is you're reporting. Because "wacky results" doesn't sufficiently
> describe it.

I understand your reluctance about a vague bug report, but if you strip out all the speculative stuff my bug report is pretty concrete:

Using the masked(?) wine-* packages and eselect-wine, when wine packages are merged, one's system is migrated to a different wine.

So, let's say, Monday, I have selected wine-stable, and run emerge @world (or, just emerge -1a $(qlist -ISC wine)).  On Tuesday, I will find, I am now on wine-d3d9 or some other thing.

This suggests there is something wrong with the logic in pkg_prerm or pkg_postinst.  At a glance, I wonder, might the heuristics in that code not parallelize safely -- but now I am speculating again so please ignore this paragraph :P