<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-cloud-services.git/meta-openstack/recipes-devtools/python/python-pycrypto_2.6.bb, branch morty</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=morty</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/atom?h=morty'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/'/>
<updated>2015-04-29T16:29:41+00:00</updated>
<entry>
<title>python-pycrypto: upgrade to 2.6.1</title>
<updated>2015-04-29T16:29:41+00:00</updated>
<author>
<name>Jackie Huang</name>
<email>jackie.huang@windriver.com</email>
</author>
<published>2015-04-29T03:08:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/commit/?id=dd324f3f25004eb023b15097233bbba81310d1d4'/>
<id>urn:sha1:dd324f3f25004eb023b15097233bbba81310d1d4</id>
<content type='text'>
Signed-off-by: Jackie Huang &lt;jackie.huang@windriver.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
</content>
</entry>
<entry>
<title>QA: fix build and runtime warnings</title>
<updated>2015-02-21T05:42:47+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@windriver.com</email>
</author>
<published>2015-02-21T05:41:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/commit/?id=441977d076e5c0aeace44ba65d301b5c6c61d59f'/>
<id>urn:sha1:441977d076e5c0aeace44ba65d301b5c6c61d59f</id>
<content type='text'>
oe-core now warns on detected missing runtime and build time warnings.
So we update our recipes to have these missingn deps (largely bash).

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
</content>
</entry>
<entry>
<title>pycrypto: void src/build separation</title>
<updated>2014-05-13T13:42:02+00:00</updated>
<author>
<name>Mark Asselstine</name>
<email>mark.asselstine@windriver.com</email>
</author>
<published>2014-05-09T13:07:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/commit/?id=c7185e4dfe4c49c6bbe0b3533257cd8bf8135f7c'/>
<id>urn:sha1:c7185e4dfe4c49c6bbe0b3533257cd8bf8135f7c</id>
<content type='text'>
distutils.bbclass does not work when there is a build/src separation
so inherit autotools-brokensep so continue building in the src dir.

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-pycrypto: override do_install</title>
<updated>2013-10-03T05:15:42+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@windriver.com</email>
</author>
<published>2013-09-13T16:34:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/commit/?id=7db05c524eeb3aaae3a34544bfb7076ecb71b88d'/>
<id>urn:sha1:7db05c524eeb3aaae3a34544bfb7076ecb71b88d</id>
<content type='text'>
python-pycrypto must inherit autotools to have the proper parameters
passed to its configuration phase. But this same package doesn't have
a "make install" target, so the autotools added install rule errors
when run against the package.

To fix this, we pick and chose what we execute by implementing our
own do_install and calling the class routines explicitly.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
</content>
</entry>
<entry>
<title>python-pycrypto: Fix configure failure</title>
<updated>2013-09-07T04:26:54+00:00</updated>
<author>
<name>Mark Hatle</name>
<email>mark.hatle@windriver.com</email>
</author>
<published>2013-09-06T22:30:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/commit/?id=bd6c1e8fb60d628c5818b60094eff1d3406eb618'/>
<id>urn:sha1:bd6c1e8fb60d628c5818b60094eff1d3406eb618</id>
<content type='text'>
Signed-off-by: Mark Hatle &lt;mark.hatle@windriver.com&gt;
</content>
</entry>
<entry>
<title>pycrypto: fix QA errors and configure fail</title>
<updated>2013-09-06T22:00:08+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@windriver.com</email>
</author>
<published>2013-09-06T20:33:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/commit/?id=4d830901c31baf8b507ebd38aa9f226c7148d2b1'/>
<id>urn:sha1:4d830901c31baf8b507ebd38aa9f226c7148d2b1</id>
<content type='text'>
Two fixes in this change, one is to clearly set capabilities and
trigger configure, to avoid build and configuration issues.

The second is to workaround an autoconf bug by exporting: ac_cv_func_malloc_0_nonnull=yes

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
</content>
</entry>
<entry>
<title>python-pycrypto: change upstream reference</title>
<updated>2013-08-28T22:41:59+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@windriver.com</email>
</author>
<published>2013-08-10T04:43:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/commit/?id=f8bd276f5bd89d9d4ae5f44e6515c04b78590a5d'/>
<id>urn:sha1:f8bd276f5bd89d9d4ae5f44e6515c04b78590a5d</id>
<content type='text'>
ftp.dlitz.net is not always avaialble, switching the upstream to
pypi.python.org results in reliable builds.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
</content>
</entry>
<entry>
<title>python-pycrypto: added 2.6</title>
<updated>2013-08-28T22:41:55+00:00</updated>
<author>
<name>Mihai Prica</name>
<email>prica.mihai@gmail.com</email>
</author>
<published>2013-05-17T14:26:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/commit/?id=421ddd1427972d9e70b24a0e40789a3bdd1ba0e0'/>
<id>urn:sha1:421ddd1427972d9e70b24a0e40789a3bdd1ba0e0</id>
<content type='text'>
Signed-off-by: Mihai Prica &lt;prica.mihai@gmail.com&gt;
</content>
</entry>
</feed>
