Search Criteria
Package Details: chia-git 1:1.3.5.r1165.gdd4d7d031-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/chia-git.git (read-only, click to copy) |
---|---|
Package Base: | chia-git |
Description: | A new blockchain and smart transaction platform that is easier to use, more efficient, and secure. - Latest git commit, provides GUI |
Upstream URL: | https://www.chia.net/ |
Licenses: | Apache |
Conflicts: | chia |
Provides: | chia |
Submitter: | BenTheTechGuy |
Maintainer: | None |
Last Packager: | BenTheTechGuy |
Votes: | 3 |
Popularity: | 0.000000 |
First Submitted: | 2020-11-01 05:57 (UTC) |
Last Updated: | 2022-11-21 02:32 (UTC) |
Dependencies (5)
- chia-cli-gitAUR
- electron (electron-binAUR)
- git (git-gitAUR, git-glAUR) (make)
- nodejs (nodejs-lts-fermiumAUR, nodejs-gitAUR, python-nodejs-wheelAUR, nodejs-lts-hydrogen, nodejs-lts-iron) (make)
- npm (corepackerAUR, python-nodejs-wheelAUR) (make)
Latest Comments
1 2 Next › Last »
GrumpyMonk commented on 2021-07-22 14:46 (UTC)
ack, thanks
BenTheTechGuy commented on 2021-07-18 21:06 (UTC)
Right now I'm working on a big change that installs the packages right to the system with no need for a virtual env or pip. In the meantime I'll revert that commit so the package still works.
GrumpyMonk commented on 2021-07-17 19:39 (UTC)
Hi, after change https://aur.archlinux.org/cgit/aur.git/commit/?h=chia-git&id=cf67fef73269032999e777a9f1aec973a9538b69 (change the way venv is managed) I can’t seem to get chia to start, always fails with PackageNotFoundError: chia-blockchain
A lot of things, including PATH set by activate, and pip -V refer to the src dir.
If I revert to the previous commit, everything is fine.
Any ideas?
BenTheTechGuy commented on 2021-05-18 16:49 (UTC)
The activation command works in scripts as well, your autostart script could just be:
or something similar
<deleted-account> commented on 2021-05-18 16:26 (UTC)
@BenTheTechGuy Thanks for looking into it. I can now use Chia with this package, assuming that I run
source /opt/chia-blockchain/activate
first. Do you know how I could set it up so that chia is available as a regular command, without sourcing anything? If that were the case, it would be easier for me to auto-start upon boot.BenTheTechGuy commented on 2021-05-17 21:00 (UTC)
@trapezestunned @EndlessEden @keybreak @BunchOfAtoms the problem is now fixed! I followed this guide to solve the error present in the previous comment. The latest version of the package should have no issues.
BenTheTechGuy commented on 2021-05-15 17:47 (UTC) (edited on 2021-05-15 17:59 (UTC) by BenTheTechGuy)
I have figured out the cause of the issue. Chia's venv points to
$srcdir/chia-blockchain
instead of the correct/opt/chia-blockchain
. So instead of trying to find chia at/opt/chia-blockchain/venv/bin/chia
, it tries to find it at/home/ben/.cache/paru/clone/chia-blockchain/src/chia-blockchain/venv/bin/chia
, or whatever your equivalent directory is. Since paru keeps the source cloned unless you manually delete it, I didn't experience this issue since the directory was still there. However, many AUR helpers delete the srcdir when you're done building the package, so it can't find chia. I'm working on a fix that points it to the right place.However, the fix I came up with of just replacing all occurances of
$srcdir
with/opt
only works partially. Even though it allowschia
to be executed, a new problem pops up trying to run it:I have started a discussion on the GitHub to try and find out the cause and fix.
<deleted-account> commented on 2021-05-14 18:23 (UTC)
@BenTheTechGuy: different guy, but I am having the same problem. None of the commands in the comments let me use chia. The other AUR package chia-bin works fine without having to run any commands, but drags in tons of dependencies I don't need on my headless machine.
BenTheTechGuy commented on 2021-05-06 17:34 (UTC)
Try
source /opt/chia-blockchain/activate
. Does it still have the same issue?1 2 Next › Last »