Your message dated Mon, 07 Dec 2020 16:22:35 +0530
with message-id <[email protected]>
and subject line Re: [Pkg-javascript-devel] Bug#974069: error Yarn hasn't been
able to find a cache folder it can use although folders are writable
has caused the Debian Bug report #974069,
regarding error Yarn hasn't been able to find a cache folder it can use
although folders are writable
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 [email protected]
immediately.)
--
974069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974069
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: yarnpkg
Version: 1.22.4-3
Severity: important
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I'm running `rails new ...`. At the end I get this:
[..]
Installing all JavaScript dependencies [4.2.2]
run yarnpkg add @rails/[email protected] from "."
yarn add v1.22.4
warning Skipping preferred cache folder "/home/daniel/.cache/yarn" because it
is not writable.
warning Skipping preferred cache folder "/tmp/.yarn-cache-1000" because it is
not writable.
warning Skipping preferred cache folder "/tmp/.yarn-cache" because it is not
writable.
error Yarn hasn't been able to find a cache folder it can use. Please use the
explicit --cache-folder option to tell it what location to use, or make one of
the preferred locations writable.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this
command.
Installing dev server for live reloading
run yarnpkg add --dev webpack-dev-server from "."
yarn add v1.22.4
warning Skipping preferred cache folder "/home/daniel/.cache/yarn" because it
is not writable.
warning Skipping preferred cache folder "/tmp/.yarn-cache-1000" because it is
not writable.
warning Skipping preferred cache folder "/tmp/.yarn-cache" because it is not
writable.
error Yarn hasn't been able to find a cache folder it can use. Please use the
explicit --cache-folder option to tell it what location to use, or make one of
the preferred locations writable.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this
command.
The folders are writable. I even tried to make /home/daniel/.cache/yarn
world-writeable. This seems odd.
Regards, Daniel
- -- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages yarnpkg depends on:
ii ca-certificates 20200601
ii node-asap 2.0.6-2
ii node-babel-runtime 6.26.0+repack-4
ii node-bytes 3.1.0-1
ii node-camelcase 5.3.1-1
ii node-chalk 2.4.2-1
ii node-chownr 1.1.3-5
ii node-ci-info 2.0.0+~2.0.0-2
ii node-cli-table 0.3.1-2
ii node-commander 4.1.1-2
ii node-death 1.1.0-1
ii node-debug 4.2.0+~cs4.1.5-1
ii node-deep-equal 1.0.1-2
ii node-detect-indent 6.0.0-1
ii node-duplexify 4.1.1-1
ii node-emoji 1.10.0-1
ii node-fast-levenshtein 2.0.6+ds-1
ii node-glob 7.1.6+~7.1.3-1
ii node-imports-loader 0.8.0-2
ii node-ini 1.3.5-1
ii node-inquirer 3.3.0-3
ii node-invariant 2.2.2-1
ii node-is-builtin-module 2.0.0-1
ii node-js-yaml 3.14.0+dfsg-2
ii node-loud-rejection 2.2.0-1
ii node-micromatch 4.0.2+repack+~4.0.1-1
ii node-minimatch 3.0.4+~3.0.3-1
ii node-mkdirp 1.0.4-3
ii node-node-uuid 3.3.2-2
ii node-object-path 0.11.5-3
ii node-path-root 0.1.1-1
ii node-proper-lockfile 4.1.1-2
ii node-puka 1.0.1+dfsg-1
ii node-pump 3.0.0-4
ii node-pumpify 2.0.1-1
ii node-read 1.0.7-2
ii node-request 2.88.1-4
ii node-request-capture-har 1.2.2-1
ii node-resolve 1.18.1-1
ii node-rimraf 2.6.3-1
ii node-semver 7.3.2-1
ii node-ssri 8.0.0-1
ii node-strict-uri-encode 2.0.0-1
ii node-strip-ansi 6.0.0-2
ii node-strip-bom 3.0.0-1
ii node-tar-stream 1.5.2-2
ii node-validate-npm-package-license 3.0.4-1
ii node-yn 4.0.0-1
ii nodejs 12.19.0~dfsg-1
yarnpkg recommends no packages.
yarnpkg suggests no packages.
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl+pY74ACgkQS80FZ8KW
0F3KHg//VBHFKsoLewiP4XUydfFuAkdBeD058+gfwCrBcponD5uhZi8IHF2YALmL
bbgaQluriZmTJLz/aeYMq04zpSX+gPNgBMaGg8+5X06fj6jHamihAvNlQWOTLBvV
TDg9QSniuENLimuBKTDK/DqS1GE5zpUMvjPdrd+38HcXRKEfCbjWcw3fwlBXXuB/
xQXSN8yIWqZxTMGswPG6vOohBeWp57nebmKiBmLegqKYefVr6inB8aa/7Mi9I63X
uLXVdyoiy7IcrsfxZYj+6DX6QKP2EIBnmzjIKC7FTzhb+Ih31u21qPhP5MzT35uD
9uORhxdtiOVDWurTvnLhWh7zLqege79ciraOwihiWqERBKn60032ZXyT7lUuQJXG
smmzlQ8eJvzB/dcGlsPfMOqyd9nR2AUvYeOQCsW9luZx45C038qiyOvFd9SRXwBZ
7QpGDU5Q1gCyz4XqAM8KFCi4T4S1WYiaibL7i9FgQs8EEp6VRWPZADYz6TUwWwkF
+hHHmMkGmjDgqrsW0tzZAMerpmBmPJ3ARasagt0oXUYc09mMmhO/nDszrQ+HenVC
TpEl83twQxvdskoduetA48FfcLiNV5dH3xVhaH4bU77xTkxAvxEdsqjo+yEYWaQ0
Yi+LMDfiX2oK9rAVQHanfIDpUjdUmEya5wLrnrN2Lq7AwsTyIAM=
=mfto
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Control: fixed -1 1.22.4-4
On Mon, 09 Nov 2020 22:00:53 +0530 Pirate Praveen
<[email protected]> wrote:
> This is caused by node-mkdirp transition, but node-yarnpkg is ftbfs
currently (caused by node-babel/node-babel7 transition) which makes it
hard to fix.
Fixed in last uplod.
--- End Message ---
