Upgrade python-wsme from 0.7.0 to 0.9.1.
Signed-off-by: Huang Qiyu
---
.../python/{python-wsme_0.7.0.bb => python-wsme_0.9.1.bb} | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
rename
1) Upgrade python-testtools from 1.8.0 to 2.2.0.
2) License checksum changed,since the testtools authors changed.
Signed-off-by: Huang Qiyu
---
.../{python-testtools_1.8.0.bb => python-testtools_2.2.0.bb} | 9 -
1 file changed, 4 insertions(+), 5
I agree to these changes. It dosen't matter to use patch " python-sqlalchemy:
1.0.9 -> 1.1.5".
Huang
> -Original Message-
> From: Mark Asselstine [mailto:mark.asselst...@windriver.com]
> Sent: Friday, January 20, 2017 3:33 AM
> To: meta-virtualization@yoctoproject.org;
Upgrade python-mox3 from 0.9.0 to 0.20.0.
Signed-off-by: Huang Qiyu
---
.../python/{python-mox3_0.9.0.bb => python-mox3_0.20.0.bb} | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
rename
From: Huang Qiyu
1) Copy the v1.0.9 bb to create python-sqlalchemy v1.1.5.
2) License checksum changed,since the copyright years were updated.
Signed-off-by: Huang Qiyu
Signed-off-by: Mark Asselstine
---
There are two distinct active release series of the python sqlalchemy
package (1.0.x and 1.1.x). For some packages, like docker-registry
there appears to be no incompatibility issues when using the 1.0.x vs
the 1.1.x series, however, there are openstack packages which are only
compatible with the
According to the changelog at
(http://docs.sqlalchemy.org/en/latest/changelog/changelog_10.html)
this is mostly bug fixes. We need a version >= 1.0.10 to properly
support the python-oslo.db uprev to stable/newton in
meta-cloud-services.
NOTE the license checksum has changed do to content change,
On Wed, Jan 18, 2017 at 3:36 AM, Huang Qiyu wrote:
> 1) Upgrade python-sqlalchemy from 1.0.9 to 1.1.5.
> 2) License checksum changed,since the copyright years were updated.
>
> Signed-off-by: Huang Qiyu
As I mentioned yesterday we still