how to actually use custom patches? do i need to change some value or set some env var?
I did add my patches to the base folder and to the patches files, updated checksums but they were not applied during build...
Git Clone URL: | https://aur.archlinux.org/linux-git.git (read-only, click to copy) |
---|---|
Package Base: | linux-git |
Description: | The Linus Torvalds' Mainline Linux kernel and modules |
Upstream URL: | https://www.kernel.org |
Keywords: | git kernel linux |
Licenses: | GPL-2.0-only |
Provides: | KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE |
Replaces: | virtualbox-guest-modules-arch, wireguard-arch |
Submitter: | jonathanio |
Maintainer: | osimarr |
Last Packager: | osimarr |
Votes: | 13 |
Popularity: | 0.000804 |
First Submitted: | 2019-12-22 10:10 (UTC) |
Last Updated: | 2024-07-20 19:34 (UTC) |
how to actually use custom patches? do i need to change some value or set some env var?
I did add my patches to the base folder and to the patches files, updated checksums but they were not applied during build...
@markboston if you build the package as is, it will compile the Linux mainline. This branch is not always stable, as it's used as a development branch. If you need a more stable image, you can use a Linux stable branch instead.
After you install a clean compilation, there will be an installed file /etc/linux-git/remote that you can edit and set the remote to the stable repository on the REMOTE variable, as explained in a comment on that file. And then the kernel version can be set on the COMMIT variable. The latest stable version you can retrieve from https://www.kernel.org/
As of today, you could set the remote file as below to get the latest stable:
REMOTE="stable/linux"
COMMIT="v6.6.10"
Then rebuild the linux-git package to compile the configured version.
i get a black screen on booting. is there another package i need to get this to boot?
im getting an error when trying to import the gpg key. no data.
In case it was missed, the /doesnt/exist message is the intentional output caused by a sed trick applied to the Makefile, per Arch upstream, to prevent it from automatically running depmod during the build stage, since pacman hooks run that post-install.
Please remove replaces
directive, in accordance with AUR submission guidelines.
Thanks for all the reports and fix tips. All build issues and versioning problem are fixed and PKGBUILD + config are updated to newest Arch Linux kernel package.
Strange issue on latest git. Complains "/doesnt/exist' is required??
No patches and just following upstream master without any tags.
DEPMOD /home/parker/.cache/paru/clone/linux-git/pkg/linux-git/usr/lib/modules/6.5.0-1-git-12107-g7ba2090ca64e
Warning: 'make modules_install' requires /doesnt/exist. Please install it.
This is probably in the kmod package.
rm: cannot remove '/home/parker/.cache/paru/clone/linux-git/pkg/linux-git/usr/lib/modules/6.5.0-1-git-12107-g7ba2090ca64e/source': No such file or directory
==> ERROR: A failure occurred in package_linux-git().
Aborting...
error: failed to build 'linux-git-v6.4.rc3.r291.4e893b5aa4ac-1':
error: packages failed to build: linux-git-v6.4.rc3.r291.4e893b5aa4ac-1
EDIT: Issue referenced here https://aur.archlinux.org/packages/linux-next-git#comment-931562
Fix is to remove source
from the cleanup rm
For building in clean chroot I had to add 'python' to makedepends or else make fails with
/usr/bin/env: ‘python3’: No such file or directory
Pinned Comments
osimarr commented on 2023-05-07 22:27 (UTC) (edited on 2023-05-12 04:05 (UTC) by osimarr)
Hi. Since the package became an orphan, I adopted it to continue what I actively maintain on https://aur.archlinux.org/pkgbase/linux-mainline-git, now on this AUR package.
The build script and config file will be up-to-date with Arch's official Linux package unless an update is required to be functional.
But I intentionally removed the documentation package because it consumes too much building time.
This package supports certain customization if compiled by the user. Check for the README file inside the package repo, or the .INSTALL message after package installation to learn how.