Copying of packages does not work for globalplatform ppa

Bug #557647 reported by Karsten Ohme
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
Undecided
Unassigned

Bug Description

Hi,

I tried to copy a package, but it does not work.

The error message ist:

The following source cannot be copied:

    * libglobalplatform6 6.0.0-0ubuntu2 in jaunty (same version already has published binaries in the destination archive)

What I did:

- selected a package
- I have chosen karmic a series
- I also tried intrepid
- Rebuild the copied sources was checked

I have never published something into the destination series, so i do not understand the error.

Karsten

Tags: lp-soyuz
Revision history for this message
Michael Nelson (michael.nelson) wrote :

Hi Karsten,

Sorry, I'd assumed that your binaries *didn't* need to be recompiled for the different series. As outlined here:

https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage#Versioning
{{{
Version numbers must be unique. This has implications if you want to provide packages for multiple Ubuntu series at once:

If your package can be used on different versions of Ubuntu without being recompiled then use the naming scheme already described. When you have successfully uploaded your package to your PPA you can copy the existing binaries to the new series; see Copying packages.

If your package does need to be recompiled to support multiple Ubuntu series, then you should add a suffix of a tilde and the series name to the version number. So a package for the Intrepid Ibex could be named myapp_1.0-1ubuntu3ppa1~intrepid1 and for the Hardy Heron myapp_1.0-1ubuntu3ppa1~hardy1. If you need to release an updated package, increment the ppan suffix. It is important to note that specifying the version name here doesn't change the series that you are targetting; this must still be set correctly as described in the Ubuntu packaging guide's section on the changelog file.
}}}

So if your binaries do need to be recompiled for each series (as it seems), then you will currently need to upload a separate ~karmic version.

Changed in soyuz:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.