Currently, when something elaborate such as `emerge -e system' fails intermittently, doing a subsequent emerge run for another target clobbers the original target list, so that an `emerge --resume' will then no longer find anything to do. It seems there is no way to retrieve the 1) original list of atoms or indeed 2) the remaining list of atoms that were going to be emerged. I assume such a list might be retrievable from some database, but no command or documentation seems to point out how to do this.
(In reply to Jeroen Roovers from comment #0) > It seems there is no way to retrieve the 1) original list of atoms or indeed > 2) the remaining list of atoms that were going to be emerged. There are "resume" and "resume_backup" dictionaries in mtimedb (/var/cache/edb/mtimedb). - "favorites" key with value being a list of atoms requested at command line. - "mergelist" key with value being a list of lists containing information about remaining packages. One-line examples: python -c $'import portage\nresume_dict = portage.mtimedb.get("resume")\nif resume_dict is not None:\n for x in resume_dict["mergelist"]: print(x[2])' python -c $'import portage\nresume_dict = portage.mtimedb.get("resume_backup")\nif resume_dict is not None:\n for x in resume_dict["mergelist"]: print(x[2])'
(In reply to Arfrever Frehtes Taifersar Arahesis from comment #1) > (In reply to Jeroen Roovers from comment #0) > > It seems there is no way to retrieve the 1) original list of atoms or indeed > > 2) the remaining list of atoms that were going to be emerged. > > There are "resume" and "resume_backup" dictionaries in mtimedb > (/var/cache/edb/mtimedb). > - "favorites" key with value being a list of atoms requested at command line. > - "mergelist" key with value being a list of lists containing information > about remaining packages. > > One-line examples: Sure, I was aware of that, but this is about exposing that information as text, as an emerge feature.
