[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#950151: marked as done (transition: pkg-js-tools)

Your message dated Sat, 8 Feb 2020 21:15:58 +0100
with message-id <a4b6bfcf-3c9e-e850-05cb-a2534a0fa475@debian.org>
and subject line Re: Bug#950151: Fwd: transition: pkg-js-tools
has caused the Debian Bug report #950151,
regarding transition: pkg-js-tools
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
950151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950151
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition

Hi all,

pkg-js-tools provides a Node.js auto installer (debhelper plugin) used
by JS Team.

Prior to 0.9.26, pkg-js-tools used DEB_HOST_GNU_TYPE instead of
DEB_HOST_MULTIARCH to install arch dependent Node.js files. This affects
i386 build since these files are not installed in the good directory.
This causes reproducible build failures (see [1] for an example) and
render these packages unusable with i386.

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.

Note that buster packages are not affected: files where previously
installed in /usr/lib/nodejs (all arch and indep files). That's why affected
packages are those which:
 *     are arch-dependent
 * and depends on pkg-js-tools
 * and were rebuilt after pkg-js-tools 0.9.0 release (0.8 in experimental)

Cheers,
Xavier

[1]: https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/i386/node-request-promise.html

Ben file (try):

title = "pkg-js-tools";
is_affected = .depends ~ "libnode64" & .build-depends ~ "pkg-js-tools";
is_good = <Fill out>;
is_bad = <Fill out>;

--- End Message ---
--- Begin Message --- 
Hi all,

On 31-01-2020 14:18, Paul Gevers wrote:
> On 29-01-2020 20:23, Xavier wrote:
>>> 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
> 
> I scheduled the node pages on this list (minus node-node-sass, it
> FTBFS). Do these non-node packages need inspection first?

All the packages that I scheduled have migrated to testing. I am closing
this bug as all other issues are tracked separately.

Paul

--- End Message ---
Reply to: