all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kaelyn <kaelyn.alexi@protonmail.com>
To: Andreas Enge <andreas@enge.fr>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	Simon Tournier <zimon.toutoune@gmail.com>,
	guix-devel <guix-devel@gnu.org>
Subject: Re: wget (was Re: i686 core-updates failure.)
Date: Sat, 15 Apr 2023 16:37:29 +0000	[thread overview]
Message-ID: <Hl8Te_UFSGJsUjfwWOK6z70f453wa_Um-g-VGqrdkbWQrgGc_hpxGsi6HOO8B_-P7tLsEcGWLC4lE5lZX9mdZebLW5GhQV3R45dMShzK1E4=@protonmail.com> (raw)
In-Reply-To: <ZDp/zzS0GGAs9O04@jurong>

Hi,

------- Original Message -------
On Saturday, April 15th, 2023 at 10:43 AM, Andreas Enge <andreas@enge.fr> wrote:

> 
> Am Fri, Apr 14, 2023 at 08:51:18PM -0400 schrieb Maxim Cournoyer:
> 
> > None, but are there wget uptsream reports about the problem?
> 
> 
> I do not see anything at
> https://gitlab.com/gnuwget/wget
> 
> Andreas

Doing a search of the error message, I just found https://savannah.gnu.org/bugs/?62110; the subject is about the HSTS tests being broken 32-bit big endian devices, but comment #3 mentions the tests failing on i686, with the same error we are seeing. It looks like https://gitlab.com/gnuwget/wget/-/merge_requests/31 was merged to fix the issue about a month after 1.21.3 was released (I haven't tested yet since the package definition downloads a release tarball instead of building from git).

Cheers,
Kaelyn


  reply	other threads:[~2023-04-15 16:38 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 16:11 i686 core-updates failure Kaelyn
2023-04-12 21:05 ` Josselin Poiret
2023-04-12 21:31 ` Andreas Enge
2023-04-13  4:37   ` Kaelyn
2023-04-13 16:25     ` Andreas Enge
2023-04-14  8:28       ` Andreas Enge
2023-04-14 20:05         ` Kaelyn
2023-04-15 11:20           ` python-pytest on core-updates (was: i686 core-updates failure.) Andreas Enge
2023-04-15 11:32             ` python-pytest on core-updates Andreas Enge
2023-04-15 14:08               ` [PATCH core-updates] gnu: python-pytest: Fix failing test_raising_repr Josselin Poiret
2023-04-15 16:14                 ` Kaelyn
2023-04-15 19:59                 ` Andreas Enge
2023-04-15 20:47                   ` Andreas Enge
2023-04-15 20:49             ` python-pytest on core-updates (was: i686 core-updates failure.) Andreas Enge
2023-04-13  9:18 ` i686 core-updates failure Simon Tournier
2023-04-13 13:23 ` jgart
2023-04-13 13:43   ` Andreas Enge
2023-04-14 15:12     ` Csepp
2023-04-14 16:58       ` Simon Tournier
2023-04-14 17:30         ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-04-13 15:31   ` Simon Tournier
2023-04-13 16:21     ` Simon Tournier
2023-04-13 15:47   ` Ricardo Wurmus
2023-04-13 16:15     ` Greg Hogan
2023-04-13 16:39     ` Simon Tournier
2023-04-13 16:47       ` Ricardo Wurmus
2023-04-13 20:02       ` Lars-Dominik Braun
2023-04-13 20:15         ` Simon Tournier
2023-04-13 20:45           ` Andreas Enge
2023-04-13 20:57             ` Simon Tournier
2023-04-14  8:25               ` Andreas Enge
2023-04-14  9:45                 ` Simon Tournier
2023-04-14 18:16                 ` Andreas Enge
2023-04-14 18:40                   ` Lars-Dominik Braun
2023-04-15  9:48                     ` ghc in core-updates on i686 Andreas Enge
2023-04-14 10:49           ` i686 core-updates failure Lars-Dominik Braun
2023-04-14 17:00             ` Simon Tournier
2023-04-13 20:33 ` wget (was Re: i686 core-updates failure.) Simon Tournier
2023-04-13 20:37   ` Andreas Enge
2023-04-13 20:43     ` Simon Tournier
2023-04-13 20:49       ` wget Andreas Enge
2023-04-15  0:51   ` wget (was Re: i686 core-updates failure.) Maxim Cournoyer
2023-04-15 10:43     ` Andreas Enge
2023-04-15 16:37       ` Kaelyn [this message]
2023-04-15 18:25         ` Kaelyn
2023-04-15 21:00           ` wget on i686 in core-updates Andreas Enge
2023-04-16 17:06           ` wget (was Re: i686 core-updates failure.) Andreas Enge
2023-04-16 17:49             ` Kaelyn

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='Hl8Te_UFSGJsUjfwWOK6z70f453wa_Um-g-VGqrdkbWQrgGc_hpxGsi6HOO8B_-P7tLsEcGWLC4lE5lZX9mdZebLW5GhQV3R45dMShzK1E4=@protonmail.com' \
    --to=kaelyn.alexi@protonmail.com \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=zimon.toutoune@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.