[]This is getting a little weird - wine/wine-staging/wine-staging-opt

nomorewindows · 2015-10-04 23:45:48

Earlier today it was wine-staging in conflict with wine which seems to be ok. But now wine-staging-opt at the same time wine-staging is installed? And wine-staging-opt is a later version than wine-staging. Of course this would be the pipelight unofficial repo.

Last edited by nomorewindows (2015-10-11 02:10:35)

karol · 2015-10-05 19:43:58

wine-staging from the official repos conflicts with what and why? Or do you mean wine-staging from the unofficial repo? Do these packages provide wine, wine-staging or ... ? What do you need wine-staging-opt for? Are you sure you need wine-staging as well?

root · 2015-10-05 20:29:52

No weird stuff at all.

If you check wine-staging-opt's package information you will see that it conflicts with wine-staging (be it the official or the unofficial pipelight one).

As you are using the unofficial pipelight repo the fix is simply to let wine-staging-opt remove wine-staging. You may encounter an error on behalf of pipelight needing it (I presume you are using that package too from the very same repo) but it is easily fixed by (re)installing it along with wine-staging-opt.
That way the newly installed pipelight package will be associated with wine-staging-opt and not wine-staging (just check pipelight package info).

All this, of course, if you need all those different packages (official (stand-alone(?)) wine plus a compatible (aka not in conflict with the former) wine-staging package) as karol has mentioned.

EDiT: Corrected wine-staging conflict reference

Last edited by root (2015-10-09 05:15:24)

nomorewindows · 2015-10-07 19:49:31

Wine-staging and wine-staging-opt are both installed at the same time with no report of conflict.
Wine-staging knocked off wine as a conflict.

karol · 2015-10-07 22:09:55

nomorewindows wrote:

Wine-staging and wine-staging-opt are both installed at the same time with no report of conflict.
Wine-staging knocked off wine as a conflict.

nomorewindows wrote:

But now wine-staging-opt at the same time wine-staging is installed?

Does it mean all is well now?

root · 2015-10-09 05:25:16

nomorewindows wrote:

Wine-staging and wine-staging-opt are both installed at the same time with no report of conflict.
Wine-staging knocked off wine as a conflict.

If the wine-staging package is the official community one there shouldn't be any conflict as wine-staging-opt does only with wine-staging<1.7.52.
This affects only the unofficial pipelight package which is 1.7.51-2 (I have updated my previous post accordingly).

You only referred to the pipelight repo,

Of course this would be the pipelight unofficial repo.

so it is hard to focus on the official community one

Long story short, all works just as it should and nothing weird is happening as far as I can tell.

nomorewindows · 2015-10-09 14:55:26

I think I just have a duplicate wine with wine-staging and wine-staging-opt.
Ok here's the difference:
wine-staging required for wine-mono
and wine-staging-opt required for pipelight

wine-staging provides wine
wine-staging-opt provides (none)

karol · 2015-10-09 21:49:59

I still don't know why do you need two packages. Can't you make pipelight work with wine-staging? What do you need wine-mono for?

nomorewindows · 2015-10-11 01:48:48

karol wrote:

I still don't know why do you need two packages. Can't you make pipelight work with wine-staging? What do you need wine-mono for?

That's what the packages specify and there is also one from the multilib repo. It is defaulting to use the multilib one. The wine-staging from multilib is newer than the one in pipelight, and the wine-staging-opt is closer to the version from multilib. But then to do pacman -S pipelight/wine-staging gives the error that wine-staging and wine-staging-opt (both of pipelight in this case) are in conflict (like we would expect), and of wine-mono needing wine (wine-staging), and wine-staging-opt is needed for pipelight. This is the same provides/requires that I just specified in my previous post.

Last edited by nomorewindows (2015-10-11 01:49:45)

nomorewindows · 2015-10-11 02:09:34

Moving multilib to below pipelight in pacman.conf. Removed wine-staging/wine-staging-opt/pipelight/wine-mono. pacman -S pipelight wine-mono and now everything should be fine. I could have been using multilib's wine-staging for awhile but this change came up just this week with pipelight's unofficial repo. So maybe this will fix the unexpected behaviour. Pacman installed wine (which was original), wine-staging-opt, wine-mono, and pipelight.

Arch Linux

#1 2015-10-04 23:45:48

[]This is getting a little weird - wine/wine-staging/wine-staging-opt

#2 2015-10-05 19:43:58

Re: []This is getting a little weird - wine/wine-staging/wine-staging-opt

#3 2015-10-05 20:29:52

Re: []This is getting a little weird - wine/wine-staging/wine-staging-opt

#4 2015-10-07 19:49:31

Re: []This is getting a little weird - wine/wine-staging/wine-staging-opt

#5 2015-10-07 22:09:55

Re: []This is getting a little weird - wine/wine-staging/wine-staging-opt

#6 2015-10-09 05:25:16

Re: []This is getting a little weird - wine/wine-staging/wine-staging-opt

#7 2015-10-09 14:55:26

Re: []This is getting a little weird - wine/wine-staging/wine-staging-opt

#8 2015-10-09 21:49:59

Re: []This is getting a little weird - wine/wine-staging/wine-staging-opt

#9 2015-10-11 01:48:48

Re: []This is getting a little weird - wine/wine-staging/wine-staging-opt

#10 2015-10-11 02:09:34

Re: []This is getting a little weird - wine/wine-staging/wine-staging-opt

Board footer