<ieure>And a previous one almost derailed the buyout of the company I was at. I was an early employee and had no problem getting them to sign the waiver. Then the company who was buying us found it in the bottom of a filing cabinet and FREAKED OUT and it became an issue raised to the board of directors of both companies, one of which was a $10b+ global bank.
<vagrantc>and how many decades have passed since the FSF did any actual enforcement?
<vagrantc>and ... on that note ... off to other things :)
<podiki>sorry, don't use them (toolbar off). but i have had problems with posframes (like the bar at the bottom but floating as box, not quite a real frame) recently
<isaneran>hmm wanted to prevent guix from downloading so much stuff again after runnin guix gc, one of these packages being guile-3.0.9-debug so I installed guile:debug which I thought would solve it but nope, still downloading it over again
<KE0VVT>lilyp: Corporations would welcome contributions to Apache Software Foundation.
<lilyp>yeah, they love themselves some rollover licenses
<bryan>I'm still finding my bearings with guix. When trying to sort a problem with ublock-origin not completely blocking ads in ungoogled-chromium, I removed the extension from within chromium and can seem to get it back. Can someone give me a hint and reference to docs where I can read up on how one should go about handling browser extensions in
<bryan>chromium? Both packages are installed (and reinstalled) with guix.
<sner>bryan: you'll find that there are quite a few spots in guix where the best (and sometimes only) source of documentation is the guix codebase
<KE0VVT>A literate programming Guix codebase would be cool.
<sner>bryan: ~cd $(guix build -S guix)~ is your best friend for when that happens
<sner>KE0VVT: bryan: if you're running into issues with chromium auto-loading the extension again after removal, it's almost definitely some state left over in your user-local chromium profile. if you don't want to purge the ~/.config/chromium dir entirely, targeted removal of some of the cached configuration there and running guix reconfigure should do it
<bryan>sner: KE0VVT: No, I just want it back after I removed it, but it's not as simple as searching it up in the google store....not complaining about that! I just need to learn more, and guix is a defferent beast.
<bryan>sner: KE0VVT: judging by my inability to type....I probably just need to sleep and it'll be a simple fix in the morning.
<Kabouik>So what happens when you're on an >2-month-old package generatioon, and you run a `guix packageqe --delete-generation=2m`? I think I did that. All running processes gradually started to stop working, and the only later generation I have is broken due to power outage during the update. That'll be interesting.
<lechner->Hi, I would like to test some changes to our bootloader configurations. How may I do so without borking a real system, please?
<gabber>Kabouik: sounds like another edge case for that gc-bug you've encountered yesterday (:
<Kabouik>Actually gabber, I had to hard-reboot due to the above issues with all processes failing, but could reboot back so nothing is broken. But I still don't understand why a guix gc would break a running system.
<Kabouik>I still want to report it, but would like to better understand what is happening first.
<gabber>i *guess* the garbage collection was too greedy without checking whether stuff is still in use
<Kabouik>It was indeed more greedy than usual (would free 100GB!), but it couldn't complete so I'm still left with very low disk space left (18GB according to df, but I'm in btrfs so that is likely inaccurate).
<gabber>and by giving the 2 months option on a profile that uses older software you're somewhat implicitly telling the gc to also collect that stuf.. imho it should at least warn the user or hinder the user from doing so
<Kabouik>I was wrong on one thing above: my current generation was not older than the 2m pattern, it was actually just a few hours old, so that generation should not be comprised in the delete-generations pattern
<podiki>i guess the error is complaining that in hurd-boot it doesn't find something it depends on? (unfortunately i also find these error messages hard to parse; if guix builds (not pulls) then there shouldn't be a circular dependency at least)
<gabber>maybe loading the modules in a repl raises a more useful error message?
<lechner->it's probably including something i worked on
<Rovanion>Is Pipewire ready for use on Guix System yet?
<lechner->some folks use it. i would like to but don't yet
<Kabouik>Is there a way to limit the CPU power that a guix command uses? I have tried "cpulimit -l 10 guix install mypackage", but there is no way this would be the clock and temperature of my CPU if that was taken into account: https://0x0.st/Htd_.png (and it was 2.9 GHz a minute ago). This is critical for me, because every "heavy" guix command I have run lately has ended up in a generalized crash of the system, presumably due to prolonged overheating, or too
<Kabouik> stringent throttling. I'm okay with waiting more, I just want the commands to complete.
<Rovanion>gabber: Not a given, it wasn't last time I wanted it on a system /shrug
<gabber>could some more active passive cooling be of help?
<Kabouik>I'm on a very compact laptop yes, but this didn't use to be an issue. And anyhow, why would cpulimit not work with guix commands?
<lechner->Kabouik / what's the last time you cleaned the heat sink
<lechner->please don't use a vacuum. you can damage the fans
<Kabouik>It's due now, but still, the temperature when idle is quite acceptable at around 45°C. The thing is my laptop may not be able to handle the full CPU power, so I'd want to limit it. Is that in BIOS only then?
<gabber>Rovanion: i've been using it for quite some time now (not sure how long exactly). it might work better or worse with different setups
<gabber>Kabouik: i have little to no experience with cpulimit but your $(guix) command only instructs the daemon to do stuff. you probably want to cpulimit your guix-daemon
<gabber>unfortunately i have no help to offer WRT this
<Kabouik>That's a good point gabber. The cpulimit command I'm using works with every other process, so I beliee you're right. Can I just kill the daemon and reload it with `cpulimit -l 50 guix-daemon`?
<gabber>Kabouik: i'd opt for trying to fix the hardware/BIOS config before going down that route
<gabber>but i guess you're pretty emergency proofen by now ;)
<Kabouik>I will try to clean the heatsink for sure, but if I'm that close to the cooling limits of my computer, I'd still like to limit the clock of the CPU for commands that can last very long like guix ones
<lechner->any computer will overheat with a clogged heatsink. i try to clean all of mine once a year but the laptops can be hard to open. any brand laptop should be built to cool properly unless you overclock
<Kabouik>The thing is my computer is 8" with an i7 gen11, so long and intense CPU jobs might be an issue even with a clean heatsink (but I fully agree that a clogged one won't help; I don't think mine is too clogged, but it's certainly not mint).
<lechner->cleaning up your desk, especially from stray clothing, may be another viable solution!
<podiki>properly working hardware should handle heat and throttling to not cause damage ever; wanting to run better thermally and be in more control of it sure, but it shouldn't damage itself
<podiki>e.g. if cooling is not sufficient a processor will clock down or just switch off, at least that's what i understand about them
<jpoiret>yeah, i'm looking if upstream has some solution on the MLs
<mwette>I've created a foo.scm package file. If I add the package symbol to the end `guix build -f foo.scm' works. If I remove the symbol and add the file to my channel-dir (and update git), then type `guix show foo-pkg1' it says "package not found". What did I forget? I've done this before.
<civodul>mwette: hi! that suggests foo.scm is not in the package search path
<civodul>to fix it, try “guix build -L . foo-pkg1” or similar
<civodul>where “.” is the directory containing foo.scm
<civodul>beware: every *.scm file in there will be loaded
<podiki>mwette: and if you haven't added it to the channels your user uses (~/.config/guix/channels.scm) and then do a guix pull; then guix won't know about it (using the -L as noted above is the alternative)
<mwette>civodul: Thanks. I think it ay be another issue. Trying something ...
<podiki>civodul: question on grafting: after an ungraft, that's when we might see packages fail to build due to some change in the now ungrafted dependency right? (even if abi compatible) or in tests failing? since both otherwise happen before grafting takes place right?
<podiki>(speaking about packages using a dependency that had a replacement)
<Franciman>hi, what's the best way to get started with guix system?
<Franciman>should i read the whole docs before being able to get started with it?
<mrh57>Franciman: why not just go ahead and install it? there's an ncurses/tui installer so you don't have to know anything to set it up, and then you can just look up the things/read the relevant sections of the docs for stuff you wanna do
<Franciman>i will try tomorrow for sure on my thinkpad t450!
<podiki>mwette: what is the name of the package (that is what guix show/search look at, not the variable name)
<mrh57>Franciman: have fun! do let us know how it goes
<KE0VVT>Franciman: Nice. I'm here for the free software policy.
<Franciman>well more resilient than debian maybe is wrong, but at least not so brittle, since i can do rollbacks
<mwette>podiki: thanks -- I checked ; that does not seem to be it
<nathan-web>I'm looking to configure my laptop to automatically login but to a locked screen. I see in the X-Window documentation a way to configure various DMs to auto-login, but is there a more minimal one that doesn't include the login interface?
<nathan-web>It sounds like I might be looking for a DM without a greeter?
<ieure>nathan-web, What do you hope to gain by auto-logging into a locked screen? You're going to have to enter credentials to use the laptop either way. What's the difference between authenticating to the display manager vs. the screen locker?
<nathan-web>Auto-loading applications so they are ready to go when I unlock.
<ieure>Okay. But it's still going to take the same amount of time.
<ieure>Right, like, say this is the amount of time it takes to boot, log in, and run all your startup programs (boot at left, post-login launch at right): [=====/=====]
<ieure>And what you're saying is, I want that same amount of time, but divided like this: [=========/=]
<ieure>You're waiting the same amount of time either way.
<nathan-web>Logging in via greeter means the computer sits there not loading anything while it waits for me. Maybe I've walked off for a second. Logging in automatically will ensure that gets loaded anyway.
<nathan-web>And also loads in the background for the amount of time that it takes to type my password.
<ieure>Well, I don't agree, but okay. Seems like a poor tradeoff IMO, a lot of work and a real weird setup for a very niche usecase.
<ieure>I think the only thing you have to do is set the DM to auto-login, and put the screen lock command in your .xsesionrc (or whatever autostarts programs when you log in)
<Andronikos>I did just run "make check" on master. There were no fails but xfails. What are xfails?
<Andronikos>https://github.com/skeeto/impatient-mode it says in the impatient-mode.el file that it is released into the public domain but without any LICENSE file or text in the file itself. There are also some HTML files that have only code. Can this even be packaged for Guix?