Bug 240312 – Please re-keyword dev-python/django

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Rob Cakebread (RETIRED) 2008-10-06 18:43:28 UTC]

Please re-keyword dev-python/django 1.0 and 9999 ~ppc64 after dev-python/sphinx is keyworded.

[Comment 1 Brent Baude (RETIRED) 2008-12-02 23:21:00 UTC]

Any ideas on this one?

copying and adjusting django/bin/django-admin.py -> build/scripts-2.5
changing mode of build/scripts-2.5/django-admin.py from 644 to 755
>>> Source compiled.
>>> Creating Manifest for /usr/portage/dev-python/django
  digest.assumed                 2
   django-0.96.2::Django-0.96.1.tar.gz
   django-0.96.2::Django-0.96.2.tar.gz
Traceback (most recent call last):
  File "tests/runtests.py", line 183, in <module>
    django_tests(int(options.verbosity), options.interactive, args)
  File "tests/runtests.py", line 117, in django_tests
    from django.db.models.loading import get_apps, load_app
  File "/var/tmp/portage/dev-python/django-1.0/work/Django-1.0/django/db/__init__.py", line 16, in <module>
    backend = __import__('%s%s.base' % (_import_path, settings.DATABASE_ENGINE), {}, {}, [''])
  File "/var/tmp/portage/dev-python/django-1.0/work/Django-1.0/django/db/backends/sqlite3/base.py", line 26, in <module>
    raise ImproperlyConfigured, "Error loading %s module: %s" % (module, e)
django.core.exceptions.ImproperlyConfigured: Error loading sqlite3 module: No module named pysqlite2
 * 
 * ERROR: dev-python/django-1.0 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_test
 *             environment, line 2716:  Called die
 * The specific snippet of code:
 *       PYTHONPATH="." ${python} tests/runtests.py --settings=settings -v1 || die "tests failed"
 *  The die message:
 *   tests failed
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/dev-python/django-1.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-python/django-1.0/temp/environment'.
 * 

[Comment 2 Patrick Lauer 2009-03-21 17:08:46 UTC]

That failure looks like python built without sqlite support. I'll try to reproduce and fix the dependencies ...

[Comment 3 Patrick Lauer 2009-03-22 09:06:33 UTC]

Right, this is triggered by python[-sqlite]

the deps in the ebuild are like this:
        sqlite3? ( || (
                ( dev-python/pysqlite:2 <dev-lang/python-2.5 )
                >=dev-lang/python-2.5 ) )
I'd want to use EAPI2, but I'd guess that this kinda kills the stabilization process.
>=dev-lang/python-2.5[sqlite] would be the changed dep.

Opinions?

[Comment 4 Nirbheek Chauhan (RETIRED) 2009-03-22 09:17:16 UTC]

(In reply to comment #3)
> Right, this is triggered by python[-sqlite]
> 
> the deps in the ebuild are like this:
>         sqlite3? ( || (
>                 ( dev-python/pysqlite:2 <dev-lang/python-2.5 )
>                 >=dev-lang/python-2.5 ) )
> I'd want to use EAPI2, but I'd guess that this kinda kills the stabilization
> process.
> >=dev-lang/python-2.5[sqlite] would be the changed dep.
> 
> Opinions?
> 

I don't get it, how will this kill the stabilization process?

1. We have a stable portage with EAPI=2 support
2. Changes to ebuild syntax don't affect the stabilization process

[Comment 5 Brent Baude (RETIRED) 2009-04-15 17:29:56 UTC]

~ppc64 done

[Comment 6 Arfrever Frehtes Taifersar Arahesis (RETIRED) 2010-01-02 23:43:07 UTC]

(In reply to comment #5)
> ~ppc64 done

Please close bugs, when you are the last architecture.