[build2] Set RPM epoch

Paul Stath PStath at jmawireless.com
Tue Jun 3 22:14:59 UTC 2025


I need to set the epoch when I package a build2 project as an RPM.

Assume the manifest file contains "version: 1.2.3".
When I use the "bpkg bindist -keep-output <project>" command to build the RPM files,
the resulting spec file contains the expected "Version: 1.2.3" line.
It does not have an "Epoch:" line.  (Which is what I expect.)

To set the epoch, I added the  "fedora-version" to the project manifest file ("fedora-version: 1:1.2.3")
Regenerate the RPM files using the "bpkg bindist -wipe-output -keep-output <project>" command.
I expected this to result in the "Epoch:" line being added to the generated spec file, but no such luck.

Also, can the "fedora-version" attribute in the package manifest file use the bpkg "version"?
Since all I want to do is set the epoch of the RPM, is it possible to specify the "fedora-version" attribute in a DRY fashion so that it uses the bpkg "version" ?
Something like:   "fedora-version: 1:$version"   or "fedora-version: 1:"

Thanks

----
Paul Stath
Principal Systems Engineer
JMA Wireless
pstats at jmawireless.com


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.build2.org/archives/users/attachments/20250603/12ac7619/attachment.html>


More information about the users mailing list