On 13/08/2019 22:02, YOUNG, MICHAEL A. wrote:
> I have been looking at the pygrub code to see if it is possible to cope
> with grub files with BLSCFG and spotted this minor issue in GrubConf.py
> where the code intends to replace ${saved_entry} and ${next_entry} with 0
> but doesn't succeed.
>
>
I've had a tinker with the patch - I don't have a Fedora build system
atm - so I just edited the file on the Dom0 and removed the pyc/pyo
files. Same issue:
pyGRUB version 0.6
┌┐
│ Fedora (5.2.6-200.fc30.x86_64) 30 (Th
On Tue, 13 Aug 2019, Andrew Cooper wrote:
> On 13/08/2019 22:02, YOUNG, MICHAEL A. wrote:
>> I have been looking at the pygrub code to see if it is possible to cope
>> with grub files with BLSCFG and spotted this minor issue in GrubConf.py
>> where the code intends to replace ${saved_entry} and ${
On 13/08/2019 22:02, YOUNG, MICHAEL A. wrote:
> I have been looking at the pygrub code to see if it is possible to cope
> with grub files with BLSCFG and spotted this minor issue in GrubConf.py
> where the code intends to replace ${saved_entry} and ${next_entry} with 0
> but doesn't succeed.
>
>
I have been looking at the pygrub code to see if it is possible to cope
with grub files with BLSCFG and spotted this minor issue in GrubConf.py
where the code intends to replace ${saved_entry} and ${next_entry} with 0
but doesn't succeed.
Signed-off-by: Michael Young
From a08eff9b1b881dc61f94
