Please mark (“select”) the everything in thesecond postof this thread between the***Start*** and ***End***markers, hit the "Quote button (needs JavaScript enabled), delete the first line (which contains [quote="olf, post:2, topic:8552"]), also delete the very last line (which only contains [/quote]), then fill out the resulting form.
If you already have performed some technical analysis or can even provide a fix for the issue, please use the issue tracker and / or file a pull request at Github instead.
Only file bugs for the Patchmanager proper here, not bugs for patches:
For bugs which occur with patches from the Web Catalog, check if the specific patch offers a “discussion” or “sources” link on its detailed patch information page in Patchmanager where you can file a bug report, otherwise please file it at the FSO thread “Bugs in patches for Patchmanager”.
SailfishOS VERSION (Settings→About product→Build): HARDWARE (Settings→About product→Manufacturer & Product name): PATCHMANAGER VERSION (Settings→Patchmanager→[Top pulley] About):
BUG DESCRIPTION
STEPS TO REPRODUCE
ADDITIONAL INFORMATION
(Please consider which other pieces of information may be relevant, e.g. denote if this is not always reproducible, if it is a regression, attach relevant data such as log files or the systemd journal, provide screenshots etc.)
I think you solved that almost perfectly by opening a new thread (“topic”) using above template, and leaving single line with a link to that new topic here.
The only improvement I can think of is to include the title of the new thread in the single line. Actually pasting only title linking to the new thread is sufficient, which is for this example: [Bug] MMS doesn’t send pictures when Patchmanager is installed
Thank you @Objectifnul and @adekker for reporting, I retested (now, nine days later) and confirmed this, but then realised that @Objectifnul already moved this discussion (without mentioning it here) to:
This is fine, because this is not a bug in Patchmanager proper, rather a network misconfiguration.
This should be fixed now (September 9th) see this Telegram message (Sorry, it seems the link works only if you are in the Telegram group Telegram: Join Group Chat, but it’s just Coderus announcing that the web app is up again.)
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.
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.
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.
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.
@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.