You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by Jason DeRose <ja...@system76.com> on 2013/12/02 13:06:05 UTC
Re: launchpad / couchdb updates
Great!
So I have a lot of experience using Launchpad Source Package Recipes to do daily builds. I tried to set this up a while ago, but was having problems with the git=>bzr VCS import failing.
But it looks like it's working now:
https://code.launchpad.net/~couchdb/couchdb/master
I see you already have a packaging branch here:
https://code.launchpad.net/~couchdb/couchdb/packaging
Is that going to be for stable releases, or for daily builds? We'll need a slightly different debian/ for each because the daily build will have to call ./bootstrap and needs a few extra dependencies.
-Jason
----- Original Message -----
From: "Dave Cottlehuber" <dc...@jsonified.com>
To: "CouchDB Developers" <de...@couchdb.apache.org>
Sent: Thursday, November 28, 2013 2:02:13 PM
Subject: launchpad / couchdb updates
hi folks,
I’ve been given ownership of the launchpad CouchDB site[1], and I’m making a few changes in the hope that we can get nightly builds coming out on LP directly. This may mean dev@ gets some auto-generated emails while I bumble my way through the interface, sorry about that.
The owning “organisation” is ~couchdb[2] which is admin’d by benoitc & myself at the moment.
If you’d like to join in and help speak up, especially if you know what you’re doing wrt to LP :-)
A+
Dave
[1]: https://launchpad.net/couchdb
[2]: https://launchpad.net/~couchdb (see what we did there)
Re: launchpad / couchdb updates
Posted by Jason DeRose <ja...@system76.com>.
Also, this should be a useful recipe example to follow:
# bzr-builder format 0.3 deb-version {debupstream}~bzr{revno}
lp:pyskein
nest-part daily lp:~pyskein/pyskein/packaging debian debian
It pulls debian/ from another branch, I used to use it for pyskein daily builds:
https://code.launchpad.net/~pyskein/+recipe/pyskein-daily
----- Original Message -----
From: "Jason DeRose" <ja...@system76.com>
To: "Dave Cottlehuber" <dc...@jsonified.com>
Cc: "CouchDB Developers" <de...@couchdb.apache.org>
Sent: Monday, December 2, 2013 5:06:05 AM
Subject: Re: launchpad / couchdb updates
Great!
So I have a lot of experience using Launchpad Source Package Recipes to do daily builds. I tried to set this up a while ago, but was having problems with the git=>bzr VCS import failing.
But it looks like it's working now:
https://code.launchpad.net/~couchdb/couchdb/master
I see you already have a packaging branch here:
https://code.launchpad.net/~couchdb/couchdb/packaging
Is that going to be for stable releases, or for daily builds? We'll need a slightly different debian/ for each because the daily build will have to call ./bootstrap and needs a few extra dependencies.
-Jason
----- Original Message -----
From: "Dave Cottlehuber" <dc...@jsonified.com>
To: "CouchDB Developers" <de...@couchdb.apache.org>
Sent: Thursday, November 28, 2013 2:02:13 PM
Subject: launchpad / couchdb updates
hi folks,
I’ve been given ownership of the launchpad CouchDB site[1], and I’m making a few changes in the hope that we can get nightly builds coming out on LP directly. This may mean dev@ gets some auto-generated emails while I bumble my way through the interface, sorry about that.
The owning “organisation” is ~couchdb[2] which is admin’d by benoitc & myself at the moment.
If you’d like to join in and help speak up, especially if you know what you’re doing wrt to LP :-)
A+
Dave
[1]: https://launchpad.net/couchdb
[2]: https://launchpad.net/~couchdb (see what we did there)
Re: launchpad / couchdb updates
Posted by Dave Cottlehuber <dc...@jsonified.com>.
Hi all,
Thanks Jason for your advice (and also the work on trusty).
Idea is to have two builds available:
- daily off master
- stable with current official releases.
The packaging branch contains just the /debian/ packaging files, as this
makes subsequent merging of git or tar.gz in another branch or repo very
straightforward. I've struggled to follow the changes in the debian
packages because of this - can't tell what's couchdb, debian, or ubuntu all
rolled into one.
I think atm we can use branches and tags if required in the packaging
branch for each release, and today I'm trying to see how much smarts can go
into /debian/rules -- afaict its really just a shell script, so we should
be able to handle both stable and daily within this.
Also, http://felipec.wordpress.com/2012/11/13/git-remote-hg-bzr-2/ made my
life much simpler - git locally, talks to bzr on launchpad.
Octavian maybe we can work on this more at couch hack :-)
On 2 December 2013 13:06, Jason DeRose <ja...@system76.com> wrote:
> Great!
>
> So I have a lot of experience using Launchpad Source Package Recipes to do
> daily builds. I tried to set this up a while ago, but was having problems
> with the git=>bzr VCS import failing.
>
> But it looks like it's working now:
> https://code.launchpad.net/~couchdb/couchdb/master
>
> I see you already have a packaging branch here:
> https://code.launchpad.net/~couchdb/couchdb/packaging
>
> Is that going to be for stable releases, or for daily builds? We'll need a
> slightly different debian/ for each because the daily build will have to
> call ./bootstrap and needs a few extra dependencies.
>
> -Jason
>
>
> ----- Original Message -----
> From: "Dave Cottlehuber" <dc...@jsonified.com>
> To: "CouchDB Developers" <de...@couchdb.apache.org>
> Sent: Thursday, November 28, 2013 2:02:13 PM
> Subject: launchpad / couchdb updates
>
> hi folks,
>
> I’ve been given ownership of the launchpad CouchDB site[1], and I’m making
> a few changes in the hope that we can get nightly builds coming out on LP
> directly. This may mean dev@ gets some auto-generated emails while I
> bumble my way through the interface, sorry about that.
>
> The owning “organisation” is ~couchdb[2] which is admin’d by benoitc &
> myself at the moment.
>
> If you’d like to join in and help speak up, especially if you know what
> you’re doing wrt to LP :-)
>
> A+
> Dave
>
> [1]: https://launchpad.net/couchdb
> [2]: https://launchpad.net/~couchdb (see what we did there)
>
>
>