Hi again,

On Sun, Jan 07, 2018 at 08:25:35AM +0100, Andreas Tille wrote:
> I'd volunteer to work on this bug but the repository specified in
> the VCS fields is not up to date.

To explain what I mean:

 $ debcheckout pydicom
 $ head pydicom/debian/changelog
pydicom (0.9.5~rc1-1) experimental; urgency=low

  * New upstream release candidate
  * Boosted policy compliance to 3.9.1 -- no changes are necessary
  * Deprecated debian/patches/up_with_statement_python2.5 -- absorbed upstream
  * Enabled unit-testing in-place

 -- Yaroslav Halchenko <deb...@onerussian.com>  Mon, 13 Sep 2010 22:26:52 -0400

pydicom (0.9.4.1-1) unstable; urgency=low
 $ apt-get source pydicom
 $ head pydicom-0.9.9/debian/changelog
pydicom (0.9.9-2) unstable; urgency=medium

  * Update maintainer email.
  * Bump standards version to 3.9.6; no changes necessary.
  * CME-base automatic modernization of debian/control.
  * Switch to debhelper 9.
  * Build python3 package.
  * Build documentation and ship it in a -doc package.

 -- Michael Hanke <m...@debian.org>  Sat, 05 Sep 2015 07:38:24 +0200


Could you please bring the Git repository in sync to enable me to make
a proper team upload instead of putting the work to inject a NMU into
the repository for something that is so simple that if it would be less
work if you do it yourself.

Thank you

      Andreas.

-- 
http://fam-tille.de

Reply via email to