GNU bug report logs - #71202
gnu: lisp.scm: add roswell package

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 71202 in the body.
You can then email your comments to 71202 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: not emma <bigbookofbug <at> proton.me>
To: "guix-patches <at> gnu.org" <guix-patches <at> gnu.org>
Subject: gnu: lisp.scm: add roswell package
Date: Sun, 26 May 2024 02:26:29 +0000

[Message part 1 (text/plain, inline)]

I was unsure whether this would fit better under lisp.scm, or lisp-xyz.scm, but think the former is a better choice because it's independent of any specific common lisp implementation.

Sent with [Proton Mail](https://proton.me/) secure email.

[Message part 2 (text/html, inline)]

[roswell-diff.scm (text/x-scheme, attachment)]

Message #8 received at 71202 <at> debbugs.gnu.org (full text, mbox):

From: Guillaume Le Vaillant <glv <at> posteo.net>
To: not emma <bigbookofbug <at> proton.me>
Cc: 71202 <at> debbugs.gnu.org
Subject: Re: [bug#71202] gnu: lisp.scm: add roswell package
Date: Mon, 27 May 2024 12:03:32 +0000

[Message part 1 (text/plain, inline)]

Hi.

I remember that in the past someone tried to make a patch for roswell.
It built fine, but there were some issues when running it. Roswell
had difficulties finding or running sbcl, I think.

So, with your patch, does everything just work fine when building and
running it?
Or are there some extra configuration steps to take? If so, maybe it
could be indicated in the 'description' field.

See <https://issues.guix.gnu.org/37200>
and <https://github.com/roswell/roswell/issues/387>.

[signature.asc (application/pgp-signature, inline)]

Message #11 received at 71202 <at> debbugs.gnu.org (full text, mbox):

From: not emma <bigbookofbug <at> proton.me>
To: Guillaume Le Vaillant <glv <at> posteo.net>
Cc: 71202 <at> debbugs.gnu.org
Subject: Re: [bug#71202] gnu: lisp.scm: add roswell package
Date: Mon, 27 May 2024 18:44:41 +0000

Hi,

I had some initial issues with sbcl and glibc32, but those were resolved by propagating patchelf and make (the former to resolve the glibc32 error, and the latter because roswell has to run a setup on initial install, and references its makefile). Based on this issue: https://github.com/roswell/roswell/issues/387 , it seems like the primary difficulty was with curl, but that was resolved. 




Sent with Proton Mail secure email.

On Monday, May 27th, 2024 at 12:03 PM, Guillaume Le Vaillant <glv <at> posteo.net> wrote:

> Hi.
> 
> I remember that in the past someone tried to make a patch for roswell.
> It built fine, but there were some issues when running it. Roswell
> had difficulties finding or running sbcl, I think.
> 
> So, with your patch, does everything just work fine when building and
> running it?
> Or are there some extra configuration steps to take? If so, maybe it
> could be indicated in the 'description' field.
> 
> See https://issues.guix.gnu.org/37200
> 
> and https://github.com/roswell/roswell/issues/387.

Message #16 received at 71202-done <at> debbugs.gnu.org (full text, mbox):

From: Guillaume Le Vaillant <glv <at> posteo.net>
To: not emma <bigbookofbug <at> proton.me>
Cc: 71202-done <at> debbugs.gnu.org
Subject: Re: [bug#71202] gnu: lisp.scm: add roswell package
Date: Tue, 28 May 2024 13:47:43 +0000

[Message part 1 (text/plain, inline)]

Patch applied as 542b18709a46e361de8f25e3fece29860532743c with a few
modifications.
Thanks.

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.