the file I used was downloaded from OpenRepos, it was exactly this file.
Yes, the current upload of Patchmanager 3.2.6 at Openrepos may not support SailfishOS 4.5.0, because it is compiled for SailfishOS 4.0.1. Edit: The reason was a change in SailfishOS from 4.4.0 to 4.5.0.
Unfortunately noone has reported here if Patchmanager 3.2.6 compiled for SailfishOS 4.4.0 from the SailfishOS:Chum community repository works.
- If it does, I will try to release Patchmanager 3.2.7 (which is in the works) at OpenRepos this weekend (Edit: done). That should work on SailfishOS 4.5.0.
- If it does not, please file an issue report at GitHub.
I do need a confirmation of either case. Edit: Done by Ahtisilli.
P.S.: Mind that SailfishOS 4.5.0 is in the EA phase, many programs may fail to install or run, and developers cannot compile anything for SailfishOS 4.5.0, yet.
2 Likes
Well actually 
1 Like
Well then, go ahead.
For Patchmanager we are not using the SDK installed locally, only Coderus’ SDK Docker images and the SailfishOS-OBS. I currently lack the time for any change of established processes, but feel free to provide a version compiled with this fresh SDK release.
Both 32-bit and 64-bit work.
Edit: Just updated to 3.2.7 from Chum. Both versions work.
3 Likes
Thank you very much for this confirmation.
If someone installed Patchmanager 3.2.7 from OpenRepos on SailfishOS 4.5.0, I would appreciate a confirmation if it works fine (or not), too.
Background: The RPMs uploaded there are compiled by a different machinery (a GitHub CI run, instead of the SailfishOS-OBS), and have to be uploaded manually, hence I may have picked an incorrect version.
Just installed now and it looks fine on my side. X10 II - 4.5
By the way, various PM Test Case were added
1 Like
@pherjung, does this statement address the Patchmanager 3.2.7 RPM at OpenRepos? I am asking, because your message is not a reply to my latest one and does not mention OpenRepos.
By the way, various PM Test Case were added
???
The PM-Testscases RPMs exist since Patchmanager 3.2.2 AFAIR.
Oh, I surely clicked on the wrong reply. Anyway, yes I installed it from OpenRepos (it was before installed from chum).
Strangely they appeared after I installed Patchmanager from OpenRepos.
1 Like
I am not so sure, because it happened to me a couple of times, too. I suspect a bug in Discourse, but was never sure, if it was not me clicking “wrong”. When I deleted a post and replied again, it appeared to work fine (but I do not remember, if “most of the time” or “all the time”).
Anyway, yes I installed it from OpenRepos (it was before installed from chum).
Thank you very much, especially as you ran an explicit test!
1 Like
Hm that shouldn’t happen automatically, but I have a hunch why it did, and its related to how openrepos works.
You can safely uninstall them.
BTW any idea when version 4.5.0.16 will be available to pick up in compatible version on patchmanager website?
I suppose you intend to address Patches in Patchmanager’s Web Catalog: This is a task the author of each Patch has to do and completely unrelated to Patchamanager or the Web Catalog proper.
What you can do is use Patchmanager’s setting to switch off the version check.
Wait you should do is to contact the authors of your favourite Patches to test these on SailfishOS 4.5.0.16 and mark them as compatible to it. As then source code of most Patches are hosted at GitHub, I am sure contributions are welcome, because “will be available” is “never” if nobody does it.
I’m sorry it seems I wasn’t clear enough. The problem is that right now the patchmanager website allows me to set 4.4.0.72 as the highest compatible version. There’s no 4.5.0.16 in the ComboBox, see sshot:
Even with the check off, the FinerVolume Control patch won’t run
i tried adding the almalinux repo with zypper and then install patchmanager 3.2.7-1, but it wants me to uninstall pretty much every other package i have on my system 
… and you still are not: It is Patchmanager’s Web Catalog you intend to address, Patchmanager’s website is here.
Please use either correct terms or web-links to express yourself unambiguously.
Yes, so someone had to pose a pull request. Why didn’t you?
1 Like
For someone that’s not working with something on daily basis it’s not that easy to learn everything at once. And even if I’d learn everything, using it like once per year or even less would result my mind to get rid of useless knowledge. That’s why I said sorry and pasted sshot.
let’s say that I will assume that there’s no bold on the word you. Otherwise I’d think you’re trying to be mean and we don’t want to think like this, right?
So to your knowledge, I couldn’t/can’t do a pull request because:
- I didn’t knew such thing is required
- I don’t have github account and there’s no way I’ll make one just for this
1 Like