From: sanvila@debian.org   
      
   On Sun, Feb 08, 2026 at 05:29:02PM -0500, James McCoy wrote:   
      
   > Just because something shows the same symptom, does not mean it is the   
   > same root cause. Rather than unarchiving and marking old bugs as   
   > "fixed", it would have been better, IMO, to file new bugs.   
   >   
   > That also wouldn't have left your link to the build logs as part of a   
   > comment in a control@ email, where it's harder to find. I only saw it   
   > when digging up this email to reply to it.   
   >   
   > At least as far as this subversion bug is considered, it is indeed a   
   > different issue from before, so I'm removing the "found" annotation.   
      
   We don't really know if if it's a different issue or not.   
      
   I wrote this to Michael Tokarev in Bug #1048754 who complained   
   in a similar way, and I believe my reply does apply here as well:   
      
   ----------------------------------------------------------------   
      
   Hi. The underlying problem here is that dpkg-source does not report   
   all the errors:   
      
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126665   
      
   So, yes, it may be the case that some packages now fail for a "different"   
   reason.   
      
   But it can also be the case that the fix was incomplete because the   
   original report was incomplete as well (because of the above bug).   
      
   I've seen this to happen quite often when people fix the thing that   
   they see in the build log but do not bother to try again.   
      
   Since I don't have an easy way to determine if the fix that was   
   implemented at the time was correct or not, I decided to reopen   
   the bug when I was able to determine that it currently fails.   
      
   I agree that this may not be perfect, but I believe it was better   
   than the all the other alternatives.   
      
   Thanks.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)