mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-26 01:26:00 +03:00
[GH-ISSUE #613] Bugfix: ModuleNotFoundError: No module named 'archivebox.vendor.base32_crockford' #1889
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#1889
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 @CalebUsadi on GitHub (Jan 11, 2021).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/613
Describe the bug
Since updating from 0.4.24-1 to 0.5.3-1, whenever I run
archivebox, or an command following it, I get the errorModuleNotFoundError: No module named 'archivebox.vendor.base32_crockford'. I didn't have this issue before, and I'm unable to revert back to the earlier version. May be related to https://github.com/ArchiveBox/ArchiveBox/issues/581.Steps to reproduce
archivebox --version,archivebox init.Screenshots or log output
Software versions
@pirate commented on GitHub (Jan 11, 2021):
Thanks for reporting. Try now, I fixed a problem with the debian packaging process and bumped it to
0.5.3-2(give it 30min to finish the release build).@CalebUsadi commented on GitHub (Jan 11, 2021):
Thank you! Trying to update with
aptdidn't yet give me an update. In retrospect I realized that I had addedppa:archivebox/archiveboxto myaptsources instead of just using the recommended installation method, can't find in the docs why I might have done that. I uninstalled archivebox withaptand reinstalled withpython3 -m pip install --upgrade archivebox. Worked perfectly.@sistein commented on GitHub (Feb 7, 2021):
Any expectations when 0.5.3-2 will be available via apt?
I would prefer to change to the more simple apt installation and 0.5.3-1 is still delivered there.
@pirate commented on GitHub (Feb 8, 2021):
oh we're already on 0.5.4 at this point, just
apt update; apt upgrade archivebox@sistein commented on GitHub (Feb 8, 2021):
@pirate looks like the build is failing => No update via apt upgrade
https://launchpad.net/~archivebox/+archive/ubuntu/archivebox/+build/20962645
@pirate commented on GitHub (Feb 8, 2021):
Looks like Debian changed the build tool they use on their servers from dh-python to pybuild, causing the unittest discovery behavior to change :(
You can install via
pipordpkgfor now until I fix it.@pirate commented on GitHub (Feb 9, 2021):
Build is passing, try now: https://launchpad.net/~archivebox/+archive/ubuntu/archivebox/ (
v0.5.6)