<dp0>Quick question for anyone that's around, how exactly are package updates handled when it depends on an updated version of some other package? Do you have to update both packages?
<dp0>Example Scenario: Say there's project A@1.0v and it depends on project B@1.0v. If there's a new version of A@2.0v and it now requires B@2.0v, is it expected that along with the update in the package to A@2.0v that B is also updated to 2.0v?
<apteryx>dp0: yes, if updating B to 2.0v doesn't break any of its dependents
<dp0>ok. thanks. I guess that makes sense. Just wasn't 100% sure since I didn't find an example of that in the documentation.
<apteryx>it if does, and if it not reasonable to have all of them updated to work with B@2.0v, then the B package can have both version 1.0v and 2.0v in Guix, and packages depending on B@1.0v can continue using it
<dp0>Bonus question, what if things are optionally dependent?
<dp0>It's compilation flags let you use your own installed version of a library or it'll come prepackaged with one.
<dp0>I'm assuming it's more preferable to have the dependencies separate so that guix can manage both individually?
<dp0>Maybe prepackaged isn't the right term, more like statically compiled with it's own version... I guess
<bdju>iyzsong: got around to that reboot and I'm in the input group now, controller still acting the same, unfortunately...
<bdju>iyzsong: I tried my wii u gamecube controller adapter and dolphin-emu said "Error Opening Adapter: Access denied (insufficient permissions)", so it probably is a permissions issue in both cases. Just not sure what to do to fix it.
<bricewge>bdju: Does your adaptator device have the corect right with your udev rule now?
<bdju> bdju: it still doesn't work, but I think I'm gonna give up on that controller for now. a dualshock 4 seems to work fine. switch pro controller still doesn't work. not sure if that also needs udev stuff. there's apparently a hid-nintendo kernel driver but it might not be merged yet
<raghavgururajan>Soheil[m]: I am afraid I can't help you there. Regarding kernel, I had some networking issues with latest versions, so started using `(kernel linux-libre-lts)` under operating-system declaration of config.scm.
<jab>raghavgururajan: anytime! I'm glad to be able to help. Any suggestions about where you want me to put your libreboot in the guix manual?
<jab>Should I put it in the System installation chapter?
<wirez>do you think gnu libre-linux guix are viable (have enough dev resources) because the licensing philosophy?
<lispmacs>yes, it is. I release like 99% of my code under GPL-3.0-or-later
<lispmacs>it doesn't really matter. supporting free software and copyleft is the right thing to do, viable or not
<lispmacs>but, all my computer system (two desktops and a server) are running linux-libre
<wirez>ya but i mean do you think a lot of ppl choose to work on copyleft libre linux because of the license? and not necessarily the code being really documented or smth else
<lispmacs>well, nobody really develops libre-linux, as you normally think of that. It is just a project that cleans out the proprietary garbage from what is, by its own license, supposed to be a 100% free-software, copyleft kernel project
<wirez>and basically copyleft philosophy is free to look at and use source however you want (like mit) but if you make changes you have to share them?
<lispmacs>a more accurate way to put it: why you share copylefted software, you MUST give all the software freedoms to those with whom you are sharing the software
<lispmacs>one of the freedoms is to be able to inspect the source code, so you must give them the source code
<lispmacs>others are to be able to modify the code and to share it with others, so your copyleft license gives them those privileges as well
<wirez>ok so proprietary is fine, but if you distribute (like sell) you gotta do so with the copyleft requirement in tact
<wirez>so it guarantees that if there's virility in licenses for software sharing and distribution which there is, it makes sure copyleft terms are what's viral and not non-copyleft
<wirez>which doesn't help mit kinda license ppl which already lets you do whatever you want, but it does protect against less permissive licensing
<lispmacs>if you distribute GPL code (for free or for money) you must hand off all the freedoms to the next guy
<wirez>and distributing gpl code is even if it's a tiny piece of your own large code?
<wirez>so mit kinda licenses hand off all freedoms, but then copyleft licenses hand off all freedoms EXCEPT that you must pass on same set of freedoms
<lispmacs>with MIT you are giving the freedoms to the next guy as well, but the next guy is under no obligation to hand off the freedoms to the next guy after him
<wirez>so it's restrictive in 1 way but only to set a minimum set of freedom
<lispmacs>GPLv3 specifically also protects against some other tricks, like "TiVoization", where manufacturer uses free software code on your device, but locks down the hardware so you can't make any changes
<leoprikler>I think that's to be evaluated on a case-by-case basis
<leoprikler>if you're piping the output of `guix import' into a file, an arbitrary line count won't matter
<tonos>I wrote around 50 lines, but most of them are just the package fields, so I guess its trivial. I'll submit the patches without the copyright line.
<Rooks>I don't think I quite understand how to add a service managed by the herd command, I am attempting to execute things like cpupower and thinkfan on boot?
<iyzsong>Rooks: to add a shepherd service, you need a 'service-type' that extend 'shepherd-root-service-type', 'sysctl-service-type' is an example for 'one-shot' shepherd service.
<dstolfa>Rooks: shepherd is configured in guile, it doesn't actually have any syntax file it parses. instead, it implements an EDSL (which in this case is just a set of record types and functions) that you can use to configure your services. in guix, it is standard to do what iyzsong said
<jorge[m]123>Hola,tengo errores al ejecutar guix pull y en la instalación de cualquier paquete.
<apapsch>guix never finishes building a docker image from gnu/system/examples/docker-image.tmpl
<apapsch>there is a qemu process constantly consuming cpu time
<apapsch>this happens in two guix binary environments, a gitlab shell runner (ubuntu) and current master locally (arch linux)
<apapsch>is this a known issue? how can I debug it?
<clemens3>mekeor[m]: some feedback, i did choose openbox and no other DE, when i was in x, no xterm.. did install again with xfce only, then got a terminal..
<apapsch>guix system docker-container --debug 9999 leads to another error: "guix system: error: | | | bind mounting `/dev/full' to `/gnu/store/m6b5pvx50zwrnqbdswl89kr93p6zasxr-guix-docker-image.tar.gz.drv.chroot/dev/full"
<ggoes>how would i go about installing a package with a different input, *and* have that input pull from the master branch? e.g. i've tried doing guix package -i emacs-exwm --with-input=emacs=emacs-next --with-branch=emacs-next=master (and the equivalent in scheme) with no luck
<ggoes>i'm not above defining a new emacs-exwm package for myself, but it seems like that shouldn't be necessary
<efraim>you might also need --with-input=emacs-minimal=emacs-next
<ggoes>oh good call, i didn't think to change emacs-minimal as well. hmm.
<maxwell_TGAP>is it possible to copy the package deffinition for python3.8 from core-updates and add it to my packages path
<sneek>civodul, oriansj says: that live-bootstrap have guile and gcc 4.7.4 (both C and C++ backends) all properly bootstrapped (no pregenerated files unlike the current root) and it might make for a stunning release.
<apteryx>maximed: I too think "it should just work". Good point about the graphics stack. Last time I was blocked by not having root (you can't just run a guix pack from /sdcard as that's (ex)FAT, with all its limitation, e.g. no exec bit nor symlinks support). I'm trying to get passed that now.
<maximed>civodul: I removed the casts (i.e., reset the code to the original version) and compiled with "-O2 -fexcess-precision=standard" and the tests pass
<leoprikler>bricewge: don't worry, you're not alone in sending small patches
<leoprikler>people without commit access have to send two-liners just to bump their favourite package :)
<civodul>sneek: later tell maximed re -fexcess-precision=standard, well done! \o/