all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 46844@debbugs.gnu.org
Subject: bug#46844: guile2.2-bytestructures fails to  compile.
Date: Mon, 01 Mar 2021 15:14:15 +0100	[thread overview]
Message-ID: <87h7lvrmfc.fsf@gnu.org> (raw)
In-Reply-To: <3f495538d371826b84b9ec6864503c60844c1d95.camel@telenet.be> (Maxime Devos's message of "Mon, 01 Mar 2021 09:06:49 +0100")

Hi,

Maxime Devos <maximedevos@telenet.be> skribis:

> guile2.2-bytestructures and guile2.0-bytestructures don't compile.
> The reason seems to be that v1.0.9 uses (scheme eval), which isn't
> defined in guile2.0 and guile2.2. v1.0.8 doesn't use (scheme eval)

Perhaps worth reporting upstream.

> Here's the commit that seems to introduce the issue while fixing
> another:
>
> guix time-machine --commit=0a1da4652d9bb93d530ca52710f30b5d05a4251d -- build guile2.0-bytestructures guile2.2-bytestructures
>
> According to a "guix refresh --list-dependent guile2.0-bytestructures guile2.2-bytestructures"
> on 372b15f8625e7f20cafdba2677d4bf3f5eccc127, only "guile2.0-git",
> "guile2.2-parted" and "guile2.2-guix" depend on these packages,
> so unless someone needs "guile2.2-guix", it should be safe to remove
> these packages.

‘guile2.2-guix’ exists mostly to check compatibility with 2.2.  I’d like
to drop 2.2 support soonish, though it’s okay to keep as long as it’s
not a burden (which it’s slowly becoming).

Thanks,
Ludo’.





  reply	other threads:[~2021-03-01 14:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01  8:06 bug#46844: guile2.2-bytestructures fails to compile Maxime Devos
2021-03-01 14:14 ` Ludovic Courtès [this message]
2021-03-01 14:47 ` Taylan Kammer
2021-03-03 14:56   ` Taylan Kammer
2021-03-05 15:36     ` Maxime Devos
2021-03-10 19:10 ` Taylan Kammer
2021-03-10 20:12   ` zimoun
2021-03-10 20:55     ` Taylan Kammer
2021-03-10 21:11       ` Taylan Kammer
2021-03-10 21:44         ` zimoun

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=87h7lvrmfc.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=46844@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /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.