1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
Debian packaging for python-cyclone
===================================
python-cyclone is managed in a Git repository using git-buildpackage (with
pristine-tar). It follows most of the advice provided by Russ Allbery at:
http://www.eyrie.org/~eagle/notes/debian/git.html
Upstream source handling is a bit complicated because:
* upstream tarballs do not contain all files in their preferred form of
modifications,
* upstream is using Git,
* upstream stores non-free files in their Git repository.
Creating an updated package for a new upstream release goes as:
0. Add a remote with upstream repository if not already done:
$ git remote add github-upstream https://github.com/fiorix/cyclone
1. Fetch new commits from upstream repository:
$ git fetch github-upstream
2. Verify the tag for the new version:
$ git tag -v v$VERSION
3. Create temporary source tarball from upstream tag:
$ git archive --format=tar --prefix=python-cyclone-$VERSION/ v$VERSION |
gzip -c > ../upstream-cyclone-$VERSION.tar.gz
4. Import new upstream tarball using git-import-orig:
$ git-import-orig ../upstream-cyclone-$VERSION.tar.gz --upstream-vcs-tag=v$VERSION -u$VERSION --pristine-tar
5. Hack, improve, update debian/changelog…
6. Build a new package:
$ git-buildpackage
|
