Le 29/01/2020 à 20:04, Helmut Grohne a écrit : > Hi Xavier, > > On Wed, Jan 29, 2020 at 06:54:36PM +0100, Xavier wrote: >> FYI, I opened a transition BTS to fix bad install to i386 arch >> (DEB_HOST_MULTIARCH problem) > > If you tell me about a bug report, please include the bug number. You > can even do so in the initial submission using X-Debbugs-Cc. > >> I didn't find in doc how to discriminate afected packages. The only way to >> see if a package is OK is to look at >> `debc|grep usr/lib/i686-linux-gnu/nodejs`: files have to be installed in >> usr/lib/i386-linux-gnu instead. > > The multiarch hinter has the relevant data for unstable: > > SELECT distinct package.name FROM package JOIN content ON content.pid = > package.id WHERE architecture = 'i386' AND filename LIKE > './usr/lib/i686-linux-gnu/%'; > > dolphin-owncloud > fswatch > libhmsbeagle-dev > likwid > node-iconv > node-modern-syslog > node-node-sass > node-nodedbi > node-re2 > node-sqlite3 > node-ws > node-zipfile > > This looks like very few affected packages and it is strictly providing > an upper bound. The non-node packages are likely just buggy. Unless I am > mistaken, lintian also has a tag for this symptom, but I cannot find it > at the moment. > > Helmut
Thanks, I can rebuild node* package if you think it's more simple than a transition
