Isn't this how Stack Exchange works?
The question was asked, answered as well as accepted on 14th Nov 2013. I cast the first Duplicate Closure Vote on 15th Nov 2013 on that question.
By the time, the first vote was cast, the question had already been answered as well as accepted to the satisfaction of the question asker.
The question is about unmet dependencies and we already have a canonical reference question for this in the form of following question:
- How do I resolve unmet dependencies after adding a PPA?How do I resolve unmet dependencies after adding a PPA?
This is a canonical reference question for the topic because it contains all the possible solutions for the problem of unmet dependencies. Obviously, there may still be cases when the solutions given therein doesn't solve the situation. In those cases, when a new question is asked on the same topic, we let it remain open until an answer is found for it. Once, this new situation is solved, we close this new question and merge the answers with the canonical question.
So, we have already reached the stage of closing this new question. The next stage is to flag it for moderators to merge the answers with the canonical question. Why are we reopening it?
(While flagging for merger, there may be a situation when the answer might not make complete sense in its current form if merged with the other one. In such situations either we should edit the answer appropriately; or, if we don't have enough knowledge on the topic, leave a comment below the answer to ask if someone could edit it appropriately.)
