[Piuparts-devel] sort-issues-by-rdep prep

[Dave Steele]

On Thu, Apr 4, 2013 at 9:31 AM, Andreas Beckmann <anbe at debian.org> wrote:
>
> I'd recommend reverting
>
> 45eccb50c328d68e579249cee93dcafcc8fcfaf9
>   detect_well_known_errors - Restore recheck and recheck-failed options.
>
> e0d138b59bddb70e712a1613c7fcd82a60323db5
>   Bump the required python version to 2.7.
>
> because in the current state this seems to be broken if activated on
> piatti which still has python 2.6 as default (untested)
>
> the "missing" options can be reactivated later
>
> a proper switch to python 2.7 should include getting rid of all the 2.6
> specific things ...
>
> (should we prepare switching to argparse in piuparts.py, too?)
>
> the next probelm I see for activating on piatti is that PYTHONPATH
> issue, so there should probably a shell wrapper script around dwke.py
> (like piuparts-master.in)
>
> Andreas
>

Is there a reason for piatti to run from /org (or /sys), going
forward? You've jumped through a number of hoops to have piatti
coexist with a stock install, including the need for PYTHONPATH, shell
wrappers, and variable substitution in dozens of files. Meanwhile, the
standard packages were left in a broken state for over a year because
of the issue. Maintaining the git mode means you have two independent
product suites to test and maintain (three if any piuparts-* packages
are installed on piatti or your test systems). You've got an
opportunity to do structural rework with the VM migration. It is worth
consideration.

In the meantime, I'll add the wrapper, and revert the 2.7 requirement
(once there is a final call on Holger's subsequent comment on whether
it is to be reverted).