If this is the case, then autopkgtest is useless to me, not just for django-restricted-resource but for all django packages.
0: the test_project is not packaged by upstream (and doesn't need to be packaged in a binary .deb imho - it's in the source package where it is useful.) There is no use-case for a -dev binary package. 1: the unit tests cannot run without a test database which is setup by the test project 2: stderr is already handled the the python unittest support. 3: the module cannot be imported without a working django environment. "django.core.exceptions.ImproperlyConfigured: Requested setting CACHES, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings." autopkgtest appears to be too restrictive to be useful. Unless there is a way to address these bugs in autopkgtest, my only choice to fix this bug is to remove autopkgtest support from this and all of the other django packages for which I was considering autopkgtest support. The unit tests are not suitable for execution during the build (require a working database which doesn't happen by default in a build chroot) and now appear to be unsupportable in autopkgtest too. I expected autopkgtest to be able to support these operations, there's no other way to do this in Debian currently. How can a working django environment be enabled with autopkgtest? I don't find the current documentation at all useful for this situation I'm afraid. Why can't autopkgtest be used to test *against* installed dependencies rather than exclusively for testing this installed package in isolation? It's the same source package - and being python, there is no need to test the installed file vs the source file beyond a checksum / path. Is autopkgtest actually only useful for vanity native packages which are developed exclusively within Debian? Why can't autopkgtest accept a pass/fail result instead of assuming that all stderr output is an automatic FAIL? It's not at all clear what benefit there would be in an autopkgtest which doesn't run the upstream unit tests - or what benefit there is in the current implementation of autopkgtest support, not just for this package but most of my other packages. -- Neil Williams ============= http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
