From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Filesystem with python3_12, but /var/db,cache with python3_13
Date: Mon, 19 May 2025 23:27:21 +0100 [thread overview]
Message-ID: <1827948.VLH7GnMWUR@rogueboard> (raw)
In-Reply-To: <f935ffaa-1ee5-06fc-9c1c-4672644991ff@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2291 bytes --]
On Monday, 19 May 2025 14:17:49 British Summer Time Dale wrote:
> Michael wrote:
> > Just as I was celebrating the last python upgrade has been a breeze, a
> > disk
> > failed on one PC in the most inopportune moment. The / directory was on
> > the SSD disk which failed. The /var/db, /var/cache and /var/log are on a
> > different (spinning) disk.
> >
> > I restored / from a backup which was 5 weeks old, excluding /var/db, /var/
> > cache and /var/log - I didn't have a backup of these. Consequently,
> > there's an incongruity in what portage thinks is installed - a day old
> > update status - and what is actually installed - 5 weeks old packages.
> >
> > I tried to run an update @world, but it failed as some package versions
> > were missing/incompatible. I tried to force python3_13 following the
> > python upgrade guide, but may have ended up making things worse. What is
> > the best way to bring this system up to date?
>
> Do you have buildpkg set in make.conf? If you do, can you try a emerge
> -ek world? That should reinstall to the version you have saved from all
> the binaries you have. You may want to try -K as well. It tells it to
> use binaries only. If you don't have buildpkg set,
No buildpkg on this system. :-(
> I'm not sure how to
> fix that. Basically, portage stores data on what is installed in /var
> but the packages are in /, mostly /(s)bin and /usr. Basically, portage
> thinks one thing but the truth is something else. I suspect emerge
> isn't happy since it is so confused.
Emerge is not happy when it tries to use package versions which the filesystem
does not have installed yet. I'll try once more to tweak python targets in
case I can get emerge to build a working toolchain. If that doesn't work I'll
fetch a stage 3, build what I need as binaries and then emerge them on the
live system before I carry on.
> I hate when a drive goes bad. :-(
Although I can't complain because this SSD lasted for more than 11 years, it
was unfortunate it died just before I was about to take a fresh backup. A day
later it wouldn't have mattered. Murphy's Law in action!
> P. S. I hope you have a backup of /etc and your world file, just in
> case you have to start over.
Yes, but I'm trying hard to avoid reinstalling.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-05-19 22:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 9:30 [gentoo-user] Filesystem with python3_12, but /var/db,cache with python3_13 Michael
2025-05-19 13:17 ` Dale
2025-05-19 22:27 ` Michael [this message]
2025-05-19 23:00 ` Eli Schwartz
2025-05-19 23:04 ` Michael
2025-05-20 18:08 ` Michael
2025-05-20 18:42 ` Dale
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=1827948.VLH7GnMWUR@rogueboard \
--to=confabulate@kintzios.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