> 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 vzctl 3.0.16 package for Gutsy. It's still unusable for
Ubuntu OpenVZ HN with Ubuntu OpenVZ VEs.
I think that Ubuntu should build fixed vzctl package for Gutsy
as backport, because it seems that your patch is not a security issue.
Gutsy is still an official stable release of Ubuntu and they will
release Hardy for a few months.
Of course, in my opinion Hardy should include the latest vzctl tool,
it means version 3.0.22 or newer.
Kir Kolyshkin <email address hidden> 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 vzctl 3.0.16 package for Gutsy. It's still unusable for
Ubuntu OpenVZ HN with Ubuntu OpenVZ VEs.
I think that Ubuntu should build fixed vzctl package for Gutsy
as backport, because it seems that your patch is not a security issue.
Gutsy is still an official stable release of Ubuntu and they will
release Hardy for a few months.
Of course, in my opinion Hardy should include the latest vzctl tool,
it means version 3.0.22 or newer.