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
Though packagers/maintainers should care for NAME and VERSION, RELEASE shall be auto-managed by OBS and ARCHITECTURE is obviously the architecture of the repo build this to guaranty that builded packages will have a higher version than the one builded before. However, we still want a neat release versioning.
For test purpose, we built some packages with increasing <B_CNT> (builds count) (xxx.n.m.OBS.x86_64.rpm). Now the tests are done we need to go back to m=1 for real production.
If we create package from internal OBS, and recreate it, there is no counter reset.
Workaround:
The only way we found to reset the counter was to delete the entire project and recreate it, which is cumbersome.
Feature request:
Could you add an admin command that allow the reset?
The text was updated successfully, but these errors were encountered:
Problem:
We modify packages name builded by obs by adding the following in project configuration:
Release: <CI_CNT>.<B_CNT>.OBS
https://en.opensuse.org/openSUSE:Build_Service_prjconf#Release
Though packagers/maintainers should care for NAME and VERSION, RELEASE shall be auto-managed by OBS and ARCHITECTURE is obviously the architecture of the repo build this to guaranty that builded packages will have a higher version than the one builded before. However, we still want a neat release versioning.
For test purpose, we built some packages with increasing <B_CNT> (builds count) (xxx.n.m.OBS.x86_64.rpm). Now the tests are done we need to go back to m=1 for real production.
If we create package from internal OBS, and recreate it, there is no counter reset.
Workaround:
The only way we found to reset the counter was to delete the entire project and recreate it, which is cumbersome.
Feature request:
Could you add an admin command that allow the reset?
The text was updated successfully, but these errors were encountered: