Launchpad itself

Build for multiple distributions

Asked by Karsten Ohme

I just have a simple package and want to upload my sources so that they are build. This also happened, but then I was disappointed, because only the specified distribution in the changelog file was build.

I tried to include multiple distributions in the changelog file but was again disappointed because multiple distribution in the version field are causing an error.

Then I found out that is possible to copy between distributions. But I don't know how this should work, it always complains that something already exists in the target distribution. But this is not true. I have only built binaries in jaunty, not in karmic, so there are no files in karmic. So I was dissappointed again.

Is there a usable way how to get Launchpad working?

I have found autoppa but this is not what I want. I don't want to use a Bazaar system I only want that my sources are built for all possible distributions.

The last solution is now to change the changelog file again and again, replace the version with ~hard ~jaunty ~karmic and so on and create a package for each distribution. Is this pain really necessary?

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Michael Nelson
Solved:
Last query:
Last reply:
Revision history for this message
Best Michael Nelson (michael.nelson) said : 		#1

Hi Karsten (again :) ),

So first, you should certainly be able to copy your packages between different distribution series of the same PPA - what was the exact error you were getting? We did have an issue yesterday which may have affected you (built packages not being published... looking at the code, the copy will fail if there are still unpublished builds in other series).

And secondly, building a package to multiple distroseries is something we are planning to support soon for source package builds (ie. from a bzr branch), but as I understand your comment above, this won't help you :/ (But bug 554621 might be relevant)

So, in short, you should be able to copy your packages the way you tried initially. If you are still unable to do this, please create a bug with the exact error and we'll look into it further.

Revision history for this message
Karsten Ohme (k-o-) said : 		#2

Thanks Michael Nelson, that solved my question.