FFE: update to 2.0.1

[Julian Taylor]

pyparsing 2.0.0 and 1.5.7 have a serious bug breaking any forward grammar:
http://sourceforge.net/p/pyparsing/bugs/67/

this is fixed in 2.0.1 with a very small patch, but it is complicated due to a split into two source packages which happened in 2.0.0 and 1.5.7, the python3 source is python3-pyparsing.

in 2.0.1 this is reverted again and it is one source package again.
I contacted upstream and they said this is intended to stay this way now.

To resolve the issue we have two options:
patch 1.5.7 and 2.0.0, easy but programs that check for version numbers to avoid the bug will not accept the package.
This is the case e.g. with matplotlib 1.3, I have filed a patch which was accepted but there might be more cases out there.

update pyparsing to 2.0.1 which is a bit more involved thus the FFe request.
pyparsing will again provide python-pyparsing and python3-pyparsing
python3-pyparsing(binary) from python3-pyparsing(source) will be obsoleted by pyparsing 2.0.1 so no upgrade issues should occur, once its published python3-pyparsing (source) can be removed.
I have contacted the debian maintainer about this but he is *very* hard to get a hold of, so I want to do it in ubuntu directly rather soon.

[Scott Kitterman (kitterman)]

Ack. Please go ahead.

[Barry Warsaw (barry)]

On Sep 04, 2013, at 09:26 PM, Julian Taylor wrote:

>To resolve the issue we have two options:
>
>patch 1.5.7 and 2.0.0, easy but programs that check for version numbers to
>avoid the bug will not accept the package. This is the case e.g. with
>matplotlib 1.3, I have filed a patch which was accepted but there might be
>more cases out there.
>
>update pyparsing to 2.0.1 which is a bit more involved thus the FFe request.
>pyparsing will again provide python-pyparsing and python3-pyparsing
>python3-pyparsing(binary) from python3-pyparsing(source) will be obsoleted by
>pyparsing 2.0.1 so no upgrade issues should occur, once its published
>python3-pyparsing (source) can be removed. I have contacted the debian
>maintainer about this but he is *very* hard to get a hold of, so I want to do
>it in ubuntu directly rather soon.

I'm not familiar with the specifics, but from your description, I agree this
sounds like the best course of action.

[Scott Kitterman (kitterman)]

This bug was fixed in the package pyparsing - 2.0.1+dfsg1-1
Sponsored for Julian Taylor (jtaylor)

---------------
pyparsing (2.0.1+dfsg1-1) unstable; urgency=low

  * New upstream release
  * provide python3-pyparsing again
  * add autopkgtests (Closes: #706317)

 -- Julian Taylor <email address hidden> Wed, 11 Sep 2013 12:22:36 +0200