Patchmanager 3 public beta
Make sure to unapply patches before upgrade from Patchmanager 2. Installation will fail if any patch is applied.
If you have installed prepatch, please remove it before patchmanager3 installation.
Changes between version 2 and version 3:
Patchmanager daemon acts like proxy, filtering open calls and decide if application should open original file or fake one.
Useful environment variables:
NO_PM_PRELOAD=1 disables preload plugin from filtering calls
PM_PRELOAD_DEBUG=1 enables additional stderr output for preload plugin
Keep in mind this is beta version and should contain a lot of bugs. However it was tested for a while.
Please report all bugs to: https://talk.maemo.org/showthread.php?t=92935
You can collect patchmanager logs by running: devel-su journalctl -al _COMM=jolla-settings + _EXE=/usr/sbin/patchmanager + _EXE=/usr/bin/patchmanager-dialog > patchmanager.log
Sources available here: https://github.com/sailfishos-patches/patchmanager/tree/patchmanager3
Translate project: https://www.transifex.com/coderus/patchmanager3
Big thanks jakibaki for Prepatch. This was very good idea to create such way for applying patches. You can review my plugin here: https://github.com/sailfishos-patches/patchmanager/blob/patchmanager3/sr...
Attachment | Size | Date |
---|---|---|
![]() | 338.18 KB | 11/01/2019 - 17:31 |
![]() | 349.84 KB | 11/01/2019 - 17:31 |
Refactored commandline mode
Comments
mixmax
Mon, 06/04/2018 - 13:20
Permalink
What is "step by step guide" ?
coderus
Mon, 06/04/2018 - 13:44
Permalink
when you explain problem step by step.
1 opened something
2 did something
3 installed something
4 then did something
5 and something happened
mixmax
Mon, 06/04/2018 - 22:36
Permalink
OK, not easy because it seems random...
1. I install patchmanager
2. I install different patches, from 'web catalog' of PM Settings
3. No problem when I reboot (expect the last one I installed)
4. I install other patches from openrepos, with storeman
5. It works
6. I reboot
7. It doesn't work any more...
I precise my device is an Intex aqua fish, modified with your script, aqua fish to Jolla C.
It could be a possible cause of the trouble, or another one, till when I reset my device , I run the script, I upgrade the system to 2.2.0.29 version, and I can't install again Storeman or warehouse, zypper returns me some problems of dependances.
It is incomprehensible for me, so I will try without the script aqua fish to jolla C.
Vieno
Tue, 06/05/2018 - 15:21
Permalink
I'm having the same problem. Trying to solve the problem was unsuccessful so far. When trying to delete all patches via a terminal session it says '... is not owned by any package'. Thats weird. May I find out more tonite.
mixmax
Tue, 06/05/2018 - 16:33
Permalink
Too bad for you, but I am relieved ! I am not alone !...
coderus
Tue, 06/05/2018 - 15:27
Permalink
Did you installed prepatch before?
Vieno
Tue, 06/05/2018 - 20:00
Permalink
No, I didn't. Is that needed? I try to send a log as well after I'm back from work.
Vieno
Fri, 06/08/2018 - 12:32
Permalink
All my problems vanished after the recent update. Thanks a lot for the essential app.
mixmax
Tue, 06/05/2018 - 16:31
Permalink
Well, it seems to be a bug with PM3 ?... Because I reset my device, upgrade SFOS to 2.1.4.14, I didn't apply aqua-fish-to-jolla-c, and the problem is the same.
Moreover, it is impossible to install PM2 still update to PM3, storeman start to work, but stop immediatly, and stay to "uninstalled", so for the moment, I will keep my device as it stood, i.e. identified like Intex, with SFOS 2.1.4.14, PM3, least possible patches from storeman, and above all avoid reboot !
Ask me if you need more details, I will do my possible, and thanks a lot for your readiness.
coderus
Tue, 06/05/2018 - 16:51
Permalink
send me log
devel-su journalctl -al /usr/sbin/patchmanager > patchmanager.log
mixmax
Wed, 06/06/2018 - 13:04
Permalink
I don't understand why, but this command doesn't return anything... ??
coderus
Wed, 06/06/2018 - 13:07
Permalink
It creates file called patchmanager.log in the folder where you execute command
mixmax
Wed, 06/06/2018 - 14:28
Permalink
Why what should happen never happens with me ??? I don't find this file ! No folder /usr/sbin/patchmanager. Only files : one calls 'patchmanager' (executable), and no 'patchmanager.log'.
mixmax
Wed, 06/06/2018 - 14:30
Permalink
So, I did 'devel-su journalctl -al /usr/sbin/patchmanager > /home/nemo/patchmanager.log', and the file was created, with inside : 'Auth failed'
olf
Mon, 06/11/2018 - 00:44
Permalink
@mixmax, please issue the two commands separately:
devel-su
# Log in as rootjournalctl -al /usr/sbin/patchmanager > ~nemo/patchmanager.log
mixmax
Fri, 06/08/2018 - 22:45
Permalink
That's what I did. And the result is a file created, with only 'Auth failed' inside.
mixmax
Tue, 06/05/2018 - 16:38
Permalink
No prepatch...
Should I ?
objectifnul
Sat, 06/02/2018 - 00:29
Permalink
Unfortunately, some patches cannot be disabled, so I cannot upgrade patchmanager.
DameCENO
Fri, 06/01/2018 - 14:29
Permalink
Great work the idea to combine patchmanager and prepatch is just sublime. Which OS version is compatible with it? I am still on 2.1.4 is that ok and would it conflict with the newly released verson of Sailfish?
Great work once again
patchmanager3_beta
Fri, 06/01/2018 - 14:31
Permalink
patchmanager is just patch manager. os compatibility is up to patch authors :)
explit
Fri, 06/01/2018 - 11:37
Permalink
Can we use the patches from patchmager 2 with patchmanager 3?
patchmanager3_beta
Fri, 06/01/2018 - 11:38
Permalink
Sure, why not? :D
Pages