Code: Select all
CFLAGS="-O2 -mtune=i586 -pipe"
CXXFLAGS="${CFLAGS}"
CHOST="i586-pc-linux-gnu"
Code: Select all
CFLAGS="-O2 -mtune=i586 -pipe"
CXXFLAGS="${CFLAGS}"
CHOST="i586-pc-linux-gnu"

Wow, I had a Gateway laptop around that time too.... it was such a weight!drkstorm wrote:but i doubt you have a 586 compile.... this puppy is a classic... gateway laptop circa '95 ...p133, 4GB HD, 52MB ram... was my ssh portal into my home network, as well as apache and mediatomb server... lol... recently retired it from firewall/router duties... good thing since this happned...
I just retired my i586 server (K6-III) this past summer. Even if Gentoo quit supporting Stage1, at least they kept the tarballs out there long enough for the last time I reinstalled that machine. Don't have to worry about it now, since everything I've got is i686 or up. Of course I do have the hankering to get a low-power Via machine for a server, and that might take me back into i586-land, depending on which rev of the CPU it would have.drkstorm wrote:i certainly appreciate it:
but i doubt you have a 586 compile.... this puppy is a classic... gateway laptop circa '95 ...p133, 4GB HD, 52MB ram... was my ssh portal into my home network, as well as apache and mediatomb server... lol... recently retired it from firewall/router duties... good thing since this happned...Code: Select all
CFLAGS="-O2 -mtune=i586 -pipe" CXXFLAGS="${CFLAGS}" CHOST="i586-pc-linux-gnu"
ok, so i have 863MB free on the drive, would that be enough? how would i go about doing such a thing?Just a thought, but do you have enough space to make a 2nd chroot on the HD?
You could do a partial re-install into that chroot just to compile this required package??

Your basically doing a re-installation of Gentoo as in the gentoo install guide but into a subdirectory on the hard disk.drkstorm wrote:ok, so i have 863MB free on the drive, would that be enough? how would i go about doing such a thing?




Thanks for the reply.richard.scott wrote:Yes if you don't touch (i.e. don't format) /dev/hdb1 then all will still be on there if you decide to re-install.
I've no idea about the passwd=foo option. Why not just change the root password when the cd loads i.e. use the passwd command.
You can then start ssh and login remotely as root :-)

The new packages should not have been made stable until the new portage, which can automatically sort these out, was stable. The issue itself is not much different than most blockers, except it breaks things if you don't download the packages first. Unfortunately most people are not in the habit of downloading sources before removing blockers.kowal wrote:Since some many Gentoo installation have issue with e2fsprogs, com_err, and ss being blocked I'm wondering if anyone has asked what is/was the root cause? Bad programing on the development side? Did we miss some kind of news, warning, update? Too many packages or bad combination of installed packages? Just like many of you my x86_x64 and x86 machines were affected.

If you read the narratives at bugs.gentoo.org in full you'll be a little disappointed, although the Sparc guys had the good sense to NOT mark the offending ebuild(s) stable until things settle down.Stupendoussteve wrote:The new packages should not have been made stable until the new portage, which can automatically sort these out, was stable. The issue itself is not much different than most blockers, except it breaks things if you don't download the packages first. Unfortunately most people are not in the habit of downloading sources before removing blockers.kowal wrote:Since some many Gentoo installation have issue with e2fsprogs, com_err, and ss being blocked I'm wondering if anyone has asked what is/was the root cause? Bad programing on the development side? Did we miss some kind of news, warning, update? Too many packages or bad combination of installed packages? Just like many of you my x86_x64 and x86 machines were affected.
tl;dr: Who's in charge?The situation today: a stable package depends on unstable packages, either
directly, or on the unstable portage that can resolve the dependencies. One or
more of these unstable packages is not yet ready to go stable.
The situation later: Those packages are ready to go stable, and things can then
be done in the sensible order.
Kudos to the sparc maintainer at least (Comment #21) for grasping this and
acting accordingly.
Note that some users have already navigated through the blocks manually, and
they would then be presented with a downgrade path that may be just as
perilous. That's unavoidable, and those users have already shown the ability
to deal with the issue, and are recently familiar with the details. They need
do no more than add a couple of ~ keywords to keep the packages they've
currently got and avoid the downgrade.
The response to this issue otherwise is very disappointing. Mistakes happen,
complex dependencies are involved, and it can take some time for the details at
the crux of the issue to become clear - that's unfortunate but understandable.
We're past that point now, and what matters much more is the response to the
issue to prevent further harm. The indecision at this point is doing way more
harm - the poor pooch is raw and tired and begging for mercy and still nobody
is stopping..

Code: Select all
# USE="-*" FEATURES="-sandbox" emerge e2fsprogs e2fsprogs-libs
Why'd you need to do that? What issues were you having?NotQuiteSane wrote:Just a note, I had to run:
to get it to compile on my serverCode: Select all
# USE="-*" FEATURES="-sandbox" emerge e2fsprogs e2fsprogs-libs
NQS

The no use flags i tried first, to see if there was a conflict somewhere, but it still failed. I noted it was failing ihe sandbox, so i disabled it.richard.scott wrote:Why'd you need to do that? What issues were you having?NotQuiteSane wrote:Just a note, I had to run:
to get it to compile on my serverCode: Select all
# USE="-*" FEATURES="-sandbox" emerge e2fsprogs e2fsprogs-libs
NQS
What package is mktemp in now? I have been very conservatively updating a production server, trying to do everything right, and still things got b0rked...somehow I lost mktemp. When I successfully emerged coreutils, it did not install mktemp. Without mktemp I can't do basic things like restart apache or mysql...which is a nuisance because this whole problem happened right in the middle of a major mysql upgrade.njcwotx wrote:one was mktemp got put into some other package
Code: Select all
~ $ equery belongs mktemp
[ Searching for file(s) mktemp in *... ]
sys-apps/coreutils-6.10-r2 (/usr/bin/mktemp -> /bin/mktemp)
sys-apps/coreutils-6.10-r2 (/bin/mktemp)
Code: Select all
ls -al /usr/bin/mktemp
ls -al /bin/mktempOriginally, I had three blockages, the first being e2fsprogs-libs-1.41.1 blocking e2fsprogs-libs-1.41.2[blocks B ] sys-libs/ss (is blocking sys-libs/e2fsprogs-libs-1.41.2)
[blocks B ] sys-libs/com_err (is blocking sys-libs/e2fsprogs-libs-1.41.2)
* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.