pycryptopp (0.7.1-4build2) focal; urgency=medium

  * No-change rebuild for libgcc-s1 package name change.

 -- Matthias Klose <doko@ubuntu.com>  Sun, 22 Mar 2020 16:54:58 +0100

pycryptopp (0.7.1-4build1) focal; urgency=medium

  * No-change rebuild to generate dependencies on python2.

 -- Matthias Klose <doko@ubuntu.com>  Tue, 17 Dec 2019 12:40:03 +0000

pycryptopp (0.7.1-4) unstable; urgency=medium

  * Use tracker team address in maintainer field.
    Closes: bug#899660, Thanks to Christoph Biedl.
  * debian/control:
    + Mark package as compliant with Debian Policy 4.1.3
    + Use salsa url in Vcs-* fields.
  * debian/patches/no-version-in-setup.patch:
    + Fix typo in DEP-3 header.

 -- Vasudev Kamath <vasudev@copyninja.info>  Sat, 02 Jun 2018 16:28:37 +0530

pycryptopp (0.7.1-3) unstable; urgency=medium

  * debian/control:
    + Take over maintenance of package.
      Closes: bug#859182. Thanks to Ramakrishnan for his contributions.
    + Mark package as compliant to Debian Policy 4.0.0.
    + Fix Vcs-* URLs to point to secure versions.
    + Update homepage field to Tahoe-LAFS project trac.
    + Make package team maintained and mark myself as uploader.
    + Build-Depend on python-all-dev and python-pkg-resources.
    + Drop python-pycryptopp-dbg in favor of automatic -dbgsym package.
  * Convert debian/rules to use pybuild.
  * debian/watch:
    + Covnert watch file format to version 4.
    + Use Github URL for tracking new version instead of PyPI.
  * Bump compat level to 9.
  * debian/copyright file is converted to DEP-5 format.
  * Add copyright-check script and generate copyright-hints file.
  * Add lintian-overrides for source with proper documentation.
  * Add DEP-3 headers to patches.

 -- Vasudev Kamath <vasudev@copyninja.info>  Sun, 23 Jul 2017 19:29:28 +0530

pycryptopp (0.7.1-2) unstable; urgency=medium

  * Orphaning the package by setting the maintainer to debian-qa.

 -- Ramakrishnan Muthukrishnan <rkrishnan@debian.org>  Fri, 31 Mar 2017 14:28:02 +0530

pycryptopp (0.7.1-1) unstable; urgency=medium

  [Ramakrishnan Muthukrishnan]
  * New upstream release.
  * New maintainer (Ramakrishnan Muthukrishnan)
  * debian/patches/*: regenerate patches. (Closes: #659206)
  * debian/rules: add build-arch and build-indep.

 -- Ramakrishnan Muthukrishnan <rkrishnan@debian.org>  Sat, 12 Nov 2016 21:03:32 +0530

pycryptopp (0.6.0.20120313-1) unstable; urgency=low

  * Update debian/watch
  * Refresh patches
  * Import new upstream version
  * Fix installation of README, renamed to README.rst

 -- Micah Anderson <micah@debian.org>  Thu, 22 Aug 2013 16:31:55 -0400

pycryptopp (0.5.29-1) unstable; urgency=low

  [ Micah Anderson ]
  * Add myself to Uploaders
  * Set compat to 7 and adjust Build-Dep

  [ Bert Agaz ]
  * Bump debhelper compatibility.
  * Update Vcs-* in debian/control.
  * Bump Standards-Version number.
  * Fix typo in debian/copyright.

  [ Piotr Ożarowski ]
  * New upstream release
  * Use dh_pyton2 instead of dh_pysupport
    - minimum required python-all build version bymped to 2.6.6-3
  * Convert source package format to 3.0 (quilt)
  * Bumped Standards-Version to 3.9.1 (no other changes needed)

 -- Bert Agaz <bertagaz@ptitcanardnoir.org>  Tue, 14 Jun 2011 23:12:11 +0200

pycryptopp (0.5.17-1) unstable; urgency=low

  [ Piotr Ożarowski ]
  * New upstream release

 -- Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>  Wed, 30 Sep 2009 22:40:25 +0200

pycryptopp (0.5.15-2) unstable; urgency=low

  [ Piotr Ożarowski ]
  * Prepare for Python 2.6:
    - add $(py_setup_install_args) to the install args (LP: #427025)

 -- Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>  Thu, 10 Sep 2009 20:18:04 +0200

pycryptopp (0.5.15-1) unstable; urgency=low

  [ Piotr Ożarowski ]
  * New upstream release
  * Bumped Standards-Version to 3.8.3
    - add debian/README.source

 -- Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>  Thu, 27 Aug 2009 00:13:48 +0200

pycryptopp (0.5.14-1) unstable; urgency=low

  * Initial release (Closes: #503977).

 -- Zooko O'Whielacronx <zooko@zooko.com>  Mon, 22 Jun 2009 22:20:50 +0200
