View previous topic :: View next topic |
Author |
Message |
guru369 Apprentice
Joined: 02 Jun 2005 Posts: 225
|
Posted: Thu Mar 22, 2007 2:24 pm Post subject: [SOLVED]Unable to update my xeffects ebuild: Git failure |
|
|
Hi.
I am using the following to keep my beryl svn ebuild updated to the latest code:
Code: |
layman -S
emerge -pe beryl | sed -s 's/................/=/' | grep 9999 | awk '{ print $1 }' | xargs emerge
|
For the last 3 days I was unable to update due to the following error:
Code: |
>>> Emerging (1 of 1) x11-wm/beryl-core-9999 to /
* beryl-mesa-0.1.99.2.tar.bz2 RMD160 ;-) ... [ ok ]
* beryl-mesa-0.1.99.2.tar.bz2 SHA1 ;-) ... [ ok ]
* beryl-mesa-0.1.99.2.tar.bz2 SHA256 ;-) ... [ ok ]
* beryl-mesa-0.1.99.2.tar.bz2 size ;-) ... [ ok ]
* checking ebuild checksums ;-) ... [ ok ]
* checking auxfile checksums ;-) ... [ ok ]
* checking miscfile checksums ;-) ... [ ok ]
* checking beryl-mesa-0.1.99.2.tar.bz2 ;-) ... [ ok ]
>>> Unpacking source...
* git update start -->
* repository: git://git.gentoo-xeffects.org/beryl/beryl-core
fatal: unable to connect a socket (Connection refused)
Cannot get the repository state from git://git.beryl-project.org/beryl/beryl-core
!!! ERROR: x11-wm/beryl-core-9999 failed.
Call stack:
ebuild.sh, line 1614: Called dyn_unpack
ebuild.sh, line 751: Called qa_call 'src_unpack'
environment, line 3514: Called src_unpack
beryl-core-9999.ebuild, line 39: Called git_src_unpack
git.eclass, line 286: Called git_fetch
git.eclass, line 207: Called die
!!! git.eclass: can't update from git://git.gentoo-xeffects.org/beryl/beryl-core.
!!! 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/x11-wm/beryl-core-9999/temp/build.log'.
!!! This ebuild is from an overlay: '/usr/portage/local/layman/xeffects'
|
Does anyone know whats wrong?
Is there a better way to update?
Thanks.
Dekel _________________ Gentoo Rulz!!!
Last edited by guru369 on Fri Mar 23, 2007 11:09 pm; edited 1 time in total |
|
Back to top |
|
|
loftwyr l33t
Joined: 29 Dec 2004 Posts: 970 Location: 43°38'23.62"N 79°27'8.60"W
|
Posted: Thu Mar 22, 2007 3:30 pm Post subject: |
|
|
why not just use the layman xeffects overlay? _________________ My emerge --info
Have you run revdep-rebuild lately? It's in gentoolkit and it's worth a shot if things don't work well.
Celebrating 5 years of Gentoo-ing. |
|
Back to top |
|
|
guru369 Apprentice
Joined: 02 Jun 2005 Posts: 225
|
Posted: Thu Mar 22, 2007 4:15 pm Post subject: |
|
|
loftwyr wrote: | why not just use the layman xeffects overlay? |
Sorry for not being clear enough. This is exactly what I use..
Dekel. _________________ Gentoo Rulz!!! |
|
Back to top |
|
|
roderick l33t
Joined: 11 Jul 2005 Posts: 908 Location: St. John's, NL CANADA
|
Posted: Thu Mar 22, 2007 4:35 pm Post subject: |
|
|
Don't worry, you were extremely clear ("layman -S" gave it away for me .. i.e. I assumed you synced for updating beryl).
Anyway, try this:
layman -d xeffects
layman -L
layman -a xeffects
The repo changed from SVN to GIT and maybe you have a stale copy. Removing the overlay, and re-adding using the above should fix it. There was a post on this on the web page: http://forums.gentoo-xeffects.org, so you may have missed it.
Cheers,
Rod. _________________ If God were a pickle, I'd still say "no pickle on my burger".
http://roderick-greening.blogspot.com/ |
|
Back to top |
|
|
nesl247 Veteran
Joined: 15 Jun 2004 Posts: 1614 Location: Florida
|
Posted: Thu Mar 22, 2007 7:58 pm Post subject: |
|
|
Actually, the fix for this is to: rm /usr/portage/distfiles/git-src
The ebuilds originally had a different git URI, and it changed. So that's why it's causing you to have that problem. |
|
Back to top |
|
|
guru369 Apprentice
Joined: 02 Jun 2005 Posts: 225
|
Posted: Fri Mar 23, 2007 11:08 pm Post subject: |
|
|
nesl247 wrote: | Actually, the fix for this is to: rm /usr/portage/distfiles/git-src
The ebuilds originally had a different git URI, and it changed. So that's why it's causing you to have that problem. |
Thanks that solved the problem.
One last Q:
Is there a better way then what I do to update to the latest svn release?
Thanks.
Dekel _________________ Gentoo Rulz!!! |
|
Back to top |
|
|
Koala Kid Guru
Joined: 09 May 2003 Posts: 382
|
Posted: Sat Mar 24, 2007 9:45 am Post subject: |
|
|
guru369 wrote: | nesl247 wrote: | Actually, the fix for this is to: rm /usr/portage/distfiles/git-src
The ebuilds originally had a different git URI, and it changed. So that's why it's causing you to have that problem. |
Thanks that solved the problem.
One last Q:
Is there a better way then what I do to update to the latest svn release?
Thanks.
Dekel |
Follow up this one
https://forums.gentoo.org/viewtopic-p-3868933-highlight-.html#3868933 _________________ "People are the worst, the worst thing about music is that people play it". M. Patton. |
|
Back to top |
|
|
|