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
43
44
45
46
47
48
49
50
51
|
Debian packaging for torsocks
=============================
torsocks is managed in a Git repository using git-buildpackage (with
pristine-tar). It follows most of the advices provided by Russ Allbery at:
http://www.eyrie.org/~eagle/notes/debian/git.html
As upstream is using Git, release tags are merged into the 'upstream' branch of the
Debian package repository when importing new tarballs.
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 tor-upstream https://git.torproject.org/torsocks.git
or if using Git over Tor:
$ git remote add tor-upstream http://dccbbv6cooddgcrq.onion/torsocks.git
1. Fetch new commits from upstream repository:
$ git fetch tor-upstream
2. Verify the tag for the new version:
export VERSION="0.2.3"
$ git tag -v ${VERSION}
3. Download and verify the upstream tarball:
$ uscan
4. Import new upstream tarball (e.g. 2.0.0):
$ gbp import-orig ../torsocks-${VERSION}.tar.xz --upstream-vcs-tag=v${VERSION} -u${VERSION} --pristine-tar
5. Hack, improve, update debian/changelog…
6. Build a new package:
$ gbp buildpackage
7. Create a new signed Git tag
$ git tag -s debian/$VERSION-1
8. Push
$ git push origin master && git push origin --tags
|
