[gentoo-user] some problems moving to 23.0 profile

Discussion:

(too old to reply)

J. Roeleveld

2024-04-06 07:50:18 UTC

Hi. Well, I followed the steps in the news item, to move
todefault/linux/amd64/23.0/desktop/gnome/systemd
and it all worked till it wants me to emerge the whole world file.
Calculating dependencies .... done!
Dependency resolution took 4.58 s (backtrack: 0/200).
!!! Problems have been detected with your world file
!!! Please run emaint --check world
!!! Ebuilds for the following packages are either all
www-apps/nextcloud:26.0.10
emerge: there are no ebuilds to satisfy
"sys-kernel/gentoo-sources:6.1.69".
I don't want to unmerge that kernel -- its my backup kernel, so I
definitely want to keep it. I am using the nextcloud they are
complaining about , I will upgrade it soon, but I want to keep it for
now.

Do you actually need to keep the kernel-sources?
Once the kernel is compiled and you moved the image to /boot/..., you
don't
need to keep the sources.
I also keep an older kernel just in case, but I don't tend to actually
keep
the sources around once I have confirmed the new kernel will boot.
--
Joost

When gentoo-sources are tree-cleaned, it is typically because they have been
superseded by later kernel patches to improve security and resolve bugs.
Therefore it is usually a 'good idea' to emerge a later kernel when this
happens, even if we're talking about a backup kernel.
Last week I came upon a similar problem on an old system I was trying to
migrate to profile 23.0, only this happened not with my backup but with the
running kernel. This PC had not been updated for 5-6 months. It's resource
constrained and I didn't want to spend many days updating most of its
deprecated packages, only to have to re-emerge them as part of the profile
migration. I can't recall if it was the same kernel as John's. During the
migration I came across some package (llvm?) which required a more up to
date kernel to be able to emerge. This forced me to upgrade the kernel
first, before I could continue with the migration. I'm mentioning this
since the utility of a backup kernel would be limited when you can't use it
to run your software.

This is my experience as well.
A "backup kernel" is, in my opinion, only useful as a fall-back in case the
system won't boot with a new kernel.
But, once it booted with the new kernel correctly, there is no reason to
actually keep the old kernel.

--
Joost

b***@simplelogin.com

2024-04-06 07:50:23 UTC

Permalink

I don't want to unmerge that kernel -- its my backup kernel, so I
definitely want to keep it. I am using the nextcloud they are
complaining about , I will upgrade it soon, but I want to keep it for
now.

You can pass --exclude to emerge to prevent it from merging a given
package. In your case, I would try to pass:

--exclude 'sys-kernel/gentoo-sources:6.1.69 www-apps/nextcloud:26.0.10'

This should let portage continue while ignoring the above completely.
Double check the correct slot numbers are used.

Hope this helps.

Best Regards,
Victor

J. Roeleveld

2024-04-06 07:50:36 UTC

Permalink

On Tue, 02 Apr 2024 02:02:08 -0400,

On Mon, 01 Apr 2024 18:05:47 -0400,

I ran into the problem of it complaining about my world file too.
Running the command it gave didn't show any problems. I went ahead
with
the rest of the change. After it was all done, that error went away
on
its own. No idea what triggered it or what removed the trigger. Must
be something to do with the profile switching process. You can likely
ignore that for now. See if it goes away for you too.
I don't know what nascloud is but the error says it is masked or not
there at all. I'd suspect the mask part since there are several
versions in the tree. You may want to check your package.mask file
and
see if there is something in there that masks it. Could be you meant
to
add the entry to keyword or unmask file but hit the wrong file. Did
that once myself. One easy way to see if it exists or is masked, use
this command, provided you have the package for it installed. I think
gentools has this command.
* Searching for nextcloud in www-apps ...
[-P-] [ ] www-apps/nextcloud-26.0.8:26.0.8
[-P-] [ ~] www-apps/nextcloud-26.0.11:26.0.11
[-P-] [ ~] www-apps/nextcloud-26.0.12:26.0.12
[-P-] [ ] www-apps/nextcloud-27.1.5:27.1.5
[-P-] [ ~] www-apps/nextcloud-27.1.6:27.1.6
[-P-] [ ~] www-apps/nextcloud-27.1.7:27.1.7
[-P-] [ ] www-apps/nextcloud-28.0.1:28.0.1
[-P-] [ ] www-apps/nextcloud-28.0.2:28.0.2
[-P-] [ ~] www-apps/nextcloud-28.0.3:28.0.3
Yours should look something like that.
For the kernels, I don't upgrade the kernel as much as I should. I
keep
all versions masked except the ones I have installed and I add those
versions to the world file, that way --depclean and other stuff, won't
remove or complain so much about it. Just emerge -n --select y =<your
kernel name and version here>. Don't forget the equal sign when
including the version.
Hope one or more of those things help.

My kernels are not in the world file at all, so I am confused why
portage should care about them when I am updating the world file. My
question is why do I need to do this at all -- could I just keep
updating as normal?

emerge: there are no ebuilds to satisfy
"sys-kernel/gentoo-sources:6.1.69".

It's referenced in " /var/lib/portage/world_sets "

What that file has is
@kernels
and I have in /etc/portage/sets.conf is
[kernels]
class = portage.sets.dbapi.OwnerSet
world-candidate = False
files = /usr/src
exclude-files = ''
Am I looking in the wrong place?

This is the right place, but because of those settings, it is part of your
world-file.

--
Joost

John Covici

2024-04-06 07:50:39 UTC

Permalink

On Mon, 01 Apr 2024 18:05:47 -0400,

I ran into the problem of it complaining about my world file too.
Running the command it gave didn't show any problems. I went ahead with
the rest of the change. After it was all done, that error went away on
its own. No idea what triggered it or what removed the trigger. Must
be something to do with the profile switching process. You can likely
ignore that for now. See if it goes away for you too.
I don't know what nascloud is but the error says it is masked or not
there at all. I'd suspect the mask part since there are several
versions in the tree. You may want to check your package.mask file and
see if there is something in there that masks it. Could be you meant to
add the entry to keyword or unmask file but hit the wrong file. Did
that once myself. One easy way to see if it exists or is masked, use
this command, provided you have the package for it installed. I think
gentools has this command.
* Searching for nextcloud in www-apps ...
[-P-] [ ] www-apps/nextcloud-26.0.8:26.0.8
[-P-] [ ~] www-apps/nextcloud-26.0.11:26.0.11
[-P-] [ ~] www-apps/nextcloud-26.0.12:26.0.12
[-P-] [ ] www-apps/nextcloud-27.1.5:27.1.5
[-P-] [ ~] www-apps/nextcloud-27.1.6:27.1.6
[-P-] [ ~] www-apps/nextcloud-27.1.7:27.1.7
[-P-] [ ] www-apps/nextcloud-28.0.1:28.0.1
[-P-] [ ] www-apps/nextcloud-28.0.2:28.0.2
[-P-] [ ~] www-apps/nextcloud-28.0.3:28.0.3
Yours should look something like that.
For the kernels, I don't upgrade the kernel as much as I should. I keep
all versions masked except the ones I have installed and I add those
versions to the world file, that way --depclean and other stuff, won't
remove or complain so much about it. Just emerge -n --select y =<your
kernel name and version here>. Don't forget the equal sign when
including the version.
Hope one or more of those things help.

--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?

John Covici wb2una
***@ccs.covici.com

John Covici

2024-04-06 07:50:49 UTC

Permalink

On Tue, 02 Apr 2024 02:02:08 -0400,

On Mon, 01 Apr 2024 18:05:47 -0400,

I ran into the problem of it complaining about my world file too.
Running the command it gave didn't show any problems. I went ahead with
the rest of the change. After it was all done, that error went away on
its own. No idea what triggered it or what removed the trigger. Must
be something to do with the profile switching process. You can likely
ignore that for now. See if it goes away for you too.
I don't know what nascloud is but the error says it is masked or not
there at all. I'd suspect the mask part since there are several
versions in the tree. You may want to check your package.mask file and
see if there is something in there that masks it. Could be you meant to
add the entry to keyword or unmask file but hit the wrong file. Did
that once myself. One easy way to see if it exists or is masked, use
this command, provided you have the package for it installed. I think
gentools has this command.
* Searching for nextcloud in www-apps ...
[-P-] [ ] www-apps/nextcloud-26.0.8:26.0.8
[-P-] [ ~] www-apps/nextcloud-26.0.11:26.0.11
[-P-] [ ~] www-apps/nextcloud-26.0.12:26.0.12
[-P-] [ ] www-apps/nextcloud-27.1.5:27.1.5
[-P-] [ ~] www-apps/nextcloud-27.1.6:27.1.6
[-P-] [ ~] www-apps/nextcloud-27.1.7:27.1.7
[-P-] [ ] www-apps/nextcloud-28.0.1:28.0.1
[-P-] [ ] www-apps/nextcloud-28.0.2:28.0.2
[-P-] [ ~] www-apps/nextcloud-28.0.3:28.0.3
Yours should look something like that.
For the kernels, I don't upgrade the kernel as much as I should. I keep
all versions masked except the ones I have installed and I add those
versions to the world file, that way --depclean and other stuff, won't
remove or complain so much about it. Just emerge -n --select y =<your
kernel name and version here>. Don't forget the equal sign when
including the version.
Hope one or more of those things help.

emerge: there are no ebuilds to satisfy
"sys-kernel/gentoo-sources:6.1.69".

It's referenced in " /var/lib/portage/world_sets "

What that file has is
@kernels

and I have in /etc/portage/sets.conf is

[kernels]
class = portage.sets.dbapi.OwnerSet
world-candidate = False
files = /usr/src
exclude-files = ''

Am I looking in the wrong place?

--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?

John Covici wb2una
***@ccs.covici.com

b***@simplelogin.com

2024-04-06 07:51:24 UTC

Permalink

Your kernels should be in the world file as evidenced by your earlier
log and pointed out by J. Roeleveld. If you didn't, portage would try to
remove it - its sources, at least - every time you ran portage with
"--depclean".

Unfortunately, kernels are periodically 'hoovered' from the Gentoo repo
and it appears 6.1.69 has already been removed and superseded by 6.1.74,
6.1.81, 6.1.82, and 6.1.83 in the 6.1.x family. Chances are your config
would work just as well on these.

The reason you have to do this is because with the upstream ebuild now
gone, portage doesn't know how to fetch said ebuild. This is not a
problem on a day-to-day basis as you would only be emerging packages
with updates or
use flag changes. But with --emptytre portage is being
told that it should recompute and install all packages, and their
dependencies, from @world as if the system were completely 'clean'. This
in turn requires that any 'pinned' versions are reinstalled as well. A
reinstall would mean uninstalling the currently installed package files
and replacing them with those from the new build. With 6.1.69 gone, this
isn't possible so portage complains.

It's the same problem you are having with nextcloud.

Adding these to "--exclude" means portage will not take them into
consideration when computing --emptytree and will leave them be as-is
without touching them. This will allow you to keep the 6.1.69 kernel,
and your existing nextcloud build.

Your nextcloud build 'might work' unless there's any significant
differences in use flags with the new profile that might lead to linked
library issues. You might have to find the hard way.

I too had an issue that was causing
sci-astronomy/calcmysky to fail when
rebuilding with the new profile (which was an upstream problem) and had
to force portage to ignore this and continue while I deal with it after
the fact (I ultimately had to wait for an version bump which was only a
minor inconvenience).

Hope this helps explain why you're facing the issue and why I think
--exclude might be your best option, especially if you _really_ want to
keep kernel 6.1.69.

Cheers,
Victor

J. Roeleveld

2024-04-06 07:51:29 UTC

Permalink

On Mon, 01 Apr 2024 18:05:47 -0400,

I ran into the problem of it complaining about my world file too.
Running the command it gave didn't show any problems. I went ahead with
the rest of the change. After it was all done, that error went away on
its own. No idea what triggered it or what removed the trigger. Must
be something to do with the profile switching process. You can likely
ignore that for now. See if it goes away for you too.
I don't know what nascloud is but the error says it is masked or not
there at all. I'd suspect the mask part since there are several
versions in the tree. You may want to check your package.mask file and
see if there is something in there that masks it. Could be you meant to
add the entry to keyword or unmask file but hit the wrong file. Did
that once myself. One easy way to see if it exists or is masked, use
this command, provided you have the package for it installed. I think
gentools has this command.
* Searching for nextcloud in www-apps ...
[-P-] [ ] www-apps/nextcloud-26.0.8:26.0.8
[-P-] [ ~] www-apps/nextcloud-26.0.11:26.0.11
[-P-] [ ~] www-apps/nextcloud-26.0.12:26.0.12
[-P-] [ ] www-apps/nextcloud-27.1.5:27.1.5
[-P-] [ ~] www-apps/nextcloud-27.1.6:27.1.6
[-P-] [ ~] www-apps/nextcloud-27.1.7:27.1.7
[-P-] [ ] www-apps/nextcloud-28.0.1:28.0.1
[-P-] [ ] www-apps/nextcloud-28.0.2:28.0.2
[-P-] [ ~] www-apps/nextcloud-28.0.3:28.0.3
Yours should look something like that.
For the kernels, I don't upgrade the kernel as much as I should. I keep
all versions masked except the ones I have installed and I add those
versions to the world file, that way --depclean and other stuff, won't
remove or complain so much about it. Just emerge -n --select y =<your
kernel name and version here>. Don't forget the equal sign when
including the version.
Hope one or more of those things help.

emerge: there are no ebuilds to satisfy
"sys-kernel/gentoo-sources:6.1.69".

It's referenced in " /var/lib/portage/world_sets "

--
Joost

Dale

2024-04-06 07:52:08 UTC

Permalink

On Mon, 01 Apr 2024 18:05:47 -0400,

I ran into the problem of it complaining about my world file too.
Running the command it gave didn't show any problems. I went ahead with
the rest of the change. After it was all done, that error went away on
its own. No idea what triggered it or what removed the trigger. Must
be something to do with the profile switching process. You can likely
ignore that for now. See if it goes away for you too.
I don't know what nascloud is but the error says it is masked or not
there at all. I'd suspect the mask part since there are several
versions in the tree. You may want to check your package.mask file and
see if there is something in there that masks it. Could be you meant to
add the entry to keyword or unmask file but hit the wrong file. Did
that once myself. One easy way to see if it exists or is masked, use
this command, provided you have the package for it installed. I think
gentools has this command.
* Searching for nextcloud in www-apps ...
[-P-] [ ] www-apps/nextcloud-26.0.8:26.0.8
[-P-] [ ~] www-apps/nextcloud-26.0.11:26.0.11
[-P-] [ ~] www-apps/nextcloud-26.0.12:26.0.12
[-P-] [ ] www-apps/nextcloud-27.1.5:27.1.5
[-P-] [ ~] www-apps/nextcloud-27.1.6:27.1.6
[-P-] [ ~] www-apps/nextcloud-27.1.7:27.1.7
[-P-] [ ] www-apps/nextcloud-28.0.1:28.0.1
[-P-] [ ] www-apps/nextcloud-28.0.2:28.0.2
[-P-] [ ~] www-apps/nextcloud-28.0.3:28.0.3
Yours should look something like that.
For the kernels, I don't upgrade the kernel as much as I should. I keep
all versions masked except the ones I have installed and I add those
versions to the world file, that way --depclean and other stuff, won't
remove or complain so much about it. Just emerge -n --select y =<your
kernel name and version here>. Don't forget the equal sign when
including the version.
Hope one or more of those things help.

Keep in mind, some packages require a kernel to satisfy dependencies. I
see several packages looking for a kernel and even checking for some
config options. I think there is a virtual in the system set that has
to be satisfied as well. If you install a kernel by hand, you may want
to look into package provided or something later. Unless it causes
emerge to refuse to update, I ignore errors about the kernel.

Victor has one idea on the other problem, skip the nextcloud package
with the --exclude option. However, once you complete the rest of
emerge -e world, you need to go back and sort this out and emerge
whatever was skipped. On my first attempt in a chroot, I had to skip
one package too. Just keep in mind, I think it skips its dependencies
as well. So it may not skip just that one package.

If you chose the exclude method, you should be able to continue with the
profile update. Just don't forget to emerge it later with the new
settings.

In short, if you use -a and it gives you the chance to say yes, I'd
carry on.

Dale

:-) :-)

J. Roeleveld

2024-04-06 07:50:50 UTC

Permalink

Do you actually need to keep the kernel-sources?
Once the kernel is compiled and you moved the image to /boot/..., you don't
need to keep the sources.

I also keep an older kernel just in case, but I don't tend to actually keep
the sources around once I have confirmed the new kernel will boot.

--
Joost

Michael

2024-04-06 07:51:56 UTC

Permalink

Do you actually need to keep the kernel-sources?
Once the kernel is compiled and you moved the image to /boot/..., you don't
need to keep the sources.
I also keep an older kernel just in case, but I don't tend to actually keep
the sources around once I have confirmed the new kernel will boot.
--
Joost

When gentoo-sources are tree-cleaned, it is typically because they have been
superseded by later kernel patches to improve security and resolve bugs.
Therefore it is usually a 'good idea' to emerge a later kernel when this
happens, even if we're talking about a backup kernel.

Last week I came upon a similar problem on an old system I was trying to
migrate to profile 23.0, only this happened not with my backup but with the
running kernel. This PC had not been updated for 5-6 months. It's resource
constrained and I didn't want to spend many days updating most of its
deprecated packages, only to have to re-emerge them as part of the profile
migration. I can't recall if it was the same kernel as John's. During the
migration I came across some package (llvm?) which required a more up to date
kernel to be able to emerge. This forced me to upgrade the kernel first,
before I could continue with the migration. I'm mentioning this since the
utility of a backup kernel would be limited when you can't use it to run your
software.

Dale

2024-04-06 07:51:24 UTC

Permalink

I ran into the problem of it complaining about my world file too.
Running the command it gave didn't show any problems. I went ahead with
the rest of the change. After it was all done, that error went away on
its own. No idea what triggered it or what removed the trigger. Must
be something to do with the profile switching process. You can likely
ignore that for now. See if it goes away for you too.

I don't know what nascloud is but the error says it is masked or not
there at all. I'd suspect the mask part since there are several
versions in the tree. You may want to check your package.mask file and
see if there is something in there that masks it. Could be you meant to
add the entry to keyword or unmask file but hit the wrong file. Did
that once myself. One easy way to see if it exists or is masked, use
this command, provided you have the package for it installed. I think
gentools has this command.

***@fireball / # equery list -p www-apps/nextcloud
* Searching for nextcloud in www-apps ...
[-P-] [ ] www-apps/nextcloud-26.0.8:26.0.8
[-P-] [ ~] www-apps/nextcloud-26.0.11:26.0.11
[-P-] [ ~] www-apps/nextcloud-26.0.12:26.0.12
[-P-] [ ] www-apps/nextcloud-27.1.5:27.1.5
[-P-] [ ~] www-apps/nextcloud-27.1.6:27.1.6
[-P-] [ ~] www-apps/nextcloud-27.1.7:27.1.7
[-P-] [ ] www-apps/nextcloud-28.0.1:28.0.1
[-P-] [ ] www-apps/nextcloud-28.0.2:28.0.2
[-P-] [ ~] www-apps/nextcloud-28.0.3:28.0.3
***@fireball / #

Yours should look something like that.

For the kernels, I don't upgrade the kernel as much as I should. I keep
all versions masked except the ones I have installed and I add those
versions to the world file, that way --depclean and other stuff, won't
remove or complain so much about it. Just emerge -n --select y =<your
kernel name and version here>. Don't forget the equal sign when
including the version.

Hope one or more of those things help.

Dale

:-) :-)

P. S. While I was typing, Victor had a good idea too. More than one
way to fix some things. :-D

John Covici

2024-04-06 07:52:45 UTC

Permalink

On Tue, 02 Apr 2024 14:47:28 -0400,

Post by J. Roeleveld

Do you actually need to keep the kernel-sources?
Once the kernel is compiled and you moved the image to /boot/..., you don't
need to keep the sources.
I also keep an older kernel just in case, but I don't tend to actually keep
the sources around once I have confirmed the new kernel will boot.
--
Joost

OK, I will do this, go to the next version of nextcloud which I need
to do anyway and see if that will fix things up. I still wonder why I
need to emerge the whole world file, but I will see what happens.

Thanks everyone.

--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?

John Covici wb2una
***@ccs.covici.com