emerge: there are no ebuilds to satisfy "=app-shells/bash-3.2_p17-r1" grobian, intended or not? http://overlays.gentoo.org/proj/alt/changeset/38303
Duplicate of bug #259957 maybe?
(In reply to comment #1) bash-3.2_p17-r1 is used for bootstrapping prefix. It is depending on the other, as ebuilds in prefix are auto-synced to the tree.
(In reply to comment #2) > (In reply to comment #1) > > bash-3.2_p17-r1 is used for bootstrapping prefix. > It is depending on the other, as ebuilds in prefix are auto-synced to the tree. > Nope, its not depending on gentoo-x86 here. We have a separate tree and they can do what they want. It is simply a restore from svn, and merely filed here as a note to self to ask grobian about it because I'm sure it just slipped through. As of right now, only affects new installs that use the latest_tree argument to bootsrap-prefix.sh. But this bug will block a snapshot upgrade until the instructions can get upgraded.
I removed it because gentoo-x86 removed it. So that's sort of semi-automatic. We have no other choice than to restore _p17-r1 since all the others are using eautoreconf, including bash-4.0. I think that's a serious bug, and I need to investigate if that's done in gentoo-x86 too.
bah, autotools is a requirement due to Interix... $!%&#!?
All bashes are fixed now, this probably breaks Interix. Don't use eautoreconf in critical ebuilds like bash, patch configure instead. (And send the **** patch upstream for maintenance sake!) We no longer need to force a special bash version.
