From: julien@lecomte.at 
  
 On 09/09/2025 22:43, Soren Stoutner wrote: 
 > On Tuesday, September 9, 2025 1:39:21€€€PM Mountain Standard Time Soren 
 Stoutner 
 > wrote: 
 >> On Tuesday, September 9, 2025 1:15:20€€€PM Mountain Standard Time Julien 
 > Lecomte 
 >> wrote: 
 >>> Hello 
 >>> 
 >>> I'm trying to create a package nwnxee that depends on package 
 >>> nwnee-dedicated. 
 >>> 
 >>> But both versions must be the same. If nwnxee is installed as version 
 >>> 8193.37.15+deb12u2~git18cffdba, then nwnee-dedicated must be 
 >>> 8193.37.15-xyz, where xyz can be any number. It can not be 
 >>> 8193.37.14-xyz nor 8193.37.16-xyz. 
 >>> 
 >>> And then, same goes for 8193.37.16 which must match with 8193.37.16 but 
 >>> not 8193.37.15. 
 >>> 
 >>> If I write nwnxee depends as `nwnee-dedicated (>= 8193.37.15), 
 >>> nwnee-dedicated (<8193.37.16)`, then I get a deprecated warning for 
 >>> nwnee-dedicated for using < 
 > 
 > If you are just asking about the required syntax, I think what you are 
 looking 
 > for is << (just < is not a valid syntax for this field). 
  
 I guess the << works. Thanks! 
  
 > https://www.debian.org/doc/debian-policy/ch-relationships.html 
 > 
 >>> What's the proper way to ensure that nwnxee version is always the same 
 >>> major.minor.patch nwnee-dedicated ? 
 >> 
 >> Are the produced from the same or different source tarballs? 
 > 
  
 Different tarballs. 
  
 --- SoupGate-Win32 v1.05 
  * Origin: you cannot sedate... all the things you hate (1:229/2)