[go: up one dir, main page]

File: README.source

package info (click to toggle)
txtorcon 24.8.0-1.1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 2,036 kB
  • sloc: python: 17,607; makefile: 227; sh: 34
file content (37 lines) | stat: -rw-r--r-- 1,038 bytes parent folder | download | duplicates (8)
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
Debian packaging for txtorcon
=============================

txtorcon 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 github-upstream https://github.com/meejah/txtorcon.git

1. Fetch new commits from upstream repository:

    $ git fetch github-upstream

2. Verify the tag for the new version:

    $ git tag -v <version>

3. Download and verify the upstream tarball:

    $ uscan

4. Import new upstream tarball (e.g. 0.8):

    $ gbp import-orig ../txtorcon-0.8.tar.gz --upstream-vcs-tag=v0.8 -u0.8 --pristine-tar

5. Hack, improve, update debian/changelog…

6. Build a new package:

    $ gbp buildpackage