From: John Covici <covici@ccs.covici.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] some problems moving to 23.0 profile
Date: Mon, 01 Apr 2024 17:46:49 -0400 [thread overview]
Message-ID: <m3edbo69iu.wl-covici@ccs.covici.com> (raw)
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.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici wb2una
covici@ccs.covici.com
next reply other threads:[~2024-04-01 21:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 21:46 John Covici [this message]
2024-04-01 21:56 ` [gentoo-user] some problems moving to 23.0 profile byte.size226
2024-04-01 22:05 ` Dale
2024-04-02 3:51 ` John Covici
2024-04-02 5:58 ` Dale
2024-04-02 6:02 ` J. Roeleveld
2024-04-02 9:17 ` John Covici
2024-04-02 18:44 ` J. Roeleveld
2024-04-02 8:20 ` byte.size226
2024-04-02 6:03 ` J. Roeleveld
2024-04-02 8:14 ` Michael
2024-04-02 18:47 ` J. Roeleveld
2024-04-02 21:53 ` John Covici
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3edbo69iu.wl-covici@ccs.covici.com \
--to=covici@ccs.covici.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox