I do wonder here at the chroot tinderbox image amd64-desktop-unstable_20150918-212348 about the doubled entry : 1444428548: Started emerge on: Oct 10, 2015 00:09:07 1444428548: *** emerge --oneshot --nospinner --color=n --accept-restrict=-fetch --accept-properties=-interactive --verbose --deep --quiet-build=y --keep-going --tree app-admin/syslog-ng:0 app-backup/spideroak-bin:0 app-office/openoffice-bin:0 app-office/openoffice-bin:0 dev-python/gnome-python-desktop-base:0 games-engines/gemrb:0 games-server/crossfire-server:0 games-strategy/freeorion:0 net-dialup/freeradius:0
Why do you need to run python-updater?
Short: Because either portage forces me to do it or python is updated. Long: I do have this snippet in my tinderbox script: grep -q -e "run 'python-updater'" -e "\[ebuild .*\].*dev-lang/python-[0-9]" $tmp if [[ $? -eq 0 ]]; then python-updater &>$log if [[ $? -ne 0 ]]; then GotAnIssue Finish "python-updater failed" fi fi
(In reply to Toralf Förster from comment #2) > Short: > Because either portage forces me to do it or python is updated. > > Long: > I do have this snippet in my tinderbox script: > > grep -q -e "run 'python-updater'" -e "\[ebuild > .*\].*dev-lang/python-[0-9]" $tmp > if [[ $? -eq 0 ]]; then > python-updater &>$log > if [[ $? -ne 0 ]]; then > GotAnIssue > Finish "python-updater failed" > fi > fi You should file bugs for every package still requiring this. We really need ot fade this out ASAP.
what do you mean?
python-updater is an obsolete tool that is unnecessary for ebuilds using the python-r1 eclasses. Rather than try to fix python-updater, it would be more productive to convert the affected ebuilds.
