Launchpad itself

Enabling other series in PPA

Asked by Kasper Peeters

My PPA page shows apt.sources lines with intrepid by default, and the packages I have uploaded are also for intrepid. However, I would now like to copy them to Hardy using the 'copy packages' option. This fails, complaining that the binaries are already present for the destination series.

What am I doing wrong? How can I enable the hardy series of my PPA, keeping the intrepid series too?

Cheers,
Kasper

PS. By the way, PPAs are is absolutely great, I wish I had known about them much earlier...

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
Julian Edwards (julian-edwards) said : 		#1

Hi

You have a couple of options open to you.

1. Select "copy binaries" when copying, to use your intrepid binaries in hardy. This may cause problems if they don't work on hardy of course.
2. Re-upload a new version of your source packages targeted to hardy.

The latter is what most users do unless the binary package is not arch-specific. Append ~intrepid1 or ~hardy1 to your package versions to make them unique.

Revision history for this message
Kasper Peeters (kasper-peeters) said : 		#2

> 1. Select "copy binaries" when copying, to use your intrepid
> binaries in hardy. This may cause problems if they don't work on
> hardy of course.

That's almost always the case because of library versions (e.g. I link
against the libgtk2 package but that has different version numbers in
intrepid and hardy).

> 2. Re-upload a new version of your source packages targeted to
> hardy.

The only problem I have with this is that my package _compiles_
and then _runs_ cleanly both on hardy and intrepid. It just links
against different versions of libraries.

So I was expecting an option to copy over the source package and
rebuild for a different distribution, from the same sources. Does that
not exist?

> The latter is what most users do unless the binary package is not arch-
> specific. Append ~intrepid1 or ~hardy1 to your package versions to make
> them unique.

My binary package is not arch specific (it compiles and runs on all
archs), but the binary produced on one arch does not run on
another. What's the best option?

Thanks!

Cheers,
Kasper

Revision history for this message
Christian Reis (kiko) said : 		#3

> So I was expecting an option to copy over the source package and
> rebuild for a different distribution, from the same sources. Does that
> not exist?

Not today. The simple answer is that we don't do rebuilds of sources; one of the problems with that is the unique naming of binaries within the pool. It's a recognized limitation FWIW and it would be cool to fix it, but not today! :)

Can you help with this problem?

Provide an answer of your own, or ask Kasper Peeters for more information if necessary.

To post a message you must log in.