Thanks! This was it. I hope that I get this to work

Ahoy, sailors. I've received many messages about updates for my patches. Please, be patient and just wait - my laptop is dead, so I can work only with my office-PC after work. Everything will be updated, but only as it possible. Thanks.

Continuing and (i.e. still the same setup):

9. [Usability bug] Updating a Patch by tapping on a newer version of it in Patchmanager2's web catalog causes significant issues
For example, see "P.P.S." in the report https://openrepos.net/comment/18958#comment-18958 and the subsequent discussion there.
The correct behaviour (from a simple user's perspective) would presumably be:
a. When an applied Patch is updated, always try to unapply the active (old) version first.
b. When an installed Patch is updated (this includes case a., after triggering an unapply action), try to uninstall the old version of this Patch before installing the new one.
c. For RPM-Patches, Warehouse / the RPM utility handles b., and it looks like such an action can notify Patchmanager2 to perform a., before actually updating the RPM. But I am not sure, if receiving such a notification is currently used by Patchmanager2 to perform a. for RPM-Patches. The wording issue (#8 of this list) supposedly contributes to my confusion here. Up to now I have only observed installing conflicting (i.e. *other*) RPM-Patches to trigger un*installing* (i.e. contrary to "unapplying") of Patches, but not updating one un*applying* its old version (at least not stated so by a SFOS-event notification). Side note: I have not (yet) taken a look, what is actually done in the pre-install scripts of RPM-Patches, or if some other mechanism to trigger Patchmanager2 exists.

10. [Feature suggestion] Indicate updateable Patches in the web catalog after entering it
Issue description: Currently one has to individually enter the sub-pages of all installed Patches in Patchmanager2's web catalog to look for updates. For RPM-Patches Warehouse handles this.
Possible solution: Indicate all installed Patches, for which an update is available, with some symbol (e.g. a star or a text "Update available") in the web catalog's top level list, after entering it (and hence refreshing the meta-data of all Patches available there).

P.S.: Continued in ...

It will be cool if you or someone will start sending PR to github for such bugs and features. I have no ETA when i can work on these.

Well, all I can do is to file these issues there: https://github.com/sailfishos-patche...manager/issues
Would that be helpful?

Pull requests (PRs) would require working code, which is beyond my capabilities.

And please provide a link on https://openrepos.net/content/coderus/patchmanager-20 to https://github.com/sailfishos-patche...manager/issues, if you want issues rather to be filed there than here.
Currently one line on Patchmanager2's OpenRepo page clearly states the opposite: "Please consider posting bugs and ideas to forum thread: http://talk.maemo.org/showthread.php?t=92935"
Sorry, I would have filed them there in the first place, if I would have known earlier, that https://github.com/sailfishos-patches/patchmanager is Patchmanager2's development location.

What is ETA? some body know?

"Estimated Time to Arrival (ETA)":
Originally used on displays at train stations and airports ("ETA: hh:mm" indicating the expected arrival time), the term ETA made its way via some classic UNIX command line tools (e.g. ftp, where "ETA: X seconds" indicates the remaining up- or download time) into (UNIX-) nerd speech.

The Urban Dictionary ("ud": either in the WWW or via the SFOS app "Unofficial Urban Dictionary") should provide you with most such nerd language explanations.

Thank you olf for your quick reply.

Continuing (i.e. still the same setup):

11. [Usability issue] Please move the entry "Unapply all patches" in Patchmanager2's top level pulley menu one or two positions further up, i.e. *above* the "About" entry.
Background: I accidentally selected "Unapply all patches" numerous times when trying to enter Patchmanager2's web catalog.
As entering the web catalog is often needed, the pulley menu entry "Unapply all patches" should be moved further away from the web catalog's entry.

12. [Big bad bug] Triggering "Unapply all patches" in Patchmanager2's top level pulley menu merely unapplies the first 10 Patches!
Hopefully Patchmanager2's built-in patch "Unapply all patches on Upgrade" behaves differently and really unapplies *all* Patches! (I still had Patchmanager1 installed when upgrading from SFOS 2.0.5.6 to 2.1.0.11, so I have not observed this situation, yet.) *Edit:* See post 2276 by coderus for an answer.

Maybe this is related to issue 6. on this list (or vice versa).

To be on the safe side, there is https://openrepos.net/content/schtur...pdate-manually.

I restored version for v2.1.0.11 and below. Grab it from openrepos (v0.1-4.5)