c/zfsonlinux
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
b48cfd2b15
zfsonlinux/debian/patches/series

13 lines
634 B
Plaintext
Raw Normal View History

zfs/debian: add packaging files based on Debian's packaging work, but simplified: - no DKMS - no dracut - no udebs and remove old patches which were based on top of Debian's packaging. Reviewed-by: Stoiko Ivanov <s.ivanov@proxmox.com> Tested-by: Stoiko Ivanov <s.ivanov@proxmox.com> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
2019-01-30 17:26:24 +03:00
0001-Check-for-META-and-DCH-consistency-in-autoconf.patch
rebase patches on top of zfs-0.8.0 rebase done with export-patchqueue and adapted to new 0.8 release Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
2019-05-24 00:11:30 +03:00
0002-always-load-ZFS-module-on-boot.patch
0003-Fix-the-path-to-the-zed-binary-on-the-systemd-unit.patch
update submodule and patches to 0.8.2 Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
2019-09-28 09:12:00 +03:00
0004-import-with-d-dev-disk-by-id-in-scan-service.patch
0005-Enable-zed-emails.patch
Preserve /etc/zfs/zed.d configuration on upgrade Of the zedlet scripts shipped by upstream, a subset are enabled by default, by creating symlinks in /etc/zfs/zed.d. These symlinks are shipped in the zfs-zed package. dpkg, however, does not support conffile handling of symlinks, and therefore any changes (removals) to the symlinks are not preserved on package upgrade. To address this policy violation, we: 1. During package build, create a list of enabled-by-default zedlets, instead of creating symlinks. 2. On package removal, identify all enabled-by-default zedlets whose symlinks do not exist (i.e., were removed by the user). This is done by creating "whiteout" links to /dev/null in their place). 3. On package installation, create links to enabled-by-default zedlets UNLESS there is already a file there (i.e., abort if there is a whiteout link). 4. We also clean up broken symlinks to removed zedlets at package postinst. (cherry picked and adapted from 5cee380324d74e640d5dd7a360faba3994c8007f [0]) [0] https://salsa.debian.org/zfsonlinux-team/zfs.git Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
2020-03-20 19:28:43 +03:00
0006-dont-symlink-zed-scripts.patch
update ZFS submodule to 2.1.11 and refresh patches Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
2023-04-20 10:26:09 +03:00
0007-Add-systemd-unit-for-importing-specific-pools.patch
0008-Patch-move-manpage-arcstat-1-to-arcstat-8.patch
update submodule and patches for 2.2.0 Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
2023-10-15 13:08:06 +03:00
0009-arc-stat-summary-guard-access-to-l2arc-MFU-MRU-stats.patch
update zfs submodule to 2.2.2 and refresh patches the removed patches were cherry-picks, which are included in 2.2.2 Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
2023-12-04 14:27:51 +03:00
0010-Fix-nfs_truncate_shares-without-etc-exports.d.patch
0011-zpool-status-tighten-bounds-for-noalloc-stat-availab.patch
fix #5288: cherry-pick fix for udev-partition links > 16 If a zvol has more than 15 partitions, the minor device number exhausts the slot count reserved for partitions next to the zvol itself. As a result, the minor number cannot be used to determine the partition number for the higher partition, and doing so results in wrong named symlinks being generated by udev. Since the partition number is encoded in the block device name anyway, let's just extract it from there instead. For upstream issue and PR discussion see: https://github.com/openzfs/zfs/pull/15970 https://github.com/openzfs/zfs/issues/15904 Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com> Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
2024-03-06 16:24:36 +03:00
0012-udev-correctly-handle-partition-16-and-later.patch
Reference in New Issue Copy Permalink