<nckx>Hi Guix. I've reinstalled my system and now get ‘Unable to activate package ‘use-package’. | Required package ‘bind-key-2.4’ is unavailable’ (only context implies the two are related). What's up with that?
<pkill9>why does `guix --version` no longer show the git commit it is on?
<PotentialUser-26>Is there a way to see which config is used to produce a certain image on CI?
<pkill9>so ive created a package within home.scm but when I append it to my packages list and reconfigure home, it doesn't install, and when I display the output of the packages list, all the vanilla packages have "out" at the end but not my created package
<orneb>nckx: I tried what you and unmatched-paren suggested yesterday but didn't work. Libreoffice is still missing the menu bar. I added exec dbus-daemon--session --address=unix:path=$XDG_RUNTIME_DIR/bu\s in my sway config file and dbus-service in my desktop.scm but didn't work.
<nckx>unmatched-paren: A series of 'magic sysrq' keys that will do stuff that you've probably already read by now.
<nckx>F didn't work, or at least my screen stayed blank.
<unmatched-paren>> Before the advent of journaled filesystems a common use of the magic SysRq key was to perform a safe reboot of a Linux computer which has otherwise locked up (abbr. REISUB), which avoided a risk of filesystem corruption. With modern filesystems, this practice is discouraged, offering no upsides over straight reBoot.
<nckx>Cunterpoint: bcachefs. I'm going to do all the precautionary stuff I can reasonably do.
<nckx>Thanks! Before I go, I'll just nudge this here: if anyone has any ideas about my original question (‘Unable to activate package ‘use-package’. | Required package ‘bind-key-2.4’ is unavailable’’), I'd be tickled pink by a ping. o/
<Lumine>This might be going out on a limb here since I'm a complete emacs noob but... M-x package-refresh-contents, nckx ?
<nckx>That prints things like ‘Contacting host: elpa.gnu.org:443’ so I'm not sure it's relevant to Guix-managed emacs, but thanks. I'm no emacs wizard myself, but I do miss ‘my’ emacs.
<Lumine>Like, I want to have guix manage the emacs and exwm, but I found some hassles with the latter, but that might be because I can't for the life of me figure out how to make a .desktop file that is discoverable by guix
<unmatched-paren>because i think i'll use them next time i send a patch that needs an operator if they are
<orneb>nckx: I reinstalled my system (Yesterday I messed it up with some kernel arguments and couldn't access the grub menu because I forgot to add (terminal-outputs '(console)) and with just dbus-service now libreoffice is showing the menu bar.
<phf-1>unfortunately, Cuirass seems unable to discover the remote worker with Avahi but the worker is taken into account by Cuirass when the parameter `(server "yyy.yyy.yyy.yyy:5555")` is added to `cuirass-remote-worker-service-type`.
<abcdw>nckx: Wrote a summary on subkey authorization problem, which happened last weekends, want to publish it on guix-devel for future reference and also to discuss subkey authorization support. Would be glad if you take a brief look and let me know if I missed something.
<nckx>podiki[m]: Subkey renewal isn't a problem (the key wouldn't change). It's indeed replacement and simply people who use different subkeys having to have each one added to the list, and not allowed to mint new ones without adding them later.
<podiki[m]>I just broke a certain other channel for the same reason, confusing of course since gitlab's handling of signing commits has nothing to do with guix pull's handling
<podiki[m]>while I'm at it, was anything else needed on other developers ends? meaning if they had just done a git pull with the offending commit, just a reset --hard back?
<apteryx>has anyone used 'vncviewer' from tigervnc-server successfullly on their tiling window manager?
<nckx>‘Just’ is a big word, but the only action we took so far was to hard-reset yes.
<nckx>The problem is that is is not something *anyone* on the Guix team can do.
<apteryx>it works in window mode, but doesn't for me in full screen, which is a pity because only fullscreen mode capture all keyboard keys.
<podiki[m]>nckx: okay, hence the "contact someone at savannah"
<nckx>podiki[m]: This can be framed as a extra security safeguard but I don't take that seriously either, since their are much less disruptive ways to compromise master. This wouldn't be a useful ‘attack’.
<nckx>podiki[m]: If you mentioned that I missed it.
<podiki[m]>nckx: perhaps just making sure the guix emacs site-lisp is in the load path (I thought it should be automatically, but mine is not for some reason); then as long as ensure is nil for use-package (should be default) it should find the guix packages
<podiki[m]>nckx: perhaps also (guix-emacs-autoload-packages) ? maybe i'll tackle this later today as well :)
<apteryx>nckx: I mean like capturing Control, Alt, everything except its escape key (F8)
<apteryx>so that I could use ratpoison or emacs comfortably from it
<apteryx>if you put vncviewer fullscreen it does it, but this mode seems broken on ratpoison (doesn't display/refresh correctly -- seems to use the full monitor instead of the ratpoison frame)
<podiki[m]>perhaps a WM setting with what keys it handles? making an exception for fullscreen?
<raingloom>hey so jupyter notebook doesn't find mpmath, but jupyter-qtconsole does. any clue what's up with that?
<PotentialUser-6>raingloom oh yes, that would be great. I'm also interested in the usb plug in, I guess that would make me avoid using non free stuff. But I need wifi fast though so for the moment the non free option is good
<apteryx>gnucode: I use that one on a laptop, it's very reliable because the driver is in the kernel tree, but it's limited to 2.4 GHz.
<raingloom>solved the jupyter issue, it seems the first one i opened didn't exit, so when i restarted it in a new environment, it used a different port, but in my browser i just reloaded the tab, so it kept talking to the kernel i started first.
<vivien>Dear guix, I think I remember the time when there was an attempt at an NPM importer, but I can’t find anything related to it anymore. Did I invent it? Dit it exist at some point? Did it get removed?
<raingloom>apteryx: if someone needs network access *right now* i'm not gonna tell them to wait for a new usb wifi adapter. :)
<yuu[m]>unmatched-paren: it solves dependencies to create a nix package and such from a ndoe project. but all these from my experience create a fixed output derivation package-deps, then use that as input for building the project
<dthompson>and I found that the releases or the repo just had minified files. so problem #1 was: how do I build these from source? I needed grunt (or gulp, can't remember) and a minifier.
<unmatched-paren>i suppose you'd do <something something sqlite> (<- this is what it looks like when unmatched-paren thinks about a thing they know literally nothing about)
<dthompson>it wasn't long before circularity and massive dependency trees revealed themselves.
<unmatched-paren>sadly, I can't think of a stronger word than "dystopia" to describe this situation
<dthompson>circularity is always a problem with these language package managers for one reason: the notion of "development" dependencies.
<yuu[m]>unmatched-paren: yeah nix-index is pretty useful. then nix-locate to find which derivation has a specific file you need
<dthompson>it's a separate tree that no one ever deals with unless they are a developer on the project
<dthompson>but typicallyi you need that whole tree to build from source with guix.
<dthompson>which immediately puts guix on a path that no one else is going down
<vivien>dthompson, but now we have esbuild in guix, and that beast minifies anything
<dthompson>back when I was an active contributor I had more than one "why would you do that?" response when I tried asking questions to people outside guix
<vivien>To quote dustycloud, back in the days: Unfortunately, Nix just downloads the prebuilt binary and installs that, which in the world of functional package management is kind of like saying "fuck it, I'm out."
<efraim>ekaitz: wait, that's it? that would make it pretty easy
<vivien>To be honest, I would definitely vote to have non-bootstrapped free software in guix, but I guess that sorting out which NPM packages are free software is not a lot easier than sorting out which one can be built from source
<unmatched-paren>cwebber: yeah, same with rust. the language has cool ideas, the ecosystem is both offputting and mandatory
<efraim>We also have the python phase to try to search for cythonized files
<cwebber>well GNU's leadership also objected to the code of conduct, and also Emacs's manual talks about how to work with windows
<dthompson>unmatched-paren: right, so I say let the *goal* be to not do that, and make special exceptions where necessary.
<vivien>dthompson, being tied to GNU does not impact the bootstrap issue
<dthompson>I think that strikes the right balance between ideal/vision and pragmatism.
<dthompson>importing a ton of nodejs stuff: that's just opening the dang floodgates
<cwebber>dthompson: yes, so I think the ideal would be: have a npm channel that we can tell people about
<cwebber>"oh yeah, you want that stuff, hey go use this thing"
<dthompson>vivien: sorry, I was referring to the "don't speak of *that* channel" thing
<yuu[m]>dthompson: i'm somewhat opposed to that too. this is because i see the issue from the nix side of things, and it is not pretty. people just go that route and don't care anymore about actually building from source when things are hard to do so or not mature tooling around it.
<cwebber>"sorry it'll make our life hell if we put that in here and this is not the place to develop it but it's there for you"
<Noisytoot>cwebber: If it only contains free software, you can tell people about it here
<vivien>Yeah, but we could have an official channel with binary free NPM stuff
<unmatched-paren>vivien: it was in response to cwebber mentioning the fact that the forbidden channel is forbidden
<vagrantc>there are all sorts of ways upstream can make things go ugly, e.g. asserting "moral rights" and whatnot
<dthompson>okay last thing: it's weird that open source devs are more frequently trying to control how their software is built and distributed. been seeing that kind of behavior more and more.
<vagrantc>efraim: you fixed lcsync non-x86 builds! thank you!
<efraim>vagrantc: and it was my first time playing with simde!
<yuu[m]>unmatched-paren: idk what to thing about this tbh. guess people are exercising their free-speech. but well it is true that then if the dependency-author wanted could just relicense make it non-free non-redistributable or somethin.
<vagrantc>efraim: i need to import that into debian :)
<efraim>I still got a non-fatal test error on x86_64 but I couldn't find a different header to use that would fix it
<unmatched-paren>dthompson: I think that's what happens when people make (free|open) source software without actually believing in it... they get protective and have this idea in their head that the software is "theirs"
<yuu[m]>dthompson: vagrantc unmatched-paren i think the problem was that dependency author did not want to deal with any related issue from nix people or any third-party. it is almost the same instance that rich hickey clojure author takes.
<yuu[m]>so forking would be the most reasonable way of doing things.
<unmatched-paren>i think nix users would be intelligent enough to know that if there are problems with the package, it's not necessarily the upstream maintainer's fault
<yuu[m]>unmatched-paren: it is not that. imagine nix people or any third-party unofficial distributor creating issues in their bug tracker. sometimes it is kinda hard to trace if the problem is nix, the software, etc etc
<drakonis>there were other instances of home-assistant people going into nixpkgs to complain about it getting packaged
***euandreh_ is now known as euandreh
<yuu[m]>unmatched-paren: indeed. but some people just do not want to deal with that for free. sometimes licensing as free software in a kinda of free community for some people is just a means for their objective. i'm not sure about this particular case though.
<acrow>Enjoyed reading the last discussion. Is it free software if no one can build it? Guix requires 'build instructions' and that's a huge virtue. It is also secure which is another increasingly important word.
<acrow>When guix adheres to it's highest bootstrapability standards it is the best corroborator of software security and freedom I'm aware of.
<yuu[m]>unmatched-paren: btw do you have a link to that free vs impossible to build stuff? i think that makes sense but never saw a fsf/gnu piece on that
<nckx>It's really bad, and I just realise it will still match primaries unless I add a "^" or something. We're just relying on style conventions. But I'm waiting for confirmation that we can use Guile here, and if so we're off to the races.
<gnucode>nckx I'm starting to wonder if you have God-like powers....
<gnucode>I don't know how you are so productive in helping guix. :)
<amk>has anyone had luck with installing guix on the pinebook pro, to emmc?
<podiki[m]>nckx: not sure if it is the same, but in another channel having just tried switching from primary to subkey in authorizations did not solve a bad pull (still complains about not authorized); we did not first fix it though as was done here
<nckx>No, it won't fix it unless you roll back (a nice word for a hard reset) upstream.
<vagrantc>acrow: hmmm.. NEWS should be PERMISSIVE-VARIANT1
<vagrantc>acrow: this is totally good enough to be usable, though, thank you so much!
<ekaitz>hi I'm having an issue with a package I'm making: the makefile generates files in the source tree, but it says "Unable to create file", if I jump to the failed build directory, set the environment vars and run make it generates them with no problem
<nckx>$HOME, for example. Disallowed in the real build environment, happily writable when merely jumping in.
<nckx>../../../../build always makes me wonder. Is it possible to share the package here?
<ekaitz>yes, but I need to change something first to make it free-software compatible, it doesn't use free software but it depends on a package that has some nonfree software and the patch that removes it is not set yet