<mange>Is it getting stuck, or just printing a message? I think git prints a message when you checkout a commit that isn't a tag/branch, but it's not actually a problem. When I tried to build that package definition it failed because of a hash mismatch.
<sturm_>mange: arg, sorry I didn't read the error output properly. I was wondering why I hadn't seen a hash mismatch yet too hah
<cedb>offload stopped working im getting : "the file does not exist or permission denied: "/root/.ssh/id_rsa""
<cedb>i dont understand since i changed nothing...
<sneek>xelxebar, lfam says: Regarding NTP and bare-bones.tmpl, Okay! I suppose that 68 years will be good enough for the time being
<karrq>xelxebar: well from what I understoon guix refresh is to update a package to a newer version, in my example conan is 1.42 in the repo but 1.45 has been released already
<cat[m]1>What are people here's thoughts on OpenIndiana?
<xelxebar>karrq: guix refresh is mainly a helper for updating package definitions in the repo. If you want to install a newer release *right now*, then `guix build --with-commit=conan=1.45.0 conan` is probably your best bet.
<xelxebar>FWIW, I just tried building it. Looks like tests are failing, so you might need to add --without-tests=conan (caveat emptor, of course).
<bdju>anyone know about video playback performance with intel iGPUs? does vaapi make a big difference? I might not have it. I'm dropping frames really bad on some videos but not others. wondering if there's any way to make things better
<SeerLite[m]>Any reason for not using Guix search-paths for this? I think it could be done by setting up a GUIX_VIMRUNTIME search path and then have Vim use that, instead of using the predefined list of paths like now
<dave[m]>Hello! I am attempting to install Guix System on my computer, but I am not having any luck with LUKS. After installing with `guix system init`, GRUB says something along the lines of "Device uuid not found" (I am not at the computer right this moment). When I try to use the rescue shell, commands like cryptodisk are not available.
<dave[m]>I am connected through Matrix. If I upload a file will users on irc be able to open it?
<civodul>dave[m]: hi! out of curiosity, why are you using "guix system init" instead of the installer?
<civodul>normally "guix system" ensures all the file system UUIDs present in your OS config are valid
<civodul>but then maybe GRUB is configured without LUKS support or something
<dave[m]>civodul: I have my file system already set up and file on the home directory from a previous distribution. I did not see a way to this with the installer.
<singpolyma>Hey all, I'm having a strange problem. Trying to define a package using ruby-build-system with argument #:ruby ruby-3.0 and getting this error: has an invalid input: ("ruby" ruby-3.0)
<phodina[m]>civodul: That works thanks but I need to add also some other stuff like kernel arguments and I'd like to have just single if statement
<civodul>phodina[m]: oh i see; i think you'll need two 'if' statements
<civodul>another option is to do (operating-system (inherit the-other-one) (kernel ...) (kernel-arguments ...))
<civodul>and then you have a single 'if' to switch pick between one and the other
<phodina[m]><civodul> "and then you have a single 'if..." <- is possible to use if statements within the operating-system to enable or disable block of code? I'm asking as I want to share config between multiple machines. Inheriting configuration would be very tricky
<phodina[m]>I haven't seen any such code in gnu/system/examples nor any gexps or unquotes
<pinoaffe>phodina[m]: yes, conditionals are possible
<pinoaffe>you could even write a function that gets a few options as its arguments and gives out a system config based on those arguments
<phodina[m]>pinoaffe: ok, my struggle is that the conditional as is not evaluated ... what unquote or gexp should I use?
<phf-1>Hello Guix! I was wondering: to what extent can Elixir/Phoenix be used with Guix?
<phodina[m]>pinoaffe: Not sure what #~, #$ or , ` I should use
<attila_lendvai>with some much appreciated help, i have managed to work out how to develop and test shepherd. i'm willing to write it up somewhere, but where? guix manual? or the cookbook? or the shepherd manual? (probably not the latter because the recepie is rather specific to guix)
<ngz>attila_lendvai: I would ask this question on the devel mailing list, including your documentation.
<attila_lendvai>if i write it up beforehand, then i'll just add it to the guix manual then, and then relocate it depending on feedback
<elais[m]>I think it should go in the shepherd manual too
<elais[m]>I’m not sure if this is still the case but I recall there being a disconnect between shepherd services as described in the guix manual and shepherd services as described in the shepherd manual
<attila_lendvai>elais[m], i think it should live in contributing.texi, and the shepherd manual should point to it.
***dgcampea-2 is now known as dgcampea
<attila_lendvai>what i'll write up is how to have a reasonably short edit-compile-test cycle in a guix system vm
<elais[m]>As long as it’s visible in some way you have my support
<podiki[m]>works for me with a known package I imported before, at least
<SeerLite[m]>How should one update a package to the new input style if it contains an auxiliary file as input? Should the `search-auxiliary-file` call be done inside a phase directly instead? (I see Chromium does this)
<SeerLite[m]>Looking into it, I see that 4b4ea166 converted Chromium's aux file input to an ungexp in the phase instead. So I'll do the same
<elais[m]>attila_lendvai: will do when I get a minute
<karrq>Hello guys. I'm trying to create a manifest.scm for a project and I need a newer version of a package than what is currently available in the guix repository. I'm kinda new but I know about `guix build --with-latest`, I don't know how to use it in the manifest... I'm using guix on arch linux. Also, on another note, I tried building the package but failed the checks
<singpolyma>karrq: you can make the package inline in your manifest.scm, either by copying and editing, or by using inherit
<karrq>singpolyma: I did try that in the past for another package but ultimately failed. Wish it would be easier
<karrq>civodul: oh sweet, `options->transformation` would definitely be useful
<apteryx>civodul: would you happen to know how to disable the guix-days mail alias?
<apteryx>I have an account to fencepost, but don't know what to do with it
<ss2>hello, I'm seeing to observe that whenever I reconfigure, Guix will loop over building certain modules. Today it had gotten to the point that it looped over it many times over before completing it: https://paste.debian.net/1232557/
<ss2>On my old laptop it took something like an hour today, and I'm having this now on another machine.
<apteryx>I'm guessing there's something on your GUILE_LOAD_PATH/GUILE_LOAD_COMPILED_PATH from an older system that is incompatible with your current Guile
<apteryx>it should get sorted after you reboot; in any case it is a warning rather than an error
<ss2>I usually don't always pull a new checkout before reconfiguring. The one on my old laptop is maybe a week or two old (I know, but my laptop can't take the brunt of upgrading everyday), and I have done several reboots.
<ss2>okay, will reboot this other machine and see if these messages go away.
<AIM[m]>Is there an equivalent for build-essential in guix?
<ss2>apteryx: yes, rebooting the host does make the difference. Thanks.
<AIM[m]>Is there a way to use my own dwm on guix without creating a new channel?
<apteryx>civodul: I'm now attempting to reword the comment that previously mentioned content-addressed; so far I have "The SYSTEM-KERNEL-ARGUMENTS? should only be used in necessity, as the '--load' and '--system' values are self-referential (they refer to the system which ends up with a parameters file containing these values)."
<apteryx>that's still a bit vague; what exact problem does it cause? It is still valid, so it doesn't create an unresolvable cycle... I'd like to explicitly mention what effect it has.
<apteryx>ah! the system doesn't end up with such a file, the boot configuration does. That's why it works. It *would* create a cycle.
<civodul>apteryx: what you propose above sounds good to me
<apteryx>v2: The SYSTEM-KERNEL-ARGUMENTS? should only be used in necessity, as the '--load' and '--system' values are self-referential (they refer to the system); thus susceptible to introduce a recursive dependency.