master→sfos3.2: Commits for 0.3.6-release2 (#438)

qml/pages/SettingsPage.qml

@@ -94,7 +94,7 @@ Page {
                 id: searchUnusedSwitch
                 //% "Search for unused repositories"
                 text: qsTrId("orn-unused-repos-switch")
-                //% "Search for unused repositories after removing packages.
+                //% "Search for unused repositories after removing packages."
                 description: qsTrId("orn-unused-repos-switch-descr")
                 checked: Storeman.searchUnusedRepos
             }

rpm/harbour-storeman.changes

@@ -1,4 +1,4 @@
-* Wed Jun 21 2023 olf <[email protected]> - 0.3.6
+* Sun Jul 30 2023 olf <[email protected]> - 0.3.6
 - Omit apparently superfluous processing of `%{version}` for qmake5 in the spec file (#405)
 - Some minor documentation and strings improvements (#428, #429, #430)
 - Cease CI building on git tags matching `test*_` (#430)

rpm/harbour-storeman.spec

@@ -2,7 +2,7 @@
 Name:           harbour-storeman
 Summary:        OpenRepos client application for SailfishOS
 # The <version> tag must adhere to semantic versioning: Among multiple other
-# reasons due to its use for `qmake5` in line 102.  See https://semver.org/
+# reasons due to its use for `qmake5` in line 107.  See https://semver.org/
 Version:        0.3.6
 # The <release> tag comprises one of {alpha,beta,rc,release} postfixed with a
 # natural number greater or equal to 1 (e.g., "beta3") and may additionally be
@@ -14,7 +14,7 @@ Version:        0.3.6
 # build at GitHub and OBS, when configured accordingly; mind the sorting
 # (`adud` < `alpha`).  For details and reasons, see
 # https://github.com/storeman-developers/harbour-storeman/wiki/Git-tag-format
-Release:        release1_%{branch}
+Release:        release2_%{branch}
 # The Group tag should comprise one of the groups listed here:
 # https://github.com/mer-tools/spectacle/blob/master/data/GROUPS
 Group:          Software Management/Package Manager

translations/README.md

@@ -25,7 +25,7 @@ export LANG=sv; harbour-storeman
 
 ### Updating the source `.ts` file with source strings from source code 
 
-Developers and release managers can use the `lupdate` process, either from [within Qt Linguist](https://doc.qt.io/qtcreator/creator-editor-external.html) or directly [at the command line](https://doc.qt.io/qt-5/linguist-manager.html), or tediously perform this manually, which hence is only suitable for small changes.
+Developers and release managers can use the `lupdate` process, either from [within Qt Linguist](https://doc.qt.io/qtcreator/creator-editor-external.html) or directly [at the command line](https://doc.qt.io/qt-5/linguist-manager.html) (mind to [include all files with translatable strings](https://github.com/storeman-developers/harbour-storeman/pull/431#issuecomment-1659024529), e.g., by `lupdate qml/ src/ *.desktop -ts translations/harbour-storeman.ts`), or tediously perform this manually, which hence is only suitable for small changes.
 
 ---------------------------------------------
 

translations/translations.pri

@@ -31,6 +31,7 @@ qm.CONFIG   = target_predeps no_link
 QMAKE_EXTRA_COMPILERS += qm
 
 translations.files = $$OUT_PWD/translations/*.qm
-translations.path  = $$PREFIX/share/$$TARGET
+translations.path  = $$PREFIX/share/$$TARGET/translations
+translations.CONFIG += no_check_exist
 
 INSTALLS += translations