launchpad help|
Size: 8382
Comment:
|
← Revision 78 as of 2008-09-10 18:52:53 ⇥
Size: 25
Comment: Fix redirect to Packaging/PPA
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| With Launchpad's Personal Package Archives (PPA), you can build and publish binary packages for multiple architectures simply by uploading a source package. Your PPA gives you: * Up to a 1 gigabyte apt repository for material licensed with an [http://opensource.org/licenses/category OSI-approved licence]. * Binaries built for x86 and AMD64 architectures. * A web front-end where Launchpad users can browse and search for your packages. The Personal Package Archives feature is currently in beta. Before you create your PPA, please note that: * Everything in your archive will be deleted automatically when PPA moves from beta to production. * The PPA beta is running in Launchpad's sandbox environment at dogfood.launchpad.net and uses a snapshot of Launchpad's production database from June 2007. * You must be an Ubuntero (i.e. have signed the Ubuntu Community Code of Conduct), a member of the Launchpad Beta Testers team and have uploaded your GPG key all in your user profile in the dogfood environment. {i} '''Important:''' If you are not a member of the Launchpad Beta Testers team in the dogfood environment, email ppa-beta@launchpad.net to request membership. == Checking your account is eligible for a PPA == Before you continue, check that your dogfood Launchpad account is eligible for a PPA. Log into your account on dogfood Launchpad, then see our guides: * [:BecomingAnUbuntero:Becoming an Ubuntero] * [:ImportingYourOpenPGPKey:Importing your OpenPGP key] * [:JoiningLaunchpadBetaTesters:Joining the Launchpad Beta Testers team] == Activating your PPA == '''Step 1:''' Visit your [https://dogfood.launchpad.net/people/+me/ profile page], in dogfood Launchpad, by clicking your name in the top-right corner of the page. attachment:name.png '''Step 2:''' Click '''Activate PPA''' in the ''Actions'' menu, in the left-hand column of the page. attachment:activate-ppa.png '''Step 3:''' Read the terms of service. '''Step 4:''' Enter a description of your PPA, then click '''Add''' if you agree to the terms of service. You are now ready to upload a source package to your PPA. If you are an administrator of a Launchpad team, you can create a team PPA using by following the same steps but clicking '''Activate PPA''' in your team's ''Actions'' menu. == Creating your source package == {i} '''Important:''' This guide does not show you how to create source packages. You should only continue if you are familiar with Debian-based packaging as used by Ubuntu. '''Dependencies:''' Your package's {{{Build-Depends}}} will always be satisfied using: * the latest packages from the PPA you're uploading to * the main Ubuntu archive. '''Versioning:''' By using {{{~ppa<n>}}} in the package version string, you can make sure users of your PPA packages can upgrade to a newer version that might hit the real Ubuntu archive later. '''Step 1:''' Edit {{{~/.dput.cf}}} and add something like: {{{ [my-ppa] fqdn = upload.dogfood.launchpad.net incoming = ~<LP_NAME>/ubuntu/ login = anonymous}}} '''Step 2:''' To upload to a team PPA, such as {{{~phototeam}}}, use something similar to {{{~/.dput.cf}}}: {{{ [phototeam-ppa] fqdn = upload.dogfood.launchpad.net incoming = ~phototeam/ubuntu/ login = anonymous}}} Now you can upload to your PPA or to the {{{phototeam}}}'s PPA (only if you are member of it). '''Step 2:''' Upload signed sources only (no binaries), using: {{{ dput phototeam-ppa <package>_<version>.source.changes }}} '''Step 3:''' As there is no override system, you have to upload you package to the right/desired component. In {{{debian/control}}}, use this syntax {{{Section: universe/devel}}}. '''Step 4:''' Launchpad will give you an ```accepted``` or ```rejected``` upload notification. '''Step 5:''' If the build fails, you will receive a failure notification. If you don't receive a build failure notification, you can check the status of your build by visiting: https://dogfood.launchpad.net/people/+me/+archive/+builds?build_state=all&build_text= == Accessing your archive == The contents of your archive is searchable and browsable using dogfood Launchpad's PPA interface at: https://dogfood.launchpad.net/ubuntu/+ppas Your archive is located at: http://ppa.dogfood.launchpad.net/<LP_NAME>/ {i} '''Note:''' Replace <LP_NAME> with your Launchpad username. To install packages from your archive add the following lines to your {{{/etc/apt/sources.list}}}: {{{ deb http://ppa.dogfood.launchpad.net/<LP_NAME>/ubuntu <development release) main restricted universe multiverse deb-src http://ppa.dogfood.launchpad.net/<LP_NAME>/ubuntu <development release> main restricted universe multiverse }}} == Frequently asked questions == '''Can anybody have a PPA?'''[[BR]] Yes, this service is available to any developer who wants to publish packages of their free software code. You need a Launchpad account, you will also need a GPG key to sign your source code uploads and you will need to accept the Terms of Service [XXX link needed] which include the Ubuntu Code of Conduct. '''Can I publish any software in a PPA?'''[[BR]] This is a free service for free software developers, so at present we will only support uploads of software under a free software or open source license. Please do not publish packages in your PPA which are not redistributable (the basic requirement for packages in Ubuntu). We may make this service available to commercial software developers too, and would be happy to hear from you if you think that would be useful for you. '''What other limitations apply to the PPA service?'''[[BR]] Other than the expectation that packages in your PPA are free software, we do ask that you not abuse the build system with unnecessary builds or automated uploads of large numbers of packages. We will monitor the total amount of build time per user and ask folks to be reasonable in their use of the shared resources in the PPA pool. Developers and teams each start with 1 gigabyte of storage space freely available in their PPA's for source and binary packages. We will not accept uploads of packages that are unmodified from their original source in Ubuntu or Debian, only packages that include your own changes. We ask that people include useful changelogs for each package so that users and other developers can understand what new features they are exploring in their work. Read the [https://dogfood.launchpad.net/people/+me/+ppa-tos PPA Terms of Service] for more information. '''How long are packages published?'''[[BR]] Packages will remain published until either you remove them yourself, or you supersede them with newer versions, or the underlying release of Ubuntu against which they were built becomes obsolete and unmaintained. '''What formats of packages are supported?'''[[BR]] At this stage only .deb packages are supported. If you are interested in building RPM or other package formats, please contact us on the [https://lists.canonical.com/mailman/listinfo/launchpad-users Launchpad users mailing list] to discuss that in more detail! '''How many users can download packages from my PPA?'''[[BR]] There are no limits on the number of users you can point at your PPA. We would encourage you to build communities of users and testers around your PPA, and there are no bandwidth restrictions on downloads from any PPA. '''How many PPAs can I have?'''[[BR]] Each user and team in Launchpad can have a single public PPA. If you want to have different versions of the same package, testing different features or focused on different use cases, then we would encourage you to create a new team and use the PPA for that team. That way, for example, you can have a team of people interested in "server" issues that has one version of the Apache package, and another interested in "workstation" issues that has a different version of the same package, each in a different PPA. Please don't abuse this capability! '''Why are only x86 and amd64 architectures supported?'''[[BR]] We use the Xen virtualisation system for security during the build process, ensuring that each build has a clean build environment and different developers cannot impact on one another's builds accidentally. This technology is only available on x86 and amd64. |
#redirect Packaging/PPA |
