You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 21, 2022. It is now read-only.
When we build a package from pinned sources (usually a developer or development branch build), we currently use the version and release from the spec file. This means that, although the package has been built from untagged sources, the resulting package will have same NEVRA as the most recent tagged, released build. We should append some data (derived from git describe) to the version or release (whichever is appropriate) to distinguish a pinned package from a released one. If we format it correctly, this will even allow yum and dnf to upgrade from a release version to a development version, from a development version to another development version, and even from a development version to the next release version.
The text was updated successfully, but these errors were encountered:
When we build a package from pinned sources (usually a developer or development branch build), we currently use the version and release from the spec file. This means that, although the package has been built from untagged sources, the resulting package will have same NEVRA as the most recent tagged, released build. We should append some data (derived from git describe) to the version or release (whichever is appropriate) to distinguish a pinned package from a released one. If we format it correctly, this will even allow yum and dnf to upgrade from a release version to a development version, from a development version to another development version, and even from a development version to the next release version.
The text was updated successfully, but these errors were encountered: