Launchpad itself

git-import forces a separate ppa for each version of a repo that needs to be built

Asked by Jason Gross

The https://code.launchpad.net/+code-imports/+new page refuses to let me create multiple imports of the same repo, so all branches that get built are forced to have the same project name. The launchpad uploader refuses to let me upload older "versions" of the same project, which means that each ppa can only build one branch of a given repo. This means that I need to make a separate ppa for each branch that I want to build, and copy over all of the packages needed to do the building. This seems like a design flaw (or an option that I'm missing, somewhere).

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Colin Watson (cjwatson) said : 		#1

No, you just have to use different package names, so a different branch in the same repository for whichever bit of your repository contains debian/ would suffice.

If you absolutely need to publish multiple versions of the same package name concurrently for the same series, then this has nothing to do with code imports, and (unnecessarily) creating multiple imports wouldn't help; it's a fundamental and deliberate limitation of PPAs (partly driven by client-side behaviour). But you don't need to copy over all your build-dependencies; you can use "Edit PPA dependencies" to cause packages in your PPA to include another PPA in sources.list when building.

Can you help with this problem?

Provide an answer of your own, or ask Jason Gross for more information if necessary.

To post a message you must log in.