From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: Timothy Sample <samplet@ngyro.com>
Cc: 30680-done@debbugs.gnu.org, racket-users@googlegroups.com
Subject: bug#30680: [racket-users] Using Racket's raco on on Guix(SD)
Date: Sun, 12 Aug 2018 20:21:13 -0400 [thread overview]
Message-ID: <87in4ff75y.fsf__17223.9404674203$1534119612$gmane$org@dustycloud.org> (raw)
In-Reply-To: <87d0unb9hk.fsf@ngyro.com>
Good news: this seems fixed with this patch. Some more comments inline.
Timothy Sample writes:
>>> Also, I checked all of this from Racket without grafts, and it never
>>> complained about compiling OpenSSL stuff. Running “raco setup” gives
>>> some other errors, though.
>>
>> You're right... without grafts it doesn't have the openssl error. The
>> other writing to the store issues still seem to persist, but it doesn't
>> block running "raco setup" (after a "raco pkg install", a step I had
>> omitted earlier).
>
> Okay. I was confused about the “raco setup” example, but the other step
> makes more sense now.
>
> I will say that even on Debian, with an regular user, I have seen
> “permission denied” errors because Racket tries to update files in
> “/usr/share”.
Okay... on that note, "raco pkg install" now completely works IME
without permission errors, I should mention. I'm still seeing a couple
of permission errors on "raco setup", but they don't look like they
matter unlike the ones that were appearing earlier. And you're right,
I tried on Debian and got some errors too.
For the record, the ones I saw looked like this:
delete-file: cannot delete file
path: /gnu/store/33rx7rh6q22h3r11x8prz37nl7ygfl22-racket-6.12/bin/raco
system error: Read-only file system; errno=30
context...:
/gnu/store/33rx7rh6q22h3r11x8prz37nl7ygfl22-racket-6.12/share/racket/collects/launcher/launcher.rkt:358:0: make-unix-launcher
/gnu/store/33rx7rh6q22h3r11x8prz37nl7ygfl22-racket-6.12/share/racket/collects/setup/setup-core.rkt:1451:13: for-loop
/gnu/store/33rx7rh6q22h3r11x8prz37nl7ygfl22-racket-6.12/share/racket/collects/setup/setup-core.rkt:1428:8: make-launcher
/gnu/store/33rx7rh6q22h3r11x8prz37nl7ygfl22-racket-6.12/share/racket/collects/setup/setup-core.rkt:1556:8: for-loop
/gnu/store/33rx7rh6q22h3r11x8prz37nl7ygfl22-racket-6.12/share/racket/collects/setup/setup-core.rkt:178:50
/gnu/store/33rx7rh6q22h3r11x8prz37nl7ygfl22-racket-6.12/share/racket/collects/setup/setup-core.rkt:1425:4: for-loop
/gnu/store/33rx7rh6q22h3r11x8prz37nl7ygfl22-racket-6.12/share/racket/collects/setup/setup-core.rkt:71:0: setup-core
/gnu/store/33rx7rh6q22h3r11x8prz37nl7ygfl22-racket-6.12/share/racket/collects/setup/main.rkt: [running body]
/gnu/store/33rx7rh6q22h3r11x8prz37nl7ygfl22-racket-6.12/share/racket/collects/raco/main.rkt: [running body]
But again, I don't think they matter.
>> ISTM that this is a separate bug. In fact I'm afraid I've polluted this
>> bug with what I thought were all the same bug but turned out to be
>> several different bugs, of which a couple are fixed now thanks to your
>> help.
>>
>> PS: About the bounty, my thoughts are that some of these smaller issues
>> being resolved are already worth a smaller amount of compensation (and
>> thanks!), but there are *two different* larger issues of which probably
>> either is worth the full amount (though I can only afford to pay for
>> one)... one of them is the issue of the grafts breaking eg openssl
>> (which maybe we should file as a separate bug?), and the other is this
>> original bug (30680) about the attempts to compile to the store (which
>> does not seem as big of a blocker as it did previously, but is still
>> very annoying). Does that seem fair? (Feel free to contact me
>> off-list.)
>
> Actually I think there is only one bug, which is the grafts thing. This
> bug was originally about compiling OpenSSL files to the store. Grafting
> doesn’t break OpenSSL it just makes Racket try to recompile its OpenSSL
> FFI wrappers.
>
> I have a patch, too. I sent it to guix-patches, but I must have made a
> mistake because it ended up in bug-guix attached to this bug report.
> The patch can be found at <https://debbugs.gnu.org/30680>. Also, the
> attachment didn’t get sent to the list, but did make it to the bug page.
> Hm.... Sorry for the goof!
It seems good to me. I'm going to push it. Thanks for your work on
this!
I'll email you off-list about paying the bounty :)
prev parent reply other threads:[~2018-08-13 0:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87d0xn24d9.fsf@dustycloud.org>
[not found] ` <0990d521-934b-069b-3f29-faf8a22a5bd0@fastmail.net>
2018-08-11 15:18 ` bug#30680: [racket-users] Using Racket's raco on on Guix(SD) Christopher Lemmer Webber
[not found] ` <87wosxexu7.fsf@dustycloud.org>
2018-08-11 20:23 ` Timothy Sample
[not found] ` <87h8k0d54i.fsf@ngyro.com>
2018-08-11 21:55 ` Christopher Lemmer Webber
[not found] ` <87va8gfu0c.fsf@dustycloud.org>
2018-08-11 22:05 ` Nils Gillmann
[not found] ` <20180811220538.ca2wyilh6gq62dm3@abyayala>
2018-08-11 23:28 ` Christopher Lemmer Webber
[not found] ` <87tvo0fpox.fsf@dustycloud.org>
2018-08-12 2:03 ` Timothy Sample
[not found] ` <871sb4cpeu.fsf@ngyro.com>
2018-08-12 9:32 ` Gábor Boskovits
2018-08-12 15:31 ` Christopher Lemmer Webber
[not found] ` <87r2j3fvor.fsf@dustycloud.org>
2018-08-12 20:44 ` Timothy Sample
[not found] ` <87d0unb9hk.fsf@ngyro.com>
2018-08-13 0:21 ` Christopher Lemmer Webber [this message]
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='87in4ff75y.fsf__17223.9404674203$1534119612$gmane$org@dustycloud.org' \
--to=cwebber@dustycloud.org \
--cc=30680-done@debbugs.gnu.org \
--cc=racket-users@googlegroups.com \
--cc=samplet@ngyro.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).