<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-cloud-services.git/recipes-devtools/python/python-pyparsing_2.0.1.bb, branch wrynose</title>
<subtitle>Mirror of git.yoctoproject.org/meta-cloud-services.git</subtitle>
<id>https://git.enea.com/cgit/linux/meta-cloud-services.git/atom?h=wrynose</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/atom?h=wrynose'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/'/>
<updated>2020-01-22T16:21:37+00:00</updated>
<entry>
<title>misc: python3 readiness</title>
<updated>2020-01-22T16:21:37+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2020-01-22T16:21:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/commit/?id=ba0ca845af46a5d9c05dbd8943744a4e78d268d5'/>
<id>urn:sha1:ba0ca845af46a5d9c05dbd8943744a4e78d268d5</id>
<content type='text'>
Updating the packages in m-c-s to be python3 parse safe. These are not
runtime tested, but will pass layer inclusion and parsing.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>python-pyparsing: fix SRC_URI's checksum</title>
<updated>2018-02-27T12:59:32+00:00</updated>
<author>
<name>Robert Yang</name>
<email>liezhi.yang@windriver.com</email>
</author>
<published>2018-02-27T07:02:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/commit/?id=15ec4cbd03c9c5372b59eb9c2eecc1512bd1c99e'/>
<id>urn:sha1:15ec4cbd03c9c5372b59eb9c2eecc1512bd1c99e</id>
<content type='text'>
The checksum was changed because the source was changed from .zip to .tar.gz,
see 3d512115129e2cea97067d23cb72fea62b70dd39 for more details.

Signed-off-by: Robert Yang &lt;liezhi.yang@windriver.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
</content>
</entry>
<entry>
<title>python-*: switch remaining pypi recipes to use the pypi class</title>
<updated>2017-11-14T17:40:01+00:00</updated>
<author>
<name>Mark Asselstine</name>
<email>mark.asselstine@windriver.com</email>
</author>
<published>2017-11-13T21:48:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/commit/?id=3d512115129e2cea97067d23cb72fea62b70dd39'/>
<id>urn:sha1:3d512115129e2cea97067d23cb72fea62b70dd39</id>
<content type='text'>
Cleanup the various python-* recipes which download from pypi. The
biggest change is to "inherit pypi" which should result in us always
using current pypi best practices. This will for example ensure we are
using https and not http which is apparently going to be disabled
soon.

In most cases we are able to drop SRC_URI, however, for some recipes
using archived versions of packages we must set PYPI_SRC_URI to
overwrite what the pypi class would derive. For example when the
archive is a zip and not a tar.gz.

In all cases we can drop the defining of 'S' and 'PR' as the pypi
class and the PR server will set these correctly.

In most cases we can drop SRCNAME. Where needed we instead set
PYPI_PACKAGE to overwrite the derived name that the pypi class would
otherwise calculate.

Signed-off-by: Mark Asselstine &lt;mark.asselstine@windriver.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
</content>
</entry>
<entry>
<title>python-pyparsing: Move from meta-openstack to meta-cloud-services</title>
<updated>2017-06-29T19:27:41+00:00</updated>
<author>
<name>He Zhe</name>
<email>zhe.he@windriver.com</email>
</author>
<published>2017-06-28T08:52:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/commit/?id=fea2e20227138b90ee406bf4e2c9fca5532c547a'/>
<id>urn:sha1:fea2e20227138b90ee406bf4e2c9fca5532c547a</id>
<content type='text'>
It's not an openstack specific package.

Signed-off-by: He Zhe &lt;zhe.he@windriver.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
</content>
</entry>
</feed>
