unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Guillaume LE VAILLANT <glv@posteo.net>
To: swedebugia <swedebugia@riseup.net>
Cc: 36258@debbugs.gnu.org
Subject: [bug#36258] [PATCH 1/2] gnu: monero: Update to 0.14.1.0.
Date: Mon, 24 Jun 2019 11:54:26 +0200	[thread overview]
Message-ID: <87y31rtijx.fsf@yamatai> (raw)
In-Reply-To: <9abcc53c-1a07-d3b3-2b9f-1571328c7414@riseup.net>


swedebugia a écrit :

> Tests completed succesfully. I saw this note:
>
> +                       ;; TODO: Find why portability_wallet test fails
> +                       ;; Maybe the Boost version used to create the test
> +                       ;; wallet and the current Boost version are not
> +                       ;; completely compatible?
> +                       "Serialization.portability_wallet"
> +                       "is_hdd.linux_os_root")
>
> Did you report this upstream?
> Could you include the failed test also (commented below the comment)
>
> Otherwise LGTM :)
>
> PS: I started working on Aeon (fork of monero) since they are very similar it
> should be "easy" to package now that you got monero working again.

I'm not entirely sure why the "Serialization.portability_wallet" test
fails. It might not be related to compatibility between Boost versions,
because compiling with the same Boost version in two different ways
gives different results.

When I compile using 'guix build monero', the test fails.
---
/tmp/guix-build-monero-0.14.1.0.drv-0/monero-0.14.1.0-checkout/tests/unit_tests/serialization.cpp:633: Failure
Value of: r
  Actual: false
Expected: true
---

When I compile by hand using 'guix environment --pure monero', the test
passes.

  reply	other threads:[~2019-06-24  9:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17  8:44 [bug#36258] [PATCH 1/2] gnu: monero: Update to 0.14.1.0 Guillaume LE VAILLANT
2019-06-17  8:44 ` [bug#36259] [PATCH 2/2] gnu: monero-gui: " Guillaume LE VAILLANT
2019-06-26 12:08   ` Guillaume LE VAILLANT
2019-06-26 22:55     ` swedebugia
2019-07-03 10:07     ` bug#36259: " Ludovic Courtès
2019-06-22 20:38 ` [bug#36258] [PATCH 1/2] gnu: monero: " swedebugia
2019-06-22 22:17   ` Guillaume LE VAILLANT
2019-06-23 11:31     ` swedebugia
2019-06-23 12:53       ` Guillaume LE VAILLANT
2019-06-23 13:18         ` swedebugia
2019-06-24  6:20           ` swedebugia
2019-06-24  9:54             ` Guillaume LE VAILLANT [this message]
2019-06-25 10:07               ` Guillaume LE VAILLANT
2019-06-25 11:32                 ` swedebugia
2019-07-03 10:06                   ` bug#36258: " Ludovic Courtès
2019-07-14 11:11                     ` [bug#36258] " swedebugia
2019-07-14 11:51                       ` Guillaume Le Vaillant
2019-07-14 13:32                         ` Ludovic Courtès
2019-07-14 14:55                           ` swedebugia
2019-07-14 16:13                             ` Guillaume Le Vaillant
2019-07-15 10:50                               ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y31rtijx.fsf@yamatai \
    --to=glv@posteo.net \
    --cc=36258@debbugs.gnu.org \
    --cc=swedebugia@riseup.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).