Package Details: monero

Git Clone URL: (read-only)
Package Base: monero
Description: Monero: the secure, private, untraceable currency - release version (includes daemon, wallet and miner)
Upstream URL:
Licenses: custom:Cryptonote
Conflicts: bitmonero-git, libmonero-wallet-git
Provides: libmonero-wallet, monero
Submitter: anonimal
Maintainer: anonimal
Last Packager: anonimal
Votes: 78
Popularity: 0.560621
First Submitted: 2016-09-21 06:24
Last Updated: 2019-03-07 22:28

Latest Comments

1 2 3 4 5 6 Next › Last »

anonimal commented on 2019-02-22 06:05

No, you are incorrect. Monero is licensed under BSD-3. Cryptonote, as well as several dependencies, are licensed under MIT/X11. It's a mixed license, so what's currently there is fine unless you really need a license array...

es20490446e commented on 2019-02-22 05:36

As seen in:

The license variable should be: license=('MIT')

Although still correct to place a copy of it on: ${pkgdir}/usr/share/licenses/${pkgname}/LICENSE

anonimal commented on 2019-01-22 10:21

I've applied the upstream patch. moneromooo authored that in October. The package should build now.

arcmags commented on 2019-01-17 08:37

Fails to build with latest boost-1.69.0-1.

This patch fixes it:

isch commented on 2018-10-27 15:13 is out:

Fixes this error I'm seeing with wallet:

anonimal commented on 2018-10-17 19:36

@ohheyrighton you'll need to simply rebuild against your current boost version.

@JKAbrams I cannot reproduce with makepkg or yaourt. These two are the standard, sane tools used for AUR. Regardless, the change is harmless.

@Ranguvar yes, but USE_SINGLE_BUILDDIR is not needed here. Do you need it for a particular reason?

Ranguvar commented on 2018-10-16 14:20 available.

USE_SINGLE_BUILDDIR=1 make if you want previous build paths.

JKAbrams commented on 2018-10-15 06:02

==> ERROR: pkgbase should not be an array

Fixed by changing




ohheyrighton commented on 2018-10-06 15:13

Needs update to point to correct libboost file

anonimal commented on 2018-07-26 00:57

Hi @redfish. Thanks for notice. Let's see if more people want them enabled. For the tests that do fail, I'm concerned that people will think that something is wrong and then send a flood of complaints.