Besides the intention of spec author regarding this contition I find that this requirement should be unconditional for this rpm.
The dconf command following with a restart worked on my XA2 Ultra.
Thanks for the help
The question is did Meecast-event-1.1-4 auto install lipstick for you?
1 Like
I guess not because I must have had everything installed already since Meecast was in use by me right before the update. But I do not know what the dconf command actually does.
Sorry to say but Harbour-meecast-event-1.1-5 still did not auto install lipstick for my device. X10III
I tested with the current Chum version too - no dice. I will install lipstick manually and run the dconf key change.
…
Yes, I know: The code of harbour-meecast-event-1.1-5 should be fine now, but it needs to be git-tagged and recompiled at the Sailfish-OBS (where the SailfishOS:Chum is located). I hope to find the time to take care about this the upcoming weekend.
6 Likes
Just wanted to interject here that this is a really nice project.
The weather forecast feature in the side menu was a good feature of SFOS and it would be really nice to have it back at some point.
Thanks to all involved for their efforts,
5 Likes
This popped up in today’s community meeting. So if you’re trying to use MeeCast and are not seeing weather in the Events View place follow @pvuorela 's instructions and force weather loading.
3 Likes
every month i made a new foreca account to “test” the api, but since yesterday this doesn’t seem to work anymore, i tried to create an additional account, but with that it also doesn’t work. maybe they recognized a pattern and blocked my api calls?
@lakeboy, thanks again for testing. I am pretty sure I now have all issues resolved, as these two tests (“Test 1” and “Test 2”) finally run fine.
I would appreciate, if you or someone else tests “in real life” again (i.e. on a device with SailfishOS 4.6.0 installed), with the packages I recompiled. The command lines below assume you are using an aarch64 device (i.e. an Xperia 10 II or 10 III; for armv7hl and i486 the download paths and RPM file names are slightly different) and that you are starting as a regular user (the dconf command must be executed as a regular user):
dconf reset /desktop/lipstick-jolla-home/force_weather_loading
devel-su
pkcon remove lipstick-jolla-home-qt5-weather-widget-settings harbour-meecast-event harbour-meecast-daemon harbour-meecast
mkdir foo
cd foo
curl -LO https://repo.sailfishos.org/obs/home:/olf:/MeeCast/4.6_aarch64/aarch64/harbour-meecast-1.1.39-1.2.1.jolla.aarch64.rpm
curl -LO https://repo.sailfishos.org/obs/home:/olf:/MeeCast/4.6_aarch64/aarch64/harbour-meecast-daemon-1.1.39-1.2.1.jolla.aarch64.rpm
curl -LO https://repo.sailfishos.org/obs/home:/olf:/MeeCast/4.6_aarch64/aarch64/harbour-meecast-event-1.1.39-1.2.1.jolla.aarch64.rpm
pkcon install-local harbour-meecast-1.1.39.2-1.2.1.jolla.aarch64.rpm harbour-meecast-daemon-1.1.39.2-1.2.1.jolla.aarch64.rpm harbour-meecast-event-1.1.39.2-1.2.1.jolla.aarch64.rpm
rm -f harbour-meecast-*
cd ..
rmdir foo
exit
Does MeeCast-EventView now work out of the box?
If so, I will submit these packages to SailfishOS:Chum.
1 Like
For me, after having set up sailfish weather event view, the packages currently in chum work out of the box. I just decided to switch to meecast for eventsview and lockscreen, and both work reliably
Sorry, this is well known, but not at all the requested test, hence not helpful.
Please test by executing every command line provided and report back here.
yes it works with your packages
1 Like
@olf nice work! Yes I can confirm that Event view of Meecast is now working. Nice work!!!
What was the missing step?
Thanks for your persistent work - whilst my home weather source isn’t working, I can follow other cities through other sources.
Happy chappy here. 
2 Likes
Only my blindness and idiocy, due to being too hectic as a result of having only little time for this (which then eats even more time 
).
1 Like
Looks like that was the techical solution 
1 Like
Well, technically it was really just that after spinning this thread of commits (2024-05-25 to 2024-06-21) to develop, implement and rectify multiple times a working approach to automatically (and at the right times) execute the commands Pekka Vuorela provided by the spec file.
1 Like
I really doubt usefulness of those ‘one click installer’ approaches, when 4.6 catastrophically failed one of those (can’t remember if it was chum or storeman) would just not install, so while in theory great, in catastrophe useless as you want to get your system back online and can’t waste time to bug report and wait weeks to get it fixed, search results get polluted by the non-working option (probably openrepos issue) and finding the right rpm to just click/install gets even harder.
Edit: idk maybe for weather it makes sense as you have to issue one command in cli, but for storeman/chum it was always just clicking the right arch rpm, then the maintainers decided to keep rpms in github and only provide failable script for newbies on openrepos, why?
maintainers decided to keep rpms in github
Or maybe this is just for the ‘installers’? Idk, idc, it’s a bit of a mess anyway, finding proper storeman client on storeman and not the installer one is an issue though
Edit2: like seriously, how do you find chum gui if the ‘installer’ fails:
Edit3: here are results for ‘storeman’, the actual rpm nowhere to be seen (I know inapp screenshot is bad but it’s the same on webpage, if installer fails you get a ton of useless crap)
Edit4: oh no, actually the ‘legacy’ is the real one that gets installed by installer if everything works fine? Can’t even tell
@throwaway69, this is absolutely senseless rambling: Not a single aspect of what you wrote is technically correct. Furthermore it is completely off-topic in this thread.
Everything is well documented: You just have to read the OpenRepos pages or READMEs at GitHub, and ultimately it is Open Source Software so you can look at how this works. If you then have a proper suggestion how to improve the SailfishOS:Chum GUI Installer and / or the Storeman Installer, you may open an issue or create a PR at GitHub.
BTW, the installers are there for a reason: Jolla introduces breaking changes with almost every SailfishOS release (see e.g. this thread), hence it is basically impossible to provide a non-trivial software by a single RPM for multiple SailfishOS releases.
TL;DR
RTFM: Reading Thoroughly First is Much advantageous.
P.S.: No bug reports mean no improvements.
Note that such ramblings do not constitute a bug report, because they lack specific information beyond “does not work for me”.
4 Likes
It’s either one-click for newbies, or you have to read 5 pages of documentation and it still fails in the end… Both of my reflashing experiences ended up with looking for just the rpm in the end, the base app hasn’t changed since 2022 it seems, the only thing that’s changed is people need to know that ‘legacy’ means it’s an actual working solution (or maybe following the github tags/releases for the rpm, seems there used to be an even bigger mess with storeman for 2.x, 3.4, <4.2, 4.2+ etc)
1 Like