<rekado>pkill9: GNU means different things to different people, and the perception of the umbrella project may change over time as the member project evolves.
<rekado>personally, I see Guix as an embodiment of what I consider to be the core of the original ideas of GNU
<rekado>to build a unified operating system that has is built around user empowerment (for the lack of a better term).
<rekado>it’s not just for the sake of building something neat.
<rekado>more concretely: Guix liberates users from oppressive sysadmins, it dissolves the hierarchy that is often baked into traditional GNU/Linux systems, it adds a safety net to make this practical, and it gives users unified tools to exercise their freedom and control over software distributed via Guix.
<rekado>it provides a unified way to manage the system at almost every level through Guile
<rekado>to me Guix delivers on the promise of the GNU idea, and it is a big part of what I wished GNU as an actual *project* was.
*rekado always waxes philosophically at this time of the day/night
<lfam>I don't think anyone ever expected to still be using the C++ code for this long. But everyone got distracted working on a distro :)
<cdegroot>(I am on Ubuntu, looking to move to Guix system but there are still small hurdles - for example, I need asdf-vm for work and builds of asdf-vm on Guix tend to be unhappy often; currently struggling with Erlang)
<lfam>Or maybe it delegates functionality to Guile portions of Guix. But, the daemon has a --discover option for this :)
<lfam>I'm looking at commit 79f9dee3c4c0e6d21066f142116a537207ae7ba4
<cdegroot>Ah, yup, you're right. I looked in the C++ code whether things were wired up for Avahi discovery but came up empty-handed. Well, something to try :) (the main reason I want this dynamic is that a bunch of installs run on laptops and even on VMs on laptops, so they're not always there; currently, with fixed substitutes, stuff times out which is not nice)
<roptat>isn't the avahi stuff delegated to publish / substitute, which are written in guile?
<roptat>come on, do you want your language to be behind French and Slovak? :D
***Server sets mode: +cntz
<mikegerwitz>Hey, everyone. I'm going to be submitting a patch series soon. The Guix manual says to send one message to guix-patches@ first, followed by the debbugs address. But looking at other patch series on the list, the timestamps in the headers suggest people aren't doing that. Is a References header (generated by git format-patch) sufficient for debbugs to handle this itself?
<nij>Hello! Currently, I put additional channels I want under /root/.config/guix/channels.scm , as suggested by the official manual. I wonder if I can add this in to config.scm, so that I don't have to manually copy channels.scm into that dir every time I start working on a new machine?
<brendyyn>hmm, doesnt look like %default-channels is configurable
<apteryx>mikegerwitz: Hi! If your patches are related (or dependent), they should be reviewed together, so should go to the same debbugs ticket
<brendyyn>apteryx: they're asking how to do that in one go, rather than two steps by first waithing for the debbugs response
<apteryx>if you just git send-email to bug-guix it'll create one ticket per patch, that's we recommend to use 'git format-patch --cover-letter ...', send the cover letter to bug-guix, then send the rest to the debbugs-NNNN@gnu.org email associated to the opened issue (you'll get a message back from Debbugs after sending the first mail).
<brendyyn>If you know how you would do the same thing on for example Arch linux, it would make it easier with understanding how to translate it to Guix's way of doing things
<logiz>I'm actually running guix in a vm, but that's because I'm trying to do all my dev work in a vm these days, and I ran into the same issue with fedora too, but I've just suffered typing xrandr every login, figured there's a better way
<brendyyn>when you run qemu you can set a resolution i think?
<logiz>yeah I'll try adding an xml change to virt-manager and see if that does it
<brendyyn>Frosku: Does your EMACSLOADPATH still have a refernce to the eamcs 27.1 path?
<rekado_>raghavgururajan: maybe you can come work with Altuna’s bioinfo group at the MDC. We write free software and hack away at cancer, herpes, and all that which can seriously spoil your day/life. And we use Guix.
<rekado_>mdevos: I can’t see *any* builds by limiting to “system”; I think you need to also add a search term
<rekado_>but for i586-gnu I can’t get it to work either
<smartineng>Hello I've just noticed some weird behavior inside the "guix environment --pure". Whenever I want to correct some commands in the [env]$ shell typing backward on my keyboard the cursor moves forward.
<rekado_>smartineng: I think this behavior is controlled by the TERM variable
<smartineng>btw. on "guix environment --container --pure" it works fine
<starfish>I installed guix on top of another distro, I have some questions
<rekado_>smartineng: I don’t know. I know that the behavior can *also* be controlled by the terminal emulator (e.g. if you’re using Gnome’s terminal you can configure the behavior of backspace in a profile)
<starfish>the packages I installed with guix (e.g., mpv), with 'man mpv' I can read the mpv manual. But when I run 'man mpv' from eshell it doesn't work. How do I fix that? Also similarly 'info guix' from CLI works but not from eshell
<starfish>So I tried logging out and logging back in, didn't work. Does it matter that Emacs I'm using not installed from guix?
<starfish>rekado: 'youtube-dl' when run from eshell wasn't working either. 'which youtube-dl' complained that youtube-dl is not found in PATH. I had to add .guix-profile/bin seperately in eshell using eshell's 'addpath' command. But I don't see something like that in case of info and man. :-(
<civodul>there's fat32 and fat16, but maybe exfat is different
<starfish>solved! Emacs looks for info paths in "Info-directory-list" variable.
<rekado_>starfish: the etc/profile file would also contain variables for man (MANPATH) and info (INFOPATH), though this may depend on having an info reader and man itself installed in the same profile.
<nij>Hi! Is %default-channels configurable? I hope to configure it with a more declarative way, instead of managing an extra file `/root/.config/guix/channels.scm`.
<nij>Also, how do I check the value of %default-channels? I evaluate that in a guix repl, but it's unbound.
<rekado_>nij: the module that defines %default-channels must be in scope
<BlackMug>i have question: since guix save old versions of the software (through generations?) does that mean the old software itself is still exist in the distro or just a record? (i mean by a record to it that it just save software name,version...etc then it will reinstall it again from the repository if roll back requested)
<rekado_>nij: instead of just declaring the symbols that are then looked up in the variant of Guix used to read the manifest you would declare the package names and the channels to be used to resolve the packages.
<BlackMug>brendyyn so the software its not really there when its upgraded, guix will save a record for the previous as lets say just data as package name x , date x , version x ..etc but the exact software has been replaced when its upgraded right?
<rekado_>BlackMug: I don’t know what you mean by “record”
<rekado_>whatever is installed via Guix ends up in /gnu/store
<brendyyn>BlackMug: Guix is way more advanced than that.
<rekado_>nij: when you ask for a package in your manifest, by default it will be looked up in the “invoking” Guix.
<BlackMug>rekado_ x package version 1 , new version of x package, upgrading to the new x package version 2 the question what happen to x version 1? is it kept as entire software or removed and just the record of it kept?
<rekado_>BlackMug: x version 1 will still be in /gnu/store
<rekado_>BlackMug: until none of your profile generations refer to it and you run “guix gc” to collect garbage.
<rekado_>only *then* will x version 1 be deleted from /gnu/store and thus no longer be accessible
<nij>rekado_: I'm a bit confused. I use `guix package -m muh-manifest.scm` to get packages.
<nij>But in this process, I'm never prompted into a repl.
<rekado_>the channels of the Guix that you use to run “guix package” will be used to look up packages in muh-manifest.scm
***zap1 is now known as zzappie
<rekado_>when using inferiors Guix starts a new “guix repl” process and talks to it to look up packages
<BlackMug>i see, but rise 2 issues bloating the of size and security concerns, for size bloating thats clear but for the security concern doesnt increase the surface attack + vulnerable software will be kept in the distro despite using the latest upgrades?
<rekado_>without inferiors we can simplify things and look them up directly
<rekado_>BlackMug: that’s why “guix gc” exists: to remove stuff you (provably) no longer use.
<nij>OH! So I want to `guix repl`, change %default-channels in it, load manifest.scm in it, and `guix package` in it?
<nij>!! linux-libre blocks everything that's unfree, without exception?!
<rekado_>brendyyn: there is a long-standing missing feature in linux-libre that prevents it from loading arbitrary firmware.
<leoprikler>Well the exception is that you need the correct deblob script for the correct kernel and you need to assume it to be correct
<rekado_>nij: no, but vanilla Linux gives us little control over what is and isn’t loaded, and the implementation of linux-libre is somewhat primitive.
<brendyyn>nij: Don't go jumping to conclusions like that. Linux developers haven't made it necessarily trivial to just remove or add proprietary parts. For example I once read there are code blobs embedded in source code some times
<PotentialUser-17>@civodul thank you for the link with the source. I am trying to add exfat support myself. How would I include a modified 'file-systems.scm' in a build or include the modifications in my config to check if it works as intended?
<mdevos>PotentialUser-17: that is a file in the Guix source code
<leoprikler>nij looks like you're failing to build the Guix derivation for that commit
<mdevos>to use it, you need to modify a "git checkout" of guix
<raghavgururajan>rekado / rekado_: I'd very much love to. IIUC, its in germany, correct? The situation is, I am currently in Canada as temporary resident, half-way way through to be eligible to apply for Permanent Residency (PR). Now I need to work in Canada for at-least a year, to be fully eligible to apply for PR. Does MDC have branch in Canada?
<leoprikler>(Interestingly, the main gitlab instance also handles issues/merge requests via mail, which I find hilarious.)
<rekado_>raghavgururajan: however, work is fluid and we sometimes hire people for project work or collaborations. You can send me things you are interested in via email and I’d check if there are ongoing projects that could involve you.
<nckx>nij: To expand on ‘partially’: you can reply to existing issues but not open new ones. The unauthenticated reply function, mind-bogglingly, has not led to a spam wave the size to wipe out all humankind. I wonder what black magic we have to thank for that.
<rekado_>brendyyn: that’s progressive enhancement; it will all work fine with JS disabled.
<rekado_>nckx: I think it’s just spam-protection by obscurity
<brendyyn>time guile -c '(+ 2)' runs in 0.007s for me
<rekado_>nij: Guile is pretty damned fast (on average faster than Python, for example), but performance depends on whether you interpret vs run compiled bytecode; and starting up Guile itself also takes a little bit of time.
<mdevos>Also, there are guile libraries that forgot to pass "--target" to "guild compile"
<mdevos>A 'verify-elf-architecture' check would be useful for debugging cross-compilation issues -- by preventing a cross-build from succeeding when the architecture of the binary is incorrect
<mdevos>(I've posted a patch fixing some cross-compilation issues in guile libraries some time ago) (unrelated to "guilx compile --target")
<nij>rekado_: turns out that geiser.el isn't enough. I still needed geiser-guile.el. Now it works! Thanks :D
<mdevos>I'll add 'verify-elf-architecture' to my TODO list. Maybe I can reuse some bits from 'validate-runpath' ...
<nij>Hello! I use `nmtui` for network management on my archmachine. But it's currently not available on the official guix channel. Whatelse would you recommend before I successfully learn to package myself?
<pkill9>it is available nij, i think it's in the network-manager package
<nij>thank you ``pkill -9``! How do I find this out in the future (for similar issues)?
<raghavgururajan>rekado_: Excellent site! I completely endorse the ideas. But why another site/infra for though? If there are internal conflicts (RMS or anything else), I truly believe that maintainers of *all* gnu projects can come to resolution through conferencing. I think its better to have one unified home for GNU; to avoid fragmentation, conflicts, friction, confusion etc. :)
<nij>maybe i should reboot? i just got network-manager for my user
<rekado_>raghavgururajan: we are not in disagreement, and there have been *many* attempts to having this conversation internally, just as there have been equally many attempts to avoid it or block it for the sake of some concept of “unity” that was never there to begin with.
<nckx>nij: <i just got network-manager for my user> Could you elaborate?
<nckx>I use (service network-manager-service-type ...).
<rekado_>raghavgururajan: the assembly provides the infrastructure that is required to have this conversation among equals.
<nij>I put "network-manager" in my manifest.scm, and ran `guix package -m manifest.scm`
<nckx>I also add (file-append network-manager "/bin/nmtui") to my setuid-programs so I don't have to sudo every time.
<apteryx>civodul: I think I'm almost done with a service for jami, that'd allow us to host live conferences, but I'm hitting some problem where the service hangs shepherd; any idea? The code is here: https://paste.debian.net/1193852/
<nckx>tissevert: %desktop-services is a superset of %base-services. nij is using %base, not %desktop.
<rekado_>raghavgururajan: I like to see things positively. Showing our faces gives us the opportunity to recognize one another, and to do together what would have been unthinkable alone.
<tissevert>oh, I didn't know about that other one, thank you !
<nckx>nij: Nothing in %base-services provides networking (static-networking doesn't count -- I combine it with NM too). Maybe dhcp-client-service conflicts. I don't have it, I think NM implies it if needed.
<apteryx>The problem comes from the jami-daemon service; running this outside of shepherd it's OK, but for some reason inside shepherd it locks its execution and I must reboot as everything on my system comes to a halt.
<rekado_>raghavgururajan: the assembly mailing list is open to those who endorse the social contract. Outside of that I don’t think I can persuade myself to make time for discussions on GNU and the way things came to be this way :)
<roptat>during the install, it should be /mnt/boot/efi
<roptat>(well, if you mount the root partition for guix at /mnt, which the guided installer does for you)
<mdevos>For $SCHOOL, we have a ‘groupswork’ (too lazy to look up proper English word), and we need to collaborate. $PERSON suggested $PROPIETARY for video/chat and $PROPRIETARY for live editing on a single document. I suggested Jami and <https://framapad.org>. My suggestion was accepted (-:. No complaints so far.
<nckx>I know I could muck about with my browser, but I'm surprised it's not a prominent option.
<roptat>nckx, there is no mention of "monospace" in the documentation
<asdf`>roptat: I have the environment in a terminal in emacs, so it does not prevent me from doing anything in other frames. But thank you for the heads up! I guess it will be a while till it finishes compiling. I'll be back with more question when it fails or - if it happens to work - I'll have a closer look at https://guix.gnu.org/manual/en/html_node/Submitting-Patches.html. Cheers!
<nckx>I'll live, usually by copying the added indentation from German, a similarly expansionist language.
<apteryx>efraim: I'm still trying to understand the example you provided; so there's a thread with a loop running forever; and there's this other clause where it returns its pid. I'm guessing that shepherd might retry its start proc until it gets a non-zero value for the pid?
<efraim>apteryx: with the fork the child is always inside the loop and the parent gets the PID
<nefix>hello! I'm trying to package Zig (ziglang.org), but it's failing at the install phase. It uses cmake-build-system and it seems to try to create a $out/lib directory to copy stuff there. It's returning a permission denied, do you know why is doing that? Should I create the lib directory before? And if so, how could I do this? Thanks!
<roptat>nckx, as a workaround, you can use the browser's console, and set a monospace font (there are two elements you need to set that on)
<rekado_>nefix: it’s that a build system wouldn’t create the target directory, but yes, you can add a build phase that creates the directory first
<nckx>That's what I meant with browser tricks above, but I thought this was supposed to be a more accessible interface.
<PotentialUser-28>I used "guix pack -R emacs". But I cannot run sudo in this emac's shell. I get /usr/bin/sudo must be owned by uid 0. In emacs shell and in dired it is owned by 'nobody'. But outside emacs its owned by root. Can someone point me in the right direction?
<nefix>Another quesion: is there a way to cache phases? I've found myself a lots of times having errors in the check / install phase and having to make a change, waiting for the thing to compile, see that I've missed out something and doing it again, so I end up wasting a lot of time re-compling things that succeed without changing the source / inputs
<leoprikler>PotentialUser-28: perhaps this is a result of packing it into a tarball? I don't think you can setuid root stuff that goes into a tarball.
<distopico>I think we can create a fork of Guix and have OSI Guix aka gnu.tools and GNU Guix
<asdf`>I have compiled and run the test suite on my local copy of guix with modified file-systems.scm. 25 tests were skipped and there are 2 XFAIL, which is actually good if I understand it correctly. Now I'm not sure what I should replace the etc in `./pre-inst-env guix system ETCETERA` with.
<nckx>distopico: You've got it backwards, I think :) GNU Guix is gnu.tools, I don't know what ‘OSI Guix’ would look like... Guix has always skewed heavily towards the Free-not-Open crowd.
<nckx>Not that they're not welcome, but we tend to aim higher than just open source.
<nckx>distopico: You mean GNU? OSI is something else, IMO (so many TLA) not really something worth emulating or improving. Regardless, it already exists. GNU is what we care about, so GNU is what needs to be saved.
<distopico>thinks like gnu.tools that claim about non-inclusion in GNU, I don't see anything different of inclusion there https://gnu.tools/en/people/ only men, no trans, but anyway now the user end needs to understand about FS, Gnu vs Gnu.tools vs OSI and so on
<lfam>Well, the idea is that we want to improve the situation. That's why a new group was formed, to avoid the problems of the old group
<roptat>distopico, which is probably the result of the history of GNU
<nckx>I missed Noisytoot's question: <gnu.tools affiliated with the OSI?> No, not at all. Not sure why ‘OSI’ is being mentioned at all. It's a different group from GNU. But this is off-topic for #guix, I suggest going to #gnuassembly to clear up such misunderstandings.
<mothacehe>I'd like to have all system tests passing before the release
<mothacehe>I asked danny and rekado_ help on the two other failures: nfs-root-fs and ldap
<morgansmith>Did we ever figure something out for triaging bugs? Looks like 46496 is a duplicate of 47325 which I fixed :) (sorta. It'd be nice to merge the nano and non-nano toolchains like everyone else does)
<morgansmith>so I get that you should never hardlink a directory so you can avoid infinite loops, but why would you ever symlink over doing a hardlink for a file? symlinking in ~/.guix-profile I think makes sense because we want it to be transparent that stuff isn't actually there. But when doing stuff in a read only filesystem like /gnu/store, wouldn't hardlinking files always be better then symlinking?
<avalenn>this is how you know for example that a derivation needs an other one, GC in Guix make heavy use of symlinks
<morgansmith>avalenn: I'm not really sure what you mean... In operating systems almost everything is some kind of reference?
<morgansmith>I mean symlink vs hardlink just moves the reference from the kernel level down to the filesystem level
<avalenn>when you do hardlink both files are strictly equivalent you can delete one without impact on the other
<avalenn>with symlink you have the main file and the symlink is only a pointer to the other
<morgansmith>avalenn: aren't dependencies bad? Isn't that an argument for how hardlinks would be better?
<avalenn>in Guix you want the dependencies to be explicit
<avalenn>and the unit of managing the dependencies is not the file, it is a group of files called derivation
<efraim>looks like the powerpc64le folks forgot to build mesa :p
<avalenn>if you replace symlinks by hardlinks you could inadvertently delete a whole derivation without knowing it is used by an other
<cbaines>the hardlinks work at the level of individual files within the store
<cbaines>avalenn, I think you're using "derivation" in place of what I'd call a "derivation output" or "store item", I'm not sure what the cannonical term is
<avalenn>cbaines you're right I was wondering about the right term too
<morgansmith>How would replacing symlinks with hardlinks cause the deletion of a derivation output? I get that there are build time dependencies and runtime dependencies, but I don't think you need to rely on symlinks to ensure that your runtime dependencies still exist.
<avalenn>I don't know how to explain it on a simple manner.
<morgansmith>efraim: Why did you change the header link to symlink when you did the nanolib patch? I'm very confused about hardlinks vs symlinks right now :P
<cbaines>on the question of symlinking files in /gnu/store, symlinks are quite different to just having a file there or using hardlinks, so that could and would break things that read files in /gnu/store
<efraim>stylistic reasons? I don't think we use hard links in any of the packages
<cbaines>that's not to say you can't have symlinks in /gnu/store, just that you wouldn't use them in place of hard links for general deduplication
<morgansmith>efraim: Well the static libraries in that patch are still hardlinked :P
<efraim>looks like I didn't touch the other link in the commit and didn't change the commit message
<efraim>git-grep says there are a couple of links but a lot more symlinks
<morgansmith>wait, does the deduplication step actually convert symlinks to hardlinks? The manual makes it sound like it's just identical files that get hardlinked
<morgansmith>oh I see. roptat thought that might be what happens and then cbaines said no that would be very bad
<avalenn>symlinks are just files whose content is the name of an other file, they are small they don't need to be deduplicated
<morgansmith>Is it very bad because some applications will be expecting a symlink and fail if they find a file? In my experience usually applications usually are expecting files, not symlinks
<avalenn>kernel resolves symlinks so most application don't see the difference
<morgansmith>I'm not saying hardlinks would be amazing and change everything. I'm sure the benefit to using them would be very small. But I'm still trying to figure out why you wouldn't just hardlink everything to get that small benifit
<asdf`>I have no idea how to continue and test my modifications to add better exfat support. If anyone wants to have a look, I uploaded a diff: https://paste.centos.org/view/49dd0c34. I've got to go. Thanks for the help so far. I'll probably check in again in the next days. Cheers!
<morgansmith>efraim: Could you close bug 46496? It's a duplicate of the nanolib one. I'm not sure if debbugs would let me do it but also I would think only comitters should close bugs.
<lfam>On other platforms, users can open and close bugs too
<morgansmith>I guess that makes sense. But I should probably close it in a way that emails the subscribed people about the fix. Is there a specific format of message I should send that's outline in the gnu standards or something?
<morgansmith>Like I know it'll email the people that the bug is closed, but I want to add an informative message
<bdju>I've changed my keyboard layout in my config.scm and I want to make sure it really worked before my next reboot or else I may have trouble logging in at the TTY. what can I do to make the new layout take effect in a TTY without rebooting? I tried `sudo herd restart term-tty2` and then switching to tty2 and the layout is still wrong.
<morgansmith>when doing a reconfigure it adds a new option to the grub boot. so worst comes to worst, you can pick the second last grub boot option and get back to a known safe state
<bdju>it's more than just inconvenience. I had software-level dvorak and now my keyboard itself is in workman layout, so it essentially types gibberish. I don't have an easy way to make my keyboard qwerty again so that the dvorak at least types normally. I'd have to get an actual different keyboard
<bdju>I changed my actual keyboard since last reboot and there is no safe generation anymore, I haven't quit my sway session since changing layouts and keyboards some months ago
<morgansmith>"Since turning it off and on again does not seem to be a valid solution, we are transferring you to a level 2 technician. Please hold. Your call is important to us."
<bdju>not sure how to set up tty autologin, and also I'd be a little nervous to have something like that set up. unless it launched sway and then locked the screen so I still needed my password or something. hmm
<bdju>I'm not in a situation where someone using my machine physically is a big concern, but I still hesitate to make things less secure
<morgansmith>bdju: Ya security is an interesting problem. I've got disk encryption so I just rely on the disk password instead of an account password
<bdju>I almost set up FDE on this install but I had never used it before and was nervous about losing access to my data. a while after I ended up setting up FDE on my pinephone and am a bit more comfortable with it now. I don't think I can add it without doing a reinstall at this point, though.
<morgansmith>Maybe sway has some config file that you can use to launch a screen locker? It'd be annoying when you manually start sway from a tty but ideal in an autologin scenario. Maybe you could make it only launch a screen locker if you're on your autologin tty
<nij>While there are guix commandlines, can I invoke them in the repl?
<nij>In particular, I wish to `guix install` a package in the repl.. so I can test if the package is well-formed while developing.
<bdju>morgansmith: thank you for the link! I also just mashed keys to figure out what I have to hit for my user and password in case it is screwed up after a reboot. wrote myself a little translation. so now I should be okay even in the worst-case
<morgansmith>bdju: I wish you luck. This is my autologin service btw (username is a variable for me. please use your own username). The first 6 ttys already have services so I put one on the 7th. I think usually most GUIs are on the 7th anyways so it all works out. (service mingetty-service-type (mingetty-configuration (tty "tty7") (auto-login username)))
<morgansmith>lfam: Thanks. I will do this. The gnu-standards just says to thank them and gives no guidance beyond that so I'll do that too.
<lfam>I think you should feel free to do it as you see fit :)
<mdevos>Are there other translators for Dutch currently on #guix?
<roptat>you'd need to find the right procedure of course
<morgansmith>I have installed font-gnu-freefont in both my system profile and my user profile. I've run fc-cache -rv. I've restarted my applications. I still cannot view a unicode penguin. I am very sad
<apteryx>are the standard output & error streams in a Shepherd service (start/stop procedures) supposed to end in /var/log/messages? They don't seem to.
<morgansmith>mdevos: I think if we changed herd start/stop/restart then there would be riots in the streets. Also you'd have to consider how clear that terminology is in different cultures and different languages. I'd bet that it's worse but I don't know.
<nckx>mdevos: ‘logische partitie’ seems to be the accepted term.
<mdevos>Technically flemish, but with Dutch-speaking Dutch parent and a Walloon parent with a French parent
<mdevos>Ik verwijder de puntjes na ‘Logical partition creation error.’
<nckx>mdevos: I only now see your <nckx, do you know how to translate "root file system"?> question. Yes! Feel free to add things to the glossary. The fewer English loan words (within reason) the better IMO.
<mdevos>-> ‘Fout bij het aanmaken van een logische partitie’
<nckx>Sounds as good as translated computer Dutch can sound IMO.
<mdevos>Ik ken alle roepwoorden van mijn computer! Ik ben heer en meester over mijn computer! Mwuhahaha
<nckx>Not sure I want my computer to know what I shout at it most.
<nij>Hello! My guix system does not play any sound.. even though in pulsemixer it shows it ain't muted. I have (service pulseaudio-service-type) in config.scm (which is run reconfigured on).. what could be going on?
<nckx>Noisytoot: I forgot to answer when you posted it half an hour ago but my telepathic answer remains the same: I'll merge it in two weeks (those two words occur in that order in the manual so it must be right), but really hope someone who actually uses Node does so before.
<Noisytoot>nckx, Is it 2 weeks from now, or 2 weeks from when I posted it to guix-patches?
<nckx>nij: It's a total guess, but does /etc/asound.conf exist on your system?
<nckx>From posting, so 9 days, but don't shoot me if it's more.
<nckx>I've a similar (but different-sounding) problem when I disconnect my Bluetooth headphones: the Pulse audio sink actually *blocks*, so anything that tries to play sound just waits. Video players, browsers, ... freeze on the first frame. When I reconnect the 'phones they start playing again.
<jeko>I am trying to create a Guix System definition with an Emacs init.el file (inside a .emacs.d directory) ready to use so I tried to set an extra-special-file but the resulting file inside the store is write protected so Emacs can't configure itself
<philipmcgrath[m]>When refactoring some packages into a new file: (1) Should you copy the whole header from the old file, or start fresh? (2) Does the old file need to reexport the packages or something for compatability?
<lfam>philipmcgrath[m]: You'll need to move the relevant copyright lines to the new file
<lfam>philipmcgrath[m]: It's annoying, but you can use `git log` and `git blame` to see who owns copyright on which parts of the file, and then re-do the headers appropriately. It's a good reason to not do this kind of refactoring work, IMO :)
<cj>Yes, I understand that libraries are more up-to-date, but I was wondering if it allows using old and vulnerable libraries. Sorry I am unable to follow the discussion normally, it is because I am using a translator.