Patchmanager 3 Beta

Rating: 
4.916665
Your rating: None Average: 4.9 (12 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

 

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.50-1.117.1.armv7hl.rpm332.79 KB21/06/2018 - 22:37
File patchmanager-3.0.50-1.117.1.i486.rpm344.44 KB21/06/2018 - 22:37
File patchmanager-3.0.51-1.118.1.armv7hl.rpm332.89 KB24/06/2018 - 18:35
File patchmanager-3.0.51-1.118.1.i486.rpm344.4 KB24/06/2018 - 18:35
File patchmanager-3.0.55-1.123.1.armv7hl.rpm333.49 KB04/09/2018 - 15:59
File patchmanager-3.0.55-1.123.1.i486.rpm344.85 KB04/09/2018 - 15:59
Changelog: 

Update may require to manually unapply all patches and then apply it again for the new features to work.

Many new features.

Comments

dfstorm's picture

Well.. After upgrade to 3.0.0.5: patch list is empty, "load engine" do nothing, about do not show version number and the "setting pull down menu" make the app (setting in that case) crash. I try removing the app, reboot, etc... No luck.

mixmax's picture

I understand what's happen. The problem is not with PM, but with the patch 'Devicelock faith text' : you can enable it, but after restarting, all patches are disabled. Sorry...

mixmax's picture

I am alone in this case ?

mixmax's picture

Hi,

is there a problem with the SFOS update ? It is impossible, since SFOS 3.0.0.5, to enable any patch.

Tks, and regards.

Ingvix's picture

Can I somehow bypass the patchmanager daemon so I can read the original files while patch is enabled? Would make developing patches a lot easier.

coderus's picture

Sure, this is noted in description text :)

Markkyboy's picture

Hi coderus, I built 2 new patches yesterday. When I try to install them, they do not appear in patchmanager list. I made the patches the same way I have made all others, but these 2 do not install. I do not get any errors or notifications, except when I try removing, I get a notification "Patch removed".
I'm going round in circles here, any suggestions for troubleshooting and why do I not get any notification to say "Patch installed"...?
I have tried unapplying/removing all patches, then removing patchmanager and then reinstalling patchmanager and all my patches, all of my patches install and apply except the 2 new ones, also, I still do not get notification to say "Patch installed".....any ideas please?

coderus's picture

I have a lot of ideas, but please give me logfile, so i can look :)

Markkyboy's picture

thanks, what's the best way to post my 'patchmanager.log' file?, I've never had to do this before..?

coderus's picture
Markkyboy's picture

Done!, thank you.

4carlos's picture

0.1.4 Analogclock did not work, but after downgrade to 0.1.2 via webkatalog it runs again. Try it.

Jolla 1, 2.0.29

danfin's picture

since upgrading, patchmanager3 beta does not seem to start up anymore. After a restart it hangs at 'analog clock' patch. If I kill it, it shows zero available patches on web catalog, 'load engine' has no effect either. I run Sailfish 2.0.29. After a restart, again it loads patches and hangs at 'analog clock'. Uninstalling 'analog clock' does not help. Any hints? Thank you!

coderus's picture

Please give me a log

Piece_Maker's picture

I'm getting the same issue as this person, log is here: 

http://termbin.com/wrkt

Running an Xperia X with 2.2.0.29 

 

danfin's picture

sorry it did not work. The console command is a bit complicated, probably a typo. After stopping auto activation of patches, opening patchmanager3 beta, and activating them manually, everything runs smooth as before. Thank you very much!

evo3de's picture

File './core/armv7hl/gdbm-1.8.3-1.1.5.armv7hl.rpm' not found on medium 'https://releases.jolla.com/releases/2.2.0.29/jolla/armv7hl/'
Problem on Jolla repositories? How to bypass / fix this problem?

coderus's picture

pkcon refresh

crakby's picture

Ok. thanks!

patchmanager3_beta's picture

after pm3 release debug messages will be reduced

crakby's picture

Hi there,
I have many logs like this. Is this ok?

15.06.18 10:59:22.938 patchmanager[721]: unknown:0 PatchManagerObject::startReadingLocalServer()::__lambda114 Requested: "/etc/buteo/profiles/sync/carddav.Contacts.xml" Not changing

coderus's picture

Sure, this is how pm3 works

mixmax's picture

Hi ! I had a new event of the trouble yesterday, after the last update of PM3, with a web catalog in PM settings patch : no access to PM settings, my device asked me to reboot in order to call or send a message, then after reboot, no patch. I resolved it by deleting /usr/share/patchamanager/patches. I recovered an clean access, without any patch, to PM settings. I had to reinstall my patches, but no to reset my device... I don't know if it can be useful for resolving the bug... Thanks again for your work.

patchmanager3_beta's picture

seems you have outdated pm version

DameCENO's picture

Are you kidding me? your input is the most useful I have seen here in a while, and I thank you for sharing, you just saved more sailors from resetting than you will ever know, I just replied to say thank you, so thank you alot.

isgursoy's picture

Are we that far from solution? Could you mail me with the way I can transfer money? mail@isgursoyyavuz.com. Do you prefer telegram over forum?

coderus's picture
isgursoy's picture

Thank you. Now they are all unapplied and i cant enable any of them. Should I proceed to 3 and reinstall patches?

isgursoy's picture

Okay thank you for great work now I did but many patches are failed to be applied, even compatible ones, including launcher combo and voice call combined as they are working before. Interesting is launcher combo is actually running, but its switch is false and patchmanager thinks it is not alive, also can not apply. Weird.

mixmax's picture

I have noted that the same patches could be applied or not depending on the order you try to apply them.

Pages