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

General
#79

I think Vasvlad and I have fully resolved installing MeeCast’s Eventview from OpenRepos (preferrably by using Storeman) on SailfishOS ≥ 4.6.0.

I would appreciate very much if someone tests this:

  1. As usual, please remove the harbour-meecast package first (which should also remove all other MeeCast packages: Please check with pkcon search name meecast that none is still installed).
  2. Then install the MeeCast’s Eventview package using Storeman (which should automatically also install the MeeCast Demon and MeeCast proper).

a. Is the installation working fine?
b. Does MeeCast’s Eventview work fine then?

1 Like
#80

I couldn’t install Event View itself as it reported “missing application” from Storeman. I did it manually and all is working well

2 Likes
#81

Thank you very much: Will investigate why Storeman / Packagekit does not get this right.

1 Like
#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.

1 Like
#87

Btw MeeCast need some Design-Love for the Event-View on the Jolla C2 Device:

Bild1
Bild1719×442 52.9 KB

6 Likes
#88

This is on more devices, on Redmi 5 Plus is same blank space.

4 Likes
#89

Same on Jolla tablet …

3 Likes
#90

@fingus, @Kuba77 and @gabs5807, it has been like this all the time: The row is filled with 4 icons in portrait- and 8 icons in landscape-orientation; the remaining gap is not large enough to fit another icon (minus empty borders to the screen edge).

But I see no corresponding issue filed, hence the main developer cannot be aware of your suggestion to optimise the layout:

P.S.: BTW, this conversation is completely off-topic for this discussion thread, hence please stop it and file a proper issue repost so it might become being worked on.

5 Likes
#91

@olf
You are right and here we go.

2 Likes
#92

I don’t have account on BSO and that’s probably a reason why I didn’t found a way to DL as requested in step b.

Is there any other way to test?

BTW: MeeCast itself installed from Chum with repo 4.3.0.15 also works. Others doesn’t seem to do anything. I didn’t restart C2 but I guess it’s not needed.

Also: It seems a small bug but after app removal in Chum I had to refresh repos most of the times as all apps were gone from GUI. I rarely uninstall but I don’t remember that on previous phones.

#93

Having no account at build.sailfishos.org should make no difference for this, but never mind, because …

BTW: MeeCast itself installed from Chum with repo 4.3.0.15 also works.

… this is also a valid way to perform this test.

But this statement irritates me:

Others doesn’t seem to do anything.

  • Which “others”?
  • And what did you intend to express with “not doing anything”?
    E.g. what was the behaviour you expected from the “others” (i.e. to do what?)?

I didn’t restart C2 but I guess it’s not needed.

Yes, for MeeCast proper not, and a reboot also should not be required for MeeCast daemon and event-view to work, but some reported the contrary.

Consequently I reverted MeeCast PR #72 by PR #76.

P.S.:

Also: It seems a small bug but after app removal in Chum I had to refresh repos most of the times as all apps were gone from GUI. I rarely uninstall but I don’t remember that on previous phones.

Sorry, wrong discussion-thread (“topic” in Discourse’s parlance), inadequate tool (a forum software) and basically the wrong server (not where the software you address is hosted) for creating an issue report.

If this is reproducible for you and you want this issue to be worked on (sooner or later), please file a proper issue report (by choosing the appropriate issue template after hitting the “New issue” button) at Issues · sailfishos-chum/sailfishos-chum-gui · GitHub.

#94

Ok, how can I test? It seems to me that MeeCast 1.11.7 works as app. Open or tiled. But I am a new user.

Sorry for shity reporting I should write the whole names: MeeCast eventview widget and MeeCast lockscreen widget.
And the exact results:

I could not install MeeCast eventview widget. Idea was that it’s is needed for the events screen. Top message said:
“Nothing provides sailfish-version < 4.6.0 needed by the to be installed harbour-meecast-event-1.11.7-1.3.1.jolla.arch64”

MeeCast lockscreen widget did install but I didn’t notice any difference on the lock or events screen. Idea was that it’s is needed for the lock screen.

Reboot didn’t changed behaviour of either MeeCast and MeeCast lockscreen widget.

I’ll see if I can reproduce Chum bug and report it on github.

Thanks for your patience.

#95

You already did test nicely by setting the OS release manually to 4.3.0.15 in SailfishOS:Chum GUI app.

It seems to me that MeeCast 1.11.7 works as app.

Yes, that is the reason why I already acted upon your observation: The next MeeCast release at OpenReops will be complied for SailfishOS 4.3.0 (as likely the current releases there are, too).

That was expected (hence I suggested to test only with MeeCast proper), only the package “harbour-meecast-eventview” installs on SailfishOS ≥ 4.6.0, which at SailfishOS:Chum is only offered for SailfishOS ≥ 4.6.0. As you manually set the SailfishOS:Chum GUI app to use packages for 4.3.0.15, the appropriate package for SailfishOS < 4.6.0 (harbour-meecast-event) is downloaded and tried to install.

  • MeeCast lockscreen widget did install but I didn’t notice any difference on the lock or events screen. Idea was that it’s is needed for the lock screen.

IIRC the status of the MeeCast lockscreen widget is “broken on recent SailfishOS releases” and “disabled in MeeCast’s code base”; see also [Suggestion] Update `MeeCast lockscreen` with enhancements by `anig` and (optionally) convert it to a Web Catalog Patch · Issue #63 · Meecast/meecast · GitHub.

I’ll see if I can reproduce Chum bug and report it on github.

:+1:

Thanks for your patience.

I feel it is me having to thank you for your efforts, which are very helpful.

1 Like
#96

Fyi I could manage to have meecast weather forecats on the event screen of the C2 with latest 5.0 public release. I successfully installed meecast and meecast-daemon from storeman. Meecast-eventview was still failing with storeman. I installed it with the terminal with “pkcon install harbour-meecast-eventview”.

1 Like
#97

This instructions seems incomplete, Can you please expand it?

#98

What is not working?