couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noah Slater <>
Subject Re: deb versioned database dirs
Date Sun, 09 Sep 2012 13:40:02 GMT

Sorry for the very late reply (doing some long overdue email sprints).

What did you do about this in the end?

I was the one who designed that scheme for Debian, so I can, at least, let
you know the thinking behind it.

I was concerned about an update to CouchDB breaking, or corrupting, old
data. So, new package versions, obviously, install a fresh CouchDB, and it
is up to you to port the data across.

Now, CouchDB is a lot more stable than it used to be, but we do, still,
have breaking changes from time to time.

How would those be handled by your package?

(Or were you just installing the package, and not hacking on it, in which
case, should we file a bug downstream?)

On Sat, Apr 7, 2012 at 3:52 AM, Randall Leeds <>wrote:

> The deb packaging I pulled from downstream has the following:
> "
> Apache CouchDB is alpha software and still under heavy development. Please
> be
> aware that important areas such as the public API or internal database
> format
> may see backwards incompatible changes between versions.
> ...
> The partitioned database directories are named like this:
>   /var/lib/couchdb/VERSION
> ...
>  -- Sam Bisbee <>  Wed, 11 Nov 2009 23:22:21 -0500
> "
> I'm considering removing this since it seems outdated and reverting to
> the normal directories. What do you all think?
> -Randall


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message