Hi,
this issue has been fixed in commit dedfcaa8e2b948124f76121b9062c827fe649e29.
Cheers,
Lars
Hi!
Kjartan Oli Agustsson 写道：
Updating channel 'kjartan' from Git repository at
'file:///home/kjartan/guix-custom'...
Authenticating channel 'kjartan', commits 3bd6c82 to 6677083 (1
new commits)...
ice-9/boot-9.scm:1685:16: In procedure raise-exception:
#:5:1: unexpected end of input while sea
I recently installed the full Guix system, and after reading the
sections of the manual about channels I set one up for my personal
modifications to existing packages. Everything worked fine until I
committed changes to one of those package definitions and re-ran 'guix
pull' which fails with:
> U
Pushed as 0aa43117907581779cf3f343c6175d98369b7e07.
Closing, even though I didn’t manage to boot it on QEMU.
Ideally Guix System would run as seemlessly as the Ubuntu ARM cdimages
work on Macs, but I can’t test and it is a different issue.
Regards,
Florian
On Tue, Jun 07, 2022 at 12:50:26PM +0200, pelzflorian (Florian Pelz) wrote:
> Ideally Guix System would run as seemlessly as the Ubuntu ARM cdimages
> work on Macs, but I can’t test and it is a different issue.
*on QEMU on Macs
Hi!
Maxim Cournoyer skribis:
> Ludovic Courtès writes:
[...]
>>> I reviewed how that works, and it'd be easy; I just didn't see the
>>> incentive yet (there's no composition needed for the service, and it'd
>>> make the definition slightly less readable). If you tell me
>>> mark+forkexec-con
Hi,
I was able to build java-plexus-component-metadata using this patch, and
from there maven to clojure-tools.
Cheers,
Futurile
Hi all,
I'm experiencing the following error when I try to make something like
(cross-libc "riscv64-unknown-linux-gnu") and it broke in every single setup I
already have for months and was working properly. In fact, it works as expected
when using a time-machine to the past.
```
$ guix shell -
Ekaitz Zarraga schreef op di 07-06-2022 om 15:43 [+]:
> I think the error was introduced in the commit
> b55310603f0df7d5ae02d47cb8d4be58bf1d41ca but I can't really explain what's
> happening.
I guess it's due to the introduction of
lookup-platform-by-target-or-system
Proposed solution:
Tobias Geerinckx-Rice writes:
>> If I delete the git repository and re-initialize it the pull is
>> successful, but once I commit any changes to this new repository the
>> problem re-appears.
>
> It must be some specific change/file, not any change.
I just re-initialized the git repo, and chang
Hi,
tl;dr: I hope there will be a security team discussing
whether/how this kind of privileged execution interval
could be exploited, and how to prevent such.
E.g., could something that stealthily gets put in a finalizer
for some innocent object be waiting to no
11 matches
Mail list logo
