Comment 16 for bug 1558857

On 11 April 2016 at 12:04, Serge Hallyn <email address hidden> wrote:

> Quoting Thiago Martins (<email address hidden>):
> > Guys,
> >
> > I'm curious about this...
> >
> > * Mesa will be upgraded from 11.1, to 11.2... Big changes...
> >
> > * MySQL just got upgraded from 5.6, to 5.7!
> >
> > * APT was upgraded from 1.2.5, to 1.2.7...
> >
> > All very recent upgrades that just happened on Xenial...
> >
> > So, why this big resistance to upgrade Libvirt from 1.3.1, to 1.3.2?
> > Most recent Libvirt 1.3.3 is already on Debian!
>
> And not building.
>
> > https://tracker.debian.org/pkg/libvirt
> >
> > Anyway, I'm just curious about why Libvirt can not receive a last
> > minute update, while many other packages can! Why is that?
>
> Because there is no good reason to do so, and the current version
> seems to be working well. We were open to it and considered it.
> If debian had 1.3.2 packaged we probably would have merged it,
> but we didn't want to risk having different .orig tarballs.
> If 1.3.3 (was stable and) had great benefits, we would consider
> merging it. But finalfreeze is now 3 days away.

Thanks for your reply Serge!