[Bug 1022515] Re: Please sync (sort of) couchdb 1.2.0-1 from Debian unstable

[Jason Gerard DeRose]

** Description changed:

- Okay, the saga continues:
+ 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 user
+ 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
  
- This time, I'm proposing (basically) syncing couchdb 1.2.0-1 from Debian
- unstable, but adding my low-delta split into couchdb/couchdb-bin.
+ **Current Status**
  
- The only remaining issue in my package is fixing the /etc/init.d/couchdb
- script, which seems broken in the upstream Apache CouchDB release. Same
- issue seems to effect the Debian package:
+ 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
  
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635534
+ 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 issues is you can't stop the daemon immediately after
+ installation.  For example, this doesn't work:
  
- As far as I can tell, the problem is that /etc/init.d/couchdb doesn't
- correctly handle cases when /var/run is on a tmpfs. The script does an
- `su couchdb` after the /var/run/couchdb directory gets created.
+ 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
+ cause any issues for you during an upgrade.

-- 
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:
  Confirmed

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
  user 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 issues 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 cause any issues for you during an upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/couchdb/+bug/1022515/+subscriptions