maverick has seen the end of its life and is no longer receiving any
updates. Marking the maverick task for this ticket as Won't Fix.
** Changed in: libvirt (Ubuntu Maverick)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
This bug was fixed in the package libvirt - 0.8.5-0ubuntu5
---
libvirt (0.8.5-0ubuntu5) natty; urgency=low
* Have upstart job source /etc/default/libvirt-bin. This is only a
temporary fix until upstart provides proper default override support
through
** Changed in: libvirt (Ubuntu)
Assignee: Serge Hallyn (serge-hallyn) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/708172
Title:
service libvirt-bin start
+1, Serge.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/708172
Title:
service libvirt-bin start does not set KRB5_KTNAME as required
--
Ubuntu-server-bugs mailing list
** Also affects: libvirt (Ubuntu Maverick)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Maverick)
Importance: Undecided = Medium
** Changed in: libvirt (Ubuntu Maverick)
Status: New = Triaged
--
You received this bug notification because you are a member
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/708172
Title:
service libvirt-bin start
Note this is not actually a regression from lucid. It only looks like
it because the package has both the sysvinit and upstart jobs, and the
sysvinit script sources /etc/default/libvirt-bin while the upstart one
does not. But only the upstart job gets installed in lucid.
So this fix will have
Note that the upstart job says
# If you used to set $libvirtd_opts in /etc/default/libvirt-bin,
# change the 'exec' line here instead.
So Im torn as to whether we should 'fix' the inclusion of /etc/default
/libvirt-bin, or fix the documentation somehow.
If we do want to modify the upstart job,
I like Serge's solution to the problem.
However, I think we should probably bring this question, generically, to
the ubuntu-server@ and ubuntu-devel@ mailing lists, and get a policy
defined for this behavior. In my opinion, we should give server
administrators a smooth mechanism for making minor
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/708172
Title:
service libvirt-bin start does not set KRB5_KTNAME as required
--
Ubuntu-server-bugs mailing list
Thomas, thank you for taking the time to file this bug report and help
us make Ubuntu better!
The upstart job is, indeed, ignoring any settings that used to be set in
/etc/default/libvirt-bin.
Seeing as there is no warning about this in the release notes or
changelog, I think this is a
11 matches
Mail list logo
