Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 545828 - app-emulation/libvirt installs systemd service configuration file into wrong directory
Summary: app-emulation/libvirt installs systemd service configuration file into wrong ...
Status: RESOLVED DUPLICATE of bug 546168
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Matthias Maier
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-07 14:16 UTC by Christian Bricart
Modified: 2015-04-17 14:32 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Bricart 2015-04-07 14:16:03 UTC 
the ebuild(s) call:
> systemd_install_serviced "${FILESDIR}"/libvirtd.service.conf libvirtd
which causes the 00gentoo.conf file to be installed into
> /etc/systemd/system/libvirtd.d/00gentoo.conf
                      ^^^^^^^^^^ 
(hence the "libvirtd" parameter to the eclass function)

As the systemd service is named "libvirtd.service", the above override will never match the service..

Trivial fix:
Either omit the (optional second) parameter to the eclass function call or set it to "libvirtd.service"


Reproducible: Always
Comment 1 Matthias Maier gentoo-dev 2015-04-17 14:32:13 UTC 
*libvirt-1.2.13-r1 (17 Apr 2015)
*libvirt-1.2.14-r1 (17 Apr 2015)
*libvirt-1.2.12-r1 (17 Apr 2015)
*libvirt-1.2.11-r4 (17 Apr 2015)
*libvirt-1.2.10-r5 (17 Apr 2015)

  17 Apr 2015; Matthias Maier <tamiko@gentoo.org> +libvirt-1.2.10-r5.ebuild,
  +libvirt-1.2.11-r4.ebuild, +libvirt-1.2.12-r1.ebuild,
  +libvirt-1.2.13-r1.ebuild, +libvirt-1.2.14-r1.ebuild,
  -libvirt-1.2.11-r3.ebuild, -libvirt-1.2.13.ebuild, -libvirt-1.2.14.ebuild,
  libvirt-9999.ebuild:
  Fix install location for libvirtd.service.d/00gentoo file; bug #545828, bug
  #546168

*** This bug has been marked as a duplicate of bug 546168 ***