I often do upstream releases of my upstream projects that I do on Launchpad, mostly for Apport and jockey. But doing this has been quite tedious until now: You have to go to the project page, pick the series (usually “trunk”), create a new release, create a new milestone along the way, then go to “add download file”, and upload your .tar.gz and .tar.gz.asc.
Because this is rather inconvenient, I don’t do as many upstream releases as I should. But thanks to our tireless launchpadlib developers it is now possible to automate all that, so I wrote a new script lp-project-upload which does all that in a simple command:
$ lp-project-upload apport 1.8.2 apport-1.8.2.tar.gz Release 1.8.2 could not be found for project. Create it? (Y/n) y
The script is based on Brad Crittenden’s recipe for uploading project files, and I added the creation of milestones and releases.
The script is contained in current Karmic’s ubuntu-dev-tools package now. Enjoy, and of course feel free to extend it for changelogs, release notes, etc.
Related posts:
- Nicer Launchpad upstream releases with lp-project-upload A while ago I introduced a script lp-project-upload to automate...
- PostgreSQL security/bug fix update, please test PostgreSQL recently published new point releases which fix the usual...
- lpshell – convenient launchpadlib script These days I often use launchpadlib in my projects for...
Ähnliche Artikel bereitgestellt von Yet Another Related Posts Plugin.
#1 by Jacob Peddicord on 2009/09/05 - 17:14
Zitieren
Sweet. This will definitely make things a lot easier.
#2 by Steve Dodier on 2009/09/05 - 17:38
Zitieren
Impressive. It is possible to upload new files for a release with that ? For instance, i name my release ‘karmic’ and upload new bugfix tarballs for this release. Also, does it create the .asc file ? And is it possible to add a description to the file via your script ?
#3 by martinpitt on 2009/09/05 - 18:24
Zitieren
@Steve:
> It is possible to upload new files for a release with that ?
I’m actually not sure what happens if you try to upload a changed version of a code release tarball for the same release. I hope that Launchpad blocks it, since that’s evil (you should do a new version instead)
> For instance, i name my release ‘karmic’
Don’t. Why not just use standard versioning schemas, like 1.0, 1.1, etc.?
> Also, does it create the .asc file ?
Not right now, but it could. My project specific “do-release” scripts already do that, so I didn’t think about it. But if it’s present, it gets uploaded along.
> And is it possible to add a description to the file via your script ?
Not right now, see announcement. All the optional parameters are missing ATM.
#4 by Dustin Kirkland on 2009/09/08 - 03:49
Zitieren
I am *so* going to use this! Thanks Martin!
#5 by Jonathan Lange on 2009/11/02 - 12:10
Zitieren
Nice! Can I persuade you to add ubuntu-dev-tools to the ‘lpx’ project on Launchpad. We’re trying to get all the Launchpad API stuff together in one big mega-project.
#6 by pitti on 2009/11/04 - 11:53
Zitieren
Hey Jonathan. Sure, done.
Pingback: Nicer Launchpad upstream releases with lp-project-upload « Martin Pitt
#7 by Spomky on 2010/01/07 - 20:50
Zitieren
I have the following error: “Does not support creating releases if more than one series exists.”
!?!!??
#8 by pitti on 2010/01/08 - 09:51
Zitieren
It means by and large what it says: You tried to upload a project which has more than just one series registered in Launchpad. Most projects just have one series (“trunk”), but if you have several, you have to attach the new release to a particular series.
I just didn’t do that yet (mainly due to lack of personal need); patches appreciated, of course.