launchpad help|
Size: 7444
Comment:
|
Size: 8471
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 124: | Line 124: |
| === Possible upload errors === Note: If your upload appears to succeed but you receive a confusing email response containing the message: * Rejected: Signer has no upload rights at all to this distribution. Not permitted to upload to the RELEASE pocket in a series in the 'CURRENT' state. this means that you forgot to specify your PPA's name on the command-line (that is, the "my-ppa" part). Therefore, your upload was trying to go into the Ubuntu distribution, rather than into a PPA, and you're not authorized to put it there. This is the default behaviour if you omit the PPA name! However, there is a pretty easy (if crude) way to disable this behaviour, by adding these lines to your ~/.dput.cf: [DEFAULT] default_host_main = notspecified [notspecified] fqdn = SPECIFY.A.PPA.NAME incoming = . Now if you omit the PPA name you'll immediately get an error including the text "SPECIFY.A.PPA.NAME", which should jog your memory. |
|
| Line 136: | Line 159: |
DRAFT: this page is a work in progress. Please seek further help or check the wiki index for a complete page on this topic.
Overview
With Launchpad's Personal Package Archives (PPA), you can build and publish binary Ubuntu packages for multiple architectures simply by uploading an Ubuntu source package to Launchpad. Every individual and team in Launchpad gets their own PPA.
Your PPA gives you:
An APT repository of up to 1 gigabyte for material licensed in accordance with the PPA Terms of Use.
- Binary packages built for x86, AMD64 and lpia architectures against Ubuntu.
- A web front-end where Launchpad users can browse and search for your packages.
Before you create your PPA, you need to:
become an Ubuntero (i.e. you must sign the Ubuntu Community Code of Conduct)
have imported your PGP key to your Launchpad account.
Installing and uninstalling software from a PPA is just as easy as installing software Ubuntu's primary archive. This makes it an ideal way to distribute beta versions, daily builds and other versions of your software for testing, without having to ask your testers to compile your software from source.
Activating a PPA
Before you can start using a PPA, whether it's your own or it belongs to a team, you need to activate it. Visit your Launchpad profile page or the team's overview page.
You can only activate your PPA if you have signed the Ubuntu code of conduct.
Installing software from a PPA
PPAs work just like normal Ubuntu archives. You can install software in the usual way - for example, through apt-get or synaptic - and whenever there's an update Ubuntu will prompt you to install it.
![/!\](/moin_static198/lp20/img/alert.png "/!\"){kind=small}
Important: when you install software from a PPA, Ubuntu will warn you that it is unsigned. PPA packages are unsigned because they are not official Ubuntu packages. You should make sure that you're confident in the PPA owner's abilities before you install their packages.
Adding a PPA to your Ubuntu repositories
To install packages from a PPA, you need to tell Ubuntu where to find it. You do this by giving Ubuntu the PPA's URL, which you can find on the PPA's Launchpad page.
Let's take a look at the AWN Testing team's PPA as an example. If you're using the most recent development version of Ubuntu, all you need do is copy these lines in the apt sources.list entries section of the page. For example:
deb http://ppa.launchpad.net/awn-testing/ubuntu intrepid main deb-src http://ppa.launchpad.net/awn-testing/ubuntu intrepid main
If, like most people, you're using another version of Ubuntu - such as the most recent stable version - then you need to select it from the drop-down box. That'll automatically update the URLs you need to copy.
Take a look at the Ubuntu guide to adding extra software repositories to find out how to add those URLs to your local Ubuntu system.
Building your source package
Before you start using your PPA to distribute software, you need to be familiar with building .deb source packages for Ubuntu. The best place to learn how to package for Ubuntu is the Ubuntu packaging guide.
When you're ready to create a package for your PPA, there are a couple of things that work slightly differently to standard Ubuntu packages:versioning and dependencies.
Let's take a look at each in detail.
Versioning
Ubuntu package names are suffixed by the version number of the package. This allows Ubuntu to distinguish newer packages from older ones and so remain up to date.
If you're creating an alternative version of a package already available in Ubuntu's repositories, you should ensure that:
- your package supersedes the official Ubuntu version
- future Ubuntu versions will supersede your package.
To do this, increase the Ubuntu version number and add a suffix of ~ppa''n'' (where ''n` is your package's revision number). For example: you're creating an experimental version of the myapp_1.0.1 package. Your PPA package would be named myapp_1.0.2~ppa1`. Here, the tilde knocks the precedence of the package down to below whatever is in front of it. So, for now this package counts as being a higher version number than myapp_1.0.1 but when Ubuntu releases myapp_1.0.2, it will supersede your PPA version.
Launchpad satisfies your package's Build-Depends using: optionally: other PPAs in Launchpad.
If you want Launchpad to satisfy your package dependencies using one or more other PPAs, follow the Edit dependencies link on your PPA or the team's overview page.
Which debuild options you use depends on whether or not you're creating an alternative version of a package already in the Ubuntu repositories. Alternative version: debuild -S -sd New package with no orig.tar.gz in Ubuntu's repositories: debuild -S -sa
Dput is the tool you use to upload your source package to Launchpad. First, you need to tell dput where to send your package and by what method. To do that, edit ~/.dput.cf to look like this: Change the first line to whatever name you want to use to refer to the source package, while retaining the square brackets. If you're uploading to a team PPA, change the ~your-launchpad-id to your team's Launchpad name. As you might expect, you must be a member of the team before you can upload to its PPA. Next, open a terminal and enter the following: Replace P with the package name and V` with the version number.
Note: If your upload appears to succeed but you receive a confusing email response containing the message: Dependencies
Note: If you're already familiar with uploading to the Ubuntu primary archive, you should note that PPA builds do not have any build dependency restrictions, unlike a build in the primary Ubuntu archive. If you want to build the same package in the primary Ubuntu archive at a later point you may need to revise the package's component and/or pocket. Depending on other PPAs
Building
Note: If you get the error clearsign failed: secret key not available when signing the changes file, use an additional option -k[key_id] when calling debuild. Use gpg --list-keys to get the key ID. Look for a line like "pub 12345/12ABCDEF"; the part after the slash is the key ID. Uploading
[my-ppa]
fqdn = ppa.launchpad.net
method = ftp
incoming = ~your-launchpad-id/ubuntu/
login = anonymous
allow_unsigned_uploads = 0
$ dput my-ppa P_V_source.changes
Possible upload errors
