<vagrantc>ok, 33 packages, each in their own individual commit. on to the next typos...
<krafter>How can I add programs to startup automatically when I log in? Does adding for example "exec redshift &" to "~/.profile" work?
<sebboh>I all. I downloaded the 1.0.0 bootable image earlier this month. Now a newer one is available. Can I boot the old one and 'update' it? Or should I just go ahead and download the new one?
<sebboh>krafter: if guix system is like other unix environments... and if you're logging into the console... then this line from the bash manual will be relevant: When bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first reads and executes commands from the file /etc/profile, if that file exists. After reading that file, it looks for ~/.bash_profile,
<sebboh>~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable. The --noprofile option may be used when the shell is started to inhibit this behavior.
<sebboh>There are specific criteria that define "interactive login shell".
<vagrantc>sebboh: you might be able to install with 1.0.0, but 1.0.1 specifically fixed a number of installer issues
<krafter>So, .profile wont run if I login non-interactively?
<sebboh>krafter: more than that.. .profile is sourced in by bash. (and maybe other shells.) Does "log in" mean "start bash" on your system? I see now that "redshift" is a program that interacts with x11, so, maybe not?
<sebboh>vagrantc: I didn't see my specific issue in the changelog. But I'll give it a shot.
<sebboh>krafter: I have only questions. :) It's not safe for me to assume you are using some popular desktop environment, because here we are in #guix.
<krafter>sebboh: "exec startx" is the line right below the one I posted above. :-D So its not strange that it doesn't work.
<krafter>There is a service runner on guix called shepherd, but I have not yet figured out how it works.
<sebboh>krafter: oh. so when you log in... your login shell starts X for you. Cool. I have to type startx every time. :) Well once your X is running you may have better luck running redshift. Do you know about .xinitrc?
<sebboh>Sorry, actually, I did finish the installation but the resultant OS didn't have whatever package the 'ip' command comes from, so I couldn't get online, so I couldn't install packages.. I gave up quickly and booted back into the installer and tried to make a better config. Maybe 1.0.1 will let me use the menu-based installer.
<kabo>lunch time, see you later, hopefully it's done building when I get back
<str1ngs>kabo: I hope that made sense. basically yes it a fork. but it also expose your changes to guix. eventually if you want to contribute them back upstream. you can submit patches
<nckx>kabo: A channel doesn't need any metadata files or anything, just guile modules: if you want to add (kabo packages gnome), just create ~/your-channel/kabo/packages/gnome.scm that starts with ‘(define-module (kabo packages gnome) …’ — that's it.
<nckx>(You can even add file:// URLs to your channels.scm if you don't want to host it just yet. But do note that ‘guix pull’ will not see uncommitted changes to that directory!)
<nckx>krafter: You can extend etc-service-type to add any file(s) to /etc: (define %my-service (simple-service 'store-my-configuration etc-service-type `(("modprobe.d/foo.bar" ,(local-file …
<nckx>(Untested, and you can probably specify a string directly in place of ,(local-file) in simple cases like yours.)
<krafter>str1ngs: Yes and I am jealous. Is logging in easy with circe?
<str1ngs>krafter: it can log, but I don't use it myself
<nckx>sneek: later tell nireno: No, there's only one ISO(hybrid) installer image. You should ask on firstname.lastname@example.org as well; the person whom I know has the most experience with partitioning the installer is hardly (ever?) on IRC.
<str1ngs>so as much as it's been dated. it only dated because GNU is old. but that doesnt mean it's not useful of has a purpose.
*nckx was never convinced by the supposed arguments for wikis over manuals, but it's easy to prove them wrong. If wikis really do draw magical contributors that manuals can't, I do hope they start a wiki soon 😛
<str1ngs>I've personally got used to using GNU manuals. my whole guix setup etc. has come from the manual.
<nckx>There's a lot of room for improvement with the manual: all the service overviews are maintained *in the manual*, not exported from the code. That's a huge duplication and the drift apart is real.
<str1ngs>yeah, but that takes man power. only way to fix that is to contribute :P
<krafter>The issue I have with both Emacs and Guix manuals is that they provide very little examples.
<str1ngs>I guess the services could be snarfed into the manaul. like guile does it?
<nckx>That's a lot easier to fix in a manual than a stateful wiki ‘app’, which will have an ‘API’, and…
<Marlin[m]><krafter "And a manual instead of a wiki."> Manuals are great, i think they are nice for the basics, but wikis are better for really specific parts
<nckx>Some people here mean wiki in a stylistic sense (hopefully the ‘cook book’ being discussed on the ML will address that audience), others (including me) assume it's an actual wiki with pages and accounts and spam and vulnerabilities and… Not saying both aren't reasonable, but it's not the same discussion.
<Marlin[m]>I think a manual would get kinda messy with too many specifics
<Marlin[m]>Imagine the entire archwiki in a single manual
<str1ngs>meh, the archwiki needs it cause, hardly anything works out of the box. not to mention archlinux is not declarative
<nckx>There's the ‘cultural’ definition of wiki again. A section like ‘choosing an IRC client’ would suit the cookbook just fine, but then that might be because it doesn't exist and can be whatever one dreams it to be ☺ Still, no need for a cumbersome Web-only CMS in any of that.
<Marlin[m]>What parts does the manual lack translating and documenting atm?
<Marlin[m]><nckx "There's the ‘cultural’ definitio"> You can usually download wiki articles
<notnotdan>Suppose I have a file A.scm which defines a package B and returns an expression that denotes the package A (in this case A depends on B). Usually I would install A by running `guix package -f A.scm`. But how can I install both A and B in this case?
<degrees380>Hi Guix, today my "guix pull" (with no --verbose options) give me a very vebose output "@build-log"; it's the first time I see such behaviour: is it normal?
<degrees380>I tryied using two different machines (and guix versions) with the very same result
<degrees380>any of you "guix pull"ed today in the "normal" way?
<kdtsh>Hi all! I took a cursory glance at the chat logs to see if other people are having a similar issue to me when doing a 'guix pull' and it seems like there are other folks. I also can't connect to ci.guix.gnu.org (though I don't know if ping get eaten by a firewall). I get logging which indicates that curl has failed to build; there's also none of th
<kdtsh>e usual messages saying that substitutes have been fetched from the official substitute server. Two issues here? - curl 7.65.0 failing to build, and can't connect to the official substitute server?
<g_bor[m]>bgardner: On a foreign distro the following things should be done: guix pull to update guix for the user, for each user you would like to have the updated guix. guix package -u for each user, to update their packages to the version provided by the new guix. guix pull as root to update root's guix, simply sudo guix pull won't work here, you will have to be in an evironment that is a root login shell, or otherwise prepare the
<g_bor[m]>env to pull for the root guix. (This is needed fr example to get the daemon to find the locales), then the service files starting up the guix daemon should be updated, to start up the version of the daemon from the freshly pulled root's guix, and the guix-daemon should be restarted. That's about it.
<g_bor[m]>But doing guix pull and guix package -u for your user will give you all that is needed, except it won't update the daemon.
<bgardner>g_bor[m]: Ah, thank you - updating the daemon was my question.
<roptat>kdtsh, have ci.guix.gnu.org ever worked for you, or is it the first time you're trying guix?
<roptat>(and, is it guix system or guix on a foreign distro?)
<kdtsh>roptat yes it's worked for me up until today. I'm running guix system in a VM
<degrees380>g_bor[m]: you said the first pull is verbose on 1.0.1, and the second?
<brendyyn>g_bor[m]: fatal error: gst/audio/gstaudiofilter.h: No such file or directory
<brendyyn>its because of that, but that file is in gst-plugins-base. im not sure why it doesnt find it
<rekado>brendyyn: maybe because the include path doesn’t include the sub-directory containing the file.
<bgardner>Calling 'crontab -e' yields '(copy-file "/tmp/crontab.951" "/var/cron/tabs/username")" followed by 'In prodedure copy-file: No such file or directory.' /tmp/crontab.951 exists, it's /var/cron/ that is missing. Do I need to do something to prepare user crontabs under mcron?
<archetyp>@ unsupported-platform /gnu/store/q8gmnxhfiqbp9f1jj668k50b64fw7rh0-curl-7.65.0.drv armhf-linux while setting up the build environment: a `armhf-linux' is required to build `/gnu/store/q8gmnxhfiqbp9f1jj668k50b64fw7rh0-curl-7.65.0.drv', but I am a `x86_64-linux'
<kmicu>donofrio__: when you install a package e.g. ‘guix install inxi-minimal’ there is a hash printed in its output … /gnu/store/hash-inxi-minimal. With that hash we can check whether your version is available on build farm as a substitute. ‘guix describe’ should show guix version.
<rekado>str1ngs: the hash of what? The store prefix is the same
<dekaidle>hello, I'm having some trouble configuring X. My (service slim-service-type (slim-configuration (xorg-configuration (keyboard-layout keyboard-layout)))) just gives me a "Wrong type to apply" (+ the keyboard-layout type) error. Any idea what I'm doing wrong? No other xorg options work either.
<mfg>what uri do i need to give guix download if i'm fetching a git commit?
<krafter>Is there a group that I can add a user to to make them able to shutdown or reboot the system?
<dekaidle>I get the same error if I just declare it directly in xorg-configuration, too
<str1ngs>mfg: that's good it uses cmake-build-system
<mfg>str1ngs: yes, but i don't understand how i should obtain the sha256 of a git tagged release ...
<str1ngs>mfg: are you using commit for git source?
<str1ngs>mfg: either way, guix will complain that the source hash is wrong. and tell you what the current hash is. which you can then use in place. I don't know how to receive just the source hash or do verification other then that. maybe there is a better way.. dunno
<mfg>str1ngs: i think so .. (version (git-version "2.0" revision commit)) revision and commit are let defined
<str1ngs>mfg: I mean in the git-reference for git-fetch
<Marlin[m]>dekaidle it means you used the wrong format on the option
<mfg>nckx: the documentation of the program states that it needs llvm 6
<rekado>so, we have zfs snapshots here and I can confirm that a few days ago some of the corrupt store items still looked fine.
<Marlin[m]>(keyboard-layout (keyboard-layout "us")) would work i think
<nckx>mfg: The quoted string here is just a label, it won't do anything (("llvm" ,llvm) is equivalent to ("larry" ,llvm)). You want ("llvm" ,llvm-6), which changes the actual variable passed to the package.
<dekaidle>Marlin[m]: I was thinking that at first too, but it works in the (bootloader) entry, plus I cannot use any other options like setting the resolution. I tried reading the manual on how these entries are built up but I'm clearly doing something fundamentally wrong, but I haven't been able to figure it out...
<Marlin[m]>Hey guys, i'm gonna look into packaging the digimend kernel drivers on guix
<rekado>(I used the daemon from “guix pull”, and it works only on /var)
<dekaidle>they all fail with an error, usually of type
<kmicu>donofrio__: a substitute saves disk space because we don’t need to compile a program on our computer (that requires installing build tools). E.g. by using hello’s (binary) substitute I don’t need to compile hello and compiling hello requires installing hello’s build-time dependencies https://hydra.gnu.org/build/3199947#tabs-build-deps
<g_bor[m]>rekado: I'm glad you could finally find out what went wrong. Do you have any idea how to prevent this in the future?
<donofrio__>are there arch specific substrates - in that I mean can I take the apache substrate for the suse x64 linux and the apply it to aix power8 arch?
<rekado>g_bor[m]: the daemon must be more careful.
<rekado>when the client reports one kind of localstatedir and the daemon has another, it should abort.
<dekaidle>if anyone has a working configuration file configuring X via slim I'd like to know how you got it working. Do I _have_ to use %desktop-services ? (I'm just using %base-services and picking other stuff I want to use manually)
<dekaidle>I've got everything working but X configuration