IRC channel logs


back to list of logs

<joolean>Hello! I'm trying to build an updated version of a package I maintain in guix. I've pulled master, but when I do `guix build [my package]' I get "guix substitute: warning: ACL for archive imports seems to be uninitialized, substitutes may be unavailable" and then later "guix/ui.scm:1255:8: Wrong type to apply: #<unknown-type (0x24f . 0x7faf767a2e48) @ 0x7faf76d672e8>"
<joolean>any ideas?
<methalo_>joolean: can you post the package definition?
<joolean>I can, although it's not even getting that far
<joolean>I get the same thing when I do `guix build guile'
<joolean>I think there's something wrong with my guix environment, but I don't know where to start
<methalo_>try ./pre-inst-env guix build mypkg.scm
<methalo_>under your guix repository
<joolean>same deal:
<joolean>substitute: guix/ui.scm:1255:8: In procedure run-guix-command:
<joolean>substitute: guix/ui.scm:1255:8: Wrong type to apply: #<unknown-type (0x24f . 0x7f22c4355e48) @ 0x7f22c491a2e8>
<joolean>guix build: error: build failed: substituter `substitute' died unexpectedly
<methalo_>i think the error is in the package definition
<methalo_>try build the package with original version
<methalo_>./pre-inst-env guix build mypkgscm --no-substitutes
<joolean>Hmmm. I don't think that's it - I tried that earlier today and after several hours it died with another error.
<joolean>But I can do it again, I suppose.
<methalo_>can you post the definition i will try run in my env
<joolean>I've stashed my changes so that I'm doing a clean build of exactly what's on the HEAD of master and I have the same problem
<joolean>Can you explain what this means: ACL for archive imports seems to be uninitialized
<joolean>I think I'd like to be able to use substitutes
<joolean>(I've figured it out.)
<civodul>hey joolean
<joolean>Hey Ludovic! How are you?
<civodul>good! and you?
<civodul>good to see you here :-)
<joolean>I'm well, thanks.
<joolean>Glad to be here!
<civodul>probably you've seen in the meantime?
<joolean>Indeed I have. I should have RTFM earlier.
<civodul>heh, np :-)
<civodul>and the horrible error with #<unknown-type ... is due to the use of Guile-SSH-for-2.0 with Guile 2.2
<joolean>One thing I should mention is that I've got Guile 2.2 installed. I wonder if that's complicating things somehow.
<civodul>i added a 'guile2.2-ssh' package yesterday
<civodul>that's the one you should be using, instead of guile-ssh
<joolean>Wait, I'm confused - do you mean a guix package?
<joolean>Okay. But nothing I'm trying to build depends on guile-ssh. Or rather, I don't know what I should change
<joolean>I'm just trying to do a fresh bootstrap of Guix from within Ubuntu
<joolean>Should I be on a different branch of Guix?
<civodul>you installed Guix from source right?
<joolean>I cloned the repository
<civodul>the problem is that it's picking Guile-SSH-for-2.0
<civodul>so you need to make sure to have 'guile2.2-ssh' installed instead
<civodul>and that should be fine
<civodul>guile-ssh is used by guix-daemon for offloading support
<joolean>Okay, let me read that.
<joolean>So what do I need to change? Do I need to patch my working copy of Guix? Do I need to install that new version of guile-ssh _outside_ of Guix?
<buenouanq>I can't get Nautilus (the file manager) to obey Gnome"s psuedo tiling commands - Any ideas? is this a GuixSD error or a Gnome error?
<civodul>joolean: you need to install that new version of guile-ssh one way or another
<civodul>you can do it with "./pre-inst-env guix package -i guile2.2-ssh --no-build-hook" for instance
<civodul>--no-build-hook disables offloading
<civodul>ACTION -> zZz
<joolean>civodul: Thanks! And thank you methalo_ as well.
<Corin>Hey, not sure this is the place to ask, but in terms of day-to-day usability, where's GuixSD at?
<Corin>And how many packages are currently maintained?
<Corin>Oh, nvm. Got the answer to the second.
<buenouanq>Corin: I am a normal casual computer user (i.e. not a software developer, Guix or otherwise) and have been using GuixSD as my main and only OS for the last year or so.
<buenouanq>Have had fewer problems than I ever did on SystemDebian.
<Corin>I notice there are a lot less pre-compiled packages than distros like Debian though. Only around 12%.
<buenouanq>Guix is about software freedom - A big part of that is not blindly trusting builds and actually verifying them yourself.
<buenouanq>It's all automated though, you really won't even notice.
<thomassgn>I've set up my .config/guix/latest link to point to a git repo to hack on packages and services, but now evrytime I call a guix command from bash it compiles a lot of guile files to my cache. Can I either: compile them like guix pull does (preferred); or set some variable to make it be compiled only once or some such?
<thomassgn>the git repo is a clone of savannah's guix repo
***Piece_Maker is now known as Acou_Bass
<lfam>thomassgn: You have a couple options. You could just go to the source directory and run `make`. You could use `git archive` to make a tarball that you pass to `guix pull --url`.
<brendyn>amz3: amz3` Did you end up managing to build GNUnet from git?
<baconicsynergy>hello beautiful people :)
<baconicsynergy>It's been a while since I've guixed. Anything cool and exciting happening lately?
<buenouanq>no excitement
<buenouanq>just boring stability
<buenouanq>if only we'd chosen a less beautiful package manager/os
<brendyn>buenouanq / baconicsynergy , Would you mind testing `guix build serf' for me? It fails for me due to some openssl tests/
<brendyn>Ok so now it just found a substitute ^.^
<baconicsynergy>brendarn: I need to reinstall guix :) I think I'll spin up a vm pretty soon
<brendarn>How can I find out why a paticular package is being built? I run `guix build serf --check' and then emacs-minimal gets download. Why? I run `guix graph serf --type=bag-with-origins|grep emacs
<brendarn>', and it is not there.
<brendarn>Trying to build gnunet-gtk but it can't find gtk+ even though I have it
<efraim>With qt 5.9 on the way I don't have a lot of enthusiasm to work on 5.8
<catonano>a friend of mine gave me an account on a server he controls. It's Zimbra. Of course I can't make it work with git send-mail :-/
<snape>ACTION switched to exwm -> it's fantastic
<janneke>efraim: i appreciate that
<janneke>we need more upstream developers to adopt guix -- what's taking them so long?
<janneke>snape: exwm?
<rekado>the emacs window manager?
<drp>functional package management in the age when people are just getting into containers?
<drp>this is all magic to me so far
<snape>yes, the emacs window manger
<janneke>snape: i don't seem to have such a package?
<snape>janneke: it got packaged recently
<janneke>snape: okay, thanks!
<janneke>i switched from GNOME to stumpwm some months ago and it's pretty great
<snape>with exem, I can C-x b to firefox, which, actually, was a dream for mt
<snape>for me
<snape>s/with exem/with exwm
<snape>And it supports Extended Window Manager Hints (which ratpoison does not support)
<snape>that allows, for example, to play 0ad
<janneke>snape: that looks just great!
<janneke>drp: what do you mean?
<janneke>ACTION looked at docker yesterday and was terribly disappointed
<janneke>i thought docker was `universal binaries' or `GUB done right'
<janneke>but it looks like a non-functional version of Guix
<brendarn>So they say. Personall I came across Guix and then became interested in making distros, so I haven't looked at all these other toys
<janneke>anyone can tell me what features/advantage docker may have over Guix?
<rekado>janneke: docker is like running whatever “guix pack” produces in a separate namespace.
<rekado>janneke: the biggest advantage over Guix is that you can use it without having to package anything.
<rekado>janneke: you can use some other package manager to create the desired binary state for you.
<janneke>rekado: thanks...yes this was my impression of docker
<janneke>rekado: `without having to package anything' can seem to be a big advantage, however it has a significant downside ;-)
<drp>janneke, what I'm getting at is that the idea of containers or "super binaries" or whatever has only just started to catch on even though they've been around as ideas for decades(jails, zones)
<drp>industry inertia says we're going to have years of docker and appimage before people go for nixos/guix
<janneke>drp: ah, yes...inertia
<drp>I have been learning nixos so I could create a secure email server with all the different parts defined and containerised
<drp>but I am looking into guix, scheme all the way down seems really cool and potentially more portable
<drp>I know someone is looking at porting to Hurd, which could help if people want BSD or seL4
<janneke>several someones even, atm :-)
<roptat>is there a way to send a file to the standard input of a program run with (system) or something similar, like "foo < bar.txt" would do in bash?
<avp_>roptat: Hi! You should take a look at procedures from (ice-9 popen) module:
<avp_>roptat: You're welcome. I hope it helps.
<efraim>I don't know what happened, but shepherd passed all its tests on aarch64
<efraim>do we have a method in place for, say, building the aarch64 ghc from an x86-64 system?
<ng0>what's "license:arev" in 0ad-data?
<snape>ng0: I just answered your email
<snape>there is another bug about the license
<ng0>oh :)
<snape>I mean, another debbugs :)
<snape>I should not have done this because it's quite confusing
<ng0>okay, yes it is. I think having all in one series would've been less confusing
<ng0>I'll get the patch from there
<buenouanq>ng0: I hear you're attempting to bless us with a gnunet service?
<ng0>well since ebing clear since the end of 2015 about what needs to be done and no one picked it up and faded into forgotten grounds so that I in parallel came up with ideas almost similar to what the past GSoC discussions were about, yep. it just takes a bit longer, I hope that the last two bugs get solved and we can release a new gnunet version.
<ng0>actually I'm working on the service since september but ran into walls.
<ng0>ah, don't take it as criticism though. I was just a bit surprised when I discovered the past work in december when I talked about this with lynX
<buenouanq>I'm just glad someone capable is doing it.
<buenouanq>I see gnunet as the much needed future of the internet.
<buenouanq>I see guix as the much needed future of package management and meta os design.
<ng0>I see myself in the position of someone who integrates gnunet into systems and constructs a system around it. I'm still learning scheme, so when it comes down to the advanced parts I might or might not require either a long break to learn or some mentor.
<buenouanq>Having them work nicely together will just be fantastic.
<ng0>at least I hope I will be able to achieve what I planed without much help
<ng0>sneek: later tell snape: with the two font licenses applied 0ad works
<ng0>I think I know enough to ask the right questions though. The theory of one part, the distribution part, is planned through, twice. What comes afterwards like distributed longterm storage etc are projects entirely up to my project and not Guix specific. would be cool to end up in Guix eventually though depending on how it will be integrated if not in it's own application.
<ng0>sneek: later tell snape: btw, 0ad is pretty huge, I don't remember the total size after it is build but I hope it's small enough to not be as big as libreoffice.
<ng0>buenouanq: But I think I'm doing okay, just sometimes I have too high expectation for myself in contrast to my view on other peoples work and behavior. Having some problems 2 years after discovering a language, coming up with a plan for a system and doing too much to sit down for theory and fun often, that's okay.
<buenouanq>Well, what exactly are you trying to put together then? I was imagining just a normal service like we currently have for postgres or whatever - What you're hinting at sounds much more grand.
<ng0>yes, a normal service. but also I expect it to scale to something similar such as our dovecot service. I only had problems testing it to proof wether it's broken or wth is going on as I know my way around in gnunet configuration mostly. and furthermore it's a base requirement for the live USB system I work on
<ng0>I'm doing some more changes to the project after initial feedback I got, so in about 1.5 - 3 weeks the website should look different and have less implicit content, bugtracker existing (either at ii or at notabug), etc
<buenouanq>So it'll create the gnunet user and deal with all permissions launch at start up etc, then any other user can access gnunet through it, right?
<ng0>that's the way gnunet is intended to be set up, yes
<buenouanq>so I won't have to manually do that or run gnunet arm -s or anything anymore
<buenouanq>what is this website you mentioned?
<ng0>I found that I need to solve a bigger problem first to make the website adjust to what I see as good, so I'll use ikiwiki first.
<ng0>experimenting with solutions for this as a subproject.
<ng0>also solutions to be documented for the maintainer question, etc. "no maintainer per se" just reflects the state that I was reading into lots of approaches how to solve the role and also shows that I like to take breaks to be prepared for most possible scenarios. It's not just me, but it's still small.