From: ametzler@bebt.de 
  
 On 2025-09-20 Jonas Smedegaard  wrote: 
 > Quoting Alexander Kj€ll (2025-09-20 19:45:07) 
 >>> It helps me (and Debian generally, I assume) that packages do not have 
 >>> missing dependencies or build-dependencies when introduced to unstable, 
 >>> and it is my understanding that when NEW queue is involved there is no 
 >>> way to know if they are missing or not because that would requre a 
 >>> crystal ball. Or am I missing something? 
  
 >> Could you explain how this helps? I don't really see it. 
  
 > It is helpful to me that I can generally expect Debian unstable to 
 > contain installable packages. 
  
 > It slows me down that for librust-*-dev packages I cannot simply check 
 > that some packages I need are listed in aptitude, but I need to check 
 > for each of them that their dependencies are ok. 
  
 > Does that make sense? I am having trouble understanding what it is that 
 > you cannot see, and wonder if we are talking past each other here. 
  
  
 And to spell it out explicitly we would prefer if you changed from 
 A) 
         Upload $package + its missing dependencies to unstable 
  
 (Causing unstable containing broken packages for $random, posibly very 
 very long time)) 
  
 to 
  
 B) 
         * Upload $package + its missing dependencies to experimental 
         * Wait for all parts to pass through NEW 
         * Re-upload everything to unstable 
  
 cu Andreas 
 -- 
 `What a good friend you are to him, Dr. Maturin. His other friends are 
 so grateful to you.' 
 `I sew his ears on from time to time, sure' 
  
 --- SoupGate-Win32 v1.05 
  * Origin: you cannot sedate... all the things you hate (1:229/2)