| Summary: | sys-fs/zfs-kmod-0.8.2 should set ZFS_KERNEL_COMPAT="5.4" | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | cyshei |
| Component: | Current packages | Assignee: | Richard Yao (RETIRED) <ryao> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | gyakovlev |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
cyshei
2019-12-06 07:42:01 UTC
I usually refer to this file to determine compatibility https://github.com/zfsonlinux/zfs/blob/zfs-0.8.2/META and it says 5.3 but yeah I see commit message says compatible up to 5.4 I'll need to investigate it a bit before bumping compat. There've been nasty bugs related to bumping compat in the past. also, ebuild contains a magic variable: ZFS_KERNEL_COMPAT_OVERRIDE you can use the following command ZFS_KERNEL_COMPAT_OVERRIDE=5.4 emerge zfs-kmod no need to copy ebuild to local overlay. I just found Brian's comment here, which explains why the META says 5.3 while the release notes say 5.4: https://github.com/zfsonlinux/zfs/pull/9654#issuecomment-560537636 The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c032fdd9d218f5709529ee78f25188cba9c69ebc commit c032fdd9d218f5709529ee78f25188cba9c69ebc Author: Georgy Yakovlev <gyakovlev@gentoo.org> AuthorDate: 2019-12-06 21:46:35 +0000 Commit: Georgy Yakovlev <gyakovlev@gentoo.org> CommitDate: 2019-12-06 21:48:42 +0000 sys-fs/zfs-kmod: revbump 0.8.2, linux-5.4 compatible Closes: https://bugs.gentoo.org/702144 https://github.com/zfsonlinux/zfs/pull/9654#issuecomment-560537636 Package-Manager: Portage-2.3.79, Repoman-2.3.17 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org> sys-fs/zfs-kmod/{zfs-kmod-0.8.2.ebuild => zfs-kmod-0.8.2-r1.ebuild} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) thanks for finding confirmation! rebvumped ebuild so everyone who have 5.4 kernel masked see the bump and unmask it. |