Patchmanager 3 Beta

Rating: 
4.86207
Your rating: None Average: 4.9 (29 votes)

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:

  • Not changing original files. Patches applied to fakeroot located at /tmp/patchmanager
  • OS update friendly. Patchmanager3 automatically detects when user start downloading an update and unapplying all patches
  • Patches can be reordered to be applied in correct order. Just drag to left and drop at required position
  • Collect information about possible conflicting patches. Visit patch info page.
  • Automatic check for updates for online catalog patches. Notificaiton will popup if new version of patch will be released

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...

 

Application versions: 
AttachmentSizeDate
File patchmanager-3.0.57-1.125.1.jolla_.armv7hl.rpm338.18 KB11/01/2019 - 17:31
File patchmanager-3.0.57-1.125.1.jolla_.i486.rpm349.84 KB11/01/2019 - 17:31
Changelog: 

Refactored commandline mode

Comments

mixmax's picture

I have a problem with this update : 'web catalog' patches work correctly, but each patch to openrepos by storeman causes troubles. They can work properly, but don't support reboot. After that, I can't run patchmanager settings, and no patch works. Thanks and regards

coderus's picture

I tried my best, but can't understand what is you problem, please explain.

mixmax's picture

Difficult for me to explain more, because of my english and because I don't understand what happen, and when it happens ! But the problem happended yesterday with a 'web catalog' patch, and as I could not access to patchmanager settings any more to uninstall it, I decided to reset my device !

coderus's picture

With what patch?

mixmax's picture

The last time, it was the patch witch makes vibrate buttons and icons-buttons, from the 'web catalog' of patchmanager settings. But before, it was any patch from storeman, apparently randomly ; sometimes it worked and suddenly, it stoped to work. That's why it's difficult to identify the cause of this trouble.

coderus's picture

Well, I'd like to see step by step guide for problem reproduction

mixmax's picture

What is "step by step guide" ?

coderus's picture

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's picture

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's picture

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's picture

Too bad for you, but I am relieved ! I am not alone !...

coderus's picture

Did you installed prepatch before?

Vieno's picture

No, I didn't. Is that needed? I try to send a log as well after I'm back from work.

Vieno's picture

All my problems vanished after the recent update. Thanks a lot for the essential app.

mixmax's picture

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's picture

send me log

 

devel-su journalctl -al /usr/sbin/patchmanager > patchmanager.log

mixmax's picture

I don't understand why, but this command doesn't return anything... ??

coderus's picture

It creates file called patchmanager.log in the folder where you execute command

mixmax's picture

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's picture

So, I did 'devel-su journalctl -al /usr/sbin/patchmanager > /home/nemo/patchmanager.log', and the file was created, with inside : 'Auth failed'

olf's picture

@mixmax, please issue the two commands separately:
devel-su # Log in as root
journalctl -al /usr/sbin/patchmanager > ~nemo/patchmanager.log

mixmax's picture

That's what I did. And the result is a file created, with only 'Auth failed' inside.

mixmax's picture

No prepatch...
Should I ?

objectifnul's picture

Unfortunately, some patches cannot be disabled, so I cannot upgrade patchmanager.

DameCENO's picture

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's picture

patchmanager is just patch manager. os compatibility is up to patch authors :)

explit's picture

Can we use the patches from patchmager 2 with patchmanager 3?

patchmanager3_beta's picture

Sure, why not? :D

Pages