View previous topic :: View next topic |
Author |
Message |
iQQator n00b
Joined: 27 Feb 2020 Posts: 12 Location: Russia
|
Posted: Tue Jun 02, 2020 12:04 pm Post subject: resuming a emerge --emptytree system |
|
|
[Moderator note: split from the 15 year old topic resuming a emerge --emptytree system, which was last active in October 2005. -Hu]
kimchi_sg wrote: | OK, since the OP seems to have emerged autoconf right after the emerge -e system failure, this will not be helpful to him. But in case anyone else with similar compile failures looks here and they have not emerged autoconf yet, this advice will save them a lot of time.
- Copy /var/cache/edb/mtimedb to a safe location. I prefer root's home directory for this.
Code: | cp /var/cache/edb/mtimedb ~ |
- Emerge whatever package is needed. For example, those compile failures caused by "missing automake" will require emerge automake
- If the emerge missing-package-name completes safely without errors, move the backup copy of mtimedb back into position and overwrite the mtimedb that is already there.
Code: | mv ~/mtimedb /var/cache/edb |
Hope this will help someone save lots of time. It did for me. |
This is not like --oneshot -1 ?) |
|
Back to top |
|
|
Ant P. Watchman
Joined: 18 Apr 2009 Posts: 6920
|
Posted: Wed Jun 03, 2020 7:56 am Post subject: |
|
|
iQQator wrote: | This is not like --oneshot -1 ?) |
--oneshot is for /var/lib/portage/world. /var/cache/edb/mtimedb contains the calculated emerge list for --resume, there's no other way to preserve that across emerges.
If the resume list's already been lost, one workaround would be to manually reinstall packages older than a known date -
Code: | emerge --nodeps -1p $(cd $(portageq vdb_path); find -mindepth 2 -maxdepth 2 -mtime +3 -printf '>=%P\n') |
|
|
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
|
|