Launchpad itself

Package copy to PPA conflicting across dists.??

Asked by Robert Hardy

Historically I used one PPA per distribution. Apparently this was not best practice as it causes upgrade issues. As a result I'm trying to merge the PPAs.

I tried to copy (without rebuilding and using a dist of Hardy) my Hardy packages including a pigz package into my main Webcon SRP PPA where a Lucid version of pigz already exists. I get this error:

Copying failed of pigz (2.1.6-1ubuntu1) Remove notification
Copied from: Webcon SRP Hardy. Target series: Hardy
pigz 2.1.6-1ubuntu1 in hardy (binaries conflicting with the existing ones)

I also get a Launchpad internal error email with an id OOPS-3b5c8c9653d7e72df96dffd8093d7fd2.

How can I work around this issue?

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
Robert Hardy (rhardy) said : 		#1

As a work around I tried asking to have the Lucid version of pigz rebuilt. Yaah! Another internal error:

Copying failed of pigz (2.1.6-1ubuntu1) Remove notification
Copied from: Webcon SRP. Target series: Hardy
pigz 2.1.6-1ubuntu1 in lucid (same version already has published binaries in the destination archive)

Launchpad encountered an internal error during the following operation: copying a
package. It was logged with id OOPS-cb31a1ac81ea66d91bb39bfacf1c20e9. Sorry for
the inconvenience.

I'm baffled how you are supposed to get packages for more than one distribution in the same PPA if the copies all fail...
Please advise.

Revision history for this message
Curtis Hovey (sinzui) said : 		#2

The oops is exactly the message you are seeing in text.
    CannotCopy: pigz 2.1.6-1ubuntu1 in lucid (same version already has published binaries in the destination archive)

If you cannot copy just the other packages, then rebuild the other packages into lucid. Since pigz is the same version, it cannot be copied, and because it is the same version, it should not be needed to be copied.

Revision history for this message
Robert Hardy (rhardy) said : 		#3

This is silly. I'm going to have to have separate source packages for each distribution with distribution names in the package titles. What a waste of space!

Revision history for this message
William Grant (wgrant) said : 		#4

On 27/10/12 06:15, Robert Hardy wrote:
> This is silly. I'm going to have to have separate source packages for
> each distribution with distribution names in the package titles. What a
> waste of space!

Modern Debian archives use a pool structure, which means a particular
package version can only exist once in a single archive, and can't be
built separately for each series. If your package's binaries can be used
on multiple Ubuntu series without being rebuilt, you can copy *with*
binaries, but if you need them rebuilt then you need a fresh upload.

Revision history for this message
Max Bowsher (maxb) said : 		#5

> This is silly. I'm going to have to have separate source packages
> for each distribution with distribution names in the package titles.
> What a waste of space!

The source packages don't need to (and shouldn't) have different names. They just need to have different versions.

Can you help with this problem?

Provide an answer of your own, or ask Robert Hardy for more information if necessary.

To post a message you must log in.