We have been working on fixing composes the last few days, and it's been failing. However it seems that people are still being mailed about broken deps even though the compose failed.
We should not bother them, since nothing has actually changed here, and if we do a bunch of composes a day to fix things they will get a bunch of duplicate emails they can't do anything about.
PR #57 might do it. If the patch is accepted, I can submit the same change against other branches.
@ausil and @lsedlar this looks like the fix from PR #57 is already merged in master and it is also already present on the f26 branch.
Is this okay to close or is this something else going on that should be looked at first?
@kellin Yeah, I think we can call this done :( sorry for the noise
Per comment from @ausil closing.
Metadata Update from @kellin: - Issue assigned to kellin - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)