View previous topic :: View next topic |
Author |
Message |
an7h Tux's lil' helper
Joined: 10 Jan 2018 Posts: 89
|
Posted: Fri Jun 22, 2018 12:21 am Post subject: Issues with patches (Gentoo Live minimal & SysRescueCd) |
|
|
Can somebody please tell me any reasons why wouldn't user patches be applied in a live environment with a Gentoo Minimal or SysRescueCd iso? I've done everything according to this article https://wiki.gentoo.org/wiki//etc/portage/patches , but whatever I do is 'ignored' somehow during compilation. I know I'm doing something wrong, but I don't understand what it is.
I'd also like to add that user patches are applied if I'm doing everything from an installed system like the one I'm using atm or on a usb flash drive. _________________ If dreams were horses, beggars would ride. |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21633
|
Posted: Fri Jun 22, 2018 1:46 am Post subject: |
|
|
There are many reasons, but they are all variants of "You did something wrong." Without knowing what you executed, we cannot tell what you may have done wrong. Please post the output of find /etc/portage/ -ls and the build log of an affected package. You can truncate the log at the start of upstream's configure/make process. We only need to see the Gentoo preparatory stages. |
|
Back to top |
|
|
an7h Tux's lil' helper
Joined: 10 Jan 2018 Posts: 89
|
Posted: Fri Jun 22, 2018 8:00 am Post subject: |
|
|
Code: | (chroot) sysresccd ~ # find /etc/portage/ -ls
123084 1 dr-x------ 9 root root 12 Jun 22 02:19 /etc/portage/
362069 32 -rw-r--r-- 1 root root 874 Jun 22 02:19 /etc/portage/bashrc
123095 32 -rw-r--r-- 1 root root 563 Jun 22 02:05 /etc/portage/make.conf
286284 0 lrwxrwxrwx 1 root root 59 Jun 22 02:11 /etc/portage/make.profile -> ../../usr/portage/profiles/default/linux/amd64/17.0/desktop
123092 1 drwxr-xr-x 2 root root 3 Jun 22 02:11 /etc/portage/package.accept_keywords
286288 32 -rw-r--r-- 1 root root 38 Jun 22 02:11 /etc/portage/package.accept_keywords/ck-sources
123093 1 drwxr-xr-x 2 root root 2 Jun 15 04:09 /etc/portage/package.mask
362049 1 drwxr-xr-x 3 root root 3 Jun 22 02:18 /etc/portage/patches
362050 1 drwxr-xr-x 3 root root 3 Jun 22 02:18 /etc/portage/patches/sys-kernel
362051 1 drwxr-xr-x 2 root root 4 Jun 22 02:18 /etc/portage/patches/sys-kernel/ck-sources-4.16.16
362052 192 -r-------- 1 root root 178961 Jun 22 02:18 /etc/portage/patches/sys-kernel/ck-sources-4.16.16/uksm-4.16.patch
362053 2432 -r-------- 1 root root 2470195 Jun 22 02:18 /etc/portage/patches/sys-kernel/ck-sources-4.16.16/reiser4-for-4.16.0.patch
123088 1 drwxr-xr-x 2 root root 4 Jun 15 02:50 /etc/portage/repo.postsync.d
123089 32 -rw-r--r-- 1 root root 1656 May 25 19:15 /etc/portage/repo.postsync.d/example
123090 32 -rwxr-xr-x 1 root root 153 Feb 23 03:28 /etc/portage/repo.postsync.d/q-reinit
124888 1 drwxr-xr-x 2 root root 3 Jun 22 02:02 /etc/portage/repos.conf
124889 32 -rw-r--r-- 1 root root 654 Jun 22 02:02 /etc/portage/repos.conf/gentoo.conf
123085 1 drwxr-xr-x 3 root root 3 Jun 15 02:45 /etc/portage/savedconfig
123086 1 drwxr-xr-x 2 root root 3 Jun 15 02:45 /etc/portage/savedconfig/sys-apps
123087 32 -rw-r--r-- 1 root root 27423 Feb 23 02:37 /etc/portage/savedconfig/sys-apps/busybox-1.28.0
123094 1 drwxr-xr-x 2 root root 3 Jun 22 02:12 /etc/portage/package.use
286289 32 -rw-r--r-- 1 root root 35 Jun 22 02:12 /etc/portage/package.use/ck-sources |
Code: | (chroot) sysresccd /usr/portage/sys-kernel/ck-sources # ebuild ck-sources-4.16.16.ebuild clean prepare
* linux-4.16.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ]
* genpatches-4.16-17.base.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ]
* genpatches-4.16-17.extras.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ]
* genpatches-4.16-17.experimental.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ]
* patch-4.16-ck1.xz BLAKE2B SHA512 size ;-) ... [ ok ]
* checking ebuild checksums ;-) ... [ ok ]
* checking miscfile checksums ;-) ... [ ok ]
>>> Preparing to unpack ...
>>> Unpacking source...
>>> Unpacking linux-4.16.tar.xz to /var/tmp/portage/sys-kernel/ck-sources-4.16.16/work
>>> Unpacking genpatches-4.16-17.base.tar.xz to /var/tmp/portage/sys-kernel/ck-sources-4.16.16/work/patches/000001
>>> Unpacking genpatches-4.16-17.extras.tar.xz to /var/tmp/portage/sys-kernel/ck-sources-4.16.16/work/patches/000002
>>> Unpacking genpatches-4.16-17.experimental.tar.xz to /var/tmp/portage/sys-kernel/ck-sources-4.16.16/work/patches/000003
* Excluding Patch #5000_enable-additional-cpu-optimizations-for-gcc.patch ... [ ok ]
* Applying 1000_linux-4.16.1.patch (-p1) ... [ ok ]
* Applying 1001_linux-4.16.2.patch (-p1) ... [ ok ]
* Applying 1002_linux-4.16.3.patch (-p1) ... [ ok ]
* Applying 1003_linux-4.16.4.patch (-p1) ... [ ok ]
* Applying 1004_linux-4.16.5.patch (-p1) ... [ ok ]
* Applying 1005_linux-4.16.6.patch (-p1) ... [ ok ]
* Applying 1006_linux-4.16.7.patch (-p1) ... [ ok ]
* Applying 1007_linux-4.16.8.patch (-p1) ... [ ok ]
* Applying 1008_linux-4.16.9.patch (-p1) ... [ ok ]
* Applying 1009_linux-4.16.10.patch (-p1) ... [ ok ]
* Applying 1010_linux-4.16.11.patch (-p1) ... [ ok ]
* Applying 1011_linux-4.16.12.patch (-p1) ... [ ok ]
* Applying 1012_linux-4.16.13.patch (-p1) ... [ ok ]
* Applying 1013_linux-4.16.14.patch (-p1) ... [ ok ]
* Applying 1014_linux-4.16.15.patch (-p1) ... [ ok ]
* Applying 1015_linux-4.16.16.patch (-p1) ... [ ok ]
* Applying 1500_XATTR_USER_PREFIX.patch (-p1) ... [ ok ]
* Applying 1510_fs-enable-link-security-restrictions-by-default.patch (-p1) ... [ ok ]
* Applying 2300_enable-poweroff-on-Mac-Pro-11.patch (-p1) ... [ ok ]
* Applying 2500_usb-storage-Disable-UAS-on-JMicron-SATA-enclosure.patch (-p1) ... [ ok ]
* Applying 2600_enable-key-swapping-for-apple-mac.patch (-p1) ... [ ok ]
* Applying 2900_dev-root-proc-mount-fix.patch (-p1) ... [ ok ]
* Applying 4200_fbcondecor.patch (-p1) ... [ ok ]
* Applying 4400_alpha-sysctl-uac.patch (-p1) ... [ ok ]
* Applying 4567_distro-Gentoo-Kconfig.patch (-p1) ... [ ok ]
* Applying 5010_enable-additional-cpu-optimizations-for-gcc.patch (-p1) ... [ ok ]
* Applying patch-4.16-ck1.patch (-p1) ... [ ok ]
>>> Source unpacked in /var/tmp/portage/sys-kernel/ck-sources-4.16.16/work
>>> Preparing source in /var/tmp/portage/sys-kernel/ck-sources-4.16.16/work/linux-4.16.16-ck ...
>>> Source prepared. |
Here you go. I assume this is enough information? _________________ If dreams were horses, beggars would ride. |
|
Back to top |
|
|
Yamakuzure Advocate
Joined: 21 Jun 2006 Posts: 2284 Location: Adendorf, Germany
|
Posted: Fri Jun 22, 2018 8:47 am Post subject: |
|
|
From the look of it, it should work. The ebuild calls "kernel-2_src_prepare()", which itself calls "eapply_user", and your patches are in the right location.
You could try to rename "/etc/portage/patches/sys-kernel/ck-sources-4.16.16" to "/etc/portage/patches/sys-kernel/ck-sources", but that is a shot in the dark... _________________ Important German:- "Aha" - German reaction to pretend that you are really interested while giving no f*ck.
- "Tja" - German reaction to the apocalypse, nuclear war, an alien invasion or no bread in the house.
|
|
Back to top |
|
|
freke l33t
Joined: 23 Jan 2003 Posts: 977 Location: Somewhere in Denmark
|
Posted: Fri Jun 22, 2018 4:42 pm Post subject: |
|
|
And running as root? (I notice the patches are readable by root only) |
|
Back to top |
|
|
an7h Tux's lil' helper
Joined: 10 Jan 2018 Posts: 89
|
Posted: Fri Jun 22, 2018 8:21 pm Post subject: |
|
|
@Yamakuzure
nope, doesn't work anyway.
@freke
yeah, running as root.
Guess, I'll just make a custom install on my flash drive, because for some reason that's the only way it works. Hmmmmm... _________________ If dreams were horses, beggars would ride. |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21633
|
Posted: Sat Jun 23, 2018 12:13 am Post subject: |
|
|
an7h wrote: | @freke
yeah, running as root. | Are you sure? Normally, Portage will change to an unprivileged user for most of its work. If you did not disable that, then, no, you are not running as root (nor should you be). Did you try fixing the permissions? The patches need to be readable by the user that Portage uses, and it's generally safe to make them world readable.
On the bright side, the Wiki page you cite completely fails to mention that you need to do this. So while it was incorrect for you to make the files root-only, you did not deviate from the instructions. |
|
Back to top |
|
|
an7h Tux's lil' helper
Joined: 10 Jan 2018 Posts: 89
|
Posted: Sat Jun 23, 2018 5:46 pm Post subject: |
|
|
@Hu
Okay, it would be good to know what this is all about either way. _________________ If dreams were horses, beggars would ride. |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21633
|
Posted: Sat Jun 23, 2018 7:52 pm Post subject: |
|
|
If you solve it, please post back with the explanation. I expect it will be as I described above: a permissions problem. |
|
Back to top |
|
|
an7h Tux's lil' helper
Joined: 10 Jan 2018 Posts: 89
|
Posted: Wed Jun 27, 2018 12:17 pm Post subject: |
|
|
Yeah, I should make sure. I'm going to do it in a short while. I thought about it, and most likely this is really what is causing my 'problem'. I'll check again and get back to you guys. _________________ If dreams were horses, beggars would ride. |
|
Back to top |
|
|
an7h Tux's lil' helper
Joined: 10 Jan 2018 Posts: 89
|
Posted: Sun Jul 22, 2018 4:48 pm Post subject: |
|
|
Okay, now I checked and it was a simple file permissions issue for the /etc/portage/bashrc file. I changed it and now it patches are being applied just fine.
Thanks for the help, guys! _________________ If dreams were horses, beggars would ride. |
|
Back to top |
|
|
|