unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Thu, 03 Nov 2022 16:13:22 +0100	[thread overview]
Message-ID: <8735b0qdf1.fsf@gnu.org> (raw)
In-Reply-To: <87v8nxcj86.fsf@contorta> (Vagrant Cascadian's message of "Wed, 02 Nov 2022 11:19:21 -0700")

Hi,

Vagrant Cascadian <vagrant@debian.org> skribis:

>>> 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?
>
> My quick and rough archeaology shows that libgit2-dev
> 1.1.0+dfsg.1-4.1+b1 was used to build guile-git 0.5.2-4, but the current
> libgit2-dev package in Debian is 1.5.0+ds-6 ... so that seems plausible.

[...]

> Maybe there is a better way I can track the various guile-* packages in
> Debian, but manually tracking all the relevent dependents seems
> implausible (or at least, a lot of work)... which may lead to the
> conclusion that maintaining Guix in Debian implausible. :/

I don’t see how that’s specific to guile-* packages though.  Anytime a
dependency is upgraded that introduces a different ABI, you need to
rebuild dependents, right?  That’s what’s happening here.

> Seems like the most likely ones I would have to keep a close eye on are
> guile-gcrypt, guile-git, guile-gnutls (although currently part of gnutls
> this will likely change soonish), guile-lzlib, guile-ssh, guile-sqlite3,
> guile-zlib, guile-zstd. And there's also keeping an eye on guile itself,
> which adds another set of packages. Wheee. Hrm.

Heh.  Speaking of which, guile-gnutls is now a thing of its own,
separate from GnuTLS:

  https://gitlab.com/gnutls/guile/

I believe Andreas Metzler already update Debian’s guile-gnutls package
accordingly.

Thanks,
Ludo’.


  reply	other threads:[~2022-11-03 15:14 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
2022-11-02 18:19     ` Vagrant Cascadian
2022-11-03 15:13       ` Ludovic Courtès [this message]
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=8735b0qdf1.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).