| Issue 464: | Submit error because of dependencies issues is confusing | |
| 17 people starred this issue and may be notified of changes. | Back to list |
Affected Version: What steps will reproduce the problem? 1. Make a commit 2. Make another commit on top of the first one 3. Push the second commit for code review, 2 (dependent) changes are created 4. Try to submit the second change without having the first one reviewed and submitted What is the expected output? What do you see instead? Gerrit will fail (expected) with some strange error: Change cannot be merged due to unsatisfiable dependencies. The following dependency errors were found: Depends on commit 3c6a75294eb1fed5e646c08d27273e5327f20093 which has no change associated with it. Please rebase the change and upload a replacement commit. It is confusing because there is a change associated with the dependent on commit, it's just not yet code reviewed, merged in. This is even more confusing when there are multiple changes shown in the dependency output, some of them in different repositories (because of Issue 463) because there are changes associated with the dependent on commit. I think the message should say something like "Depends on commit .... which has no merged change in this repository associated with it" (or something like that). Please provide any additional information below.
May 20, 2011
Project Member
#1
nas...@grainawi.org
Status:
Accepted
Sep 27, 2011
What is the proper workaround for this for now? |
|
| ► Sign in to add a comment |