| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| fix-spelling.patch | Fix a few typos on the manpages and source code.=================================================================== | Giovani Augusto Ferreira <giovani@debian.org> | no | 2016-07-07 | ||
| fix-ruby3.0.patch | [PATCH] Fix build failure with ruby 3.0 With ruby 3.0, build fails like: ``` /builddir/build/BUILD/dislocker-0.7.3/src/config.c: In function 'setclearkey': /builddir/build/BUILD/dislocker-0.7.3/src/config.c:59:13: error: expected identifier or '(' before numeric constant 59 | int true = TRUE; ``` This is because ruby 3.0 header will include <stdbool.h>, which defines "true"/"false", ref: https://pubs.opengroup.org/onlinepubs/009695399/basedefs/stdbool.h.html So using "true" as variable must be renamed. |
Mamoru TASAKA <mtasaka@fedoraproject.org> | no | 2021-01-07 | ||
| wrong-libdir.patch | don't install don't install to /usr/lib64 just because it exists in build env This package fails to build in Ubuntu and in Debian because both are using usrmerge in their build environments, which causes /usr/lib64 to exist and the upstream build system to wrongly install files to it instead of to /usr/lib. Patch the build system to never use /usr/lib64 as this is always wrong for a Debian package. =================================================================== |
Steve Langasek <steve.langasek@ubuntu.com> | yes | 2022-08-22 |