all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: amirouche@hyper.dev
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 35518@debbugs.gnu.org
Subject: [bug#35518] gnu: guile-pfds bugfix
Date: Wed, 01 May 2019 12:58:03 +0200	[thread overview]
Message-ID: <3e5e53e5a9abd81fb7f58a63d890b065@hyper.dev> (raw)
In-Reply-To: <87imuuvgpd.fsf@elephly.net>

On 2019-05-01 08:20, Ricardo Wurmus wrote:
> Hi amirouche,
> 
>> I am not sure how to handle this case.
> 
> Is this fix available upstream?

It is not available upstream. The maintainer is unresponsive for several 
months (years?).

> Has this been reported upstream?

Yes at https://github.com/ijp/pfds/pull/6

> In either case there should be a note about the upstream status of this
> change.

I think pfds would need a new maintainer.

> I’d prefer not to add a patch file here but to add a build phase after
> unpack that uses substitute* to patch the file.

Ok I will do that.

  reply	other threads:[~2019-05-01 10:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01  0:52 [bug#35518] gnu: guile-pfds bugfix amirouche
2019-05-01  3:42 ` [bug#35518] (no subject) amirouche
2019-05-06 11:09   ` Ricardo Wurmus
2019-05-06 12:42     ` [bug#35518] [PATCH] fix guile-pfds bug amirouche
2019-05-06 13:10       ` Ricardo Wurmus
2021-07-14  2:43       ` bug#35518: gnu: guile-pfds bugfix Maxim Cournoyer
2019-05-01  6:20 ` [bug#35518] " Ricardo Wurmus
2019-05-01 10:58   ` amirouche [this message]
2019-05-01 11:46   ` amirouche
2019-05-06  8:05     ` Ludovic Courtès
2019-05-06  8:05     ` Ludovic Courtès
2019-06-26  1:47 ` [bug#35518] upstream unresponsive Amirouche
2020-06-06  3:33 ` [bug#35518] guile-pfds hamts fix Jack Hill

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=3e5e53e5a9abd81fb7f58a63d890b065@hyper.dev \
    --to=amirouche@hyper.dev \
    --cc=35518@debbugs.gnu.org \
    --cc=rekado@elephly.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 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.