mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 09:06:02 +03:00
[GH-ISSUE #232] "No such file or directory" on favicon in virtualenv #1668
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#1668
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 @anarcat on GitHub (May 6, 2019).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/232
Describe the bug
I installed archivebox from pip (yaaay!) and couldn't do the original setup, which failed at the
archivebox initstep with:FileNotFoundError: [Errno 2] No such file or directory: '/home/anarcat/.virtualenvs/archivebox/lib/python3.7/site-packages/archivebox/themes/legacy/favicon.ico'
Steps to reproduce
virtualenv --python=python3 ~/.virtualenvs/archivebox~/.virtualenvs/archivebox/pip3 install archivebox, which correctly installed archivebox 0.4.1archivebox initwhich crashed with the aforementioned error messageScreenshots or log output
Software versions
Workaround
Copy over the theme manually from the 0.4.1 tree:
@anarcat commented on GitHub (May 6, 2019):
sorry, the first version of this was just the template because i mistakenly hit "enter" before completing the report... great UI github. :)
@pirate commented on GitHub (May 6, 2019):
Ah lol I should never have pushed v0.4.1 to production PyPi, I was too eager and I was just trying to test the packaging setup. None of the versions in PyPi are ready for users. For now, just install from the django branch with
pip install -e ..I'm closing this for now because it was a Manifest.ini issue that I fixed a while back already, it's just a stale test release in PyPi that will be replaced when I publish the real v0.4.
@anarcat commented on GitHub (May 6, 2019):
i think it's fine you pushed it to pypi, it made it possible for me to install it, but yeah - there are bugs. :) i would say that you should push that branch out to pypi already to fix that bug, even! ;)