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 should search for nslcd.k5start-nslcd.service. But this was not the case. It just worked with k5start-nslcd.service file which I have. However, for the non-main packages, the documentation seems to be correct. On Thu, Sep 6, 2018 at 10:42 PM Niels Thykier <[email protected]> wrote: > 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 <[email protected]> > wrote: > > 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.service* instead of the usual > *debian/package.service*. > > Moreover, maintainer scripts are only generated for units that match the > > given *name*. > > > > It is just not obvious from the help that this is only the case for > > packages except for the main package. For the main package, name.service > > seems to work. > > > > > > So, please close this issue. > > > > [...] > Before I close it, could you perhaps mention if there is something we > could do to improve the documentation that would have helped you find > the solution sooner? > > Thanks, > ~Niels >
