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
52
|
General maintenance
This package is maintained in Git via the Alioth pkg-cryptsetup project.
Alioth is used only for repository access control and mailinglist hosting,
not for any of its other features.
This package uses the "3.0 (quilt)" source format.
Importing a new upstream release
Since upstream release 1.7.2, we use cryptographically signed Git release
tags as basis for the Debian cryptsetup package.
To import a new upstream release into our packaging repository, do the
following:
0. Ensure that you have the cryptsetup upstream Git repository available
as a remote in the Git repository where you're doing the packaging
work and it's up to date:
git remote add --tags upstream git+ssh://gitlab.com/cryptsetup/cryptsetup.git
git config remote.upstream.fetch v1_7_x:upstream
1. Update 'upstream' remote
git fetch upstream
2. Determine the release tag corresponding to the new release. At the time
of this wriging, upstream uses tags in the form:
v<version>
where <version> is the version number with periods replaced by under-
scores. E.g. for upstream release '1.7.2', the release tag is 'v1_7_2'.
This convention may change, so double-check with git tag.
3. Validate the gpg signature for this release tag:
git verify-tag <tag>
4. Merge the upstream release tag <tag> into the master branch of your
packaging repository:
git checkout master
git merge <tag>
N. After development and testing, the final packages to be uploaded to
Debian are built and tagged in the repository as follows:
gbp buildpackage --git-tag
-- Jonas Meurer <mejo@debian.org> Wed, 05 Oct 2016 20:57:12 +0200
|
