Re: [gentoo-user] Portage being silly with kernel sources
On 10/11/20 10:06 AM, Rich Freeman wrote: On Sun, Oct 11, 2020 at 12:23 PM Daniel Frey wrote: The problem is it's always trying to pull in unstable packages when I have two slotted kernels in world: sys-kernel/gentoo-sources:5.4.48 sys-kernel/gentoo-sources:5.4.66 I tried masking kernels >5.5 but now it's trying to pull in unstable kernel 5.4.70. I do not run unstable kernels, and have two stable kernels installed. Why is portage insistent on pulling in sys-kernel/gentoo-sources (non-slotted) when two slotted entries already exist? I'm not sure what you mean by "slotted" here. Do you mean stable? The most likely explanation is that you have ACCEPT_KEYWORDS=~amd64 somewhere, or sys-kernel/gentoo-sources somewhere in package.accept_keywords. OK, I did some poking around. I'm not running ~amd64 but I did discover that autounmask had a gentoo-sources entry in it. It was for a specific slot though (gentoo-sources:5.4.18), I wonder why it was applying it to all gentoo-sources packages? Nonetheless, I removed the file under portage/package.accept_keywords and it's resolved itself. Dan
Re: [gentoo-user] Portage being silly with kernel sources
On Sun, 11 Oct 2020 19:37:49 -0400, Rich Freeman wrote: > Ugh, I really need to get my eyes checked. You're right of course... There's no "of course" about it ;-) -- Neil Bothwick An unemployed Court Jester is nobody's fool. pgpx1XFUbTotx.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Portage being silly with kernel sources
On Sun, Oct 11, 2020 at 6:47 PM Neil Bothwick wrote: > > On Sun, 11 Oct 2020 16:58:30 -0400, Rich Freeman wrote: > > > > I too stick to stable sources, partly for the reason you give, partly > > > to avoid excessive reboots and partly because some systems use ZFS. > > > > > > % cat /etc/portage/package.accept_keywords/kernel > > > sys-kernel/gentoo-sources -~amd64 > > > sys-kernel/linux-headers -~amd64 > > > > > > Works for me. > > > > Uh, that will pull unstable kernels, at least as far as Gentoo is > > concerned. They're basically all stable as far as upstream is > > concerned. > > Not at all, it says "-~amd64" not "~amd64", removing the ~amd64 setting > that is used as default. > Ugh, I really need to get my eyes checked. You're right of course... -- Rich
Re: [gentoo-user] Portage being silly with kernel sources
On Sun, 11 Oct 2020 16:58:30 -0400, Rich Freeman wrote: > > I too stick to stable sources, partly for the reason you give, partly > > to avoid excessive reboots and partly because some systems use ZFS. > > > > % cat /etc/portage/package.accept_keywords/kernel > > sys-kernel/gentoo-sources -~amd64 > > sys-kernel/linux-headers -~amd64 > > > > Works for me. > > Uh, that will pull unstable kernels, at least as far as Gentoo is > concerned. They're basically all stable as far as upstream is > concerned. Not at all, it says "-~amd64" not "~amd64", removing the ~amd64 setting that is used as default. The latest kernel I have installed is 5.4.66, which is the latest: % qlist -ICv gentoo-sources sys-kernel/gentoo-sources-5.4.66 sys-kernel/gentoo-sources-5.4.60 -- Neil Bothwick Sigh - An amplifier for people who suffer in silence pgpJbctN69NpI.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Portage being silly with kernel sources
On Sun, Oct 11, 2020 at 1:57 PM Neil Bothwick wrote: > > I too stick to stable sources, partly for the reason you give, partly to > avoid excessive reboots and partly because some systems use ZFS. > > % cat /etc/portage/package.accept_keywords/kernel > sys-kernel/gentoo-sources -~amd64 > sys-kernel/linux-headers -~amd64 > > Works for me. Uh, that will pull unstable kernels, at least as far as Gentoo is concerned. They're basically all stable as far as upstream is concerned. I also run zfs just about everywhere so I tend to stick to longterm kernels. I just pull them directly from git - there is a stable repo and a branch for every longterm, so all I need to do is a git pull and I get the latest one. I tend to like to manage this myself on systems where I'm using zfs, btrfs, or nvidia binary modules. -- Rich
Re: [gentoo-user] Portage being silly with kernel sources
On Sun, 11 Oct 2020 09:23:29 -0700, Daniel Frey wrote: > I have nvidia-drivers installed. It has a dependency to > virtual/linux-sources. > > The problem is it's always trying to pull in unstable packages when I > have two slotted kernels in world: > > sys-kernel/gentoo-sources:5.4.48 > sys-kernel/gentoo-sources:5.4.66 > > I tried masking kernels >5.5 but now it's trying to pull in unstable > kernel 5.4.70. Are you running ~arch globally? If so, the simple solution is to turn it off for kernel-sources. > I do not run unstable kernels, and have two stable kernels installed. > > Why is portage insistent on pulling in sys-kernel/gentoo-sources > (non-slotted) when two slotted entries already exist? Because it will always try to install the latest version that fits all your requirements. > I do not want to install unstable kernel sources as I don't use them > and am trying to spare the thousands of unnecessary writes on my SSD. > Whenever I update I check to see if there's a new stable kernel > available manually and update to it if needed. I too stick to stable sources, partly for the reason you give, partly to avoid excessive reboots and partly because some systems use ZFS. % cat /etc/portage/package.accept_keywords/kernel sys-kernel/gentoo-sources -~amd64 sys-kernel/linux-headers -~amd64 Works for me. -- Neil Bothwick (A)bort, (R)etry, (P)retend this never happened... pgpQ9XlaGvts3.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Portage being silly with kernel sources
Portage is neither silly nor smart. Will do what will be told to do. By default is tracking stable packages unless you have specified otherwise either by changing universally the tracking $ARCH in make.conf or per package in package.accept_keywords file or directory. I would guess that you've got "sys-kernel/gentoo-sources" somewhere into package.accept_keywords in the past and forgot about it. If gentoo-sources has not been manually overridden and portage complains about it then another package depends on the unstable version of gentoo-sources and trying to pull it, so you have to find which one is it.
Re: [gentoo-user] Portage being silly with kernel sources
On Sun, Oct 11, 2020 at 12:23 PM Daniel Frey wrote: > > The problem is it's always trying to pull in unstable packages when I > have two slotted kernels in world: > > sys-kernel/gentoo-sources:5.4.48 > sys-kernel/gentoo-sources:5.4.66 > > I tried masking kernels >5.5 but now it's trying to pull in unstable > kernel 5.4.70. > > I do not run unstable kernels, and have two stable kernels installed. > > Why is portage insistent on pulling in sys-kernel/gentoo-sources > (non-slotted) when two slotted entries already exist? > I'm not sure what you mean by "slotted" here. Do you mean stable? The most likely explanation is that you have ACCEPT_KEYWORDS=~amd64 somewhere, or sys-kernel/gentoo-sources somewhere in package.accept_keywords. -- Rich
[gentoo-user] Portage being silly with kernel sources
This is one of those frustrating times where portage is trying to do something silly. I have nvidia-drivers installed. It has a dependency to virtual/linux-sources. The problem is it's always trying to pull in unstable packages when I have two slotted kernels in world: sys-kernel/gentoo-sources:5.4.48 sys-kernel/gentoo-sources:5.4.66 I tried masking kernels >5.5 but now it's trying to pull in unstable kernel 5.4.70. I do not run unstable kernels, and have two stable kernels installed. Why is portage insistent on pulling in sys-kernel/gentoo-sources (non-slotted) when two slotted entries already exist? I do not want to install unstable kernel sources as I don't use them and am trying to spare the thousands of unnecessary writes on my SSD. Whenever I update I check to see if there's a new stable kernel available manually and update to it if needed. Dan
