systemctl daemon-reload causes message "Failed to connect to bus: No such file or directory"
on fedora the build process of vdr-epg-daemon fails with this message: make install-systemd make[1]: Entering directory '/builddir/build/BUILD/vdr-epg-daemon-1.1.100' cat contrib/epgd.service | sed s:"":"/usr/bin":g | sed s:"":"mariadb.service":g | sed s:"":"/usr/lib64/epgd":g | install -C -D /dev/stdin /builddir/build/BUILDROOT/vdr-epg-daemon-1.1.100-1.fc26.x86_64/usr/lib/systemd/system/epgd.service chmod a+r /builddir/build/BUILDROOT/vdr-epg-daemon-1.1.100-1.fc26.x86_64/usr/lib/systemd/system/epgd.service cat contrib/epghttpd.service | sed s:"":"/usr/bin":g | install -C -D /dev/stdin /builddir/build/BUILDROOT/vdr-epg-daemon-1.1.100-1.fc26.x86_64/usr/lib/systemd/system/epghttpd.service chmod a+r /builddir/build/BUILDROOT/vdr-epg-daemon-1.1.100-1.fc26.x86_64/usr/lib/systemd/system/epghttpd.service systemctl daemon-reload Failed to connect to bus: No such file or directory make[1]: Leaving directory '/builddir/build/BUILD/vdr-epg-daemon-1.1.100' make[1]: *** [Makefile:121: install-systemd] Error 1 make: *** [Makefile:97: install] Error 2 rpm spec file: http://pkgs.fedoraproject.org/cgit/rpms/vdr-epg-daemon.git/tree/vdr-epg-daemon.spec # for now i removed systemctl daemon-reload from Makefile sed -i -e 's|systemctl daemon-reload||' Makefile Is there any other solution ? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: systemctl daemon-reload causes message "Failed to connect to bus: No such file or directory"
On 02/27/2017 10:32 AM, Martin Gansser wrote: on fedora the build process of vdr-epg-daemon fails with this message: make install-systemd make[1]: Entering directory '/builddir/build/BUILD/vdr-epg-daemon-1.1.100' cat contrib/epgd.service | sed s:"":"/usr/bin":g | sed s:"":"mariadb.service":g | sed s:"":"/usr/lib64/epgd":g | install -C -D /dev/stdin /builddir/build/BUILDROOT/vdr-epg-daemon-1.1.100-1.fc26.x86_64/usr/lib/systemd/system/epgd.service chmod a+r /builddir/build/BUILDROOT/vdr-epg-daemon-1.1.100-1.fc26.x86_64/usr/lib/systemd/system/epgd.service cat contrib/epghttpd.service | sed s:"":"/usr/bin":g | install -C -D /dev/stdin /builddir/build/BUILDROOT/vdr-epg-daemon-1.1.100-1.fc26.x86_64/usr/lib/systemd/system/epghttpd.service chmod a+r /builddir/build/BUILDROOT/vdr-epg-daemon-1.1.100-1.fc26.x86_64/usr/lib/systemd/system/epghttpd.service systemctl daemon-reload Failed to connect to bus: No such file or directory make[1]: Leaving directory '/builddir/build/BUILD/vdr-epg-daemon-1.1.100' make[1]: *** [Makefile:121: install-systemd] Error 1 make: *** [Makefile:97: install] Error 2 This is an upstream makefile bug. Preparing an installation tree should not attempt to reload or restart system daemons. In a mock chroot, this does not work because typically, systemd is not running inside the chroot. Florian ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: systemctl daemon-reload causes message "Failed to connect to bus: No such file or directory"
> On 02/27/2017 10:32 AM, Martin Gansser wrote: > > This is an upstream makefile bug. Preparing an installation tree should > not attempt to reload or restart system daemons. In a mock chroot, this > does not work because typically, systemd is not running inside the chroot. > > Florian The developer told me the following: ( https://projects.vdr-developer.org/issues/2476#note-3 ) If you are in normal environment, you get without a reload after systemd always messages that a reload still pending. Is there a flag, for example, 'DO_NOT_RELOAD_INIT_SYSTEM', which is given for the build in an installation tree? Or how do you recognize that you are in an installation tree? Primarily, the "make install" is designed for live environments. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: systemctl daemon-reload causes message "Failed to connect to bus: No such file or directory"
On 02/27/2017 11:49 AM, Martin Gansser wrote: On 02/27/2017 10:32 AM, Martin Gansser wrote: This is an upstream makefile bug. Preparing an installation tree should not attempt to reload or restart system daemons. In a mock chroot, this does not work because typically, systemd is not running inside the chroot. Florian The developer told me the following: ( https://projects.vdr-developer.org/issues/2476#note-3 ) If you are in normal environment, you get without a reload after systemd always messages that a reload still pending. Is there a flag, for example, 'DO_NOT_RELOAD_INIT_SYSTEM', which is given for the build in an installation tree? Or how do you recognize that you are in an installation tree? Primarily, the "make install" is designed for live environments. A set DESTDIR variable should be a good approximation to that. Florian ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: systemctl daemon-reload causes message "Failed to connect to bus: No such file or directory"
> On 02/27/2017 11:49 AM, Martin Gansser wrote:
>
> A set DESTDIR variable should be a good approximation to that.
>
> Florian
You mean something like here: ?
https://github.com/libreswan/libreswan/blob/master/initsystems/systemd/Makefile
installsystemdservice:
@mkdir -p $(SYSTEMDDIR)
$(INSTALL) $(INSTCONFFLAGS) $(SYSTEMDFILE) $(SYSTEMDDIR)
@if test $(SYSTEMDDIR) = ${UNITDIR} ; then \
systemctl --system daemon-reload ; \
fi
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: systemctl daemon-reload causes message "Failed to connect to bus: No such file or directory"
On 02/27/2017 01:16 PM, Martin Gansser wrote:
On 02/27/2017 11:49 AM, Martin Gansser wrote:
A set DESTDIR variable should be a good approximation to that.
Florian
You mean something like here: ?
https://github.com/libreswan/libreswan/blob/master/initsystems/systemd/Makefile
installsystemdservice:
@mkdir -p $(SYSTEMDDIR)
$(INSTALL) $(INSTCONFFLAGS) $(SYSTEMDFILE) $(SYSTEMDDIR)
@if test $(SYSTEMDDIR) = ${UNITDIR} ; then \
systemctl --system daemon-reload ; \
fi
I suppose $(SYSTEMDDIR) (make variable) has DESTDIR applied, but
${UNITDIR} (shell variable) does not? Yes, then this is what I had in mind.
Thanks,
Florian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: systemctl daemon-reload causes message "Failed to connect to bus: No such file or directory"
> On 02/27/2017 01:16 PM, Martin Gansser wrote:
>
> I suppose $(SYSTEMDDIR) (make variable) has DESTDIR applied, but
> ${UNITDIR} (shell variable) does not? Yes, then this is what I had in mind.
>
> Thanks,
> Florian
Problem solved, thanks.
- systemctl daemon-reload
+ ifeq ($(DESTDIR),)
+ systemctl daemon-reload
+ endif
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
