Summary: | sys-apps/systemd-250.3 with sys-kernel/linux-headers-5.17 ERROR: Problem encountered: found unknown filesystem(s) defined in kernel headers: | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | HougeLangley <hougelangley1987> |
Component: | Current packages | Assignee: | Gentoo systemd Team <systemd> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://github.com/systemd/systemd/pull/22312 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build_log |
Description
HougeLangley
2022-02-07 16:37:55 UTC
Created attachment 764533 [details]
build_log
Please provide emerge --info. (In reply to Mike Gilbert from comment #2) > Please provide emerge --info. Sorry for that. I will upload when compile done. I really just want to confirm what version of sys-kernel/linux-headers is installed in your environment. Hi HougeLangley, I think you must be using my loongson-overlay on a LoongArch system, because that's the only way you'll encounter a 5.17 linux-headers I could think of: https://github.com/xen0n/loongson-overlay/blob/master/sys-kernel/linux-headers/linux-headers-5.17_rc2_p20220124.ebuild to be exact (and you're being exceptionally quick to pick up my changes XD). As the problem doesn't exist in ::gentoo, I think the technical support burden falls onto me instead, and this bug should probably closed as INVALID. I'll have to re-fork systemd to fix this problem, most probably. EDIT: Indeed this is a LoongArch system with pretty stock loongson-overlay configuration, as can be seen in the build log. The linked systemd PR could be preemptively incorporated, though. Just in case the fix didn't get incorporated in systemd-stable in time before linux-5.17 is officially cut. Yeah, please make a point of mentioning when filing bugs if you know anything is interesting about your system ;) (And include --info). Sorry, I have to install systemd-9999 instead. If the problem is caused by a prerelease version of linux-headers, we will run into it in Gentoo eventually. Bug reports like this are a good thing, so long as you provide sufficient information. Let's keep this open. |