#wine-staging

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

04Bug 550506: normal, Normal, ---, wine, UNCONFIRMED , app-emulation/wine-9999: Failed Patch: 0001-atl-Added-stub-AtlIPersistPropertyBag_Save.patch

woo, life on the bleeding edge gcc builds

anish: "it compiles, lets ship it" ;)

sounds like a plan

sounds about right

where do I report games that work in staging but not in wine?

I am pretty sure I have one this time

it's the new touhou fighter

Hijiri: i would recommend to check if there is a bug report on bugs.winehq.org matching the problem you have with vanilla wine

Hijiri: and then report there, that the problem doesn't occur when using wine-staging

Hijiri: if you are a bit experienced with compiling wine, you can also try to bisect which patch exactly fixes it

slackner, didn't you want to fork appdb too?

ok, thanks, I'll do it when I'm not in class later

Yoshimo: not fork, its too ugly - we want to rewrite it from scratch based on modern frameworks

Yoshimo: but its not finished yet and doesn't have the highest priority atm

Hijiri: kk, if you are planning to bisect and need help, just ask here ;)

i agree from a graphical point of view, does the code look similiarly ugly?

Yoshimo: yes, its based on php and full of bugs - the upstream database (which is public available for download) is even partially corrupted

dangling references all over the place ^^

moreover it was written in ancient php versions .. any more questions? *g*

not really

10New Wine Staging bug 324 filed by sergey.slice@gmail.com.

04Bug http://bugs.wine-staging.com/show_bug.cgi?id=324 normal, ---, ---, bugs, UNCONFIRMED , Impossible to apply patches to wine 1.7.44

10sebastian@fds-team.de changed the Status on bug 324 from UNCONFIRMED --- to RESOLVED INVALID.

hey guys, I'm trying to create a pkgbuild for wine-staging seeing as the current one is very old

I'm getting this with a fresh prefix though now: http://dpaste.com/0A5ZKX7

different errors with existing prefix, driver couldnt be loaded or some such

this is the pkgbuild: http://dpaste.com/1QMSEDK

crap, sec

jleclanche: you are trying to compile wine with gcc 5.1

yes i am

jleclanche: downgrade gcc, then it should work

jleclanche: gcc 5.1 currently results in broken wine builds, this is not wine-staging specific

slackner, is there a bug for that somewhere?

jleclanche: but .. i'm wondering a bit, there are up-to-date PKGBUILDs everywhere

damn.

austin_laptop: not sure if there is an upstream one, but in our bug tracker it was reported already

jleclanche: wine-silverlight on AUR is basically wine-staging, the weird name has historical reasons ^^

jleclanche: or you can also use my repos: http://repos.fds-team.de/stable/arch/

(instructions: https://github.com/wine-compholio/wine-staging/... )

slackner, url?

please note that 1.7.44 was not released yet, so doesn't make sense to build that one ^^

hm ill use your repos

and uh

i didnt have issues compiling my own version of wine-multimedia from git, last build was last week

jleclanche: i've locked the gcc version on my builders, so they should work

so i think this is an issue on wine-staging, austin_laptop

jleclanche: yes, gcc was updated just recently

or thats possible too

jleclanche: no, its a general issue with wine of course

yeah seemed like a weird coincidence

austin_laptop: for example https://bugs.wine-staging.com/show_bug.cgi?id=270

04Bug 270: normal, ---, ---, bugs, UNCONFIRMED , Cannot launch MS Office 2010 (broken wine build with gcc 5.1)

btw slackner whats -compat in your repo?

jleclanche: our wine-staging packages install to /opt/wine-staging, to try out the staging version parallel to regular wine

jleclanche: if you don't want that, install wine-staging-compat additionally, it provides compatibility symlinks to replace regular wine

slackner, thanks

eck

ill try to downgrade i think then

jleclanche: thats also no perfect solution, you'll still need the up-to-date gcc-libs packages

jleclanche: otherwise it breaks packages from official arch repos

yes thats not an issue

actually uh

slackner: how did you downgrade it?

jleclanche: i never upgraded it, i locked when the packages before

ergh

no package for gcc49, ill grab gcc48

austin_laptop: you taking care of filing this on wine?

slackner: regarding the package in the aur, im not a fan of the pkgbuild, this is the one i wrote: http://dpaste.com/1NF9388

jleclanche, no; I was just curious about it. Please cc me if you do file one.

slackner: if you need it moved let me know

austin_laptop: will do in a min

jleclanche: thx for sharing. what do you mean with "need it moved" ?

jleclanche: we already have our own pkgbuilds for the builders, but if you have some useful changes, feel free to send me patches ;)

jleclanche: i would like to keep the folder layout though, most people using wine-staging use it in addition to upstream wine, not as a replacement

jleclanche: you can find the build files for 1.7.43 here for example: http://repos.fds-team.de/stable/all/20150525-12...

slackner: i meant fo rthe AUR one

makes no sense for it to be at wine-silverlight

just file a merge request with wine-staging and replace the pkgbuild

i can merge it now if you file it

jleclanche: i'm not responsible for maintaining the wine-silverlight AUR package, anish is the maintainer

anish: ^

jleclanche: problem with merging / renaming is that people will not be able to upgrade easily

ok

I've bought this up multiple times

I don't own the staging package

I talked to the maintainer

he was ready to abandon it

and he hasn't

anish: the maintainer abandoned it

last month

okay

I'll take it then

anish: take a look at the pkgbuild i linked please

jleclanche: what did you change ?

i wrote a new one from scratch

just kept the build process

why ./patchinstall.sh ?

no idea, like i said i kept the old build process

also what slacker mentioned earlier

the main package shouldnt allow duplicate installation

if you want to allow it, you can create a separate package that installs to opt

see

the problem is there are no guidelines for this

you might make that package

someone is going to come along and claim it as dup

and it's gonna get removed

(this has happened before0

bring it up if it happens

with me or another TU

if the packages are legitimately different then it shouldnt get flagged

maybe, but there is no process for that

I have to monitor the aur mailing list to be aware of something like this

merge discussions don't tend to email the maintainers

(at least I haven't been)

anish: Make sure the descriptions clearly flag the difference then it's up to the TU that reviews it

ok

but that still leaves the migration issue

wine-silverlight has been around since 2012