Add RPM specification file #50
Open
+483
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mmerklinger
force-pushed
the
rpm-spec-file
branch
from
b2b5244
to
48e6143
Compare
|
How will the rpm file be used? Will we add a CI job to this repository that builds the package? |
|
No, the package is build on Fedora COPR. In COPR we add a project, which is a RPM repository. In this RPM repository we reference the RPM specification file in this Git repository. From COPR we can request new builds of the package. |
mmerklinger
force-pushed
the
rpm-spec-file
branch
from
48e6143
to
37ac765
Compare
|
It would be probably also good to make the new version check mandatory to pass in the CI pipeline. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a RPM specification file to build the package on Fedora.
python3-nitrokey.specand patchprotobuf.patch.pyproject.tomlandpython3-nitrokey.specare the same.The new CI job needs to run on a Fedora container, because the RPM tools ob Debian don't understand the contained RPM macros. For new releases the version number must be raised in
pyproject.tomlandpython3-nitrokey.spec.