Package: src:django-compat
Version: 1.0.13-1
Severity: important
Tags: patch

This package build-depends on python3 dev packages even though it has no
arch:any Python3 content.  This is not needed and complicates transition
trackinig for us, the python maintainers, (which is why I'm filing this as
important) [1].  As you can see, the package shows up as affected by the
transition when, in fact, it isn't.

Please see the attached patch.  I have written the debian/changelog in the NMU
form, but have no immediate intent to NMU.  Patch not build-tested due to
bug #865661, but it should work fine.  It would be appreciated if you could
address this when you address #865661.

Scott K


[1] https://release.debian.org/transitions/html/python3.6.html
diff -Nru django-compat-1.0.13/debian/changelog django-compat-1.0.13/debian/changelog
--- django-compat-1.0.13/debian/changelog	2016-08-08 22:57:21.000000000 -0400
+++ django-compat-1.0.13/debian/changelog	2017-06-29 12:37:34.000000000 -0400
@@ -1,3 +1,10 @@
+django-compat (1.0.13-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update build-depends to align to those needed for arch:all packages
+
+ -- Scott Kitterman <[email protected]>  Thu, 29 Jun 2017 12:37:07 -0400
+
 django-compat (1.0.13-1) unstable; urgency=medium
 
   * New upstream production release.
diff -Nru django-compat-1.0.13/debian/control django-compat-1.0.13/debian/control
--- django-compat-1.0.13/debian/control	2016-08-08 22:57:21.000000000 -0400
+++ django-compat-1.0.13/debian/control	2017-06-29 12:38:59.000000000 -0400
@@ -5,9 +5,9 @@
 Section: python
 Priority: optional
 Build-Depends: debhelper (>= 9), dh-python,
- python | python-all (>= 2.6.6-3) | python-dev | python-all-dev,
+ python-all (>= 2.6.6-3),
  python-setuptools (>= 0.6b3), python-django, python-six, python-django-nose,
- python3 | python3-all | python3-dev | python3-all-dev, python3-setuptools,
+ python3-all, python3-setuptools,
  python3-django, python3-six, python3-django-nose
 X-Python-Version: >=2.7
 Testsuite: autopkgtest

Reply via email to