Re: [gentoo-user] System crash on "Detecting C compiler ABI info"
On 02.04.24 21:43, Paul Sopka wrote: On 02.04.24 20:50, J. Roeleveld wrote: Did you upgrade GCC recently? If yes, did you follow the gcc-upgrade guide: https://wiki.gentoo.org/wiki/Upgrading_GCC ? -- Joost Thank you for your answer Joost. As far as I know, I didn't upgrade GCC recently. I just rebuilt libtool to be sure, but that didn't help. Nanderty I rebuilt with emptytree over night from tty. The system didn't crash, but it hung up at the first program to use this, media-libs/libjpeg-turbo.
Re: [gentoo-user] some problems moving to 23.0 profile
On Tue, 02 Apr 2024 14:47:28 -0400, J. Roeleveld wrote: > > On Tuesday, 2 April 2024 10:14:11 CEST Michael wrote: > > On Tuesday, 2 April 2024 07:03:42 BST J. Roeleveld wrote: > > > On Monday, 1 April 2024 23:46:49 CEST John Covici wrote: > > > > 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. > > > > Here is what I get: > > > > > > > > emerge --ask --emptytree @world > > > > > > > > These are the packages that would be merged, in order: > > > > > > > > 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 > > > > !!! masked or don't exist: > > > > www-apps/nextcloud:26.0.10 > > > > > > > > emerge: there are no ebuilds to satisfy > > > > "sys-kernel/gentoo-sources:6.1.69". > > > > (dependency required by "@kernels" [set]) > > > > (dependency required by "@selected" [set]) > > > > (dependency required by "@world" [argument]) > > > > > > > > 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. 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 cov...@ccs.covici.com
Re: [gentoo-user] System crash on "Detecting C compiler ABI info"
On 02.04.24 20:50, J. Roeleveld wrote: Did you upgrade GCC recently? If yes, did you follow the gcc-upgrade guide: https://wiki.gentoo.org/wiki/Upgrading_GCC ? -- Joost Thank you for your answer Joost. As far as I know, I didn't upgrade GCC recently. I just rebuilt libtool to be sure, but that didn't help. Nanderty
Re: [gentoo-user] Re: New profiles 23.0
On Saturday, 30 March 2024 19:34:42 CEST Walter Dnes wrote: > Thanks for the help. I've migrated my 3 operating Gentoo machines; > main desktop, backup desktop, and an old used Lenovo Thinkpad X201. The > poor thing was thrashing away for over 18 hours with 657 packages on the > emerge --emptytree!!! And that's after using a homebrew bash script to > select the max available speed on the CPU. "time" output... What does that script do? > > real1086m47.440s > > user1732m29.120s > > sys 146m54.026s > > > > > I got the news item when I ran "emerge --sync". My understanding is > > > that step 1 in the news item says "Please also update your system > > > fully and depclean before proceeding" so I should update world > > > first. > > > > Yes. And depclean. > > I ended up unmerging specific items manually. Depclean is "rather > agressive", and wants to remove all but the latest kernel, *EVEN A > KERNEL THAT I'M CURRENTLY USING*. I'm currently on 6.1.67... Unless you plan on recompiling that kernel, there is no need to actually KEEP the sources. > [x8940][waltdnes][~] eselect kernel list > Available kernel symlink targets: > [1] linux-6.1.57-gentoo > [2] linux-6.1.67-gentoo * > [3] linux-6.6.13-gentoo > [4] linux-6.6.21-gentoo > > I ran into the Intel integrated graphics problem described in... > https://discussion.fedoraproject.org/t/f39-kernel-6-6-x-no-video-on-intel-in > tegrated-graphics/98360 > > His solution... > > > I was filling out the details for a bug report. Under the description, > > it asked if I have tried rawhide. I installed 6.7.0-0.rc4.35.fc40 > > and it fixed the issue! > > This appears to be a bug in the 6.6.x kernels, which is fixed in > 6.7.x. My 2 desktops and the Thinkpad all have integrated Intel > graphics, so I'll sit at 6.1.67 until 6.7.x, or higher, goes stable. > /var/db/repos/gentoo/sys-kernel/gentoo-kernel/gentoo-kernel-6.7.10.ebuild > is already present, but is keyworded "~amd64".
Re: [gentoo-user] System crash on "Detecting C compiler ABI info"
On Tuesday, 2 April 2024 16:11:20 CEST Paul Sopka wrote: > Hello Gentoo, > > my entire system crashes reliably on "Detecting C compiler ABI info" > when compiling some packages, happened on sci-libs/netcdf and > media-libs/svt-av1. > > I am pretty sure it isn't a hardware instability since I can compile > everything that doesn't run "Detecting C compiler ABI info" without any > issues at all. > > Does anybody have an idea why this happens? > > I wish you all a nice afternoon! > > Nanderty Did you upgrade GCC recently? If yes, did you follow the gcc-upgrade guide: https://wiki.gentoo.org/wiki/Upgrading_GCC ? -- Joost
Re: [gentoo-user] some problems moving to 23.0 profile
On Tuesday, 2 April 2024 10:14:11 CEST Michael wrote: > On Tuesday, 2 April 2024 07:03:42 BST J. Roeleveld wrote: > > On Monday, 1 April 2024 23:46:49 CEST John Covici wrote: > > > 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. > > > Here is what I get: > > > > > > emerge --ask --emptytree @world > > > > > > These are the packages that would be merged, in order: > > > > > > 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 > > > !!! masked or don't exist: > > > www-apps/nextcloud:26.0.10 > > > > > > emerge: there are no ebuilds to satisfy > > > "sys-kernel/gentoo-sources:6.1.69". > > > (dependency required by "@kernels" [set]) > > > (dependency required by "@selected" [set]) > > > (dependency required by "@world" [argument]) > > > > > > 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
Re: [gentoo-user] some problems moving to 23.0 profile
On Tuesday, 2 April 2024 11:17:25 CEST John Covici wrote: > On Tue, 02 Apr 2024 02:02:08 -0400, > > J. Roeleveld wrote: > > On Tuesday, 2 April 2024 05:51:08 CEST John Covici wrote: > > > On Mon, 01 Apr 2024 18:05:47 -0400, > > > > > > Dale wrote: > > > > John Covici wrote: > > > > > 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. > > > > > Here is what I get: > > > > > > > > > > emerge --ask --emptytree @world > > > > > > > > > > These are the packages that would be merged, in order: > > > > > > > > > > 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 > > > > > !!! masked or don't exist: > > > > > www-apps/nextcloud:26.0.10 > > > > > > > > > > emerge: there are no ebuilds to satisfy > > > > > "sys-kernel/gentoo-sources:6.1.69". > > > > > (dependency required by "@kernels" [set]) > > > > > (dependency required by "@selected" [set]) > > > > > (dependency required by "@world" [argument]) > > > > > > > > > > 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. > > > > > > > > > > So, should I just not do the whole world file at all -- do I really > > > > > need to do that, or wait till I upgrade nextcloud and till I am no > > > > > longer using that kernel and then do it? > > > > > > > > > > Thanks in advance for any suggestions. > > > > > > > > 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. > > > > > > > > > > > > root@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 > > > > root@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 = > > > 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? > > > > Actually, based on the output, it is in your world file: > > > > > emerge: there are no ebuilds to satisfy > > > > > "sys-kernel/gentoo-sources:6.1.69". > > > > > (dependency required by "@kernels" [set]) > > > > > (dependency required by "@selected" [set]) > > > > > (dependency required by "@world" [argument]) > > > > 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 = '' > >
[gentoo-user] System crash on "Detecting C compiler ABI info"
Hello Gentoo, my entire system crashes reliably on "Detecting C compiler ABI info" when compiling some packages, happened on sci-libs/netcdf and media-libs/svt-av1. I am pretty sure it isn't a hardware instability since I can compile everything that doesn't run "Detecting C compiler ABI info" without any issues at all. Does anybody have an idea why this happens? I wish you all a nice afternoon! Nanderty
[gentoo-user] xz-backdoor followup / restrict high entropy files in ebuilds
Hi all,
the xz-backdoor (CVE-2024-3094) luckily did not target gentoo, but it could
have easily done so. One step in this sophisticated attack involved injecting
concealed code into the build-process by some kind of homebrew steganography.
I asked myself how many high-entropy files I can find in distfiles. All these
gif|png|jpg|jpeg|wav|der|xz|gz|p12 might actually be low entropy, but checking
this would require a more sophisticated approach — in a naive approach, I just
checked how much bzip2 is able to compress files.
But I also found some really unnecessary and — IMHO — high risk stuff in
distfiles. tpm-tools f.e. has the /.git/ subdir with all those blobs. Python
has some audio-testfiles.
In an ideal world, upstream would instead include some low entropy generators
for this stuff. Gentoo should address the problem even if upstream is not
responsive.
I wonder if we should have some functionality in eclasses to
a) let src_unpack() filter/drop distfile content, controlled by an
ebuild-variable (to deal f.e. with /.git/)
b) let src_unpack() warn on high entropy content (except files whitelisted in
ebuild)
This would at least allow to easily identify high risk stuff that warrants more
scrutiny.
Greets,
Andreas
BTW, this is my naive test script, sort output on -r -k3
#!/bin/bash
TMPDIR=/tmp/distfiles-entropy.$(date +"%Y%m%d%H%M%S")
trap ' rm -rf ${TMPDIR} ' EXIT
mkdir ${TMPDIR}
cd ${TMPDIR}
for DISTFILE in $(find /var/cache/distfiles/ -type f -printf '%f\n')
do
mkdir ${DISTFILE}
case ${DISTFILE} in
*.tar.gz) gzip -dc /var/cache/distfiles/${DISTFILE} | tar
-C ${TMPDIR}/${DISTFILE} -xf -;;
*.tgz) gzip -dc /var/cache/distfiles/${DISTFILE} | tar
-C ${TMPDIR}/${DISTFILE} -xf -;;
*.tar.xz) xzcat/var/cache/distfiles/${DISTFILE} | tar
-C ${TMPDIR}/${DISTFILE} -xf -;;
*.txz) xzcat/var/cache/distfiles/${DISTFILE} | tar
-C ${TMPDIR}/${DISTFILE} -xf -;;
*.tar.bz2) bzcat/var/cache/distfiles/${DISTFILE} | tar
-C ${TMPDIR}/${DISTFILE} -xf -;;
*.tbz) bzcat/var/cache/distfiles/${DISTFILE} | tar
-C ${TMPDIR}/${DISTFILE} -xf -;;
*.gz) gzip -dc /var/cache/distfiles/${DISTFILE} >
${TMPDIR}/${DISTFILE}/file;;
*) cat /var/cache/distfiles/${DISTFILE} >
${TMPDIR}/${DISTFILE}/file;;
esac
find ${DISTFILE} -type f | xargs bzip2 -cv 2>&1 >/dev/null
rm -rf ${TMPDIR}/${DISTFILE}
done
Re: [gentoo-user] some problems moving to 23.0 profile
On Tue, 02 Apr 2024 02:02:08 -0400, J. Roeleveld wrote: > > On Tuesday, 2 April 2024 05:51:08 CEST John Covici wrote: > > On Mon, 01 Apr 2024 18:05:47 -0400, > > > > Dale wrote: > > > John Covici wrote: > > > > 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. > > > > Here is what I get: > > > > > > > > emerge --ask --emptytree @world > > > > > > > > These are the packages that would be merged, in order: > > > > > > > > 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 > > > > !!! masked or don't exist: > > > > www-apps/nextcloud:26.0.10 > > > > > > > > emerge: there are no ebuilds to satisfy > > > > "sys-kernel/gentoo-sources:6.1.69". > > > > (dependency required by "@kernels" [set]) > > > > (dependency required by "@selected" [set]) > > > > (dependency required by "@world" [argument]) > > > > > > > > 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. > > > > > > > > So, should I just not do the whole world file at all -- do I really > > > > need to do that, or wait till I upgrade nextcloud and till I am no > > > > longer using that kernel and then do it? > > > > > > > > Thanks in advance for any suggestions. > > > > > > 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. > > > > > > > > > root@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 > > > root@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 = > > 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? > > Actually, based on the output, it is in your world file: > > > > > emerge: there are no ebuilds to satisfy > > > > "sys-kernel/gentoo-sources:6.1.69". > > > > (dependency required by "@kernels" [set]) > > > > (dependency required by "@selected" [set]) > > > > (dependency required by "@world" [argument]) > > 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 cov...@ccs.covici.com
Re: [gentoo-user] some problems moving to 23.0 profile
On 02/04/2024 04:51, John Covici wrote: 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? 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 signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] some problems moving to 23.0 profile
On Tuesday, 2 April 2024 07:03:42 BST J. Roeleveld wrote: > On Monday, 1 April 2024 23:46:49 CEST John Covici wrote: > > 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. > > Here is what I get: > > > > emerge --ask --emptytree @world > > > > These are the packages that would be merged, in order: > > > > 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 > > !!! masked or don't exist: > > www-apps/nextcloud:26.0.10 > > > > emerge: there are no ebuilds to satisfy > > "sys-kernel/gentoo-sources:6.1.69". > > (dependency required by "@kernels" [set]) > > (dependency required by "@selected" [set]) > > (dependency required by "@world" [argument]) > > > > 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. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] some problems moving to 23.0 profile
On Monday, 1 April 2024 23:46:49 CEST John Covici wrote: > 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. > Here is what I get: > > emerge --ask --emptytree @world > > These are the packages that would be merged, in order: > > 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 > !!! masked or don't exist: > www-apps/nextcloud:26.0.10 > > emerge: there are no ebuilds to satisfy > "sys-kernel/gentoo-sources:6.1.69". > (dependency required by "@kernels" [set]) > (dependency required by "@selected" [set]) > (dependency required by "@world" [argument]) > > 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
Re: [gentoo-user] some problems moving to 23.0 profile
On Tuesday, 2 April 2024 05:51:08 CEST John Covici wrote: > On Mon, 01 Apr 2024 18:05:47 -0400, > > Dale wrote: > > John Covici wrote: > > > 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. > > > Here is what I get: > > > > > > emerge --ask --emptytree @world > > > > > > These are the packages that would be merged, in order: > > > > > > 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 > > > !!! masked or don't exist: > > > www-apps/nextcloud:26.0.10 > > > > > > emerge: there are no ebuilds to satisfy > > > "sys-kernel/gentoo-sources:6.1.69". > > > (dependency required by "@kernels" [set]) > > > (dependency required by "@selected" [set]) > > > (dependency required by "@world" [argument]) > > > > > > 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. > > > > > > So, should I just not do the whole world file at all -- do I really > > > need to do that, or wait till I upgrade nextcloud and till I am no > > > longer using that kernel and then do it? > > > > > > Thanks in advance for any suggestions. > > > > 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. > > > > > > root@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 > > root@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 = > 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? Actually, based on the output, it is in your world file: > > > emerge: there are no ebuilds to satisfy > > > "sys-kernel/gentoo-sources:6.1.69". > > > (dependency required by "@kernels" [set]) > > > (dependency required by "@selected" [set]) > > > (dependency required by "@world" [argument]) It's referenced in " /var/lib/portage/world_sets " -- Joost
