IRC channel logs


back to list of logs

<quiliro>kirisime: what does this do?: (derivation-outputs (<the_package_derivation>))
<quiliro>jort: nice
<jort>don't applaud quite yet, good intentions aren't enough
<quiliro>jort: the are the base of good results
<kirisime>It lists you the outputs of the package built package?
<quiliro>fake intentions aren't enough but true intentions some day get results
<dftxbs3e>jonsger[m]: -- reproduce my setup to hack on GNU Guix for powerpc64le-linux
<jort>quiliro, In any case, it's the corporate cloud services I really want to get away from - that's my main motivation.
<erudition>dftxbs3e oops I was gonna mention, an implementation of PARSEC does exist. They released the source code. But anyway, off topic.
<dftxbs3e>erudition: it's not complete, it doesnt have the byzantine tolerance
<dftxbs3e>which is the challenging part
<dftxbs3e>" Foolproof handling of malice " -- not implemented
<quiliro>i need a guile tutorial!
<kirisime>I need a guix documentations!
<quiliro>info guix
<quiliro>i have seen some videos too and blogs also
<quiliro>did you see the packaging tutorial?
<erudition>Oh ok
<kirisime>There honestly isn't much there
<zaab>alright, this is a very noob question: i try to compile, but it fails because it cannot find math.h
<quiliro>i have searched outside of guix also
<erudition>Well I'd think the proof could be machine-verified anyway
<excalamus>kirisime: I'm working through the manual now. Here is what I've found helpful...
<erudition>Then you need only peer review the input assumptions
<excalamus>kirisime: If you're familiar with Emacs, reading the info files in there is very convenient. Excellent searching capabilities, plus, you can take notes with org-mode easily in another buffer. If not, just use the regular 'info guix' in the CLI.
<excalamus>kirisime: Everything documentation-wise seems to be on the cgit repo. Let me grab that for you. It's technically at the bottom of the Guix documentation page, at the veeeery bottom.
<excalamus>kirisime: scratch that last one. That's the maintenance git.
<excalamus>kirisime: Those seem to be the git repos. Under videos are the sources for the videos hosted on
<excalamus>kirisime: Also, I found under the maintenance repo a collection of talk notes, as well as links to those talks:
<excalamus>kirisime: I know that's a lot. I have a few minutes before my g/f gets home. I'm happy to help if I can.
<excalamus>kirisime: Message me on sneek (however the heck that's done) if I log off.
<kirisime>excalamus: Thanks a bunch, I'll look over these if I can't find what I'm looking for elsewhere
<excalamus>kirisime: You're welcome! I stumbled upon the git repo stuff yesterday.
<quiliro>sneek_: later tell exclamus: there are videos on mediagoblin
<jort>quiliro, dftxbs3e I'm unable to reproduce the install issue now, but the network connection to does seem to hang quite aoften
<quiliro>jort: ok
<quiliro>the video tutorials are just intro
<quiliro>to make packages, i think there is a blog post
<quiliro>plus the manual of course
<quiliro>info manual
<excalamus>quiliro: I'm interested in packaging and read through the tutorial you mentioned. I was inspired, but a little lost on where to start. I'm re-reading the manual (and taking notes). I may need to go shortly, but I would appreciate knowing I can ask broad, potentially bone-headed questions.
<sneek_>Welcome back excalamus, you have 1 message.
<sneek_>excalamus, quiliro says: there are videos on mediagoblin
<quiliro>sneek_: later tell excalamus here is the message bot
<quiliro>excalamus: i think emacs-guix also helps
<quiliro>excalamus: and reading the source is also possible with emacs-guix
<quiliro>nice curses interface too
<quiliro>well, rather emacs interface
<excalamus>In what way does emacs-guix help? In reading the manuals? I'm an avid Emacser, but, honestly, felt overwhelmed at reading another manual.
<sneek_>excalamus, you have 1 message.
<sneek_>excalamus, quiliro says: here is the message bot
<quiliro>excalamus: just use it: M-guix <enter>
<quiliro>it is easier to use than to read the manual
<quiliro>but later you can skim the can do it in 30 minutes
<excalamus>mmk, silly question "How does Emacs make things better?", lol. It's Emacs! I'lll give it a look over.
<quiliro>it it more like a dictionary
<excalamus>I appreciate you talking with me. I have to go, g/f's home, but I may be on later. Thanks you! :)
<zaab>Am I supposed to configure e.g. vim from guile?
<quiliro>zaab: i do not think so...unless you want to change compilation options
<quiliro>if you want to compile vim a diferent way than default, you can make a new package with guile
<quiliro>zaab: but user config of vim i do not know how it is done...probably on a file on the user home directory
<quiliro>zaab: maybe addons could need to be installed via guix
<zaab>quiliro: alright so I still configure i3, vim, etc from their normal configs?
<quiliro>i have configured is just changing the .i3.conf file i think
<quiliro>it was just editing a file in the home
<zaab>in my system config, I appended set-xorg-configuration to services. Why is that different?
<zaab>would be nice to configure the entire system in scheme maybe, but I do not know if it is intended
<quiliro>zaab: because xorg is handled by the system, not by the user...i do not like that either
<quiliro>i would like each user to start their own X session
<quiliro>with startx
<zaab>quiliro: you think it is wrong to add i3 to system packages?
<quiliro>yes...but that is the way it is done
<quiliro>kirisime: did you check ?
<zaab>quiliro: lets say I have defined in my system a user named zaab. Can I also choose some packets specific to that user?
<quiliro>yes you can...i have not done that, but you can
<quiliro>inside that user definition there must be a manifest
<zaab>quiliro: I am completely new. Where can I look up how to do this?
<zaab>(and look up what a manifest is)
<quiliro>perhaps it is described in the info manual
<quiliro>zaab: a manifest is a list of packages :-)
<quiliro>sometimes it is in a separate file
<quiliro>zaab: do you have emacs installed?
<minall>Kiel vi fartas guix!
<minall>quiliro: What does zaab wantsP
<quiliro>minall: saluton. ni fartas bone:
<zaab>quiliro: I do not. I would like to take part of the emacs community sometime, but right now I am already dealing with a lot of unfamiliar software
<minall>quiliro: bone!
<quiliro>he want to define packages a user will have installed on the system configuration file
<minall>quiliro: wow, that's specific
<quiliro>emacs makes things easier...and you can use your mouse just as with any other editor
<quiliro>with emacs and emacs-guix, hacking is much easier
<minall>It is
<quiliro>hacking guix is
<quiliro>minall: is also a newbie! but he has learned very quickly
<quiliro>it is important to have a patient mentor in order to that so minall?
*quiliro is patient?
<quiliro>but as soon as you want to get serious, you can type Alt-x guix <Enter>
<quiliro>Alt-x is usually named M-x
<kirisime>quiliro: I've read that page many times over and I'm not sure how it'd be useful to me now
<quiliro>not all keyboards have Alt
<kirisime>Well, maybe I just need some sleep
<quiliro>kirisime: what page?
<kirisime>Defining packages
<quiliro>oh...i am still a newbie with that too
<kirisime>This thing depends on imagemagick, but the configure script doesn't find it correctly and it fails even if every environment variable gets set right
<quiliro>kirisime: i think that knowledge of guile synthax would be the important thing on your level of knowledge
<quiliro>kirisime: why don't you check the source code to how other packages do it?
<kirisime>Going into the build directory in guix-environment, sourcing the environment-variables file and running ./configure --with-imagemagick=/gnu/store/...-imagemagick actually works though
<quiliro>then you can copy and paste almost
<minall>quiliro: Yes!, you are jaja
<zaab>quiliro: I read the info page on the user definition
<zaab>I cant find a place to leave the user packages
<kirisime>'s called %build-inputs
<quiliro>kirisime: %build-inputs are the user pacages on the user definition?
<quiliro>zaab: search manifest on the guix info manual
<quiliro>and maybe there could be something
<zaab>thanks. I will look tomorrow. sleep tight
<quiliro>minall: veo que has escritu tu bitácora pero no has indicado algo interesante, cómo hiciste o qué retos ha habido...además no hay lo de hoy
<excalamus>Hi, guix!
<excalamus>I'm a bit confused by ~/.config/guix/current. It links to a different guix than ~/.guix-profile. Why the need for ~/.config/guix/current?
<apteryx>rekado: re ice-9 and guix records; in the case of guix, it seems the constructor is implicitly built, and never used explicitly, correct?
<apteryx>Then what is the use of specifying its name (e.g., the make-operating-system constructor defined for the 'operating-system' record is never used explicitly. Then why require it to be named at all? I wonder :-)
***scs is now known as Guest49074
<leungbk`>efraim: I read your message about the problems with the recursive crate importer. I think we can deal with the problem of duplicate recipes appearing by ensuring the #:cargo-development-inputs do not contain entries that are already in #:cargo-inputs (and also making sure the same #:cargo-input doesn't appear more than once in a given recipe). Do you expect this to cause any problems during the build phase of a package?
***Sleep_Walker is now known as Guest50077
***scs is now known as Guest92488
***scs is now known as Guest67683
<efraim>sneek later tell leungbk` I'm not sure about making sure packages only appear in cargo-inputs or cargo-dev-inputs, but the package definition only needs to happen once
<efraim>sneek_: botsnack
<reepca>so I've been running the tests and I'm noticing that all the importers seem to expect to be using newer versions of guile-json (where objects are alists instead of hash tables), but our package definition for guix specifies guile-json-1. Consequently most importer tests are failing.
<reepca>never mind, just checked the backlog and saw it's already mentioned
<apteryx>could someone tell me what is "this-thing" referring to in the (guix records) define-record-type* docstring?
<apteryx>seems to be optional (defaulting to the object id)
<apteryx>I don't quite understand but I haven't seen it being used in the Guix sources
<apteryx>hmm, actually, it is in (gnu system) --> this-operating-system
<reepca>on a different note, pinentry is a gpg thing, right? magit is failing to prompt me for a password for an ssh key.
<apteryx>right, it's released by the GPG group
<apteryx>I'm using gpg-agent as my ssh-agent, maybe that's why it's important in my case... I forgot what ssh-agent does... Maybe it uses pinentry as well?
<reepca>apteryx: how does one specify that?
***scs is now known as Guest24351
<reepca>hmm, well, I put enable-ssh-support in my ~/.gnupg/gpg-agent.conf, restarted it, and set SSH_AUTH_SOCK to the result of 'gpgconf --list-dirs agent-ssh-socket', but the prompt still shows up in the magit-process buffer and I can't enter anything.
<reepca>on manually running ssh-add it asks for the passphrase for the key in the terminal, then after that it asks for a password to protect it with in a graphical dialog box
<rekado>bgardner: unfortunately, I wasn’t able to make LDAP authentication work.
<rekado>I can do “su ldap-account” only if I also prefix the command with LD_LIBRARY_PATH pointing to /gnu/store/…-nss-pam-ldapd-0.9.10/lib/
<rekado>otherwise it doesn’t even try talking to LDAP
<reepca>is tests/ outdated? It looks like it should have been changed with commit 4d04bc50d2df32be326e0f48f378dc581f873989 2 weeks ago to match the new behavior of recognizing version tags and dropping the "v" at the start.
<reepca>currently it's failing on line 56 because the version field is "0.1.0" now instead of "git.v0.1.0"
***scs is now known as Guest96831
***scs is now known as Guest81298
***Guest50077 is now known as Sleep_Walker
***scs is now known as Guest55595
<vagrantc>hadn't seen any updates to master for a while ... just cooincedence, or is there some reason not to push that i missed?
*vagrantc tries pushing
<dftxbs3e>10 minutes ago there was a push
<minall>Hello guix!
<efraim>It's Sunday, Sunday is normally slow
<quiliro>minall: saluton, kiel vi fartas?
<minall>quiliro: MI fartas bone, cu ja vi
<quiliro>Mi fartas bone ankaŭ. :-)
<bandali>so, uh, what’s the turnaround time for simple patches like adding a new emacs package?
<vagrantc>bandali: it really depends on who has time to review
<bandali>vagrantc, right
*vagrantc wonders if upgrading pyqt requires upgrading qt first
<vagrantc>upgrading electron-cash whines at the user when running pyqt older than 5.12.x
<vagrantc>seems to work fine...
<vagrantc>but that's pretty annoying
<efraim>I found the pyqt version is tied to the qt version
<efraim>5.12 wasn't just a version bump, only reason I haven't done it yet
<vagrantc>efraim: and now looks like 5.13 is also available...
<vagrantc>nothing urgent, just curious
<efraim>I used to do it on my firefly
<numerobis>Hi guix! I was wondering whether there was a plan to package ripgrep, or a reason for not including it? I assume there must be some technical issue?
***scs is now known as Guest54076
<vagrantc>numerobis: probably just needs someone to do it
<numerobis>vaarantc: All right, thanks!
<vagrantc>that said, i've not tried packaging any rust stuff, so there could be technical blockers i'm clueless of :)
<numerobis>vaarantc: That's what I would think, considering how popular ripgrep is and the large amount of other packages that guix now offers. :)
*vagrantc had no idea ripgrep was the killer app of the modern experience :)
<quiliro>minall: kiel vi faras la studon de la kontrolilo komputila Stallman habla de servicios de comunicaciçon como libres si te permiten
<quiliro>Minall: Kiel vi faras la studon de la komputila kontrolil?
<zaab>hey team. I dont know how to run xmonad on guix. I tried going into the xmonad environment and then I run `ghc ~/.xmonad/xmonad.hs`, but the build fails
<xavierm02>zaab: You probably need to use xinit / startx somewhere
<zaab>sorru my internet shut off
<xavierm02>zaab: You probably need to use xinit / startx somewher
<zaab>xavierm02: I never would have guessed that. Why is that? I am experimenting now
<xavierm02>Are you just trying to start xmonad, or doing something else?
<zaab>xavierm02: I guess I am trying to configure xmonad
<xavierm02>that should be the same thing as on any other os
<xavierm02>or package manager
<xavierm02>depending on whether you ar eusing guix or guixsd
<xavierm02>Try creating a ~/.xinitrc file with "exec xmonad" in it
<xavierm02>and then run startx
***scs is now known as Guest98825
<quiliro>xavierm02: that will not work with guix system
<quiliro>the xorg server is started by herd
<quiliro>by using sudo herd status xorg-server
<quiliro>you can see if it has started
<quiliro>the users cannot control the X server
<quiliro>they can only login
<malaclyps>so I did a guix pull, than a guix package -u, and now sway is kinda broken on my machine. Rolling back the upgrade makes it work again, but I'm interested in working out what might have happened.
<malaclyps>I can't see a change in the guix "sway" package definition, and looking in the /gnu/store for the sway directories, I can see that the binary is the same, but it links to a few differing libraries
<malaclyps>is there a way to see what/how might have prompted those changes between two guix package generations?
<rekado>malaclyps: when inputs to a package change, the package is rebuilt with these changed inputs.
<rekado>malaclyps: you can take a look at the Guix git repository to see how these inputs may have been changed.
<malaclyps>rekado: ah, good idea thankyou
<malaclyps>I've now rolled back a generation, and upgraded everything *except* sway, which makes it less of a problem, but I'm still curious!
<malaclyps>if the inputs to those inputs changed, would it also be rebuilt?
***scs is now known as Guest76012
<tune>I keep failing to generate a gpg key because "No pinentry" but I installed the package "pinentry"
<tune>I have tried again a few times, starting a new shell and such, running "hash guix"
<tune>not sure what the issue is
<tune>gpg: agent_genkey failed: No pinentry
<tune>Key generation failed: No pinentry
<rekado>tune: you need to tell GPG about it. In .gnupg/gpg-agent.conf I had to add “pinentry-program /home/rekado/.guix-profile/bin/pinentry-gtk-2”
<tune>okay, thanks. I'll try that
<tune>still having the same problem... worth noting that I didn't have that file yet so I just created it and added a line like that as the only line
<rekado>which pinentry did you install?
<rekado>does the file name you provided correspond to the pinentry program you installed?
<tune>just plain old "pinentry", and I tried just having it point to that also
<GNUtoo>hi, is it possible to run guix in lxc?
<GNUtoo>I tried to make lxc run that through virt-manager / virsh: /gnu/store/9alic3caqhay3h8mx4iihpmyj6ymqpcx-guile-2.2.4/bin/guile --no-auto-compile /gnu/store/c7qcancm3bj3294l6krhsyr96wn3h0mk-shepherd-0.6.1/bin/shepherd --config /gnu/store/19fzhcg975bmxhhicf2nnp56sbsv8wsy-shepherd.conf
<GNUtoo>it boots then crash with "bad file descriptor"
<tune>rekado: ah I had to reload the agent, it works now!