On 2/13/15 6:56 AM, Igor Bondarenko wrote: > Please use this thread for any discussion of the 1.2.1 release, and vote on > the > [VOTE] thread. >
I got some test failures on OSX, but it passed clean on Ubuntu and CentOS. OSX isn't really one of our main targets, so I'm not too concerned. https://forge-allura.apache.org/p/allura/pastebin/54de46236d19cd2420b31319 And I got warnings for each of our packages, when I had a brand new virtualenv (and new setuptools I think is the key difference): /Users/brondsem/dev/asf-allura-dev-releases/venv/lib/python2.7/site-packages/pkg_resources/__init__.py:2510: PEP440Warning: 'ForgeBlog (0.0dev-r0)' is being parsed as a legacy, non PEP 440, version. You may find odd behavior and sort order. In particular it will be sorted as less than 0.0. It is recommend to migrate to PEP 440 compatible versions. I think we'll need to change our setup.cfg files to drop tag_svn_revision. And changing `tag_build = dev` to `tag_build = dev0` seems to be the recommended way to have a -dev suffix. Since we don't specify version numbers for our individual tool packages. -- Dave Brondsema : [email protected] http://www.brondsema.net : personal http://www.splike.com : programming <><
