| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| debian/man-getopt-examples.patch | util-linux: getopt(1) should point to where examples are on a Debian system Debian BTS #913049 |
Matthew Vernon <matthew@debian.org> | no | 2018-11-06 | ||
| debian/verbose-tests.patch | verbose-tests Enable verbose tests and print content of failing tests output file. |
Andreas Henriksson <andreas@fatal.se> | no | 2014-07-30 | ||
| debian/hardlink-tests-known-failed.patch | hardlink tests: set known failed sha256 cannot be initialized on some archs / buildds. |
Chris Hofstaedtler <zeha@debian.org> | no | 2022-04-12 | ||
| debian/lsfd-usrbin.patch | Install lsfd into /usr/bin | Chris Hofstaedtler <zeha@debian.org> | no | 2022-04-14 | ||
| debian/sensible-pager.patch | Use sensible-pager | Chris Hofstaedtler <zeha@debian.org> | no | 2022-07-14 | ||
| debian/tests-mark-lsfd-tests-failing-in-sbuild.patch | tests: mark lsfd mkfds-socketpair as failing in sbuild | Chris Hofstaedtler <zeha@debian.org> | no | 2024-02-29 | ||
| debian/tests-mark-fadvise-drop-as-known-failing-on-buildds.patch | tests: mark fadvise/drop as known failing on buildds buildds build on a tmpfs, but this is not visible inside the build environment. |
Chris Hofstaedtler <zeha@debian.org> | no | 2024-04-02 | ||
| upstream/audit-arch.h-add-defines-for-m68k-sh.patch | audit-arch.h: add defines for m68k, sh John Paul Adrian Glaubitz points out that libseccomp needs to release 2.6.0, too. Upstream commit 5ebf0edb0a0531cba801c7791543c610725bf944. |
Chris Hofstaedtler <zeha@debian.org> | no | 2024-04-09 | ||
| upstream/Fix-ul_path_read_buffer.patch | Fix ul_path_read_buffer() The current implementation cuts off the last character of the buffer if there is no trailing newline. (cherry picked from commit 6273c12257973cbd3c59a710049ee8a8027bbbb1) |
Daan De Meyer <daan.j.demeyer@gmail.com> | no | 2024-05-09 | ||
| upstream/libmount-utils-add-pidfs-to-pseudo-fs-list.patch | libmount/utils: add pidfs to pseudo fs list (cherry picked from commit 62cf52f81d5baaba2cfe6dfe00aa4975ebd55d92) |
Mike Yuan <me@yhndnzj.com> | no | 2024-05-11 | ||
| upstream/fsck-warn-if-fsck.-type-not-found-and-device-is-specified.patch | fsck: warn if fsck.<type> not found and device is specified The fsck(8) command prints an error for certain 'required' filesystems, such as extN, if the corresponding fsck.<type> helper is not found. However, for other filesystems, it silently ignores the device. While this behavior is acceptable for the -A option, if a user explicitly specifies the device on the command line, it is probably a good idea to be more verbose and issue a warning that the device will be ignored. The warning is enabled only for interactive mode (only one device specified or -s). Note that some filesystems do not have an fsck utility, so caution is needed when issuing such warnings to prevent the generation of a large number of unwanted entries in system logs, etc." |
Karel Zak <kzak@redhat.com> | no | 2024-02-08 | ||
| upstream-master/libuuid-drop-check-for-HAVE_TLS.patch | libuuid: drop check for HAVE_TLS In the function get_clock() TLS is used unconditionally anyways. |
=?utf-8?q?Thomas_Wei=C3=9Fschuh?= <thomas@t-8ch.de> | no | 2024-05-07 | ||
| upstream-master/libuuid-split-uuidd-cache-into-dedicated-struct.patch | libuuid: split uuidd cache into dedicated struct To clear the struct we need to be able to refer to it by name. |
=?utf-8?q?Thomas_Wei=C3=9Fschuh?= <thomas@t-8ch.de> | no | 2024-05-07 | ||
| upstream-master/libuuid-clear-uuidd-cache-on-fork.patch | libuuid: clear uuidd cache on fork() After fork() the memory of the calling thread is preserved into the new process. This also includes TLS. Make sure to reset the cache after a fork to avoid reuse of cached values. Only the TLS of the thread calling fork() is relevant as that is the only thread that gets forked. New threads will received newly initialized TLS. Fixes https://github.com/util-linux/util-linux/issues/3009 |
=?utf-8?q?Thomas_Wei=C3=9Fschuh?= <thomas@t-8ch.de> | no | 2024-05-07 | ||
| upstream-master/libsmartcols-fix-reduction-stages-use.patch | libsmartcols: fix reduction stages use There is no proper check for the number of reduction stages, so in some cases, the code can loop indefinitely. The patch also fixes 'rc' variable shadowing. |
Karel Zak <kzak@redhat.com> | no | 2024-05-15 | ||
| upstream-master/libmount-Fix-atime-remount-for-new-API.patch | libmount: Fix atime remount for new API All atime settings are mutually exclusive, and the attr_set mask for the mount_setattr() syscall cannot contain multiple MOUNT_ATTR_ atime related options. Unfortunately, during a remount, the list of options is composed of both old and new options. In this case, libmount sets more atime options to the mask. The correct behavior is to use the last atime related option from the list. |
Karel Zak <kzak@redhat.com> | no | 2024-05-14 |