1 Shed Skin Packaging for Debian
2 ==============================
3
4 Firstly, download the latest upstream source release. Although it might be
5 desirable to get the latest code from the repository, Debian will eventually
6 be using the actual source releases specified in the watch file. Here's how
7 to download using the watch file:
8
9 uscan --force-download --destdir=..
10
11 The --force-download option is required when --download indicates that the
12 package is up-to-date. This will make the necessary symbolic link for the
13 shedskin_0.9.orig.tar.gz archive that must be present when building the
14 package.
15
16 Using the Upstream Repository
17 -----------------------------
18
19 One can also try and persuade Gitorious to yield a file by visiting the
20 following address:
21
22 http://gitorious.org/shedskin/mainline/archive-tarball/30ac2af
23
24 The digest string can be replaced with a tag:
25
26 http://gitorious.org/shedskin/mainline/archive-tarball/0.9
27
28 The idea is then to combine the snapshot with this packaging infrastructure.
29
30 Unpack the archive:
31
32 cd ..
33 tar zxf shedskin-mainline-30ac2af.tar.gz
34 mv shedskin-mainline shedskin_0.9
35
36 Make a copy of the archive for Debian non-native packaging purposes:
37
38 tar zcf shedskin_0.9.orig.tar.gz shedskin_0.9
39
40 Building the Package
41 --------------------
42
43 Move into the sources directory:
44
45 cd shedskin_0.9
46
47 Now, copy the debian directory from this directory into the export directory:
48
49 cp -R ../shedskin-packaging/debian/ .
50
51 There are patches in debian/patches which should be applied when pbuilder is
52 run. These should not need to be applied manually.
53
54 Using pbuilder, try and build the package (this example is using my signing
55 key):
56
57 pdebuild --auto-debsign --debsign-k 9F308B3C
58
59 Add extra options for the first packaging of a new release:
60
61 pdebuild --auto-debsign --debsign-k 9F308B3C --debbuildopts -sa
62
63 This makes sure that the original source archive is produced and referenced in
64 the changes file (used by dput when uploading a package to a Debian package
65 repository/archive).
66
67 For a different distribution:
68
69 pdebuild --auto-debsign --debsign-k 9F308B3C --debbuildopts -sa \
70 -- --distribution squeeze
71
72 Some files will appear in /var/cache/pbuilder/result/ (such as the binary
73 package files), whereas others will appear in the parent directory.
74
75 Uploading the Package
76 ---------------------
77
78 With an appropriate .dput.cf file, the following command can be used to upload
79 package files to the Debian Mentors service:
80
81 dput debexpo /var/cache/pbuilder/result/shedskin_0.9-1_i386.changes
82
83 Maintenance Notes
84 -----------------
85
86 When packaging a new release, update the release history below along with the
87 debian/changelog file:
88
89 debchange -v 0.9-1 -D unstable
90
91 The "-n" part of the version number causes a non-native Debian package to be
92 produced.
93
94 Shed Skin Release History
95 =========================
96
97 Release Git Changeset
98 ------- -------------
99 0.9-1 30ac2afab36d38c0574124ca029e0cd2bfe023ae
100 0.9 31b8214b451d87fae5ec7194a7b4430daa3f49ce
101 0.8-1 d7cf784f5e12952a5630f6b78b3155995c825a38
102 0.8 7f7388c3dfab40dc1776cfd6334dd41bdaa62beb
103 0.7.1 d35a07c99c29618e0dad6d31a3cf01599c0d758a
104 0.7 8fc85b49137a79ca9acc5e63fa9fdfbb50751907
105 0.6 1e6708d49e9092a7949ed74b7e339c5245bb6661
106
107 Release Subversion Revision
108 ------- -------------------
109 0.5 1507
110 0.4 1363
111 0.3-2 1165
112 0.3-1 1165