Re: [openstack-dev] [all] [test-]requirements-PYN.txt will cause gate failures on check-*-requirements

2015-07-02 Thread Davanum Srinivas
Sergey,

i don't think so. Please go ahead and file one for oslo.* if you get a chance.

-- dims

On Thu, Jul 2, 2015 at 9:58 AM, Sergey Vilgelm svilg...@mirantis.com wrote:
 Do we have a common bug on launchpad for this work, to collect all patches?

 On Thu, Jul 2, 2015 at 2:39 AM, Robert Collins robe...@robertcollins.net
 wrote:

 On 2 July 2015 at 11:36, Robert Collins robe...@robertcollins.net wrote:
  On 29 June 2015 at 15:59, Robert Collins robe...@robertcollins.net
  wrote:
  Hi, so we're nearly ready to deprecate the python-version-specific
  requirements files. Once we have infra's requirements cross checking
  jobs all copacetic again, we should be able to move forward.
 
  So we've got them working again in master, and I'm about to work on
  support for stable - things are a bit awkward and all tied together
  there. Sorry for the extended disruption on requirement updates!
 
  The status right now is:
  - all stable jobs are failing on requirements checks, because we don't
  have the needed code modules in the openstack/requirements stable
  branches. This is critical and my top priority to unblock everything
  stable/.
 
  - master requirement checks should work Just Fine, as long as the
  requirements are current. However the bot doesn't know enough to merge
  -PYN requirements files for you. So you need to do that manually. The
  easiest way IMO is:
 
  REQS=$(pwd)/reqs
  virtualenv $REQS
  . $REQS/bin/activate
  pip install -U pip setuptools -e
 
  git+https://git.openstack.org/openstack/requirements#egg=openstack.requirements
  cd path-to-project
  cat requirements-py3.txt  requirements.txt
  cat test-requirements-py3.txt  test-requirements.txt
  git rm *requirements-py3.txt
  update-requirements --source $REQS/src/openstack.requirements .
  git diff
  # you'll have some cruft to cleanup - duplicate comments at the bottom
  of the files and so on
  # commit and review
  # repeat from 'cd path-to-project' as needed.
 
  One word of caution. Some of the projects i've done this for -
  keystone and glance - had -e editable lines in their requirements
  files: these got through because infra wasn't linting the -py3 files
  at all until recently, and I'm not yet sure if we can get them back
  in. So we may need to actually fixup those dependencies asap. E.g. get
  /a/ release of glance-store out with its partial python3 support, to
  permit the glance python34 gate to work at all.

 Second word of caution. tox.ini probably needs editing too.

 -Rob



 --
 Robert Collins rbtcoll...@hp.com
 Distinguished Technologist
 HP Converged Cloud

 __
 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




 --
 Thanks,
 Sergey Vilgelm
 OpenStack Software Engineer
 Mirantis Inc.
 Skype: sergey.vilgelm
 Phone: +36 70 512 3836

 __
 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




-- 
Davanum Srinivas :: https://twitter.com/dims

__
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] [all] [test-]requirements-PYN.txt will cause gate failures on check-*-requirements

2015-07-02 Thread Sergey Vilgelm
Do we have a common bug on launchpad for this work, to collect all patches?

On Thu, Jul 2, 2015 at 2:39 AM, Robert Collins robe...@robertcollins.net
wrote:

 On 2 July 2015 at 11:36, Robert Collins robe...@robertcollins.net wrote:
  On 29 June 2015 at 15:59, Robert Collins robe...@robertcollins.net
 wrote:
  Hi, so we're nearly ready to deprecate the python-version-specific
  requirements files. Once we have infra's requirements cross checking
  jobs all copacetic again, we should be able to move forward.
 
  So we've got them working again in master, and I'm about to work on
  support for stable - things are a bit awkward and all tied together
  there. Sorry for the extended disruption on requirement updates!
 
  The status right now is:
  - all stable jobs are failing on requirements checks, because we don't
  have the needed code modules in the openstack/requirements stable
  branches. This is critical and my top priority to unblock everything
  stable/.
 
  - master requirement checks should work Just Fine, as long as the
  requirements are current. However the bot doesn't know enough to merge
  -PYN requirements files for you. So you need to do that manually. The
  easiest way IMO is:
 
  REQS=$(pwd)/reqs
  virtualenv $REQS
  . $REQS/bin/activate
  pip install -U pip setuptools -e
  git+
 https://git.openstack.org/openstack/requirements#egg=openstack.requirements
  cd path-to-project
  cat requirements-py3.txt  requirements.txt
  cat test-requirements-py3.txt  test-requirements.txt
  git rm *requirements-py3.txt
  update-requirements --source $REQS/src/openstack.requirements .
  git diff
  # you'll have some cruft to cleanup - duplicate comments at the bottom
  of the files and so on
  # commit and review
  # repeat from 'cd path-to-project' as needed.
 
  One word of caution. Some of the projects i've done this for -
  keystone and glance - had -e editable lines in their requirements
  files: these got through because infra wasn't linting the -py3 files
  at all until recently, and I'm not yet sure if we can get them back
  in. So we may need to actually fixup those dependencies asap. E.g. get
  /a/ release of glance-store out with its partial python3 support, to
  permit the glance python34 gate to work at all.

 Second word of caution. tox.ini probably needs editing too.

 -Rob



 --
 Robert Collins rbtcoll...@hp.com
 Distinguished Technologist
 HP Converged Cloud

 __
 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




-- 
Thanks,
Sergey Vilgelm
OpenStack Software Engineer
Mirantis Inc.
Skype: sergey.vilgelm
Phone: +36 70 512 3836
__
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] [all] [test-]requirements-PYN.txt will cause gate failures on check-*-requirements

2015-07-01 Thread Robert Collins
On 2 July 2015 at 11:36, Robert Collins robe...@robertcollins.net wrote:
 On 29 June 2015 at 15:59, Robert Collins robe...@robertcollins.net wrote:
 Hi, so we're nearly ready to deprecate the python-version-specific
 requirements files. Once we have infra's requirements cross checking
 jobs all copacetic again, we should be able to move forward.

 So we've got them working again in master, and I'm about to work on
 support for stable - things are a bit awkward and all tied together
 there. Sorry for the extended disruption on requirement updates!

 The status right now is:
 - all stable jobs are failing on requirements checks, because we don't
 have the needed code modules in the openstack/requirements stable
 branches. This is critical and my top priority to unblock everything
 stable/.

 - master requirement checks should work Just Fine, as long as the
 requirements are current. However the bot doesn't know enough to merge
 -PYN requirements files for you. So you need to do that manually. The
 easiest way IMO is:

 REQS=$(pwd)/reqs
 virtualenv $REQS
 . $REQS/bin/activate
 pip install -U pip setuptools -e
 git+https://git.openstack.org/openstack/requirements#egg=openstack.requirements
 cd path-to-project
 cat requirements-py3.txt  requirements.txt
 cat test-requirements-py3.txt  test-requirements.txt
 git rm *requirements-py3.txt
 update-requirements --source $REQS/src/openstack.requirements .
 git diff
 # you'll have some cruft to cleanup - duplicate comments at the bottom
 of the files and so on
 # commit and review
 # repeat from 'cd path-to-project' as needed.

 One word of caution. Some of the projects i've done this for -
 keystone and glance - had -e editable lines in their requirements
 files: these got through because infra wasn't linting the -py3 files
 at all until recently, and I'm not yet sure if we can get them back
 in. So we may need to actually fixup those dependencies asap. E.g. get
 /a/ release of glance-store out with its partial python3 support, to
 permit the glance python34 gate to work at all.

Second word of caution. tox.ini probably needs editing too.

-Rob



-- 
Robert Collins rbtcoll...@hp.com
Distinguished Technologist
HP Converged Cloud

__
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