Ubuntu
python-pbr package

python-pbr 3.1.1-2ubuntu1 source package in Ubuntu

Changelog

python-pbr (3.1.1-2ubuntu1) bionic; urgency=medium

  * Merge from Debian unstable, remaining changes:
    - Drop build-dependencies on python3-all-dev and python-all-dev,
      This package doesn't build anything that involves a binary
      extension.
  * Dropped changes, no longer required:
    - Relax build-dependency on subunit, which has been raised in the
      packaging for some reason but not raised upstream.
    - Fix autopkgtests to not try to test against non-default pythons.
    - Drop dependencies on pip and virtualenv as these are not in Ubuntu
      main.

python-pbr (3.1.1-2) unstable; urgency=medium

  [ Daniel Baumann ]
  * Updating standards version to 4.1.0.

  [ Thomas Goirand ]
  * Uploading to unstable.
  * Fixed Standards-Version to 4.1.1.
  * Remove not-needed version in (build-)depends.
  * Watch file uses HTTPS.
  * debian/rules: Remove things defined in openstack-pkg-tools.
  * Using pkgos-dh_auto_install.

python-pbr (3.1.1-1) experimental; urgency=medium

  * Team upload.

  [ Daniel Baumann]
  * Updating vcs fields.
  * Updating copyright format url.
  * Updating maintainer field.
  * Running wrap-and-sort -bast.
  * Removing gbp.conf, not used anymore or should be specified in the
    developers dotfiles.
  * Correcting permissions in debian packaging files.
  * Updating standards version to 4.0.1.

  [ Thomas Goirand ]
  * New upstream release (Closes: #868615, #868976).
  * Fixed (build-)depends.
  * Removed patch folder.
  * Removed setting-up of http_proxy in debian/rules, as this breaks tests.
    TODO: check it doesn't requires network to build now.
  * Remove doc/source/static/nature.css from debian/copyright as it is also
    removed upstream.
  * Removed XS-Testsuite field from debian/control.
  * Standards-Version is now 4.0.0 (no change).

  [ Ondřej Nový ]
  * Fixed homepage (https).
  * Fixed VCS URLs (https).
  * d/rules: Changed UPSTREAM_GIT protocol to https
  * d/copyright: Changed source URL to https protocol
  * Add d/p/disable_tests.patch

 -- James Page <email address hidden>  Mon, 30 Oct 2017 11:35:57 +0000

Upload details

Uploaded by:
James Page
Uploaded to:
Bionic
Original maintainer:
Ubuntu Developers
Architectures:
all
Section:
python
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Builds

Bionic: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
python-pbr_3.1.1.orig.tar.xz 70.7 KiB ed8126ebd7a9eef94bf002c93d98b6d67471f9875c81d924d26a89fcab70f301
python-pbr_3.1.1-2ubuntu1.debian.tar.xz 8.4 KiB ddea60337387a3f53eefe05bf99256a38e82172f90caff8e68ec15b0afb492b0
python-pbr_3.1.1-2ubuntu1.dsc 2.8 KiB ec6850683737dd04450adf95105eff8ccdd602aa5bd8f7d3aa253b712a68f1da

Available diffs

View changes file

Binary packages built by this source

python-pbr: inject useful and sensible default behaviors into setuptools - Python 2.x

 PBR (Python Build Reasonableness) is a library that injects some useful and
 sensible default behaviors into your setuptools run. PBR can:
  * Manage version number based on git revisions and tags (Version file).
  * Generate AUTHORS file from git log
  * Generate ChangeLog from git log
  * Generate Sphinx autodoc stub files for your whole module
  * Store your dependencies in a pip requirements file
  * Use your README file as a long_description
  * Smartly find packages under your root package
 .
 PBR is only mildly configurable. The basic idea is that there's a decent way
 to run things and if you do, you should reap the rewards, because then it's
 simple and repeatable. If you want to do things differently, cool! But you've
 already got the power of Python at your fingertips, so you don't really need
 PBR.
 .
 PBR builds on top of the work that d2to1 started to provide for declarative
 configuration. d2to1 is itself an implementation of the ideas behind
 distutils2. Although distutils2 is now abandoned in favor of work towards PEP
 426 and Metadata 2.0, declarative config is still a great idea and
 specifically important in trying to distribute setup code as a library when
 that library itself will alter how the setup is processed. As Metadata 2.0 and
 other modern Python packaging PEPs come out, PBR aims to support them as
 quickly as possible.
 .
 This package provides support for Python 2.x.

python-pbr-doc: inject useful and sensible default behaviors into setuptools - doc

 PBR (Python Build Reasonableness) is a library that injects some useful and
 sensible default behaviors into your setuptools run. PBR can:
  * Manage version number based on git revisions and tags (Version file).
  * Generate AUTHORS file from git log
  * Generate ChangeLog from git log
  * Generate Sphinx autodoc stub files for your whole module
  * Store your dependencies in a pip requirements file
  * Use your README file as a long_description
  * Smartly find packages under your root package
 .
 PBR is only mildly configurable. The basic idea is that there's a decent way
 to run things and if you do, you should reap the rewards, because then it's
 simple and repeatable. If you want to do things differently, cool! But you've
 already got the power of Python at your fingertips, so you don't really need
 PBR.
 .
 PBR builds on top of the work that d2to1 started to provide for declarative
 configuration. d2to1 is itself an implementation of the ideas behind
 distutils2. Although distutils2 is now abandoned in favor of work towards PEP
 426 and Metadata 2.0, declarative config is still a great idea and
 specifically important in trying to distribute setup code as a library when
 that library itself will alter how the setup is processed. As Metadata 2.0 and
 other modern Python packaging PEPs come out, PBR aims to support them as
 quickly as possible.
 .
 This package provides the documentation.

python3-pbr: inject useful and sensible default behaviors into setuptools - Python 3.x

 PBR (Python Build Reasonableness) is a library that injects some useful and
 sensible default behaviors into your setuptools run. PBR can:
  * Manage version number based on git revisions and tags (Version file).
  * Generate AUTHORS file from git log
  * Generate ChangeLog from git log
  * Generate Sphinx autodoc stub files for your whole module
  * Store your dependencies in a pip requirements file
  * Use your README file as a long_description
  * Smartly find packages under your root package
 .
 PBR is only mildly configurable. The basic idea is that there's a decent way
 to run things and if you do, you should reap the rewards, because then it's
 simple and repeatable. If you want to do things differently, cool! But you've
 already got the power of Python at your fingertips, so you don't really need
 PBR.
 .
 PBR builds on top of the work that d2to1 started to provide for declarative
 configuration. d2to1 is itself an implementation of the ideas behind
 distutils2. Although distutils2 is now abandoned in favor of work towards PEP
 426 and Metadata 2.0, declarative config is still a great idea and
 specifically important in trying to distribute setup code as a library when
 that library itself will alter how the setup is processed. As Metadata 2.0 and
 other modern Python packaging PEPs come out, PBR aims to support them as
 quickly as possible.
 .
 This package provides support for Python 3.x.