[GH-ISSUE #1847] RPM release number is wrong #1105

Closed
opened 2026-02-27 00:02:15 +03:00 by kerem · 2 comments
Owner

Originally created by @sixg0000d on GitHub (Oct 20, 2020).
Original GitHub issue: https://github.com/electerm/electerm/issues/1847

Electerm version:

1.5.7

Operating system(linux, macos, or windows7/8/10?):

Linux

Expected Behavior

The release number of rpm package released may be smaller, more likely to be 1.

Can you reproduce the same behavior in other terminal:

Current Behavior

Possible Solution

Steps to Reproduce

1.Download the rpm package from the release, then:

rpm -qi ./*.rpm

2.it show me

Release: 508

Context (Environment)

Detailed Description

The most of RPM build guide / guideline is guiding us the release number should reset when software is update, like:
https://rpm-packaging-guide.github.io/
https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/#_release_and_post_release_versions

If there is a problem with the package and it is not related to the source code of electerm itself but related to packaging, you can rebuild with same version and increase the release number, it's beneficial to RPM version and upgrade management.

I have tried to build the RPM package follow the README to figure out why the release number is so large, but the package I built locally, twice, the release numbers are 1 .

Suggestions?

The number of times this version of the software was released. Normally, set the initial value to 1%{?dist}, and increment it with each new release of the package. Reset to 1 when a new Version of the software is built.

And the %{?dist} is a rpm macro, the results are like el8, fc32, but it's can only expansions for rpmbuild system, so just ignore that, set release value to 1 each release.

Originally created by @sixg0000d on GitHub (Oct 20, 2020). Original GitHub issue: https://github.com/electerm/electerm/issues/1847 <!--- Provide some basic info --> ## Electerm version: 1.5.7 ## Operating system(linux, macos, or windows7/8/10?): Linux ## Expected Behavior <!--- Tell me what should happen --> The release number of rpm package released may be smaller, more likely to be 1. ## Can you reproduce the same behavior in other terminal: <!--- If same bahavior happens in other terminal, maybe it is supposed to be like this or not a problem of terminal app --> ## Current Behavior <!--- Tell me what happens instead of the expected behavior --> ## Possible Solution <!--- Not obligatory, but suggest a fix/reason for the bug, --> ## Steps to Reproduce <!--- Provide a link to a live example, or an unambiguous set of steps to --> <!--- reproduce this bug. Include code to reproduce, if relevant --> 1.Download the rpm package from [the release](https://github.com/electerm/electerm/releases), then: ``` rpm -qi ./*.rpm ``` 2.it show me ``` Release: 508 ``` ## Context (Environment) <!--- How has this issue affected you? What are you trying to accomplish? --> <!--- Providing context helps us come up with a solution that is most useful in the real world --> ## Detailed Description <!--- Provide a detailed description of the change or addition you are proposing --> The most of RPM build guide / guideline is guiding us the release number should reset when software is update, like: https://rpm-packaging-guide.github.io/ https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/#_release_and_post_release_versions If there is a problem with the package and it is not related to the source code of electerm itself but related to packaging, you can rebuild with same version and increase the release number, it's beneficial to RPM version and upgrade management. I have tried to build the RPM package follow the README to figure out why the release number is so large, but the package I built locally, twice, the release numbers are 1 . ## Suggestions? <!--- Not a bug report, just some thoughts or suggestions? It is totally OK and welcome too --> > The number of times this version of the software was released. Normally, set the initial value to 1%{?dist}, and increment it with each new release of the package. Reset to 1 when a new Version of the software is built. And the `%{?dist}` is a rpm macro, the results are like `el8`, `fc32`, but it's can only expansions for rpmbuild system, so just ignore that, set release value to `1` each release.
kerem 2026-02-27 00:02:15 +03:00
Author
Owner

@zxdong262 commented on GitHub (Oct 26, 2020):

Thank you @sixg0000d I will investigate

<!-- gh-comment-id:716271814 --> @zxdong262 commented on GitHub (Oct 26, 2020): Thank you @sixg0000d I will investigate
Author
Owner

@zxdong262 commented on GitHub (Oct 26, 2020):

Fixed in latest release

<!-- gh-comment-id:716524238 --> @zxdong262 commented on GitHub (Oct 26, 2020): Fixed in latest release
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/electerm#1105
No description provided.