From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Release progress, week 3
Date: Wed, 02 Nov 2022 12:07:22 +0100 [thread overview]
Message-ID: <87pme5vclx.fsf@gnu.org> (raw)
In-Reply-To: <87k04lci5u.fsf@contorta> (Vagrant Cascadian's message of "Thu, 27 Oct 2022 10:04:13 -0700")
Hi,
Vagrant Cascadian <vagrant@debian.org> skribis:
> On 2022-10-27, Ludovic Courtès wrote:
>> Release progress: week 3.
> ...
>> • Architectures:
>>
>> - powerpc64le-linux builds are back behind ci.guix, thanks to
>> Tobias!
> ...
>> - armhf-linux: No progress so far.
>
> Not sure where this fits into the release process, but I uploaded a git
> snapshot to Debian of guix from commit
> c07b55eb94f8cfa9d0f56cfd97a16f2f7d842652 ...
Yay, thanks!
> All 6 of the failures have the same error:
>
> test-name: channel-news, no news
> ...
> actual-error:
> + (git-error
> + #<<git-error> code: -1 message: "invalid version 0 on git_proxy_options" class: 3>)
> result: FAIL
This looks like an ABI issue with libgit2. Are you sure the same
version of libgit2 is used on all these platforms?
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-11-02 11:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 9:56 Release progress, week 3 Ludovic Courtès
2022-10-27 17:04 ` Vagrant Cascadian
2022-11-02 11:07 ` Ludovic Courtès [this message]
2022-11-02 18:19 ` Vagrant Cascadian
2022-11-03 15:13 ` Ludovic Courtès
2022-11-04 23:10 ` test suite/ABI issues building guix on Debian (was Re: Release progress, week 3) Vagrant Cascadian
2022-11-06 9:35 ` Release progress, week 3 Efraim Flashner
2022-11-07 9:23 ` Ludovic Courtès
2022-11-07 14:03 ` Andreas Enge
2022-11-15 20:48 ` Maxim Cournoyer
2022-11-16 14:22 ` Andreas Enge
2022-10-29 21:01 ` Guillaume Le Vaillant
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=87pme5vclx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=vagrant@debian.org \
/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).