Bug#888183: libc6: Breaks openvz virtuals again

2018-01-24 Thread James Cloos
> "AJ" == Aurelien Jarno writes: AJ> No, that simply doesn't scale. Other packages than the one in src:glibc AJ> depends on libc6 >= 2.26, and more and more are going to pick up this AJ> dependency in the next months. They might also be unpacked before libc6 AJ> preinst

Bug#888183: libc6: Breaks openvz virtuals again

2018-01-23 Thread Aurelien Jarno
On 2018-01-23 19:56, James Cloos wrote: > AJ> Do you have a list of other packages from the glibc src that are > AJ> upgraded before? > > The following packages have unmet dependencies: > libc-dev-bin : Depends: libc6 (> 2.26) but 2.25-6 is installed > libc6-dev : Depends: libc6 (= 2.26-4) but

Bug#888183: libc6: Breaks openvz virtuals again

2018-01-23 Thread James Cloos
AJ> Do you have a list of other packages from the glibc src that are AJ> upgraded before? The following packages have unmet dependencies: libc-dev-bin : Depends: libc6 (> 2.26) but 2.25-6 is installed libc6-dev : Depends: libc6 (= 2.26-4) but 2.25-6 is installed libc6-i386 : Depends: libc6 (=

Bug#888183: libc6: Breaks openvz virtuals again

2018-01-23 Thread Aurelien Jarno
On 2018-01-23 17:57, James Cloos wrote: > > "AJ" == Aurelien Jarno writes: > > AJ> It's exactly what the message does. It stopped the upgrade and prevented > AJ> libc6 to be unpacked. That way your system is still usable. > > But that is NOT what the message does. The

Bug#888183: libc6: Breaks openvz virtuals again

2018-01-23 Thread James Cloos
> "AJ" == Aurelien Jarno writes: AJ> It's exactly what the message does. It stopped the upgrade and prevented AJ> libc6 to be unpacked. That way your system is still usable. But that is NOT what the message does. The other debs from the glibc source are already

Bug#888183: libc6: Breaks openvz virtuals again

2018-01-23 Thread Aurelien Jarno
On 2018-01-23 17:17, James Cloos wrote: > > "AJ" == Aurelien Jarno writes: > > AJ> This is perfectly normal that you do no get a dialog asking wether you > AJ> want to upgrade libc6, as your kernel is too old for that. > > Not it is not normal. It still should have

Bug#888183: libc6: Breaks openvz virtuals again

2018-01-23 Thread James Cloos
> "AJ" == Aurelien Jarno writes: AJ> This is perfectly normal that you do no get a dialog asking wether you AJ> want to upgrade libc6, as your kernel is too old for that. Not it is not normal. It still should have given that dialog so that I could skip libc and its

Bug#888183: libc6: Breaks openvz virtuals again

2018-01-23 Thread Aurelien Jarno
On 2018-01-23 20:04, cl...@jhcloos.com wrote: > Package: libc6 > Version: 2.26-4 > Severity: important > > [Reporting this from a different box.] > > The latest libc upgrade again breaks openvz virtuals. > > On kvm/xen/bare you get a dialog asking whether you want to upgrade libc. > > On vz

Bug#888183: libc6: Breaks openvz virtuals again

2018-01-23 Thread cloos
Package: libc6 Version: 2.26-4 Severity: important [Reporting this from a different box.] The latest libc upgrade again breaks openvz virtuals. On kvm/xen/bare you get a dialog asking whether you want to upgrade libc. On vz you get a notice about the (un-upgradable) kernel version but not the