IRC channel logs


back to list of logs

<Minall>lsmod | grep ath9k doesn't output anything, since the module isn't loaded
<vagrantc>"sudo lsmod ath9k" neither needs sudo, and is a syntax error for lsmod on top of it
<Minall>In the h-node page it says that my wifi device uses that module to work, and it is not loaded by any reason, so since it's not loaded, and my device isn't working, if I load the module it should work
<Minall>modinfo does give me output of the module, it just doesn't load
<vagrantc>usually you shouldn't need to load modules manually
<vagrantc>not for hardware
<quiliro>ok, is 'sudo modprobe ath9k'
<vagrantc>quiliro: no, that's not.
<quiliro>vagrantc: is just a test
<Minall>Yep, I shoudn't... The installation image was the same, it didn't detect wifi either
<Minall>So perhaps the installation by any reason sayed: 'oh, this is a pc, so we don't need that module since is just for wireless for example, on a laptop'
<quiliro>Minall: as I said in the morning, probably your hardware has killed you wifi temporarily
<Minall>And, maybe 'blacklisted' the module? since I can't load it with modprobe either (I need sudo to use this command btw)
<Minall>modprobe: ERROR: could not insert 'ath9k': Exec format error
<Minall>That's the output of modprobe, and the module does exist, since modinfo works
<Minall>quiliro: perhaps, or maybe the USB was not well-writed
<Minall>vagrantc: very unlikely, yep
<vagrantc>this is usb ath9th-htc?
<vagrantc>er, ath9k-htc ?
<Minall>Nope, I tried to install that package too, but not luck. It's integrated on the laptop
<quiliro>usb wireless?
<quiliro>i think it is an internal wifi
<Minall>that package uses the module that I'm trying to load, since the module is included directly on the kernel, it isn't necessary to install anything like a package to have the module
<Minall>It is an internal, so that package doesn't work
<vagrantc>and it's listed with lspci?
<Minall>The thing is, why is modprobe not working... perhaps its blacklisted? something is blocking it from loading
<quiliro>as you confirmed in the morning
<Minall>vagrantc: Yes, lspci detects the device and its vendor well
<quiliro>and it uses ath9k as is written in that web pagk
<Minall>quiliro: Yes, it works perfectly, but using that module of course, and by any reason, it isn't loaded
<quiliro>Minall: did you test trisquel as i suggested in the morning?
<quiliro>the the card work on another system?
<lprndn>Minall: Concerning ssdm, it's a weird service. sddm-service-type doesn't have a default config so you should add (sddm-service) instead. Or (sddm-service-type (sddm-configuration)). Does it helps?
<Minall>In other systems, to load modules at boot one has to add it to /usr/..., since guix doesn't have /usr for obvious reasons, where can I see if a module is blacklisted on guix?
<Minall>lprndn: I'll add it and see if it works
<vagrantc>what do you mean add to /usr/ ?
<Minall>I mean, there's a file in every debian based system which you can add modules, i think is located somewhere on /usr/share/modules/modules.d?
<Minall>But the point is, is there a file like that on guix?
<Minall>quiliro: I'm downloading trisquel right now!
<vagrantc>Minall: /etc/modprobe.d woudl be the one for local system configuration
<vagrantc>not sure if guix uses that
<Minall>sddm-service not assigned variable, id you forget to use the 'use-modules' form?
<quiliro>you can blacklist modules on initrd
<quiliro>Section 8.12 Initial RAM Disk
<vagrantc>but you would have to go out of your way to blacklist one of the recommended wifi devices
<Minall>Doesn't seem like it
<Minall>vagrantc: What do you mean?
<Minall>quiliro: I'll check that part
<vagrantc>Minall: it is one of the recommended devices to get in the manual, i would be surprised if it were blacklisted, unless you explicitly blacklisted it
<Minall>What if I add to my reconfigure, initrd-modules ath9k or to firmware?
<vagrantc>and i would think you'd know if you explicitly blacklisted it
<Minall>vagrantc: i didn't, this is a new installation, it may be a bug
<Minall>Yep lol
<quiliro>Minall: you first have to check why it does not should load by default
<Minall>I'll check the linux-libre files to see if I can see the modules
<Minall>quiliro: yep, sadly
<lprndn>Minall: You need to add "sddm" (non quoted) to the use-service-modules part of your configuration. FYI, slim is part of /gnu/services/desktop.scm but sddm is located in its own file.
<quiliro>i am inclinated to to think that you have a hardware killswitch for the wifi
<Minall>lprndn: That's probably the thing
<Minall>let me check it
<Minall>quiliro: Me too, lol, but there isn't any button on the keyboard, AND rfkill doesn't show the device as hard-blocked, which is when your wifi is blocked by a buttom of some sort
<Minall>So it has to be the module (please)
<quiliro>Hard blocked: no and Soft blocked: no ?
<quiliro>Minall: ^
<Minall>nope, there's no output using rfkill
<Minall>Since rfkill only works with wifi devices, and there 'isn't' on
<Minall>In order to rfkill to have an output, ip link should work too
<quiliro>Minall: when you run: ifconfig -a
<quiliro>you see the device?
<Minall>That command should be similar to ip link, so is the same lol
<quiliro>and! iwconfig
<Minall>We need to find a way to load the module
***atw```` is now known as atw
<Minall>list ethernet nd lo, 'no wireless extensions'
<quiliro>Minall: would you please check your log?
<Minall>which one?
<quiliro>just run sudo dmesg on eshell
<quiliro>then you can search the results
<lprndn>Minall: Just in case, do you have a firmware part in your configuration?
<Minall>quiliro: ok!
<Minall>lprndn:No, I don't is a new installation, with all the defaults, well I'm trying to not use gdm now. BTW, where did you learned that sddm had to be added on use-modules?
<Minall>I'll give you guys the dmesh once I end installing wgetpaste
<quiliro>Minall: just to be sure: lspci -v -s 02:00.0 | grep Kernel
<Minall>lprndn: that is my config, I still have the same error lol
<Minall>quiliro: Kernel modules: ath9k
<Minall>this output
<gnutec>Try install icecat on guix but the system stop and I just give up. Too big download of packages, no audio, no make. Then I back to Trisquel, but now, with Btrfs clean install. Internet 4G is expencive here in Brazil. How work?
<quiliro>Minall: (modules (list xf86-video-intel))
<quiliro>Minall: was necessary?
<Minall>quiliro: Welp, my pc uses intel, so that's the driver
<Minall>lprndn: I didn't had to add (sddm-service config), just sddm-service... what you sayed worked, thanks!
<quiliro>maybe that avoids other modules from loading...not experienced yet to just add
<Minall>where did you learned that lprndn ?
<quiliro>Minall: would you please try without (modules (list xf86-video-intel)) ?
<Minall>Mhh, unlikely, since I'm trying to load it in my next reconfigure, but I'm right now on a totally base new installation from the USB, so I don't have xf86-video-intel YET installed
<quiliro>maybe it es not even necessary
<Minall>Perhaps, but how should I see that?
<quiliro>see what?
<Minall>That I don't need the driver
<quiliro>mejor en español
<quiliro>no lo necesitas a menos que no lo cargue
<Minall>quiliro: vagrantc Tambien no esta ayudando, pero en ingles, seguro que en español es mejor?
<lprndn>Minall: ok. Hum... The first time, I think from the error message but I already got the 'use-module' error output before so I knew what it was about. Can you try just (sddm-service)?
<Minall>quiliro: Estariamos hablando de dos cosas diferentes, porque el modulo o el driver digamos ath9k ya esta en el kernel, y si es necesario lo carga, pero no lo carga por alguna razon
<Minall>Pero un driver de video si se tiene que instalar por lo general desde el paquete, como con openchrome, para que este el modulo en el sistema, y xorg pueda iniciar por ese modulo
<Minall>Creo que la unica manera de comprobar eso es, si el log de xorg no cambia al instalar el paquete, que eso vere cuando termine de reconfigurar
<Minall>lprndn: Yes, i tried with just (sddm-service) and it worked like a charm!, I'm reconfiguring right now!
<quiliro>Minall: i think that if you want to add you must use another syntax...if you write like that, i think it will replace default loading
<Minall>lprndn: Where did you learned that I had to add sddm to use-modules?
<quiliro>but not sure
<Minall>quiliro: Maybe you're right, since we're inserting a configuration in xorg, not just installing a package as I say
<quiliro>no es necesario instalar el módulo de vídeo, se detecta
<Minall>quiliro: It's to compare how it goes
<quiliro>just try without the module...don't fix something that is not bad
<Minall>quiliro: En ese caso se hubiera detectado el driver intel o el openchrome en las computadoras que he instalado guix, pero no ha sido asi...
<Minall>quiliro: Mhh, I'll try, I'm reconfiguring right now,
<quiliro>now it detects the intel driver?
<gnutec>The problem is guix need guile-2.2. But in Trisquel has only guile-2.0. But the idea is really good. If I have a good internet, I try to install audio on guix system.
<Minall>quiliro: What do you mean?
<quiliro>if it does detect it now and it did not without that module addition, then it is worth it to add it
<Minall>gnutec: which problems did you had with audio on guix?
<quiliro>if if is the same, it is not useful
<Minall>quiliro: I see where you're heading... how should I see if the driver is needed?
<quiliro>lspci -v
<quiliro>lspci -v -s vw:xy.z
<quiliro>but leave that for later
<quiliro>better to see why wifi does not work
<Minall>-s invalid bus numberç
<lprndn>Minall: In the error output. It seems vague when you're not used to it but it's really what's it's telling you ;) Also, looking at the repository, you can see sddm has its own file.
<Minall>ok ! lol
<quiliro>if you change severla things at a time, you will not know whic one had what effect
<Minall>lprndn: What do you mean, looking at the repository? so its separated? like a normal package? is that what you mean?
<Minall>quiliro: one by one ! lol
<Minall>you're right
<quiliro>Minall: concentrate....ommmmmmmm
<lprndn>Minall: Yeah. If you look at guix's sources you'll see that all services are defined in /gnu/services just like packages are defined in /gnu/packages.
<Minall>lprndn: Amazing!!
<Minall>quiliro: I'll finish reconfiguring and i'll install trisquel, the download is done
<quiliro>Minall: you can use emacs-guix
<quiliro>Minall: you do not need to install trisquel
<Minall>quiliro: Oh, install it nope, i mean use it
<quiliro>just run it live and check if the wifi works
<quiliro>emacs-guix can show you the source
<Minall>I know it will work, because *suspense*
<Minall>First' I had an guix installation usb that the instalation DID detect the wifi, but didn't work, it gave me some errors
<Minall>Then I sayd: oh, those errors should be because the USB is faulty, I'll rewrite the image, because I need the wifi
<quiliro>perhaps the wifi is defective
<Minall>Then, i rewrited, and the next guix USB installation didn't even detect the wifi, but I had a cable nearby and I installed with ethernet
<Minall>quiliro: unlikely, I used the wifi in the system I had before nicely
<quiliro>Minall: on emacs you can use guix-edit
<quiliro>M-x guix-edit
<Minall>So, Right now I'm making another guix installation USB, what if it does detect the wifi?
<Minall>What should that mean?
<Minall>Yes! I totally can, but for what?
<quiliro>to see the source
<Minall>quiliro: of what?
<quiliro>of ssdm
<Minall>I losed you there sorry, what do you want me to check?
<quiliro>but that is another topic
<quiliro>anyway, if the wifi works with the new usb, it could be that the module was not well read or that the wifi device has something causing it not to if it works and before it did not with the same version of guix, it is probably hardware
<Minall>Here's what I think:
<Minall>If the wifi works with the new USB:
<quiliro>but not necessarily. since you fiddle a lot with the system....
<Minall>the installation that I used was faulty, and sayed: Oh, this is a pc, it doesn't need that module, let's blacklist it or something, but the new installation will detect the wifi and don't blacklist the module
<Minall>In case I'm right, then just by adding the module correctly should be enough... but modprobe doesn't seem to work
<quiliro>Minall: the only reason to load that module manually is a bug in guix
<Minall>quiliro: 64 bytes from icmp_seq=1 ttl=51 time=97,527 ms
<quiliro>Minall: so. you tryed without modules?
<Minall>Still reconfiguring lol
<quiliro>or you tryed with trisquel live?
<Minall>I'm creating the guix installation,
<quiliro>creating with or without modules on the config.scm?
<quiliro>Minall: did you comment?: (modules (list xf86-video-intel))
<Minall>As you sayed
<Minall>Oh sorry
<quiliro>it is ok, just want to holp
<Minall>fase 'build' right now!
<quiliro>sneek_: botsnack
<quiliro>sneek_: apropos cons
<sneek_>(guile): const #<procedure const (value)>
<sneek_>(guile): module-constructor #<procedure 25e0e0 at ice-9/boot-9.scm:2004:2 (obarray uses binder eval-closure transformer name kind duplicates-handlers import-obarray observers weak-observers version submodules submodule-binder public-interface filename)>
<sneek_>(guile): cons* #<procedure cons* (_ . _)>
<sneek_>(guile): cons-source #<procedure cons-source (_ _ _)>
<sneek_>(guile): acons #<procedure acons (_ _ _)>
<sneek_>(guile): record-constructor #<procedure record-constructor (rtd #:optional field-names)>
<sneek_>(guile): cons #<procedure cons (_ _)>
<quiliro>will do privately
<Minall>quiliro: I learned to use tags on org mode
<Minall>But I'm loss about the agenda
<quiliro>how to add flyspell correction on spanish for emacs on guix?
<quiliro>i get this error every time i start emacs:
<quiliro>(Searching for program No existe el fichero o el directorio ispell)
<quiliro>the file or directory ispell does not exist
<apteryx>hello Guix!
<quiliro>hello apteryx
<apteryx>shouldn't the derivation of operating-system produce all necessary components?
<quiliro>you nick reminds me of a comics character
<quiliro>apteryx: what components
<apteryx>If you look up `operating-system-derivation' in (gnu system), you'll see that it strictly deals with services.
<apteryx>The bootloader derivation is left to the responsibility of some other code.
<apteryx>I'm not sure if that's neat; in my opinion it'd be neater to have the derivation of operating-system be self-contained.
<apteryx>if that's necessary*
<apteryx>that other code is `operating-system-bootcfg' in (gnu system)
<apteryx>the generator for grub config is `grub-configuration-file' in (gnu bootloader grub)
<apteryx>it produces grub.cfg
<quiliro>sneek_: later tell minall Install emacs-bongo package for playing media (video, audio) from inside Emacs.
<sneek_>Will do.
<Minall>Hello guix!
<sneek_>Welcome back Minall, you have 1 message.
<sneek_>Minall, quiliro says: Install emacs-bongo package for playing media (video, audio) from inside Emacs.
<Minall>quiliro: Kiel vi fartas
<quiliro>Minall: ĉu wifi-o funcias?
<Minall>1 minut of suspense
<apteryx>Q: if you could use Guix to partition your system HD, would you rather 1) explicitly define the partitions using a 'partitions' field on the operating-system record, or 2) have Guix infer the partitions based on the file-systems defined?
<Minall>Now it works
<Minall>Now, why?
<quiliro>apteryx: both...sometimes i just want it to decide automatically, sometimes i want to define partitions
<Minall>Now the wifi is detected
<Minall>I'm going to connect to wifi!!!
<quiliro>Minall: probably hardware: usb device or usb port or wifi device or bad guix system image
<Minall>bad guix system image?
<quiliro>Minall: much do you know about arch compared to how much you know about guix?
<Minall>arch - 30% guix - 15%
<Minall>I have a lot to learn
<quiliro>bad guix system image = bad recording
<quiliro>Minall: time for arch - time for guix?
<quiliro>in months
<apteryx>quiliro: thanks for the input. I guess I can start with a 'partitions' field that would defaults to #f and do nothing in this case (the existing operating system configs would continue to behave the same as they do now). It'd also need some special command line flag with big warnings to be "activated"
<Minall>4 months on arch
<Minall>2 month on guix?
<quiliro>same rate of learning then!
<quiliro>i learn more in guix since we learn together!
<apteryx>like... --recreate-partitions=yes --> WARNING: this will cause all data on drive X to be lost. Type 'yes' to continue.
<quiliro>apteryx: nice
<Minall>quiliro: That's good to hear, but we still compare to nothing!! we have a long way to go
<quiliro>making packages has still to be learned
<Minall>A lot of things!
<quiliro>i think you know more of guix than of arch
<quiliro>do you know how to make an arch package?
<Minall>quiliro: No clue!
<Minall>Maybe youre right jaja
<quiliro>so least you know the same
<Minall>Atleast on guix I can use a good programming language
<quiliro>but i think you know more of guix than what you know of arch
<quiliro>you can use guile on arch too!
<Minall>quiliro: But not so awesomely as on guix
<quiliro>heck! you can use guix on ach too
<Minall>Welp, but why
<quiliro>Minall: that is true
<Minall>The only reason would be to use the VM like style of guix
<Minall>To make environments
<quiliro>maybe your users use arch and you want them to use your programs
<quiliro>so you install guix on arch
<quiliro>or use guix pack
<Marlin[m]>hi guix, i'm kinda confused on how to get irony-mode working on guix. I got the emacs-irony-mode and the server package, but i can't seem to understand what to do next
<quiliro>Marlin[m]: ^
<Marlin[m]>i mean the guix packages
<Marlin[m]>it complains about missing dependencies when i try to do irony-server-install
<Marlin[m]>isn't the irony-server package supposed to have everything it needs?
<ryanprior>Ah it's possible you might be able to launch the server without having to do irony-install-server, maybe there's package specific docs on that?
<ryanprior>I think irony-install-server compiles the server if it isn't already compiled, which requires that you have all the deps. But the package might propagage all those deps, it might just give you the compiled server.
<ryanprior>I haven't used irony-mode with guix yet, but that's what comes to my mind as to what might be happening?
<Marlin[m]>if i try to type stuff in irony mode, it says there's a version mismatch and asks me to compile it again
<quiliro>how can i use apertium on guix?
<quiliro>i cannot install the languages
<PotentialUser-60>hi all
<Guilherme>I am a new user from NixOS
<Gamayun>Hi Guilherme :-)
<rekado>Marlin[m]: please send email to with the details. It’s easier for people to figure out what might be wrong.
<roptat>hi guix!
<simple_>im interessted in trying guix (currently using arch). im considering just installing the package manager and play with that or using the distro with chroot. is there a clear advantage to one of those two?
<efraim>Installing the package manager is really easy and self contained if you want to get rid of it later
<efraim>In my opinion it's the easier way to get a feel for using guix
<roptat>simple_, I agree, using the distro in a chroot is going to be very difficult, I'm not even sure it's possible
<mbakke>simple_: Once you have the package manager installed, you can experiment with Guix System using `guix system vm`.
<simple_>great, thanks! will do that
<mbakke>roptat: do you know the current status of Java on core-updates?
<roptat>I haven't tested core-updates yet
<roptat>I think rekado and g_bor[m] fixed the bootstrap
<rekado>roptat: we haven’t actually pushed anything though.
<rekado>“fixed” is a big word…
<rekado>I found that removing a call to “free” removes a crash of the bootstrap JVM.
<rekado>it’s very ugly to do that and we should agree on whether we are okay with that sort of thing.
<pkill9>grafts confuse me, if i run `guix build love` it returns the store path without building anything, but if i run `guix build --with-graft=mesa=mesa love`, it starts downloading a mix of substitutes and sources
<rekado>my opinion as an amateur and fatalist is: this is just the bootstrap JVM, so it’s fine to have it go up in smoke as long as it gets us to the next stage.
<rekado>pkill9: grafts are very simple. “with-graft” is not.
<pkill9>oh ok
<rekado>(well, to me anyway)
<pkill9>what's the difference?
<rekado>pkill9: I suppose you already know what grafts are?
<rekado>if not here’s my take on them;
<rekado>take any store item
<rekado>the files in that prefix directory may contain references to /gnu/store/…
<rekado>grafting goes through each of the files, copies them, and replaces these references with new references.
<rekado>so you end up with an almost identical store item that has a different hash and contains new references.
<rekado>in most cases doing this is much faster than rebuilding the package
<rekado>we do this because we may need to swap out a broken build that’s close to the bottom of the pile
<rekado>in functional package management anything after package P will have to be rebuilt when P changes.
<rekado>say we have a dependency chain like this: P -> Q -> R -> S -> T
<rekado>P is vulnerable, so we fix it and obtain P*
<rekado>without grafts we would have to build a new Q with P* as an input
<rekado>then we would have to build a new R with that new Q as an input
<rekado>and so on and on … until we hit T.
<rekado>this will take a lot of time and energy
<rekado>instead we assume that P and P* are interchangeable
<rekado>they have the same ABI
<rekado>so it should be fine just to take the old build of Q and simply let it refer to P* instead of P.
<rekado>this ensures that Q is not affected by the vulnerability in P.
<rekado>so we graft P* onto Q to get Q*, without having to actually build anything.
<pkill9>ok, i understand this part
<pkill9>but why does --with-graft try to rebuild everything
<rekado>building Q might be really expensive, but getting to Q* is just a matter of copying, scanning references, and replacing them.
<rekado>with-graft is used to replace arbitrary inputs via the grafting mechanism.
<rekado>it will have to at least build the replacement
<rekado>I don’t know what you expect --with-graft=mesa=mesa to do
<rekado>you would normally do something like “--with-graft=mesa=my-modified-mesa”
<pkill9>i thought it would just conclude that there's nothing to change and return the normal store hash
<mbakke>Did Go ever work on i686?
<rekado>that would cause my-modified-mesa to be built (if it doesn’t exist yet) and then build grafted packages for every other package in the bag that needs mesa.
<rekado>pkill9: I don’t think it tries to be smart at all.
<rekado>pkill9: the request to replace a thing with itself is not a common use-case, so I don’t think we’re trying to optimize that case.
<pkill9>ok, when you say it would have to at least build the replacement, you mean the new grafted input? Why does guix try to build a bunch of other stuff in the package graph when i run `guix build --with-graft=mesa=mesa love`? (im just replacing mesa with itself as an example, or maybe that's causing it to bork?)
<rekado>pkill9: could you pass --dry-run and show us what it plans to build?
<rekado>yeah, that doesn’t look right.
<rekado>I can see why it would (mistakenly) download dependencies, but it shouldn’t get sources in this case.
<efraim>Maybe mesa is different? I wouldn't think so though
<rekado>pkill9: could you please send email to
<rekado>rebuilding xorg-server, libepoxy, and all that isn’t normal.
<rekado>what are your thoughts about merging wip-texlive?
<mbakke>pkill9: can you inspect those .drv files? I would assume these are just "grafting" derivations, which would be expected.
<rekado>substitutes look bad for armhf-linux, but i686-linux and x86_64-linux are in decent shape.
<rekado>mbakke: but why would it download the source code for those packages?
<rekado>I also think that we’re declaring graft derivations separately.
<rekado>“The following grafts will be made”
<mbakke>rekado: Right, I missed the source downloads. Looks like a bug indeed :-)
<mbakke>rekado: armhf and aarch64 can barely keep up with master right now, so they will "never" gain decent coverage on big rebuild branches.
<mbakke>so I think we can merge it
<mbakke>as long as texlive and important dependencies (i.e. 'guix') are still working on those arches, of course
<rekado>we don’t have ant-bootstrap on i686-linux
<rekado>(on wip-texlive)
<rekado>64.3% substitutes available on i686-linux
<mbakke>rekado: we don't have ant-bootstrap on i686-linux on master either
<rekado>so, not too bad then.
<rekado>70.4% substitutes available on x86_64-linux
<rekado>sdl2 is missing on wip-texlive / x86_64-linux
<samplet>mbakke: Should I just cherry-pick the Haskell changes from core-updates? What makes things easiest for you?
<mbakke>samplet: cherry-picking will work nicely
<rekado>switched berlin from 1G to 10G
<rekado>don’t think it’ll make much of a difference according to initial tests.
<rekado>but it seems to work
<rekado>complain if it doesn’t
<rekado>I’ll merge master into wip-texlive and then wip-texlive into master later today.
<quiliro>Saluton Guix!
<Minall>Hello guix!
<Minall>quiliro: Kiel vi fartas!
<quiliro>Minall: Bone! Ĉu kaj vi?
<Minall>Mi fartas bone
<efraim>'requires.private' in a package's .pc file means it should be propaged, right?
<rekado>efraim: yes
<efraim>ok, i'll go ahead and fix openconnect
<rekado>hmm, gnome-maps is broken (again)
<rekado>says “Unsatisfied dependency: Goa”
<rekado>ah, looks like an easy fix
<rekado>(and it’s already been reported as 35761
<efraim>gnutec: you have an IMB->IBM typo :)
<efraim>and depending on how powerful your machine is and how expensive your internet is, you might decide to disable substitutes and build everything locally since the sources are generally smaller than the binaries and change less frequently
<gnutec>efraim: Yes! Thanks. I really don't know that. What about the audio?
<efraim>I don't know, I can't actually read Portuguese
<gnutec>efraim: The audiu doesn't work. With lspci, he is there. You have the same problem?
<efraim>The last time I played a video my audio worked, that was about 2 weeks ago
<gnutec>efraim: Ok!
<mbakke>rekado: did you see commit 2cf1e37c109c8d03fae75bc84f7012f3afa956e5? I wonder if gnome-online-accounts:out is required.
<rekado>oh, I did not see that one.
<rekado>It might not actually be required.
<mbakke>I'll just ignore that input in the merge (conflict).
<rekado>mbakke: okay, thanks! The arguments have also been adjusted to include both :out and :lib. Only :lib needs to remain then.
***Server sets mode: +cnt
<rekado>I just merged wip-texlive into master.
<rekado>I hope this doesn’t cause any problems.
<dutchie>Hi, I'm trying to compile master, and I get error: failed to load 'gnu/tests/install.scm': No such file or directory
*dutchie tries autoreconf
<dutchie>nope :(
<dutchie>gnu/tests/install.scm is there, it looks right at first glance
<pkill9>bad news: there is nonfree software packaged in Guix - aseprite:
<pkill9>oh actually the guix packaged aseprite is older, that's probably a newer license, so it's probably not nonfree
<pkill9>ah, yea
<Sharlatan>Hi, I try to build/add new package but can't reproduce steps in
<Sharlatan>"./pre-inst-env" not sure what that should be
<dutchie>it's a script produced after you've run ./configure
<Sharlatan>there is not configure in guix git repo :)
<Sharlatan>only "./bootstrap" wich is executable
<dutchie>yep, that will create a configure script for you
<Sharlatan>I expected the same
<Sharlatan>ok, autoconf missed
<Sharlatan>yep here
<Sharlatan>guix package -i autoconf automake gettext texinfo graphviz help2man
<Sharlatan>guix environment guix
<Sharlatan>Still can't see "./pre-inst-env"