http://bugs.winehq.org/show_bug.cgi?id=13912
Summary: Appdb does not show Wine version 1.0-rc5. Product: WineHQ Apps Database Version: unspecified Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P1 Component: appdb-unknown AssignedTo: wine-bugs@winehq.org ReportedBy: kennybobs@o2.co.uk
Adding test results to the appdb does not yet show 1.0-rc5 as a Wine version.
http://bugs.winehq.org/show_bug.cgi?id=13912
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Difficulty|--- |Minutes
http://bugs.winehq.org/show_bug.cgi?id=13912
Jeff Zaroyko jeffzaroyko@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffzaroyko@gmail.com
--- Comment #1 from Jeff Zaroyko jeffzaroyko@gmail.com 2008-06-14 17:16:34 --- it has to be added to bugzilla since the appdb retrieves a list of versions from that database.
http://bugs.winehq.org/show_bug.cgi?id=13912
--- Comment #2 from Jeff Zaroyko jeffzaroyko@gmail.com 2008-06-14 20:57:31 --- I have written an program in elisp to do this if it helps streamline this into the release process, since a few people have joked on irc about writing an emacs script to do this, I've gone ahead and done it.
http://jeffz.name/wine/winehq-bugzilla.el
http://bugs.winehq.org/show_bug.cgi?id=13912
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|appdb-unknown |bugzilla-unknown Product|WineHQ Apps Database |WineHQ Bugzilla
http://bugs.winehq.org/show_bug.cgi?id=13912
Jeff Zaroyko jeffzaroyko@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |julliard@winehq.org
--- Comment #3 from Jeff Zaroyko jeffzaroyko@gmail.com 2008-06-14 22:09:38 --- Since this happens every so often, can this or something similar be adopted for the release process?
http://bugs.winehq.org/show_bug.cgi?id=13912
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Difficulty|Minutes |---
http://bugs.winehq.org/show_bug.cgi?id=13912
--- Comment #4 from Alexandre Julliard julliard@winehq.org 2008-06-16 02:50:00 --- Ideally this should be done in the wine_release script (http://source.winehq.org/git/tools.git/?a=blob;f=wine_release), which is run under the wineowner account on WineHQ at release time.
http://bugs.winehq.org/show_bug.cgi?id=13912
--- Comment #5 from Jeff Zaroyko jeffzaroyko@gmail.com 2008-06-16 06:13:55 --- Created an attachment (id=14091) --> (http://bugs.winehq.org/attachment.cgi?id=14091) interactive patch, prompts for authorised bugzilla email and password on stdin
is it run interactively or by something else?
http://bugs.winehq.org/show_bug.cgi?id=13912
--- Comment #6 from Jeff Zaroyko jeffzaroyko@gmail.com 2008-06-16 06:17:04 --- Created an attachment (id=14092) --> (http://bugs.winehq.org/attachment.cgi?id=14092) add the release to the list of available versions using an authorised bugzilla email and pass supplied in the environment
if it's not run interactively, can two environment variables be set by the calling process with an authorised bugzilla email and password?
http://bugs.winehq.org/show_bug.cgi?id=13912
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch
http://bugs.winehq.org/show_bug.cgi?id=13912
--- Comment #7 from Alexandre Julliard julliard@winehq.org 2008-06-16 08:21:39 --- It's not run interactively, it's called from my local release script. Though if it's a web query it doesn't have to be in wine_release. I was thinking it would be possible to add it to the database directly on the winehq side.
In any case this should really be a shell script, the discussion about doing this in emacs was a joke, my release script is not in elisp. We don't even have emacs installed on winehq...
And if it requires a user account, someone will have to give me permissions to do this ;-)
http://bugs.winehq.org/show_bug.cgi?id=13912
--- Comment #8 from Jeff Zaroyko jeffzaroyko@gmail.com 2008-06-16 17:04:28 --- (In reply to comment #7)
It's not run interactively, it's called from my local release script. Though if it's a web query it doesn't have to be in wine_release. I was thinking it would be possible to add it to the database directly on the winehq side.
In any case this should really be a shell script, the discussion about doing this in emacs was a joke, my release script is not in elisp. We don't even have emacs installed on winehq...
And if it requires a user account, someone will have to give me permissions to do this ;-)
Well, elisp is not a joke.
It can be turned into a shell script by adding "#!/usr/bin/emacs --script" to the head of the file.
http://bugs.winehq.org/show_bug.cgi?id=13912
--- Comment #9 from Austin English austinenglish@gmail.com 2008-06-17 07:07:50 --- (In reply to comment #8)
Well, elisp is not a joke.
It can be turned into a shell script by adding "#!/usr/bin/emacs --script" to the head of the file.
What good will that do if emacs isn't installed on that system?
http://bugs.winehq.org/show_bug.cgi?id=13912
--- Comment #10 from Jeff Zaroyko jeffzaroyko@gmail.com 2008-06-17 16:19:22 --- (In reply to comment #9)
(In reply to comment #8)
Well, elisp is not a joke.
It can be turned into a shell script by adding "#!/usr/bin/emacs --script" to the head of the file.
What good will that do if emacs isn't installed on that system?
Why is installing emacs a problem?
http://bugs.winehq.org/show_bug.cgi?id=13912
--- Comment #10 from Jeff Zaroyko jeffzaroyko@gmail.com 2008-06-17 16:19:22 --- (In reply to comment #9)
(In reply to comment #8)
Well, elisp is not a joke.
It can be turned into a shell script by adding "#!/usr/bin/emacs --script" to the head of the file.
What good will that do if emacs isn't installed on that system?
Why is installing emacs a problem?
--- Comment #11 from Jeff Zaroyko jeffzaroyko@gmail.com 2008-06-18 04:40:26 --- Created an attachment (id=14151) --> (http://bugs.winehq.org/attachment.cgi?id=14151) one liner
ok - instead as suggested, how about using this one liner to insert the version into the bugs.version table if wineuser has access to do so without a password?
http://bugs.winehq.org/show_bug.cgi?id=13912
--- Comment #12 from Alexandre Julliard julliard@winehq.org 2008-06-18 13:58:39 --- (In reply to comment #11)
Created an attachment (id=14151)
--> (http://bugs.winehq.org/attachment.cgi?id=14151) [details]
one liner
ok - instead as suggested, how about using this one liner to insert the version into the bugs.version table if wineuser has access to do so without a password?
That's much nicer, thanks. There is a password on the mysql account, but we can probably handle that with a private config file.
http://bugs.winehq.org/show_bug.cgi?id=13912
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #13 from Alexandre Julliard julliard@winehq.org 2008-06-27 10:07:58 --- Looks like it worked, I've added it to the release script. Thanks.
http://bugs.winehq.org/show_bug.cgi?id=13912
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #14 from Ken Sharp kennybobs@o2.co.uk 2009-01-10 21:36:02 --- All looks ok now? Closing...
-
wine-bugs＠winehq.org