title: svn mergeinfo - E195016: "must be ancestrally related"
body: <p>Although there are several similar questions here (e.g., <a href="https://stackoverflow.com/questions/490164/svn-reintegration-merge-error-must-be-ancestrally-related">SVN - Reintegration Merge error: "must be ancestrally related"</a>) and on the Web, I wasn't able to figure out why <code>svn mergeinfo &lt;file&gt;</code> causes an error in all of my SVN repositories. In contrast to all other Q&amp;As that I have found, I am actually able to execute <code>svn merge</code> successfully. For example, undoing a previous commit to a <code>pom.xml</code>file:</p>
  
  <pre><code>svn merge -r 17409:17408 pom.xml
  --- Reverse-merging r17409 into 'pom.xml':
  U    pom.xml
  --- Recording mergeinfo for reverse merge of r17409 into 'pom.xml':
  U   pom.xml
  --- Eliding mergeinfo from 'pom.xml':
  U   pom.xml
  </code></pre>
  
  <p>However, when I execute <code>svn mergeinfo</code>, I get the following error:</p>
  
  <pre><code>svn: E195016: 'https://../trunk/MyProject/pom.xml@50446' must be ancestrally related to
  'https://../trunk/MyProject@50446'
  </code></pre>
  
  <p>In this example, 50446 is the current head revision number and I get that same error for every file I've tried. Only when I execute the mergeinfo command on the top directory itself, it works:</p>
  
  <pre><code>svn mergeinfo .
      youngest common ancestor
      |         last full merge
      |         |        tip of branch
      |         |        |         repository path
      50446              50446   
      |                  |       
    -------| |------------         ../trunk/MyProject
       \                         
        \                        
         --| |------------         ../trunk/MyProject
                         |       
                         50446   
  </code></pre>
  
  <p>And even stranger, I don't find any mergeinfo properties set. Commands like <code>svn propget svn:mergeinfo --recursive</code> or <code>svn propget svn:mergeinfo --depth=infinity</code> don't output anything and return successfully with status code 0.</p>
  
  <p>Does anyone have an idea how I can fix our files to be "ancestrally related" again to the projects they are located in?</p>