[Pkg-libvirt-maintainers] Bug#730604: Bug#730604: libvirt-bin: Please rename libvirt-bin.service back to libvirtd.service and use symlink or Alias= instead

Laurent Bigonville bigon at debian.org
Wed Nov 27 10:07:03 UTC 2013


Le Wed, 27 Nov 2013 08:08:22 +0100,
Guido Günther <agx at sigxcpu.org> a écrit :

> On Wed, Nov 27, 2013 at 07:36:31AM +0100, Laurent Bigonville wrote:
> > Package: libvirt-bin
> > Version: 1.1.4-1
> > Severity: normal
> > 
> > Hi,
> > 
> > Could you please rename back the libvirt-bin.service systemd service
> > file to libvirtd.service and use a symlink (libvirtd.service ->
> > libvirt-bin.service) or add Alias=libvirt-bin.service in the service
> > file instead.
> 
> I've actually done this already here a couple of weeks ago to reduce
> the upstream diff but didn't get around to test if the upgrade works
> as expected when the unit name changes (since we don't stop the
> service in the preinst). Now that I read the below it was a good idea
> to not upload without proper testing.
> 
> > Other upstream project are expecting the service to be called
> > libvirtd.service and I guess this would be a good idea to not change
> > this expectation in debian.
> > 
> > There was some discussion about using a symlink vs Alias= on the bug
> > #719695, maybe a systemd maintainer could tell us the status of
> > this?
> 
> I wasn't aware of that. So a symlink would be the better solution once
> this is fixed.
> 
> As a interim solution we could add a libvirtd alias if it breaks other
> software.

Well quickly looking at codesearch.debian.net it's only breaking
firewalld (which is not even enabled yet *hint*), so it's not that
urgent I guess

Cheers

Laurent Bigonville



More information about the Pkg-libvirt-maintainers mailing list