I found a old email from Neil, hope you see this, and I think I followed
it correctly but maybe I either missed something or things have changed
since those instructions were posted. What I'm wanting to do, update gentoo-sources manually and remove them manually as well but running
emerge -auDN world doesn't pull in newer versions and --depclean leaves
the older versions alone as well. Following the email info, I ended up
with this:
root@fireball / # cat /etc/portage/sets.conf
[kernels]
class = portage.sets.dbapi.OwnerSet
world-candidate = False
files = /usr/src
root@fireball / # cat /etc/portage/sets/kernels
sys-kernel/gentoo-sources
root@fireball / #
and this I've tried with and without:
root@fireball / # cat /var/lib/portage/world_sets
kernels
root@fireball / #
This is what I get tho:
root@fireball / # emerge -auDN world
Error during set creation: Redefinition of set 'kernels' (sections: 'usersets', 'kernels')
On Thu, 3 Feb 2022 17:49:59 -0600, Dale wrote:
I found a old email from Neil, hope you see this, and I think I followedI do this.
it correctly but maybe I either missed something or things have changed
since those instructions were posted. What I'm wanting to do, update
gentoo-sources manually and remove them manually as well but running
emerge -auDN world doesn't pull in newer versions and --depclean leaves
the older versions alone as well. Following the email info, I ended up
with this:
root@fireball / # cat /etc/portage/sets.conf
[kernels]
class = portage.sets.dbapi.OwnerSet
world-candidate = False
files = /usr/src
root@fireball / # cat /etc/portage/sets/kernelsBut not this.
sys-kernel/gentoo-sources
root@fireball / #
and this I've tried with and without:If you add the set to world_sets, it's the same as putting the kernel in world.
root@fireball / # cat /var/lib/portage/world_sets
kernels
root@fireball / #
This is what I get tho:That's because there's already a set called kernels - emerge --list-sets
root@fireball / # emerge -auDN world
Error during set creation: Redefinition of set 'kernels' (sections:
'usersets', 'kernels')
will show you all of them. Just rename your set.
On Fri, 4 Feb 2022 11:44:01 -0600, Dale wrote:
These are the packages that would be merged, in order:It is probably being pulled in as a dependency of virtual/linux-sources, which is part of your profile.
Calculating dependencies... done!
[ebuild NS ~] sys-kernel/gentoo-sources-5.16.3:5.16.3::gentoo
[5.6.7:5.6.7::gentoo, 5.10.46:5.10.46::gentoo, 5.14.15:5.14.15::gentoo,
5.15.17:5.15.17::gentoo] USE="-build -experimental -symlink" 120,568 KiB
Total: 1 package (1 in new slot), Size of downloads: 120,568 KiB
Would you like to merge these packages? [Yes/No]
It still wants to upgrade. Could it be that something is pulling it in
as a dependency or something? Am I still doing something wrong? This is
a update to the above:
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild NS ~] sys-kernel/gentoo-sources-5.16.3:5.16.3::gentoo [5.6.7:5.6.7::gentoo, 5.10.46:5.10.46::gentoo, 5.14.15:5.14.15::gentoo, 5.15.17:5.15.17::gentoo] USE="-build -experimental -symlink" 120,568 KiB
Total: 1 package (1 in new slot), Size of downloads: 120,568 KiB
Would you like to merge these packages? [Yes/No]
It still wants to upgrade. Could it be that something is pulling it in
as a dependency or something? Am I still doing something wrong? This is
a update to the above:
Calculating dependencies... done!It is probably being pulled in as a dependency of
[ebuild NS ~] sys-kernel/gentoo-sources-5.16.3:5.16.3::gentoo
[5.6.7:5.6.7::gentoo, 5.10.46:5.10.46::gentoo,
5.14.15:5.14.15::gentoo, 5.15.17:5.15.17::gentoo] USE="-build
-experimental -symlink" 120,568 KiB
Total: 1 package (1 in new slot), Size of downloads: 120,568 KiB
Would you like to merge these packages? [Yes/No]
It still wants to upgrade. Could it be that something is pulling it
in as a dependency or something? Am I still doing something wrong?
This is a update to the above:
virtual/linux-sources, which is part of your profile.
So I need to go back to my old way, mask them all and unmask when I want
to upgrade? It's what I'm used to doing anyway. lol
You're using ~amd64 sources, which means they update frequently. I found
this annoying so I only use the stable sources, even on ~amd64 systems to keep updates to a reasonable level while ensuring I don't miss important updates. I added this to package.accept_keywords
sys-kernel/gentoo-sources -~amd64
sys-kernel/linux-headers -~amd64
Having said that, it wants to install a new kernel this morning :-/
You're using ~amd64 sources, which means they update frequently. I
found this annoying so I only use the stable sources, even on ~amd64 systems to keep updates to a reasonable level while ensuring I don't
miss important updates. I added this to package.accept_keywords
sys-kernel/gentoo-sources -~amd64
sys-kernel/linux-headers -~amd64
Having said that, it wants to install a new kernel this morning :-/
If you want a bit more control, I'd just mask it completely in /etc/portage/package.mask/ and then unmask whatever version you want
to install in /etc/portage/package.unmask
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 302 |
Nodes: | 16 (2 / 14) |
Uptime: | 100:15:43 |
Calls: | 6,767 |
Calls today: | 5 |
Files: | 12,295 |
Messages: | 5,376,420 |
Posted today: | 1 |