--- Log opened Fri Feb 12 00:00:27 2021 00:23 < jonasschnelli> I'm getting an error during "guix pull": https://0bin.net/paste/bLX1D3+t#5Wj9Eh9XqfRGmcpfJVUB1BlhYgPfzggWuG7ZWGab3Ip 00:23 < jonasschnelli> any idea? 00:23 < gribble> https://github.com/bitcoin/bitcoin/issues/5 | Make the version number the protocol version and not the client version · Issue #5 · bitcoin/bitcoin · GitHub 00:23 < jonasschnelli> /builder for `/gnu/store/s88cz6cp4zf6qvaj7cjfc4jkhx4qs11c-guix-manual.drv' failed with exit code 1 02:48 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 02:49 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #bitcoin-builds 03:19 -!- Laverne35Rolfson [~Laverne35@static.57.1.216.95.clients.your-server.de] has joined #bitcoin-builds 03:30 -!- midnight [~midnight@unaffiliated/midnightmagic] has quit [Ping timeout: 240 seconds] 03:33 -!- midnight [~midnight@unaffiliated/midnightmagic] has joined #bitcoin-builds 04:24 < jonasschnelli> however, the guix build through ./contrib/guix/guix-build.sh works 04:47 < wumpus> when do you need to run guix pull ? 04:49 -!- Xaldafax [~Xaldafax@cpe-104-34-193-119.socal.res.rr.com] has joined #bitcoin-builds 04:50 < wumpus> it mentions it in the docs under "GUIX with time machine capabilitites" which is about updating guix to a version with time-machine capabilities, i guess mine already had that because i never needed to run that (as far as i remember) 04:51 < fanquake> Indeed. time-machine appeared in Guix 1.1.0, which was released April 2020 04:52 < fanquake> 1.2.0 has also been released since then 04:52 < wumpus> if it's only about updating ancient versions of guix it would make sense to move it to a less prominent place, and word the section like 'if you get this and this error, do this and this' 04:52 < fanquake> which I'd assume most recent builders would be using 04:52 < fanquake> There's not really a reason, and hopefully no need that anyone would need to remain stuck on an "old" version of Guix at this point 04:53 < fanquake> This section is now also dated: https://github.com/bitcoin/bitcoin/tree/master/contrib/guix#when-will-guix-be-packaged-in-debian 04:54 < fanquake> as a Guix package is currently available in Debian Sid 04:55 < wumpus> good point-the doc could use some updating 04:55 < wumpus> thinking of switching my guix VM to debian and trying that 04:57 < fanquake> What are you using at the moment? 04:57 < fanquake> I have been using Alpine 04:59 < wumpus> i am currently using an ubuntu focal bare cloud image, with guix installed using the vanilla guix-install.sh 05:00 < fanquake> Good that there is some diversity in where Guix is being run 05:02 < wumpus> looks like hirsute (ubuntu 21.04) will have the guix package from debian 05:05 < wumpus> yes that's very good! something i still would like to try is to use a guix-the-distribution VM to build, looks like they have a qemu image for download so it shouldn't even be more work than setting up an ubuntu VM 05:08 < wumpus> but first trying to reproduce your result in https://github.com/bitcoin/bitcoin/pull/21089#issuecomment-777974133 05:09 < fanquake> ok! 05:21 < jonasschnelli> got "mkdir: cannot create directory 'unsigned': File exists" during guix (windows) 05:21 < jonasschnelli> https://0bin.net/paste/luuziQJe#PmmwR0UhjMEZ3l3LslNmEaTMHyYOZHkgNZKPDRKiMkH 05:21 < jonasschnelli> (it was a new git HEAD though) 05:21 < wumpus> jonasschnelli: i had the same yesterday, your clean script needs to rm -rf 'windeploy' 05:22 < jonasschnelli> wumpus: thanks 05:23 < jonasschnelli> shouldn't that be part of guix-build.sh? 05:24 < fanquake> The script is meant to warn at the start and halt the build if your directory is not clean 05:24 < fanquake> https://github.com/bitcoin/bitcoin/blob/master/contrib/guix/guix-build.sh#L48 05:25 < fanquake> and here, for the build directories: https://github.com/bitcoin/bitcoin/blob/master/contrib/guix/guix-build.sh#L97 05:25 < fanquake> The recommended cleanup is to use: git clean -xdff --exclude='/depends/SDKs/*' 05:25 < jonasschnelli> I guix built master (successfully),.. than fetched git master again (after a merge) and invoked guix-build.sh again because I assume new git heads will not require some sort of a "clean" 05:26 < jonasschnelli> okay... sounds good 05:27 < wumpus> fanquake: i don't want to to that because that throws away also the depends downloads 05:27 < fanquake> wumpus: fair enough, in that case you could also exclude depends/sources/* 05:29 < fanquake> hopefully we can streamline/automate this even more 05:29 < wumpus> fanquake: that's a good idea 05:29 < fanquake> exactly why it's good to have lots of people testing at the moment 05:30 < wumpus> dongcarl yesterday suggested to use SOURCES_PATH=$HOME/Downloads/depends BASE_CACHE=$HOME/Downloads/depends-BASE_CACHE` to download the depends sources to somewhere else outside the git tree, this seems even better, but it needs some open PRs merged 05:32 < wumpus> I guess if we can move the SDKs to somewhere else then it's even easier 06:17 < jonasschnelli> 44m8.317s (non virtualized) for a complete guix build.... roughly 32buils per 24h. If we want that for each merge on master, I think a dedicated machine would be beneficial (or even required). 06:18 < jonasschnelli> I'll add a nighly guix build as a first step 06:35 -!- Laverne35Rolfson [~Laverne35@static.57.1.216.95.clients.your-server.de] has quit [Remote host closed the connection] 06:38 -!- Brandi33Nolan [~Brandi33N@static.57.1.216.95.clients.your-server.de] has joined #bitcoin-builds 06:45 -!- jonatack [~jon@37.169.23.248] has joined #bitcoin-builds 08:54 < luke-jr> seems like building in a Gentoo prefix would be a strict improvement over Guix 09:11 < luke-jr> ugg, it isn't even possible to simply add a SSH server to the official Guix VM image 09:21 < luke-jr> problem with Gentoo would be it'd force updates all the time 09:33 < luke-jr> hmm, I'm not sure Guix is actually gaining anything over Ubuntu at this point 09:34 < luke-jr> the VM image apparently isn't reproducible 09:34 < luke-jr> and with substitutes in play, it's just trusting binaries from the Guix project 09:35 < luke-jr> to even run a SSH server on the VM image requires over 1 GB of new substitutes to replace the shipped binaries 09:52 -!- nckx [~nckx@tobias.gr] has quit [Ping timeout: 264 seconds] 10:26 < luke-jr> I suppose I could try the Ubuntu+Guix concept, but at what point of losing supposed benefits is it no longer worth the effort? 10:35 -!- nckx [~nckx@tobias.gr] has joined #bitcoin-builds 10:39 -!- jonatack [~jon@37.169.23.248] has quit [Ping timeout: 256 seconds] 10:41 -!- jonatack [jon@gateway/vpn/airvpn/jonatack] has joined #bitcoin-builds 10:42 < luke-jr> dongcarl: Fetching 3efb201881e7a76a21e0554906cf306432539cef.tar.gz from https://github.com/tpoechtrager/apple-libtapi/archive 10:42 < luke-jr> why does a non-OSX target do this? 10:51 -!- jonatack [jon@gateway/vpn/airvpn/jonatack] has quit [Ping timeout: 240 seconds] 10:53 < luke-jr> what is this? Updating channel 'guix' from Git repository at 'https://github.com/dongcarl/guix.git'… 10:53 -!- jonatack [~jon@37.169.23.248] has joined #bitcoin-builds 11:50 < wumpus> i'm also building the guix build on a guix VM 11:51 < wumpus> yes it would be nice if they had a server image that had ssh enabled instead of the desktop environment 12:08 < wumpus> also the UEFI partition being at the end of the image makes it harder to resize it 12:36 < luke-jr> wumpus: guix dev suggests a bug report for that one 12:41 -!- Brandi33Nolan [~Brandi33N@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 256 seconds] 13:19 -!- jonatack [~jon@37.169.23.248] has quit [Read error: Connection reset by peer] 13:21 -!- jonatack [~jon@37.169.23.248] has joined #bitcoin-builds 13:26 < wumpus> trying to switch to a more minimal config.scm gives me "service 'file-system-/dev/pts' requires 'udev', which is not provided by any service", cannot find that error anywhere online 13:37 < wumpus> it looks like 'desktop' indirectly imports that but i have no idea how, and without desktop it apparently doesn't even have a base service like that, this is frustrating 13:47 < wumpus> so yes i'd definitely recommmend installing guix on top of some other OS, not using it as OS :-) 14:05 < wumpus> oh, problem was that i forgot to append %base-services to services, go LISP 14:35 < luke-jr> wumpus: what exactly do we hope to gain from Guix at this point? >_< 14:37 < wumpus> the possibility to run the build for the distributed binaries on different linux distros 14:37 < wumpus> anyhow don't really feel like arguing this every time 14:38 < luke-jr> it's not running on different distros any more than gitian already is.. 14:40 < luke-jr> all Guix is doing is running *their* distro in a container 14:42 < wumpus> and it is easier to fully bootstrap from source than ubuntu (still not easy, but ok, that is expected to improve in the future) 14:43 < luke-jr> it's *impossible* to fully bootstrap from source. 14:43 < wumpus> building in different environments instead of everyone depending on ubuntu's binary packages provides somewhat more assurance, it's less of a single point of failure 14:44 < copumpkin> it seems like this could be avoided by a nice "guix for bitcoin FAQ" :) there are lots of nice benefits to the build model (IMO, but I'm biased) even outside of reproducibility but lots of people will have these questions 14:44 < luke-jr> I suspect it's a pain to do so for Ubuntu, but probably possible 14:44 < wumpus> no, that is not impossible 14:44 < luke-jr> wumpus: Guix's packages seem to be no better than Ubuntu's 14:45 < luke-jr> wumpus: I have been trying for days, and tried for days last year too. If it is possible, nobody has managed to make it practical. 14:45 < wumpus> luke-jr: it needs to be done but it is just not our priority right now for 0.22 14:45 < wumpus> first step is to have guix on the same level as ubuntu-based builds, then we can look into the bootstrapping from source stuff 14:46 < wumpus> you're just demanding too much to be done at once and keep repeating exactly the same every time honestly it's tiring 14:46 < luke-jr> I've tried to like Guix, I really have. But I am _this_ close to a Concept NACK. :/ 14:46 < wumpus> go ahead, you're the only one pushing back against this, you can keep building knots with gitian if you want 14:47 < wumpus> we've been working on this for what, years now? it's not going to stop because you have trouble with building some packages 14:47 < luke-jr> I'm not asking it to stop 14:48 < luke-jr> point is that it isn't ready to replace gitian, nor even Ubuntu 14:48 < wumpus> for us it is 14:53 < luke-jr> bleh: x86_64-linux-gnu-g++: fatal error: Killed signal terminated program cc1plus 14:53 < luke-jr> probably OOM 14:58 < wumpus> usually 15:50 -!- jonatack_ [~jon@37.166.60.165] has joined #bitcoin-builds 15:53 -!- jonatack [~jon@37.169.23.248] has quit [Ping timeout: 240 seconds] 17:01 < luke-jr> {standard input}:5578685: Error: unknown pseudo-op: `.llst13988' 17:02 < luke-jr> nm, apparently another OOM 17:03 < luke-jr> though this time I was using the same memory/jobs as gitian, so this indicates guix is requiring more memory too 17:04 < luke-jr> there's no way to resume the build? it has to go start over from x86-64? :/ 18:16 < dongcarl> jonasschnelli: Please feel free to reach out to me for any help at all! 18:17 * dongcarl will take a look at all the convo next week. Trying to take the weekend off properly this time... 19:36 -!- jonatack_ [~jon@37.166.60.165] has quit [Ping timeout: 246 seconds] 20:47 -!- darwix [~yeg@S01061cabc0a5ae33.ed.shawcable.net] has joined #bitcoin-builds 21:06 -!- Xaldafax [~Xaldafax@cpe-104-34-193-119.socal.res.rr.com] has quit [Quit: Bye...] 22:29 -!- darwix [~yeg@S01061cabc0a5ae33.ed.shawcable.net] has quit [Ping timeout: 264 seconds] 22:53 -!- darwix [~darwix@S01061cabc0a5ae33.ed.shawcable.net] has joined #bitcoin-builds 23:09 -!- darwix [~darwix@S01061cabc0a5ae33.ed.shawcable.net] has quit [Remote host closed the connection] --- Log closed Sat Feb 13 00:00:28 2021