View previous topic :: View next topic |
Author |
Message |
mutex Tux's lil' helper
Joined: 04 Sep 2003 Posts: 146
|
Posted: Fri Sep 05, 2003 2:09 pm Post subject: sash-3.4.tar.gz could not be downloaded (stage2) |
|
|
After running emerge system, emerge tries to download sash-3.4.tar.gz from http://www.canb.auug.org.au/~dbell/programs/sash-3.4.tar.gz but then emerge reports a 404 Not Found error.
Should I manually edit the .emerge file to point to a different mirror?
Should I download the file manually and place it into /usr/portage/distfiles? |
|
Back to top |
|
|
Earthwings Bodhisattva
Joined: 14 Apr 2003 Posts: 7753 Location: Germany
|
Posted: Fri Sep 05, 2003 2:28 pm Post subject: |
|
|
Quote: |
Should I download the file manually and place it into /usr/portage/distfiles?
|
this one is a good idea. |
|
Back to top |
|
|
mutex Tux's lil' helper
Joined: 04 Sep 2003 Posts: 146
|
Posted: Fri Sep 05, 2003 2:32 pm Post subject: |
|
|
I thought so too... only I can't find ftp or lynx... are they not compiled yet? How can I download them? |
|
Back to top |
|
|
sklettke Guru
Joined: 05 Nov 2002 Posts: 352 Location: Madison, WI
|
Posted: Fri Sep 05, 2003 3:22 pm Post subject: |
|
|
Try using wget, if lynx or ftp isn't working. Wget is what portage uses to download the source. But again, by running mirrorselect -a -s4, it should add mirrors to make.conf and automatically try different servers and continue downloading like it did before.
Don't edit the ebuild, instead run mirrorselect, or manually update /etc/make.conf.
Scott _________________ Jab.ID: scottk@jabber.org
Kernel: 2.6.11-rc3-nitro0
KDE 3.3.2 with Xorg
MythBox: 2.6.5-gentoo-dev-r2 (LVMed 360GB in XFS; Athlon 2500+) |
|
Back to top |
|
|
mutex Tux's lil' helper
Joined: 04 Sep 2003 Posts: 146
|
Posted: Fri Sep 05, 2003 4:50 pm Post subject: |
|
|
How does the mirrorselect command replace the error in the ebuild file? For situations where emerge cannot connect to the server, it uses a different one, however when it can connect to the server but the path is invalid, it simply quits without trying any other server. The path is incorrect inside the actual ebuild file.
Will using the mirrorselect command fix this? |
|
Back to top |
|
|
jcall n00b
Joined: 29 Aug 2003 Posts: 14
|
Posted: Thu Sep 11, 2003 4:07 pm Post subject: |
|
|
I ran into the same problem (funny, I didn't a few days ago when doing this same thing, before I decided that my multi-boot system needed a different partitioning scheme . . .)
I fixed it by editing /usr/portage/app-shells/sash/sash-3.4-r5.ebuild, and changing the SRC_URI line to: SRC_URI="http://distro.ibiblio.org/pub/linux/distributions/gentoo/distfiles/${P}.tar.gz
then ran "emerge system" again.
sash-3.4.tar.gz then downloaded just fine, but then I ran into the same problem for sash-3.x-readline.diff.gz (well, host not found, anyway). So, I changed the file again. Now that area of the file reads:
SRC_URI="http://distro.ibiblio.org/pub/linux/distributions/gentoo/distfiles/${P}.tar.gz
http://distro.ibiblio.org/pub/linux/distributions/gentoo/distfiles/sash-3.x-readline.diff.gz
And my emerge is continuing . . .
-jared |
|
Back to top |
|
|
|