Bug#818618: dpkg-genchanges: Please exclude packages disabled in unstaged builds

2018-11-10 Thread Samuel Thibault
Hello, Guillem Jover, le sam. 10 nov. 2018 02:46:27 +0100, a ecrit: > You might want to try the problematic upload but removing the entry > only from the Package-List field, keeping the entries in the .changes > Binary field, and see what happens. I got a reject: Invalid dsc file: Package-List a

Processed: Re: Bug#901827: dpkg: Support two-sided version constraint ranges, required to properly translate Cargo dependencies

2018-11-10 Thread Debian Bug Tracking System
Processing control commands: > severity 901827 important Bug #901827 [dpkg] dpkg: Support two-sided version constraint ranges, required to properly translate Cargo dependencies Severity set to 'important' from 'wishlist' > block 913408 by 901827 Bug #913408 [librust-crossbeam-epoch-0.5-dev] libru

Bug#901827: dpkg: Support two-sided version constraint ranges, required to properly translate Cargo dependencies

2018-11-10 Thread Ximin Luo
Control: severity 901827 important Control: block 913408 by 901827 Ximin Luo: > Guillem Jover: >> [..] >> >> So you could have package slab-X.Y and then depend on just that, or if >> for some reason you need to have coinstallability down to the minor >> version, then slab-X.Y.Z, in which case that

Processed: Re: Bug#901827: dpkg: Support two-sided version constraint ranges, required to properly translate Cargo dependencies

2018-11-10 Thread Debian Bug Tracking System
Processing control commands: > severity 901827 important Bug #901827 [dpkg] dpkg: Support two-sided version constraint ranges, required to properly translate Cargo dependencies Ignoring request to change severity of Bug 901827 to the same value. > block 913408 by 901827 Bug #913408 [librust-cross

Bug#869184: dpkg: source uploads including _amd64.buildinfo cause problems

2018-11-10 Thread Salvatore Bonaccorso
Hi Guillem! On Fri, Nov 09, 2018 at 11:48:27AM +0100, Guillem Jover wrote: > Hi! > > On Thu, 2018-11-08 at 20:28:57 +, Holger Levsen wrote: > > On Thu, Nov 08, 2018 at 09:24:01PM +0100, Salvatore Bonaccorso wrote: > > > We were again biten by this issue for some security-updates (most > > > r