Control: tags -1 moreinfo On Tue, 11 Mar 2025 14:04:40 +0100 Guillem Jover <[email protected]> wrote: > Source: iproute2 > Source-Version: 6.13.0-1 > Severity: wishlist > > Hi! > > This package explicitly depends dpkg-dev (which is part of > build-essential), and build-essential in its autopkgtest Depends, > where it is also explicitly depending on @builddeps@, which already > includes the latter (which transitively includes the former). > > This is redundant, and has been entangling this package with dpkg's > testing migration for several Debian releases via its autopkgtests. > > Please drop both explicit dpkg and build-essential from the autopkgtest > Depends.
Hi, This is intentional, otherwise if a regression was introduced in those packages that breaks iproute2's autopkgtest, it would not be picked in unstable, and would start failing iproute2's autopkgtest _after_ they migrate, instead of _before_, which is the point of debci. With a quick glance at the results, these tests have always succeeded since they were enabled in debci. Could you please clarify what do you mean by "entangling"? What problem are you observing, precisely?
