[Bug 1007433] Re: circular dependency causes zookeeperd to not be running after installation of zookeeperd

2012-06-06 Thread James Page
This bug is certainly 'revealed' by the switch of default Java from 6 to 7. I did a bit of testing around the last few packages needed to support removal of openjdk-6 from main and if I tweak the dependencies for ca- certificates-java to runtime depend on openjdk-7-jre-headless everything starts

[Bug 1007433] Re: circular dependency causes zookeeperd to not be running after installation of zookeeperd

2012-06-06 Thread James Page
@Clint With regards to the two other potential bugs in zookeeper: 1) /var/lib/zookeeper should belong to zookeeper A --no-create-home might help here (or I can make it quiet) - the permissions get set post user creation so they should be correct at runtime. 2) the upstart job should be

[Bug 1007433] Re: circular dependency causes zookeeperd to not be running after installation of zookeeperd

2012-06-04 Thread Brian Murray
** Changed in: apt (Ubuntu) Importance: Undecided = Medium ** Changed in: dpkg (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to zookeeper in Ubuntu. https://bugs.launchpad.net/bugs/1007433

[Bug 1007433] Re: circular dependency causes zookeeperd to not be running after installation of zookeeperd

2012-06-02 Thread Raphaël Hertzog
Clint, where do you see a *circular* dependency? The dependencies that you show are not circular. Also the ordering of package installation is decided by apt and not dpkg, so this is an apt bug if any. ** Also affects: apt (Ubuntu) Importance: Undecided Status: New -- You received

Re: [Bug 1007433] Re: circular dependency causes zookeeperd to not be running after installation of zookeeperd

2012-06-02 Thread Clint Byrum
Excerpts from Raphaël Hertzog's message of 2012-06-02 06:25:02 UTC: Clint, where do you see a *circular* dependency? The dependencies that you show are not circular. Also the ordering of package installation is decided by apt and not dpkg, so this is an apt bug if any. I don't necessarily