Is anyone available to test this for natty and/or maverick?
--
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/823638
Title:
Please put comment in /etc/default/libvirt-bin or remove it
Verified for maverick-proposed. (defaults file has a warning)
--
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/823638
Title:
Please put comment in /etc/default/libvirt-bin or remove
This bug was fixed in the package libvirt - 0.7.5-5ubuntu27.17
---
libvirt (0.7.5-5ubuntu27.17) lucid-proposed; urgency=low
* debian/libvirt-bin.upstart: add a pre-stop script to shut down running VMs
before the host shuts down. (LP: #350936)
* debian/libvirt-bin.default:
Hello gdahlman, or anyone else affected,
Accepted libvirt into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in
Hello gdahlman, or anyone else affected,
Accepted libvirt into natty-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in
When you say it is fixed in 0.9.2-4ubuntu10 means that this does not get
fixed in 10.04-LTS ? which has libvirt version 0.7.5
--
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/823638
@Jiri,
that message was automatically generated by launchpad when the fixed
package went upstream. The packages to fix this for lucid through natty
are waiting to be accepted into the -proposed queues. Once they show up
there, someone (other than me) will have to confirm that they fix the
issue
Actually,
this was *not* by design. If the /etc/default/libvirt-bin file exists
it is supposed to be sourced. That is supposed to be the case at least
until the upstart config override files are supported.
This was actually a bug. The file must be re-sourced in each upstart
config section.
This bug was fixed in the package libvirt - 0.9.2-4ubuntu10
---
libvirt (0.9.2-4ubuntu10) oneiric; urgency=low
* Source /etc/default/libvirt-bin at the upstart 'start' section (LP: #823638)
-- Serge Hallyn serge.hal...@ubuntu.com Mon, 15 Aug 2011 13:00:41 -0500
** Changed in:
** Also affects: libvirt (Ubuntu Natty)
Importance: Undecided
Status: New
** Description changed:
+ =
+ SRU Justification
+ 1. Impact: changes to /etc/default/libvirt-bin are ignored at start
+ 2. How bug was addressed: change 'exec' section to a script, and
** Changed in: libvirt (Ubuntu Lucid)
Status: New = In Progress
** Changed in: libvirt (Ubuntu Maverick)
Status: New = In Progress
** Changed in: libvirt (Ubuntu Natty)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Thanks, I will add a comment next time the package gets uploaded.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad
** Changed in: libvirt (Ubuntu)
Status: New = Triaged
** Changed in: libvirt (Ubuntu)
Importance: Undecided = Low
--
You received this bug
12 matches
Mail list logo
