Hello,
Christopher Baines skribis:
> The max-age of that narinfo is currently based on the scheduled removal
> of the zstd compressed nar, which is going to happen quite far in the
> future.
>
> I did think of a number of ways to approach this, and I'm not sure I've
> settled on the right one
Hi Sebastian,
Sebastian Dümcke skribis:
> just wanted to chime in. Since last week I have some working code to
> generate AppImages with guix pack. I was planning on tidying this up
> for submission over the next weeks.
> There is still work to do regarding documentation, adding options
>
[resending as a wide reply, sorry]
Felix Lechner writes:
> Hi Ricardo,
>
> On Sat, Apr 06 2024, Ricardo Wurmus wrote:
>
>> Any ideas what might be going on here?
>
> Could it be "ModuleNotFoundError: No module named 'jupyter_server'"?
I don't think so. There is no jupyter_server module in the
Hi Nathan,
On Mon, Apr 08 2024, Nathan Dehnel wrote:
> I don't think you're supposed to edit /etc/guix/channels.scm directly,
> I think it's generated by guix system reconfigure.
As Ludo' pointed out on Mastodon recently [1] the system channels can
also be customized, if needed. [2]
Kind
On 2024-04-08 23:06:00 -0500, Nathan Dehnel wrote:
> I don't think you're supposed to edit /etc/guix/channels.scm directly,
Is this documented anywhere? I used the code for over a year and it worked just
fine. I cannot find any instruction to not touch it anywhere in the info
manual.
> I think
On 2024-04-09 06:16:12 +0200, Marek Paśnikowski wrote:
> 09.04.2024 06:06:00 CEST Nathan Dehnel:
> > I don't think you're supposed to edit /etc/guix/channels.scm directly,
> > I think it's generated by guix system reconfigure.
> > https://gitlab.com/nonguix/nonguix/-/issues/33
> > I have
09.04.2024 06:06:00 CEST Nathan Dehnel:
> I don't think you're supposed to edit /etc/guix/channels.scm directly,
> I think it's generated by guix system reconfigure.
> https://gitlab.com/nonguix/nonguix/-/issues/33
> I have ~/.config/guix/channels.scm generated by putting
>
Wow, that's incredible.
>Port number themselves stem from TCP emerging from earlier protocols (see the
>early RFCs 322, 349, 433 and those that obsolete them), and a clean design
>would probably elect to eschew them, leveraging a \(2^{128}\) address space to
>allow process-to-process
