Hi Pjotr,
> somehow propagated-inputs don't go into the archive. You'd think they are
> critical
> dependencies.
>
> Q1: is that to be expected?
I’m not sure, but it seems wrong. What I used to do is to create a
profile and export that recursively:
guix archive --export --recursive \
Hello,
I hope this is on topic. Recently, 2 critical vulnerabilities (see
https://meltdownattack.com/) affecting virtually all intel cpus are
discovered. I am running libreboot x200 (see
https://www.fsf.org/ryf). What should I do right now to patch my laptop?
Cheers,
Alex
Hello,
> Hello,
Send it by mistake...
For example, in the current directory, I have 'foo.scm':
--8<---cut here---start->8---
(define-module (foo)
#:use-module (guix records)
#:export (foo foo-x))
(define-record-type*
foo make-foo foo?
(x foo-x (default "x"
2017-11-07 22:49 GMT+01:00 Pjotr Prins :
> With regard to talks we should limit the total time for that - say 2-3
> hours total. And have the rest of the day free flowing discussion and
> hacking. Talks are useful, but I think the real impact will be to be
> together and sit down and inspire each
Hi Alex,
Alex Vong writes:
> I hope this is on topic. Recently, 2 critical vulnerabilities (see
> https://meltdownattack.com/) affecting virtually all intel cpus are
> discovered. I am running libreboot x200 (see
> https://www.fsf.org/ryf). What should I do right now to patch my laptop?
I haven'
On Sat, Jan 06, 2018 at 09:20:50PM +0800, Alex Vong wrote:
> I hope this is on topic. Recently, 2 critical vulnerabilities (see
> https://meltdownattack.com/) affecting virtually all intel cpus are
> discovered. I am running libreboot x200 (see
> https://www.fsf.org/ryf).
> What should I do right
Gábor Boskovits writes:
> 2018-01-05 16:44 GMT+01:00 Ricardo Wurmus :
>
>>
>> Gábor Boskovits writes:
>>
>> > If I understand well, then the check phase in ant-build-system
>> > runs without make-flags.
>> > In the definition of java-asm we configure the build with make-flags, so
>> > the build
Leo Famulari writes:
> The Spectre bugs have to be fixed per-application for now. As far as I
> know, we haven't made any related changes to packages besides
> linux-libre.
>
> Mozilla has released an update that is supposed to mitigate the
> vulnerability but I don't if they'll be porting it bac
Actually we still have a couple of build failures, some test failures, and
the
commit messages are not conformant to the policy. Currently making the few
remainig
failures work should be the primary task. I will check the details.
I already have an integration branch where I reorder commits and mak
ng0 writes:
> You can stash those po/* files, it's the first thing I do if I ever
> happen to work on a complete new checkout.
Do you stash JUST the po files? I have often found these po files very
annoying while trying to make changes to Guix and test locally. I think
that if I do "git stash"
Chris Marusich transcribed 1.6K bytes:
> ng0 writes:
>
> > You can stash those po/* files, it's the first thing I do if I ever
> > happen to work on a complete new checkout.
>
> Do you stash JUST the po files?
Yep. And I never stash apply them back. There's a stash of the po that I have
for abo
Danny Milosavljevic writes:
> Try this:
>
> diff --git a/gnu/build/linux-boot.scm b/gnu/build/linux-boot.scm
> index 4dd740174..810a0d63f 100644
> --- a/gnu/build/linux-boot.scm
> +++ b/gnu/build/linux-boot.scm
> @@ -507,7 +507,14 @@ to it are lost."
> (switch-root "/root")
>
Leo Famulari writes:
> On Wed, Dec 27, 2017 at 07:57:17PM -0500, Mark H Weaver wrote:
>> Alas, your most recent changes seem to have now broken qgpgme:
>>
>> https://hydra.gnu.org/eval/109869#tabs-now-fail
>> https://hydra.gnu.org/job/gnu/master/qgpgme-1.9.0.x86_64-linux
>> https://hydra.g
Leo Famulari writes:
> ### Guix status ###
>
> The CPU makers are issuing microcode updates as a hardware-level
> mitigation, but I don't think we'll be providing those in Guix.
It seems some (but not all) mitigations may require firmware/microcode
updates. For details, see:
https://newsroom.i
Mark H Weaver writes:
> Leo Famulari writes:
>
>> The Spectre bugs have to be fixed per-application for now. As far as I
>> know, we haven't made any related changes to packages besides
>> linux-libre.
>>
>> Mozilla has released an update that is supposed to mitigate the
>> vulnerability but I d
16 matches
Mail list logo
