Launching xulrunner affects boot time

[Jorge Castro]

Because of bug #421422 currently couchdb launches xulrunner on boot, which affects boot time. Since the packaging fix won't be available for karmic there needs to be a way to figure out how to make couch not affect the boot time for karmic. (See attached bootchart)

[Elliot Murphy (statik)]

This has been fixed, https://code.edge.launchpad.net/~statik/ubuntu/karmic/couchdb/fix-bug427036/+merge/11543

[Elliot Murphy (statik)]

The proposed fixed was rejected with good rationale after discussion both in ubuntu and upstream. I'm working on a new fix that moves everything that was in the couchdb package into the couchb-bin package, and puts only the init script in the couchdb package, and then desktopcouch can depend on couchdb-bin.

[Daniel Holbach (dholbach)]

Ok, I'll unsubscribe the sponsors team until then! Thanks a lot Elliot!

[Elliot Murphy (statik)]

chad is finishing up the diff for couchdb that goes along with these other three changes. chef-server and chef-slice were deliberately not changed, they should still depend on couchdb rather than couchdb-bin.

[Steve Langasek (vorlon)]

A few tweaks needed to the package:

- couchdb-bin needs to replace the previous couchdb package, for smooth upgrades
- /etc/default/couchdb is a config file for use by the init script, so should be in the couchdb package
- ${couchdb-bin:Depends} is not declared anywhere - and there's no reason to use a substitution, anyway. This should be a hard-coded dependency ( Depends: couchdb-bin (= ${binary:Version}) ), no reason to invent a new substitution.

I've made these three adjustments to the package and am uploading now; thanks for preparing this.

Going forward, I think all the other contents in /var and /etc should also be moved to the couchdb package, since they're only relevant to the system couchdb instance - other users making use of the binaries aren't going to be able to write to these directories, so what's the point of including them without the init script? In particular, having users' individual couchdb instances reading their configuration from /etc/couchdb/, a directory *writable* by the system couchdb user, seems like it would be a potential security problem, so I can't see any reason to want these files without having the full couchdb package installed.

[Launchpad Janitor (janitor)]

This bug was fixed in the package couchdb - 0.10.0~svn813472-0ubuntu2

---------------
couchdb (0.10.0~svn813472-0ubuntu2) karmic; urgency=low

  * Split couchdb into couchdb (to hold only the init) and couchdb-bin
    (to hold everything else). (LP: #427036)

 -- Chad Miller <email address hidden> Wed, 16 Sep 2009 14:12:56 -0400

[Martin Pitt (pitti)]

Thanks, Chad! I NEWed the package, so it will be in the archive in 1.5 hours.

Now desktopcouch needs to update its dependency to -bin.

[Martin Pitt (pitti)]

I agree to Steve's concerns about /var/ and /etc/, as I also said on the merge proposal. But they can be moved back later.

[Launchpad Janitor (janitor)]

This bug was fixed in the package desktopcouch - 0.3.1-0ubuntu2

---------------
desktopcouch (0.3.1-0ubuntu2) karmic; urgency=low

  * Depend on couchdb-bin instead of couchdb (LP: #427036)

 -- Elliot Murphy <email address hidden> Wed, 16 Sep 2009 17:32:51 -0400

[Martin Pitt (pitti)]

Both debdiffs uploaded, thanks! Please commit to your branches.

[Launchpad Janitor (janitor)]

This bug was fixed in the package bindwood - 0.2~~rev9-0ubuntu2

---------------
bindwood (0.2~~rev9-0ubuntu2) karmic; urgency=low

  * Depend on couchdb-bin instead of couchdb (LP: #427036)

 -- Elliot Murphy <email address hidden> Wed, 16 Sep 2009 17:25:46 -0400