vcswatch reports that
this package seems to have new commits in its VCS but has
not yet updated debian/changelog. You should consider updating
the Debian changelog and uploading this new version into the archive.
Here are the relevant commit logs:
commit 08e7fed6a5170c9b693f2e72d4abfdf7a7de9560
Author: Stephan Sürken <absurd@debian.org>
Date: Thu Apr 25 12:54:42 2024 +0200
views.py (ExceptionMiddleware.error): Use level DEBUG (not WARNING) for (django) HTTP errors (Fixes: Potential log spam when webapp is spammed)
* With the update to logging in 2.2, we will catch django's logging -- so we will already get a warning log (for 404 and such) anyway
* You can always check access.log for other HTTP responses (that do not trigger a django log)
* Django's exception string is quite long (listing all unsuccessful paths) -- we don't want that in a production log
commit 15b5c8bdef0934252c665cdf61a6cae4cfd1c1c3
Author: Stephan Sürken <absurd@debian.org>
Date: Thu Apr 25 12:37:23 2024 +0200
views.py (ExceptionMiddleware.error): Don't use django's message system for HTTP errors (Fixes: Duplicate messages on error pages)
I don't see what other good this may bring, apart from confusion ;).
commit d1888dac5c920d4f5f9f56accf1d96fdb9b4ffd5
Author: Stephan Sürken <absurd@debian.org>
Date: Thu Apr 25 12:26:50 2024 +0200
util.py (log_exception): Don't use fstring for logging
The bare 'log()' call was not catched by pylint
commit 18aa8cd6979c8f12e13e5e42d21427e8b6e549de
Author: Stephan Sürken <absurd@debian.org>
Date: Mon Apr 22 14:45:45 2024 +0200
setup.py: Use pep440-style version for setuptools only (Fixes: Incomplete version displayed if version has '~')