Package Details: mist-git 0.8.2.r6.g18fa764-1

Git Clone URL: https://aur.archlinux.org/mist-git.git (read-only, click to copy)
Package Base: mist-git
Description: Mist dapp browser and Ethereum wallet (git version).
Upstream URL: https://github.com/ethereum/mist
Licenses: GPL
Conflicts: libnode, libnode-git, mist
Provides: libnode, mist
Submitter: 5chdn
Maintainer: None
Last Packager: 5chdn
Votes: 6
Popularity: 0.000000
First Submitted: 2016-01-20 10:25
Last Updated: 2016-08-25 08:02

Latest Comments

« First ‹ Previous 1 2

5chdn commented on 2016-03-13 08:37

here you go, give it a try. and thanks, i could use some help, i'm not the most experienced install-scripter ;-)

cameel commented on 2016-03-12 22:15

Co-maintainer? Is this even possible on AUR?

The answer is... maybe. It's a bit early to say if I'll keep long term interest in this package. I've just started using it very recently and for the time being I can't even get mist to create an ETH account (https://github.com/ethereum/mist/issues/248) :) Actually I'm only trying out the git version because I wanted to see if the issue has been fixed in master. But as long as I'm around I can try to help in maintaining it in one way or another...

5chdn commented on 2016-03-12 19:44

"pkgver to 0.5.2" ... that is a mess, but it is caused upstream. i will push fixes in a minute. do you wish to become co-maintainer?

cameel commented on 2016-03-12 19:23

Another issue with the package is that building it affects user's home directory. Namely ~/.meteor gets filled with about 1 GB of mostly JS code. Apparently meteor-js copies it from /opt/meteor the first time it's used. This data does not seem to be required by mist after it's been built.

Apart from being an annoyance when you're short on disk space, I suspect it might influence building process in unexpected ways if the user does develop something with meteor-js. Of if he has already built another package (or even an earlier version of mist-git) on the same machine. In other words, the build environment is not isolated and builds won't be repeatable.

Making PKGBUILD or post_install() delete ~/.meteor after the build is of course not a good idea. It might have been already present. It would be best if the PKGBUILD configured the package is such a way that the meteor stuff lands somewhere in the build directory instead. Any suggestions on how to do that?

cameel commented on 2016-03-12 18:40

Also, same problem as with https://aur.archlinux.org/packages/mist/ The file /usr/share/mist/resources/node/geth/geth is not marked as executable.

For anyone having probems starting the wallet, until the PKGBUILD is fixed, you have to add this line at the end of package() to make it work:

chmod 755 "${pkgdir}/usr/share/${pkgname}/resources/node/geth/geth"

Or, if you want to use geth-git, remove the file and make it a symlink to /usr/bin/geth

cameel commented on 2016-03-12 18:38

Package fails to build for me:

==> Entering fakeroot environment...
==> Starting package()...
-> Installing Mist...
cp: cannot stat '/tmp/pacaurtmp-cameel/mist-git/src/mist-git/dist_wallet/Ethereum-Wallet-linux64-0-5-1/.': No such file or directory
==> ERROR: A failure occurred in package().
Aborting...


Ethereum-Wallet-linux64-0-5-1 is missing but there's Ethereum-Wallet-linux64-0-5-2 instead. Bumping pkgver to 0.5.2 fixes the problem.