On Sun, May 06, 2018 at 08:42:00PM +0000, Niels Thykier wrote: > Chris Lamb: > > tags 898077 + pending > > thanks > > > >> Lintian should perhaps check of there is a python package that meets the > >> dependency requirement? Or allow e.g. "*scour"? > > > > We can't do a wildcard (!)
It would also have been wrong in this case, since the Python 3 module package does not (and should not) have a dependency on the dh addon. In stretch the dh addon is (wrongly) in the Python 2 module package, that's the only reason why we ended up with the python-scour -> scour dependency. > > but we can also check for > > python-scour. I've done this in Git, pending upload: > > > > > > https://salsa.debian.org/lintian/lintian/commit/fc69686ae2d6aff415762812e805af4e5e9ca627 > > > > data/debhelper/dh_addons-manual | 1 + > > debian/changelog | 4 ++++ > > 2 files changed, 5 insertions(+) > > > > > > Regards, > > > > Hi, > > I am not entirely convinced this is a good idea. As I understand it, > that dependency is a temporary measure to avoid breakage but the plan is > to remove the dependency (i.e. packages will be required to build-depend > directly on "scour" for the add-on). >... python-scour is Python 2, so the plan is that python-scour will be removed after buster. Looking at scenarios like stretch-backports, it might be easiest to consider python-scour build dependencies as fine here for now and handle them after buster with the general Python 2 removal. > Thanks, > ~Niels cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
