Re: [openstack-dev] [oslo][horizon][infra] oslo.policy in django-openstack-auth fails with stable/juno global requirement check
Excerpts from Akihiro Motoki's message of 2015-03-16 11:53:07 +0900: Thanks Doug, It is a good direction to have the stable branches for all libraries. It seems better that I wait for adopting oslo.policy in django-openstack-auth. In the current infra, a library specified in LIBS_FROM_GIT will be installed even if its version does not match global-requirement (for example, even if global-requirement requires =1.1.9, dev version of library which is newer than 1.1.9 will be installed and leads to global-requirement failure. It seems the version check is not so easy and seems better to wait stable/ branches are created I would have to double check, but I believe that if the library has a stable branch that's the version that will be checked out and so LIBS_FROM_GIT will cause the HEAD of the stable branch to be installed. I don't think that solves your problem, since django-openstack-auth doesn't yet have a stable branch, but once it does the gate should continue to work as you want and you will be able to introduce the policy library on the master branch without having any effect on the stable branch tests. Doug Akihiro 2015-03-16 1:45 GMT+09:00 Doug Hellmann d...@doughellmann.com: Excerpts from Akihiro Motoki's message of 2015-03-16 01:25:08 +0900: Hi Oslo team, I am working on adopting the graduated oslo.policy in django-openstack-auth [1] but I have a question on how to migrate openstack.common.policy to oslo.policy in libraries which have no stable branch. django-openstack-auth has no stable branches as other python-*client. stable/juno global-requirements requries django_openstack_auth=1.1.7,!=1.1.8,=1.1.9, and the development is for 1.1.10 or 1.2.x, so I first thought it is no problem. However, in the review of [1], gate-tempest-dsvm-neutron-src-django_openstack_auth-juno fails with the error that oslo.policy is not in global-requirements in stable/juno. Is it a problem in the infra side? Or is it a thing we should avoid? Any advise will be appreciated. All libraries should have stable branches going forward because we are capping requirements in the stable branches. See https://review.openstack.org/#/c/155072/ for details. Doug [1] https://review.openstack.org/#/c/164420/ Thanks, Akihiro __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [oslo][horizon][infra] oslo.policy in django-openstack-auth fails with stable/juno global requirement check
Hi Oslo team, I am working on adopting the graduated oslo.policy in django-openstack-auth [1] but I have a question on how to migrate openstack.common.policy to oslo.policy in libraries which have no stable branch. django-openstack-auth has no stable branches as other python-*client. stable/juno global-requirements requries django_openstack_auth=1.1.7,!=1.1.8,=1.1.9, and the development is for 1.1.10 or 1.2.x, so I first thought it is no problem. However, in the review of [1], gate-tempest-dsvm-neutron-src-django_openstack_auth-juno fails with the error that oslo.policy is not in global-requirements in stable/juno. Is it a problem in the infra side? Or is it a thing we should avoid? Any advise will be appreciated. [1] https://review.openstack.org/#/c/164420/ Thanks, Akihiro __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [oslo][horizon][infra] oslo.policy in django-openstack-auth fails with stable/juno global requirement check
Excerpts from Akihiro Motoki's message of 2015-03-16 01:25:08 +0900: Hi Oslo team, I am working on adopting the graduated oslo.policy in django-openstack-auth [1] but I have a question on how to migrate openstack.common.policy to oslo.policy in libraries which have no stable branch. django-openstack-auth has no stable branches as other python-*client. stable/juno global-requirements requries django_openstack_auth=1.1.7,!=1.1.8,=1.1.9, and the development is for 1.1.10 or 1.2.x, so I first thought it is no problem. However, in the review of [1], gate-tempest-dsvm-neutron-src-django_openstack_auth-juno fails with the error that oslo.policy is not in global-requirements in stable/juno. Is it a problem in the infra side? Or is it a thing we should avoid? Any advise will be appreciated. All libraries should have stable branches going forward because we are capping requirements in the stable branches. See https://review.openstack.org/#/c/155072/ for details. Doug [1] https://review.openstack.org/#/c/164420/ Thanks, Akihiro __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [oslo][horizon][infra] oslo.policy in django-openstack-auth fails with stable/juno global requirement check
Thanks Doug, It is a good direction to have the stable branches for all libraries. It seems better that I wait for adopting oslo.policy in django-openstack-auth. In the current infra, a library specified in LIBS_FROM_GIT will be installed even if its version does not match global-requirement (for example, even if global-requirement requires =1.1.9, dev version of library which is newer than 1.1.9 will be installed and leads to global-requirement failure. It seems the version check is not so easy and seems better to wait stable/ branches are created Akihiro 2015-03-16 1:45 GMT+09:00 Doug Hellmann d...@doughellmann.com: Excerpts from Akihiro Motoki's message of 2015-03-16 01:25:08 +0900: Hi Oslo team, I am working on adopting the graduated oslo.policy in django-openstack-auth [1] but I have a question on how to migrate openstack.common.policy to oslo.policy in libraries which have no stable branch. django-openstack-auth has no stable branches as other python-*client. stable/juno global-requirements requries django_openstack_auth=1.1.7,!=1.1.8,=1.1.9, and the development is for 1.1.10 or 1.2.x, so I first thought it is no problem. However, in the review of [1], gate-tempest-dsvm-neutron-src-django_openstack_auth-juno fails with the error that oslo.policy is not in global-requirements in stable/juno. Is it a problem in the infra side? Or is it a thing we should avoid? Any advise will be appreciated. All libraries should have stable branches going forward because we are capping requirements in the stable branches. See https://review.openstack.org/#/c/155072/ for details. Doug [1] https://review.openstack.org/#/c/164420/ Thanks, Akihiro __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Akihiro Motoki amot...@gmail.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
