[Pkg-erlang-devel] Couchdb 1.0 and CouchDB package split

Sergei Golovan sgolovan at nes.ru
Fri Jul 16 04:24:56 UTC 2010

Hi Elliot!

On Fri, Jul 16, 2010 at 6:45 AM, Elliot Murphy <elliot at canonical.com> wrote:
> Hi!
> I'd like to make some more progress on the couchdb package, and I'm
> uncertain the best way to proceed, so I'm asking for advice.
> I've committed the package split changes to SVN, asked for feedback
> and so far have none. Should we just go ahead and upload?

I don't want to upload such a big change without Sam's approval. He's
responsible for a couchdb package in Debian.

> I see there is a branch created in SVN order to apply a patch for
> Erlang R14A compatibility, whats the procedure from here to get that
> merged back to trunk?

After R14A was uploaded to unstable couchdb has become broken
(it couldn't start), so I've uploaded a small fix (and merged it to the
trunk). The uploaded package hit testing today, so couchdb is working
again in unstable and testing.

> Finally, since CouchDB 1.0 is out I'd like to get that packaged and
> uploaded, but given the previous two points I'm not sure whats next.

I think that you could prepare 1.0 (with or without split, as you want)
and after Sam's (and later my) review I'll upload it.

> I think maybe this is the way forward: on trunk, I merge in the
> changes Sergei made on the branch. Then I update to version 1.0, test,
> and ask for an upload. Is this right? Should there be a separate
> upload inbetween the package split and the update to 1.0? Thanks for
> your help.

I've already merged changes from R14A compatibility branch to the trunk,
but since 1.0 is compatible itself the patch is to be removed. So, prepare
1.0, let Sam review it, then I'll upload it to the unstable.

Sergei Golovan

More information about the Pkg-erlang-devel mailing list