[Pkg-xen-devel] Bug#912441: Bug#912441: xen-utils-4.11: package missing pygrub binaries

[Joshua M. Boniface]

Hi Hans,

On 2018-10-31 12:39 p.m., Hans van Kranenburg wrote:
> tags 912441 + pending
> thanks
>
> Hi,
>
> On 10/31/2018 04:44 PM, Joshua M. Boniface wrote:
>> Package: xen-utils-4.11
>> Severity: important
>>
>> Dear Maintainer,
>>
>> We have discovered that the `pygrub` binaries, expected under
>> `/usr/lib/xen-4.11/bin`, are no longer present in the xen-utils-4.11
>> package.
> Thanks for testing the package.
>
> The file is indeed missing, while it should be there.
>
>> Reviewing the source package reveals that the binary is still present
>> under `tools/pygrub/src/pygrub`, however it is not referenced anywhere
>> obvious in the package build configurations, nor is there any changelog
>> indication that it has been moved or removed.
> There's an exclude in debian/rules, which is too broad.
>
> The fix:
> https://salsa.debian.org/xen-team/debian-xen/commit/d4b0d104f158217036c779e2c7f608d659e01f59
>
>  From your comments, I suspect you already grabbed the file from the
> source package to get a working environment again, for now?

I did attempt this, but it looks like there's some other dependencies missing when I do so, for instance:

 > Traceback (most recent call last):
 >  File "/etc/xen/boot/pygrub", line 25, in <module>
 >    import fsimage
 > ImportError: libfsimage.so: cannot open shared object file: No such file or directory

And it looks like the same issue occurs on a rebuild of the packages with the fix applied (took the `apt-get source`, 
modified `rules`).

>> The other files present in that source directory are installed under
>> `/usr/lib/xen-4.11/lib/python/grub`, just not the binary.
>>
>> [...]
> Hans
Thanks,
Joshua