| 1 |
On 10/11/20 10:06 AM, Rich Freeman wrote: |
| 2 |
> On Sun, Oct 11, 2020 at 12:23 PM Daniel Frey <djqfrey@×××××.com> wrote: |
| 3 |
>> |
| 4 |
>> The problem is it's always trying to pull in unstable packages when I |
| 5 |
>> have two slotted kernels in world: |
| 6 |
>> |
| 7 |
>> sys-kernel/gentoo-sources:5.4.48 |
| 8 |
>> sys-kernel/gentoo-sources:5.4.66 |
| 9 |
>> |
| 10 |
>> I tried masking kernels >5.5 but now it's trying to pull in unstable |
| 11 |
>> kernel 5.4.70. |
| 12 |
>> |
| 13 |
>> I do not run unstable kernels, and have two stable kernels installed. |
| 14 |
>> |
| 15 |
>> Why is portage insistent on pulling in sys-kernel/gentoo-sources |
| 16 |
>> (non-slotted) when two slotted entries already exist? |
| 17 |
>> |
| 18 |
> |
| 19 |
> I'm not sure what you mean by "slotted" here. Do you mean stable? |
| 20 |
> |
| 21 |
> The most likely explanation is that you have ACCEPT_KEYWORDS=~amd64 |
| 22 |
> somewhere, or sys-kernel/gentoo-sources somewhere in |
| 23 |
> package.accept_keywords. |
| 24 |
> |
| 25 |
|
| 26 |
OK, I did some poking around. I'm not running ~amd64 but I did discover |
| 27 |
that autounmask had a gentoo-sources entry in it. It was for a specific |
| 28 |
slot though (gentoo-sources:5.4.18), I wonder why it was applying it to |
| 29 |
all gentoo-sources packages? |
| 30 |
|
| 31 |
Nonetheless, I removed the file under portage/package.accept_keywords |
| 32 |
and it's resolved itself. |
| 33 |
|
| 34 |
Dan |
Archives