From: rra@debian.org 
  
 Simon McVittie  writes: 
  
 > Note that if a package exists in unstable, it will usually get copied into 
 > Ubuntu 'universe' for their LTS releases, even if it is unsuitable for 
 > that purpose. experimental might be a better choice for that reason. 
  
 Or Ubuntu should stop pulling things into universe that have RC bugs, or 
 at least that class of RC bugs. It feels weird to make Debian upload 
 decisions based on an Ubuntu practice with obvious flaws, and it's easier 
 to find and use packages in unstable. Maybe we can instead help Ubuntu do 
 something more sensible. 
  
 Do we have a documented way of marking an RC bug as being a persistent 
 blocking bug to prevent a package from entering testing, as opposed to 
 some other transient problem that is expected to be fixed, so that Ubuntu 
 could trigger off of that field? I feel like this isn't the first time 
 something like that would be useful. 
  
 That said, there may be other release-related reasons that I don't know of 
 that would argue against having a package in unstable that we'll probably 
 never be able to include in a release. 
  
 -- 
 Russ Allbery (rra@debian.org)               
  
 --- SoupGate-Win32 v1.05 
  * Origin: you cannot sedate... all the things you hate (1:229/2)