IRC channel logs


back to list of logs

<roptat>hi guix!
<rekado>Hi Guix
<rekado>Laalf: you can export the store with “guix publish”
<rekado>Laalf: it spawns a web server and can serve substitutes like the build farm.
<rekado>I see a bunch of messages about problems with substitutes from berlin. Is this still a problem?
<roptat>rekado: I think the issue is when you try to install guix 0.15.0, berlin doesn't have all required substitutes for this version
<civodul>Hello Guix!
<kmicu>( ^_^)/
<XWill1>Hi, i'd like to have the button for screen rotation working and i think this error from eudev is related: udevd[191]: Unknown key identifier 'direction'
<XWill1>do you have some clues for me?
<mbakke>XWill1: Do you get that error when pressing a hardware button? Did you add any custom udev rules?
<XWill1>No this error is at boot time, i have a custom rule for a wacom tablet, but this 'direction' key is in hwdb rules
<XWill1>KEYBOARD_KEY_6c=direction # rotate
<rekado>roptat: I guess we could rebuild them.
<rekado>roptat: I’m currently busy but I can give this a try later.
<XWill1>I tried setkeycodes 6c 153, then herd restart udevd => it restarts the X server and rotation is working
<XWill1>i'd like to config this in my config.scm
<XWill1>My guess is that the udevadm doesn't know that direction=153 when it builds the hwdb.bin
<jlicht>hey guix
<g_bor>hello guix!
<g_bor>After a recent problem on my system I could partially reconver, but I sometimes get messages like error: build failed: getting attributes of path ... : No such file or directory.
<g_bor>Do you know how to get this sorted out?
<rekado>g_bor: corrupt store?
<g_bor>rekado: most probably yes.
<g_bor>Or rather a corrupt database...
<g_bor>Don't know
<g_bor>It says that I have a certain item in store, but it is not in there in fact.
<g_bor>for example I have this for libx11, gui build returns only the two strings, corresponding to the store item names, but those items are not in the store.
<pkill9_>how do i use `git format-patch` for sending a patch to
<g_bor>pkill9_: you use git format-patch to generate the patch, and you can send that with git send-email.
<g_bor>rekado: bioconductor 3.8 is released, and it seems that the 3.7 tarballs are not available any more.
<g_bor>Do we have to do something? (I guess yes :) )
<pkill9_>g_bor: but how do i generate the patch? running `git format-patch` doesn't output anything
<g_bor>pkill9: for example to create a patch from the last commit you can do git format-patch -1
<pkill9_>ah ok
<rekado>g_bor: yes, we’ll have to upgrade everything.
<rekado>I can do this tomorrow.
<rekado>but the tarballs really should still be available.
<rekado>I’m using 0.15.0 to build a system on Berlin. This should get us more substitutes for people installing from 0.15.0.
<rekado>g_bor: this still exists:
<rekado>so everything should be fine.
<rekado>“bioconductor-uri” hands out the primary URL and falls back to the Archive URL if that fails.
<rekado>I’ll update to 3.8 tomorrow.
<g_bor>rekado: ok, we noticed this as we were trying to use the importer
<pkill9_>the guix-patch mailing list seems to have butchered part of the patch in attempt to hide email addresses:
<pkill9_>actually nevermind, i assume it's only butchered in the web mailing list browser
<kmicu>Thank you rekado for building that 0.15.0 revision on Berlin.
<verisimilitude>Hello there.
<verisimilitude>I have a quick question regarding something I've heard: Is Guix now packaging Common Lisp libraries?
<verisimilitude>This is something I'd wanted to help with for a while, but I had other obligations that prevented me from progressing with respect to that. If this is the case, I'd like to know any way I can help.
<verisimilitude>If I heard wrong, I suppose now is as good a time as any to start progressing with this, in any case.
<verisimilitude>I don't know how this is working, if it is, but I had an idea for it I'd like to discuss, being a heavy Common Lisper, if that's fine.
<verisimilitude>I'll just wait for a response, now.
<rekado>verisimilitude: yes, there are a number of packages for common lisp libraries in Guix
<verisimilitude>Now, I'd not checked, but is this recent; I don't recall this being the case months back.
<verisimilitude>I may have simply overlooked things, however.
<verisimilitude>Is there any central person overlooking this, rekado?
<efraim>you can check git blame to see who's been working on the packages, I haven't been paying much attention to the lisps much
<verisimilitude>I suppose I can install git if I need to; is there, say, a gitweb interface for checking this, though?
<efraim>Perhaps this?
<verisimilitude>That's good; I appreciate it, efraim.
<verisimilitude>It seems a Pierre Neidhardt has been doing most of this work, so I should talk my ideas over with him.
<verisimilitude>I've taken care of that now; again, I appreciate the help from both of you.
<Laalf>i cant guix pull because guix pull: error: symlink: File exists: "/var/guix/profiles/per-user/user/current-guix"
<Laalf>also i dont quite understand how you configure offload. if someone has a more extensive instruction that would be nice.
<g_bor> hello guix!
<Laalf>is there some magic i can do to fix guix pull: error: symlink: File exists: "/var/guix/profiles/per-user/user/current-guix" ? can i delete current-guix safely?
<pkill9_>dunno, i think some others have had the same issue
<g_bor>hello Laalf, yes, some others had this issue.
<g_bor>I also can't say much more about that, I could not reproduce it so far.
<pkill9_>if i thappened to me, i would try moving the symlink to 'current-guix.backup' and doing it again, but I dunno if that will bork anything so don' thold me responsible
<g_bor>pkill9_: it might break the user profile, but root and system profiles should be kept intact...
<Laalf>also i tried guix offload. what does "GSSH ERROR] Unable to import a key from the file:" tell me?
<g_bor>I don't know what checks are run there, but I believe that pulling then would not break anything.
<g_bor>changes in the user profile might get lost, but if you use manifests you cn easily recover from that.
<g_bor>Laalf: I did not try that yet.
<g_bor>people, it seems that problems around python-minimal might escalate. WDYT?
<g_bor>As of now we have substitutes, but something does not seem right there.
<g_bor>We have two reports of a possible memory leak in the test suite.
<Laalf>g_bor: does guile-ssh take openssh keys?
<g_bor>it has 5324 rdeps.
<g_bor>Laalf: yes, I did try that.
<Laalf>g_bor: i generated my openssh key and set /home/user/.ssh/id_rsa in my /etc/guix/machine.scm
<civodul>Laalf: OpenSSH public keys are accepted:
<g_bor>hello civodul!
<g_bor>Did you see these recent issues with python-minimal?
<civodul>g_bor: i did! i'm not sure what can be done
<civodul>other than hoping for substitutes to be available
<Laalf>civodul: i copied the file to /root/ and it still cant import
<civodul>Laalf: what does 'guix offload test' report?
<g_bor>Could we patch that test out, or maybe update to somewhere after the fix?
<g_bor>it seems #33213 has a promising solution.
<g_bor>also, we could merge #33248,#33213 and #33223 to have all info together.
<Laalf>civodul: private-key-from-file: [GSSH ERROR] Unable to import a key from the file:
<civodul>Laalf: are you sure you specified a private key file and not a public key file in the 'private-key' field?
<Laalf>civodul: [GSSH ERROR] Unable to import a key from the file: "/root/.ssh/id_rsa"
<civodul>i'd suggest making sure the file is 600, and double-checking its content
<Laalf>civodul: its 600. the start of it looks like the start of an 80s song
<Laalf>so about right
<ng0>how does an ssh key look like the start of an 80s song?
*civodul was wondering too :-)
<ng0>ah, chords
<lsl881>hi! I am creating a patch for guix.texi
<civodul>hello lsl881, neat!
<verisimilitude>Hello, lsl881.
<lsl881>I wanted to know if it is OK to use makeinfo to check everything is alright for almost all available formats. The point is that for the --pdf option I am installing texlive and it is taking long. I am using the substitutes option but it takes long too
<lsl881>It is downloading like 2GB
<verisimilitude>Have you tried installing texlive-tiny instead, lsl881?
<verisimilitude>I had a similar issue.
<g_bor>it seems we also have an issue with nss.
<g_bor>it has 812 revdeps.
<g_bor>Now fails its testsuite consistently.
<g_bor>It seems that we will have to wait for staging for a while, so this also seems a candidate for grafting.
<civodul>grafting wouldn't help though, because you'd still need to build the actual thing
<civodul>mbakke wrote that the memory leak in the test suite showed up only with recent kernels, right?
<g_bor>sey, that is right for the python issue.
<g_bor>The nss issue is because of an expired certificate.
<civodul>oh, what's the nss issue? :-)
*civodul catches up after a week of vacations
<g_bor>It is only on help-guix yes, Björn had a look, it fails its test suite.
<g_bor>good night!