IRC channel logs
2026-04-19.log
back to list of logs
<lispmacs[work]>in my home configuration, I am using specifications->packages in the usual way. I am wondering if it possible, in the configuration, to indicate that I want to install all the build dependencies of a package, but not the package itself. I.e., what I would get if I ran "guix shell -D emacs" <ieure>lispmacs[work], You can do that, but not with specifications->packages. (home-environment (packages (append (package-inputs whatever-package) (specifications->packages ...)))) <ieure>lispmacs[work], Sorry, you actually want (map cadr (package-inputs ...)) <ieure>Actually... (filter package? (map cadr (package-inputs ...))) <ieure>Because some packages have non-package inputs which would break home-environment. <lispmacs[work]>for the part where you put the "...", what exactly would I type for the emacs package? and do I need to import something? <ieure>lispmacs[work], `emacs', and it's in (gnu packages emacs) <ieure>lispmacs[work], You could also do (package-inputs (specification->package "emacs")) <ieure>lispmacs[work], Why do you want this? <lispmacs[work]>I build and install emacs myself, in ~/local, but I always have used "guix shell -D emacs" (or emacs-next) to get the dependencies <ieure>lispmacs[work], Why are you compiling it yourself? <lispmacs[work]>I wanted to have those dependencies automatically in my profile, but not install emacs itself from guix <lispmacs[work]>ieure: I am often filing bug reports or tweaking/testing things, and nobody will help me unless I'm using the latest commit <lispmacs[work]>I just keep a branch of emacs in my home directory, and pull the last commits before I go to test or report something <ieure>lispmacs[work], Why don't you make a variant of the Guix package? <lispmacs[work]>lack of understanding of how to do that or what the benefits would be <ieure>Well, you wouldn't have to do all this stuff. <lispmacs[work]>currently, all I do is "guix shell -D emacs" then "git pull", "make distclean", "./configure ...", and "make install". is the other idea simpler? <ieure>lispmacs[work], It is overall simpler. <ieure>lispmacs[work], There's an `emacs->emacs-next' procedure in gnu/packages/emacs.scm (which is the source for (gnu packages emacs)) which does most of this for you. You just need to specify an origin for the source you want to build and a version. <ieure>Whip yourself up a guix.scm in your ~/local and `guix build -f guix.scm' to build it, `guix install -f guix.scm' (I *think*, check the manual) to install it into your per-user profile. <ieure>Yes, you can give an origin with a file:/// URL. But you will have to use `guix hash' to figure out the correct hash to put in there. <ieure>lispmacs[work], Alternately, you can use direnv to automatically activate a profile containing the Emacs build deps when you cd into its source directory. See the "Guix environment via direnv" section of the Guix Cookbook. <nckx>You can use git-checkout to avoid the edit-rehash-edit-build dance. <kestrelwx>untrusem: By the way the PRs have the same versions for everything other than my River 0.3.x series being newer. <untrusem>I saw the zig-wayland was 0.5 in theesm pr and zig-xcbcommon, that's all <theesm>only needed to bump river to be able to try out reka (was a byproduct of packaging it)... think as soon as kestrelwx PR is merged i'll create one for reka <morganw>Hi. Is it a known issue that using xfce-desktop-service-type to get an XFCE desktop seems to have dark mode partially enabled even when the dark themes are disabled? <librecat>how long does a stable guix release get long term support if applicable? <Rutherther>librecat: it doesn't releases do not get any support <librecat>does guix use llm assistance in any way? <Rutherther>librecat: releases are only snapshots in time, they do not get any updates. They are meant only for installation, you should always get latest master after installation <nckx>librecat: Neither Guix the software nor ‘the project’ do, but contributors might. I thought there was an RFC or discussion on the matter but I seem to have haluccinated that :-/ Or it wasn't about Guix proper. <Rutherther>there is a discussion about it, on guix-devel mailing list <yelninei>having 4 different versions of the same 2.5k line patch sucks, but I hope I can finally complete this <nox>librecat: you can obviously not always tell what someone used to make a contribution, but there is no official stance LLM-generated code as far as I can tell. <nox>my personal opinion is that it's a blatant violation and utter disrespect of the spirit of free software <nckx>Rutherther: Annoyingly, it refuses to show up in my webmail. I'll gladly take not having hallucinated, though. <Rutherther>The thread is "Can a project accept LLMs' code contribution and remain free software?" <nckx>ACTION .oO …I don't undestand you, Lucene. I really don't. <quartz>hi, when trying to guix pull I get a git timeout, any idea how to debug it? I can git clone the repos manually without issue <Aurora_v_kosmose>Rutherther: In the same way the Linux kernel can when someone submits soteln code. The compromised contribution has to be ripped out and the Free/Libre state is restored. <folaht>The patch that I want to apply to the package that I want to alter doesn't seem to work. <kestrelwx>folaht: Share the specifics, there's a link to the paste website in the topic. <ieure>folaht, If you paste your package definition, I will take a look. <ieure>folaht, What's happening when you build it? Doesn't build at all? Your changes don't seem to be getting used? <folaht>I'm getting the error: guix build: error: ./xkeyboard-config-yr.patch: invalid package patch specification <ieure>folaht, Okay, please paste the package definition. It sounds like there's an error in how you're specifying the patch. <folaht>I think my patch is all wrong. I never patched anything before. <ieure>folaht, There's no patch in there, is that the original package definition? I need the thing you're trying to build, which does not build. <folaht>So I can use a patch locally correct? <folaht>I can modify a package that way correct? <nckx>Did you forget the ‘--with-patch=xkeyboard-config=’ part? <nckx>I can see that error message meaning that. <ieure>folaht, So, you have presented a problem and given the error, but have not given me any steps I can take to reproduce the error. If you want help, you need to provide that. <folaht>nckx, no I forgot to even test the patch. The patch isn't working, because I never patched before. <ieure>And whatever command you're running. <folaht>$ guix shell --container --nesting --development xkeyboard-config <folaht>[env]$ guix build xkeyboard-config --with-patch=mutt=./xkeyboard-config-yr.patch <folaht>[env]$ guix build xkeyboard-config --with-patch=./xkeyboard-config-yr.patch <ieure>Agree, this also works for me: `guix build xkeyboard-config --with-patch=xkeyboard-config=/home/ieure/Downloads/xkeyboard-config-yr.patch' <ieure>folaht, Note that you don't need the `guix shell' invocation at all. <nckx>folaht: Note that in your last [env] example (after ‘Oh sorry’) you forgot ‘xkeyboard-config=’ again. Maybe only here and not in your terminal, but check. <folaht>ieure, ah. Then why is guix shell in there at all? <ieure>folaht, The error is telling you that your --with-patch argument is wrong, you've given the path to the patch, but the format is --with-patch=package-name=/path/to/the.patch <ieure>folaht, I have no idea, either the author of the guide you were reading was doing other things or just didn't understand how things work. This is why I always prefer the official project documentation. <nckx>(To be fair, if that is the only thing that error message is for, it could be much more clear. Like mentioning the ‘=’ character at all, for one.) <nckx>ieure: I'd guess the former considering the author but who knows what futurile was like in 2023 :) <ieure>nckx, I think the error message is pretty clear, especially if you look at the Guix manual, which clearly says: ‘--with-patch=PACKAGE=FILE’ <nckx>If it were good, you wouldn't need to. <ieure>There's only one patch being specified, the error says there's a problem with it. Seems clear enough to me. <folaht>Hurray, it's working but it also failed lol <ieure>folaht, `--without-tests=xkeyboard-config' YOLO <folaht>ieure, I could also just try to figure out what the error is saying <folaht>-yr(yr-afyro):"European (Afeuro, phonemic latin)" <folaht>+yr:"European (Afeuro, phonemic latin)" <folaht>I get the feeling it's telling me something I shouldn't do. <ieure>folaht, It's complaining about the changes in your patch, you can patch the tests also, or disable them. <folaht>I want my added conlang to be legit for xkeyboard use. <ieure>Then you will need to fix the tests and include those fixes in your patch. <folaht>Yeah, oh wait, I can probably just find those tests somewhere and see what it actually tests on. <ieure>Tests are in the xkeyboard-config source. <folaht>Yeah, I found it already. The group names in base.xml and the symbol file needs to match <quartz>hi, any idea what could be the reason for this <quartz>`guix pull: error: Git error: failed to connect to git.guix.gnu.org: Operation timed out` ? <ieure>quartz, Codeberg could be having issues. <quartz>it happens for all channels (gitlab too) I think the issue is with me <quartz>and i can do a git clone myself with no issue <ieure>I don't know, then. Restart guix-daemon? <quartz>doesn't work, rebooting didn't help either <ieure>Weird. You can clone the same repo from a shell? <Rutherther>quartz: does "guix build hello && guix build hello --check" succeed for you? <Rutherther>sorry rather "guix buiL hello && guix build hello --check --no-grafts" <Rutherther>and you've installed guix through the guix-install.sh? <quartz>is it for foreign distro? I installed guix system <Rutherther>oh you're on guix system even? then I have no idea what the issue is at all. You aren't the first with this problem, though <Rutherther>I was thinking it could be some sort of 'protection' that misbehaves, something like AppArmor/SELinux, but there are more aggressive variants <yarl>quartz: you might try to wrap guix pull into strace? <yarl>Dunno it that would work but worth a try <quartz>it's very verbose but nothing that catches my eye, should i be looking for something specific? <quartz>connect(16, {sa_family=AF_INET6, sin6_port=htons(443), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2a01:4f8:c013:3c5b::", &sin6_addr), sin6_scope_id=0}, 28) = -1 EINPROGRESS (Operation now in progress) <quartz>poll([{fd=16, events=POLLOUT}], 1, 30000) = 0 (Timeout) <ieure>quartz, Ah, either you or Codeberg have IPv6 issues. <ieure>quartz, Can you ping Codeberg's IPv6? 2a0a:4580:103f:c0de::1 <makx>ping does work from here <quartz>nope, I can't, is there a way to force IPv4 ? <Rutherther>sure couple of options, ie. you can set net.ipv6.conf.all.disable_ipv6 and net.ipv6.conf.default.disable_ipv6 to 1 through sysctl