File: README.source

package info (click to toggle)
ruby-rjb 1.5.5-3
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster, sid
  • size: 704 kB
  • sloc: ansic: 3,859; ruby: 2,604; java: 247; makefile: 35; sh: 3
file content (42 lines) | stat: -rw-r--r-- 1,250 bytes parent folder | download | duplicates (2)
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 rjb
========================

rjb 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/arton/rjb

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=rjb-$VERSION/ v$VERSION |
          gzip -c > ../upstream-rjb-$VERSION.tar.gz

4. Import new upstream tarball using git-import-orig:

    $ gbp import-orig ../upstream-rjb-$VERSION.tar.gz --upstream-vcs-tag=v$VERSION -u$VERSION --pristine-tar

5. Hack, improve, update debian/changelog…

6. Build a new package:

    $ gbp buildpackage