Package Details: daedalus 0.12.0-1

Git Clone URL: https://aur.archlinux.org/daedalus.git (read-only, click to copy)
Package Base: daedalus
Description: Cryptocurrency wallet
Upstream URL: https://github.com/input-output-hk/daedalus
Licenses: MIT
Submitter: tensor5
Maintainer: cga
Last Packager: tensor5
Votes: 10
Popularity: 1.24
First Submitted: 2017-12-02 17:23
Last Updated: 2018-12-30 14:40

Pinned Comments

cga commented on 2020-12-05 14:48

Been trying to find a way to package Daedalus, but you are better off using the official .bin script for now. Maintaining ownership of the package, hoping for proper Linux support by IOG. Right now they use NixOS and it's very messy to package.

Refer to this for now: https://daedaluswallet.io/

Latest Comments

« First ‹ Previous 1 2 3

asbachb commented on 2018-01-08 22:57

I used node version management to install a specific version of node which installed node binaries to /usr/local/lib/node_module instead of /usr/lib/node_modules so npm could not link the package.

For now I created a symlink and the package compiles quite fine.

asbachb commented on 2018-01-03 22:28

Build fails for me:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'link',
1 verbose cli   'daedalus-client-api' ]
2 info using npm@5.5.1
3 info using node@v8.9.3
4 verbose npm-session 199dc892d7b1b887
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 http fetch GET 404 https://registry.npmjs.org/daedalus-client-api 1529ms
8 silly fetchPackageMetaData error for daedalus-client-api@latest 404 Not Found: daedalus-client-api@latest
9 verbose stack Error: 404 Not Found: daedalus-client-api@latest
9 verbose stack     at fetch.then.res (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/fetch.js:42:19)
9 verbose stack     at tryCatcher (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
9 verbose stack     at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:512:31)
9 verbose stack     at Promise._settlePromise (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:569:18)
9 verbose stack     at Promise._settlePromise0 (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:614:10)
9 verbose stack     at Promise._settlePromises (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:693:18)
9 verbose stack     at Async._drainQueue (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:133:16)
9 verbose stack     at Async._drainQueues (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:143:10)
9 verbose stack     at Immediate.Async.drainQueues (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:17:14)
9 verbose stack     at runCallback (timers.js:789:20)
9 verbose stack     at tryOnImmediate (timers.js:751:5)
9 verbose stack     at processImmediate [as _immediateCallback] (timers.js:722:5)
10 verbose cwd /home/asbachb/.cache/pacaur/daedalus/src/daedalus
11 verbose Linux 4.14.10-1-ARCH
12 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "link" "daedalus-client-api"
13 verbose node v8.9.3
14 verbose npm  v5.5.1
15 error code E404
16 error 404 Not Found: daedalus-client-api@latest
17 verbose exit [ 1, true ]

gwpl commented on 2017-12-18 18:32

@codybonney you are right! The first error message is

[19:31:16:0282] [error] Error while loading ca.crt: Error: ENOENT: no such file or directory, open '/home/gwpl/download/temp2del/input-output-hk-github/daedalus/tls/ca/ca.crt'

Here is suggestion how to fix it that may be considered to be integrated into PKGBUILD : https://github.com/input-output-hk/daedalus/issues/522#issuecomment-338822000

gwpl commented on 2017-12-18 11:13

Regarding "Connecting to network..." issue:

I looks like daedalus tries to connect to 127.0.0.1:8090. I've only found notes with advices to run ./scripts/build/cardano-sl.sh or ./connect-to-mainnet, however they are not provided in packages (however they are in cardano-sl github repository):

$ pacman -Ql daedalus cardano-sl | grep 'connect\|cardano-sl.sh' | wc -l
0

returns nothing. Therefore, how to run deadalus to get out from "Connecting to network..." stage? (also raised topic here: https://forum.cardanohub.org/t/linux-daedalus-connecting-to-the-network-archlinux/3148 also here https://github.com/input-output-hk/daedalus/issues/608 )

Shouldn't those bash scripts be added to packages if are required?

codybonney commented on 2017-12-17 17:43

Looks like daedalus, when launched, is looking for a certificate at:

$(pwd)/tls/ca/ca.crt

I see that this package creates one at:

src/daedalus/tls/ca.crt

gwpl commented on 2017-12-17 11:44

Could you please provide reference from where have you taken 702353E0F7E48EDB ? I.e. how one can easily verify to whom does it belong to ?

Hyperfocus commented on 2017-12-10 12:09

On Manjaro linux the package is missing the rocksdb dependency and received a compilation error but it's probably due to the code itself

tensor5 commented on 2017-12-07 14:16

Hi Gio,

You need to add the public key for the ncurses package. Run:

gpg --keyserver keys.gnupg.net --recv-keys 702353E0F7E48EDB

and then try again building daedalus. Let me know!

Gio commented on 2017-12-07 02:12

HI.

Thank You for adding this. Unfortunately, when I try to install it (compiled with Pamac) I get:

ncurses-6.0-20170902.tgz ... FAILED (unknown public key 702353E0F7E48EDB)

Thank you.