> On 09/25/2026 12:48 AM IST Helmut Grohne <[email protected]> wrote: > > > On Thu, Sep 24, 2026 at 09:48:57PM +0530, Nilesh Patra wrote: > > On 24/09/26 8:55 pm, Alexandre Detiste wrote: > > > Package: lintian > > > Version: 2.141.0 > > > Severity: important > > > > > > Dear Lintian Maintainers, > > > > > > To avoind needlessy pulling in python3-pip & python3-setuptools > > > in ever single flit run, the engine "python3-flit" has been spun-out. > > > > > > Please rework lintian to check for "python3-flit | flit" instead of > > > "flit". > > It currently checks for flit:any. I initially thought I could just add > > python3-flit:any > > and that would just work but I saw python3-flit is not marked `M-A: > > foreign`. > > > > I suspect depends on setuptools is the reason for that? In that case :any > > should be simply > > skipped, right? > > I am somewhat confused here. :any only ever makes sense if the target > package carries "Multi-Arch: allowed". Neither flit nor python3-flit > have that Multi-Arch value. So both python3-flit:any and flit:any would > be universally unsatisfiable.
Yes, hence the original question to skip ":any" in the lintian check -- I did not see initially that flit was an arch:all package when I was about to add python3-flit:any, and only later noticed it does not make much sense. Maybe the :any was an old heuristic and nobody paid attention to it. I will drop it also for flit:any in lintian. Thanks for responding! Nilesh
