<rekado>we also may not need to use *all* files contained in ghc-4.08.2-hc-unreg.tar.bz2
<rekado>if we can manage to go about this intelligently we might be able to get away with only picking a few of those files.
<Andronikos>The package stagit does not come with manuals. Was it forgotten?
***califax_ is now known as califax
<johnabs[m]>Hi guys, can someone quickly give me a heads up on how to get npm working in guix? I thought it was packaged under node, but when I tried to use an environment with node added, npm was not present. Is it packaged elsewhere?
<yuu[m]>that makes me wonder: is there cli app for locating arbitrary files in all derivations produced by guix repo? akin to nix-locate
<zamfofex>I have been investigating the issues regarding Guix and Repology, and I was wondering if there is any way I can help or incentivize work to be put towards resolving it. It seems that Guix blocked IP address ranges including Repology’s because some such addresses (not including Repology’s) were performing mischievous actions such as port scans. I was wondering whether it’d be possible to choose the address ranges more selectively
<zamfofex>(So to not block Repology.) Or conversely to reassess whether there is still an issue regarding those IP addresses at all.
<apteryx>Repology's server is in Russia, and it seems the whole (?) of Russian IPs has been blocked from accessing the networking on which the MDC operates (where Berlin is hosted)
<apteryx>rekado: do you happen to know why the Russian IPs are being blocked from accessing the network used by the MDC?
<GNUtoo>If I do (if (not (target-x86-64?)) (service foo)) then it works only if I'm not on x86-64, otherwise I've some error like that: In procedure struct-vtable: Wrong type argument in position 1 (expecting struct): #<unspecified>
<GNUtoo>The examples in the guix source code there are always two statements, one when the if is true and one when the if is false, so the error doesn't happen because it always return something valid in any cases
<Kabouik>I've had issues two days ago with LibreOffice Impress crashing when saving and then forgetting all about my environment (my dark GTK theme would be light again, and some fonts (but not all) were missing). I'm not sure how to reproduce that; it occurred several times but rebooting fixed it. Anyone ever observed that too?
<rekado>apteryx: no idea about Russian IPs. I don’t know if they are blocked by the MDC or the wider DFN network. All I was told was that there had been a massive increase in attacks on the MDC infrastructure coming from that range of IPs, so someone decided to block them at some level.
***wielaard is now known as mjw
<jonsger[m]>rekado: s/a user/an user/g or? I think its a typo in your last cookbook commit, but I'm not 100% sure with English...
<horizoninnovatio>A friend is having trouble installing wine-staging on fedore silver-blue ("immutable operating system"). Could the Guix package manager be a good work-a-round to solve this issue? Are there any potential problems? thank you :)
<cbaines>sometimes, but if it fails to start the first time, it usually only takes one or two attempts to get it to start
<nckhexen>I thought Leo might want to handle it, but it's been a week. sektor[m]: What I don't understand is why use %default-extra-linux-options, and not gnu/packages/aux-files/linux-libre/5.19-x86_64.conf.
<sektor[m]>Good question. I was going off what I remember from the cookbook.
<civodul>cbaines: i like the optimistic tone of your reply :-)
<civodul>sektor[m]: re services, you'll want to have the doc in doc/guix.texi, under the relevant section
<civodul>(now solved because ran "guix build xf86-video-vesa" on berlin, but the question remains valid :-))
<nckhexen>sektor[m]: I wonder if anyone has a clear reason. ☺ I think there's no reason not to put these in .config, but I'll take care of that. Thanks! How accessible is our installer after this change?
<civodul>nckhexen: yes, but i'm fine either way :-)
<nckhexen>I was going to add them to the .configs instead, because I'm not convinced that the dichotomy is meaningful (IIUC, our .configs are not ‘vanilla’, they are already ours, so why have another layer?).
<nckhexen>sektor[m]: I think I've noticed the same (the kernel failing to request_module() one that should have been there). It wasn't the core problem at the time so I didn't debug it. I don't know if initrd module loading (as opposed to the brute-force load-linux-module done by linux-boot.scm) is even set up at all.
<sektor[m]>Interesting. I was pulling my hair out when I was working on it last week.
<civodul>nckhexen: did we already hit that before? (xz OOM)
<nckhexen>‘Physical’ yes, but I assume you're talking about the 32-bit address space limit here?
<nckhexen>So, here's something I was going to say anyway: I've been absent from Guix a lot lately, I know. It does not take an astute reader to correlate this to increased activity by a certain individual, as much as I wish I were stronger than that. *That* is 90% of what I associate with ‘Guix’ now. Which sucks, as I've always got my energy from the social channels. And me being trivially nerd-sniped into fixing/coding/helping, that worked well for everyone
<nckhexen> ☺ Until it didn't. I'd like to get over that. Which means that I'm looking for useful work to do to make this fun again. I guess I'll go read the 1.4 thread, which I've been avoiding.
<mbakke>civodul: yes, let's get it done; anything in particular that needs to be done?
<patched[m]>For some reason, `guix package -u` insists on building nheko, even when `guix weather nheko` as that substitutes are available both on ci and bordeaux... Why? And can I fix this somehow? I've had the same problems with other programs in the past too.
<nckhexen>I hope you all make it to Brussels this year (if allowed) and we can all celebrate Guix's teenage years in style.
<patched[m]>I have too little ram to build the derivation on my own
<Baptiste>Hello everyone, I don't think the question I'm about to ask is a borderline question, so please correct me if I'm wrong. Can someone tell me what options do I have left trying not to use the proprietary driver for my GPU when the package xf86-video-nouveau didn't seem to be able to start the X server?
<gnucode>Baptiste you could try to blacklist the nouveau driver.
<gnucode>then it'll fall back onto Intel graphics or vesa.
<nckhexen>sektor[m]: You're probably closer to remembering the solution than I am to debugging your issue, but ‘guix shell glibc -- locale’ might be a start.
<gnucode>one of those should work. You won't be gaming anytime soon. :)
<apteryx>gnucode: that shouldn't happen (we tell xz to use 50% max the system memory); perhaps there's a bug
<Baptiste>gnucode I tried that, the X server does start but my HDMI is not recognized by xrandr and I cannot connect my external monitor
<apteryx>civodul: are you perhaps packing multiple tarballs in parallel, or doing more than one build on that i686 machine? xz will use maximum 50% of the system memory
<Sughosha>Hi Guix! I am packaging something and want to build it by trivial-build-system. I want to have the arguments with gexp like "(#~(list #:modules ((guix build utils))))", but I am getting this error: <https://paste.debian.net/1257053>.
<Boo_>Does anyone know what could be causing this issue when reconfiguring my guix system after adding the bluetooth service? `No applicable method for "#<<generic> provided-by (1)>" in call (provided-by "#<unspecified>")` My config can be found here: http://paste.debian.net/1257057/
<nckhexen>I quite enjoy manually configuring my kernel, but I am also a bit odd. What I mean is we seem to have manually curated x86/arm .conf files, but not for any other architectures. So I am going to apply your original patch to linux.scm, because otherwise it wouldn't take effect on riscv64/powerpc64. But I don't understand the rationale if there is one.
<nckhexen>ekaitz: Please share the messages, don't just report ‘errors’.
<ekaitz>nckhexen: uf it just fails with the references from the docs
<sneek>daviwil, podiki[m] says: saw you had a stream about the fhs container, sorry I missed it! I see some tips I have would be useful to be shared (better get to that cookbook writing)
<podiki[m]>just tweeted you actually, with the answer for what you were trying to do :)
<podiki[m]>I tend to use -D ungoogled-chromium since that pulls in pretty much everything for any web/graphical apps
<podiki[m]>the other trick is the right things to share, especially for hardware access
<podiki[m]>the other fun thing is appimages, really all you need the fhs container for is to run it to get the offset as it is called, then you can mount it as a disk image without a container (no fuse mounting in the container allowed I guess)
<podiki[m]>(the software you were trying was next on my list for that other package channel, too)
<daviwil>Cool! I didn't see the tweet, was it on Mastodon or Twitter?
<abhiseck`>is it possible to undefine C keywords? I just saw "#undef const"\n "#define const" in a source file.
<unmatched-paren>abhiseck`: #undef is sometimes put before #define to "protect" the #define, as ``#define FOO 34'' after ``#define FOO BAR'' will actually do ``#define BAR 34'' because of the already-defined ``FOO'' macro
<abhiseck`>sorry, I don't know a better place, it's related to coreutils though. coreutils doesn't have a irc channel afaik.
<sektor[m]>Nw I need to figure out how to mail patches in Emacs so I don't have to context switch.
<unmatched-paren>It's fine to discuss non-guix free software/programming related things here, afaik.
<abhiseck`>unmatched-paren: that's a relief that I'm not violating channel rules. :-)
***tsv is now known as tsvallender
***tsvallender is now known as help
<lechner>unmatched-paren: Hi, the wording of "non-guix free software" depends on the dash, doesn't it?
<unmatched-paren>lechner: Not really. It's supposed to mean "free software that isn't guix". Though I agree that it's a wee bit unclear in general.
<unmatched-paren>non guix free software is basically the same as non-guix free software. Just a stylistic difference.
<tsvallender>I'm trying to allow non-root users to run the 'light' program, which I believe I do by adding it to setuid-programs, but I must be doing something wrong as it's currently making my entire operating-system invalid. What's the right way to do this?
<Kabouik>I suppose #guix is a bit of an emacs antichamber (it did drag me to trying emacs after all these years)
<Kabouik>Cool. I want to use emacs -nw exclusively. When emacs opens new emacs windows (which I will call panes here just to avoid the ambiguity with WM windows), like with `C-h ?`, or in my case `M-x R RET`, it splits my terminal window in two panes.
<Kabouik>I would want it to actually open a new $TERM window and show the new emacs buffer there.
<Kabouik>This would also allow me to more easily move/arrange/resize windows with my WM keybindings, including spreading windows on multiple screens.
<rekado>this wouldn’t deal with *any* and *all* window splits, though
<Kabouik>I was thinking about exactly something like that unmatched-paren (although I didn't know how to write it). But how can I tell emacs to use that when it starts new panes from my actions in the first window?
<rekado>emacs has the deprecated pop-up-frames variable and pop-up-frame-function
<Kabouik>I'm really surprised that counting on the WM to manage emacs windows is a corner case. That seems like the best way to use multiple monitors and workspaces. I know I could manually start a new client and then display a buffer from the server, but that would be a lot of manual step, and the buffer would have opened in the server window too, which I do not want
<rekado>Kabouik: in Emacs if you want your window manager to handle windows you need to let Emacs create a ‘frame’ whenever a buffer is to be displayed.
<rekado>the manual has a lot to say about this in section 29.13.4 Additional Options for Displaying Buffers
<Kabouik>I'll look into it then, thanks, both of you