#wine-staging

anish: ping

Isn't it planned to have a staging branch on winehq?

it's not really a branch

it can become one

i don't think so, as long as it's not a full source tree

Andre_H: it is not planned to change the whole concept of wine-staging. there are good reasons why we maintain it as a set of patches

Andre_H: the idea of wine staging only works with patches properly, so there will never be a normal branch

well, yes, that's what I meant

ok, so I can stop monitoring

Andre_H: yep, staging will not appear there. it might be possible that winehq will mirror the repo though

winehq will most probably mirror the patches

in a ftp or in a git way?

i would think of a git mirror

so beside of that all staging related things we agreed on at wineconf are implemented now?

Andre_H: no, there is a lot still missing

for example? (trying to get some infos for todays WWN)

we working on providing binary packages, but we still don't know how we are supposed to provide the packages

patch flow things are not there yet

meaning patch status list

i heard that they have a CDN now, but no one talked to us so far about syncing files and the details of the repositories

i think it's still in a process of setting that up, but no need to wait for that, better to ask right away

well, I don't consider the packaging things as a part of "staging integration"

sure, you did the work, but it's packaging of wine, not wine itself

- patch status page needs to be updated for signed-off-by

- automatic reject notifications still missing

(i think we agreed on that point at wineconf, right?)

- assigning reviewers might also need changes

another thing which is missing so far, is a way to submit patches explicitly to staging. This is not really upstreams fault though, we haven't decided about the optimal way yet.

- and, as mentioned yesterday, the current MAINTAINERS list doesn't really work yet for areas without frequent contributors

yep, thats another good point

that all doesn't sound that "staging" to me... we have staging things in the bugzilla related infrastructure now, that is staging integration to me

DarkPlayer: good point

Andre_H: well, i would consider it all part of the staging integration. obviously changes do not only affect one of both sides ;)

Hello

I have an issue with wine-staging

I can't open any exe

fixme:service:scmdatabase_autostart_services Auto-start service L"MountMgr" failed to start: 2

this is the error

and then "bad exe format"

edoardo: which distribution?

Debian Stretch

oh hang on

looks like i'm not running staging

wine --version

wine-1.6.2

edoardo: yep, that isn't wine-staging. but your description of the problem sounds like you are missing the 32-bit part of wine

i have the 32 bit wine

with multiarch

wine:i386 and wine64:x86_64

edoardo: do you have wine-staging installed in parallel, and if yes, does it show the same issue?

(most packages install it to /opt/wine-staging/bin/wine)

nope i tought to have staging in this machine, but i have the stock wine

let me add the staging version

and remove the old one

edoardo: its most likely not a problem of wine in general, but either a missing package, or a broken wine build

that's why i'm removing the entire install

edoardo: most distros are not aware that the stable version 1.6.2 released over 2 years ago doesn't build properly with modern gcc 5 anymore

what packages do i need?

wine-staging and wine-staging-amd64?

ok nvm, solved it

edoardo: just wine-staging, it will pull in all required dependencies

i also installed wine-staging-compat