1. 01 Aug, 2018 1 commit
  2. 30 Jul, 2018 1 commit
  3. 19 Jul, 2018 1 commit
  4. 18 Jul, 2018 8 commits
  5. 05 Jul, 2018 1 commit
  6. 27 Jun, 2018 1 commit
  7. 12 Jun, 2018 1 commit
    • qingszhao's avatar
      Update python3 versions in tox.ini envlist · 6c546bc9
      qingszhao authored
      This updates the envlist to include modern versions of python. It
      doesn't really mean anything except for you run tox without specifying
      an environment it will now run py35 and py36 instead of py34 (which
      isn't used anywhere anymore)
      Change-Id: I935cf6d104fa5b516332cbb587d327dc587d0c32
  8. 11 Jun, 2018 1 commit
    • qingszhao's avatar
      fix tox python3 overrides · 0ddb7ec6
      qingszhao authored
      We want to default to running all tox environments under python 3, so
      set the basepython value in each environment.
      We do not want to specify a minor version number, because we do not
      want to have to update the file every time we upgrade python.
      We do not want to set the override once in testenv, because that
      breaks the more specific versions used in default environments like
      py35 and py36.
      Change-Id: I70b4fb58c7800158907d80f83018e39d1b785668
  9. 08 Jun, 2018 1 commit
  10. 01 Jun, 2018 1 commit
  11. 31 May, 2018 1 commit
    • Matthew Treinish's avatar
      Revert "Remove win32/nt checks for wrapper script gen" · ee26945c
      Matthew Treinish authored
      This reverts commit 07de8446.
      The output console_scripts generated after this commit landed are no
      longer directly callable from windows machines. Prior to the this
      reverts we wrapped console_script entrypoints in a .exe on windows so
      you could directly execute them, just like on *nix systems. However,
      after the commit we are no longer generating callables on windows.
      Instead PBR generates a txt file, without a suffix, that is not a valid
      executable on windows. It is exactly the same output as on a *nix
      system, but this neglects that scripts with shebangs don't work on
      windows. (For example generated output on windows see [1]) The exe files
      were needed so that we could directly execute the console scripts on
      windows. This commit restores this functionality so that PBR will
      properly generate executable console_scripts on windows machines again.
      Closes-Bug: #1761134
      [1] http://paste.openstack.org/show/722389/
      Change-Id: Ifc13879b7f64650d444e3a14df1a53b2172828e4
  12. 24 May, 2018 1 commit
  13. 09 May, 2018 1 commit
  14. 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
  15. 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
  16. 03 Apr, 2018 1 commit
  17. 29 Mar, 2018 1 commit
  18. 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
  19. 26 Mar, 2018 4 commits
  20. 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
  21. 15 Mar, 2018 1 commit
  22. 31 Jan, 2018 1 commit
  23. 24 Jan, 2018 1 commit
  24. 18 Jan, 2018 1 commit
  25. 17 Jan, 2018 3 commits
  26. 09 Jan, 2018 2 commits