Thanks, I'll take a look.
On Sun, Oct 21, 2018 at 8:53 AM Niels Thykier wrote:
> Control: tags -1 patch
>
> On Tue, 9 Oct 2018 12:56:11 +0300 Emel Hasdal
> wrote:
> > Yes, I can.
> >
> > I believe the man page may be misleading. In my case, when using the
> --name
> > parameter, it did not wor
Control: tags -1 patch
On Tue, 9 Oct 2018 12:56:11 +0300 Emel Hasdal wrote:
> Yes, I can.
>
> I believe the man page may be misleading. In my case, when using the --name
> parameter, it did not work the way it is stated for the
> main package.
>
> For the following line,
> dh_installsystemd
Yes, I can.
I believe the man page may be misleading. In my case, when using the --name
parameter, it did not work the way it is stated for the
main package.
For the following line,
dh_installsystemd -pnslcd --name=k5start-nslcd k5start-nslcd.service
according to the documentation, it shoul
Hi,
Thanks for the report and sorry for the late reply.
I am glad you figured out a solution. :)
On Fri, 25 May 2018 14:22:49 +0300 Emel Hasdal wrote:
> Well it appears that this is explained in dh_installsystemd man pages:
> *--name=**name*Install the service file as *name.service* instead of
Well it appears that this is explained in dh_installsystemd man pages:
*--name=**name*Install the service file as *name.service* instead of the
default filename, which is the *package.service*. When this parameter is
used, *dh_installsystemd* looks for and installs files named
*debian/package.name.
Tracking down the issue further, I think I have found the culprit and the
workaround.
Here is the full story of my workaround:
I had added the following lines in debian/rules for installing unit files
for a package which is not the main package, pynslcd package in my case,
along with other unit f
6 matches
Mail list logo
