Bug#770779: unblock: python-django-guardian/1.2.4-2
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
python-django-guardian was RC bug #763222. I believe this is a just a
technical bug in the tests, the actual package should work fine.
However, it means the package won't build.
This in turn has introduced an RC bug in djangorestframework #769216,
and other packages that depend on djangorestframework are scheduled for
removal from testing.
What would be considered an acceptable fix?
I could recommend:
* Just disabling the tests.
Pros: easy patch.
Con: potentially risky.
* Continue hacking on the tests until they work.
I imagine this will mean:
mv guardian/testapp/migrations guardian/testapp/south_migrations
build new migrations in guardian/testapp
Pros: We fix the problem and keep the tests.
Cons: 1. While the process of generating the patch is going to be simple,
the actual patch itself is going to be extensive, because of the
requirement to move the exiting migration directory. 2. We start
diverging more and more from upstream code.
* Use the upstream git code.
While there are some bugs that we would have to patch, the total patch
set would be a lot simpler this way. e.g. the following bugs are open
upstream:
https://github.com/lukaszb/django-guardian/issues/284
https://github.com/lukaszb/django-guardian/issues/254
Pros: I believe many problems we have hacked/patched in the Debian
version are already fixed upstream, and if we stop diverging so much
from upstream, it will make future updates (including security
updates) much easier.
Cons: We diverge from the current Debian version.
I don't have a solution just yet, however just trying to solicit
feedback if any of the above solutions would be considered acceptable
for the release team.
My favoured solution is the last one, because it is going to result in
the simplest package, with minimal differences from upstream.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16-0.bpo.2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE= (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Reply to: