|
[-]
[+]
|
Changed |
_service:tar_git:sailfishos-chum-gui-installer.changes
|
|
|
|
[-]
[+]
|
Changed |
_service:tar_git:sailfishos-chum-gui-installer.spec
^
|
|
|
|
[-]
[+]
|
Changed |
_service
^
|
| @@ -2,7 +2,7 @@
<service name="tar_git">
<param name="url">https://github.com/sailfishos-chum/sailfishos-chum-gui-installer.git</param>
<param name="branch"/>
- <param name="revision">0.6.2</param>
+ <param name="revision">0.6.3</param>
<param name="token"/>
<param name="debian">N</param>
<param name="dumb">N</param>
|
|
[-]
[+]
|
Changed |
_service:tar_git:sailfishos-chum-gui-installer-0.6.3.tar.gz/.github/workflows/build.yml
^
|
| @@ -1,19 +1,38 @@
-name: CI on SFOS 3.1.0
+name: CI on SDK 3.1.0
on:
push:
tags:
- - '*'
+ # '**' also matches the slash ('/'), in contrast to '*',
+ # see https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet
+ - '**'
pull_request:
branches:
- main
+ # Allows to run this workflow manually from the Actions tab.
+ workflow_dispatch:
+
+defaults:
+ run:
+ # Note that 'bash' provides -o pipefail, in contrast to the default (i.e. unspecified, which also uses bash) or 'sh',
+ # see https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsshell
+ shell: sh
+
+# Do not use concurrency in order to enforce checking every commit of a Pull Request.
+# See, e.g.: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-only-cancel-in-progress-jobs-or-runs-for-the-current-workflow
+#concurrency:
+ #group: ci-${{ github.ref_name }}
+ # 'false' (default) allows for two concurrent runs, one executing and one freshly enqueued; 'true' for only one; no 'concurrency:' defined for multiple.
+ #cancel-in-progress: false
jobs:
build:
runs-on: ubuntu-22.04
env:
+ # Do not wait up to the default of 10 minutes for network timeouts in a workflow which runs ca. 2 minutes.
SEGMENT_DOWNLOAD_TIMEOUT_MINS: 1
steps:
+
- name: Checkout
uses: actions/checkout@v3
@@ -32,6 +51,9 @@
- name: Build i486 on 3.1.0.12
uses: coderus/github-sfos-build@old-stable
with:
+ # Solely build for i486 on 3.1.0, because this is a noarch RPM and i486 matches the architecture of the host (compiling faster than cross-compilation)
+ # and 3.1.0 is the oldest supported release hence with the smallest Docker image to download from Docker hub.
+ # See also https://github.com/sailfishos-patches/patchmanager/pull/437#issuecomment-1615317003
release: 3.1.0.12
arch: i486
@@ -40,3 +62,4 @@
with:
name: RPM-build-results
path: RPMS/
+
|
|
[-]
[+]
|
Changed |
_service:tar_git:sailfishos-chum-gui-installer-0.6.3.tar.gz/.icons/README.md
^
|
| @@ -5,7 +5,7 @@
All available stages of the SVG icon and exported PNGs in various resolutions can be acessed in the [`.icon` directory of the SailfishOS:Chum GUI Installer](https://github.com/sailfishos-chum/sailfishos-chum-gui-installer/tree/main/.icons):
- A preparatory SVG icon with both texts, "Chum" and "Chum GUI", the original text "CHUM" and font examples (all freely licensed) to [choose a font most closely to the original one](https://github.com/sailfishos-chum/sailfishos-chum-gui/issues/132#issuecomment-1365622701): [`sailfishos-chum_combined.svg`](https://github.com/sailfishos-chum/sailfishos-chum-gui-installer/blob/main/.icons/sailfishos-chum_combined.svg)<br />
<sub>Ultimately the font "System-ui", which originally was a preliminary choice, was retained (due to a lack of input).</sub><br />
- <sup>Note that any element (e.g., text) can be easily switched invisible or deleted in any SVG editor.</sup>
+ <sup>Note that any element (e.g. text) can be easily switched invisible or deleted in any SVG editor.</sup>
- A "two in one" SVG icon with both texts, "Chum" and "Chum GUI": [`sailfishos-chum_combined_cleaned.svg`](https://github.com/sailfishos-chum/sailfishos-chum-gui-installer/blob/main/.icons/sailfishos-chum_combined_cleaned.svg)<br />
<sub>Note that either text can be easily switch invisible in any SVG editor to export PNG versions of either icon.</sub>
- Two SVG icons with only a single text retained for minimising the file sizes: [`sailfishos-chum.svg`](https://github.com/sailfishos-chum/sailfishos-chum-gui-installer/blob/main/.icons/sailfishos-chum.svg) & [`sailfishos-chum-gui.svg`](https://github.com/sailfishos-chum/sailfishos-chum-gui-installer/blob/main/.icons/sailfishos-chum-gui.svg)
|
|
[-]
[+]
|
Changed |
_service:tar_git:sailfishos-chum-gui-installer-0.6.3.tar.gz/README.md
^
|
| @@ -2,14 +2,14 @@
**The SailfishOS:Chum GUI Installer performs the initial installation of the [SailfishOS:Chum GUI application](https://github.com/sailfishos-chum/sailfishos-chum-gui#readme). SailfishOS:Chum GUI Installer selects, downloads and installs the correct variant of the SailfishOS:Chum GUI application built for the CPU-architecture of the device and the installed SailfishOS release from the SailfishOS-OBS.**
-The SailfishOS:Chum GUI Installer works on any SailfishOS release ≥ 3.1.0 and all supported CPU-architectures (armv7hl, i486 and aarch64). The current SailfishOS:Chum GUI Installer RPM can be obtained from its ["latest release" page at GitHub](https://github.com/sailfishos-chum/sailfishos-chum-gui-installer/releases/latest), [OpenRepos.net](https://openrepos.net/content/olf/sailfishos-chum-gui-installer) and [the SailfishOS-OBS](https://build.merproject.org/package/show/sailfishos:chum/sailfishos-chum-gui-installer).
+The SailfishOS:Chum GUI Installer works on any SailfishOS release ≥ 3.1.0 and all supported CPU-architectures (armv7hl, i486 and aarch64). The current SailfishOS:Chum GUI Installer RPM can be obtained from [OpenRepos.net](https://openrepos.net/content/olf/sailfishoschum-gui-installer#node-11554), its ["latest release" page at GitHub](https://github.com/sailfishos-chum/sailfishos-chum-gui-installer/releases/latest) and [the SailfishOS-OBS](https://build.merproject.org/package/show/sailfishos:chum/sailfishos-chum-gui-installer).
### Important notes
* If you experience issues with the SailfishOS:Chum GUI Installer, please take a look at its log file `/var/log/sailfishos-chum-gui-installer.log.txt`. If that does not reveal to you what is going wrong, please check first if an issue report describing this issue [is already filed at GitHub](https://github.com/sailfishos-chum/sailfishos-chum-gui-installer/issues), then you might file a new issue report there and attach the log file to it, or enhance an extant bug report.
* If you experience issues when installing, removing or updating packages after a SailfishOS upgrade, try running `devel-su pkcon refresh` in a terminal app.
* When the SailfishOS:Chum GUI Installer fails to install anything (i.e, a minute after installing it the icon of the SailfishOS:Chum GUI application has not appeared on the launcher / desktop), most likely the preceding or the following bullet point is the reason.
-* Before software can be build for a SailfishOS release at the SailfishOS-OBS, Jolla must create a [corresponding "download on demand (DoD)" OBS-repository](https://build.merproject.org/project/subprojects/sailfishos). It may take a little time after a new SailfishOS release is published before the corresponding "DoD" repository is being made available, during which installing the SailfishOS:Chum GUI application by the SailfishOS:Chum GUI Installer or updating the SailfishOS:Chum GUI application by itself on a device with the new SailfishOS release already installed does not work, because the SailfishOS:Chum GUI application cannot be compiled for this new SailfishOS release at the Sailfish-OBS, yet; consequently this is always the case for "closed beta (cBeta)" releases of SailfishOS. In such a situation one has to manually download the SailfishOS:Chum GUI application built for the last prior SailfishOS "general availability (GA)" release (e.g., from [the SailfishOS:Chum repository](https://build.merproject.org/project/show/sailfishos:chum/sailfishos-chum-gui)), then install or update the SailfishOS:Chum GUI application via `pkcon install-local <downloaded RPM file>`, and hope that there is no change in the new SailfishOS release which breaks the SailfishOS:Chum GUI application; if there is, please report that soon at [SailfishOS:Chum GUI application's issue tracker](https://github.com/sailfishos-chum/sailfishos-chum-gui/issues).
+* Before software can be build for a SailfishOS release at the SailfishOS-OBS, Jolla must create a [corresponding "download on demand (DoD)" OBS-repository](https://build.merproject.org/project/subprojects/sailfishos). It may take a little time after a new SailfishOS release is published before the corresponding "DoD" repository is being made available, during which installing the SailfishOS:Chum GUI application by the SailfishOS:Chum GUI Installer or updating the SailfishOS:Chum GUI application by itself on a device with the new SailfishOS release already installed does not work, because the SailfishOS:Chum GUI application cannot be compiled for this new SailfishOS release at the Sailfish-OBS, yet; consequently this is always the case for "closed beta (cBeta)" releases of SailfishOS. In such a situation one has to manually download the SailfishOS:Chum GUI application built for the last prior SailfishOS "general availability (GA)" release (e.g. from [the SailfishOS:Chum repository](https://build.merproject.org/project/show/sailfishos:chum/sailfishos-chum-gui)), then install or update the SailfishOS:Chum GUI application via `pkcon install-local <downloaded RPM file>`, and hope that there is no change in the new SailfishOS release which breaks the SailfishOS:Chum GUI application; if there is, please report that soon at [SailfishOS:Chum GUI application's issue tracker](https://github.com/sailfishos-chum/sailfishos-chum-gui/issues).
* Disclaimer: The SailfishOS:Chum GUI application and its installer may still have flaws, kill your kittens or break your SailfishOS installation! Although this is very unlikely after years of testing by many users, new flaws may be introduced in any release (as for any software). Mind that the license you implicitly accept by using the SailfishOS:Chum GUI application or the SailfishOS:Chum GUI Installer excludes any liability.
### Installation instructions
@@ -22,13 +22,13 @@
* **Initial installation without having Storeman installed**
1. Enable "System → Security → Untrusted software → Allow untrusted software" in the SailfishOS Settings app.
- 2. Download the current SailfishOS:Chum GUI Installer RPM from its ["latest release" page at GitHub](https://github.com/storeman-developers/harbour-storeman-installer/releases/latest), [OpenRepos.net](https://openrepos.net/content/olf/sailfishos-chum-gui-installer) or the [SailfishOS:Chum repository](https://build.merproject.org/project/show/sailfishos:chum/sailfishos-chum-gui-installer).
+ 2. Download the current SailfishOS:Chum GUI Installer RPM from [OpenRepos.net](https://openrepos.net/content/olf/sailfishoschum-gui-installer#node-11554), its ["latest release" page at GitHub](https://github.com/storeman-developers/harbour-storeman-installer/releases/latest) or the [SailfishOS:Chum repository](https://build.merproject.org/project/show/sailfishos:chum/sailfishos-chum-gui-installer).
3. Tap on the "File downloaded" notification on your SailfishOS device or select the downloaded RPM file in a file-manager app and choose "Install" in its pulley menu; then confirm the installation.
4. Preferably disable "Allow untrusted software" again.
### Features of SailfishOS:Chum GUI Installer
* SailfishOS:Chum GUI Installer creates a persistent log file `/var/log/sailfishos-chum-gui-installer.log.txt`.
-* SailfishOS:Chum GUI Installer runs "unattended": I.e., without any manual steps, after its installation has been triggered, until the SailfishOS:Chum GUI application is installed.
+* SailfishOS:Chum GUI Installer runs "unattended": I.e. without any manual steps, after its installation has been triggered, until the SailfishOS:Chum GUI application is installed.
* SailfishOS:Chum GUI Installer is slow, because it calls `pkcon` three times, which acts quite slowly. The minimal run time for SailfishOS:Chum GUI Installer is about 7 seconds, the typical run time is rather 10 seconds (measured from the moment SailfishOS:Chum GUI Installer's installation is triggered, until the SailfishOS:Chum GUI application is installed and its icon is displayed at the "launcher"). This is already a lot, but I rarely experienced a stalled Packagekit daemon (`packagekitd`, for which `pkcon` is just a command line frontend, communicating with the daemon via D-Bus) during heavy testing, which can be observed with the crude `pkmon` utility (`Ctrl-C` gets you out.:smiley:), so the SailfishOS:Chum GUI Installer tries to detect these "hangs" and to counter them: If that happens, its run time can be up to slightly more than 1 minute. In the worst case a stalled PackageKit daemon (and with it its `pkcon` client process(es)) stalls SailfishOS:Chum GUI Installer, until the PackageKit daemon reaches its idle time out of 300 seconds (5 minutes; this could theoretically happen three times, resulting in a likely unsuccessful run time of more than 15 minutes).<br />
Also note that SailfishOS sometimes fails to show an icon of a freshly installed app on the launcher ("homescreen") until SailfishOS is rebooted (rsp. more precisely: Lipstick is restarted).
|
|
[-]
[+]
|
Changed |
_service:tar_git:sailfishos-chum-gui-installer-0.6.3.tar.gz/bin/sailfishos-chum-gui-installer
^
|
| @@ -5,7 +5,7 @@
# despite minor errors.
set -o pipefail # May not be supported, busybox's ash and bash do.
export LC_ALL=POSIX # For details see https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html#tag_08_02
-export POSIXLY_CORRECT=1 # Can have side-effects, see e.g., https://github.com/Olf0/sfos-upgrade/issues/73
+export POSIXLY_CORRECT=1 # Can have side-effects, see e.g. https://github.com/Olf0/sfos-upgrade/issues/73
# Ultimately this ensures an almost consistent behaviour across shell implementations.
# Specify bash as interpreter of this script (in its first line), as this ensures
@@ -28,7 +28,7 @@
# This script is designed to be called fully detached (by a "double fork"
# / a "daemonize") as the last statement of the %posttrans scriptlet
-# (the last executed) of an RPM spec file or directly (e.g., in a shell).
+# (the last executed) of an RPM spec file or directly (e.g. in a shell).
# Memorise how we were called (argument checks are primarily intended for interactive use):
mypid="$$"
@@ -72,7 +72,7 @@
printf '\n%s\n' "$(date -Iseconds) $logentry"
systemd-cat -t "$called" -p 7 printf '%s' "$logentry"
-ssus="$(ssu s | grep -iv 'UID:\? ')"; logentry='[Debug] `ssu status`, UID omitted:'
+ssus="$(ssu s | grep -iv 'UID:\? ')"; logentry='[Debug] \`ssu status\`, UID omitted:'
printf '\n%s\n%s\n' "$(date -Iseconds) $logentry" "$ssus"
systemd-cat -t "$called" -p 7 printf '%s %s' "$logentry" "$(printf '%s' "$ssus" | sed 's/$/, /g' | tr -d '\n')"
@@ -143,7 +143,7 @@
logentry="[Warning] Failed to refresh sailfishos-chum repository, because error-code $retc was returned by: $logentry"
printf '\n%s\n' "$(date -Iseconds) $logentry"
systemd-cat -t "$called" -p 4 printf '%s' "$logentry"
- logentry="[Notice] Trying to terminate (i.e., sending SIGTERM to) all processes named (ID) `pkcon`, then sleeping for $wait seconds."
+ logentry="[Notice] Trying to terminate (i.e. sending SIGTERM to) all processes named (ID) \`pkcon\`, then sleeping for $wait seconds."
printf '%s\n' "$(date -Iseconds) $logentry"
systemd-cat -t "$called" -p 5 printf '%s' "$logentry"
killall -q -TERM pkcon
@@ -156,7 +156,7 @@
logentry="[Error] Failed to refresh sailfishos-chum repository, because error-code $retc was returned by: $logentry"
printf '\n%s\n' "$(date -Iseconds) $logentry"
systemd-cat -t "$called" -p 3 printf '%s' "$logentry"
- logentry="[Warning] Trying to interrupt (i.e., sending SIGINT to) all processes named (ID) `pkcon`, then sleeping for $wait seconds."
+ logentry="[Warning] Trying to interrupt (i.e. sending SIGINT to) all processes named (ID) \`pkcon\`, then sleeping for $wait seconds."
printf '%s\n' "$(date -Iseconds) $logentry"
systemd-cat -t "$called" -p 4 printf '%s' "$logentry"
killall -q -INT pkcon
@@ -170,7 +170,7 @@
logentry="[Error] Failed to refresh sailfishos-chum repository, because error-code $retc was returned by: $logentry"
printf '\n%s\n' "$(date -Iseconds) $logentry"
systemd-cat -t "$called" -p 3 printf '%s' "$logentry"
- logentry="[Warning] Trying to hang-up (i.e., sending SIGHUP to) all processes named (ID) `pkcon`, then sleeping for $i seconds and ultimately killing them."
+ logentry="[Warning] Trying to hang-up (i.e. sending SIGHUP to) all processes named (ID) \`pkcon\`, then sleeping for $i seconds and ultimately killing them."
printf '%s\n' "$(date -Iseconds) $logentry"
systemd-cat -t "$called" -p 4 printf '%s' "$logentry"
killall -q -HUP pkcon
@@ -210,7 +210,7 @@
systemd-cat -t "$3" -p 6 printf '%s' "[Info] Self-removal in 20 seconds: $2";\
eval $2)' sh_rm_inst-chum-gui "$mypid" "$logentry" "$called"
# The first 15 characters of the spawned process' name
- # (to be used for, e.g., `ps` and `pgrep` / `pkill`) are:
+ # (to be used for, e.g. `ps` and `pgrep` / `pkill`) are:
# sh_rm_inst-chum
fi
done
@@ -231,7 +231,7 @@
systemd-cat -t "$3" -p 6 printf '%s' "[Info] Executing: $2";\
eval $2)' sh_do_inst-chum-gui "$mypid" "$logentry" "$called"
# The first 15 characters of the spawned process' name
- # (to be used for, e.g., `ps` and `pgrep` / `pkill`) are:
+ # (to be used for, e.g. `ps` and `pgrep` / `pkill`) are:
# sh_do_inst-chum
# Double-fork / "Daemonise" ("SysV-style") in shell code, (ab)using this
# interpreter instance for the preamble (setting the environment):
|
|
[-]
[+]
|
Changed |
_service:tar_git:sailfishos-chum-gui-installer.rpmlintrc
^
|
| @@ -12,7 +12,7 @@
# - It extracts strange changelog entries out of Git, if a %%changelog section is used
addFilter('incoherent-version-in-changelog')
# - It sometimes re-writes the %version-%release strings of package names,
-# when referencing (only) a branch (i.e., not a git tag), for example,
+# when referencing (only) a branch (i.e. not a git tag), for example,
# 0.5.2-1 to 0.5.2+main.20230129011931.1.g584263a-1.8.1.jolla
addFilter('filename-too-long-for-joliet')
|
