How to publish packages for more than one Ubuntu release?

Asked by Frederik Elwert on 2011-10-02

When I publish packages (via quickly share/release), I want to do so for more than one Ubuntu release, e.g. all versions from lucid onwards.

Currently, the only way I could figure out was to edit the debian/changes file, insert a new release name, and build/push packages the classical way (debuild, dput). This works, but is quite some extra work, and involves the classical packaging techniques without the quickly candy. So is there a way to make quickly publish packages for more than one Ubuntu release?

Question information

Language:
English Edit question
Status:
Answered
For:
Quickly Edit question
Assignee:
No assignee Edit question
Last query:
2011-10-02
Last reply:
2011-12-08
Michael Terry (mterry) said : #1

Run the following command to retarget your quickly project to Ubuntu 10.04 (lucid):

quickly configure target-distribution lucid

Then you should be able to run 'share' or 'release' and get lucid builds.

Unfortunately, you'll have to retarget your project for each Ubuntu release and then do a 'release'. There's no way to say "I want lucid and above".

Jonathan Kossick (j-kossick) said : #2

But when I retarget my project I get the message, that this version is already registered. (I try to release for different Ubuntu versions one by one).

I dealt with this by uploading one release using quickly, and then using launchpads “copy packages” feature to copy the packages to other series. It works quite well, but causes issues when the python version changed in Ubuntu. So I built the initial packages on Lucid for older Ubuntu releases with python 2.6.

Jonathan Kossick (j-kossick) said : #4

Ahh ok this is working. I think it would be a benefit to configure the dependencies additionally but I cant find a way to do this.
I found "quickly configure dependencies" but after running this there is only a empty textfile opening.
Do you found something like this?

"quickly configure dependencies" is used to add additional dependencies that python-mkdebian cannot detect itself. You can use standard debian dependency syntax in that file.

But I don’t know if it is possible to override the automatically extracted dependencies. I’m quite sure it is not possible to override dependencies like the python version, as this uses special variables in the debian/control file which get expanded only at build time.

Jonathan Kossick (j-kossick) said : #6

I don`t understand why there is no way to release to all series at the same time. If I would copie the binaries after release I also have to realease different versions because of the change of the python version after 10.10.

So what is the best way to release to all series without having a lot of work and different version numbers?

Can you help with this problem?

Provide an answer of your own, or ask Frederik Elwert for more information if necessary.

To post a message you must log in.