launchpad development|
Size: 986
Comment:
|
Size: 1083
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 19: | Line 19: |
| dch -i | dch -i "Reupload." |
| Line 22: | Line 22: |
| That last command will prompt you to edit the debian changelog. It creates a new entry for you, which is what tells the system that the package has changed and needs re-processing. | That last command will add an entry to the Debian changelog, which is what tells the system that the package has changed and needs re-processing. You can override the name/email that is used by setting the DEBEMAIL environment variable. |
| Line 24: | Line 24: |
| Make sure that the name and email address in the new entry '''exactly match''' a name and email address in your GPG key, or you'll get a debsign error. | debsign (run by debuild below) will attempt to find your GPG key by using the email address in the changelog entry. Alternatively, you can set DEBSIGN_KEYID=yourid in ~/.devscripts. |
Re-Uploading a Package
Here's how to re-upload an existing package to Soyuz on dogfood.
First, make sure you have this in your ~/.dput.cf:
[dogfood] fqdn = dogfood.launchpad.net method = ftp incoming = ubuntu/ login = anonymous allow_unsigned_uploads = 0
On your local machine, run:
apt-get source <package> # (Or obtain in some other way) cd <package-dir> dch -i "Reupload."
That last command will add an entry to the Debian changelog, which is what tells the system that the package has changed and needs re-processing. You can override the name/email that is used by setting the DEBEMAIL environment variable.
debsign (run by debuild below) will attempt to find your GPG key by using the email address in the changelog entry. Alternatively, you can set DEBSIGN_KEYID=yourid in ~/.devscripts.
Then:
debuild -S cd .. dput dogfood <package>.changes
Now, on dogfood:
sudo -u launchpad -i <<EOF /srv/launchpad.net/codelines/current/scripts/process-upload.py -vv -C insecure ../../ubuntu-queue EOF
