Skip to content

Issue with the Built-Using packages from the grub-common package in Ubuntu #430

Description

@Taumille

Hello, I'm trying to build an Ubuntu image with Elbe and I am confronted to a problem regarding the Built-Using parameter from Ubuntu archives.
In my specific case, I'm trying to build an Ubuntu Noble image for an x86 platform and so I need the grub-common package but in the Packages.xz (link here) we can see :

[...]
Package: grub-common
Architecture: amd64
Version: 2.12-1ubuntu7
Built-Using: lzo2 (= 2.10-2build3)
[...]

As I understand it, the Built-Using parameter indicates that grub-common has been built using the lzo2_2.10-2build3 package, downloading the package isn't mandatory to run grub-common on the target however, downloading it is a way to comply with the lzo2 license by providing the source code (cf. https://www.debian.org/doc/debian-policy/ch-relationships.html#additional-source-packages-used-to-build-the-binary-built-using).

This is done in elbe with this line

But this particular case creates an issue as the version 2.10-2build3 of lzo2 isn't available anymore in Ubuntu and has been replace with the version 2.10-2build4. Indeed switching the include_built_using variable to False in the code solved the issue.

However I wanted to ask, what is the proper way to solve the issue ? Should I ask the Ubuntu developers to update the grub-common package to use the latest lzo2 build ? Is there an xml parameter in elbe to switch off the downloading of built-using packages ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions