mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-26 01:26:00 +03:00
[GH-ISSUE #805] Pip dist: archivebox setup failed due to "[WinError 2] The system cannot find the file specified" on Win10 #3526
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#3526
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @fireattack on GitHub (Jul 22, 2021).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/805
(It says " Hint: Try deleting E:\archivebox/node_modules and running it again" but there is not
node_modulessubdir.)So does
archivebox init --setup.I should have all the environments:
@pirate commented on GitHub (Jul 24, 2021):
Have you tried running AB anyway (skipping finishing setup)? It may work partially, just without a few extractors.
Running directly on windows without WSL2/Docker/Cygwin is not officially supported. Unfortunately I can't help much as I don't have a windows system to test on easily.
@barnett2010 commented on GitHub (Jul 29, 2021):
win10 cmd
@barnett2010 commented on GitHub (Jul 29, 2021):
If don’t install the npm module,
pdf screenshot singlefile .all file does not exist
@Explorare commented on GitHub (Jul 30, 2021):
Met the same issue today.
[env]
Windows 10 19043.1110
Python 3.9.6
Node 16.6.0
npm 7.19.1
I've tried manually install the mercury / singlefile / readability using npm, but the program still didn't recognize them.
@pirate commented on GitHub (Jul 31, 2021):
Please post the full unredacted output of
archivebox --version.@Explorare commented on GitHub (Jul 31, 2021):
@Explorare commented on GitHub (Jul 31, 2021):
Tried to install the dependencies manually but the check result stills blaming not found them. The SingleFile dependency once validated but became invalid in the next check. Don't know why.
@pirate commented on GitHub (Aug 2, 2021):
Can you post the output of running these commands inside the archivebox directory:
you may need to prepend
./node_modules/.binlike so:@Explorare commented on GitHub (Aug 2, 2021):
I installed the mercury-parser again globally this time and it is recognized. But with no luck on the rest.
@pirate commented on GitHub (Aug 4, 2021):
I just noticed you don't have CHROME enabled, which means Singlefile work work anyway (it needs Chrome). Readability and Mercury may be able to work using the wget output, but you also don't have wget installed so all three are pointless. Without either wget or Chrome, ArchiveBox is really not doing much, most of the extractors will fail.
I highly highly recommend running ArchiveBox in docker instead, running it directly on Windows without Docker/WSL/WSL2 is really not supported as you'll run into all kinds of dependency problems such as what you encountered here.
I'm going to close this as
wontfixbecause I don't want to set a precedent of supporting ArchiveBox directly on Windows, or I will open pandoras box and have far too many support tickets given its lackluster compatibility right now. Docker on Windows is the only Windows install method I'm willing to provide support for.Sorry for the hassle, but I promise in the long run you will have fewer issues and a more secure setup running it in Docker vs without.