View previous topic :: View next topic |
Author |
Message |
mikjo n00b
Joined: 17 Feb 2013 Posts: 3
|
Posted: Sun Feb 17, 2013 7:06 pm Post subject: Failed to emerge dev-python/django-9999 |
|
|
I am trying to add Django to Gentoo running on my Raspberry Pi using:
emerge --ask django
I get the below message:
* Messages for package dev-python/django-9999:
* ERROR: dev-python/django-9999 failed (unpack phase):
* subversion: can't fetch to /usr/portage/distfiles/svn-src/django/trunk from http://code.djangoproject.com/svn/django/trunk.
*
* Call stack:
* ebuild.sh, line 93: Called src_unpack
* environment, line 3412: Called subversion_src_unpack
* environment, line 3695: Called subversion_fetch
* environment, line 3590: Called die
* The specific snippet of code:
* ${ESVN_FETCH_CMD} ${options} "${repo_uri}" || die "${ESVN}: can't fetch to ${wc_path} from ${repo_uri}.";
*
* If you need support, post the output of `emerge --info '=dev-python/django-9999'`,
* the complete build log and the output of `emerge -pqv '=dev-python/django-9999'`.
* The complete build log is located at '/var/tmp/portage/dev-python/django-9999/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-python/django-9999/temp/environment'.
* Working directory: '/usr/portage/distfiles/svn-src/django'
* S: '/var/tmp/portage/dev-python/django-9999/work/Django-9999'
I am able to emerge other "things"
Appreciate help
Thanks!
Mike |
|
Back to top |
|
|
MustrumR n00b
Joined: 15 Nov 2011 Posts: 71 Location: Right here
|
Posted: Mon Feb 18, 2013 8:01 am Post subject: |
|
|
They are now using git. The fetch/unpack part of the ebuild needs to be rewritten to use git-2.eclass instead of subversion.eclass |
|
Back to top |
|
|
mikjo n00b
Joined: 17 Feb 2013 Posts: 3
|
Posted: Mon Feb 18, 2013 9:02 am Post subject: |
|
|
[quote="MustrumR"]They are now using git. The fetch/unpack part of the ebuild needs to be rewritten to use git-2.eclass instead of subversion.eclass[/quote]
That explains, Thanks!
Should I report this in Bugzilla?
/Mike |
|
Back to top |
|
|
smartass Apprentice
Joined: 04 Jul 2011 Posts: 189 Location: right behind you ... (you did turn around, didn't you?)
|
Posted: Mon Feb 18, 2013 11:18 am Post subject: |
|
|
Definitely report it, that's what teh bugzilla is here
You could also submit a patch to the bug (don't forget to add the PATCH keyword) for the new ebuild using git which will speed up the bugzilla process.. There are tons of ebuilds using the git eclass, so you should be able to make a patch |
|
Back to top |
|
|
mikjo n00b
Joined: 17 Feb 2013 Posts: 3
|
Posted: Mon Feb 18, 2013 10:20 pm Post subject: |
|
|
[quote="smartass"]Definitely report it, that's what teh bugzilla is here
You could also submit a patch to the bug (don't forget to add the PATCH keyword) for the new ebuild using git which will speed up the bugzilla process.. There are tons of ebuilds using the git eclass, so you should be able to make a patch[/quote]
This was bug 457976 which is fixed.
#emerge --sync
#emerge portage
#emerge django
and I am back on track.
Thanks! |
|
Back to top |
|
|
|