unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Andrew Miloradovsky <andrew@interpretmath.pw>,
	Brett Gilio <brettg@posteo.net>
Cc: 38509-done@debbugs.gnu.org
Subject: bug#38509: [PATCH] gnu: libuv: Update to 1.34.0
Date: Tue, 28 Jan 2020 00:20:23 +0100	[thread overview]
Message-ID: <87wo9cqyfc.fsf@devup.no> (raw)
In-Reply-To: <8e8894cf-1ab3-374c-0444-70552ed425f3@interpretmath.pw>

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

Andrew Miloradovsky <andrew@interpretmath.pw> writes:

> Hi Brett,
>
> WRT the differences, it seems to be mostly fixes and refactoring:
>
> - https://github.com/libuv/libuv/tree/v1.34.0
>
> WRT the failed tests, it is due to treating EAGAIN as the failure:
>
> - https://github.com/libuv/libuv/issues/2531
>
> Not sure how to properly fix it, fixing the tests themselves is
> non-trivial, and retrying several more times likely won't work either.

/etc/nsswitch.conf does not exist in the build container, which is
probably why the getnameinfo tests fail.  Could you submit a patch for
Guix that disables those, and enables the rest?

Meanwhile I'm closing this issue, as we have the latest LibUV on the
'core-updates' branch.

By the way, if you need a newer libuv on 'master', you can create a
separate variable as in e.g. ffec356a29a58d97ec34e1152aa3136e78471dc6.

Thanks!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

      reply	other threads:[~2020-01-27 23:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06  8:57 [bug#38509] [PATCH] gnu: libuv: Update to 1.34.0 Andrew Miloradovsky
2019-12-07  1:27 ` Brett Gilio
2019-12-07  1:34   ` Brett Gilio
2019-12-07 13:31     ` Andrew Miloradovsky
2020-01-27 23:20       ` Marius Bakke [this message]

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=87wo9cqyfc.fsf@devup.no \
    --to=mbakke@fastmail.com \
    --cc=38509-done@debbugs.gnu.org \
    --cc=andrew@interpretmath.pw \
    --cc=brettg@posteo.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 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).