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
|
The versions given here should be taken as examples.
Use of the version control system
---------------------------------
You may either create an empty Monotone database
# mtn -d $db db init
or use an existing one.
All work on this package is tracked in the
www.ada-france.org monotone repository.
# upstream_branch=com.adacore.florsist tracks AdaCore tarballs.
# debian_branch=org.debian.libflorist tracks the Debian packaging
Download the branches from the server to your database. The first
time you contact this server, monotone will show its key. You should
check that it matches f8a11727e8983cf9083c08c6a2acaa27e439dd39.
# server=www.ada-france.org
# mtn -d $db pull mtn://$server?$upstream_branch
# mtn -d $db pull mtn://$server?$debian_branch
Recreate the repackaged archive from a tag.
# mtn -d $db checkout -r t:florist-2014 florist-src
# tar caf libflorist_2014.orig.tar.gz florist-src --exclude=_MTN
# rm -fr florist-src
Inspect the unpatched source tree.
# tar xf libflorist_2014.orig.tar.xz
# cd florist-src
# mtn -d $db checkout -r h:$debian_branch .
Build the package
# debuild
Beware that:
- mtn status does not list all changes. Try "mtn list missing", "mtn
list unknown", "mtn list ignored" and "mtn status" to get the
equivalent of "git status".
- Monotone will detect changes outside debian/ caused by patches.
Always "quilt pop -a" when preparing a commit.
-- Nicolas Boulenguez <nicolas@debian.org>, Thu, 28 Apr 2016 01:36:43 +0200
|
