Yeah, I discovered and tested the above fix already - I just reported
this bug because having a tracking bug is a necessary part of the
stable release update (SRU) process: https://wiki.ubuntu.com/StableReleaseUpdates
> This would also be a good time for Ubuntu to update libguestfs to a
> version that doesn't have known security issues (but is on the same
> stable branch). See my comment here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1194472#c2
In general, new upstream versions (even microreleases) are not
permitted in a stable release update. Rather, only targeted fixes for
specific bugs are permitted. There is an exception process to allow
for micro releases of certain packages, but it does not appear that
libguestfs currently has that approval: https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions
On Tue, Sep 22, 2015 at 12:52 PM, Richard Jones <email address hidden> wrote: /github. com/libguestfs/ libguestfs/ commit/ 101d728e80cce73 b882aac7af45701 3491d03311
> This was fixed a (really) long time ago:
> https:/
Thanks for noticing/replying to this bug!
Yeah, I discovered and tested the above fix already - I just reported /wiki.ubuntu. com/StableRelea seUpdates
this bug because having a tracking bug is a necessary part of the
stable release update (SRU) process:
https:/
> This would also be a good time for Ubuntu to update libguestfs to a /bugzilla. redhat. com/show_ bug.cgi? id=1194472# c2
> version that doesn't have known security issues (but is on the same
> stable branch). See my comment here:
> https:/
In general, new upstream versions (even microreleases) are not /wiki.ubuntu. com/StableRelea seUpdates/ MicroReleaseExc eptions
permitted in a stable release update. Rather, only targeted fixes for
specific bugs are permitted. There is an exception process to allow
for micro releases of certain packages, but it does not appear that
libguestfs currently has that approval:
https:/