Overview
Request 838529 accepted
Now "osc service disabledrun" does all the magic.
BTW, the rpmlint warning about it not being PIE is because the project hardcodes "-fPIC" as option everywhere.
- Some .spec cleanup:
* Use %autosetup
* Use %find_lang --with-qt
* Remove redundant options to %cmake
* Use %cmake_build
- Use ~git instead of +git to mark it as "before 2.3.0"
- Add _service to generate the tarball and set the version
- Update to version 2.3.0~git20200908.0e0ccde5:
* Delete hublist.eu
* Fix race condition in Search::on
Request History
favogt created request
Now "osc service disabledrun" does all the magic.
BTW, the rpmlint warning about it not being PIE is because the project hardcodes "-fPIC" as option everywhere.
- Some .spec cleanup:
* Use %autosetup
* Use %find_lang --with-qt
* Remove redundant options to %cmake
* Use %cmake_build
- Use ~git instead of +git to mark it as "before 2.3.0"
- Add _service to generate the tarball and set the version
- Update to version 2.3.0~git20200908.0e0ccde5:
* Delete hublist.eu
* Fix race condition in Search::on
13ilya accepted request
Thank you!
1 Now if a more recent commit comes out, what actions should I take to update to it?
2 I understand correctly, if I delete the tar.xz file and click on "Trigger services" (how to do it from osc?) Then it will be recreated automatically from git?
3 What is the compression ratio for xz? If not 9, how can it be set to 9?
4 How can you split the language file into separate packages for each language?
5 That is, I can't do anything about it from the spec-file, am I getting it right? Is PIE something to do with memory addressing in 32-bit systems or is it something else in gcc?
I probably at least need to change the version number in the spec-file, and in the changes-file something to write. Or don't I even need to do that? And also do not you need to specify the hash of the last commit and its date yourself?
The tar_scm service has "changesgenerate" enabled and another service updates the version number in the .spec file. So it's all covered!
The only thing you need to do (which is not really possible to automate in this case) is to update the version number to "2.4.0~git" or whatever after 2.3.0 is released.