Skip to content

[RPM Packaging] The format used in 'pyproject.toml' for 'packages' key does not seem to fit standards for RPM build #165

@ArmandBENETEAU

Description

@ArmandBENETEAU

Hello tappy team!

I am working in an organization that is using the TAP format, and in this goal we are building this tappy project as a '.rpm' package.
However since, the last release (v3.2) and especially since the modification of your build method, we are not able to package directly this project.

The good new is that I've found the cause of this issue.

Indeed, in your pyproject.toml file, there is this section:

[tool.hatch.build.targets.wheel]
sources = ["src"]
packages = ["tap"]

And after some tests, it seems that the standard RPM tools[1] used to build a rpm package from a python repository does not always recognize this syntax. Simply changing this section to the following fixes the problem in my case.

[tool.hatch.build.targets.wheel]
sources = ["src"]
packages = ["src/tap"]

I guess it depends on the version of hatchling used, but since it is not explicitly set in your project...
For information the hatchling version I'm using is 1.27.0.

Best regards and have a beautiful day!
Armand.

PS: this issue is also valid for pytest-tap repo!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions