Set owner to @munificent.
Added Area-Pub, Accepted labels.

It looks like the problem with your specific package graph is that you are depending on asset_pack both from git and using a path dependency. (Your pubspec has a git dependency and, I think, simple_audio has a path dependency.) My hunch is that there is no valid solution for your dependency graph because of this.

Unfortunately, the solver doesn't determine that efficiently. There's two problems here:

1. It runs out of heap space trying to find a solution. It should be able to explore lots of solutions without burning heap space.
2. It's trying a bunch of solutions that don't help and don't make sense. There's no point in trying every version of, for example, meta, when meta doesn't even depend on asset_pack which is the problematic package.

This is a bug in the solver, and I'll try to get a fix in.

In the meantime, you can avoid this by avoiding the source mismatch that you have on asset_pack. Everything that depends on that needs to get it from the same source.

Removed Priority-Medium label.
Added Priority-High label.

This comment was originally written by @davidB

I workaround it, by symlinking manually my local simple_audio.
I'd got the same issue with official simple_audio, because it depends on an other repo than my fork of asset_pack.

White the previous solver, I'd got an alert in this case.

Do you think it's possible (in this case) for dependencies definition of the root project override transitive one (IIRC maven and ivy apply this rule) ?

Thanks

White the previous solver, I'd got an alert in this case.

Yes, this is what the new solver should be doing too. Your dependency graph is problematic, it's just failing to reach the failed state so that it can tell you that.

Do you think it's possible (in this case) for dependencies definition of the root project override transitive one (IIRC maven and ivy apply this rule) ?

Yes, see: https://code.google.com/p/dart/issues/detail?id=8566

Added Started label.

With this patch: https://codereview.chromium.org/14685002/

pub should now handle this case much better.

Added Fixed label.

This issue has been moved to dart-lang/pub#527.