Control: tags -1 + patch Control: forwarded -1 https://salsa.debian.org/ci-team/autodep8/merge_requests/17
On Fri, 20 Apr 2018 at 21:01:53 +0200, Paul Gevers wrote: > On Tue, 12 Dec 2017 12:22:38 +0000 James Page <james.p...@ubuntu.com> wrote: > > I've attached a patch that automatically remaps oslo. -> oslo_ which I > > think will > > resolve this issue. > > To be honest, I don't like it. I also don't like it. I don't think it scales well to have special cases for particular packages or families of packages in the autodep8 package: if the package under test needs special treatment, it should ask for it. IMO the autodep8 bug here is that there is currently no way to ask for it. My understanding is that the convention is that a package imported via `import oslo_log` should be packaged as `python3-oslo-log`, and I'm going to propose a patch for Python Policy to make this clearer - but I realise renaming an existing package is really annoying, because it involves the NEW queue and transitional packages, so the Oslo packages will probably stay as they are for a while. On Fri, 21 Jun 2019 at 08:34:55 +0100, James Page wrote: > rather than whitelist in autodep8 (which I agree is not > preferable) maybe [we] could use an XS- field in the debian control > file for a package so that the package maintainer can manipulate > the behaviour of the generate command directly, rather than having > to have an associated change in autodep8 itself. This is basically what https://salsa.debian.org/ci-team/autodep8/merge_requests/6 does. I've proposed an alternative at https://salsa.debian.org/ci-team/autodep8/merge_requests/17 using a file in debian/tests/ (which is how the pkg-perl autopkgtest works, and I personally slightly prefer that approach), but I'd be happy with either one. smcv
