This reverts commit a256ae6a.

2b21e131 (community/grafana: upgrade to 7.5.3, 2021-04-07) disabled
this check on armv7, but it fails on armhf as well.

unfortunately newer setuptools versions introduces changes that cause
breakage to a great amount of python3 modules that were written in a
_PERFECTLY_ acceptable form and some that even followed the _EXAMPLES_
provided by upstream.

To avoid mixing npm packages installed by the user using npm with
packages managed by apk.

npm is bundled in Node.js, but it's a standalone project with its
own release cycle and version number. main/nodejs provides LTS
version of Node.js, so it includes old version of npm.

Alpine build tools don't handle subpackages with pkgver different
from the origin pkgver. Thus the current 'npm' subpackage has version
14.16.1-r0 (version of the Node.js) which is confusing, because the
real version of the packaged 'npm' is 6.14.11.

Moreover, npm has gazillion bundled dependencies, so there's a high
risk of security vulnerabilities; using npm bundled in Node.js
quite complicates security patching and requires rebuilding complete
Node.js package.

For these reasons, I think it will be better to split npm into a
separate aport and provide the latest version instead of some arbitrary
version bundled in the Node.js tarball.

Actually, I planned this three years ago (see commit message in
244cc743), but forgot about it.

There's one unpleasant consequence of this change - the latest npm
version is 7.9.0 which is lower than 14.16.1 (version inherited from
nodejs package). Since Alpine doesn't have "epoch" version as e.g.
Fedora, there's nothing I can do about it beside informing the users
(using nodejs.post-upgrade script).

Creating an alpine-linux container errors out with the error:

> 'mknod: dev/zero: File exists'

Antoni Aloy Torrens authored 3 years ago and Leo committed 3 years ago

Co-authored-by: Leo <thinkabit.ukim@gmail.com>