| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| ffs_sftp.patch | https://github.com/libssh2/libssh2/issues/90 | B Stack | no | 2021-02-02 | ||
| ffs_traditional_view.patch | bgstack15@gmail.com | no | 2023-01-23 | |||
| ffs_desktop_notifications.patch | bgstack15 | no | 2022-02-06 | |||
| ffs_devuan.patch | bgstack15 | no | ||||
| ffs_dpkg_vendor_specific_about.patch | bgstack15 | no | ||||
| ffs_devuan_gtk3.patch | B Stack | no | 2020-08-31 | |||
| ffs_no_check_updates.patch | bgstack15 | no | 2023-01-22 | |||
| ffs_icon_loader.patch | Message: Warning! I have absolutely no idea what I am doing. Check https://freefilesync.org/forum/viewtopic.php?t=8780 for future developments. In Devuan Ceres, starting in 2021-08 with libglib2.0-0=2.68.3-2 the file icon_loader.cpp fails to compile. By removing the static_cast, this file can compile. The built application throws all sorts of GLib-GObject-CRITICIAL messages but the application operates. Downgrade to "deb [check-valid-until=no] https://snapshot.debian.org/archive/debian/20210801T144205Z/ unstable main non-free contrib" in /etc/apt/sources.list and install the exact libglib version necessary to compile without this patch. $ sudo apt-get -V install libglib2.0-0=2.66.8-1 libglib2.0-bin=2.66.8-1 libglib2.0-data=2.66.8-1 libglib2.0-dev=2.66.8-1 libglib2.0-dev-bin=2.66.8-1 libglib2.0-0:i386=2.66.8-1 Zenju tried addressing this for me, but it still does not compile, even with g++-12. So I still have to omit this macro call. UPDATE by Fab Stz on 2022-08-08: Preprocessor output for `::g_object_ref(gicon); ` is: ::((typename std::remove_reference<decltype (gicon)>::type) (g_object_ref) (gicon)); Since commit https://gitlab.gnome.org/GNOME/glib/-/commit/5b2bee3f539056b42c802608f9f00cc9ddd64b79 that is shipped starting from 2.67.0, the macro g_object_ref changed and is also defined when __cplusplus is defined in some circumstances. Removing the scope resolution operator `::` permits the code to build. There remains to check whether this is the correct fix. |
bgstack15 | no | 2022-05-24 | ||
| pkg-config.patch | put pkg-config command into a variable When cross-compiling on debian, the build system dh set the name of the pkg-config command name to use into PKG_CONFIG variable. For armhf, it is PKG_CONFIG=arm-linux-gnueabihf-pkg-config . Since the pkg-config that is installed during cross-compiling is the one of the build-arch (amd64), and not the one of the host-arch (armhf), using `pkg-config` instead of `arm-linux-gnueabihf-pkg-config` would prevent detection of the libraries. . freefilesync (11.23-1) UNRELEASED; urgency=medium . * Initial release. (Closes: #925512) |
Fab Stz <fabstz-it@yahoo.fr> | invalid | self | 2022-08-09 | |
| reproducible-build.patch | Permit reproducible builds by use of SOURCE_DATE_EPOCH Currently the code relies on __DATE__ and __TIME__ macros. . This prevents to have reproducible build because these values changes every time we compile. . To achieve reproducible builds, make use of SOURCE_DATE_EPOCH as proposed on https://reproducible-builds.org . See: - https://reproducible-builds.org/docs/ - https://reproducible-builds.org/docs/source-date-epoch/ |
Fab Stz <fabstz-it@yahoo.fr> | yes | self | 2022-08-11 | |
| wx-config-version.patch | Set wx-config version Useful when there are multiple versions of wx-config installed on the system | Fab Stz <fabstz-it@yahoo.fr> | yes | Debian | 2022-08-12 |