-
Notifications
You must be signed in to change notification settings - Fork 22
Debugging "64‐bit issues"
Currently the majority of patches out these are developed and tested on / for 32-bit systems. Some of them have a problem on 64-bit systems where they do not apply due to library paths being different.
This is a known problem, a solution on the patchmanager side is in the works. No timeschedule though wrt a release at the moment
See progress of Patchmanger Issue #71 about this.
In the mean time, this is how to fix such a patch:
- Verify that the patch is actually failing due to 64bit. Inspect the patch file, if the files changed are under
/usr/lib
(usually that is/usr/lib/qt5/qml
), this might be the problem we are seeing. - Back up the original patch file
- Verify that for each file under
/usr/lib
in the patch, a corresponding file exists on your system under/usr/lib64
- Open the patch file in an editor, and change all occurrences of
/usr/lib
to/usr/lib64
. Be very careful not to change the format of the .diff file in any other way than correcting the paths. - Save the patch and try again to apply it
Note that if you are using patchmanager to apply patches, the patch file must be named unified_diff.patch
. No other names will work.
It’s probably best if you start by renaming the patch from /usr/share/patchmanager/patches/patchname
to /usr/share/patchmanager/patches/patchname-mine
, and edit the corresponding names in the new patch.json
file. This way you have both the old and the new versions available and visible in patchmanager.
Original source: https://forum.sailfishos.org/t/bugs-in-patches-for-patchmanager/8553/15