| View previous topic :: View next topic |
| Author |
Message |
modnaruved
Apprentice
Joined: 21 Mar 2011
Posts: 163
|
 Posted: Thu Mar 06, 2025 1:08 pm Post subject: Incr. upd. Gentoo after long pause 17.1 to 23 since 01.06.24 |
 |
|
Hi all,
The system was running smoothly until June 2024, with the last update around June 1st. According to the news, it's necessary to upgrade from profile 17.1 to 23. Minimal preparations were made, but the profile switch and initial update steps have not been performed yet.
I’d like to ask: is it still possible to perform an incremental update of the Portage tree to minimize potential conflicts? This approach used to work quite well, but now there are many fragmented guides, and I’d appreciate clarification on whether it's feasible to fetch a snapshot of the Portage tree for a specific date and deploy it. If so, what are the steps to achieve this?
Apologies for the delay in addressing this issue and for any potential topic duplication. I hope this information will be helpful not only for me but for other users as well.
Technical system details are attached. Any help or advice would be greatly appreciated!
Attaching technical information:
To provide relevant technical information, I’ve gathered the following data:
Basic system information:
emerge --info
List of installed packages:
qlist -I
Kernel version:
uname -a
Current profile:
eselect profile list
Status of world file:
cat /var/lib/portage/world
I access the machine via SSH within a tmux session, and basic utilities like wgetpaste are available.
Thank you! |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54972
Location: 56N 3W
|
| Posted: Thu Mar 06, 2025 1:28 pm Post subject: |
|
|
modnaruved,
Yes. You can do a step and repeat to get to current Gentoo, if you need to.
The idea is to get up to date on the old profile, then change profiles without an emerge --sync as you don't want any updates during the profile switch.
Given | Code: | | Timestamp of repository gentoo: Sat, 01 Jun 2024 19:45:00 +0000 |
provided your system is up to date at that time, I would just go for it. Its less than a year ago.
| Code: | emerge --sync
emerge -1uDUav @world --keep-going --backtrack=500 |
and see what happens.
If portage solves the dependency graph, let it build. If not, pastebin the command and all of the output.
The hard bit of this may be getting your install up to date.
If you are using distcc, take great care with compiler versions. They must be identical everywhere.
Do not use ccache until the last step of the profile update. Then only if you flush the cache.
| Code: | | EMERGE_DEFAULT_OPTS="--jobs 4 ... |
Don't use --jobs there at all you only hove 6G real RAM.
is a bit aggressive too. Try -j2 there.
Swap, where it can be used, is very slow. It will be faster, end to end to stay out of swapping if you can.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
modnaruved
Apprentice
Joined: 21 Mar 2011
Posts: 163
|
| Posted: Thu Mar 06, 2025 1:59 pm Post subject: |
|
|
| NeddySeagoon wrote: | modnaruved,
Yes. You can do a step and repeat to get to current Gentoo, if you need to.
|
NeddySeagoon, thank you so much for your helpful response!
I want to make sure I understand the steps correctly. Should I first update the profile from 17.1 to 23 as required (without any sync - just upgrade profile), and then try to proceed with either incremental updates or directly run the following commands?
| Code: | emerge --sync
emerge -1uDUav @world --keep-going --backtrack=500 |
If incremental updates are possible, could you please clarify the exact steps? For example, how to fetch and deploy snapshots of the Portage tree, perhaps from a week after 01.06.24, or later? Or, given the relatively short gap, would it be more practical to just update the profile and proceed with a full sync, as suggested?
I really appreciate any additional guidance on this — thank you again for your support! |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54972
Location: 56N 3W
|
| Posted: Thu Mar 06, 2025 2:22 pm Post subject: |
|
|
modnaruved,
You must not change the profile until your Gentoo is up to date.
You may not be able to get the latest glibc and gcc but get the lastest that your profile permits.
Try | Code: | emerge --sync
emerge -1uDUav @world --keep-going --backtrack=500 |
now. It may work.
If not, read on and play with snapshots.
There are two ways to get snapshots.
1. is from git Every ebuild that ever was since Gentoo started in CVS in 2002 is available in git.
2. from the squashfs snapshots that go back to 2016.
There are 2 ways to use the snapshots.
2a. With squashfs kernel support, you can mount a snapshot at /var/db/repos/gentoo, or wherever your gentoo repo is.
2b. Use unsquash from squashfs-tools to unpack the squashfs snapshot.
Lets go with 2a.
Pick a snapshot you like, it can be fairly random.
Mount it over your gentoo repo.
Do not --sync, its read only
| Code: | | emerge -1uDUav @world --keep-going --backtrack=500 |
If it works, run it and do all the other update steps, if not, try an older snapshot.
Move on to a newer snapshot or even you up to date repo
The process is described in detail. That page is a mess as it also covers CVS but the CVS archive is gone. It's been moved into git. That only matters if you want to get back before 2016.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
modnaruved
Apprentice
Joined: 21 Mar 2011
Posts: 163
|
| Posted: Thu Mar 06, 2025 3:09 pm Post subject: |
|
|
| NeddySeagoon wrote: | modnaruved,
You must not change the profile until your Gentoo is up to date.
You may not be able to get the latest glibc and gcc but get the lastest that your profile permits.
|
NeddySeagoon,
It seems reasonable to first update the system as much as possible while staying on the current profile — just as you initially suggested. After that, switching to the new profile directly might make the most sense. The squashfs or Git options remain interesting alternatives, but for now, I’m leaning towards simply proceeding with a full sync.
Also, potential issues with getting the very latest versions of glibc and gcc don't seem critical and likely won’t interfere with stabilizing the current profile to its most up-to-date state. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
