From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] problems with world update
Date: Sat, 22 Feb 2025 14:17:35 -0600 [thread overview]
Message-ID: <c5a8212e-d162-0f4f-2520-6563619fb8fa@gmail.com> (raw)
In-Reply-To: <m1cyf94uk1.wl-covici@ccs.covici.com>
covici@ccs.covici.com wrote:
> Hi. Well, I am having problems with update world again. Here is the
> output from the emerge itself:
>
> Script started on 2025-02-22 14:36:57-05:00 [COMMAND="emerge --update --deep --changed-use --with-bdeps=y --keep-going world" TERM="xterm-256color" TTY="/dev/pts/1" COLUMNS="80" LINES="24"]
> ^[]0;emerge\a
> These are the packages that would be merged, in order:
>
> <<< SNIP >>>
>
> Here is my package.mask:
>
>
>
>
> #1.4.1 has some serious problems
>> =app-backup/rsnapshot-1.4.1
>
> #i use udev
>> =sys-fs/static-dev-0.1
>> =dev-libs/icu-76.1-r1
>> =dev-libs/json-c-0.18
> =app-text/poppler-24.10.0
>
>> =app-emulation/libvert-10.9
>> =dev-python/libvirt-python-11.9
>
> Any assistance would be very much appreciated.
>
>
I'm not the best at this. It looks to me like you are going to have to
allow the masked version of libvert and possibly the other one to if
they tend to update in sets. Otherwise, you may have to mask a lot of
other packages until you can use the newer libvert packages.
I run a mixed system here, some stable, some unstable. Sometimes it is
hard to get the combination right so that you can be up to date and not
be running behind on some important packages. It's like walking a tight
rope at times.
Hope that helps. If not, someone else may have a better idea.
Dale
:-) :-)
prev parent reply other threads:[~2025-02-22 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-22 20:02 [gentoo-user] problems with world update covici
2025-02-22 20:17 ` Dale [this message]
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=c5a8212e-d162-0f4f-2520-6563619fb8fa@gmail.com \
--to=rdalek1967@gmail.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