source: debian-alt/doc/launchpad.txt @ f867a9d

Last change on this file since f867a9d was f867a9d, checked in by zzz <zzz@…>, 4 years ago

Debian: Update launchpad instructions
Add debian build instructions

  • Property mode set to 100644
File size: 5.6 KB
1Instructions to upload to launchpad PPA
3You must have a GPG key already uploaded to the
4usual public key servers, where launchpad can find it.
9- Make a launchpad account
10- Log into launchpad
11- Get your GPG fingerprint (gpg -K --fingerprint)
12- Add your GPG fingerprint at the form on
14- Wait for the encrypted email response
15- Decrypt and click the confirmation link in the email
16- Click confirm on the page
17- Make a PPA, lets call it 'test'
18- OPTIONAL: Go to i2p.packages PPA and copy over existing I2P to your PPA:
19  (select "copy existing binaries")
20    trusty, vivid, wily, xenial
21    not precise (only if building for precise which you probably aren't)
22    not utopic (obsolete, disabled by launchpad)
23- Go to i2p.packages PPA and copy over service-wrapper-java to your PPA.
24  This is required for the build.
25  (select "copy existing binaries")
26    trusty
27    not precise (only if building for precise which you probably aren't)
28    not vivid, wily, xenial (more recent versions 3.5.25-2 or 3.5.26-3 are in official launchpad)
29    not utopic (obsolete, disabled by launchpad)
31- you need the following packages
32  sudo apt-get install devscripts dput dh_systemd
34- check out clean copy of release:
35  mtn co -d -b i2p.i2p i2p.i2p.foobar -r t:i2p-0.9.xx
37Generate files to upload
40- export TZ=UTC
41- cd i2p.i2p.foobar
42- edit debian/changelog to add the release at the top
43  * version MUST be 0.9.XX-1ubuntu1
44    next version for fixes would be 0.9.XX-2ubunutu1
45  * series MUST be trusty
46  * name and email MUST EXACTLY match what's in your GPG keyring
47    or the signing will fail.
48    (or add -kkeyid argument to debuild, which you must do
49     if you want to sign with a subkey)
50    run gpg -K to list your private keys
51- edit debian/control to uncomment libservice-wrapper-java line
52- ant debian-release-tarball
53  this will make a directory ../i2p-0.9.XX-0-xxxxxxxx/
54  and a tarball ../i2p_0.9.XX.orig.tar.bz2
55- cp debian/changelog ../i2p-0.9.XX-0-xxxxxxxx/debian/
56- cd ../i2p-0.9.XX-0-xxxxxxxx/
57- Build the *1ubuntu1* files:
58  If you have NOT done a successful dput for this release yet:
59    debuild -S -sa -kkeyid
60  otherwise, if just fixing up the control files, patches, etc:
61    debuild -S -sd -kkeyid
62  (note: no space allowed in -kkeyid)
63- If patches fail, you must fix them up, either manually or with quilt
64  (quilt instructions go here)
66- You will now have the following files in ..:
67  i2p_0.9.XX-1ubuntu1.debian.tar.xz
68  i2p_0.9.XX-1ubuntu1.dsc
69  i2p_0.9.XX-1ubuntu1_source.changes
71- And from the copy above:
72  i2p_0.9.XX.orig.tar.bz2
74Upload to launchpad
77- cd ..
78- Upload to launchpad:
79  dput ppa:your-lp-id/your-ppa-name i2p_0.9.XX-1ubuntu1_source.changes
81This will upload the following files:
82  i2p_0.9.XX-1ubuntu1.dsc            (the GPG signature)
83  i2p_0.9.XX-1ubuntu1.debian.tar.xz  (basically the debian/ directory tarball)
84  i2p_0.9.XX-1ubuntu1_source.changes (the changelog text file)
85  i2p_0.9.XX.orig.tar.bz2            (the source tarball)
87Note: If you didn't add your GPG fingerprint to your launchpad account
88way up there above in step 2 or so, the upload will work,
89but you will get no email back, and it will never build or show up on
90the pending-build page.
92Wait for it to build and be published.
93Could be minutes to hours.
95The amd64 build produces one deb:
96   libjbigi-jni (amd64)
97The i386 build produces three debs:
98   i2p-doc (arch-independent), i2p-router (arch-independent), and libjbigi-jni (i386)
99So the build isn't done until both arch builds are complete.
103If it works, copy trusty to vivid, wily, and xenial in your PPA
104  (select "copy existing binaries")
105  Wait a few minutes for that to happen
110Add your PPA following the instructions at http://i2p-projekt.i2p/en/download/debian:
111     sudo apt-add-repository ppa:your-lp-id/your-ppa-name
112     sudo apt-get update
113     sudo apt-get install i2p
114     mv ~/.i2p ~/.i2p-save
115     i2prouter start
116     (test...)
117     stop router
118     sudo dpkg-reconfigure i2p
119     (reconfigure as a service)
120     (i2p should start as a service. test...)
126Then copy trusty, vivid, wily, and xenial from your PPA to the i2p-maintainers PPA
127  (select "copy existing binaries")
128  Copy trusty first and wait for it to be published in i2p-maintainers or the others will fail.
131Creating milestone, release, and uploading files
134You must first create a milestone, then create a release
135and attach it to the milestone.
136Go to
137Down at bottom, click 'create milestone'
138    Name: 0.9.xx (NOT i2p 0.9.xx)
139    Code name: empty
140    Date targeted: Actual release date
141    Tags: empty
142    Summary: empty
143Click 'register milestone'
144Now you are back on
145At your milestone, 'release now'
146    Date released: Actual release date
147    Release notes: empty
148    Changelog: empty
149Click 'create release'
150Now you on the page for that milestone
151Click 'add download file'
152For each of the four files
153    i2psource_0.9.xx.tar.bz2
154      Description: I2P 0.9.xx Source Code
155      Sig: i2psource_0.9.xx.tar.bz2.sig
156      File Content Type: Code Release Tarball
157    i2pinstall_0.9.xx_windows.exe
158      Description: I2P 0.9.xx Installer for Windows
159      Sig: i2pinstall_0.9.xx_windows.exe.sig
160      File Content Type: Installer File
161    i2pinstall_0.9.xx.jar
162      Description: I2P 0.9.xx Installer (Linux / OSX / FreeBSD / Solaris)
163      Sig: i2pinstall_0.9.xx.jar.sig
164      File Content Type: Installer File
166      Description: I2P 0.9.xx Update
167      Sig:
168      File Content Type: Installer File
Note: See TracBrowser for help on using the repository browser.