Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 489422 - Stage 3 install fails on i486 at emerge-webrsync step.
Summary: Stage 3 install fails on i486 at emerge-webrsync step.
Status: RESOLVED DUPLICATE of bug 484950
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] baselayout (show other bugs)
Hardware: All Linux
: Normal major (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-26 04:22 UTC by Ron OHara
Modified: 2013-10-26 15:02 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ron OHara 2013-10-26 04:22:48 UTC 
The i486 stage3 tarball does not work at the emerge-webrsync step of the documented install.

livecd / # emerge-webrsync
!!! Section 'gentoo' in repos.conf refers to repository without repository name set in '/usr/portage/profiles/repo_name'
emerge-webrsync: error: Repository 'gentoo' not found


Reproducible: Always

Steps to Reproduce:
1. Follow instructions on http://www.gentoo.org/doc/en/gentoo-x86-quickinstall.xml for an i486 install rather than an i686 install
2. get to the Code Listing 2.15 step ...  emerge-webrsync
3.
Actual Results:  
livecd / # emerge-webrsync
!!! Section 'gentoo' in repos.conf refers to repository without repository name set in '/usr/portage/profiles/repo_name'
emerge-webrsync: error: Repository 'gentoo' not found


Expected Results:  
download of portage for next step of install
Comment 1 Ron OHara 2013-10-26 04:27:06 UTC 
workaround.

before the emerge-webrsync command, do this:

mkdir /usr/portage/profiles
echo gentoo >/usr/portage/profiles/repo_name

then continue the install as documented.

emerge-webrsync
Comment 2 Bruce Hill 2013-10-26 04:29:33 UTC 
https://bugs.gentoo.org/show_bug.cgi?id=484730
Comment 3 Jeroen Roovers (RETIRED) gentoo-dev 2013-10-26 15:02:20 UTC 

*** This bug has been marked as a duplicate of bug 484950 ***