IRC channel logs


back to list of logs

***Zungo is now known as Juesto
***asdf__ is now known as fsstjsgj
<reepca>Question... why does our clone procedure pass a null pointer as the child stack? How does that work?
<reepca>never mind, saw the bit about that tucked away in the man page
<efraim>I'm glad you figured that out because I had no clue and that just sounded strange
<catonano>some time ago I posted here a linkk to a tweet pointing to a talk by some illustrious clojurer about why it's important to have a single language in the whole stack. I can't remember it. Can anyone here gently point me back to it ?
<catonano>I found it ! It's here
<civodul>Hello Guix!
<catonano>hello civodul !!
<efraim>it turns out porting ccl to aarch64 isn't quite as trivial as copying platform-linuxarm.h to platform-linuxarm64.h and changing "32" to "64" in the new header file
<reepca>civodul: I finally pushed my local changes. I've run into a bit of a brick wall in trying to figure out what's going wrong. The guile builder for the bootstrap make is failing in a bizarre way, though it's more accurate to say the bootstrap guile itself is failing in a bizarre way. I asked a bit about it in #guile. Some low-level part of the bootstrap guile produces some sort of error, but the output says nothing about what kind of
<reepca>error, and attempting to invoke the bootstrap guile interactively from within the build environment causes it to display the copyright notice and immediately exit (exit code 0, though). Additionally, --no-auto-compile is ignored, but GUILE_AUTO_COMPILE=0 is honored.
<reepca>The issue only happens in the build environment. Aside from diving straight into guile's source to try to figure out what a "apply-smob/1" is and why it might fail, the only way I can think of continuing debugging is to slowly comment out isolation mechanisms and see when it starts working.
<civodul>heya reepca
<civodul>reepca: wait, i'm a bit lost, could you email the details somewhere?
<civodul>with ways to reproduce etc.
<civodul>i'm catching up with email right now
<reepca>probably a good idea
<civodul>cool thanks
<civodul>also could you send a summary of the latest changes you've made?
<civodul>ideally on the mailing list if that's fine with you
<civodul>rekado: how was BOSC? :-)
<civodul>rekado: your slides are great, esp. the whale that says "LOL" :-)
<civodul>(my officemate must wonder why i'm laughing :-))
<catonano>can thhese slides be seen ? I wanna laugh too !
<civodul>they're in guix-maintenance.git currently, i'll put them on the web site
<catonano> civodul: ahh thanks !
<catonano>they're beautiful !
<quigonjinn>using 'guix system vm-image config.scm', I'm getting the error:"Could not access KVM kernel module: Permission denied, failed to initialize KVM: Permission denied". Any idea what the issue may be?
<civodul>quigonjinn: make sure /dev/kvm is read/write for your user
<quigonjinn>civodul: yes it is, my user is in the group dialout. I get the same error, running the command as root.
<quigonjinn>I can also run qemu with the --enable-kvm flag, though I don't know if that should be indicative or not
<reepca>civodul: description sent. Hopefully it's not too rambly, it's 5:00 in the morning over here
<civodul>reepca: indeed, for a minute i was wondering if you had changed time zones or something :-)
<civodul>anyway, thanks!
<civodul>i'll comment ASAP
<efraim>when I run `guix weather` against bayfront I get: guix/scripts/substitute.scm:678:16: In procedure fetch-narinfos:
<efraim>guix/scripts/substitute.scm:678:16: In procedure struct_vtable: Wrong type argument in position 1 (expecting struct): #f
<civodul>efraim: what --substitute-urls option did you pass?
<civodul>yeah that's not a valid URL :-)
<efraim>hmm, good call :)
<civodul>should be
<civodul>but yeah, error handling should be fixed
<efraim>hmm, just got 0% from
<efraim>i'll try it again now that guix-publish is running
<civodul>efraim: i think you'll need "-s aarch64-linux"
<efraim>i'm running it from the firefly ATM
<civodul>i'm failing to contact it ATM
<efraim>you made sure to use port 8181?
<civodul>yes, the connection is established but nothing happens
<civodul>now the core of 'guix publish' is single-threaded
<civodul>so if there's no nginx front-end or equivalent, that might explain things
<efraim>i got the hashes all the way across the bottom, now it's thinking, has been for a while
<civodul>do you get the "updating list of substitutes" progress report?
<quigonjinn>could someone tell me their permissions from 'ls -l /dev/kvm' from a guixsd system?
<reepca>quigonjinn: crw-rw----+
<solene>hello, is there a way to download an iso of the nightly version ?
<quigonjinn>reepca: and what group does it belong to? it's dialout for me, but I suspect it should be the kvm group, which does exist on my system
<quigonjinn>actually, changing the group to kvm with chown fixed the problem for me. But are we supposed to change groups manually in guixsd, or would a 'guix system reconfigure' have fixed that?
<solene>quigonjinn: maybe you could add your user to kvm group ?
<quigonjinn>solene: it seems it's not needed, because 'guix system vm-image' run successfully. I suppose the user in this case is guixbuilder
<solene>quigonjinn: I have the problem that guisd doesn't boot on my system so I would have tried a nightly build if available. (the previous releases don't boot either)
<solene>or, if someone is kind enough, one could provide me a vm-image generated from his/her computer
<quigonjinn>solene: I could generate a vm-image, but my upload speed is terribly slow, so it would probably be a bad idea to send the whole image to you
<solene>quigonjinn: It's only 190M once compressed with xz, at 60 kb/s that would takes 190 minutes
<quigonjinn>solene: does the GuixSD 0.13.0 Virtual Machine Image from not work for you? What's the issue?
<solene>quigonjinn: I am using OpenBSD on my main system, I can't use virtual machine
<quigonjinn>but you asked for a virtual machine image, no?
<quigonjinn>ACTION goes afk for a while
<solene>quigonjinn: no, I didn't ask for a VM, I asked for a bootable iso :)
<nckx>solene: I'll build one.
<solene>nckx: I appreciate
<nckx>No idea how long it will take. It's currently building... ncurses? OK. :-/
<solene>I have time :)
<nckx>solene: Oh: x86_64, I hope, right?
<solene>nckx: yes
<civodul>efraim: i'm about to push your post on aarch64, thanks!
<civodul>i'm adding a sentence at the top to give context, and one at the bottom to ask for help re build machines
<civodul>fine with you?
<efraim>sounds good, i was thinking it might be more "first-person" than some of the other posts
<civodul>indeed, but i think that's also fine
<jsierles>civodul: hey! what are the prerequisites for running the weather command locally?
<efraim>after placing it in guix/scripts/weather.scm, its './pre-inst-env guix weather --substitute-urls='
<efraim>with '-s foo-linux' to check the 'foo' architecture
<jsierles>efraim, ok, so that means having a checkout of guix, and having compiled guix somehow?
<civodul>here we go!
<efraim>hmm, not sure how to run it without a checkout
<jsierles>i suppose it's time to work out how to use a local checkout.
<civodul>if you don't have a checkout, you can put it in GUILE_LOAD_PATH
<jsierles>i see
<efraim>civodul: yay!
<efraim>i probably should've signed odroid_guix.key
<civodul>right, still time to do it!
<civodul>i've seen the reproducible-build/Debian people got hardware from
<jsierles>civodul: so it does look like an issue with my reverse proxy
<civodul>jsierles: oh, interesting
<civodul>ok, i've never used it
<civodul>efraim: i can talk to your server now, and it has 75% of the substitutes i'm interested in :-)
<civodul>(for aarch64-linux)
<efraim>not bad
<civodul>it's also very fast
<efraim>I think it should only have aarch64-linux, and a lot of sources
<civodul>'guix weather' does not check for source
<efraim>it didn't get stuck on ccl?
<civodul>initially i tried with "-m foo.scm", but now it does get stuck
<civodul>what's the story?
<efraim>ccl is unsupported, so it has a wierd entry for one of the inputs
<civodul>oh it should skip unsupported packages
<civodul>but still, kinda weird
<civodul>oh i see: the 'origin' form ends up doing (base32 "")
<civodul>leading to an invalid hash, hence the error
<jsierles>civodul: i'll look into it. do you know if the client does some http streaming?
<efraim>it looks like chez does it differently, I need to change the supported-systems there anyway
<wigust>Hello Guix
<civodul>jsierles: it uses "http pipelining" quite extensively (is that what "http streaming" means?)
<civodul>hello wigust!
<jsierles>civodul yes that would be it
<civodul>so you need to authorize it, it's important for performance
<civodul>efraim: your server just got stuck (my requests are at 87%)
<efraim>i was running guix weather against it with everything, but just turned it off
<efraim>turned off the request, not the server
<civodul>so it has 58% of the aarch64 binaries
<civodul>not bad either for a lonely machine!
<efraim>i bet I could game the system by targeting python and perl packages :)
<civodul>heheh :-)
<civodul>we should really fix remaining issues in core-updates now
<nckx>solene: It's unlikely to solve your boot problems but... oh well. I'm uploading a regular disk-image too.
<solene>nckx: thx I'm downloading it
<solene>my boot problem is that I just get a blank cursor (white square) before getting grub/syslinux, then the screen shutdown, and display the white square again and again
<Juesto>looks like a motherboard ROM issue solene
***Piece_Maker is now known as Acou_Bass
<Juesto>or unable to boot properly
<solene>I had no problem with others OSes, only guix has this problem. FreeBSD/OpenBSD/NetBSD and a few others linux distros works
<Juesto>cd or usb
<solene>usb, it's a laptop which doesn't have an optical drive
<Juesto>was the same stick used for other distros sometime?
<Juesto>it may be that it is faulty for some reason
<solene>no, but I tried guix with differents memory sticks
<nckx>solene: Oh. Then why explicitly ask for an ISO? Be sure to try the regular image too.
<Juesto>are the isos hybrid?
<solene>I though the iso were hybrid ?
<nckx>They should be. But that's a recent thing & there are surely still some bugs to coax out.
<Juesto>theres only a usb install image and a vm disk image on the official download page
<nckx>I mean, testers are good, but let's establish that we can boot something, anything, first :-P
<Juesto>sure, on a vm
<Juesto>i'll try the iso
<Juesto>in 2 hours
<solene>I'm dding the memory now
<Juesto>actually between 3-6 hours
<solene>nckx: you may want to compress it ? That would save a lot of time to download for juesto :)
<Juesto>actually, it is 96kbs for some reason
<solene>(and save bandwidth / energy)
<Juesto>solene: not sure if its me or his server
<Juesto>since i normally should have 400kb/s
<solene>Juesto: if you download slowly, you will get it faster if you need to download 200M instead of 900
<Juesto>i know
<nckx>Good point. Server should do 10Mbps, though.
<Juesto>actually i can just close the culprit
<Juesto>ping my ip
<Juesto>nvm actually
<solene>I really want to get into guix community and hack on it, but I haven't got any of my computer to boot it
<Juesto>the usb install image didnt work?
<nckx>solene: UEFI or BIOS?
<Juesto>well you can always try on a vm
<solene>I have a laptop supporting only UEFI and even with 0.13 this doesn't work
<Juesto>In that case the ESP should be made booteable
<solene>ESP ?
<Juesto>i've checked that the images have boot flag on the first partition
<Juesto>EFI system partition solene
<Juesto>it only contains efi/boot64.efi
<Juesto>which is the standard file UEFI looks for
<Juesto>efi and uefi inherit all the stuff that was advanced RISC computing back then
<Juesto>and nckx i dont mind waiting
<solene>still copying, while I download the iso at 5 Mb/s, openbsd can't do better than 1 Mb/s on usb
<nckx>solene: With large bs=? Eek.
<solene>nckx: yes :)
<solene>1M or 5M or 10/20/100 that doesn't do better than 1 Mb/s
<solene>haha 1081411584 bytes transferred in 1016.061 secs (1064317 bytes/sec)
<solene>that doesn't boot better :(
<solene>at least now, my usb keyboard gets power than shutdown, power, shutdown etc...
<Juesto>im a bit sleepy
<Juesto>ups wrong channel
<civodul>solene: the USB install image of 0.13.0 is supposed to boot on UEFI machines
<civodul>it does on mine
<civodul>perhaps you could send the details to
<Juesto>404 /
<nckx>solene: Yeah. Try the non-ISO .img (now available in delicious xz flavour!). If that doesn't work, and you can't fiddle with boot options to get it to, you'll have to talk to someone with more of a clue about UEFI than me.
<Juesto>is the stick gpt?
<Juesto>You need to tweak in gparted
<Juesto>move the boot flag to the ESP
<nckx>solene: ...from the same URL. You may need to hard-refresh.
<Juesto>no need
<Juesto>i tried
<Juesto>depends on browser i guess
<solene>Juesto: I just use dd to make the stick
<nckx>Juesto: OK. That box usually serves only substitutes, so it caches more aggressively than I usually do.
<Juesto>solene: i did use dd too actually a converter from raw to vdi for use with virtualbox
<Juesto>on the official release i've checked that the boot flag is in the first partition, not the second which is the ES
<Juesto>probably related to mbr
<solene>my current box supports EFI and legacy
<solene>nckx: it's copying... slowly :)
<nckx>solene: I successfully installed GuixSD on a UEFI-only machine using that .img (well, a week older) so it really should work.
<nckx>The same machine that now built it for you, so I hope it works just for the poetry of things.
<solene>nckx: I'll try on my computer which doesn't support guix at all too, I'll keep you informed
<Jackneillll>why dont you guys distribute an .iso like everyone else?
<nckx>Jackneillll: Because it's a lot of fiddly work for little gain? Anyway, we will soon.
<ng0>it's almost done
<Jackneillll>nckx, what kind of work?
<nckx>Ironically, the main reason ISOs were added were to support VPS providers which only support that format. Ah. Legacies.
<ng0>an ISO is not something you create within a days worth of work
<Jackneillll>anyway, i've downloaded the usb installer, made it to a .vdi, but how am i supposed to install it in vbox?
<Jackneillll>(vboxmanage --format vdi)
<ng0>what is that, VirtualBox?
<Jackneillll>ng0, yes vbox is a common shortening
<Jackneillll>of that name
<nckx>Jackneillll: Making valid(ish) ISOs that boot GRUB on all platforms and pretend to be something else entirely when dd'd to block devices. That kind of work.
<nckx>More gory details await all who ventures within the guix-devel archives.
<ng0>nckx: the next leap of faith would be to make an architecture-aware ISO which gets bigger but can start on two or more architectures.
<Jackneillll>nckx, right, but in that case please provide info in how to use the usb one with vbox. i have seen the qemu img, but that doesnt? have gui for the lazy?
<nckx>ng0: I saw you mention that before (I forget where) and found it *very* interesting. By ‘architectures’, I take it you don't just mean x86 and x86_64? I wasn't even aware of that being done.
<ng0>we don't support Virtualbox. There are some people that have documented this I think, but it should be easy to locate. Qemu has GUIs and with the right switches I found it easier than Virtualbox.
<nckx>Jackneillll: ^ and also the unfortunate fact that the lazy, at least for now, will not have a good time installing and learning GuixSD.
<ng0>nckx: that isn't being done.. it's just something I came to think of after a recent discussion, and my goals.
<ng0>nckx: I mean x86_64, i686 (and what else is possible later on, but at least those 2). some systems do that, but I have to locate them and look at their code.
<ng0>and if it isn't possible, x86_64 should tell you that you got the wrong architecture if you plug it into an i686 system
<nckx>Hm. I used to know enough GRUB to do that.
<nckx>In fact, that should be trivial.
<nckx>ng0: What happens when you plug that in there now? Nothing?
<ng0>probably, but all I really have after throwing away the only true i686 I had is x86_64
<ng0>well.. I think I could use qemu to simulate this
<nckx>ng0: I can try myself (I have an i686! Which reminds me I should sell it), just thought you might already know.
<ng0>ok.. it's not high up my priority list
<ng0>and the idea is just at the start of an idea
<ng0>my use case goes farther thna just the install-image but the basic theory (booting) needs to exist ;)
<quiliro>hello people!
<sneek>Welcome back quiliro, you have 1 message.
<sneek>quiliro, nckx says: Just ‘git am <patch.eml>’. That's the easy part.
<nckx>Down, sneek.
<quiliro>nckx: i have just guix pull-ed
<quiliro>and openmolar is in guix now!
<quiliro>i have installed it
<nckx>quiliro: So I read. Congratulations :-)
<quiliro>but i don't know how to run it :-D
<quiliro>nckx: thank you :-)
<quiliro>i am so proud of myself!
<quiliro>i am running it now!
<quiliro>it has a wizard that asks me the root password of mysql database...but guixsd has never asked me to set that password
<quiliro>debian asks when it installs the database
<quiliro>is there a way i can set it up?
<rekado>quiliro: since the store is read-only the database state has to be kept outside of the store.
<quiliro>oh...openmolar did not install mariadb or mysql
<rekado>This is why it cannot be configured when the package is installed (e.g. in a post-install script).
<rekado>quiliro: yes, it does not install these.
<rekado>Only the Python bindings are among the inputs.
<rekado>but that’s not necessarily bad.
<quiliro>it is correct because only the client needs to have mysql
<rekado>just like music applications don’t come with JACK and don’t configure it
<quiliro>i meant the server
<quiliro>so i should install mysql or mariadb?
<quiliro>i will try mariadb
<quiliro>after installing what would the database root password would be?
<quiliro>so i can set the new database root password
<quiliro>i suppose it would be blank
<quiliro>and it can be changed with 'mysql -u root'
<quiliro>no password
<quiliro>mysql> SELECT User, Host, HEX(authentication_string) FROM mysql.user;
<quiliro>and finally
<quiliro>mysql> ALTER USER user IDENTIFIED BY 'new_password';
<quiliro>am i correct?
<quiliro>i cannot start the database server ;-(
<quiliro>$ mysql -u root
<quiliro>ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (2 "No such file or directory")
<quiliro>i will be back...i have a meeting
<quiliro>please send the message to sneek
<cbaines>sneek, tell quiliro I'm running mariadb on GuixSD, and the socket does appear at /run/mysqld/mysqld.sock the server might not be running?
<sneek>quiliro, cbaines says: I'm running mariadb on GuixSD, and the socket does appear at /run/mysqld/mysqld.sock the server might not be running?
<lfam>cbaines: Try 'later tell so-and-so'
<cbaines>Ah, ok :)
<cbaines>is "tell" a rather redundant command then...?
<cbaines>for people who don't want to talk to one another
<lfam>I'm not sure why it offers the "tell them now" feature
<efraim>maybe for if people are blocked?
<ng0>sneek, tell ng0 that this feature is strange
<ng0>I can not talk to myself though
<sneek>ng0, ng0 says: that this feature is strange
<lfam>I wonder if anyone has noticed this in Guix
<lfam>libidn2 bug report:
<rain1> this looks like a great example of reproducible science only thing its missing is a guix package to re-run the tests
<jackhill>I'm reading the "running system services in containers" blog post. Where do manditory access control frameworks (like SELinux) fit in?
<cbaines>I remember hearing rekado talking about SELinux, but I can't remember where...
<rekado>SELinux is orthogonal to containers.
<rekado>SELinux requires a) writing policies involving types/labels and b) labelling files.
<rekado>the files in the store would have to be labelled, i.e. their attributes have to be modified outside of Guix, e.g. by a service or cron job
<rekado>I wanted to play with this, but I don’t think I’ll have enough time for this in the next weeks.
<jackhill>right. I'm trying to think through how that would additionally benefit security.
<jackhill>would it make sense to have labeling be part of a defivation?
<rekado>it might
<jackhill>I guess traditional distros have some sort of se-relabel command
<rekado>for grafts Ludo had the idea of treating them as a continuation of the build.
<rekado>for labeling this might be done in a similar fashion.
<rekado>traditional distros have it easy because of the FHS
<rekado>the rules to apply labels are much simpler
<rekado>we would have to take into account more than a handful of directories, so it’s worth rethinking the common ways of doing things.
<jackhill>ACTION nods
<rekado>ACTION –> zzzZ
<jackhill>rest well!
<rekado>ACTION nods off