[pkg-wine-party] Building wine 1.7.32 using the instructions at pkg-wine.alioth.debian.org

[jre]

Well, I wanted to switch to use git-buildpackage anyway some day. So
here we go:

$ sudo apt-get install git-buildpackage pristine-tar cowbuilder
$ sudo apt-get build-dep wine-development
$ git clone git://git.debian.org/git/pkg-wine/wine.git

$ cd wine
$ ./debian/scripts/import 1.7.32
Edit the version in the commit message to "1.7.32-1~local", save and
close the editor.
Remove "upstream-37406.patch" from debian/patches/series (This patch
only applies to 1.7.29).
$ git commit -a -m "Local work"

Now prepare to build 32-bit packages. (This is all you need if you are
on i386. If you are on amd64, I assume you already added i386 as foreign
arch. Further if you are on amd64 you can build 64-bit packages
*additionally* later on. If you are on another arch I hope you can
figure it out on your own.)

DIST=jessie ARCH=i386 git pbuilder create
gbp buildpackage \
  --git-pbuilder \
  --git-arch=i386 \
  --git-dist=jessie \
  --git-ignore-new \
  --git-upstream-tag=wine-1.7.32

(ignore-new because of the untracked files in .pc).
The build process failed here first, because some debs couldn't be
downloaded. A second run fixed that.

... and you're done, all i386 wine packages built.



On 12/04/2014 12:29 PM, Adam Baxter wrote:> I have checked out
pkg-wine.git and imported the upstream 1.7.32, then
> done some unholy merging to make git-buildpackage recognise it.

Not necessary with above walkthrough. Note though that you end up with
everything on "master". So once the git repository is updated again, you
can't merge easily. I'd recommend therefore to put all your local stuff
in another branch and adapt the gbp command.


> First problem: the page says to use debian/maint/build which doesn't
> seem to exist.

Yes, that are outdated instructions. You'll find that file only in the
wine 1.6 (stable) packaging.


> Second problem: debian/control is actually debian/control.in and I
> can't remember how those templates work. Searching for control.in on
> Google is pointless

d/control is created by d/rules from d/control.in.
After changing between stable and development branch I issue a plain
"./debian/rules". Otherwise no extra work needed here.


> Third problem: git-buildpackage says gbp:error: Can't determine
> upstream version from changelog, I suspect this is because
> debian/control only mentions wine-development

No idea. d/control and d/changelog have to use the same, either wine, or
wine-development.


> I'm tearing my hair out here - can you help?

Sorry, I'm not a hairdresser.


Greets
jre