<hji>could someone point me to any docs on what constitutes free software in the context of guix packaging? esp. with regards to minimized JS for self-hosted documentation etc that fedora and debian has a policy of removing, whereas guix seemingly doesn't (at least not for the few packages that i've checked)
<mmalter>Hello everyone. Quick question, might be silly, I am a newbie. Can you make profiles depend on eachother? Include a manifest in another one? Does it make sense doing so?
<nckx>bavier1: <binary blobs> Well, their argument seems to be that you can assemble the blobs at home from the totally-not-a-blob assembly code (which can only be generated by said problematic compiler), so they're not *binary* blobs! …OK?
<nckx>Probably that its fine, like a GPL software programme written only for Windows would still be able to incorporate other GPL components. It doesn't violate the licence. ‘Freedom’ isn't a legal concept.
<mmalter>In that case it's all well. I was thinking about what happens if there is a breach that could be contested on the basis of wether the assembly code *is* the main implementation. It is left to the court to decide where you draw the line between gibberish and usable source code. Hypotheticals…
<nckx>$partner calls all programming languages gibberish. Humans wrote megabytes of copyrightable source code by flipping front-panel 0/1 switches 😊 It's, like, all relative, man.
<bdju>nckx: did my first reboot since making the luks config change and it worked fine, asks me for the password before login even with it not being the root drive, then mounts fine.
<bdju>nckx: also I noticed several errors while booting up including that old cpm or whatever one you had noted as a difference, so I guess it still does appear. but I was able to get to the login fine. (I guess we did determine the mounting was the issue back then)
<bdju>also in case anyone has weirdness with their sway screenshot bind breaking, a reboot just fixed that for me
<nckx>Yep. The CP437 error would only be suspicious if you were building a custom kernel, since it's built into the Guix ones. (No idea what that error message is trying to say, then, but it doesn't seem to matter.)
<roptat>I found bug reports upstream, and tried solutions listed there, but it didn't work
<roptat>apparently the issue happens on other distros too, but for an unrelated reason: they apparently use qt5ct which we don't have, and it messes with icon search path, so the solution is to ensure the application name is reset before searching for the icon
<roptat>I applied the patch for the future version of keepassxc, and I tried to install qt5ct too, setting the right environment variable for it to be selected, but that didn't work at all
<roptat>bdju, I don't even get anything from running it with strace... I'm rebuilding with more debugging, and I think I can "hide" the issue by having keepass fallback to a hard-coded directory in the store
<roptat>so currently it does "icon = QIcon::fromTheme(name);" but fromTheme can take an optional QIcon argument that it falls back to if it doesn't find name in the current theme
<roptat>well it won't help actually, when the icon is not provided directly by keepassxc
<Guest14769>Hi, this may not be the place to ask. But I'm trying to run a windows image that contains malware using virtual manager. How do I configure it so that it has not connection to the internet or my host machine. It's just to prevent the malware from maybe escaping.
<roptat>Guest14769, when the machine is stopped, you can open it (from the list of machines, double click on it, but don't start it yet). The window that opens for the machine should have a "i" icon in the toolbar that lets you configure the hardware options, including network
<roptat>bdju, ok, if I hardcode my theme name, I get a few icons, so qt seems to be unable to find the default theme name and immediately falls back to hicolor, where it finds almost no icon