<lfam>Give me a minute to gather my thoughts on the subject
<sys2>I haven't set up the deps for guix graph to display graphically yet... so I think that's out.. also I'd like to check the system profile (and no sudo access, but I do have root access), so it'll need to be text based
<pancak3>I submitted a pretty important emacs-next patch like 3 days ago in a bug report (43277) but I'm not sure if the right people have been notified :/ Is there someone is specific I should let know?
<civodul>yeah, and the "nix shell" examples remind me of time-machine
<civodul>the "lock files" are liked pinned channels it seems
<cbaines>and while lock files do provide "reproducibility", it does deviate from the typical way Guix would do that, via being explicit upfront, and instead start trying to record the environment so that it can be reproduced
<raghavgururajan>civodul: Would you be restore yesterday's IRC logs, to its original? Snopyta's admins were investigating but the original logs disappeared. We they are unable to report and discuss with DisMail and ProtonMail team.
<pancak3>So 4 days ago I submitted a patch that fixes 43277 (emacs-next not working) but it does some pretty serious changes (like downgrading the version because the previous version was wrong). Is there someone who deals with Emacs changes that I should CC? I want to make sure it gets looked at
<pancak3>oh I totally forget who suggested it to me. I should really be more grateful :P wasn't my idea though
<pancak3>I'm kicking myself for submitting the emacs-next package with the version "22.214.171.124". The 1 on the end is the build number. It just get incremented locally every time you run make. "28.0.50" is the real version number
<pancak3>but 126.96.36.199 > 28.0.50. Does Guix handle this well?
<rekado_>I’ve been thinking about moving all my Emacs stuff to a separate profile
<nckx>raghavgururajan: I'd created a ‘.orig’ back-up of yesterday's log but it simply showed up at the top of logs.guix.gnu.org, so that's how that works... I'll send you the original.
<morgansmith>xelxebar: I probably shouldn't be so proud but some of the first scheme I wrote was this for my manifest: (map (lambda (x) (string-append "emacs-" x)) '("all-the-icons" ...
<xelxebar>morgansmith: Yeah, specifications->manifest is your friend. It's a bit annoying to build/rebuild the first time (or after a guix pull) but that's a fairly minor up front cost for the benefit of clear and executable build documentation.
<rekado_>there’s none. It’s just something we did at the institute where I support Guix users.
<morgansmith>oh, so it was like something people but in their bashrc's or something? How did the automatic loading work?
<morgansmith>Also, what's the different between loading a profile and just using guix environment to load a manifest? Profiles only contain packages right? So they should be the same?
<rekado_>morgansmith: loading etc/profile may be faster
<rekado_>if you’ve run “guix pull” since the last time you used the profile “guix environment” may have to do some more work
<rekado_>loading etc/profile on the other hand is instant.
<morgansmith>rekado_: Ah, that makes sense. So guix environment will try to generate a profile for you which is different from trying to load a pre-existing profile. Makes sense. Thank you!
<morgansmith>I think I'm going to try and set up a secondary profile which has all my main software so I can use the default profile just for trying out new software. If I go crazy maybe I'll set up a profile just for installing modified packages I'm currently hacking on in the guix source :P
***ChanServ sets mode: +o nckx
***nckx sets mode: -b *!*@xmpp.snopyta.org
***ChanServ sets mode: -o nckx
<morgansmith>I just noticed the guix manual suggests doing "sudo -E ./pre-inst-env guix-daemon --build-users-group=guixbuild" before doing "./pre-inst-env guix build package" but I've never done this. Is the manual outdated? Should I be doing this? (section 15.2)
***roptat_ is now known as roptat
<roptat>morgansmith, only if you have modified the daemon or don't have a daemon running
<wleslie>oh it's the message report, I thought sneek had become a bug management system
<morgansmith>is there and different between sourcing /etc/profile and using guix package --search-paths=prefix? I'm asking because I want to activate a profile with --search-paths=suffix but I want to make sure it's a valid way to activate a profile
<civodul>note that .profile is for login shells only
<civodul>so to test it you should do "bash --login" or similar
<morgansmith>nothing is wrong with my env vars right now (that I know of) but in the past I've had no shortage of troubles. Most of those troubles where getting ssh-agent and gpg-agent working (but that was on arch-linux and the config still works flawlessly on Guix so I've got no Guix specific complaints)
<morgansmith>hmm... what file is run for every single shell? I don't want to use bashrc since my login shell doesn't read that :P
<raghavgururajan>mothacehe: Thanks! Btw, why there is different things like stable and latest? Guix is rolling-model right? So, i think there should be only latest?
<PotentialUser-60>I have a problem. I wanted to instal guix on my machine but the istaller desn't see my network card. Can you please help me to solve this issue? My network card is working with tisqurell linux.
<mothacehe> raghavgururajan: Even though Guix can be seen as a rolling release distribution, we sometimes release some stable version (last one is 1.1.0).
<raghavgururajan>mothacehe Cool! I was thinking if we could just have one webpage to download images and which is always latest. Because, currently the stable has no point as it would be updated to latest guix after guix pull anyway.
<roptat>isn't trisquell an fsdg distro? if it works with them, isn't there an issue?
<nckx>raghavgururajan: The release installer is supposed to be better tested than a random latest commit.
<raghavgururajan>roptat: Yeah, Trisquel is FSDG. Might be the older kernel that would have supported that hardware.
<raghavgururajan>nckx: Ah In that case, cool! I thought the stable image was generated from the commit, that was the release of Guix 1.1.0
<nckx>And having known bugs (‘the wi-fi freeze’, ‘the NVME oopsy’) makes it easier to support in a way.
<minall>Hello Guix Community!... does the guix ISO work?, I could install guix without a problem a few versions earlier but, not I dd'd into my USB 2 times and my laptop still doesn't detect the installation
<nckx>I'm not a file system designer, but compare readdir("/usr/bin"); readdir("/usr/sbin"); done; to what a Guix system needs to do. Symlinks are just text files that need to be looked up from scratch. ‘Caching is magic’ only kicks in once caches exist.
<nckx>How can that not be orders of magnitude slower?
<brown121407>brettgilio: that should work too. I used NGINX just cause the first tutorials for setting up ZNC for a subdomain were with NGINX. I don't know either NGINX or Apache, but the Guile config made it a bit easier to work with this stuff
<nckx>Does anyone use Guix's php(-fpm)? What's the right way to tweak php.ini?
<brettgilio>[13:19] brettgilio: So apparently new Firefox versions downloaded from their website block you from browsing when it has an update.
<nckx>It will leave a lot of old-distro cruft behind but it works surprisingly well.
<catinabox>ahh lovely, thanks; yeah, I figured, because one time when I borked a GuixSD install really badly I used guix system init on the existing root filesystem to repair it; just wanted to check that it was still a working idea even if the root filesystem was a foreign distro :)
<lfam>catinabox: Yes, it still is expected to work and is even the recommended way in certain cases
<cbaines>wooho! I think I've finally cracked the "calling (backtrace) in Guile actually raises another exception" issue I've been trying to resolve for months now
<cbaines>and I can finally see what's going wrong in my code
<cbaines>Rather than Guile (backtrace) erroring with:
<cbaines>In procedure string->number: Wrong type argument in position 1 (expecting string): #f
<civodul>cbaines: so there was an exception raised from 'backtrace'?
<civodul>(i use 'display-backtrace', didn't know 'backtrace' was a thing)
<cbaines>It works some of the time, but I think it's having problems because sqlite is involved
<cbaines>what I can see is that (backtrace) is called, and then code after it doesn't execute, and I get that output about: In procedure string->number: Wrong type argument in position 1 (expecting string): #f
<PotentialUser-51>hey guys, I installed the disto with the grapical interface and I want to update the packages that were installed with the desktop environment I chose but no updates get done whether I do "guix pull && guix package -u". how can I update the packages that were installed via the graphical installer?
<rekado_>“guix-build-coordinator-queue-builds-service-type” — the “-service-type” suffix has always irked me. I imagine a world where this would be part of the value itself, some sort of … “type” perhaps
<andreas-e>I never understood why these things are called "type". They are more like "values", no? Not a type in the programming sense.
***rekado_ is now known as rekado
<rekado>(service guix-build-coordinator-queue-builds-service-type) is a value
<cbaines>Thinking about system tests, if there's new system tests for each evaluated commit, and those come with big disk images, then 7.5 days of evaluations multiplied by disk images per evaluation could add up
<andreas-e>While we are chatting, the space on bayfront has dropped from 2.5GB to 1.3GB. I just stopped cuirass. But it may already be too late since there is a partition.img being built.
<andreas-e>It would be good if we could drop building the images on bayfront indeed.
<andreas-e>How about just dropping the "-type" suffix? Then "(service openssh-service-type)" becomes "(service openssh-service)", which looks entirely reasonable.
<andreas-e>Or even "(service openssh)", but I suppose that would clash with packages.
<rekado>oh, but we still have old-style values like “openssh-service”
<rekado>yes, that would be problematic, but only because there are no types
<cbaines>(define openssh-service (service openssh-service-type)) ; the naming here makes sense to me
<rekado>I wonder, though, if a macro (like the enum macro) could help
<nckx>andreas-e: There are 3 GiB to be gained with a risk-free ‘sudo rm -rf /home/*/.cache/’, if it's really close.
<catinabox>hmmm, I haven't used guile much, is there something already called "templates" like there is "types"? what if it was called e.g. openssh-service-template?
<darkpsi>yea first one. i am running it in a chroot boot from the installsion iso, since i could not get past initramfs it complained about trying to populate /etc/ from the guix store, so i thought i would try reconfiguring the sytem from a guix pull to see if that would fix the issue.
<darkpsi>@nckx got it to work did not bind pts on the chroot sorry.
<nckx>Glad you got it to work. 🙂 I'm still waiting on ‘guix pull’ myself.
<andreas-e>So our "guix publish" process has a --ttl of 15 days, which seems quite long. Filling a cahce of 86GB is reasonable, but could become a problem if there are actually people accessing bayfront as a substitute server. Presumably the Guix Data Service does?