source: debian-alt/doc/launchpad.txt @ 6b8cb54

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

Debian: Refresh patch, update docs

  • Property mode set to 100644
File size: 5.7 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- copy debian-alt/(series)/changelog to debian/
43- edit debian/changelog to add the release at the top
44  * version MUST be 0.9.XX-1ubuntu1
45    next version for fixes would be 0.9.XX-2ubunutu1
46  * series MUST be trusty (or precise)
47  * name and email MUST EXACTLY match what's in your GPG keyring
48    or the signing will fail.
49    (or add -kkeyid argument to debuild, which you must do
50     if you want to sign with a subkey)
51    run gpg -K to list your private keys
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- cp debian-alt/(series)/(other files besides changelog) to ../i2p-0.9.XX-0-xxxxxxxx/debian/
57- cd ../i2p-0.9.XX-0-xxxxxxxx/
58- Build the *1ubuntu1* files:
59  If you have NOT done a successful dput for this release yet:
60    debuild -S -sa -kkeyid
61  otherwise, if just fixing up the control files, patches, etc:
62    debuild -S -sd -kkeyid
63  (note: no space allowed in -kkeyid)
64- If patches fail, you must fix them up, either manually or with quilt
65  (quilt instructions go here)
67- You will now have the following files in ..:
68  i2p_0.9.XX-1ubuntu1.debian.tar.xz
69  i2p_0.9.XX-1ubuntu1.dsc
70  i2p_0.9.XX-1ubuntu1_source.changes
72- And from the copy above:
73  i2p_0.9.XX.orig.tar.bz2
75Upload to launchpad
78- cd ..
79- Upload to launchpad:
80  dput ppa:your-lp-id/your-ppa-name i2p_0.9.XX-1ubuntu1_source.changes
82This will upload the following files:
83  i2p_0.9.XX-1ubuntu1.dsc            (the GPG signature)
84  i2p_0.9.XX-1ubuntu1.debian.tar.xz  (basically the debian/ directory tarball)
85  i2p_0.9.XX-1ubuntu1_source.changes (the changelog text file)
86  i2p_0.9.XX.orig.tar.bz2            (the source tarball)
88Note: If you didn't add your GPG fingerprint to your launchpad account
89way up there above in step 2 or so, the upload will work,
90but you will get no email back, and it will never build or show up on
91the pending-build page.
93Wait for it to build and be published.
94Could be minutes to hours.
96The amd64 build produces one deb:
97   libjbigi-jni (amd64)
98The i386 build produces three debs:
99   i2p-doc (arch-independent), i2p-router (arch-independent), and libjbigi-jni (i386)
100So the build isn't done until both arch builds are complete.
104If it works, copy trusty to vivid, wily, and xenial in your PPA
105  (select "copy existing binaries")
106  Wait a few minutes for that to happen
111Add your PPA following the instructions at http://i2p-projekt.i2p/en/download/debian:
112     sudo apt-add-repository ppa:your-lp-id/your-ppa-name
113     sudo apt-get update
114     sudo apt-get install i2p
115     mv ~/.i2p ~/.i2p-save
116     i2prouter start
117     (test...)
118     stop router
119     sudo dpkg-reconfigure i2p
120     (reconfigure as a service)
121     (i2p should start as a service. test...)
127Then copy trusty, vivid, wily, and xenial from your PPA to the i2p-maintainers PPA
128  (select "copy existing binaries")
129  Copy trusty first and wait for it to be published in i2p-maintainers or the others will fail.
132Creating milestone, release, and uploading files
135You must first create a milestone, then create a release
136and attach it to the milestone.
137Go to
138Down at bottom, click 'create milestone'
139    Name: 0.9.xx (NOT i2p 0.9.xx)
140    Code name: empty
141    Date targeted: Actual release date
142    Tags: empty
143    Summary: empty
144Click 'register milestone'
145Now you are back on
146At your milestone, 'release now'
147    Date released: Actual release date
148    Release notes: empty
149    Changelog: empty
150Click 'create release'
151Now you on the page for that milestone
152Click 'add download file'
153For each of the four files
154    i2psource_0.9.xx.tar.bz2
155      Description: I2P 0.9.xx Source Code
156      Sig: i2psource_0.9.xx.tar.bz2.sig
157      File Content Type: Code Release Tarball
158    i2pinstall_0.9.xx_windows.exe
159      Description: I2P 0.9.xx Installer for Windows
160      Sig: i2pinstall_0.9.xx_windows.exe.sig
161      File Content Type: Installer File
162    i2pinstall_0.9.xx.jar
163      Description: I2P 0.9.xx Installer (Linux / OSX / FreeBSD / Solaris)
164      Sig: i2pinstall_0.9.xx.jar.sig
165      File Content Type: Installer File
167      Description: I2P 0.9.xx Update
168      Sig:
169      File Content Type: Installer File
Note: See TracBrowser for help on using the repository browser.