On Oct 17, 2014, at 08:57 AM, Данило Шеган wrote:
>Cheers Barry, much appreciated!
No problem!
>It seems it's all done and released in main:
> http://packages.ubuntu.com/source/utopic/pyparsing
> https://launchpad.net/ubuntu/utopic/+source/pyparsing/2.0.3+dfsg1-1
>
>Let me know if I still need
Cheers Barry, much appreciated!
It seems it's all done and released in main:
http://packages.ubuntu.com/source/utopic/pyparsing
https://launchpad.net/ubuntu/utopic/+source/pyparsing/2.0.3+dfsg1-1
Let me know if I still need to ping ubuntu-release for an approval.
--
You received this bug no
I just uploaded 2.0.3+dfsg1-1 to unstable. As soon as it lands there,
I'll do a sync to utopic. Can you give ubuntu-release a heads up that
this needs to be approved?
** Changed in: pyparsing (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you
Should be relatively straightforward to update Debian to the latest and
then sync to Utopic. I'll start looking at that. If it's a pure bug
fix release, it won't require an FFE, but it will require approval by
the release team, since final freeze is today.
** Changed in: pyparsing (Ubuntu)
Thanks for the quick turn-around, Robie!
There actually is a 2.0.3 release at pypi:
https://pypi.python.org/pypi/pyparsing/2.0.3#downloads
FWIW, not having this in would result in a bunch of Canonical Landscape
engineers (>15) unable to switch to Utopic for development, so consider
me shouting :)
Thanks. Looks like 2.0.3 is tagged upstream but not yet released.
It would be easiest to fix this in Debian and then sync (looks like a
bugfix only release, with test suite additions, so it seems pretty
safe).
But to make Utopic before release, we need to cherry-pick the fix, or
pull in 2.0.3 fro