<str1ngs>well pure environment works okay, so that's a start
<reepca>Has anyone else had luck with getting emacs to actually load dynamic modules? I can get it to load one, run emacs_module_init and everything, but it seems like none of the module api functions actually do anything. Nothing gets defined, and calling elisp functions doesn't do anything
<str1ngs>reepca: writing your own modules you mean?
<reepca>I see that current emacs is built with --with-modules, so it should be working...
<sirgazil>Should I expect the graphical installer to generate an configuration file that includes %base-services by default just as it should include %base-packages? Because my config.scm generated by the installer does not include %base-services.
<lisbeths>One is microsoft corporation and there is an 85% chance they are the culprit
<lisbeths>another is that my grandma downloads random exe files and so it could be a russian hacker. it is very unlikely it was them though becuase it was a higher tier hack as well as they have no motive to add this line of code to my xinit
<lisbeths>another possibility is that someone in the guix team was able to slip me the line exit 0 into my xinit
<lisbeths>this is also unlikely becaues the guix team has "no motive" to slip me this line. There is nothign to financially gain from it and as far as I know there is no one in the guix project who knows me who would want to exact revenge on me leaving no motive
<lisbeths>however there is still a small percent chance that some program from guix is respoinsble and so therefore it is my duity to inform you of the possibility tha tone of your coders is being a bit too silly and invovled with light grey hat hacking
<lisbeths>in all likelihood it was microsoft corproation however
<switchy>how would I best maintain my own updates on top of pre-existing packages? GUIX_PACKAGE_PATH runs into conflicts (understandably...). should I have a local clone of the standard channel and just manage merging in changes from upstream?
<dftxbs3e>switchy: ./pre-inst-env and a git checkout
<dftxbs3e>pre-inst-env is created when you "make" the project from git
<switchy>dftxbs3e, so for standard packages, I should just use regular guix, but if I'm modifying them I should use pre-inst-env?
<dftxbs3e>switchy: yes, you should recompile guix from your git checkout for it to use your modification, and the ./pre-inst-env
<switchy>dftxbs3e, why would I need to recompile guix just to change packages?
<dftxbs3e>switchy: I think that's how it works, I may be wrong, I'm quite new. I think package definitions are compiled inside Guix
<switchy>dftxbs3e, cool, I'll give that a shot. thanks!
<dftxbs3e>samplet: building at full speed with all 32 cores used at all times now, with -M 4 on both the daemon and the guix build command
<dftxbs3e>Before it was stuck at some steps for hours with only a single core occupied
<apteryx>switchy: I think you could also use channels
<apteryx>which is kind of the same idea (a git repo with your custom modifications), except that it's lighter (you don't need to duplicate the full guix project) and more convenient to share across machines/users.
<apteryx>it's relatively new and I haven't used it yet, but it seems nice! It's documented in the manual.
<samplet>dftxbs3e: Nice. I just started building “hello” for powerpc64le-linux-gnu.
<dftxbs3e>should we run ranlib on the object first? Or I think there's an argument to pass to ar
<dftxbs3e>samplet: "s Add an index to the archive, or update it if it already exists. Note this command is an exception to the rule that there can only be one command letter, as it is possible to use it as either a command or a modifier. In either case it does the same thing."
<apteryx>dftxbs3e: git log --grep=gcc in guix sources doesn't cut it?
<samplet>dftxbs3e: Right. Using target always makes cross compilers.
<samplet>The big change was moving to 7.4. But there was also a change in cross compiler environment variables.
<dftxbs3e>samplet: are the people in charge of doing this work here? What about Ludovic, do they only interact through the mailing list?
<dftxbs3e>I would think there's a set of maintainers that keep track of every change and would have a clear view of the state of each branch, no?
<dftxbs3e>Or the changes that are left, why things don't work
<samplet>dftxbs3e: It’s early days for “core-updates”. Some big changes, like GCC 7.4, have been committed and a lot of things are broken. In the next month or two, those problems will be addressed, and “core-updates” will be merged.
<dftxbs3e>samplet: okay, does that mean we're better off waiting few months before getting it to powerpc64le?
<samplet>dftxbs3e: It would be easier, sure. Getting started will be nicer, because you will be able to download a lot more binaries. Specific PowerPC problems will still be there, though.
<dftxbs3e>samplet: yes, powerpc specific problems are fine, we've gotten over lots of problems that get similar over various projects
<dftxbs3e>the community knows about all the problems specific to powerpc
<dftxbs3e>samplet: well for now, if we can create the bootstrap binaries, it can still get merged right? As long as the process to create them is documented
<dftxbs3e>or if it doesnt get merged, at least I can bootstrap guix 1.0 with bootstrap binaries created by say, 0.13.0
<samplet>dftxbs3e: I can’t say for sure. I guess you could create a branch on 0.13.0 (or whatever), get the bootstrap tarballs, and then keep that branch so that people could reproduce them in the future.
<dftxbs3e>samplet: there's a chance it works out of the box on v0.13.0 :P
<dftxbs3e>bootstrapping x86_64-linux from x86_64-linux still ongoing on the server
<dftxbs3e>samplet: do you think I should cancel it..?
<samplet>dftxbs3e: Maybe. It might not be that interesting.
<dftxbs3e>samplet: alright, I canceled it, I'll use the power for v0.13.0 + c89e21078862bd29b70a3bc0f33d160c59720364 - it probably works without cross-compiling, I'm thinking the cross compiling process as a whole has an issue
<lisbeths>I think perhaps guix intall icecat is stuck in a loop
<dftxbs3e>samplet: what are you testing out on the machine?
<samplet>dftxbs3e: I was trying to build small example of the “_Float128” error, so I could iterate on it.
<dftxbs3e>try recompiling guix, it doesnt take so long
<efraim>Would it make more sense to add it to the gcc flags instead of glibc cflags?
<lisbeths>nevermind I am not in a loop just taking a long time to compile
<dftxbs3e>lisbeths: it may compile things multiple times because the dependencies arent compiled the same way exactly so it has to make several copies compiled each with their own parameters so it's fully reproducible :P
<samplet>dftxbs3e: I have to go now. I detached my screen session which is building one last (doubtful) test. I’d like to know the result, but if you have to bring down the server or anything – feel free. Hopefully the 0.13.0 project works!
<roptat>but yes, you have NetworkManager or Connman
<roptat>most of guix is managed by the services, and they don't need to add anything to your profile
<ZombieChicken>okay, that just makes things worse in a sense; I'm trying to update some software and running (as root, since I'm just testing this in a VM) "guix pull && guix package -u" and guix package -u is complaining I need to run guix pull which, as you'll notice, I did literally seconds ago> What gives?
<roptat>probably your shell is not calling the new guix
<roptat>make sure ~/.config/guix/current/bin is first in your PATH and run "hash guix"
<roptat>(hash guix has no output, it just invalidates bash's cache of binary's locations)
<ZombieChicken>yeah, that's really weird. I would ahve thought that would have been done automatically, or a message printed telling the user "Hey, guix was updated and now you have to manually run 'hash guix' so things don't spit out useless error messages"
<rekado_>ZombieChicken: it does that, but there’s a bug report about it not working …
<roptat>it should have told you that on your first guix pull
<ZombieChicken>alright, that's fun. ran "guix package -i xorg-server xterm" followed by "guix package -i xinit", then 'startx -- vt1' (expecting a driver or permission error). Instead, I'm getting complaints that tty, hexdump, expr, uname, and hostname aren't available...
<g_bor[m]>Was wondering what is the guixy way to set up a simple static website. I would like to clone a git repo (something like a git-reference origin), and set up an nginx service to serve from that.
<efraim>dftxbs3e: I'm pretty sure you can 'guix download' the file on your ppc64le machine and host them somewhere later, as long as you put their hash in commencement.scm
<roptat>g_bor[m], maybe create a package for it, and use that package as the root of the website?
<roptat>look at cat-avatar-generator-service-type for an example :)
<dftxbs3e>efraim: well yes I have it on my ppc64le machine; I'm trying to edit the source to add the hashes etc
<sirmacik>wee, I've managed to solve gnupg/gnome-keyring problem with setting right path to pinentry (I need to get used to new paths), but still don't know how to automatically run cron daemon on system start :/
<pkill9>and now it's decided to not work again, lol
<pkill9>luckily i got the output when it was working so i cna compare
<pkill9>sirmacik: ok my only guess as to what's going wrong is that the version of gnome-tweaks must match the version of gnome-shell, so here is an updated package definition that uses the matching version: https://paste.debian.net/plain/1082343
<sirmacik>but while viewing file in evince it looks okay, but prints the same way as view from emacs
<sirmacik>so probably I'm missing something for ghostscript but no idea what
<dftxbs3e>hmm, "/tmp/guix-build-file-boot0-5.33.drv-3/file-5.33/src/.libs/file: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory" - that's a bug
<dftxbs3e>it fails to set libz.so.1 to its full /gnu/store path and instead uses system's libz.so.1
<joshuaBPMan>I'm starting to wonder, if me forcing my laptop to shutdown via the power button may be causing some filesystem corruption...
<joshuaBPMan>and if mac laptops are really the best way to run GNU/Linux. I just seem to keep running into weird issues.
<nixd>Hello guys, I am fairly new to guix and I have a little question regarding the package repo design of guix. Is there a reason why most packages are not in the repo with different versions, but only the last? Would this not hinder the complete reproducability? Say you have a full system configuration and require a specific version of a package, but
<nixd>only the latest one is present in the repo. Would I have to write my own package definition for my old version? Why are previous version package definitions thrown out of the repo (If I am even correct in saying this)?
<rekado_>ultimately we would have to commit to maintaining all snapshots of the software universe as seen from all versions of Guix
<nixd>I see, but what I don't seem to understand is how just appending new versions for toolchains/build systems and everything else instead of deleting the old ones would cause much stress. If everything would be kept around it should work out, no?
<philip>okay, so I'm trying a different usb live disk creator tool. When I open the iso extracted from the xz file I downloaded, the tool warns that the image does not contain a partition table, and thus probably can't be booted.
<joshuaBPMan>philip: hmmm. I am able to boot via that image. So it should be working.
<joshuaBPMan>philip: Does your machine have a CD drive? Perhaps you could boot your computer that way?
<philip>oof, it does, but that would be kind of a pain I would think.
<joshuaBPMan>philip: True. But on my older laptop, I was not able to boot via usb. I had to use the cd.
<joshuaBPMan>before you do that....I believe that image should have a partition table....
<sirmacik>is here someone who worked on ghostscript package?
<philip_>Well, I'm back, and the boot worked, but I wasn't able to successfully install on a particular partition. So I've decided to do a backup of my important directory and then wipe away all the other meaningless distros on my laptop
<arshin>philip_: might make everything else unbootable (or hard to boot) unless you're careful with how guix installs grub
<philip_>oh, that's fine. I don't really care about all the other distros.
<philip_>I'm just going to install it into my whole hard drive without doing any manual partitioning
<arshin>philip_: suit yourself. it's usually a better educational experience (if you're interested in that) to figure such stuff out rather than "delete everything -> reinstall"
<philip_>true, true. I've done a lot of that with other distros (NixOS, Arch, Void, Ubuntu) though, so I don't think I'm losing out by skipping the setup.
<philip_>Skipping the hard (but probly better way) that is. Before, I was trying to have 5 50GB partitions, one for each distro, but given how large the Nix/Guix store can get, I would like a larger partition anyway.
<philip_>I've only used NixOS actually, but I assume guix gc is the same as nix-garbage-collect. It does help, but the store can still easily get to 50GB, right? Plus, the store is never the only thing on a system.
<arshin>philip_: I don't know, I'm only beginning to play with GuiX in VM.
<pkill9>this is a little off topic, but since it was mentioned earlier, how feasible is it to run your own mail server?
<sirmacik>pkill9: I do it with mailcow and it is like a breeze
<pkill9>crab1: I have a pam-limits-service to make jack run, but otherwise i don't think there is a system-wide service for it, it just runs as a daemon as the user i think
<arshin>efraim: thanks. my /home is a separate partition too.
<arshin>"Currently Guix System only supports ext4 and btrfs file systems." - is this only for root/store, or in general?
<rekado_>crab1: jack2 is activated on demand via dbus.
<rekado_>I don’t think you need any service for that.
<rekado_>if you don’t need the dbus feature I suggest using jack1 instead.
<michaelmcandrew>hello all, a noob question that I couldn't find an answer to via google: is there an obvious gui mail client choice? (I use thunderbird but saw that it is not available). Is it claws? Anything else available?
<bavier>michaelmcandrew: I've used 'claws-mail' in the past
<sirmacik>arshin: encrypted root with esp partition
<arshin>sirmacik: something like this on kernel cmdline: BOOT_IMAGE=/vmlinuz-linux-libre cryptdevice=UUID=11111111-2222-3333-4444-354354645645:crroot cryptkey=rootfs:/crypto_keyfile root=/dev/mapper/crroot