1. 01 Jun, 2018 1 commit
  2. 09 May, 2018 1 commit
  3. 30 Apr, 2018 1 commit
    • Ian Wienand's avatar
      Don't poke in pip for requests · 0da792af
      Ian Wienand authored
      Pip10 has removed the ability to poke inside it for things like
      requests.  Explicitly add it to the venv.
      Change-Id: Ie12168091dc4c737f3913720c1743bea666b5d9c
  4. 24 Apr, 2018 1 commit
    • Ian Wienand's avatar
      Fix builddoc with sphinx <= 1.6 · a562b124
      Ian Wienand authored
      I went to build infra-specs which specifies sphinx==1.5.6 and hit
       Traceback (most recent call last):
         File "setup.py", line 29, in <module>
        File ".../pbr/builddoc.py", line 235, in run
        File ".../pbr/builddoc.py", line 162, in _sphinx_run
          freshenv=self.fresh_env, warningiserror=self.warning_is_error)
        File ".../sphinx/application.py", line 244, in __init__
        File "...//sphinx/application.py", line 311, in _init_builder
          raise SphinxError('Builder name %s not registered' % buildername)
       sphinx.errors.SphinxError: Builder name h not registered
      It appears to be a typo introduced with
      I18bbf693bca2f6e49d822ae2940d2170a2b90ce9; make sure we're walking the
      self.builders list; not the string self.builder.
      Change-Id: Ic038029c361b3ede48f2b495c74430d3ad1eab82
  5. 03 Apr, 2018 1 commit
  6. 29 Mar, 2018 1 commit
  7. 27 Mar, 2018 1 commit
    • Ben Nemec's avatar
      Explicitly read setup.cfg as utf-8 on Python 3 · 10fce39a
      Ben Nemec authored
      Per the referenced bug, relying on the terminal encoding to read
      setup.cfg is not safe.  Unfortunately, Python 2 doesn't accept an
      encoding when reading config files so we need a fallback path for
      that version.
      Change-Id: If49344db2f9139c0557f6acd17671163e02468a5
      Closes-Bug: 1745396
  8. 26 Mar, 2018 4 commits
  9. 20 Mar, 2018 2 commits
    • Clark Boylan's avatar
      Better Sem-Ver header handling · 183b445c
      Clark Boylan authored
      This makes Sem-Ver header handling more reliable by ignoring any
      potential user configured git log output format. Instead PBR supplies
      its own format string that will output the commit message bodies in
      their entirety without wrapping and other whitespace formatting done for
      Change-Id: I957a8c182585119534b4e02c34e7140a3e07d1d6
      Related-Bug: 1738685
      Fixes-Bug: 1704625
    • Clark Boylan's avatar
      Make docs on env vars a little clearer · 7e2d1666
      Clark Boylan authored
      It was pointed out that the packager docs don't make it super obvious
      that the env var settings that packagers can set are env vars. Add
      export statements to the docs to imply it a bit more that we are talking
      about env vars here.
      Change-Id: I9e9eefa661994237a63b59dcefab11961ef339e1
      Fixes-bug: 1724425
  10. 15 Mar, 2018 1 commit
  11. 31 Jan, 2018 1 commit
  12. 24 Jan, 2018 1 commit
  13. 18 Jan, 2018 1 commit
  14. 17 Jan, 2018 3 commits
  15. 09 Jan, 2018 3 commits
  16. 08 Jan, 2018 3 commits
  17. 05 Jan, 2018 1 commit
  18. 04 Jan, 2018 1 commit
  19. 03 Jan, 2018 1 commit
    • Stephen Finucane's avatar
      Deprecate testr and nose integration · 113685e1
      Stephen Finucane authored
      These are not recommended for use in OpenStack anymore and both nose and
      testr offer native setuptools commands that can be manually aliased to
      'test' on a per-project basis if necessary. Deprecate with an eye to
      removal in the future.
      Change-Id: I753f2ffe8b223b180b8ed813d879b3a28b47a1ab
      Signed-off-by: 's avatarStephen Finucane <sfinucan@redhat.com>
  20. 15 Dec, 2017 1 commit
  21. 11 Dec, 2017 1 commit
  22. 06 Dec, 2017 3 commits
    • Stephen Finucane's avatar
      tests: Increase coverage of requirements parsing · 6c8455c8
      Stephen Finucane authored
      This is mostly an exercise in refactoring, moving tests into a single
      test case. An additional test is added, however, verifying that default
      requirement files are indeed used if nothing else is provided.
      Change-Id: I8dc6cc8c50f1280f24731480501fab61fc401809
    • Stephen Finucane's avatar
      trivial: Move packaging tests to test_packaging · ec210af0
      Stephen Finucane authored
      There's a little bit of duplication going on here. Resolve this by
      moving tests that predominantly focus on FILE to tests/test_FILE.
      Change-Id: I29355155853e543d017db00c936bcdc88c1c97ad
    • Monty Taylor's avatar
      Put test-requirements into an extra named 'test' · 225e8823
      Monty Taylor authored
      In bindep files we use a 'test' environment to indicate dependencies
      that are needed for testing. Make the same thing available for our
      python dependencies, allowing things like "pip install .[test]" or "pip
      install shade[test]" to work.
      Change-Id: If3ad8b6a79a8cab2f7434b73207f35384e8516ba
  23. 05 Dec, 2017 1 commit
  24. 04 Dec, 2017 1 commit
    • Jeremy Stanley's avatar
      Support Description-Content-Type metadata · 538d2c21
      Jeremy Stanley authored
      As of setuptools 36.4.0, support for Description-Content-Type
      metadata was added via the long_description_content_type variable.
      Add a metadata.description-content-type option for setup.cfg so it
      can be provided through PBR. This makes it possible to instruct PyPI
      and potentially other frontends to know an explicit RFC 1341 content
      type, along with character set and variant, for the accompanying
      long description.
      Change-Id: I852f603d9ca4e4cd469eab4cae9933ef2581e3af
  25. 02 Dec, 2017 1 commit
  26. 01 Dec, 2017 1 commit
  27. 22 Nov, 2017 1 commit
  28. 20 Nov, 2017 1 commit