From: Christopher Howard <christopher@librehacker.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 49307@debbugs.gnu.org
Subject: bug#49307: clisp: build failure: failing tests
Date: Tue, 13 Jul 2021 06:13:41 -0800 [thread overview]
Message-ID: <3ce371520d41479df39a993258f2bdce69559634.camel@librehacker.com> (raw)
In-Reply-To: <8635sipqhp.fsf@gmail.com>
Hello. The clisp build failure occured on my work computer, whereas the file corruption occurred on my home computer. Incidentally, I gave up home off solving the corruption issue and has to wipe and
reinstall guix on that system. I will try to rebuild the clisp package now on both systems.
--
Christopher Howard
my gemini capsule: gemini://gem.librehacker.com
gemini browser: https://git.skyjake.fi/gemini/lagrange/releases
On Tue, 2021-07-13 at 10:28 +0200, zimoun wrote:
> Hi Christopher,
>
> On Sat, 03 Jul 2021 at 09:40, zimoun <zimon.toutoune@gmail.com> wrote:
> > On Thu, 01 Jul 2021 at 09:37, Christopher Howard <christopher@librehacker.com>
> > wrote:
> > > Hi, yes, I am able to reproduce the error, even when I switch to your
> > > guix commit (using time-machine).
> >
> > As Guillaume, CLISP builds successfully for me too.
> >
> > Could this bug related to your message [1]:
> >
> > Something is certainly corrupted somewhere, but I can't figure
> > out where, or what it is exactly that I need to repair or delete
> > or whatever.
> >
> > ?
> >
> > 1:
> > <https://yhetil.org/guix/e0e21927198fb55f82784c0f3ad661d82104c80e.camel@librehacker.com>
>
> Is it still an issue for you?
>
> All the best,
> simon
next prev parent reply other threads:[~2021-07-13 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 0:43 bug#49307: clisp: build failure: failing tests Christopher Howard
2021-07-01 7:51 ` Guillaume Le Vaillant
2021-07-01 17:37 ` Christopher Howard
2021-07-03 7:40 ` zimoun
2021-07-13 8:28 ` zimoun
2021-07-13 14:13 ` Christopher Howard [this message]
2021-07-13 16:40 ` Christopher Howard
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=3ce371520d41479df39a993258f2bdce69559634.camel@librehacker.com \
--to=christopher@librehacker.com \
--cc=49307@debbugs.gnu.org \
--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 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).