Package Details: dogecoin-qt 1.14.0-1

Git Clone URL: (read-only)
Package Base: dogecoin-qt
Description: Cryptocurrency
Upstream URL:
Licenses: MIT
Provides: dogecoin-qt
Submitter: Thermi
Maintainer: Thermi
Last Packager: Thermi
Votes: 46
Popularity: 0.000441
First Submitted: 2014-02-01 16:57
Last Updated: 2019-07-12 23:46

Pinned Comments

Thermi commented on 2017-06-20 10:30

New version with a (hopefully) working dogecoin-qt version that links against openssl-1.0. Please give feedback!

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

Thermi commented on 2017-06-11 23:42


Because, as is mentioned in the pinned comment, dogecoin-qt does not build with openssl 1.1.0.e, which is the current version of openssl for Arch Linux. To make it build, you'll have to patch the dogecoin-qt source code. Sure, you can bypass the checksum and fix it, but that does not fix the errors in the source code.

Fornax commented on 2017-06-11 19:40

Can I do anything to help get this package working again? I haven't been able to access my money for over a week and it's frustrating.

Can't you just update the checksum? I'm still getting "ERROR: One or more files did not pass the validity check!".

Thermi commented on 2017-06-06 21:32

Github regenerated the tarball, that's why the checksum changed. It still doesn't build with openssl 1.1.0e, because some function names changed.

libcg commented on 2017-06-04 09:22

Prepending to ./configure the following line fixed the build for me:

CFLAGS+=" -I/usr/include/openssl-1.0" CPPFLAGS+=" -I/usr/include/openssl-1.0" LDFLAGS+=" -L/usr/lib/openssl-1.0"

Also @Thermi it looks like the shasum issue is caused by Github regenerating the tarball.

libcg commented on 2017-06-04 09:06

@Thermi: I'm not sure what happened, but comparing the contents of the tarball with the matching git commit doesn't show any difference. Would it be possible that someone rewrote the whole git history? That would be extremely unlikely...

Fornax commented on 2017-06-02 18:34

Hey, thanks for maintaining this package.

It worked great for a while, but since a few weeks it doesn't start anymore. Turns out the boost libs on my system were automatically updated to version 1.64, but dogecoin is still looking for version 1.63. Symlinking them usually works, but that's a pretty silly workaround. Could dogecoin-qt please be recompiled with boost 1.64?

Here's the full output for the curious:
dogecoin-qt: error while loading shared libraries: cannot open shared object file: No such file or directory

I tried reinstalling the program, but now I can't install it anymore:

==> Validating source files with sha256sums...
v1.10.0.tar.gz ... FAILED
dogecoin.desktop ... Passed
==> ERROR: One or more files did not pass the validity check!

Would be great if you could patch this soon.

Thermi commented on 2017-05-26 23:40


Thermi commented on 2017-05-25 14:58

@erb I asked why the checksum changed, because that is not supposed to happen. The checksum was right for a very long time after the release. Release tarballs are not supposed to change. Do not build or install this package until the reason is cleared.

EDIT: Besides, the package doesn't build at all with openssl 1.1.0.e.

erb commented on 2017-05-25 14:57

If anyone is wondering, the sha256sum of the v1.10.0.tar.gz is e392f4142819fdab313ba921af53fdbd2cf6ee8965d237d0cb5cda8a52c97084.

Raansu commented on 2017-05-22 05:50

The sha256sum of the source tarball should be updated.