[PKG-Openstack-devel] Bug#770706: Bug#770706: Bug#770706: Bug#770706: Bug#770706: Bug#770706: Bug#770706: keystone.service does not start, /var/run/keystone not created

[Thomas Goirand]

On 12/15/2014 04:44 PM, Gaudenz Steinlin wrote:
> I don't see a reason why this should not work, but I wonder why you
> don't just add an override_dh_systemd_enable target wich first uses
> pkgos to generate the service files and then just calls
> dh_systemd_enable. This seems like the more obvious solution to me.

True, I could just have used the override there instead of in the
installinit, however, I'm happy to have dh_systemd_enable to run
"normally" when there's a debian/<something>.service the normal way.

> Having this in a separate target would probably also make it possible to
> build packages without systemd by just not build depending on
> dh-systemd.

I don't see why you would like to do this. The dh-systemd utility is
available in Wheezy backports, and even if the OpenStack packages do
support systemd now, we don't have to use that as init system...

>> This works, then, except for keystone
>> where there's no #DEBHELPER# in the postinst (because I wanted to keep
>> the control of when invoke-rc.d is called, ie after the daemon starts,
>> the admin tenant is created, and the keystone endpoint is registered).
>> This means that for Keystone, we need to manually add what
>> dh_systemd_enable does. Then I've been asking myself what would happen
>> in Wheezy, and it's looking like the only thing that will happen is that
>> it's going to add a dependency on init-system-helpers, which IMO is
>> quite fine, because it's already available from the official
>> wheezy-backports.
> 
> I don't understand the problem you are trying to solve here. Why are you
> not just adding the #DEBHELPER# at the end of the postinst where you
> want it to be? I don't see how the debhelper inserted snippets don't
> give you control over where they are called. But maybe I'm missing
> something.

I just wanted to do things by hand myself for keystone, but all the
other packages have it. Nothing to worry about IMO (the only thing I'm
worried about is the unblock requests ...).

Thomas