Daniel Pocock
2016-May-14 17:10 UTC
[Pkg-xen-devel] Bug#824341: wheezy-pu: update xen-utils-4.1 with patch to boot jessie/grub2 VMs
Package: release.debian.org Severity: normal Tags: wheezy User: release.debian.org at packages.debian.org Usertags: pu X-Debbugs-CC: pkg-xen-devel at lists.alioth.debian.org If somebody is still running wheezy for their dom0 (host) environment and they are using jessie or other systems with grub2 in their VMs, they can't boot their VM. A rather trivial 1-line fix in the dom0 (host) system fixes the problem. Please advise if the release team would accept an upload to old-stable adding the following 1-line patch: https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;bug=783346;filename=GrubConf.py-jessie.patch;att=1 The bug report with the patch and discussion is: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783346 Note that if people are using XCP, they are stuck on wheezy for their dom0 because XCP was not included[1] in jessie, so they can't solve this issue by simply upgrading the host. Regards, Daniel 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740517
Adam D. Barratt
2016-May-14 17:35 UTC
[Pkg-xen-devel] Bug#824341: wheezy-pu: update xen-utils-4.1 with patch to boot jessie/grub2 VMs
Control: tags -1 + moreinfo On Sat, 2016-05-14 at 19:10 +0200, Daniel Pocock wrote:> If somebody is still running wheezy for their dom0 (host) environment > and they are using jessie or other systems with grub2 in their VMs, they > can't boot their VM. > > A rather trivial 1-line fix in the dom0 (host) system fixes the problem. > > Please advise if the release team would accept an upload to old-stable > adding the following 1-line patch: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;bug=783346;filename=GrubConf.py-jessie.patch;att=1Given that xen-utils-4.1 only exists on architectures that are covered by wheezy-lts, is there a good reason not to handle the change via that route? We're working towards EOLing wheezy now so generally aren't taking new updates. Regards, Adam
Daniel Pocock
2016-May-14 17:47 UTC
[Pkg-xen-devel] Bug#824341: wheezy-pu: update xen-utils-4.1 with patch to boot jessie/grub2 VMs
On 14/05/16 19:35, Adam D. Barratt wrote:> Control: tags -1 + moreinfo > > On Sat, 2016-05-14 at 19:10 +0200, Daniel Pocock wrote: >> If somebody is still running wheezy for their dom0 (host) environment >> and they are using jessie or other systems with grub2 in their VMs, they >> can't boot their VM. >> >> A rather trivial 1-line fix in the dom0 (host) system fixes the problem. >> >> Please advise if the release team would accept an upload to old-stable >> adding the following 1-line patch: >> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;bug=783346;filename=GrubConf.py-jessie.patch;att=1 > > Given that xen-utils-4.1 only exists on architectures that are covered > by wheezy-lts, is there a good reason not to handle the change via that > route? We're working towards EOLing wheezy now so generally aren't > taking new updates. >If I understand the LTS wiki correctly, users don't need to make any extra effort to get the package from LTS, so I think that strategy sounds fine Can anybody else comment, is there any reason not to do it this way? This appears to be the page with LTS instructions for releasing the fix: https://wiki.debian.org/LTS/Development
Possibly Parallel Threads
- Bug#824341: wheezy-pu: update xen-utils-4.1 with patch to boot jessie/grub2 VMs
- Bug#824341: wheezy-pu: update xen-utils-4.1 with patch to boot jessie/grub2 VMs
- Bug#783346: patch for booting Jessie domU with wheezy dom0
- Bug#783346: Bug#783346: patch for booting Jessie domU with wheezy dom0
- Bug#783346: Bug#783346: Bug#783346: patch for booting Jessie domU with wheezy dom0