When performing a stage1 install, the /usr/portage/scripts/bootstrap.sh script fails to download http://www.research.ibm.com/trl/projects/security/ssp/gcc3_3_2/protector-3.3.2-2.tar.gz ERROR 404: Not Found !!! Couldn't download protector-3.3.2-2.tar.gz. Aborting. !!! Fetch for /usr/portage/sys-devel/gcc/gcc-3.3.4-r1.ebuild failed, continuing... After looking at the website, I see that file is no longer available. There is a new version of protector called protector-3.3.2-3.tar.gz. I modified the ebuild file as follows: PP_FVER="${PP_VER//_/.}-2" changed it to PP_FVER="${PP_VER//_/.}-3" then Portage tells me to run the following: ebuild /usr/portage/sys-devel/gcc/gcc-3.3.4-r1.ebuild digest gcc then fails to compile with: Failed Patch: gcc333-ssp-3.3.2_1-fixup.patch Reproducible: Always Steps to Reproduce: 1. 2. 3.
The current versions and locations are http://www.research.ibm.com/trl/projects/security/ssp/gcc3_3_2/protector-3.3.2-3.tar.gz and gcc3_4_1/protector-3.4.1-1.tar.gz (the 3.3.x version is updated!!, not used currently in ebuilds)
this bug is very false I just bootstrapped a stable system and have had no problems getting the package. Yes there should be an update in portage but only for those that are ~x86 users stable systems shouldnt be testing latestest software which makes updating the ebuild useless at this point.
I do not think that the "bug is very false" . There seems to be two problems here: *) Given 2004.3 is a fixed release , the gcc ebuild for stage 1 -- I assume it is the version described above , "gcc-3.3.4-r1.ebuild" -- includes http://www.research.ibm.com/trl/projects/security/ssp/gcc/ . That URL is no longer valid . *) Option (LONG) "Selecting Mirrors" left my system with mirrors : ftp6.uni-erlangen.de , vlaai.snt.ipv6.utwente.nl (ftp & html) , gentoocompass.org . NONE of these "mirrors" include protector-3.3.4-2.tar.gz . REF : http://forums.gentoo.org/viewtopic.php?t=248944&highlight=protector http://forums.gentoo.org/viewtopic.php?t=241668&highlight=protector
I can confirm this bug. I just bootstrapped a brain new installation and I can see the same problem. My GENTOO_MIRRORS variable is clean.
added mirror://gentoo to SRC_URI