Ok, “good”, at least that’s consistent. Could be a Mono bug or an Elements RTL HTTP bug; unfortunately I cannot reproduce it in a simple test case that loads the same URLs :(. I’ll investigate.
(The HTTP Error 0 ones are the bugs; the 404 are legit, those packages simply don’t exist ion those repos),
Workaround for now: delete your cache start Fire and load your project, and let Fire finish resolving the references (check the References node in the tree). That uses the native Cocoa version of EBuild that’s linked into the IDE, which (for me) does not exhibit this bug; once Fire is done resolving, all the packages will be in the cache, so when you build, the Mono-based version of EBuild that runs the compiler will pick them up from there.
I’ll see what I can do re the HTTP error over the next few days 