Bug 231289 – Output package list to be rebuild with app-admin/python-updater

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Christian Faulhammer (RETIRED) 2008-07-09 11:56:41 UTC]

If the emerge process fails when resolving dependencies (because the needed ebuild isn't there anymore and a newer version needs to be emerged), one has to go through the whole process of python-updater again.  If all to be emerged packages were output as a ready list, one could copy it, and run the emerge command oneself.

[Comment 1 Ali Polatel (RETIRED) 2008-07-24 01:23:19 UTC]

python-updater -c cat

[Comment 2 Gokdeniz Karadag 2008-10-05 16:14:02 UTC]

I think piping to cat is not an exact replacement of this functionality.

A use case; Joe wants to run python-updater after an upgrade. He gives no parameters to python-updater, wanting to finish the process. A problem occurs during the emerge and it is interrupted [1]. After fixing the problem he must have to run pytohn-updater all over again, which takes a good amount of time to determine broken packages.

To fix it, patch is a one liner

========== patch ============
--- 1/python-updater    2008-10-05 19:11:54.000000000 +0300
+++ 2/python-updater    2008-10-05 19:13:05.000000000 +0300
@@ -405,6 +405,7 @@

 # (Pretend to) remerge packages
 if [[ -n "${PKGS_TO_REMERGE}" ]]; then
+    echo -e "Running\n${PMS_COMMAND[${PMS_INDEX}]} ${PMS_OPTIONS[${PMS_INDEX}]} ${PKGS_TO_REMERGE}"
     ${PMS_COMMAND[${PMS_INDEX}]} ${PMS_OPTIONS[${PMS_INDEX}]} ${PKGS_TO_REMERGE}
 else
     einfo "No packages needs to be remerged."


============================
[1] Possible reasons: 
*a failed ebuild which is fixed very recently and a portage tree sync would fix it
*fetch restriction
*unavailable binary package while using --usepkgonly (this actually happened to me)
* etc..