SFOS ≥ 4.6 (Foreca / MeeCast): How to (re-)enable weather infos in Events View

General
#82

On a C2 with SFOS 5, storeman says something like “needs SFOS<4.6” when I try the package “meecast event view”. I downloaded “harbour-meecast-eventview-1.11.7-1.aarch64” from openrepos.net but again there is an issue when installing (could not see the error message). I do not have more time to investigate now but will try later.

#83

Same for me.
I then installed MeeCast from Storeman and it works great!
Thx.

#84

Oh, @lakeboy, @patoll and @filip.k, these results are confusing for me, because they seem to contradict.

@patoll’s report is the most complete one, as it names device and OS version (and even the specific MeeCast-Eventview RPM file). Thanks!

  1. @patoll wrote «storeman says something like “needs SFOS<4.6” when I try the package “meecast event view”», which points to something I have not considered, because all Packages uploaded by a account at OpenRepos end up in a single RPM repository (see here the one of Vasvlad). But Storeman might evaluate some information on the app web-page, then offering the new harbour-meecast-eventview package on a new, separate “MeeCast Eventview for SailfishOS >= 4.6.0” page would resolve this. I can either research this in Storeman’s code (which I did not write) or ask Vasvlad to simply try this.

    But @lakeboy wrote «I couldn’t install Event View itself as it reported “missing application” from Storeman.«, which seems to be a completely different error message!?! :astonished:

  2. @lakeboy wrote «I did it manually and all is working well», which could either mean "… by executing pkcon install harbour-meecast-eventview" (which may have pulled this package from SailfishOS:Chum, if that repository is subscribed) or “… after downloading harbour-meecast-eventview-1.11.7-1.<arch>.rpm from this OpenRepos web-page by clicking on the appropriate harbour-meecast-eventview package for the CPU-architecture of the device, then using pkcon install-local harbour-meecast-eventview or a file-manager / Jolla’s Transfers list to install it”.

    This is contrasted by @patoll’s statement «I downloaded “harbour-meecast-eventview-1.11.7-1.aarch64.rpm” from OpenRepos but again there is an issue when installing (could not see the error message)», which may indicate an issue with the package itself. OTOH, this my be a result of testing on SailfishOS 5.0.0, because Jolla does not yet provide the tooling to compile explicitly for it; currently all MeeCast packages at OpenRepos are compiled for SailfishOS 4.3.0 (which should / are reported to run fine on 4.6.0, 4.5.0, 4.4.0 and 4.3.0), while users of SailfishOS:Chum have reported packages (in general and this one) compiled there for SailfishOS 4.6.0 to work fine on 5.0.0. Hence this may be resolved by recompiling the package(s), which will let them cease to work on older releases than the one compiled for (some users including me are reluctant to upgrade SailfishOS due to regressions).

    As it would be really helpful to know which minimal target release still runs on SailfishOS 5.0.0, I would be happy, if you (or another C2 user) can try this, given that you can spare the time (and please take your time, we are working on understanding and resolving these issues for months, hence a few days more or less do not make a significant difference):

    a. Remove all installed MeeCast packages: pkcon remove harbour-meecast-eventview harbour-meecast-daemon harbour-meecast

    b. Download the harbour-meecast package (only; this is sufficient for testing) from the RPM sub-repository 4.5.0.24_aarch64 of sailfishos:chum/MeeCast, by clicking on it (the second entry of the bullet-list), then click on the package name again in the title of the page which opened ("Detailed Information About <packagename>").

    c. Install the downloaded package by a file-manager, pkcon install-local <path-to-package> or the “Transfers” list in SailfishOS’ settings app:

    • Does it install?
    • Does it start and seem to work (just a few taps for a very quick & dirty test (often called “smoke test”))?

    d. Remove the package again: pkcon remove harbour-meecast

    If that worked fine, please repeat steps a to d with Meecast’s SFOS:Chum sub-repos for 4.4.0.72_aarch64, and if that worked well with the one for 4.3.0.15_aarch64.

    Finally, please report the lowest SailfishOS target release for which MeeCast installed and started on SailfishOS 5.0.0, and install all packages again to restore a fully working MeeCast (by pkcon install harbour-meecast harbour-meecast-daemon harbour-meecast-eventview with the SailfishOS:Chum GUI app set to 4.6.0.15, or manually in it with the same setting).

    Take your time, and if you lack any, or that is too tedious for you to test, please tell so (I might try to find another Jolla C2 owner to test this, then).

P.S.: Sorry @filip.k, I do not comprehend your posting: To me the first and second sentence seem contradict each other. Did you mean to express «On a Jolla C2 with SFOS 5.0.0, Storeman says something like “needs SFOS<4.6” when trying to install the package “Meecast Event View”, but installing the package “MeeCast” works»?

1 Like
#85

Yes. And MeeCast as app works nicely.

Will try your test on my C2 in the afternoon hopefully.

1 Like
#86

If you are sure about this you can start the steps a to d right away with the Meecast’s SFOS:Chum sub-repo for 4.3.0.15_aarch64 and it should work, because I believe the most current packages at OpenRepos were compiled by Vasvlad with the SDK for SFOS 4.3.0; consequently you can start right away checking if my assumption is true (and don’t have to iterate through 4.5.0 and 4.4.0 before that).

Will try your test on my C2 in the afternoon hopefully.

As stated, we are not in a hurry, because all MeeCast packages work fine when installing them from the SailfishOS:Chum community repository. But as SailfishOS:Chum will likely continue to be slightly hard to use with cBeta and EA releases of SailfishOS, I would be glad to resolve the remaining issues (should not be much) at OpenRepos in the long run.