Paweł, please follow the StableReleaseUpdate process or request a
backport. Both is documented on wiki.ubuntu.com:
http://wiki.ubuntu.com/SRU and http://wiki.ubuntu.com/UbuntuBackports.
I'm closing this particular bug here as "Fix released" (for Hardy).
** Changed in: vzctl (Ubuntu)
Importance
Kir Kolyshkin <[EMAIL PROTECTED]> writes:
> Fixing bug #183774 should also fix this one. So it might make sense to
> make this bug a duplicate of the bug #183774. Not sure how to do in
> launchpad though :(
Unfortunately, syncing the latest version of vzctl 3.0.22 from Debian
will not fix old vzc
Fixing bug #183774 should also fix this one. So it might make sense to
make this bug a duplicate of the bug #183774. Not sure how to do in
launchpad though :(
--
Please apply upstream OpenVZ patch for Upstart issue
https://bugs.launchpad.net/bugs/160409
You received this bug notification because
** Changed in: openvz-tools
Status: Unknown => Fix Released
--
Please apply upstream OpenVZ patch for Upstart issue
https://bugs.launchpad.net/bugs/160409
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs maili
** Also affects: openvz-tools
Importance: Undecided
Status: New
** Changed in: openvz-tools
Importance: Undecided => Unknown
Bugwatch: None => 'Bug tracker at http://bugzilla.openvz.org/' #662
Status: New => Unknown
--
Please apply upstream OpenVZ patch for Upstart issue
The patch was commited by OpenVZ people and it will be available in
vzctl-3.0.19 [3].
I'm going to prepare unofficial package with fixed vzctl for Gutsy users. I
think that
will be useful for them.
[3] http://bugzilla.openvz.org/show_bug.cgi?id=662#c6
--
Please apply upstream OpenVZ patch for
