All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libgpg-error: bump to version 1.21
Date: Sat, 16 Apr 2016 09:06:38 +0200	[thread overview]
Message-ID: <1460790398.8200.4.camel@embedded.rocks> (raw)
In-Reply-To: <57113DC8.7090509@zacarias.com.ar>

On Fr, 2016-04-15 at 16:15 -0300, Gustavo Zacarias wrote:
> On 20/03/16 17:28, J?rg Krause wrote:
> 
> > Hi Arnout,
> > 
> > I'm really sorry for the long delay. This patch has lost my
> > attention...
> > 
> > > ? It's mind-boggling that "a small library with error codes"
> > > needs
> > > architecture-specific handling...
> > 
> > It is indeed! I had a closer look and I think the whole magic
> > libgpg-
> > error does for retrieving the initialization of a lock object can
> > be
> > done without all the target configuration files. I'll contact the
> > maintainers about this issue.
> > 
> > Best regards
> > J?rg Krause
> 
> Hi all.
> A small attention note: this is now required for the recently
> released?
> libgcrypt 1.7.0 since it depends on gpg-error >= 1.13 (which uses
> the?
> new mutex code IIRC which causes this headache).
> It's not a high-priority since it's just new feature, no security
> bug?
> fixes... yet ;)
> Regards.
> 

I started a discussion with upstream [1] about this issue and proposed
a patch [2] to fix the architucture dependends (which is none in my
mind).

Let's hope we can find a suitable solution...

[1]?http://comments.gmane.org/gmane.comp.encryption.gpg.devel/21150
[2]?http://comments.gmane.org/gmane.comp.encryption.gpg.devel/21176

  reply	other threads:[~2016-04-16  7:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-02 19:28 [Buildroot] [PATCH 1/1] package/libgpg-error: bump to version 1.21 Jörg Krause
2016-01-02 22:59 ` Arnout Vandecappelle
2016-03-20 20:28   ` Jörg Krause
2016-04-15 19:15     ` Gustavo Zacarias
2016-04-16  7:06       ` Jörg Krause [this message]
2016-07-03 22:07         ` Maxime Hadjinlian

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=1460790398.8200.4.camel@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --cc=buildroot@busybox.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.
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.