[Bug 1022515] Re: Please sync (sort of) couchdb 1.2.0-1 from Debian unstable
Launchpad Bug Tracker
1022515 at bugs.launchpad.net
Tue Jul 31 03:15:12 UTC 2012
This bug was fixed in the package couchdb - 1.2.0-2ubuntu1
---------------
couchdb (1.2.0-2ubuntu1) quantal; urgency=low
* Merge from Debian unstable (LP: #1022515, LP: #817656):
- fixes ownership of /etc/couchdb. LP: #731272.
* Remaining changes:
- Use pkg-config instead of the js-config script shipped by libmozjs
- debian/rules, debian/control: split couchdb and couchdb-bin
- debian/postinst: renamed to couchdb-bin.postinst
- debian/couchdb-bin.postrm: don't try to delete couchdb system
user/group
* Dropped changes, superseded upstream:
- Backport svn r1039345 from 1.0.3
- debian/patches/couchio-*: patchset from CouchIO to fix U1 replication
over SSL. It's not clear if these were upstreamed, but most of the
source files they applied to no longer exist at all upstream, so if
these are still needed they will need to be redone.
- debian/patches/fix-help2man.patch: dropped, no longer needed
- debian/patches/jquery15-fix.patch: Make Futon work with jQuery 1.5
- debian/patches/moz*.patch: Spidermonkey 1.8.54 patchset
* Dropped changes, included in Debian:
- debian/control - bump standards version
- debian/control - fix lintian error not-binnmuable-all-depends-any
- Build against a proper libmozjs
- Update build-depends/depends/build config (we no longer need the
--with-js build flags)
* Dropped changes, superseded in Debian:
- source/format - mark package as 1.0 format
- change the default permissions on /etc/couchdb to 0775 and files to
0664
[ Jason Gerard DeRose ]
* /etc/couchdb/default.ini and /etc/couchdb/default.d are delivered in the
`couchdb-bin` package and are owned by root
* /etc/couchdb/local.ini and /etc/couchdb/local.d are delivered in the
* The `couchdb-bin` package does not create nor require the "couchdb" user
(this is now done in the `couchdb` package instead). LP: #1007125.
* Added a short sleep delay in couchdb.postrm so couchdb is more likely to
have actually terminated by the time we `deluser couchdb`, which is needed
for `sudo apt-get purge couchdb` to work when couchdb is running
-- Steve Langasek <steve.langasek at ubuntu.com> Tue, 31 Jul 2012 02:04:48 +0000
** Changed in: couchdb (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1022515
Title:
Please sync (sort of) couchdb 1.2.0-1 from Debian unstable
Status in “couchdb” package in Ubuntu:
Fix Released
Bug description:
I'd like to see CouchDB 1.2.0 synced from Debian, but adding in a
couchdb/couchdb-bin split similar to what was done by the desktopcouch
folks for the current Ubuntu 1.0.1 package.
This split is critical for Novacut and Dmedia because otherwise our
users have an unused system-wide CouchDB running for no reason. We've
been maintaining our own newer CouchDB packages in our PPA, and I'd
love to stop doing that.
For more background, I tried to do something similar for CouchDB 1.1.1
in Precise, but didn't make it in time:
https://bugs.launchpad.net/ubuntu/+source/couchdb/+bug/903098
== Current Status ==
I have a debdiff attached, ready for review, and I have test packages for Precise and Quantal in ppa:novacut/daily:
https://launchpad.net/~novacut/+archive/daily
I've found no regressions from the 1.0.1 Ubuntu package. There's still
one nasty issue (also present in 1.0.1) that I hope to resolve, but
haven't yet. The issue is you can't stop the daemon immediately after
installation. For example, this doesn't work:
sudo apt-get install couchdb
sudo /etc/init.d/couchdb stop
But this does work:
sudo apt-get install couchdb
<reboot>
sudo /etc/init.d/couchdb stop
== What needs further testing ==
I don't use system-wide CouchDB on a regular basis, so I need help
testing the `couchdb` side of the split.
In particular, if there is anyone running the 1.0.1 package in a
production setting, I need feedback on whether the permission and
ownership changes I made in /etc/couchdb cause any issues for you
during/after an upgrade to my 1.2.0 package.
== debian/changelog ==
couchdb (1.2.0-1ubuntu1) quantal; urgency=low
* Started with branch of 1.2.0-1 from Debian unstable
* Split into `couchdb-bin` and `couchdb` binary packages as found in Ubuntu,
with goal of keeping delta between Debian and Ubuntu as low as possible
* Changes from how the split is done in Ubuntu:
- /etc/couchdb/default.ini and /etc/couchdb/default.d are delivered in the
`couchdb-bin` package and are owned by root
- /etc/couchdb/local.ini and /etc/couchdb/local.d are delivered in the
`couchdb` package and are owned by the "couchdb" user
- The `couchdb-bin` package does not create nor require the "couchdb" user
(this is now done in the `couchdb` package instead)
* Changes from Debian:
- After couchdb.postinst runs, only /etc/couchdb/local.ini and
/etc/couchdb/local.d are owned by the "couchdb" user, while the rest of
/etc/couchdb remains owned by root
- Patched /etc/init.d/couchdb so /var/run/couchdb is owned by the "couchdb"
user, needed for the init.d script to actually work (var-run.patch)
- Added a short sleep delay in couchdb.postrm so couchdb is more likely to
have actually terminated by the time we `deluser couchdb`, which is needed
for `sudo apt-get purge couchdb` to work when couchdb is running
- Added couchdb-bin.postinst to fix permissions in /etc/couchdb after
upgrading from the couchdb-bin 1.0.1 package
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/couchdb/+bug/1022515/+subscriptions
More information about the Ubuntu-sponsors
mailing list