emerge fails but re-emerge works

[paulb787]

I am emerging kde and its a big one 515 packages. On the 301 package kdepim- runtime

I believe. The emege failed. I executed emerge kde-meta again and it worked fine. What could cause

This . I am curious if this is normal?

Ebuild failed was.the message

[mark_alec]

It is possible that there was an incorrect dependency somewhere, so a package was emerged before all its dependencies were. Without knowing details, it is impossible to tell

[few]

I am emerging kde and its a big one 515 packages. On the 301 package kdepim- runtime

I believe. The emege failed. I executed emerge kde-meta again and it worked fine. What could cause

This . I am curious if this is normal?

Ebuild failed was.the message

No, that that's not normal. File a bug including the build.log and your emerge --info.

[John R. Graham]

Look at the build log before filing a bug. There a few errors that can just indicate a system resource issue, such as "Bus error", or a hardware (or possibly tools) issue, such as "Segmentation fault" or "Internal compiler error". Bugs need to be reproducible and these issues, if transient and infrequent, probably should not be reported.

As mark_alec says, it could be a dependency issue. If so, it should be pretty obvious from the build log. Dependency issues should be reported.

- John