+++ This bug was initially created as a clone of Bug #387937 +++ 12:02 < rb07> I think the problem was caused by my emerging portage when the message that a new version was available appeared, 12:02 < rb07> but I'm not sure. 12:04 < rb07> any ideas on how to break the circular dependency? 12:05 < rb07> I'm sure I can build libtool w/o using emerge, but how do I mark it as installed? so I can continue. 12:05 <@darkside_> message that a new version was available appeared 12:05 <@darkside_> so you ran emerge --sync? 12:05 < rb07> yes, several times 12:06 <@darkside_> don't do that 12:06 < rb07> I know the servers can blacklist me for high use. 12:06 <@darkside_> no, more issues than that, you ran --sync wayyy too early 12:06 <@darkside_> Code Listing 1.11: Updating the tree 12:06 < rb07> I meant several times from yesterday to today, not in a row. 12:07 <@darkside_> then and only then can you --sync for the first time 12:07 < rb07> I see. 12:08 < rb07> But there was another problem with a package, that's the reason I ran the sync. 12:08 < rb07> Binutils was the problem. 12:08 <@darkside_> ok? 12:09 < rb07> The downloaded binutils size was different from the expected size. 12:09 <@darkside_> oh, that issue is in the bootstrap image? :(
tomorrow's image can be used, as I verified (and fixed) bootstrap today
