Package Details: monero 0.13.0.3-1

Git Clone URL: https://aur.archlinux.org/monero.git (read-only)
Package Base: monero
Description: Monero: the secure, private, untraceable currency - release version (includes daemon, wallet and miner)
Upstream URL: https://getmonero.org/
Licenses: custom:Cryptonote
Conflicts: bitmonero-git, libmonero-wallet-git
Provides: libmonero-wallet, monero
Submitter: anonimal
Maintainer: anonimal
Last Packager: anonimal
Votes: 70
Popularity: 2.457723
First Submitted: 2016-09-21 06:24
Last Updated: 2018-10-17 19:37

Latest Comments

1 2 3 4 5 Next › Last »

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

0.13.0.3 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

pkgbase=('monero')

to

pkgbase="monero"

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.

redfish commented on 2018-07-22 03:06

Just noticed that unit_tests are disabled here. I have them running in monero-git, all pass except those DNS related ones and ringdb.not_found. Reporting in case you wish to re-enable the unit_tests here as well.

anonimal commented on 2018-07-16 03:11

@growler I'd suggest to not use pacaur and instead use yaourt (I use, without issue). You can also $ git clone https://aur.archlinux.org/monero.git && cd monero && makepkg -sci

growler commented on 2018-07-12 16:38

Still can't install this normally, any ideas?

growler@beast:~|⇒ pacaur -S monero libmonero-wallet :: Packages monero libmonero-wallet not found in repositories, trying AUR... :: resolving dependencies... :: looking for inter-conflicts...

AUR Packages (2) libmonero-wallet-0.12.3.0-1 monero-0.12.3.0-1

:: Proceed with installation? [Y/n] :: Retrieving package(s)... Cloning into 'monero'... remote: Counting objects: 6, done. remote: Compressing objects: 100% (6/6), done. remote: Total 6 (delta 0), reused 2 (delta 0) Unpacking objects: 100% (6/6), done. :: View monero PKGBUILD? [Y/n] n :: View monero.install script? [Y/n] n :: Checking libmonero-wallet,monero integrity... ==> Making package: monero 0.12.3.0-1 (Thu 12 Jul 2018 17:36:46 BST) ==> Retrieving sources... ==> ERROR: /home/growler/.tmp/pacaur/monero/monero is not a clone of https://github.com/monero-project/monero Aborting... :: Preparing libmonero-wallet,monero... ==> Making package: monero 0.12.3.0-1 (Thu 12 Jul 2018 17:36:48 BST) ==> WARNING: Skipping dependency checks. ==> Retrieving sources... ==> ERROR: /home/growler/.tmp/pacaur/monero/monero is not a clone of https://github.com/monero-project/monero Aborting... :: failed to verify integrity or prepare libmonero-wallet,monero package :: failed to verify integrity or prepare libmonero-wallet,monero package

anonimal commented on 2018-06-12 21:54

Yes, thanks @kragol, I'll apply the patch.

From the manpage:

When running update (only effective with the checkout procedure), throw away local changes in submodules when switching to a different commit; and always run a checkout operation in the submodule, even if the commit listed in the index of the containing repository matches the commit checked out in the submodule.

kragol commented on 2018-06-12 09:09

The third patch seems to be causing trouble if for whatever reason the build process is interrupted.

After an interruption, running makepkg again results in an error (ERROR: A failure occurred in prepare()) which is due to the third patch that is already applied to the miniupnp submodule. The problem is that when running makepkg a second time, it resets the monero repo to its original state before applying the patch again, but it does not reset the submodules to their originial states. Hence, makepkg fails when trying to patch the miniupnp submodule because it is already patched.

A quick workaround seems to be to add the option --force to the submodule update command in prepare()

git -C "${pkgname}" submodule update --init --recursive --force