all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Olivier Dion <odion@efficios.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 65624@debbugs.gnu.org
Subject: [bug#65624] [PATCH] gnu: liburcu: Update to 0.14.0.
Date: Wed, 06 Sep 2023 10:32:52 -0400	[thread overview]
Message-ID: <87msxztlrf.fsf@laura> (raw)
In-Reply-To: <87bkef99x7.fsf@gmail.com>

On Wed, 06 Sep 2023, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
> Hi,
>
> odion@efficios.com writes:
>
>> From: Olivier Dion <odion@efficios.com>
>>
>> * gnu/packages/datastructures.scm (liburcu): Update to 0.14.0.
>
> According to QA new errors were introduced with this upgrade:
> https://qa.guix.gnu.org/issue/65624.  It looks like it broke at least
> multipath-tools.

There are missing include statements in compilation units of multipath-
tools for <assert.h>.  It probably worked before because Userspace RCU
was including it in its public header file and not anymore.  Therefore,
it is a bug of mutlipath-tools which was fixed in version 0.9.6.

So I see two solutions to this.  Either I back-port the patch to version
0.9.3 or we update multipath-tools to 0.9.6.

Thought? 
-- 
Olivier Dion
EfficiOS Inc.
https://www.efficios.com




  reply	other threads:[~2023-09-06 14:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 15:22 [bug#65624] [PATCH] gnu: liburcu: Update to 0.14.0 odion
2023-09-06  4:56 ` Maxim Cournoyer
2023-09-06 14:32   ` Olivier Dion [this message]
2023-09-06 17:13     ` Maxim Cournoyer
2023-09-07 15:20       ` [bug#65624] [PATCH v2 1/2] gnu: multipath-tools: Update to 0.9.6 odion
2023-09-07 15:20         ` [bug#65624] [PATCH v2 2/2] gnu: liburcu: Update to 0.14.0 odion
2023-09-10 14:48         ` bug#65624: [PATCH v2 1/2] gnu: multipath-tools: Update to 0.9.6 Maxim Cournoyer

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=87msxztlrf.fsf@laura \
    --to=odion@efficios.com \
    --cc=65624@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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.