public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] some problems moving to 23.0 profile
Date: Tue, 02 Apr 2024 08:03:42 +0200	[thread overview]
Message-ID: <5771314.DvuYhMxLoT@persephone> (raw)
In-Reply-To: <m3edbo69iu.wl-covici@ccs.covici.com>

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




  parent reply	other threads:[~2024-04-02  6:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 21:46 [gentoo-user] some problems moving to 23.0 profile John Covici
2024-04-01 21:56 ` 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 [this message]
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=5771314.DvuYhMxLoT@persephone \
    --to=joost@antarean.org \
    --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