#32293: import _scproxy and spatialite database backend segfaults
-------------------------------+--------------------------------------
Reporter: Jon Janzen | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 3.1
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => invalid
Comment:
Hi Jon. Sorry to say, this isn’t really an issue with Django that we can
address here.
It’s not clear exactly what the issue could is, but I’d suggest that
you’ll need to review each installed component checking for that you have
the latest versions and such. I’m afraid that’s probably a bit of a
detective hunt. I’d guess a post to the spatialite forums might be your
best way forwards...
Sorry that doesn’t get you moving.
--
Ticket URL: <https://code.djangoproject.com/ticket/32293#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.11a0826228ac111a431bbcc81bb23097%40djangoproject.com.
