Skip to content

Commit

Permalink
Restore very last bullet point
Browse files Browse the repository at this point in the history
  • Loading branch information
Olf0 authored Mar 20, 2023
1 parent 6a5c904 commit 325211d
Showing 1 changed file with 12 additions and 0 deletions.
12 changes: 12 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,3 +46,15 @@ RPMs of [older Storeman releases are also available at OpenRepos](https://openre
* [Storeman Installer 1.3.8](https://github.com/storeman-developers/harbour-storeman-installer/releases/tag/1.3.8) and all later versions create a persistent log file `/var/log/harbour-storeman-installer.log.txt`.
* Storeman Installer 2 runs "unattended": I.e., without any manual steps, after its installation has been triggered, until Storeman is installed.
* Storeman Installer is slow, because it calls `pkcon` two (releases before v1.3.8) to three times (releases from v[1.3.8](https://github.com/storeman-developers/harbour-storeman-installer/releases/tag/1.3.8) on), which acts quite slowly. The minimal run time for Storeman Installer 2 is about 7 seconds, the typical run time is rather 10 seconds (measured from the moment Storeman Installer's installation is triggered, until Storeman is installed and its icon is displayed at the "launcher"). This is already a lot, but rarely the Packagekit daemon stalled (`packagekitd`, for which `pkcon` is just a command line front-end, 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 Storeman Installer now 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 Storeman 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).
* You can follow Storeman Installer's actions with a `tail -f /var/log/harbour-storeman-installer.log.txt`, but mind that this file has to exist before telling `tail` to read it. Storeman Installer will create this log file during its installation, but here you want to start the `tail -f` right *before* that happens. This can be easly achieved by:<br />
`[defaultuser@sailfishos ] devel-su`<br />
`[root@sailfishos ] touch /var/log/harbour-storeman-installer.log.txt`<br />
`[root@sailfishos ] chmod 0666 /var/log/harbour-storeman-installer.log.txt`<br />
Open another terminal window on or ssh session to your device and execute:<br />
`[defaultuser@sailfishos ] tail -f /var/log/harbour-storeman-installer.log.txt`<br />
Then return to the first terminal window or ssh session:<br />
`[root@sailfishos ] pkcon --install-local <path/to/downloaded/harbour-storeman-installer-?.?.?-*.noarch.rpm>` # Insert real values for `?` (a single character, here a single digit number) and `*` (multiple characters).<br />
If you have already enabled a package repository, which offers Storeman Installer (e.g. OpenRepos/olf or SailfischOS:Chum), a simpler command works, without manually downloading the *harbour-storeman-installer* RPM package:<br />
`[root@sailfishos ] pkcon install harbour-storeman-installer`<br />
BTW, you can list all installed or online available (but not installed) Storeman-related packages by issueing:<br />
`[defaultuser@sailfishos ] pkcon search name storeman`

0 comments on commit 325211d

Please sign in to comment.