@mizar,
This
That's exacly what i said, previous update 18.0.82.2 has libapache2-mod-proxy-lock-plesk with *greater* release then 18.0.82.3, and thus, the new package is not installed.
became clear later to me, my apologies for the confusion.
In essence, I was a bit overwhelmed by the fact that two - exactly - identical servers were different somehow, with the only difference that one of the server being updated automatically (the dev server, if we need to assign a name) and the other one being updated manually (a couple of days later).
Setup and config should have been exactly the same, with one or two differences (that should not matter for this issue).
The Imunify conflict is remaining and resulting in even more mind-blowing situations.
This might be related to one of the differences between the two servers : I did install (in the past) Imunify via CLI on one server and with Plesk GUI on the other server, but the CLI install has been reverted to a Plesk based installation.
The nasty thing about Imunify is that packages are not cleaned properly when uinstalling Imunify via either Plesk or CLI - a lot of manual action is required.
At this moment, there is this odd situation that both servers install / update different packages and package versions, which can be related to
a) the (past) Plesk based installation : there is an indication of that, but no certainty
b) the "roll out" of Imunify updates : not all things are updated simultaneously
It seems to be the case that the "roll out" repos are not properly synchronized, but I cannot confirm that.
There is a (constant) difference in the roll out repo used by both servers.
In my humble opinion, this is not a good thing and Plesk should take it up with Imunify / CloudLinux ....... but then again, it is up to Imunify / CloudLinux.
If and when I have time, I will contact Imunify / CloudLinux.
There are - potentially - many other conflicts, but I cannot establish them with certainty, so it is - relatively - safe to ignore the other conflicts.
One other matter of importance might be that Plesk leaves a lot of obsolete packages.
Can an automated clean-up of packages be adding to a next Plesk micro update?
Kind regards....
PS I hope that PPP-73985 will be resolved (and a patch released soon), since it is likely that some Plesk instance might be affected.