bug#36747: Official MesCC bootstrap binaries differ from my locally built ones

2019-07-22 Thread Mark H Weaver
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

bug#36770: AMD-Vi IOMMU bug, kernel crashes using GuixSD 1.0.1 resubmit

2019-07-22 Thread romulasry
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

bug#36481:

2019-07-22 Thread Raghav Gururajan
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,

bug#35424: Gnome terminal doesn't keep current working directory in new tab/window

2019-07-22 Thread Ricardo Wurmus
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 >

bug#36747: Official MesCC bootstrap binaries differ from my locally built ones

2019-07-22 Thread Jan Nieuwenhuizen
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:

bug#36754: New linux-libre failed to build on armhf on Berlin

2019-07-22 Thread Mark H Weaver
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

bug#36763: `guix search` does unexpected logical and

2019-07-22 Thread zimoun
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

bug#36754: New linux-libre failed to build on armhf on Berlin

2019-07-22 Thread Ricardo Wurmus
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: > >

bug#36757: AMD-Vi IOMMU bug, kernel crashes using GuixSD 1.0.1"

2019-07-22 Thread romulasry
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

bug#24076: gnupg [-agent]: when signing [commits], it claims that there is no pinentry - but there is

2019-07-22 Thread Robert Vollmert
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.

bug#36363: let's encrypt hash mismatch

2019-07-22 Thread Ludovic Courtès
Hi Chris, Chris Marusich skribis: > Ludovic Courtès writes: > >> Julien Lepiller skribis: >> >>> expected hash: 0zhd1ps7sz4w1x52xk3v7ng6d0rcyi7y7rcrplwkmilnq5hzjv1y >>> actual hash: 0zycy85ff9ga53z1q03df89ka9iihb9p8bjhw056rq2y4rn3b6ac >>> hash mismatch for store item >>>

bug#36731: shepherd lost track of nginx

2019-07-22 Thread Ludovic Courtès
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

bug#36069: Menu-based installer unusable through noVNC

2019-07-22 Thread Ludovic Courtès
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 >

bug#36069: Menu-based installer unusable through noVNC

2019-07-22 Thread Björn Höfling
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

bug#35424: Gnome terminal doesn't keep current working directory in new tab/window

2019-07-22 Thread Ben Sturmfels
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

bug#36747: Official MesCC bootstrap binaries differ from my locally built ones

2019-07-22 Thread Mark H Weaver
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.

bug#36747: Official MesCC bootstrap binaries differ from my locally built ones

2019-07-22 Thread Jan Nieuwenhuizen
sults 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<---cut here---end--->8--

bug#36747: Official MesCC bootstrap binaries differ from my locally built ones

2019-07-22 Thread Jan Nieuwenhuizen
Jan Nieuwenhuizen writes: > Hmm, I'm not sure how much work it would be. If we're lucky then the > recipes from gnu/packages/bootstrap.scm *gnu/packages/make-bootstrap.scm -- Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar®