On 23/07/19 16:40, Ben Sturmfels wrote:
>>> Interesting. Is this file installed to /etc/profile.d/vte.sh on other
>>> systems? Or is it otherwise sourced?
>>>
>>
>> I can only speak for my own system. I don't have gnome-terminal
>> installed, but I do have tilda which uses vte. My
>> ~/.guix-pro
On 23/07/19 16:35, Efraim Flashner wrote:
>> Interesting. Is this file installed to /etc/profile.d/vte.sh on other
>> systems? Or is it otherwise sourced?
>>
>
> I can only speak for my own system. I don't have gnome-terminal
> installed, but I do have tilda which uses vte. My
> ~/.guix-profile
On Mon, Jul 22, 2019 at 09:09:13PM +0200, Ricardo Wurmus wrote:
>
> Hi Ben,
>
> >> Just minor thing, but on other systems I use, when you open subsequent
> >> Gnome Terminal tabs, the current working directory is maintained in the
> >> new tab. On my Guix System, new tabs start up back at /home/b
are at
>> http://lilypond.org/janneke/guix/20190722/
>
> I built these, and here are the results:
>
> mhw@jojen /gnu/store/hd3lk0f08a0sq40qqa6yv1q9gbk7gxww-bootstrap-tarballs-0$
> sha256sum *
> b5915c71ff5ea722864e1097ce1e7ed50fd68ad7544521f2dd6969173c26
Hi Janneke,
> I have added a very similar set of two patches to wip-cu-binaries,
> branched @ ef809e3ac036eccc5f9c9edd8fb661d14ae15f2f.
>
> They give the same md5sum for me as the wip-binaries branch that
> branched off of master; so mine are at
> http://lilypond.org/janneke
https://ibb.co/kyBrwRc
Image uploaded to site because of:
Your request to the bug-Guix mailing list Posting of your message titled
"bug#36757: AMD-Vi IOMMU bug, kernel crashes using GuixSD 1.0.1" has been
rejected by the list moderator. The moderator gave the following reason for
rejecting you
Oh wow! Thanks for reporting that. It appears I have the same issue. I
enabled cups and I passively noticed sometimes but often cpu buffer
light blinking rapidly in my x200t even though I am not performing any
operations. Now checking the system monitor, what you say appears to be
true.
Regards,
R
Hi Ben,
>> Just minor thing, but on other systems I use, when you open subsequent
>> Gnome Terminal tabs, the current working directory is maintained in the
>> new tab. On my Guix System, new tabs start up back at /home/ben.
>
> I've found that sourcing vte.sh fixes the issue, and the working
>
61d14ae15f2f.
They give the same md5sum for me as the wip-binaries branch that
branched off of master; so mine are at
http://lilypond.org/janneke/guix/20190722/
After this commit should come the update-commit, using them in
bootstrap.scm.
HTH,
janneke
--
Jan Nieuwenhuizen | GNU LilyPond http://l
Hi Ricardo,
Interesting. I distinctly remember that there was no log file when I
looked last time. Hmm.
Anyway, it seems that now, all of the failed builds have either build
logs available or else information about which dependency failed. I
don't remember seeing any of this last time, but I'm
Dear,
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 the expected crypto libraries as `libb
Mark H Weaver writes:
> Unfortunately, I'm unable to get *any* information about what went wrong
> from Cuirass. None of the failed builds have associated log files, and
> the build details page has no useful information either. For example:
>
> https://ci.guix.gnu.org/build/1488517/details
https://ibb.co/kyBrwRc
Image uploaded to site because of:
Your request to the bug-Guix mailing list Posting of your message titled
"bug#36757: AMD-Vi IOMMU bug, kernel crashes using GuixSD 1.0.1" has been
rejected by the list moderator. The moderator gave the following reason for
rejecting you
Just to note that this is still a problem. I just installed
gnupg (via guix install gnupg), and gpg --generate-keys fails
due to missing pinentry. I had to find this bug report to
work around this.
Hi Chris,
Chris Marusich skribis:
> Ludovic Courtès writes:
>
>> Julien Lepiller skribis:
>>
>>> expected hash: 0zhd1ps7sz4w1x52xk3v7ng6d0rcyi7y7rcrplwkmilnq5hzjv1y
>>> actual hash: 0zycy85ff9ga53z1q03df89ka9iihb9p8bjhw056rq2y4rn3b6ac
>>> hash mismatch for store item
>>> '/gnu/store/1drx
Hi Mark,
Mark H Weaver skribis:
> Ludovic Courtès writes:
>
>> Robert Vollmert skribis:
>>
>>> The result was this:
>>>
>>> $ sudo herd restart nginx
>>> Service nginx is not running.
>>> herd: exception caught while executing 'start' on service 'nginx':
>>> Throw to key `srfi-34' with args `(
Hello!
Björn Höfling skribis:
> [env]$ git diff | more
> diff --git a/gnu/system/install.scm b/gnu/system/install.scm
> index 912096027f..3e692a5bdc 100644
> --- a/gnu/system/install.scm
> +++ b/gnu/system/install.scm
> @@ -428,6 +428,8 @@ Access documentation at any time by pressing
> Alt-F2.\
On Sat, 20 Jul 2019 17:17:21 +0200
Robert Vollmert wrote:
> > Robert and Björn, could you check if adding the ‘cirrus’ and
> > possibly the ‘cirrusfb’ module(s) to ‘initrd-modules’ in the image
> > you run at your VPS solves the issue?
>
> It would need to be added to the installer. Is there a
On Thu, 25 Apr 2019, Ben Sturmfels wrote:
> Hi Folks,
>
> Just minor thing, but on other systems I use, when you open subsequent
> Gnome Terminal tabs, the current working directory is maintained in the
> new tab. On my Guix System, new tabs start up back at /home/ben.
I've found that sourcing vt
Hi Janneke,
Jan Nieuwenhuizen wrote:
>> What I need is a way to build the new bootstrap tarballs without using
>> the existing 'core-updates' branch. I need a way to build them from a
>> branch that's based upon the much older bootstrap binaries that we've
>> been using for many years. Preferab
ols and mes
bootstrap tarballs.
I have put the results of
--8<---cut here---start->8---
./pre-inst-env guix build --system=i686-linux mes-minimal-stripped-tarball
./pre-inst-env guix build --system=i686-linux
mescc-tools-static-stripped-tarball
--8<-
21 matches
Mail list logo
