python-django-push-notifications
Send push notifications through GCM or APNS in Django (Python3 version)

NEW: Take a look at the new package tracker: tracker.debian.org/pkg/python-django-push-notifications

general

source
python-django-push-notifications (optional, misc)
version
1.6.0-3
maint
Debian Python Team, Michael Fladischer (u)
std-ver
4.1.3
VCS
Git (browse)

versions ... ...pool

stable
save 1.6.0-2
testing
save 1.6.0-2
unstable
save 1.6.0-3
Ubuntu
1.6.0-2

binaries

todo

  • The package should be updated to follow the last version of Debian Policy (Standards-Version 4.6.2 instead of 4.1.3).

problems

  • The package has not yet entered testing even though the 5-day delay is over. Check why.
  • The package has a debian/watch file, but the last attempt to use it for checking for newer upstream versions failed with an error:
    In debian/watch no matching files for watch line   https://github.com/jleclanche/django-push-notifications/releases (?:.*/)?(\d\S+)\.(?:tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz)))

autoremoval from testing

  • Version 1.6.0-2 of python-django-push-notifications is marked for autoremoval from testing on 2024-04-26.
  • It depends (transitively) on and djangorestframework, affected by RC bug(s) and 1066740
  • You should try to prevent the removal from testing by fixing these bugs.

testing migration

excuses:
  • Migration status for python-django-push-notifications (- to 1.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating python-django-push-notifications introduces new bugs: #917677.
  • Not built on buildd: arch all binaries uploaded by fladi, a new source-only upload is needed to allow migration
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-push-notifications.html
  • 1748 days old (needed 5 days)

bugs

all bug history graph
0
RC
0
I&N
0
M&W
0
F&P
0