all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 53434@debbugs.gnu.org,
	Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Subject: [bug#53434] Patches to unbreak many i686 packages
Date: Wed, 16 Feb 2022 17:38:33 +0100	[thread overview]
Message-ID: <d1829b68d6a308afa17396920efa3df6267c2133.camel@telenet.be> (raw)
In-Reply-To: <8735kiyl1q.fsf_-_@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]

Ludovic Courtès schreef op wo 16-02-2022 om 14:53 [+0100]:
> Hi,
> 
> Maxime Devos <maximedevos@telenet.be> skribis:
> 
> > Denis 'GNUtoo' Carikli schreef op za 22-01-2022 om 03:59 [+0100]:
> > > * gnu/packages/gnome.scm (upower)[arguments]<#:tests?>:
> > 
> > Reported upstream at
> > <https://gitlab.freedesktop.org/upower/upower/-/issues/167>.

> However, it turns out there upower builds fine currently:
> [...]
> Did the problem sort itself?

The test failure was somewhat non-deterministic.

> This reminds me that we had to build with ‘-fexcess-
> precision=standard’
> many packages on i686 since the switch to GCC 10.  Would it help?

Possibly, but perhaps backporting the upstream fix that largely avoids
floating-point arithmetic would be better?
(See
<https://gitlab.freedesktop.org/upower/upower/-/merge_requests/101>.)

Also, looks like there's a '0.99.15' release now
(https://gitlab.freedesktop.org/upower/upower/-/tree/v0.99.15),
so perhaps we could just update upower?

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-02-16 17:07 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-22  2:54 [bug#53434] Patches to unbreak many i686 packages Denis 'GNUtoo' Carikli
2022-01-22  2:59 ` [bug#53434] [PATCH 01/11] gnu: gtk-vnc: Remove dependency on GJS on non-x86_64 Denis 'GNUtoo' Carikli
2022-01-22  2:59   ` [bug#53434] [PATCH 02/11] gnu: gtk-vnc: Build with correct librsvg Denis 'GNUtoo' Carikli
2022-01-22  2:59   ` [bug#53434] [PATCH 03/11] gnu: gnome-settings-daemon: " Denis 'GNUtoo' Carikli
2022-01-22  2:59   ` [bug#53434] [PATCH 04/11] gnu: vlc: " Denis 'GNUtoo' Carikli
2022-01-22  2:59   ` [bug#53434] [PATCH 05/11] gnu: python-dbusmock: Disable tests on i686 Denis 'GNUtoo' Carikli
2022-01-22  2:59   ` [bug#53434] [PATCH 06/11] gnu: node: " Denis 'GNUtoo' Carikli
2022-01-22  2:59   ` [bug#53434] [PATCH 07/11] gnu: guix: " Denis 'GNUtoo' Carikli
2022-01-23 21:35     ` [bug#53434] Patches to unbreak many i686 packages Ludovic Courtès
2022-01-22  2:59   ` [bug#53434] [PATCH 08/11] gnu: mesa: Disable tests on i686 Denis 'GNUtoo' Carikli
2022-01-26  3:27     ` Denis 'GNUtoo' Carikli
2022-01-22  2:59   ` [bug#53434] [PATCH 09/11] gnu: imath: " Denis 'GNUtoo' Carikli
2022-01-26  1:06     ` Denis 'GNUtoo' Carikli
2022-01-26  3:17       ` Leo Famulari
2022-01-26  3:44       ` Leo Famulari
2022-01-22  2:59   ` [bug#53434] [PATCH 10/11] gnu: openexr: " Denis 'GNUtoo' Carikli
2022-01-22  2:59   ` [bug#53434] [PATCH 11/11] gnu: upower: " Denis 'GNUtoo' Carikli
2022-01-24 10:43     ` Maxime Devos
2022-02-16 13:53       ` [bug#53434] Patches to unbreak many i686 packages Ludovic Courtès
2022-02-16 16:38         ` Maxime Devos [this message]
2022-02-17 10:40           ` Ludovic Courtès
2022-02-17 20:30             ` Maxime Devos
2022-02-18  7:50             ` Maxime Devos
2022-02-18 13:43               ` Ludovic Courtès
2022-04-23 19:54         ` Denis 'GNUtoo' Carikli
2022-04-28 21:35           ` bug#53434: " Ludovic Courtès
2022-01-22 12:38 ` [bug#53434] " Maxime Devos
2022-01-22 16:49   ` Denis 'GNUtoo' Carikli
2022-01-22 19:19     ` Denis 'GNUtoo' Carikli
2022-01-22 19:32       ` Maxime Devos
2022-01-23 21:32         ` Ludovic Courtès
2022-01-22 19:34       ` Maxime Devos
2022-01-23 22:39 ` 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

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

  git send-email \
    --in-reply-to=d1829b68d6a308afa17396920efa3df6267c2133.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=53434@debbugs.gnu.org \
    --cc=GNUtoo@cyberdimension.org \
    --cc=ludo@gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.