IRC channel logs

2019-08-23.log

back to list of logs

<leungbk>Is there a way to view build logs of successfully installed packages?
<leungbk>I want to confirm that my tests are running.
<nckx>leungbk: There's ‘--log-file’.
<leungbk>@nckx Thanks!
<Minall>Hello guix!
<Minall>quiliro: Kiel vi fartas!
<rschifflin>o/
<Minall>Hello guix!, I'm unable to share internet throught my laptop... In other systems I will set my laptop as a router to share internet to other pc... But when I do the same on guix, it doesn't work..
<Minall>What should I do?
<tune>anyone managed to get ibus and ibus-anthy working?
<tune>I can't get it or mako working, both seem somewhat related to dbus. starting to wonder if it's all related
<jgibbons[m]>If i want the store on a dedicated drive what should i put in my config?
<ecbrown>jgibbons[m]: can you put /gnu on a separate partition, https://guix.gnu.org/manual/en/html_node/File-Systems.html
<ecbrown>then associate it with the UUID of the drive?
<jgibbons[m]>More complex than that. The kernel is in the store.
<jgibbons[m]>Is the installer smart enough to specify to grub the kernel's location in hd1 when the / directory is in hd0 but store is in hd1?
<jgibbons[m]>I guess I'll have to try it in a VM.
<ecbrown>here's an embarassing question: which package provides the `clear' command?
<jgibbons[m]>readline i think
<jgibbons[m]>nope. ncurses.
<jgibbons[m]>readline has ncurses as a propagated input.
<jgibbons[m]>i guess that's just how it works.
<ecbrown>whoop! there it is! thanks. not a package i think about installing so often :-)
<jgibbons[m]>Now i'm wondering why I installed readline.
<jgibbons[m]>Looks like the instaler ISO from the website gives an eerror when I try to use one drive for / and a second drive for /gnu
<jgibbons[m]>Time to see if it has been fixed since then. It's been forever since I called guix pull
<jgibbons[m]>Tomorrow I will see if the installer ISO was fixed in the source.
<jgibbons[m]>Good night guix
<civodul>Hello Guix!
<rekado>historic #guix logs restored: http://logs.guix.gnu.org/guix
<rekado>a couple of days are missing, because logs for them were not included in the dump I received.
<rekado>(converted the logs from a SQL database dump)
<jonsger>nice rekado :)
<efraim>rekado: I probably have some more logs from my quassel instance if you want
<rekado>efraim: I’d be happy to get more logs :)
<efraim>I'll have to see if I can figure out how to get just the guix logs, I think I have logs going back to 2015 sometime
<civodul>rekado: yay, thanks!
<civodul>now we can read the smart things we said back in 2013 :-)
<rekado>I already found one smart thing I said about macros vs eval in 2015 on #guile…
*rekado shakes head
<civodul>:-)
<nly>lol
<pinoaffe>I tried to make my own channel ( https://gitlab.com/pinoaffe/guix_config ), but I get an error "no code in module" - any idea why?
***len1 is now known as lenn
<nly>check the define-module statement at the top of modules
<nly>it should match the filename
<nly>(define-module (gnu packages python-unmerged) -> (define-module (boost-unmerged)
<pinoaffe>nly: oh hey, thanks ;)
<nly>:)
<pinoaffe>nly: I changed that, it still doesnae work
<nly>what's the error?
<pinoaffe>still the same error, "no code for module boost-unmerged"
<nly>just a sec, checking the manual
<nly>i have to check what .guix-channel does
<nly>i see you have directory 'packages' in there
<nly>this is still wrong (define-module (gnu packages boost-unmerged)
<nly>(define-module (boost-unmerged))
<nly>pinoaffe^
<pinoaffe>right, now I get it, it works, thanks a lot for your patience
<nly>reason being (boost-unmerged) translates directly to ./boost-unmerged.scm
<nly>and it's easy to guess (gnu package boost-unmerged) translates to? :)
<nly>./gnu/packages/boost-unmerged.scm
<nly>which does not exist
<nly>hope it makes sense :)
<nly>pinoaffe^
<pinoaffe>yeah, I changed the directory paths a bit
<roelj>Is there going to be another minor version bump for Guix anytime soon?
<sneek>Sneeky bot running on Guile version 2.0.11 using bobot++ 2.3.0-darcs
<civodul>hi roelj!
<civodul>roelj: i thought we could do that once core-updates is merged, but that has been taking more time than expected
<civodul>do you think it should happen sooner?
<roelj>civodul: Maybe. I like the minor version bumps because I use it as semi-stable version to jump to. Maybe my use-case is just wrong though.
<roelj>civodul: And.. of course.. I'd like to upgrade ;)
<civodul>you can always run "guix pull"
<civodul>versions are mostly useful for new installs actually
<rekado>I was hoping we could merge core-updates ‘soon’ and then cut a release.
<rekado>what is to be done about core-updates-next, though?
<rekado>should I stop building core-updates on ci.guix.gnu.org and build core-updates-next instead?
<zaab>hey anyone guix users happen to be at ccc? would be awesome to meet up! :D
<rekado>I can’t go.
<jonsger>does some one see this error while running `guix lint --checkers=refresh hello` https://paste.opensuse.org/view/raw/8185477
<rekado>jonsger: I cannot reproduce this.
<jonsger>maybe 4496ea74aaf9d2497ac3eaf8f780a250bed24503 fixes it. I build guix now from newest master, let's see if the issue is still there
<jonsger>guix is built against guile-json3
<civodul>rekado: core-updates-next is being built for the "core" subset
<civodul>fortunately that's "only" for x86
<civodul>the rest is still valid, i think
<civodul>but essentially, it needs to be built
<civodul>that's unfortunate because we had reached the point where core-updates was almost entirely built
<civodul>but that's life!
<rekado>the 30 new servers might arrive on the 28th already
<civodul> https://ci.guix.gnu.org/jobset/core-updates-next
<civodul>nice!
<rekado>installing them will be slow, because we can’t just do a PXE install :-/
<civodul>we still have a bug where offloaded builds sometimes get "stuck" though :-/
<rekado>do you know if anyone looked into what needs to be done for PXE installs to work?
<rekado>would be really nice if I could install a Guix base on all servers over network and then use ‘guix deploy’ to install a particular configuration.
<rekado>my plan now is to boot each of the servers from USB, manually install a base system, and then use ‘guix deploy’.
<civodul>rekado: i don't think anyone looked into PXE
<civodul>i think we discussed it with Danny a while back?
<g_bor[m]>civodul: hello.
<g_bor[m]>Hello guix.
<g_bor[m]>I also discussed this with danny.
<g_bor[m]>It seems we have everything we need on the server side.
<g_bor[m]>What needs to be done is to get Guix System boot.
<civodul>i'm not really familiar with PXE but i feel like we should spawn this topic on the list and get Danny on board ;-)
<rekado>I remember from my past attempts with iPXE that the root disk couldn’t be found.
<rekado>(it was also *extremely* slow)
<civodul>couldn't be found by the kernel?
<rekado>yes
<jonsger>the `guix lint --checkers=refresh` error seems to be network/certificate related, as with "0xffff" hosted on github it succeeds
<rekado>with iPXE the whole disk image is used to boot the system.
<rekado>PXE is simpler and expects just the kernel and the initrd
<civodul>the file system lookup code in Guix looks for local block devices
<civodul>maybe we need to do something there?
<rekado>probably
<rekado>I didn’t investigate this; my tests happened about a year ago, though.
<g_bor[m]>Yes, rekado is right. For this we would need a kernel and an initrd. These should be able to find and mount the root filesystem. IIRC danny proposed to keep the root on nfs as a first step.
<g_bor[m]>rekado: it looks like from the docs, that ipxe can also be made to work with the kernel+initrd only. Though I might be mistaken...
<quiliro>Saluton Gikso!
<sisyphe_>I made a tool to generate package definition for rust crates (recursively), maybe someone can find it useful: https://github.com/lelongg/carguix
<quiliro>nly: Mi vidis vian filmon en Viewtube-o.
<quiliro>nly: dankon....
<jonsger>rekado: the lint issue is still persistent on d78bc23411
<quiliro>sisyphe_: what is rust crates?
<jonsger>quiliro: https://crates.io/ rust packages
<sisyphe_>quiliro: fancy name for packages
<nly>quiliro i can almost read that i believe, glad it's helping :)
<jonsger>okay this gets confusing now. On my other Tumbleweed machine I got a different error while running `guix lint --checkers=refresh hello`
<jonsger>ah, only missing env variables
<jonsger>still the same error
<len1>Hi, I am looking for some help in writing a guix package
***len1 is now known as lenn
<nly>hi lenn
<nly>are you familiar with scheme?
<lenn>a little bit
<nly>you only need to know a few details about the package
<nly>do you use emacs by any chance?
<lenn>so I've already written the easy parts of pkg def but I don't know how to write the build itself
<lenn>I use spacemacs, yeah
<nly>ah i see, i hope you're using the yasnippets package... that can ease the boilerplate a bit
<lenn>Is the arch aur pkg definition helpful?
<lenn>boilerplate is ready
<nly>do you know the build steps for your pkg?
<lenn>well the easy part is to download executable from git
<lenn>and put it into the /usr/bin
<nly>you would need to see the build instructions in their git repo
<nly>well, you could try that
<lenn>that's the instructions - download a bin file and put it into the right path
<lenn>*bin file
<lenn>here is the definition I have so far: https://pastebin.com/LmsyL5FE
<nly>there must be a build from source/git is there not?
<lenn>there's a makefile in the source, but I am not good make so, I tried to take the easy way of just downloading the bin file
<lenn>similiar to the way arch aur pkg ddev-bin is build
<nly>i found these build instructions https://github.com/drud/ddev/blob/master/docs/developers/building-contributing.md
<reepca>dangit nly, I was just about to paste that link...
<nly>reepca haha, would you know if directly copying the binary would work?
<nly>(not that i'd recommend that, just curious)
<quiliro>nly: it would be nice if the videos were on your website...maybe with mediagoblin
<quiliro>i heard it is easy to set up
<lenn>ty, I'm checking them out
<nly>lenn your package looks good otherwise
<quiliro>i saw a page on the guix website with links to videos...but i think that yours are not there
<lenn>ok brb in a few min
<jonsger>rekado: oke, the issue seems to be have something to do with my openSUSE package. Can't reproduce it with guix binary install
<nly>quiliro i have them over on guix-tube but those links will work only while i can run my machine
<nly>i'll look for a foss friendly alternative to host them as a more reliable mirror
<reepca>nly: it looks like it's statically-linked, I tested running it on guix system (gave me this weird feeling) and it seemed to work, though how much of that is my profile I don't know.
<nly>ah thanks reepca, i just learned something
<jonsger>it's very strange. Happens with guix 1.0.1 openSUSE package on Tumbleweed, but not with 1.0.1 from the binary installer
<Minall>Hello guix!
<Minall>quiliro: Kiel vi fartas!
<civodul>rekado: i've been told it'd be nice to have /tmp and possibly /etc/{passwd,shadow,group} in our 'guix pack -f docker' images
<civodul>thoughts?
<civodul>i don't see any downsides to that, and it does seem to make things more convenient
<nly>civodul you might be interested in this? http://issues.guix.gnu.org/issue/37094
<relatev>Is there a way to specify multiple architectures in a definition of /etc/guix/machines.scm? Like aarch64-linux and armhf-linux for one machine
<quiliro>Minall: saluton...mi fartas bone...
<Minall>quiliro: Que ta la tarea!
<quiliro>Minall: la tarea está muy bien
<civodul>nly: nice!
<quiliro>te felicito
<Minall>Gracias!
<jonsger>I filled https://issues.guix.gnu.org/issue/37160 for now, maybe others have ideas :P
<pinoaffe>is there documentation for how defining a build system works?
<civodul>pinoaffe: not really i'm afraid!
<civodul>hopefully you can easily find out by looking at, say, (guix build-system python)
<efraim>When I did perl6 I started I think with the gnu build system and then factored my custom build phases out into a build system
<pinoaffe>civodul: yeah, that's what I've been doing so far, was hoping there'd be documentation of some sort
<civodul>pinoaffe: unfortunately it's lacking in this area
<rekado>civodul: I don’t know if that’s a good idea. In my opinion a bundle generated with ‘guix pack’ should use whatever user/group database that the host is using, so wouldn’t it be better to (optionally) map the host’s /etc/{passwd,group,shadow} files into the container at execution time?
*rekado extends the CRAN importer to import R packages from git
<Minall>Hello guix, how can I change the build options of a package? for example, adding: ./configure --with-xwidgets to emacs
<civodul>rekado: the thing is that Docker does not create /etc/{passwd,group,shadow}
<civodul>so if it's missing from the image, then it's really missing
<civodul>apparently typical images (Debian, etc.) contain all that
<civodul>because they basically contain the whole distro
<joshuaBPMan>Hello, I've had guix install on my laptop before. I recently upgraded it to an SSD, and doubled the RAM. Now when I try to install (manual install via DVD), I keep getting kernel panics. I can format my sda partitions, mount them, start herd cow, but I have not had any luck finishing guix system init /mnt. The last time it ended in a kernel pa
<joshuaBPMan>nic...what is the most likely cause? A faulty installation image or a broken laptop?
<tune>you could run memtest86 to rule out the possibility of bad RAM
<tune>also remake the DVD installer or better yet use a flash drive (if you have one) so you can rewrite it more easily in case of corrupt data
<joshuaBPMan>tune: I can't seem to install guix via usb. The Macbook bios doesn't recognize it as bootable.
<joshuaBPMan>It's a Macbook 7,1. It's always done that. :(
<tune>ah... macbooks can be tricky. I helped a friend install debian on his macbook once, but I don't remember the details anymore
<joshuaBPMan>yeah...I'm considering switching to something else. What would be a good switch? Lenovo? I'd love to get libre all the way down to the bios...but I'm ok with an old intel machine as long as the motherboard supports 8GB of ram and 500GB harddrive or SSD
<joshuaBPMan>even 250GB harddrive would be fine
<weedloser>fully libre on modern hardware is going to be really difficult
<weedloser>old thinkpads is the goto if it's really important.
<tune>yeah, something like the thinkpad x200 with libreboot support, or for something newer there's the asus c201 chromebook with libreboot support
<tune>the pinebook pro just came out but I don't think it's *fully* libre. probably better than a lot of options, at least.
<vagrantc>i wouldn't recommend the c201...
<tune>there's also the MNT Reform being worked on
<vagrantc>haven't gotten X working usably on c201...
<tune>the c201 has the gpu and wlan issues I guess but if you put those aside it's got a free ec firmware which is more than what the thinkpads have
<tune>oh okay
<vagrantc>it's been a while since i tried ... severe shearing and full-screen 1-second redraws on trivial actions...
<joshuaBPMan>thanks for the tip. How about a used laptop with proprietary bios? What brand should I pick? Dell Lenovo?
*vagrantc needs to figure out how to order a pinebook pro ...
<vagrantc>that should be possible to free; just need to rip out the DRM in arm-trusted-firmware
<tune>a friend of mine just got to order his pinebook pro. you need a forum account and then they send you a coupon code which is needed to actually order it
<tune>due to high demand
<tune>so there's a queue to get the code I believe
<weedloser>dell xps is really solid
<vagrantc>yeah, i got a forum account, and tried to get the code, no idea if it worked, though
<weedloser>painbook pro
*vagrantc needs to test guix on the original pinebook
<vagrantc>might need to pull in some kernel config updates; running current 5.2.x on debian works reasonably
<vagrantc>not a fast machine, but not bad either
<tune>it would be interesting to hear which ARM options worked well with guix, I've been thinking of migrating away from my ThinkPad X220T at some point
<joshuaBPMan>weedloser: thanks
<jgibbons[m]>When I try to generate an install iso, it looks like guix doesn't include grub.
<jgibbons[m]>time guix system disk-image --file-system-type=iso9600 --verbosity=3 --root=installation-os-x86_64.iso --system=x86_64-linux -e '(@ (gnu system install) installation-os)'
<jgibbons[m]>(part of a script)
<Minall>./pre-inst-env: command not found, what should I do?
<jgibbons[m]>Did you ./bootstrap?
<quiliro>Minall and I are following https://guix.gnu.org/blog/2018/a-packaging-tutorial-for-guix/
<quiliro>Direct checkout hacking
<Minall>jgibbons[m]: On it!
<quiliro>jgibbons[m]: i get the same error as Minall even after running ./bootstrap
<jgibbons[m]>What part of the tutorial are you on?
<quiliro>jgibbons[m]: we are setting the environment...it was probably that
<quiliro> https://guix.gnu.org/manual/en/guix.html#Building-from-Git
<jgibbons[m]>that section looks like it's based on the manual section with the same title
<jgibbons[m]> http://guix.gnu.org/manual/en/guix.html#Building-from-Git
<jgibbons[m]>Does ./bootstrap give you an error?
<quiliro>jgibbons[m]: it is working now
<Minall>Yep, running ./bootstrap and ./configure
<jgibbons[m]>How'd you fix it?
<jgibbons[m]>ok
<quiliro>that was the command we should have run...as you said
<quiliro>then ./configure
<jgibbons[m]>I forgot ./configure
<quiliro>and then make check
<jgibbons[m]>Didn't know make check was necessary
<Minall>make check seems to not be that important if it all works, since it only checks for errors
<quiliro>QA is very important
<jgibbons[m]>Is anyone able to add this little detail to the tutorial?
<quiliro>jgibbons[m]: it is in the tutorial to go to the contributiong part of the manual before continuing
<quiliro>but it would be better to incorporate it to the tutorial and add the channel details too
<quiliro>i guess there will be another blog with a newer tutorial
<quiliro>or maybe a tutorial that Minall keeps updating
<quiliro>in spanish...
<quiliro>;-)
<Minall>jaja! could be amazing
<quiliro>Minall: aren't you already making your own tutorial?
<Minall>Yes, but can it be on guix?, hardly, but possible
<quiliro>it can be on guix if it promotes only free software
<xavierm02>If I'm trying to package something, and I'm in a guix environment in the directory with the sources, how do I patch sheebangs?
<xavierm02>(other than manually)
<xavierm02>My bad this may be a useless question
<xavierm02>the more general question is: Is there some way to run one phase of a build system in the current directory?
<bavier>hello again guix
<g_bor[m]>Hello guix!
<g_bor[m]>xavierm02: I believe we di not have such a machinery at the moment. I would add a hard failung phase after patch-shebangs, and use keep-failed.
<g_bor[m]>Sorry for my spelling. I'm on mobile...
<Palpares_>"sorry for the car accident, I'm on mobile..."
<Palpares_>"sorry for not looking at you tonight darling, I'm on mobile..."
<quiliro>what is the difference between (list (list "pkg-config" pkg-config)) and (list "pkg-config" pkg-config)
<quiliro>?
<reepca>quiliro: one is a list containing a list of 2 elements, and the other is just a list of two elements
<quiliro>thank you reepca
<quiliro>so the first has only one element (which itself has two) and the second has 2 elements?
<reepca>Yes. Another way of putting it is that the second thing you wrote is a list containing only the first thing you wrote.
<quiliro>ok...i do not think i get the use of a list inside a list
<reepca>quiliro: the two-element lists specify a name and a package-like thing. You could also think of it as a list of "input-spec" structures, but that approach would end up being more verbose.
***sneek_ is now known as sneek
<PotentialUser-67>Hello, how to configure ethernet (static ip) for installation pfocess and config scm?
<sisyphe_>looking for help packaging a rust crate which use pkg-config at build time. is someone available ?
<bricewge>What is meaning to prefix some variables with %? For example %base-services.
<quiliro>hello bricewge ... prefix % means to place % before the variable
<quiliro>% is used as an aid to remember the type of wariable it is
<quiliro>it is like _ in C language
<bricewge>quiliro: Okay, thanks!
<quiliro>bricewge: what do you think would be a better wording ?
<quiliro>to explain that
<bricewge>Hum it was just the meaning of % that I was missing
<quiliro>where did you see it?
<bricewge>Is there somehwere that it's written about?
<bricewge>Reading code and the manual
<nckx>There is no clear meaning, different people use it differently.
<quiliro>yes...i just do not remember where...i think it is explained in the guix manual or on some scheme or guile manual
<nckx>Ludo' explained his understanding (because I was equally confused by the different conflicting uses) in a mail which I can't find.
<nckx>It's just a convention, often meaning ‘systemy’ or ‘globalish implementation detail’, but everyone brings their own nuances, then writes code using it that way.
<nckx>quiliro: It would be interesting if you could find a more formal definition than mine, although I haven't. 🙂
<bricewge>nckx: Finding the good keywords, when doing a search on such topic, to have relevant result is quite difficult.
<nckx>Indeed… tell my mail client.
<nckx>It doesn't even want to search for ‘%’ ☹
<Minall>Hello guix!
<Minall>quiliro: Kiel vi Fartas!
<quiliro>Minall: Mi fartas bone. Ĉu kaj vi?
<quiliro>Minall: Kiel vi fartas?