The Storeman Installer for SailfishOS performs the initial installation of the Storeman OpenRepos client application. Storeman Installer selects, downloads and installs the correct variant of the Storeman application built for the CPU-architecture of the device and the installed SailfishOS release from the SailfishOS-OBS.
Starting with version 0.2.9, Storeman is built by the help of the SailfishOS-OBS and initially installed by the Storeman Installer (or manually). To update from Storeman < 0.2.9 (requires SailfishOS ≥ 3.1.0), one should reinstall Storeman via the Storeman Installer. After an initial installation of Storeman ≥ 0.3.0, further updates of Storeman will be performed within Storeman, as usual.
The Storeman Installer works on any SailfishOS release ≥ 3.1.0 and all three supported CPU-architectures (aarch64, armv7hl and i486). The current Storeman Installer RPM can be obtained from its "latest release" page at GitHub and OpenRepos.net.
RPMs of older Storeman releases are also available at OpenRepos, e.g. v0.1.8 which works on SailfishOS 2.2.1 and may work on older SailfishOS 2 releases.
/var/log/harbour-storeman-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, then you might file a new issue report there and attach the log-file to it, or enhance an extant bug report.devel-su pkcon refresh
in a terminal app.Initial installation without having Storeman already installed
Installation via Storeman (i.e. updating from Storeman < 0.2.9)
/var/log/harbour-storeman-installer.log.txt
.pkcon
two (releases before v1.3.8) to three times (releases from v1.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).