Re: Migration/Triage for 2019-12-24

2020-01-07 Thread Lucas Kanashiro
Hi, On Tue, Jan 7, 2020 at 9:01 AM Andreas Hasenack wrote: > Hello, > > On Mon, Jan 6, 2020 at 10:04 PM Bryce Harrington > wrote: > > > * nut: Argparse is flagging an error from specifying --xsltproc-opts > > multiple times (I think?) which perhaps may be a behavioral change > > from

Re: Migration/Triage for 2019-12-24

2020-01-07 Thread Andreas Hasenack
Hello, On Mon, Jan 6, 2020 at 10:04 PM Bryce Harrington wrote: > * nut: Argparse is flagging an error from specifying --xsltproc-opts > multiple times (I think?) which perhaps may be a behavioral change > from either py2 to py3, or else from optparse to argparse. > - "error: argument

Re: Migration/Triage for 2019-12-24

2020-01-06 Thread Steve Langasek
On Mon, Jan 06, 2020 at 05:03:20PM -0800, Bryce Harrington wrote: > * These seem to be transitioning from py2 to py3, and need to go in as a > set. > - python-oauth > - python-oauthlib > - blinker > - pyjwt - this includes autopkgtests for py 2 and 3, and the build log > mentions

Migration/Triage for 2019-12-24

2020-01-06 Thread Bryce Harrington
== Proposed Migration == I did a quick broad survey over the current proposed migration failures, just to identify what's wrong for each. I didn't have time to dig in very deeply but hoping this is of some use to others. * A bunch of the failures are related to some sort of problem with 'six'.