For an easier user testing experience, you can now install the latest git as a convenient Ubuntu package.
The instructions are very similar to using the standard Ubuntu packages, however the PPA name is different. Instead of ppa:ubuntu-wine/ppa, you add ppa:ubuntu-wine/daily.
From a terminal:
sudo add-apt-repository ppa:ubuntu-wine/daily sudo apt-get update sudo apt-get install wine1.3
The packages are versioned like wine1.3-1.3.27+daily-20110901.
Limitations: The major version number is based on the latest released version of the Ubuntu packages, so on release days you might see something like 1.3.27+daily-20110909 which would actually be equivalent 1.3.28. If I get especially behind and don't update the official packages after Monday, you might even see a "1.3.27+daily" that's actually ahead of 1.3.28.
In all cases wine --version should return what it normally does, however - this is just the package revision that is being wonky.
Possible future: These packages are a convenient way to run some tests that may be much too slow for testbot to run against every patch, such as autohotkey-based application automation.
Thanks, Scott Ritchie
On 1 September 2011 10:50, Scott Ritchie scott@open-vote.org wrote:
For an easier user testing experience, you can now install the latest git as a convenient Ubuntu package.
This seems very handy, thank you.
As this seems like as good a place as any for Ubuntu packaging of wine - do you see any fix in the future for gstreamer support on Wine when compiling on 64-bit Ubuntu? The current Wine configure script (quite correctly) disables support because the installed glibconfig.h includes type definitions correct for 64-bit compilation for incorrect for 32-bit compilation. ia32-libs doesn't contain header files and there is no other package that can provide the 32-bit header. Perhaps proper multilib support in the upcoming 11.10 provides a solution?
Alex
On Thu, Sep 1, 2011 at 3:05 PM, Alex Bradbury asb@asbradbury.org wrote:
As this seems like as good a place as any for Ubuntu packaging of wine
- do you see any fix in the future for gstreamer support on Wine when
compiling on 64-bit Ubuntu? The current Wine configure script (quite correctly) disables support because the installed glibconfig.h includes type definitions correct for 64-bit compilation for incorrect for 32-bit compilation. ia32-libs doesn't contain header files and there is no other package that can provide the 32-bit header. Perhaps proper multilib support in the upcoming 11.10 provides a solution?
One way to do this is setup an i386 chroot (using debootstrap + schroot) and use that to build 32-bit wine. I used this setup to test the gstreamer patch and it works without a glitch. See [1] for more info.
Multiarch support already kind of works in current Ubuntu (11.04), though not that excellent and it's not yet enabled by default. Haven't tried installing glib-dev using that, but I'm guessing that even if it did work pkgconfig most likely won't know about it, so we would have the wrong -I flags output from the configure script (because there is no way for us to specifically ask pkgconfig for a certain architecture).
Anyway, what do you use gstreamer for or what applications use it? I'm the one that "broke it", but to be honest I based my assessment that it was already broken just by reading the code, not by actually testing it with an application.
Octavian
On 09/01/2011 05:05 AM, Alex Bradbury wrote:
On 1 September 2011 10:50, Scott Ritchie scott@open-vote.org wrote:
For an easier user testing experience, you can now install the latest git as a convenient Ubuntu package.
This seems very handy, thank you.
As this seems like as good a place as any for Ubuntu packaging of wine
- do you see any fix in the future for gstreamer support on Wine when
compiling on 64-bit Ubuntu? The current Wine configure script (quite correctly) disables support because the installed glibconfig.h includes type definitions correct for 64-bit compilation for incorrect for 32-bit compilation. ia32-libs doesn't contain header files and there is no other package that can provide the 32-bit header. Perhaps proper multilib support in the upcoming 11.10 provides a solution?
Alex
I'll work on this for Oneiric beta, after I'm done with that it's possible I can backport it to Natty but no guarantees.
Thanks, Scott Ritchie
On 1 September 2011 11:50, Scott Ritchie scott@open-vote.org wrote:
The packages are versioned like wine1.3-1.3.27+daily-20110901.
Limitations: The major version number is based on the latest released version of the Ubuntu packages, so on release days you might see something like 1.3.27+daily-20110909 which would actually be equivalent 1.3.28. If I get especially behind and don't update the official packages after Monday, you might even see a "1.3.27+daily" that's actually ahead of 1.3.28.
I don't use Ubuntu, so this doesn't really affect me, but can't you use the output from "git describe" for the version?
On 09/01/2011 05:21 AM, Henri Verbeet wrote:
On 1 September 2011 11:50, Scott Ritchie scott@open-vote.org wrote:
The packages are versioned like wine1.3-1.3.27+daily-20110901.
Limitations: The major version number is based on the latest released version of the Ubuntu packages, so on release days you might see something like 1.3.27+daily-20110909 which would actually be equivalent 1.3.28. If I get especially behind and don't update the official packages after Monday, you might even see a "1.3.27+daily" that's actually ahead of 1.3.28.
I don't use Ubuntu, so this doesn't really affect me, but can't you use the output from "git describe" for the version?
Unfortunately I have to use Launchpad Recipe's supported substitution variables here, and while they do have one for the latest git-tag if I build locally this doesn't work on launchpad itself. The reason for this is that the launchpad recipe builders don't have git proper, but instead rely on bzr-git imports (the package is actually building off the launchpad bzr import of the Wine git tree merged with my packaging bzr branch).
Yeah it's a bit lame, and I'll raise the issue with the launchpad folks when I see them next, but it's a pretty minor problem atm.
Thanks, Scott Ritchie
On Thu, Sep 1, 2011 at 8:43 PM, Scott Ritchie scott@open-vote.org wrote:
Unfortunately I have to use Launchpad Recipe's supported substitution variables here, and while they do have one for the latest git-tag if I build locally this doesn't work on launchpad itself. The reason for this is that the launchpad recipe builders don't have git proper, but instead rely on bzr-git imports (the package is actually building off the launchpad bzr import of the Wine git tree merged with my packaging bzr branch).
Yeah it's a bit lame, and I'll raise the issue with the launchpad folks when I see them next, but it's a pretty minor problem atm.
Hello,
Is there any good ways to get the git-describe-like version number from the daily build ppa version number? That's useful while running a regression test. For example, I'd like to know exactly what is wine1.3_1.3.28+daily-20110912 in http://bugs.winehq.org/show_bug.cgi?id=28450 .
Thanks!
On Tue, Sep 20, 2011 at 9:27 PM, Qian Hong fracting@gmail.com wrote:
Is there any good ways to get the git-describe-like version number from the daily build ppa version number? That's useful while running a regression test. For example, I'd like to know exactly what is wine1.3_1.3.28+daily-20110912 in http://bugs.winehq.org/show_bug.cgi?id=28450 .
I'm guessing daily builds are done after daily commits, so you could use the build id (which is just a prefix of the last commit id) from here [1].
In your case, it's probably 9b729bb1b348 - 12-Sep-2011 15:45.
Octavian
On Tue, Sep 20, 2011 at 11:48, Octavian Voicu octavian.voicu@gmail.com wrote:
On Tue, Sep 20, 2011 at 9:27 PM, Qian Hong fracting@gmail.com wrote:
Is there any good ways to get the git-describe-like version number from the daily build ppa version number? That's useful while running a regression test. For example, I'd like to know exactly what is wine1.3_1.3.28+daily-20110912 in http://bugs.winehq.org/show_bug.cgi?id=28450 .
I'm guessing daily builds are done after daily commits, so you could use the build id (which is just a prefix of the last commit id) from here [1].
In your case, it's probably 9b729bb1b348 - 12-Sep-2011 15:45.
Octavian
Or use 'git describe', which will also contain the wine version/number of commits since that version. E.g., today's is: wine-1.3.28-421-gb615335
and the sha1 hash is b6153354dd28c57fb1f92f85df1f1ba751794fc1.
On Wed, Sep 21, 2011 at 2:48 AM, Octavian Voicu octavian.voicu@gmail.com wrote:
I'm guessing daily builds are done after daily commits, so you could use the build id (which is just a prefix of the last commit id) from here [1].
In your case, it's probably 9b729bb1b348 - 12-Sep-2011 15:45.
Octavian
Thanks Octavian, this tip helps a lot. Thanks Austin all the same ;)
-
Alex Bradbury -
Austin English -
Henri Verbeet -
Octavian Voicu -
Qian Hong -
Scott Ritchie