Closed Olf0 closed 2 years ago
Current maintainership does not do changes on PM2 at this time. Closing wontfix.
Well, this might be of relevance for @elros34's PM2-forever.
Furthermore version / dependency management of Patchmanager and patches for Patchmanager in general is still not well solved. I will start a discussion thread for this.
IMO, each Patchmanager2 version should be only installable (by regular means) on the SailfishOS version(s) its built-in Patch "Unapply all patches on update" is applicable to. Otherwise (as currently the case), users cannot apply this built-in Patch and have to take care about unapplying all Patches manually, when updating SailfishOS. This implicitly leads to a bad user experience and "accidents" due to still applied Patches while updating SailfishOS! NB: Experienced users can always manually install any version of Patchmanager2 with
rpm -ihv --force
Tested with Patchmanager 2.3.3-10.41.1.jolla (installs flawlessly, but built-in Patch fails to apply, as it is only for SFOS 2.1.1.24 / 2.1.1.26), 2.3.2-10.40.1.jolla (installs flawlessly, but built-in Patch fails to apply, as it is only for SFOS 2.1.1.23) and 2.3.1-10.39.1.jolla (installs and built-in Patch is applicable: O.K.) on a Jolla 1 phone under SFOS 2.1.0.11 Expected result: Patchmanager 2.3.3-10.41.1.jolla and 2.3.2-10.40.1.jolla fails to install (easily, i.e. without
rpm --force
) under SailfishOS 2.1.0.11Hence please fix this packaging issue in future releases of Patchmanager2.
Originally reported on TMO.