[BUG] cacache doesn't work on Android about cacache HOT 7 CLOSED

Thank you so much for investigating this. Hopefully a solution will be applied soon.

I noticed that the "possible patch" you linked above is present in the Termux repository, and I noticed there are other .patch files there too, I am wondering how does that work? Is it possible that Termux applies the patch in a forced way themselves, so that we don't really have to wait for a fix on the original package? Or is it something else?

from cacache.

Thank you so much for investigating this. Hopefully a solution will be applied soon.

I noticed that the "possible patch" you linked above is present in the Termux repository, and I noticed there are other .patch files there too, I am wondering how does that work? Is it possible that Termux applies the patch in a forced way themselves, so that we don't really have to wait for a fix on the original package? Or is it something else?

When building packages for Termux, the building system of Termux packages will apply this patch to the sources, thus the deb files will contain a patched npm. But when npm is updated, the patched files will be overridden by the files from official package, so this patch will not work anymore.

from cacache.

But from the way you said it, it looks like npm should work right after installing in termux, as long as I don't update npm, but as mentioned in the other issue this is not the case, why?

from cacache.

But from the way you said it, it looks like npm should work right after installing in termux, as long as I don't update npm, but as mentioned in the other issue this is not the case, why?

Because npm you installed through apt/pkg install nodejs contains patched files, the moveFile function will not call fs.link. But if you update it manually, the patched file will be overridden.

from cacache.

Sorry if I wasn't clear, that's not what I tried to ask. My question is: considering the patch exists, why do I still get an error, even if I don't update npm manually?

from cacache.

Sorry if I wasn't clear, that's not what I tried to ask. My question is: considering the patch exists, why do I still get an error, even if I don't update npm manually?

Emmm... I have no idea. After a fresh install of nodejs, the move-file.js in $PREFIX/lib/node_modules/npm/node_modules/cacache/lib/util should only contains a workable moveFile function. If you still get the same error after a fresh install of nodejs through apt or pkg, please report this bug to https://github.com/termux/termux-packages.

from cacache.

I know this is truly an edge case, but I am running into this linking issue when using a mounted fs that does not support links (s3fs-fuse).

from cacache.