IRC channel logs


back to list of logs

<raghavgururajan>allana Why not? Guix can co-exist with other package managers.
<allana>raghavgururajan: totally, I didn't mean to suggest that it shouldn't be there. I am actually wondering in what case it would be useful for someone.
<slyfox>it's probably useful to introspect .rpm files
<allana>slyfox: thanks.
<terpri>allana, dunno, but diffoscope and opm ("Open Build Service command line tool") both depend on it
<raghavgururajan>allana Yes yes, I didn't take it that way. 🙂
<Blackbeard>I am back
<drakonis>oho my kernel finished rebuilding
<Blackbeard>I need help with the flags
<Blackbeard>should I do "-DCMAKE_INSTALL_PREFIX=/bin"
<dftxbs3e>sneek, later tell allana rpm is also needed to *build* .rpm files, so if you want to distribute a package for an rpm-based distro, that can be useful. Maybe you can even use GNU Guix to build and then get it to output a .rpm file directly.
<Blackbeard>or without the /
<sneek>I've heard sneek is a sneek sneek that sneek sneek sneek sneek sneek
<sneek>From what I understand, sneek is a sneek sneek that sneek sneek sneek sneek sneek
<dftxbs3e>I find this bot so useful and beautiful at the same time. It seems to be equipped with a very human interface and I like it.
<Blackbeard>hahahhahaha sneek sneek
<dftxbs3e>Often, bots are like command line programs. Sneek instead behaves more like a classical IRC user.
<dftxbs3e>It's also such an elegant solution to the lack of permanent log of IRC. Just a public mailbox..
<dftxbs3e>And it doesnt bother you either, you get the message when you choose to connect back here.
<dftxbs3e>As well as everyone else in the channel.
<dftxbs3e>So that relevant conversation can be made more asynchronous, even over IRC.
<Blackbeard>it is working!!!!!
<Blackbeard>:D :D
<lfam>Is there a nice way in Git to figure out who is doing most of the work on a file? Like, a changed lines count by author?
<Blackbeard>lfam: hey
<lfam>Hi Blackbeard
<drakonis1>git blame?
<bandali>lfam, how about git shortlog -sn -- filename
<sneek>Welcome back bandali, you have 1 message.
<sneek>bandali, raghavgururajan says: When you are available, please ping me via PM.
<bandali>ah :-)
<bandali>sneek, botsnack
<lfam>Shortlog! I can never remember that name
<Blackbeard>I can't 'make authenticate'
<Blackbeard>make: *** No rule to make target 'authenticate'. Stop
*lfam bbl
<Blackbeard>I am trying to do this
<lfam>Blackbeard: Is your Git repo up to date?
<Blackbeard>lfam: I just did a git pull
<Blackbeard>And yesterday was the first time I did a git clone
<lfam>What if you run just `make`?
<Blackbeard>I have got the same error every time
<Blackbeard>make: *** No targets specified and no makefile found. Stop.
<Blackbeard>I am inside the guix directory of course
<lfam>It sounds like you didn't build yet
<lfam>Do `guix environment --pure guix -- ./bootstrap && ./configure --localstatedir=/var && make`
<Blackbeard>lfam: ohh I was just following the link I sent, didn't know I had to do all that :)
<Blackbeard>thanks :)
<Blackbeard>I just started reading the cookbook
<Blackbeard>seems like it has the best tutorial for packaging
<lfam>I guess the instructions in the manual need to be re-ordered
<Blackbeard>No Guile development packages were found.
*Blackbeard sent a long message: < >
<lfam>`guix environment --pure guix` should provide Guile
<lfam>Did you copy and paste my command exactly?
<lfam>Hm, it's not working for me either
<lfam>That's new
<Blackbeard>lfam: I ran by one in separate commands, seems like it will work now :)
<Blackbeard>first I did copy your command
<lfam>That used to work
<Blackbeard>I am so happy :) It is working now
<Blackbeard>I did a lot of progress today
<Blackbeard>widelands is working and now I am compiling guix
<Blackbeard>Yes ٩(◕‿◕。)۶
<Blackbeard>it worked lfam :)
<Blackbeard>lfam: now authenticate is failing, but guix compiled :)
<lfam>I'm running authenticate now
<lfam>`make authenticate` fails for me too, with ""could not authenticate commit bcfacecd3baab3066f89c686a01d4d066f9a4241: key A0C5E3522EF8EF5C64CDB7F0FD73CAC719D32566 is missing""
<Blackbeard>lfam: 'make check' is also failing for me
<lfam>Please report the `make check` things to <>
<lfam>Also the `make authenticate` problem
<lfam>I don't know what's up with `make authenticate` for me because I do have that key
<Blackbeard>lfam: ok :)
<lfam>And the key is listen in 'build-aux/git-authenticate.scm' so idk
<Blackbeard>lfam I ran it again and it is working now
<Blackbeard>maybe i did something wrong
<lfam>Who knows
<efraim>Lfam Blackbeard: the magic is: guix environment --pure guix -- sh -c './bootstrap && ./configure...'
<lfam>Thanks efraim
<efraim>With the sh -c 'commands here'
<lfam>Did this used to work?
<efraim>I don't think so
<Blackbeard>efraim: ohh I see
<Blackbeard>My PC went down while running tests and I didn't turn it on again
<Blackbeard>We have winds of up to 110 km/h
<Blackbeard>I think the electricity will go out again
<Blackbeard>Damien Cassou: hello
<Blackbeard>But tomorrow morning I'll try it :)
<Blackbeard>I am so happy about writing my first patch ٩(◕‿◕。)۶
<Blackbeard>Hopefully tomorrow it will be done
<DamienCassou>I installed Guix on Fedora. However, my / partition is way too small. I tried to move the content /gnu/store to my home partition and make /gnu/store a symlink but guix won't accept a symlink: `guix pull: error: the path `/gnu/store' is a symlink; this is not allowed for the store and its parent directories`. Is there some way to make /gnu/store live in my /home partition
<Blackbeard>Damien Cassou: I think you can make a partition in your disk that has home
<Blackbeard>And then modify fstab
<Blackbeard>No wait you don't even need a partition just a directory I think
<Blackbeard>Anyway have fstab Mount /home/damien/gnu as /gnu
<Blackbeard>That's would be my first option
<DamienCassou>can you mount a directory in another directory? Never heard of that before. In the meantime, I'm experimenting with creating a file and create an ext4 partition instide it then mount this file
<Blackbeard>Damien Cassou: no you Mount one directory as another
<DamienCassou>thank you Blackbeard
<Blackbeard>Damien Cassou: if it works let me know. I might try it too
<DamienCassou>Creating a file and mounting it as described above works fine. I might try your solution too
<guix-vits>Hi Guix.
<DamienCassou>hi guix-vits
<guix-vits>I've a script that take a 4Kib of printable chars from /dev/random; the password generated by this script was not accepted by freenode at registration time (probably because of the message being split); so i replaced the all not [a-zA-Z0-9] chars with some [a-z] ones -- anyway, no success; The registration was completed only with a 256-chars long pass; idk what is the max length.
***apteryx_ is now known as apteryx
<MaliRemorker>Does guix import texlive not work?
<MaliRemorker>guix import texlive fontspec returns with error on here
<guix-vits>MaliRemorker: is svn installed?
<MaliRemorker>yes it is
<MaliRemorker>i tried the same command from the command line
<MaliRemorker>and "it worked"
<guix-vits>i'd same error, but has no svn (at least in profile).
<MaliRemorker>I mean, I joined this: "export" "--non-interactive" "--trust-server-cert" "-r" "49435" "svn://" "/tmp/guix-directory.nGRbWg")
<MaliRemorker>into an actual command
<MaliRemorker>and this worked
<MaliRemorker>(adding svn at the beginning)
<MaliRemorker>maybe it's the environment of the import command that messes things up
<guix-vits>... or cleaned them up too much...
<MaliRemorker>or that
<MaliRemorker>cran importer works
<MaliRemorker>well, as of recently I am experimenting with multiple profiles, maybe that's where the problem lies
<MaliRemorker>I still see no benefits of multiple profiles :)
<rekado>NieDzejkob: re asciidoc: I didn’t want to deal with potential fallout from switching all users of asciidoc over to asciidoc-py3.
<rekado>NieDzejkob: we can do this for all applications individually and then remove the old asciidoc.
<rekado>nckx: I’m working on free space on berlin.
<MaliRemorker>folks, so when you have a bunch of packages, say >20 (think a few big R programs and dependencies not yet in guix) ... how do you maintain them?
<rekado>MaliRemorker: I package them all for Guix.
<rekado>R packages are very easy to package.
<MaliRemorker>sure i do that too :)
<MaliRemorker>if i commit them to guix
<MaliRemorker>then i also kind of get into the commitment to maintain them :)
<MaliRemorker>the more packages there are , the more updates , it feels like it would take more than one overworked human
<MaliRemorker>[by sure i do that, too: i have a non-official channel]
<MaliRemorker>[ * ... too ( i mean) ...]
<MaliRemorker>@rekado btw, how would you deal with dependencies to a R package which are under 'Suggests' category in the DESCRIPTION file? Some people will need this, some won't. Would you still record them as inputs in the main package declaration, or not?
<rekado>MaliRemorker: I usually don’t add packages in the Suggest category to the inputs.
<rekado>With R packages it’s enough to install those when needed.
<ngz>Hello. I have a package for libraqm (<>), but I'm not sure where it should go. Maybe "unicode.scm"? WDYT?
<guix-vits>test, autologin: 128-chars
<guix-vits>ngz: if this is packaged to Debian, i'd look there...
<guix-vits>it has tag "shared library".
<guix-vits>ngz: fontutils.scm ? Libraries already there: freetype, fontconfig, t1lib, libotf, libspiro.
<ngz>guix-vits: You may be right, indeed. fontutils.scm seems a good choice. Thank you.
<NieDzejkob>rekado: ah, alright
<Blackbeard>Hello ٩(◕‿◕。)۶
<katco>i'm getting an error when running `guix pull`: `guix pull: error: symlink: File exists: "/var/guix/profiles/per-user/katco/current-guix"`. any idea how to fix this?
<guix-vits>katco: try `sudo guix pull` -- it will be on behalf of katco, but with more priveledges. IDK if it'll help, though.
<katco>good idea, i'll give that a try
<katco>ah yes, that works. i wonder if i did that on accident before to get into this state.
<katco>thank you!
<leoprikler>you should chown /var/guix/profiles/per-user/katco
<katco>i did think of that, but it's already `katco:katco`
<leoprikler>not katco:users?
<leoprikler>and current-guix?
<katco>same, both the symlink and what it points to
<nckx>Good morning Guix. Hullo Blackbeard. Did you build a working Widelands?
<DamienCassou>I'm creating a package for `foo` which consists of a bash file which itself references the binary file `bar` and expects it to be in `PATH`. `bar` is already packages in Guix. I can patch `foo` so it references `/gnu/store/...-bar/bin/bar` instead of just `bar` and that works. Is there a patch I can send upstream so patching in Guix is not necessary?
<nckx>katco: What about /home/katco/.config/guix? Everything there should be owned by you:you. What I've done in the past to work around this error is: GUIX="$(readlink -m $(which guix))" && rm -f ~/.config/guix/current /var/guix/profiles/per-user/$USER/current-guix && $GUIX PULL. That's the general principle, don't blindly copy-paste.
<nckx>You shouldn't ‘sudo guix pull’. ‘sudo -i guix pull’ should work if you want to pull root's Guix.
<nckx>DamienCassou: I don't think so. That all sounds like the standard way to do things (what could upstream do differently?).
<leoprikler>DamienCassou: depends on how `foo` is created
<DamienCassou>foo isn't created, it's a bash script that is part of a git repository
<leoprikler>if you use autotools' configure or any similar stuff to create it, the problem would go away
<DamienCassou>foo =
<DamienCassou>bar =
<nckx>DamienCassou: You're doing the right thing already.
<nckx>An alternative is to use wrap-program, but prefer substitute* if ‘bar’ is easy to match & replace.
<leoprikler>in this case you could even do wrap-script
<nckx>Ooh, newness.
<katco>nckx: aha! `${HOME}/.config/guix/current` is owned by `root:root`
<nckx>katco: Aha! Chown away.
<DamienCassou>thank you
<nckx>leoprikler: Interesting, thanks. I agree that's even better.
<Blackbeard>nckx: my package works now :D
<Blackbeard>I could play waylands on my guix (:
<Blackbeard>Now I am setting everything so I can send a patch
<nckx>katco: Did that fix it? Would you be willing to file a bug report? It's not a ‘bug’ per se but Guix is being a bit more silently pedantic than it needs to be.
<guix-vits>katco: i'm sorry: "Sudo'ing guix pull will (or at least in the past did) create /blah/$USER/files with owner root:root, so it ‘works’ but also forces you to always use ‘sudo guix pull’ from now on.", i was wrong.
<guix-vits>nckx: thanks.
<katco>nckx: i ran into a meeting, but it caused some issues. i'd be happy to file a bug, and i'll add more context, here, later in the day.
<nckx>katco: Thanks!
<nckx>Enjoy your meeting.
<katco>nckx: should things in `/var/guix/profiles/per-user/katco/current-guix/` be owned by me? those are currently owned by `root`
<NieDzejkob>For me, the link is owned by kuba:users, but the contents are owned by root:root
<mehlon>same here
<nckx>katco: The symlink itself should be katco:katco, but it links into the store, which is always root-owned, so that's fine.
<nckx>Check the link itself though.
<nckx>Your user's Guix needs to flip it after pulling.
*katco sent a long message: < >
<katco>`r-xr-xr-x 5 root root 4.0K Dec 31 1969 sygks85bn8x8bsg6969hzb0sxq63rbgc-profile/` though... does that matter?
<NieDzejkob>anything in /gnu/store will be owned by root
*nckx has to run, but none of that is wrong. :-/
<NieDzejkob>(The First Axiom of Guix)
<mehlon>the second rule of Guix is you do not talk about Guix club
<bavier`>mehlon: if you want to help with anbox, PM me
<mehlon>sorry, I don't really know how to package stuff in guix anyway
<mehlon>nor how to do the androidy thing
<bavier`>ha, np, I hardly do, was hoping you might ;)
<mehlon>I guess you can copy stuff from the NixOS, they seem to have a functioning version
<rekado>laptop broke down. Blank screen :(
<bavier`>rekado: oh noes!
<guix-vits>rekado: Is it old?
<bandali>anyone else's fans nearly constantly running on guix system?
<bandali>fwiw, this is an x200
<NieDzejkob>not for me
<NieDzejkob>what does `top' say?
<bandali>it *seems* to me that fans get especially busy when i'm using erc, sometimes
<bandali>nothing useful really
<bandali>the cpus are basically idle, and ram is at like 1.16/7.68 gb
<bandali>sometimes, unplugging and plugging the charger back in calms the fans down, but not always
<bavier`>bandali: do you have thermald
<bavier`>shot in the dark, I've not had issues with my fans
<bandali>bavier`, yup, i have services for thermald, tlp, and powertop auto tune in my system config
<guix-vits>bandali: cat /sys/devices/system/cpu/cpufreq/policy*/scaling_governor is "powersave"?
<bandali>guix-vits, it's performance
<NieDzejkob>Huh, pip doesn't work in a virtualenv
<NieDzejkob>The generated pip script is importing a slightly different module than the real pip3 script from the python package. The virtualenv version we're packaging is quite old, I'll try upgrading
<nckx>bandali: ‘performance’ really means ‘constantly pin the CPU frequency at <scaling_max_freq> no matter what’ — even when your system is idle. ‘powersave’ (or ‘conservative’, which claims to be more suitable for battery-powered devices) are generally better choices.
<bandali>nckx, hmm, in that case it makes sense that the fans would be running given that the frequency is maxed out. i wonder if it's one of the above three services i've enabled?
<nckx>I don't know, I use none.
<bandali>hm, so tlp's sched-powersave-on-bat? is #t by default, and i haven't changed it in my system config
<nckx>I set ‘conservative’ and other defaults in my kernel configuration.
<nckx>bandali: And you're on bat?
<bandali>nckx, yup
<bandali>bat or ac seem to both be on performance for some reason
<nckx>bandali: When you cpufreq-info (usually the first place to start debugging this stuff), what are the available governors? You can only select ones that have been loaded as modules, and I'm not sure which ones Guix provides by default.
<nckx>☝ in cpufrequtils if you don't yet have it.
<bandali>ty, brb, installing it
<guix-vits>bandali: cat /sys/devices/system/cpu/cpufreq/policy*/scaling_available_governors
<guix-vits>poor man's XD
<nckx>bandali: grep . /sys/devices/system/cpu/cpufreq/policy*/* = poor man's cpufreq-info
<guix-vits>nckx, Matrix has you 0_o...
<bandali>conservative ondemand userspace powersave performance schedutil
<nckx>(Or just the nature of clichés, but I choose to believe that I'm psychic.)
<nckx>I don't understand why $whatever_service isn't loading the sane one then.
<nckx>You can set it manually (by echoing, say, powersave or conservative to each core's scaling_governor governor file as root) and see if it helps.
<guix-vits>bandali: shcedutil was default in Arch, last time i'd check; if the good ol' ondemand available to you, then you are on AMD. Intel has good powersave in intel_pstate.
<bandali>guix-vits, i am on intel: Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GH
<nckx>schedutil is hit 'n miss (when the scheduler likes your average workload, you're golden). Ondemand isn't AMD-only.
<nckx>All the gory deets:
<guix-vits>bandali: interesting. I'm on Pentium B960, only two governors...
<bandali>guix-vits, that's older than core 2 duo right? maybe that's why
<guix-vits>idk. pstate driver was some sort of "new thing"...
<nckx>guix-vits: Sandy Bridge & up.
<nckx>It's what I'm using on my Ivy Bridge laptop.
<guix-vits>bandali: cat /sys/devices/system/cpu/cpufreq/policy*/scaling_available_governors ?
<guix-vits>cat /sys/devices/system/cpu/cpufreq/policy*/scaling_driver ?
<nckx>I'm betting acpi-cpufreq.
<nckx>That definitely supports ondemand well.
<nckx>(Others likely as well, just no experience.)
<bandali>conservative seems nice
<bandali>but i still can't think why tlp or some other service would set performance for bat
<bandali>i'll see if i can get it to always use conservative instead
<guix-vits>but it's possible that acpi-cpufreq was loaded by mistake (like how it happens in radeon vs amdgpu)?
<nckx>bandali: That's what I do. It scales to 100% when needed, even with AC plugged in I prefer my lap cool and top quiet.
<bandali>nckx, nice
<anadon>`guix pack --format=squashfs rseqc` fails for me and I'm not sure how to debug this. The logfile trace did not mean anything to me.
<bandali>guix-vits, not sure. i think that's what it should be for older cpus like core 2 duo
<nckx>guix-vits: What other driver would you expect? The ACPI one is pretty solid AFAIK. It's not like the old P4 modulation driver which is 100% stay-away quality.
<nckx>anadon: I get ‘guix pack: warning: Singularity requires you to provide a shell | hint: Add `bash' or `bash-minimal' to your package list.’, testing anyway.
<joshuaBPMan>Hey guix, I'm hoping to build an installation image and test the installer. It's just taking it forever to build. :)
<nckx>anadon: Works for me, created /gnu/store/ql76bdhxlffy0qrjjzxbcci8mwzswxj3-squashfs-pack.gz.squashfs .
<anadon>@nckx Still nada.
<anadon>Using `guix pack --format=squashfs rseqc bash`
<nckx>Which I can mount -o loop and browse.
<nckx>anadon: That's odd. Seems like [interaction with] something outside of Guix is to blame. Are you running a Guix kernel?
<anadon>I'm running CentOS7 to regain some sanity.
<nckx>The notorious CentOS.
<anadon>Let me phrase that better, I'm using CentOS7 and in order to have sane packaging I'm using guix.
<nckx>I'm going to guess (a pretty safe guess, but just a guess) that your CentOS kernel lacks some modern thing that Guix's use of mksquashfs expects.
<anadon>Having stability through packages so stale they don't work is not my understanding of a good idea.
<nckx>Does Singularity support any other format?
<nckx>anadon: Agreed, and it's been a source of trouble before.
<anadon>Docker technically, but it isn't bulletproof.
<nckx>All vaguely relevant search results are due to the squashfs module not being loaded, I guess that's not your problem.
<anadon>If Hurd had significant funding, the per user kernel modules could just fix this.
<nckx>I wouldn't expect mksquashfs to require kernel support but ‘Failed to read existing filesystem’ makes me unsure.
<nckx>anadon: Heh.
<anadon>Any way to track that down? I keep failing to get sigificant use cases working with guix at my institution because of things like this.
<nckx>I don't disagree but won't hold my breath.
<anadon>I'm actually surprised it doesn't get some DoD funding.
<nckx>anadon: I think Guix is giving you all the output from mksquashfs already, unless there's more info in e.g. dmesg I don't know what to say.
<anadon>The uptime and flexibility of such a system would fix so much shit.
<nckx>If you're comfy with building Guix from source you can add the -noappend to the mksquashfs call in (guix scripts pack) yourself. If you're not, there's no time like the present. You can at least limp on until someone find a better solution.
<nckx>Assuming that works of course.
<anadon>You know what, I have sideproject time and my main work is on hold for a week. Sure. Compile then replace the existing binary?
<nckx>anadon: Clone the guix repo, then (using your existing guix to enter a guix environment) run bootstrap, configure, and make. Then you can invoke your source-build guix with ./pre-inst-env guix …. Any changes you make to the code will take effect immediately (you'll just get some ‘file x newer that compiled y’ spam).
<nckx>Read ‘(guix)Building from Git’ to get started.
<nckx>No need to make install or otherwise replace anything.
<nckx>If you know more about mksquashfs than I do you can also just test wether an mksquashfs installed through Guix can create file systems at all on your kernel.
<nckx>(guix install squashfs-tools.)
<anadon>One thing I'm seeing is that when the initial squashfs image is created, it is owned by guixbuilder01 and it seems to be acting as if the subsequent calls are by a different user.
<anadon>Having a server side failure when cloning:
<nckx>SELinux? Are you able to disable enforcement to find out?
<nckx>anadon: Missing paste.
<nckx>anadon: Hold your nose and GIT_SSL_NO_VERIFY=true git clone…
<nckx>(Or you know, don't, and debug yet another thing but don't sue me either way.)
<anadon>Holding the boat together with sticks and tape.
<nckx>I'd love to give a better answer but I have no idea how to set up SSL stuff on foreign distroes if it's not covered in the manual.
<anadon>I suspect that the server side cert is just not signed by a trusted authority.
<nckx>It definitely is, unless your SSL store predates Let's Encrypt.
<anadon>Have I mentioned that I want to burn CentOS to the ground today? It feels like this is a daily occurrence.
<anadon>Huh, ztsd isn't supported in pack. Should it?
<nckx>I'm a big zstd fan so yes, sure, I just don't use guix pack much. I'll add it to my TODO-when-bored-list.
<anadon>What would be involved with supporting it? I might be able to have my first contribution!
<nckx>anadon: That would be much appreciated. It seems pretty trivial;
<nckx>%compressors list the available compressors, which are just invoked binaries (no writing zstd Guile bindings for you).
<nckx>Add zstd to that, document it in guix.texi, write a test, and I think you're done.
<nckx>TBH I'd already started (it's not much more work than writing a TODO entry…) but will gladly cede to you.
<nckx>anadon: One possible caveat is making sure zstd is called with options that produce bit-identical output everywhere. So no --threads=0 IIUC.
<nckx> implies this shouldn't be a problem.
<NieDzejkob>anadon: what are the values of CURL_CA_BUNDLE, SSL_CERT_FILE and SSL_CERT_DIR?
<anadon>NieDzejkob: All empty
<NieDzejkob>anadon: do you have nss-certs installed?
<anadon>nckx: Looking over this code, the multi-step approach may be a little error prone. Someone on SO suggested creating a base dir which has the structure desired and to `mksquashfs` it in one shot. If this were to be done, then to use symlinks in place of the actual files and make sure that they are de-referenced seems like it might be more
<anadon>performant and stable. Thoughts?
<anadon>NieDzejkob: yes
<nckx>anadon: I didn't write the original nor have I ever used singularity (or any neostaticbinary runner, just plain .tgz packs) but that all sounds reasonable. Probably best proposed at length on guix-devel@. How does your solution deal with actual symlinks we want in the final image?
<joshuaBPMan>Well I am testing the guix installer image on a macbook. That's kind of cool.
<joshuaBPMan>It looks like the graphical installer is not working so well.
<joshuaBPMan>It is just flashing on and flashing off.
<joshuaBPMan>Blue screen. Blue screen. Black screen.
<NieDzejkob>joshuaBPMan: is that current master or 1.0.1?
<joshuaBPMan>I have to switch to a virtual console to get it to work.
<NieDzejkob>I was experiencing something similar on qemu
<NieDzejkob>the gui was, like, crashing immediately all the time
<joshuaBPMan>NieDzejkob: I just guix pulled last night I believe.
<joshuaBPMan>guix describe says: 4b759d3c548270eba348521669bae15c9e5b72bc
<joshuaBPMan>It also has the date as March
<joshuaBPMan>I suppose that I could mention in the manual about holding the "option" key down while the macbook starts.
<NieDzejkob>Looks like it's a bug in the installer, I'd suggest messaging the list
<joshuaBPMan>I'll do that.
*katco sent a long message: < >
<NieDzejkob>nckx: ^ see the long message above
<katco>ugh. sorry!
<raingloom>anyone knows what's the nix equivalent of `guix system vm`? i'm trying to debug my Wacom tablet again and wanna see how it works in Nix.
<raingloom>(already tested it successfully in Arch, but i don't wanna keep maintaining my Arch VM forever)
<katco>interesting. if i remove the symlinks `${HOME}/.config/guix/current-guix`, `/var/guix/profiles-per-user/katco/current-guix`, and then delete `${HOME}/.cache/guix`, this seems to have gotten me unstuck.
<drakonis>raingloom: `nixos-rebuild build-vm`
<raingloom>drakonis: that's nixos only, i was hoping for something that works from Guix with Nix installed as a shepherd service
<raingloom>like, there is no nixos-rebuild command in the nix package installed by Guix
<raingloom>but whatevs, I guess I'll just start it from an ISO
<raingloom>(and this is why I like Guix more :) )
<drakonis>you might want to hop onto #nixos
<raingloom>hmm, i guess that's a good idea.
<terpri>how can i add extra kernel module packages to be modprobe-able from the system profile?
<terpri>e.g. ddcci-driver-linux
<terpri>modprobe only loads modules from /run/booted-system/kernel/..., not /run/booted-system/lib/modules/... which is where the package's files end up
<bdju>Does anyone know the nix-equivalent to a "guix pull"?
<bdju>I have been using "nixos-rebuild switch --upgrade", but is there something that will just pull in the new stuff without doing anything?
<bdju>guix is a lot simpler, imo
<joshuaBPMan>I'm trying to install tex. Essentially I want to export an org-mode file.
<joshuaBPMan>is tex-live the best option?
<terpri>joshuaBPMan, texlive, yes
<terpri>there are some subsets available (texlive-tiny, texlive-base) but easier to just install the whole thing imo
<joshuaBPMan>texlive-base seems to be a smaller tex package.
<terpri>hm, -tiny seems to be just -base plus dependencies on bash, coreutils and sed
<anadon>Digging a bit more from earlier, for containers, should the current squashfs and docker options be deprecated in favor of the Open Containers Initiative specification?
<mbakke>terpri: there is some work on making kernel modules more accessible in
<mbakke>for now I suppose insmod works?
<terpri>mbakke, thanks
<terpri>and yes, insmod works fine for now
<MtotheM>I get that guix is all about freedom and transparency. but can you defined a different kernel if you want it? for example mainline or rc?
<terpri>MtotheM, yes, it's really easy to use a custom kernel if you want
<jackhill>indeed :) there was even a blog post:
<MtotheM>That's nice. cause this laptop I just got need driver blobs to work properly. the wifi for example.
<MtotheM>Thanks for the link
<jackhill>there is also something to that effect in the cookbook