FS#59500 - [linux] New PKBUILD for Kernel 4.7.11 does not support having a custom kernel installed w/ stock
Attached to Project:
Arch Linux
Opened by Sebastian Jug (jugs) - Tuesday, 31 July 2018, 19:55 GMT
Last edited by Jan Alexander Steffens (heftig) - Wednesday, 01 August 2018, 07:28 GMT
Opened by Sebastian Jug (jugs) - Tuesday, 31 July 2018, 19:55 GMT
Last edited by Jan Alexander Steffens (heftig) - Wednesday, 01 August 2018, 07:28 GMT
|
Details
Description:
In 4.17.10 I was able to change pkgbase=linux-custom and then compile and install my custom kernel of the same version (linux-4.17.10 & linux-custom-4.17.10). Now in 4.17.11, I am unable to install both kernels of the same version as when I try to install it the modules directory is the same between the two builds and there is a conflict. Additional info: # pacman -S linux *:: Proceed with installation? [Y/n] y (1/1) checking keys in keyring (1/1) checking package integrity (1/1) loading package files (1/1) checking for file conflicts error: failed to commit transaction (conflicting files) linux: /usr/lib/modules/4.17.11-arch1/build/vmlinux exists in filesystem (owned by linux-custom) linux: /usr/lib/modules/4.17.11-arch1/extramodules exists in filesystem (owned by linux-custom) linux: /usr/lib/modules/4.17.11-arch1/kernel/arch/x86/crypto/aes-x86_64.ko.xz exists in filesystem (owned by linux-custom) linux: /usr/lib/modules/4.17.11-arch1/kernel/arch/x86/crypto/aesni-intel.ko.xz exists in filesystem (owned by linux-custom) linux: /usr/lib/modules/4.17.11-arch1/kernel/arch/x86/crypto/blowfish-x86_64.ko.xz exists in filesystem (owned by linux-custom) linux: /usr/lib/modules/4.17.11-arch1/kernel/arch/x86/crypto/cast5-avx-x86_64.ko.xz exists in filesystem (owned by linux-custom) linux: /usr/lib/modules/4.17.11-arch1/kernel/arch/x86/crypto/cast6-avx-x86_64.ko.xz exists in filesystem (owned by linux-custom) linux: /usr/lib/modules/4.17.11-arch1/kernel/arch/x86/crypto/chacha20-x86_64.ko.xz exists in filesystem (owned by linux-custom) linux: /usr/lib/modules/4.17.11-arch1/kernel/arch/x86/crypto/crc32-pclmul.ko.xz exists in filesystem (owned by linux-custom) linux: /usr/lib/modules/4.17.11-arch1/kernel/arch/x86/crypto/crc32c-intel.ko.xz exists in filesystem (owned by linux-custom) linux: /usr/lib/modules/4.17.11-arch1/kernel/arch/x86/crypto/crct10dif-pclmul.ko.xz exists in filesystem (owned by linux-custom) linux: /usr/lib/modules/4.17.11-arch1/kernel/arch/x86/crypto/des3_ede-x86_64.ko.xz exists in filesystem (owned by linux-custom) Steps to reproduce: 1) Install stock arch linux kernel 4.17.11+ 2) Follow https://wiki.archlinux.org/index.php/Kernels/Arch_Build_System to checkout and build linux-custom 4.7.11+ kernel 3) Install linux-custom 4) See module directory conflict when trying to install |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Wednesday, 01 August 2018, 07:28 GMT
Reason for closing: Fixed
Additional comments about closing: 4.17.11.arch1-1
Wednesday, 01 August 2018, 07:28 GMT
Reason for closing: Fixed
Additional comments about closing: 4.17.11.arch1-1
(The issue is that the special handling of CONFIG_LOCALVERSION got mislaid when moving things over to git.)