<leoprikler>I'm guessing based on the values I found in guix/scripts/something.scm
<leoprikler>for instance, build sets verbosity to two, which is why you get the entire build logs
<lfam>kolyad: It's documented in the manual section Common Build Options, which are options that can be used with any command that builds things. That includes `guix system`, `guix package`, `guix environment`, and others
<sneek>Welcome back raghavgururajan, you have 1 message.
<sneek>raghavgururajan, nckx says: Your builder is trying to run ‘gulp’ which doesn't exist. ‘127’ usually just means ‘command not found’. I doubt gulp is available; Node stuff in general is a nightmare to properly package or use.
<raghavgururajan>Hello Folks! I was trying to package gnome-contacts, which uses meson-build-system. It asked for 'folks' as dependency and I did putting 'folks' as input. But even after that, meson is throwing an error "Could not generate cargs for folks". What is this mean?
<numerobis>Hi #guix! The new guix pull --news is amazing, great work!! :) Is it possible to see all the previous news, though, and not just the ones added in the latest 'guix pull'?
<roptat>numerobis, guix pull --list-generations I think
<raghavgururajan>roptat Also, by any chance do you know what is 'goa'? For gnome-music, meson asks for 'goa-1.0'. But on web, there is no program/package like that. Colloqially, gnome-online-accounts is called as goa. But I am pretty sure that is not the right dependency.
<ng0>we're thinking about our guile multiversioning at the moment, I have a couple of packages to publish in pkgsrc. does guix still have guile 1.8 or 2.0 at this point for some packages? I found it a good resource reading
<jonsger>raghavgururajan: I replied to your mailing thread about gnome-contacts
<roptat>you need to run guix system init/reconfigure to install u-boot properly
<roptat>and the correct u-boot needs to be defined in your config.scm file
<roptat>my ene.scm is an operating-system declaration that uses a u-boot bootloader defined above the declaration (although, the u-boot package I use is already defined in Guix)
<roptat>in you example, there's an operating-system declaration with a u-boot-bootloader that's already defined by guix
<mogom49>so if i want only generate u-boot. can i do "guix build u-boot-[my created u-boot package]-bootloader". is it?
<roptat>see the line with "define u-boot-cubietruck-bootloader" in ene.scm? that's where I define the bootloader. Here, I inherit from an already defined bootloader, because I want the same, but with another package
<mogom49>:) so what to do if i want only generate u-boot image for test u-boot?
<roptat>ok, if you only want to build it (but not use it), you can create a file, say u-boot.scm where you (define-public my-uboot (make-u-boot-package ...))
<roptat>you'll have to import (gnu packages bootloaders) too
<roptat>then at the end of the file add my-uboot (it refers to the variable you defined, so the file can be evaluated to a value, instead of #<unspecified>) and you can build the package with "guix build -f u-boot.scm"
<roptat>if all goes well, you'll end up with the store path where u-boot is built
<mogom49>'=D thanks, the builtin u-boot can run on the target board?
<roptat>I think what make-u-boot-package does is to specialize the u-boot package for a board
<roptat>if you don't specialize it, it won't run correctly I think
<jonsger>`guix download file:///path/to/bash` where bash is the one from static-bootstraps leads to /gnu/store/qziv75p1qz4lw31rppbbfx65piqjs689-bash but `guix build` tries to download /gnu/store/n9g7kihfj1kzz0nh9106wvbx7g7sc49f-bash
<roptat>oh nevermind I didn't see the bug report associated with it ^^'
<roptat>mh... I think there was only a typo, so I'm going to fix it, try to build a few package that use svn-fetch and push if it works
***ng0_ is now known as ng0
<alextee[m]>is there a way to refresh font caches or something in latex? looking these up online just confuses me more. i installed a bunch of tex related packages with fonts but i keep getting errors that it can't find fonts lol
<truby>hi guix :) has anyone looked into using guix environment -C with something similar to guix pack -S to make FHS compliant container environments containing the asked for packages? This would be really useful for making reproducible build environments for C/C++ programs whose build systems aren't necessarily friendly to non-FHS distros
<truby>(if the answer is no I'm happy to dig into the code and look at this myself if it's something anyone else would find useful other than me!)
<leoprikler>truby: with "FHS compliant" you mean only relying on /bin and /usr etc., not e.g. /gnu?
<truby>yeah, particularly reliance on /bin,/lib,/usr/bin,/usr/lib
<truby>I can already create a squashfs and load it with singularity e.g. with guix pack -R -S bin=/bin lib=/lib gcc-toolchain@8; singularity shell /path/to/result.squashfs
<truby>being able to do this in one line with guix environment -C --fhs or whatever would be really great (for my workflow at least :-))
<leoprikler>perhaps you want to make use of --expose=SPEC and --share=SPEC