Le ven. 17 sept. 2021 à 21:20, Felix Lechner <felix.lech...@lease-up.com> a écrit : > > Hi, > > On Fri, Sep 17, 2021 at 1:39 PM Bastien Roucariès > <roucaries.bast...@gmail.com> wrote: > > > > Package that include "/usr/(?:lib|share)/(?:[^/]+/)?/nodejs/.*\.node$' are > > arch:any package (include node plugin) and thus should be arch:any > > Thank you for this suggestion! > > The files in question are shipped in installable packages that do not > contain the Arch:any designation. (It appears in d/control in the > sources.) The installable architecture in DEBIAN/control is either the > actual port or 'all'. Furthermore, I believe the wildcarded directory > level before 'nodejs' must be a known multi-arch triplet.
yes it is > Is it okay > if Lintian instead requires that the multi-arch component of the file > paths found matches the target architecture of the installable package > in which they were shipped? Yes it is > If that is acceptable, Lintian already has checks to constrain the > installation paths for shared libraries, although they may need to be > expanded. (And we have to watch out for -cross packages.) Do you have > candidates for examination besides node-iconv (which I found locally) > that should trigger the condition? I am fixing node-expat-expat that ship under /usr/lib/ > > Moreover in this case ma:foreign is a error (they are plugins) > > That will be addressed at the same time, although I am not yet sure how. Thanks > Kind regards > Felix Lechner