Le 26 juillet 2019 01:03:08 GMT+02:00, "Ludovic Courtès" a écrit
:
>Hi Julien,
>
>Julien Lepiller skribis:
>
>> I gave a small tutorial to someone today, where we installed guix on
>top of a foreign distro. We used the script and everything went
>smoothly, and after finding out that we were goin
On Fri, Jul 26, 2019 at 01:04:40AM +0200, Ludovic Courtès wrote:
> What about adding a few words under “Hardware Considerations”?
>
While my patch before addresses AMD-specific tweaks in the manual
under Hardware Considerations, it is not enough if on the *download
page* Guix is claimed to run on
> I have applied ‘your’ patch in
> 41097b2dee9367974c6dd16ac1ba2ee945457237.
>
> I'm closing this bug for now. However, could you update and
> confirm that this actually solves the problem?
Oh Shoot! I just saw your previous reply and replied to it. Sorry for
the delay. Anyway that patch fixe
> I will do so swiftly since I updated libvirt to the 'broken' version
> (although I never had any troubles like yours). Thank you for
> reporting this upstream.
About that, it appears I misunderstood the patch. That recent build was
not to fix the bug I reported. Anyway, I have been told by o
Hi,
I believe there is an issue with 'lower-gexp'. Running the following
snippet to lower a G-Expression for "i686-linux" yields output that
references store paths built for x86_64. In this case, the Guile
interpreter used is an x86_64 binary.
#+BEGIN_SRC scheme
(define (display-exp exp)
(mlet*
Ricardo Wurmus skribis:
> pelzflorian (Florian Pelz) writes:
>
>> On Wed, Jul 24, 2019 at 05:42:49PM +0200, pelzflorian (Florian Pelz) wrote:
>>> We could make a list of known bad GPUs.
>>>
>>
>> When thinking about it, a list of known bad GPUs might be legally
>> safer than saying AMD GPUs are
Hi Julien,
Julien Lepiller skribis:
> I gave a small tutorial to someone today, where we installed guix on top of a
> foreign distro. We used the script and everything went smoothly, and after
> finding out that we were going to build php (we were trying to define a VM
> that would serve one
Hi,
"pelzflorian (Florian Pelz)" skribis:
> On Wed, Jul 24, 2019 at 01:13:44PM +0200, Julien Lepiller wrote:
>> Hi guix,
>>
>> The online manual says it is available in other languages on its index page,
>> with links to… the current page. Can we fix that so one can switch to that
>> other la
Hi,
Julien Lepiller skribis:
> Hi guix, it seems that the devel version of the manual is not regenerated as
> intended. The website says that it's still from July 18th.
Indeed it fails like this:
--8<---cut here---start->8---
ludo@berlin ~$ sudo su - static
Tobias Geerinckx-Rice 写道：
Could anyone please update the libvirt package/service to this
latest
build?
I will do so swiftly since I updated libvirt to the 'broken'
version
(although I never had any troubles like yours). Thank you for
reporting this upstream.
I have applied ‘your’ patch in
Raghav,
On Thu, Jul 25, 2019 at 11:46 AM, Raghav Gururajan
wrote:
Hello Guix!
I posted the bug on libvirt mail list few days ago
(https://www.redhat.
com/archives/libvir-list/2019-July/msg01309.html). It appears the bug
has now been fixed
(https://github.com/libvirt/libvirt/commit/759bf903
Hi,
Ricardo Wurmus skribis:
>> I think it would be great to have the following variant of substitute*:
>>
>> (substitute*-once filename (pattern vars) body)
>>
>> which acts like the usual substitute-*, except it also asserts that the
>> substitution applies to exactly one line in the file, caus
Hi Simon,
zimoun skribis:
> As discussed here [1], the `relevance` in `guix/ui.scm` does not match
> "inter-field".
>
> Attached a fix.
> Now, the example from the manual
> $ guix search crypto library | \
> recsel -e '! (name ~ "^(ghc|perl|python|ruby)")' -p name,synopsis
> outputs t
Hello romulasry,
romulasry skribis:
> https://ibb.co/kyBrwRc
I don’t actually see a crash on this picture, just repeated messages
like:
AMD-Vi: Event logged [IO_PAGE_FAULT …]
Did the system actually crash or hang?
I suppose it would be worth reporting the issue to the kernel developers
bec
Hello Jan,
Jan skribis:
> What I did:Ran guix system installer from a DVD.When the system
> started I switched to tty3 mounted a flash drive and a partition in
> folders I made in /mnt/.Then I unmounted these disks and removed
> folders.Then I tried installing the system without any DE/WM.The
>
> Perhaps we should add gnupg-minimal for use in other package
> definitions.
That would actually be wise.
Regards,
RG.
Raghav Gururajan writes:
>> Is there a good
>> reason not to include pinentry-tty or somemthing similarly small?
>
> It appears pinentry-tty is only console-based. If graphical
> applications like MUA, Key Managers etc require pinentry-program, it
> usually uses pop-up (gui) for passphrase inpu
> Is there a good
> reason not to include pinentry-tty or somemthing similarly small?
It appears pinentry-tty is only console-based. If graphical
applications like MUA, Key Managers etc require pinentry-program, it
usually uses pop-up (gui) for passphrase input. Since pinentry provides
both cons
Raghav Gururajan writes:
> I still suggest that there should be a default/fallback option for
> this. After reviewing guix repository, I found pinentry, emacs-
> pinentry, pinentry-tty, pinentry-qt, pinentry-gtk2, pinentry-gnome3,
> pinentry-emacs and pinentry-efl, as available pinentry program
Hello Guix!
I am not sure whether someone patched this bug. There has been changes.
REPORTED ISSUE: After running first `guix pull` as "root" user, the
output for `which guix` and `hash guix` for that "root" user are always
`/run/current-system/profile/bin/guix` instead of being
`/root/.config/gu
Hello Guix!
I posted the bug on libvirt mail list few days ago (https://www.redhat.
com/archives/libvir-list/2019-July/msg01309.html). It appears the bug
has now been fixed (https://github.com/libvirt/libvirt/commit/759bf903a
6c24a8efa25c7cf4b099d952eda9bd3).
Could anyone please update the libvir
21 matches
Mail list logo
