Hi,
> This may be fixed by Gnulib commit
> 480d374e596a0ee3fed168ab42cd84c313ad3c89 (not present in
On gettext, commit 1afbcb06fded2a427b761dd1615b1e48e1e853cc seems to fix
the problem. I ran three consecutive tests :
--8<---cut here---start->8---
,
Mathieu
>From e4ad9aa61fa75afa4417616de36cd25e9631fd67 Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe <m.othac...@gmail.com>
Date: Wed, 12 Apr 2017 21:17:24 +0200
Subject: [PATCH] gnu: gettext: Fix make check issues on multi-core machines.
* gnu/packages/patches/gettext-gnulib-multi-core.p
* gnu/packages/base.scm (findutils): Reindent, no functional change.
---
gnu/packages/base.scm | 64 +--
1 file changed, 32 insertions(+), 32 deletions(-)
diff --git a/gnu/packages/base.scm b/gnu/packages/base.scm
index 1ae3c8911..e620d9cea 100644
;; Copyright © 2017 Rene Saavedra <ren...@openmailbox.org>
+;;; Copyright © 2017 Mathieu Othacehe <m.othac...@gmail.com>
;;;
;;; This file is part of GNU Guix.
;;;
@@ -259,8 +260,13 @@ interactive means to merge two files.")
r <efr...@flashner.co.il>
;;; Copyright © 2016 Jan Nieuwenhuizen <jann...@gnu.org>
+;;; Copyright © 2017 Mathieu Othacehe <m.othac...@gmail.com>
;;;
;;; This file is part of GNU Guix.
;;;
@@ -24,6 +25,7 @@
#:use-module (guix packages)
#:use-module (guix download)
Hi Marius !
> It looks like you forgot the actual patch :)
Ha ! You're right :)
>
> Please also add it to gnu/local.mk. TIA!
Ok, I'll a new batch, to be applied to core-updates.
Thanks,
Mathieu
gnu/local.mk (dist_patch): Add gettext-multi-core.patch and
gettext-gnulib-multi-core.patch.
Commit 480da86d0969a667e8d2a564de535cb73a6a2229 ommited them.
---
gnu/local.mk | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gnu/local.mk b/gnu/local.mk
index 51f92f088..620fb07f3 100644
---
@@
;;; Copyright © 2016 Efraim Flashner <efr...@flashner.co.il>
;;; Copyright © 2016 Jan Nieuwenhuizen <jann...@gnu.org>
;;; Copyright © 2017 Rene Saavedra <ren...@openmailbox.org>
+;;; Copyright © 2017 Mathieu Othacehe <m.othac...@gmail.com>
;;;
;;; This file is part of G
> and those entries would be “lowered” to somewhere.
> That way we’d provide the abstraction level that users may expect (“how
> do I add a menu entry for my other distro?”) and at the same time reduce
> the risk of mistakes (“I didn’t what to put in ‘store-device’ I put my
> pet’s name there”).
Hi Tomáš,
> My question without answer is - how can I specify bootloader menu entries now?
You're right, you have to pass a now. The
documentation patch is still in review, you can find it here :
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26339#489
The example has been updated :
Hi,
If Guile-SSH is not detected, depends-on-guile-ssh? will be called here:
--8<---cut here---start->8---
(guix build pull)
(let* ((files (remove (if (false-if-exception
(resolve-interface '(ssh session)))
Hi Ludo,
It seems better but I can't get it to work neither :
> (find (match-lambda
> (('ssh _ ...) #t)
> (_ #f))
> -(source-module-closure file #:select? (const #t
> + (source-module-closure module #:select? (const #t)
Hello,
> So how does the ‘menu-entry’ example that Tomáš gave translate with this
> new API? (Apologies for asking, I admit I haven’t fully adjusted to the
> new API mentally. :-))
Well it's still moving :)
We can ask him but I guess something like that :
--8<---cut
Hi Ludo,
Since the rework, are in (gnu bootloader grub). They can no
longer be used in menu-entries field of .
The is used instead. and
are very similar though.
What we can do here is :
* Give default values as per (as proposed
by Danny in doc patch review).
* Rename "menu-entries"
* doc/guix.texi (GRUB configuration): Rename to "Bootloader
configuration".
Adapt occurences of "GRUB" in other sections.
---
doc/guix.texi | 164 --
1 file changed, 91 insertions(+), 73 deletions(-)
diff --git a/doc/guix.texi
* gnu/bootloader.scm (): New variable. Export associated getters,
This record is extracted from grub module.
* gnu/bootloader/extlinux.scm (extlinux-configuration-file): Use
menu-entry->boot-parameters to convert menu-entry records to
boot-parameters.
* gnu/bootloader/grub.scm (): Remove.
Hi,
Here's the patch to use menu-entry instead of boot-parameters to define
custom bootloaders entries as discussed.
The second patch is the updated documentation for bootloader rework.
Thanks,
Mathieu
Mathieu Othacehe (2):
bootloader: Use menu-entry to define custom bootloader entries
Hi Ludo,
> I believe this is fixed by commit
> 20ed093977cc80ba1729c38e05ae7955a38069a6, which follows a modification
> to the ‘source-module-closure’ so that callers can catch
> missing-dependency errors.
>
> Please let me know what you think!
It seems ok, thanks for fixing it !
>
> After
Hi !
> People apparently start other Linux distributions with it :)
Yes because they use initrd only to mount root partition, then kernel is
starting /sbin/init provided by systemd or other init mechanism.
For people who's custom kernel is able to access root partition without
loading any
Hi Danny,
> For another future patch: Hmm, should we make this optional? I didn't have
> an initrd for many years.
Well I tried to run GuixSD without initrd and it's not possible
yet. Besides mounting root partition, it's also used to start the
initial guile script
> In the future, I think it’ll be preferable to commit code/tests/doc
> together. That is, in the commit that changes the API from being
> GRUB-specific to supporting multiple bootloaders, we include not only
> the code but also the doc update. This simplifies review, makes sure
> each commit
Hi,
Just sent a v2 addressing your remarks !
Thanks,
Mathieu
> I think it would make sense to be explicit about this in the manual.
>
> Ludo’.
* doc/guix.texi (GRUB configuration): Rename to "Bootloader
configuration".
Remove device-mount-point field from menu-entry description.
Adapt occurences of "GRUB" in other sections.
---
doc/guix.texi | 177 --
1 file changed, 98
* gnu/bootloader.scm (): New variable. Export associated getters,
This record is extracted from grub module.
* gnu/bootloader/extlinux.scm (extlinux-configuration-file): Use
menu-entry->boot-parameters to convert menu-entry records to
boot-parameters.
* gnu/bootloader/grub.scm (): Remove.
Hi Ludo,
> Do we still need ‘device-mount-point’ now? For the dual-boot use case,
> I don’t see how this would be used.
Nope, you're right it's not needed in .
>> + (initrd (menu-entry-initrd menu-entry
>
> It’s weird to set ‘store-device’ and ‘store-mount-point’ here since
> there’s no
Hi Mark,
This problem should be resolved by make clean-go && make, see here :
https://lists.gnu.org/archive/html/guix-patches/2017-05/msg00152.html
Mathieu
Mark H Weaver writes:
> The error message is:
>
> ERROR: In procedure GNU with Linux-Libre 4.11 (beta):
> ERROR: Wrong type to
;l...@gnu.org>
;;; Copyright © 2015 Taylan Ulrich Bayırlı/Kammer <taylanbayi...@gmail.com>
+;;; Copyright © 2017 Mathieu Othacehe <m.othac...@gmail.com>
;;;
;;; This file is part of GNU Guix.
;;;
@@ -36,26 +37,14 @@
;;;
;;; Code:
-(define (depends-on-guile-ssh? file)
- "Return tru
,
Mathieu
Mathieu Othacehe (2):
build: pull: Fix compilation list construction.
guix: modules: Export module-name->file-name.
guix/build/pull.scm | 31 ---
guix/modules.scm| 1 +
2 files changed, 9 insertions(+), 23 deletions(-)
--
2.13.0
* guix/modules.scm (module-name->file-name): Export it.
---
guix/modules.scm | 1 +
1 file changed, 1 insertion(+)
diff --git a/guix/modules.scm b/guix/modules.scm
index 8c63f21a9..26c38e8d2 100644
--- a/guix/modules.scm
+++ b/guix/modules.scm
@@ -23,6 +23,7 @@
#:use-module (ice-9 match)
> I'm having a hard time tring to understand ,trace output.
I get why, it's because guile-ssh is not in my %load-path. So loading
"ssh/session.scm" fails in "source-module-dependencies".
It's a bit of a vicious circle here : if resolve-interface '(ssh
session) fails, depends-on-guile-ssh? will
Hello,
I tought this one was pushed and told Clément it was ok to push, my
mistake! I just pushed it, so I close the ticket now.
To people used to select bootloader entries with shortcuts, be aware
that at next reconfigure, the entries will be reversed on all
bootloaders (top of the list =>
Hi Ludo & Andreas,
> Could you do:
>
> guix gc --references
> /gnu/store/vd8bx5jd868mnhm0mdj8zgjsvjakzh4y-disk-image.drv | grep
> disk-image-builder
>
> and try to run the qemu-system-arm command that appears there with the
> arguments that from gnu/build/vm.scm line 163?
>
> Mathieu came up
Hi,
This seems like a good idea ! If we decide to make it unconditional the
patch attached does the job. We can also make it configurable in
bootloader-configuration for instance.
WDYT ?
Mathieu
>From 3ec63fb55a074b547724c70d560cc61776c9298e Mon Sep 17 00:00:00 2001
From: Mathieu Othac
> Not really. I think we can at least send a heads-up to guix-devel and
> help-guix.
Ok. Would the attached patch earlier in the thread be ok for you then ?
Thanks,
Mathieu
Hi,
> Is this a bug?
No it's not, the following snippet should work better.
--8<---cut here---start->8---
(fold-packages
(lambda (package lst)
(if (string-prefix? "python" (package-name package))
(cons (and=> (package-source package)
Hey Pierre,
You can find the backtrace in /tmp/last-installer-error file.
About the bug itself, it has been reported here:
https://issues.guix.gnu.org/issue/35622
Both patches seems fine to me, but I'd like to understand why the regex
fails. Could you run this command and report the result:
> LGTM! (Please add a “Fixes …” line to the commit log for future
> reference.)
Done and pushed.
Mathieu
hen :)
Mathieu
>From dd212927d50eeed9b8d16beed1f98228299c8633 Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe
Date: Wed, 29 May 2019 09:44:44 +0200
Subject: [PATCH] installer: Fix wifi menu crash with hidden SSIDs.
* gnu/installer/connman.scm (): Mention that name may be false.
* gnu/installer/newt/wifi.scm (w
Hey,
> I think 200 is good. You wouldn’t want the backtrace to be filled with
> bytevectors, for instance.
Fine with me. Pushed.
Thanks for reviewing,
Mathieu
Hey Ludo,
> Longer-term it would be good to audit Guile-Parted: it probably
> shouldn’t be possible for Guile-Parted to refer to “defunct” Parted
> objects.
Yup, with hindsight I realize that keeping Guile-Parted so low-level was
a mistake. With a few more abstractions (gnu installer parted)
Danny suggested, I don't have
a strong opinion myself. WDYT?
Thanks,
Mathieu
>From d5f792414d0666d554dc8c7b6fee351bbe7a1c14 Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe
Date: Tue, 14 May 2019 14:05:36 +0200
Subject: [PATCH] installer: Increase backtrace verbosity.
* gnu/installer.scm (insta
Hey,
> So I guess you can go ahead and push, Mathieu!
Pushed as 445bd4d5e5, thanks to both of you for reviewing it :)
Mathieu
Hey,
> ,use (system repl debug) ; or #:use-module (system repl debug)
> (terminal-width 200)
>
> f.e. at the top of gnu/installer.scm
Thanks for testing Florian. Based on Danny suggestion we could set
COLUMNS to 200 to have a more verbose backtrace (like guix itself).
Using higher values,
And the patch ...
Sorry,
Mathieu
>From 3348df0c72e9bcdf31b63155d9c6bdbaee515524 Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe
Date: Sat, 4 May 2019 18:10:40 +0200
Subject: [PATCH] installer: Increase backtrace verbosity.
* gnu/installer.scm (installer-program): Set COLUMNS env varia
wrapping. The attached patch fixes the issue.
Thanks,
Mathieu
>From f68ded2f134d55c20f98300c0514c4fc18cd1d50 Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe
Date: Sat, 4 May 2019 11:33:33 +0200
Subject: [PATCH] installer: Reflow run-file-textbox-page text.
* gnu/installer/newt/page.scm (run-
Hey Ludo,
> I would perhaps add that checkbox only for the passphrase, in part
> because when I test an install I prefer to have fewer keystrokes :-),
The parameter is disabled by default and enabled only for disk
encryption and root/user passwords so I'm not sure I get what you mean.
> but
Hello,
> I believe the broader issue is that the installer cannot really be
> restarted after a failed install, as we discussed a while back on
> guix-devel. Mathieu, can you confirm?
I'm not aware of this layout issue, however, after the installer is
restarted, the install is doomed because
Hey,
> Not sure if this can be fixed. Mathieu?
The textbox object used for the backtrace window only supports vertical
scrolling. However, the text should be broken in lines that fit the box
horizontally, I'll try to find why it doesn't work.
Mathieu
t now has such a checkbox, WDYT?
Thanks,
Mathieu
>From fba1d82b2e27917a5efef339b326fe2d98e62bc0 Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe
Date: Sun, 5 May 2019 12:54:40 +0200
Subject: [PATCH] installer: Add password 'hide' checkbox.
* gnu/installer/newt/page.scm (run-input-page)[input-hide-che
Hey Ludo,
> Does that make sense?
>
> I think we should audit and adjust Guile-Parted in that spirit. WDYT?
Yes, it seems like the right thing to do. I'll try to apply those
changes to Guile-Parted next week. However, as we cannot reproduce those
null-pointer issues, we won't be sure if we
Hey Ludo,
> Does that make sense?
>
> I think we should audit and adjust Guile-Parted in that spirit. WDYT?
Sorry for the delay!
I followed your advice and hid all destroy related functions behind
pointer finalizers. I also added some unit tests to Guile-Parted.
I pushed everything but feel
Hey,
I pushed the missing file :).
> It might be useful to add calls to ‘gc’ here and there in the tests to
> stress-test memory management.
Inserting gc calls here:
--8<---cut here---start->8---
(test-assert "partition-remove extended"
(with-tmp-device
Hey,
> So perhaps you should define your own ‘define-wrapped-type’ macro that
> does ‘define-record-type’ + the weak hash table thing, and replace all
> ‘define-record-type’ instances in structs.scm with
> ‘define-wrapped-type’. How does that sound?
Seems like the right thing to do :)
Hello Danny,
> However, even after that, disk-print, if used, prints nonsensical (negative)
> values for "free" (but installation succeeds).
>
> That bug prevents graphical installation on any drive bigger than 1 TiB.
> Let's make a bugfix Guix release shortly.
Your fix seems ok for me, thank
This patch is a bit more viable that the previous one I think.
Mathieu
>From f126146880e3904f39728313dfc10288b51fc23a Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe
Date: Thu, 31 Oct 2019 15:05:54 +0100
Subject: [PATCH] gnu: clang-from-llvm: Fix set-glibc-file-names phase.
* gnu/packa
f53a14bb0889cb47 Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe
Date: Thu, 14 Nov 2019 13:25:00 +0100
Subject: [PATCH] gnu: Add clang-toolchain.
* gnu/packages/llvm.scm (make-clang-toolchain): New method.
(clang-toolchain): New public variable defined using previous method.
---
gn
> Applying both your patch and my patch works for me, in both pure and
> non-pure environments. I would suggest taht we also hide clang in the
> same way as gcc is hidden (in favour of clang-toolchain) to avoid
> confusion, but otherwise it seems these two patches together at least
> get things
> I'm not sure what the answer is there though, as we still need to patch
> in the full path to the headers... maybe a cmake option and associated
> macro to be used in that file?
They already have a CMake option to select libc++ or libstdc++, so
adding another option to specify the path of
> It seems to be also an issue for evaluations that look successful but
> are reported as failed, see here:
Looking at those evaluation logs, I think there is yet another issue. On
core-updates:
* Evaluation 8747 fails because it cannot build curl
(https://ci.guix.gnu.org/eval/8748/log/raw).
Hello,
I edited your patch to include a copyright line, adapted commit log
message to our conventions and pushed it! Please tell me if you want a
different copyright.
I also pushed my patch adding clang-toolchain packages.
Thanks,
Mathieu
Hello,
It seems to be also an issue for evaluations that look successful but
are reported as failed, see here:
https://ci.guix.gnu.org/eval/8641/log/raw -> mark as failed
https://ci.guix.gnu.org/eval/8725/log/raw -> mark as failed
Mathieu
Hello,
I'm closing this one as you pushed the patch.
Mathieu
> Marius: I believe this will only cause a rebuild for clang and not
> llvm, which means that it only affects ~30 packages. Perhaps this can
> go in master? Would love to know your thoughts.
There is also the problem that IceCat depends on Rust which depends on
Clang as stated by Mark.
Mathieu
Hello,
> In case it's not clear: Booting works, but restarting the session
> crashes.
Not much to add, but I have the same issue and once logged out, I need to
restart my machine to login again to GNOME on Ubuntu 18.04.
Mathieu
02e78096963616d4e2f999119fc4d Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe
Date: Mon, 9 Dec 2019 16:16:45 +0100
Subject: [PATCH] Add ssh authentication support.
* Makefile.am (SOURCES): Add git/auth.scm,
(TESTS): add tests/clone.scm.
* configure.ac: Check for git and ssh binaries.
* git.scm
Hola!
> As for the detection, this appears to work:
>
> (define (binfmt-misc?)
> (let ((pid (getpid))
> (cmdline (call-with-input-file "/proc/self/cmdline"
> get-string-all)))
> (match (primitive-fork)
> (0 (dynamic-wind
> (const #t)
>
amalingam
>
> On Mon, Dec 2, 2019 at 9:18 AM Pon Arun Kumar R
> wrote:
>
>> I downloaded the 1.0.1 image from the guix webpage and wrote a bootable
>> DVD and used the graphical installer on a machine (lenova thinkpad t410
>> 64bit)
>>
>> On Mon, Dec 2, 2019
Hey!
> Apart from this detail, it looks great to me!
>
> You have push access, right?
>
> Speaking of which, we really need to push a release at some point.
> Erik, would you be available to do that, or would you like to delegate?
Great, thanks for reviewing :). I couldn't get it to work with
> Thanks for merging this! Would it be possible to change the copyright
> to Arm Ltd. but leave my email as the point of contact? Please let me
> know if this is an issue.
No I guess its ok. Pushed!
Mathieu
Mmmh, I get what's going on in tests/processes.scm. It's an issue in
(guix scripts processes) where argv0 is checked for "guix-daemon".
When using --system my-system, argv0 is "qemu-my-system". So we need to
check both argv0 and argv1 for "guix-daemon".
I'll propose a patch.
Mathieu
properly for the test suite.
WDYT?
Mathieu
>From 3b6f5708043a29343275fadf0b0e0e651bb6971e Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe
Date: Fri, 29 Nov 2019 10:37:12 +0100
Subject: [PATCH] process: Fix binfmt support.
Guix-daemon does fork itself for each client process. The pid of the client is
hardcoded into the clone arg
ead keys,
>
> I tried several attempts, and I doubt whether it is something to do with
> the BIOS settings update as a pre-requite for the installation.
>
> Thanks,
> Pon ArunKumar R
>
> On Mon, Dec 2, 2019 at 8:54 AM Mathieu Othacehe
> wrote:
>
>>
>> Hel
Hello Clément,
> I think there are small modifications to do to (guix git) and (git
> clone).
I did integrate a part of libgit2 ssh authentification mechanism in
Guile-Git in 2017. You can find it in (git fetch) module.
It is currently broken, because of a regression. See
> * Fix the regression mentionned above.
I would need some help for this regression I don't understand, but I
will take care of the work needed in Guile-Git and (guix git) once this
is fixed.
I think too that extending Cuirass to support new use-cases would be
really great :).
Thanks,
Hello,
I have 3 failing tests when building guix 1.0.1-10.41b4b71 on armhf. I
didn't build with -K argument and as it takes ~10 hours, so I'll just paste
my terminal output for now.
It seems to fail on ci.guix.info but the log is partial?
Hello Carl,
The attached patch fixes it for me, but this piece of code should be
rewritten so that we don't have the same failure at every clang major
version update.
WDYT?
Mathieu
>From ac0cf4e25f9acdb02bee402b45a8f31a4830fcb7 Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe
Date: Thu, 31
Hello David,
This patch is a real progress, thank you! However, I still have a
linking error when compiling a trivial test program with clang:
mathieu@elbruz ~/guix [env]$ ./pre-inst-env guix environment --ad-hoc clang
--pure
mathieu@elbruz ~/guix [env]$ clang ~/tmp/t.cpp
clang-8: error:
error:
> + (wrong-type-arg
> + #f
> + "Wrong type to apply: ~S"
> + (#f)
> + (#f))
> result: FAIL
>From 13d2014879372a947e3239c14bdc9f6ae8f3c318 Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe
Date: Tue, 26 Nov 2019 08:31:43 +0100
Subject: [PATCH] tests: lzlib: Do not
> This should allow us to close:
>
> https://issues.guix.info/issue/39217
> https://issues.guix.info/issue/38447
Fixed by 1d02052067e04d7dd8fd1ec17557ca02a30b9bcf.
Thanks,
Mathieu
Hello Janneke,
> Do you have a patch/branch where I can see this related error? If mes
> builds are an exception, it could be nice to solve it there? Or is
> this a Qemu thing and is Qemu the only package that suffers from this?
>
> Trying to help here, but I'm not sure if I understand what's
ncement)
for mes packages.
So, maybe the best option is to patch QEMU directly, as proposed in
the attached patch. WDYT?
Thanks,
Mathieu
>From 6d5dea746ce7b501cdb5ba41c5eff0c9ea7eb0b0 Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe
Date: Tue, 3 Mar 2020 12:45:33 +0100
Subject: [PATCH] gnu
Hey,
> clang-runtime requires a similar fix for CPLUS_INCLUDE_PATH. No idea
> what's up with GHC@8.4 yet, but unsurprisingly removing libc from the
> include paths does not make a difference.
Closing this one, thanks for pushing!
Mathieu
Hello,
When building the attached operating-system (very close to
bare-bones.tmpl) with the following command:
guix system disk-image --target=aarch64-linux-gnu mini.scm --no-grafts
the produced disk-image weights 2.6G (2717242368 bytes). On the same
branch in January it was around 1.5G.
I'll
Hey,
> So is it expected that C_INCLUDE_PATH comes before the hard-coded GCC
> include directory? How can we work around that?
Turns out, the best source of documentation here is
gcc/incpath.c. Here's a summary of my understanding.
Header search list:
* QUOTE
-> -iquote
* BRACKET
-> -I
Hey!
> I’d rather go for #2. To do that, we could modify the ‘set-paths’ phase
> to manually remove glibc from C_INCLUDE_PATH (fragile), or we could
> modify GCC (perhaps removing the ‘remove_duplicates’ call for SYSTEM).
>
> Either way, this wouldn’t work well with ‘guix environment’, where
Oops wrong shortcut, sorry!
> I’d rather go for #2. To do that, we could modify the ‘set-paths’ phase
> to manually remove glibc from C_INCLUDE_PATH (fragile), or we could
> modify GCC (perhaps removing the ‘remove_duplicates’ call for SYSTEM).
>
> Either way, this wouldn’t work well with
Hey Marius,
> Did you get anywhere with this? As Ludovic mentioned, it might make
> sense to work around it in gnu-build-system too if patching GCC turns
> out to be difficult.
Yup, turned out patching GCC was too difficult. I'm experimenting a
filter over inputs passed to
Hey,
> Perhaps we should not call it at the top level, in case it throws an
> exception or has unwanted side effects? I’d suggest moving it to
> the procedures where it’s used. Thoughts?
>
> Apart from that it LGTM, thanks!
Fixed and pushed! Shall we inform users (guix pull news?) that they
irass
inputs and (guix git-download) module.
Mathieu
>From ae380c15f1c37e2c94e0954975f5f712e76340ac Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe
Date: Mon, 3 Feb 2020 18:05:02 +0100
Subject: [PATCH] git: Add ssh authentication support.
SSH agent authentication method is used.
* guix/g
ay.)
Here's a version with optional authentication support. I do not find it
too intrusive, but let me know what you think!
Thanks,
Mathieu
>From 4554baf59564eb0c31cfe235acd078d54afef6d7 Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe
Date: Mon, 3 Feb 2020 18:05:02 +0100
Subject: [PATCH] git: Add
Hello,
> "815d3ac4c343c75beca2d752adc34312bfeff4fe"; system: "x86_64-linux";
> host version: "98e3953e96d1f172e2e44d1f2d2f2e6b107f2daa"; pull-version: 1).
> Please report it by email to .
>
> I attached the full output of the pull.
This seems to be caused by the update to Guile-SSH 0.12.0. I
Hello,
On core-updates, qemu-minimal (4.2.0), fails to build. This seems to be
the same issue as this bug. The error is:
--8<---cut here---start->8---
In file included from
/gnu/store/jsjsczgr8xdnbdminl7lm2v56b7dq7lq-glibc-2.31/include/features.h:489:0,
This should allow us to close:
https://issues.guix.info/issue/39217
https://issues.guix.info/issue/38447
And other issues I'm not aware of?
Mathieu
Hey Ludo,
Nice progress on that branch :)
> Could it be a side effect of the MS_MOVE dance in
> 1d02052067e04d7dd8fd1ec17557ca02a30b9bcf?
Could be, I ran the following command on wip-installer-test branch:
--8<---cut here---start->8---
make check-system
Hey Ludo,
> But I think the problem should show up even with “make check-system
> TESTS=installed-os” on master.
Well this does not involve the graphical installer, so I'm not sure to
understand.
Anyway, testing the installer in Qemu, I can reproduce a failure where
the first umount in
Hello,
> On master there’s pretty much the same command as above, with ‘-m16’,
> and “yet it works”.
>
> https://ci.guix.gnu.org/log/ymzp5yz2r3zfw4xczwwlykyjv2kqcqs0-qemu-4.2.0
On master, when building qemu, this is the gcc include path (obtained
with "gcc -v -x c -E /dev/null"):
Hello,
> You mean that Ctrl-C wouldn’t work on the ‘guix system init’ process,
> right? Is that behavior controlled by Newt, Mathieu?
Before running the guix process, newt is suspended and resumed right
after (see run-install-shell procedure). So it should reset the original
terminal
The "guix size" report is attached. Several issues appear:
* Inclusion of gcc-cross-sans-libc-aarch64-linux-gnu-7.5.0 and
gcc-cross-aarch64-linux-gnu-7.5.0.
* Three different versions of guile-2.2.6.
* Duplicated glibc, bash and coreutils.
Thanks,
Mathieu
size_core
Description: Binary data
Hi,
> Ah yes, we should try to introduce a “lib” output there as well. I
> vaguely remember this was tricky but I’m not sure why; worth a try!
Ok then, I'll give it a try.
> Speaking of which, the Data Service has things like:
>
>
>
Hey,
> Could you find out (perhaps by looking at ‘guix graph -t references’)
> what is referencing these two cross-compilers?
Turns out on master,
--8<---cut here---start->8---
guix size `guix build guile|grep -v debug`
--8<---cut
1 - 100 of 670 matches
Mail list logo
