Package Details: linux-pf 6.15.pf1-1

Git Clone URL: https://aur.archlinux.org/linux-pf.git (read-only, click to copy)
Package Base: linux-pf
Description: The pf-kernel and modules
Upstream URL: https://pfkernel.natalenko.name
Keywords: bbr bbr3 bbrv3 kernel linux linux-pf ovpn-dco pf-kernel v4l2loopback
Licenses: GPL-2.0-only
Provides: KSMBD-MODULE, linux-pf, NTFS3-MODULE, NTSYNC-MODULE, OVPN-MODULE, V4L2LOOPBACK-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Replaces: virtualbox-guest-modules-arch, wireguard-arch
Submitter: nous
Maintainer: post-factum
Last Packager: post-factum
Votes: 209
Popularity: 0.004913
First Submitted: 2011-07-24 12:01 (UTC)
Last Updated: 2025-05-31 15:59 (UTC)

Dependencies (20)

Required by (13)

Sources (2)

Pinned Comments

post-factum commented on 2023-09-25 20:30 (UTC) (edited on 2024-10-08 14:21 (UTC) by post-factum)

Official binary builds for various x86_64 ISA levels are available here.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 106 Next › Last »

ZhangHua commented on 2023-10-02 03:36 (UTC)

@post-factum It seems that there is a version mismatch? According to your changelog, v6.5-pf4 is kernel 6.5.5 but the pkgver is 6.5.4 in PKGBUILD. What's more, please consider adding pkgrel in kernelrelease, you can see linux package for more info.

ZhangHua commented on 2023-09-29 01:33 (UTC)

@post-factum It is OK now. Thanks for your hardworking. :-)

post-factum commented on 2023-09-28 15:31 (UTC)

What about now?

ZhangHua commented on 2023-09-28 11:03 (UTC)

@post-factum I don't know if it should stay in provides, but it should not stay in replaces indeed. Because pacman will always ask me if replacing linux-pf with overlays/linux-pf. The repository overlays is generated by paru for keeping built packages. On AUR, we mainly create various AUR package for package variants, they technically are not related to, just like linux-pf and linux-pf-pfkernel. I think this may be the main reason. So maybe if we need keeping linux-pf in provides does not matter, for making less changes, I agree with keeping linux-pf in provides.

post-factum commented on 2023-09-28 08:20 (UTC)

This very PKGBUILD is used for building binary packages with different name suffixes in OBS, for instance, linux-pf-generic. So I guess this should stay?

ZhangHua commented on 2023-09-28 00:45 (UTC)

@post-factum It seems that there is still having linux-pf in replaces and provides. Letting linux-pf in replaces will cause pacman always trying to use linux-pf replace linux-pf, you can use paru's ChrootBuild feature to test this, paru will put built AUR packages in a local repository, this problem will be noticed. Letting linux-pf in provides is also useless as the package's name is linux-pf, it absolutely provides itself.

post-factum commented on 2023-09-27 17:53 (UTC)

Actually, I've checked customisation for μ-arches in your pkg, it doesn't look invasive, so I've picked it up as well: https://codeberg.org/pf-kernel/release-scripts/commit/c286e1e8cc5ccb6daeeade36711fb3f5d739ae25

post-factum commented on 2023-09-27 11:23 (UTC)

Yes, that sounds like a good idea. Thanks, I'll consider that for the next update.

ZhangHua commented on 2023-09-27 10:22 (UTC)

@post-factum Following linux package should be a good idea. However, setting -dkms packages to conflicts is not good as we may install other kernels that need those -dkms packages to work. I think we may simply remove them from replaces? If you installed a -dkms package which has kernel module that is provided by linux-pf kernel, the kernel module shipped by kernel will be disabled by dkms, so I think we can simply remove this limit, people who want to use those -dkms modules can also install related packages directly.

post-factum commented on 2023-09-27 08:35 (UTC)

I think I should keep replaces for at least virtualbox-guest-modules-arch wireguard-arch as the linux package do, right? Should I move -dkms packages only to conflicts then?

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 106 Next › Last »