Your message dated Wed, 4 Apr 2018 13:11:13 +0530
with message-id <>
and subject line Re: plinth: FTBFS with Django 2.x
has caused the Debian Bug report #880835,
regarding plinth: FTBFS with Django 2.x
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Source: plinth
Version: 0.15.3+ds-1
Severity: normal
Usertags: ftbfs-django-2.x

Dear Maintainer,

plinth fails to build from source when using Django 2.x from


    File "/usr/lib/python3/dist-packages/django/core/management/", line 
351, in _run_checks
      return checks.run_checks(**kwargs)
    File "/usr/lib/python3/dist-packages/django/core/checks/", line 
73, in run_checks
      new_errors = check(app_configs=app_configs)
    File "/usr/lib/python3/dist-packages/django/core/checks/", line 13, 
in check_url_config
      return check_resolver(resolver)
    File "/usr/lib/python3/dist-packages/django/core/checks/", line 23, 
in check_resolver
      return check_method()
    File "/usr/lib/python3/dist-packages/django/urls/", line 388, 
in check
      for pattern in self.url_patterns:
    File "/usr/lib/python3/dist-packages/django/utils/", line 36, 
in __get__
      res = instance.__dict__[] = self.func(instance)
    File "/usr/lib/python3/dist-packages/django/urls/", line 527, 
in url_patterns
      patterns = getattr(self.urlconf_module, "urlpatterns", 
    File "/usr/lib/python3/dist-packages/django/utils/", line 36, 
in __get__
      res = instance.__dict__[] = self.func(instance)
    File "/usr/lib/python3/dist-packages/django/urls/", line 520, 
in urlconf_module
      return import_module(self.urlconf_name)
    File "/usr/lib/python3.6/importlib/", line 126, in import_module
      return _bootstrap._gcd_import(name[level:], package, level)
    File "<frozen importlib._bootstrap>", line 994, in _gcd_import
    File "<frozen importlib._bootstrap>", line 971, in _find_and_load
    File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
    File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
    File "<frozen importlib._bootstrap_external>", line 678, in exec_module
    File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
    File "«BUILDDIR»/plinth/", line 20, in <module>
      from captcha import views as cviews
    File "/usr/lib/python3/dist-packages/captcha/", line 2, in <module>
      from captcha.helpers import captcha_image_url
    File "/usr/lib/python3/dist-packages/captcha/", line 4, in 
      from django.core.urlresolvers import reverse
  ModuleNotFoundError: No module named 'django.core.urlresolvers'
  E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: 
python3.6 test 
  dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13
  debian/rules:7: recipe for target 'build' failed
  make: *** [build] Error 25
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


The full build log is attached.


     : :'  :     Chris Lamb
     `. `'` /

Attachment: plinth.0.15.3+ds-1.experimental.amd64.log.txt.gz
Description: Binary data

--- End Message ---
--- Begin Message ---
On Tue, 13 Mar 2018 13:36:52 +0530 Sunil Mohan Adapa
<> wrote:
> With the release of Plinth 0.25, Plinth itself is ready for Django 2.x.
> Waiting on django-captcha and python3-bootstrapform (almost ready) to
> fix this.

django-captcha has been updated to latest release with Django 2.0
support. With this last one, all the dependencies of Plinth and Plinth
itself are now Django 2.0 ready.  I have done the following tests.

- Run test suite with Django 2.0 (originally failure is what caused this

- Run Plinth interface with Django 2.0 and access it.

- Build Plinth Debian package with Django 2.0 (although not using pbuilder).

I believe the bug is now fixed.


Attachment: signature.asc
Description: OpenPGP digital signature

--- End Message ---

Reply via email to