From: Vivien Kraus via Guix-patches via <guix-patches@gnu.org>
To: 66052@debbugs.gnu.org
Cc: liliana.prikler@gmail.com, maxim.cournoyer@gmail.com,
rg@raghavgururajan.name
Subject: [bug#66052] [PATCH gnome-team 0/1] Update tracker, and ignore i686 missing tests
Date: Sun, 17 Sep 2023 14:59:08 +0200 [thread overview]
Message-ID: <cover.1694955548.git.vivien@planete-kraus.eu> (raw)
Dear guix,
tracker does not build on i686-linux. There are 2 failing test cases: parsing
a double does not give the same result as the compiler implementation of a
literal parser, and the far away dates are off (I suspect a 32-bit time_t).
Anyway, I relaxed the former so that it is equal up to 1e-12, and I disabled
the latter.
What do you think?
Best regards,
Vivien
Vivien Kraus (1):
gnu: tracker: Update to 3.6.0.
gnu/packages/gnome.scm | 20 ++++++++++++++++++--
1 file changed, 18 insertions(+), 2 deletions(-)
base-commit: e9ff5d51e3297089e66c124195e1f1b42dbded65
--
2.41.0
next reply other threads:[~2023-09-17 13:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-17 12:59 Vivien Kraus via Guix-patches via [this message]
2023-09-17 11:29 ` [bug#66052] [PATCH gnome-team 1/1] gnu: tracker: Update to 3.6.0 Vivien Kraus via Guix-patches via
2023-09-17 13:27 ` Liliana Marie Prikler
2023-09-17 11:29 ` [bug#66052] [PATCH gnome-team v2] " Vivien Kraus via Guix-patches via
2023-09-17 16:22 ` Liliana Marie Prikler
2023-09-17 11:29 ` [bug#66052] [PATCH gnome-team v3] " Vivien Kraus via Guix-patches via
2023-09-17 18:55 ` Liliana Marie Prikler
2023-09-17 11:29 ` [bug#66052] [PATCH gnome-team v4] " Vivien Kraus via Guix-patches via
2023-09-17 19:51 ` Liliana Marie Prikler
2023-09-17 11:29 ` [bug#66052] [PATCH gnome-team v5] " Vivien Kraus via Guix-patches via
2023-09-18 17:00 ` Liliana Marie Prikler
2023-09-24 10:01 ` bug#66052: " Liliana Marie Prikler
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=cover.1694955548.git.vivien@planete-kraus.eu \
--to=guix-patches@gnu.org \
--cc=66052@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=maxim.cournoyer@gmail.com \
--cc=rg@raghavgururajan.name \
--cc=vivien@planete-kraus.eu \
/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).