| *** petefoth_ has joined #baserock | 04:36 | |
| *** petefoth has quit IRC | 04:37 | |
| *** petefoth_ is now known as petefoth | 04:37 | |
| *** persia_ has quit IRC | 04:44 | |
| *** persia_ has joined #baserock | 04:45 | |
| *** petefoth has quit IRC | 05:05 | |
| *** mike has joined #baserock | 06:10 | |
| *** mike is now known as Guest58619 | 06:11 | |
| *** petefoth has joined #baserock | 06:28 | |
| *** franred has joined #baserock | 07:16 | |
| *** Albert has joined #baserock | 07:40 | |
| *** jonathanmaw has joined #baserock | 07:51 | |
| *** mdunford has joined #baserock | 07:57 | |
| *** gary_perkins has joined #baserock | 07:57 | |
| *** tiagogomes has joined #baserock | 08:02 | |
| *** bashrc_ has joined #baserock | 08:04 | |
| *** rdale has joined #baserock | 08:06 | |
| *** ssam2 has joined #baserock | 08:49 | |
| *** ChanServ sets mode: +v ssam2 | 08:49 | |
| *** CTtpollard has joined #baserock | 08:51 | |
| *** Krin has joined #baserock | 08:52 | |
| richard_maw | Does anyone have time to look at some BSP patches? | 08:55 |
|---|---|---|
| richard_maw | I submitted the BSP stuff we needed for OpenStack as https://gerrit.baserock.org/#/q/status:open+project:baserock/baserock/definitions+branch:master+topic:openstack-bsp | 08:57 |
| *** edcragg has joined #baserock | 08:58 | |
| richard_maw | don't worry about the merge conflicts, it's from gerrit not handling patch series' particularly nicely | 08:58 |
| richard_maw | the merge conflicts should go away if it's merged in dependency order | 08:58 |
| * straycat thought it was due to IPV6 being after those patches were created | 08:59 | |
| straycat | *being enabled | 08:59 |
| * richard_maw has the ability to +2 and merge them through, but would much prefer extra eyes so there's other people aware of what we're up to | 08:59 | |
| * straycat assumes they've been built and tested | 09:01 | |
| richard_maw | straycat: multiple times | 09:01 |
| richard_maw | I thought I'd rebased after the IPv6 was merged, but looking at the commit times, they are close enough that it may not have happened | 09:02 |
| richard_maw | straycat: nope, definitely not the cause, I'd rebased on top of the IPV6 change | 09:04 |
| straycat | okay i didn't fetch the changes from gerrit, so it's possible i checked out the wrong thing | 09:05 |
| richard_maw | yeah, the openstack-v5-kernel branch pushed to git.baserock.org isn't the rebased version | 09:06 |
| straycat | yes i just downloaded the change from gerrit and it is based on ipv6, so i guess that's not the problem | 09:07 |
| straycat | richard_maw, okay +1'd all the things on the basis that you've already tested it and none of it looks insane, that's the best i can do really | 09:11 |
| richard_maw | edcragg's armv8 BSP patches https://gerrit.baserock.org/#/q/status:open+project:baserock/baserock/definitions+branch:master+topic:baserock/edcragg/armv8b64-definitions and https://gerrit.baserock.org/#/q/status:open+project:baserock/baserock/definitions+branch:master+topic:baserock/tiago-ed/moonshot-deployment also need more eyes | 09:13 |
| *** persia is now known as persia__ | 09:14 | |
| *** persia_ is now known as persia | 09:14 | |
| richard_maw | though I don't think all of the moonshot deployment patches are applicable, since they depend on https://gerrit.baserock.org/#/c/102/ | 09:14 |
| *** persia__ is now known as persia_ | 09:14 | |
| straycat | franred, thanks for merging my change :) | 09:15 |
| franred | straycat, no probs :) | 09:17 |
| ssam2 | richard_maw: i looked at them and was not sure whether to +1 or +2. Can +2 if you want (i don't have any reason that they shouldn't be merged) | 09:22 |
| richard_maw | ssam2: that's fine, I can +2 and merge them myself since we've got the requisite 2 +1s | 09:26 |
| *** zoli__ has joined #baserock | 09:33 | |
| persia | catching up on backscroll: qemu-user-static for armv5 on x86 is nearly entirely feature-complete, and I've previously found it a sensible way to do armv5 work (as finding fast armv5 is hard). | 09:56 |
| persia | The rule for what can be built on what is set by the linux personality features. setarch is the relevant userspace configuration tool. Not every subarch can do every other subarch, but the code in setarch is incomplete. | 09:57 |
| persia | For ARM, ARMv8 can do ARMv8 and ARMv7, but not earlier. | 09:57 |
| persia | ARMv7 can do ARMv6 and ARMv5, but not earlier | 09:57 |
| persia | ARMv6 can do at least ARMv5 and ARMv4: I don't know about earlier. | 09:58 |
| *** fay_ has quit IRC | 10:06 | |
| gary_perkins | Hi, I'm told by rdale that morph uses git:// style urls, not ssh://git@ urls. Is this by design? | 10:09 |
| *** fay_ has joined #baserock | 10:09 | |
| persia | Oh, and on qemu-user-static: if you set up your binfmts right, you can just unpack a blob and chroot() normally. | 10:10 |
| richard_maw | gary_perkins: morph uses both in different contexts | 10:10 |
| persia | gary_perkins: Yes. | 10:10 |
| richard_maw | we prefer git:// urls for reads, but you need a ssh://git@ url for writes | 10:10 |
| gary_perkins | ok, thanks for the info. It's just that we havn't setup a route for trove.codethink to be accessible for VPN users yet. So there is just an SSH proxy in place at the moment | 10:11 |
| straycat | you can also use the git@host:repo form, though morph makes some assumptions about urlparse which leads to some unexpected directory name: git@host, but it still works | 10:12 |
| straycat | https://github.com/pypa/pip/pull/2371 :( | 10:22 |
| jonathanmaw | :/ pygtk requires pygobject-2.0, which is incompatible with baserock's glib. making it use pygobject-3.0 doesn't work, since it's expecting a 'codegen' program of some kind, which pygobject-3.0 doesn't seem to provide. | 10:27 |
| franred | I want to enable python api in kmod, this is required for openstack (more specific for iscsi software). For this kmod needs cython so cython has to be moved to even core.morph or foundation.morph. Actually is in python-core. does anyone see weird to move cython to core? | 10:30 |
| jjardon | franred: is it a build or a runtime dependency? | 10:32 |
| franred | jjardon, it is a build dependency | 10:35 |
| bashrc_ | does anyone know if it's possible to check out a topic branch from gerrit? | 10:43 |
| straycat | bashrc_, if you find the number of the change on the tip of the topic branch and then use git-review -d <change number> then you'll get the entire topic | 10:44 |
| bashrc_ | ah ok, havn't used git-review yet | 10:44 |
| *** gary_perkins has quit IRC | 10:46 | |
| straycat | it does make it all a bit easier | 10:46 |
| *** gary_perkins has joined #baserock | 10:47 | |
| straycat | i'm sure you can also do that without git-review but i don't know how | 10:47 |
| jjardon | jonathanmaw: in what sense pygobject-2.0 is incompatible with baserock glib? AFAIK, There was not any api breackage in glib | 10:49 |
| persia | Without git-review, one fetches the specific ref from gerrit, and then checks out FETCH_HEAD, which includes the parents, etc. | 10:52 |
| persia | Using git-review is much easier. | 10:52 |
| ssam2 | mason is red, but I've cleaned up lots of disk space on cache.baserock.org so it should go green again | 11:02 |
| pedroalvarez | straycat: some days late but: pong | 11:07 |
| straycat | pedroalvarez, hey :) | 11:13 |
| *** flatmush has quit IRC | 11:14 | |
| *** flatmush has joined #baserock | 11:27 | |
| *** zoli__ has quit IRC | 11:29 | |
| *** zoli___ has joined #baserock | 11:29 | |
| ratmice__ | ssam2: agree that ldconfig error is harmless, its actually the one which doesn't get the error that concerns me, which would seem to mean either ldconfig isn't being run, or is scanning the wrong directories, or? | 11:30 |
| *** zoli___ has quit IRC | 11:32 | |
| jjardon | franred: if its a kmod dependency, I think move it to core is fine | 11:32 |
| franred | jjardon, Im currently writing the patch for this :) | 11:33 |
| jonathanmaw | jjardon: full build failure log: http://paste.baserock.org/uloxojacok a whole lot of stuff is apparently deprecated | 11:51 |
| jonathanmaw | but those are just warnings, the actual errors appear to be the "could not write function" lines. | 11:51 |
| *** nowster has joined #baserock | 11:53 | |
| nowster | "The site baserock.branchable.com is not here yet." Is that something I should be concerned about? | 11:54 |
| *** zoli__ has joined #baserock | 11:55 | |
| pedroalvarez | nowster: is not loading for you? | 11:55 |
| nowster | nope | 11:55 |
| nowster | This is editing the wiki | 11:55 |
| pedroalvarez | ah | 11:55 |
| nowster | OpenID moans about Branchable's OpenID policy, too. | 11:56 |
| ssam2 | ratmice__: I'm pretty sure the warning does happen, it just gets logged into a file rather than to the console | 11:56 |
| jjardon | jonathanmaw: what branch/tag are you trying to compile? pygobject-2-28 branch builds fine here (latest glib, but not a baserock system) | 11:59 |
| nowster | Has the procedure for updating the wiki changed? | 12:17 |
| ratmice__ | ssam2: ahh, i was assuming that was a part of a diff between logfiles | 12:17 |
| ssam2 | ratmice__: ok! the situation is two different build tools, so it's probably just a case of the logfiles being arranged differently or something | 12:18 |
| ssam2 | nowster: the procedure is 'do it', as far as I know | 12:18 |
| nowster | ssam2: in that case, the sign in may be broken | 12:18 |
| nowster | I can neither log in to edit using either Google or OpenID. | 12:19 |
| ssam2 | nowster: hmm. I get an error when using http://openid.baserock.org/ | 12:19 |
| ssam2 | that used to work, so I think Branchable have broken something | 12:20 |
| ssam2 | yes, using my StackOverflow OpenID also fails | 12:20 |
| ssam2 | I can file an issue with Branchable after lunch, if nobody beats me to it | 12:21 |
| ssam2 | we don't host the wiki, so there's not much else I can do | 12:21 |
| jonathanmaw | jjardon: I'm using tag PYGOBJECT_2_28_6 | 12:26 |
| jonathanmaw | I'll try the branch to see if it's different. | 12:26 |
| jonathanmaw | jjardon: that branch worked. | 12:34 |
| jjardon | jonathanmaw: \o/ | 12:34 |
| * petefoth is trying to make the words 'Disambiguate definitions' fit the tune a d rhythm of 'Accentuate the positive' https://www.youtube.com/watch?v=fZUmAbi0Vm4 | 13:04 | |
| *** Albert has quit IRC | 13:27 | |
| ssam2 | is anyone still having an issue logging in to baserock.branchable.com ? I find that in firefox I get the ' The site baserock.branchable.com is not here yet.' error, but in Epiphany I can log in fine | 13:28 |
| ssam2 | so maybe the problem is fixed but my cache is stale | 13:28 |
| pedroalvarez | just logged in without problem | 13:31 |
| *** mdunford has quit IRC | 13:33 | |
| *** Albert has joined #baserock | 13:33 | |
| *** Albert has joined #baserock | 13:33 | |
| *** mdunford has joined #baserock | 13:47 | |
| *** mdunford has quit IRC | 13:54 | |
| *** mdunford has joined #baserock | 14:00 | |
| straycat | oh cool all the openstack bsp stuff got merged | 14:01 |
| *** gary_perkins_ has joined #baserock | 14:09 | |
| *** gary_perkins has quit IRC | 14:10 | |
| straycat | what's the url for the ci? | 14:11 |
| petefoth | straycat: https://mason-x86-64.baserock.org/ ? | 14:22 |
| ssam2 | I think the login problems on wiki.baserock.org are https:// related | 14:35 |
| ssam2 | perhaps we need to send them our certificate: https://www.branchable.com/tips/using_https/ | 14:36 |
| straycat | petefoth, thanks! | 14:36 |
| straycat | oh it's red | 14:36 |
| petefoth | Yes but the last error was 5 hours ago, which could mean it has been building without error for 5 hours | 14:38 |
| straycat | oh right | 14:40 |
| nowster | ssam2: "HTTPS Everywhere" strikes again | 14:43 |
| straycat | petefoth, seems to be failing to build stage2-gcc | 14:45 |
| * petefoth withdraws, having reached the limit of his knowledge of Baserock CI | 14:46 | |
| straycat | petefoth, unless it's silently building something else | 14:46 |
| straycat | i don | 14:46 |
| straycat | 't know, | 14:46 |
| pedroalvarez | straycat: CI is currently building sed | 14:47 |
| pedroalvarez | well, now cython | 14:47 |
| petefoth | straycat: someone hels may have a better ideaopf how to a: view and b: interpret the log from the current build. | 14:47 |
| straycat | oh, i couldn't see that | 14:47 |
| pedroalvarez | not possible to see that without access to the VM | 14:48 |
| straycat | ahhh! | 14:48 |
| * petefoth thinks he should write somethign about how to check on the progress of Baserock CI (but has not idea what to write) | 14:49 | |
| paulsherwood | petefoth: code? :-) | 14:50 |
| straycat | it would be nice if it showed the current build in progress | 14:50 |
| petefoth | paulsherwood: :) Don't be silly! | 14:50 |
| ssam2 | it'd be much better if it showed what it was currently doing. I don't think anyone is working on Mason right now though | 14:51 |
| ssam2 | there is a V2 version out for review, which I hope to deploy at some version to try out | 14:52 |
| ssam2 | but that version doesn't have any kind of 'now building' status page either, it just sets Verified+1 or Verified-1 in Gerrit once it completes | 14:52 |
| * paulsherwood wonders if he's the only one that finds it harder to contribute to reviews now gerrit is in place | 14:53 | |
| ssam2 | I think it'd be quite annoying to not know what the Mason is currently doing | 14:53 |
| ssam2 | paulsherwood: how do you find it harder? | 14:53 |
| paulsherwood | ssam2: i go to any gerrit web page, glaze over, and give up | 14:53 |
| * straycat actually finds it much easier | 14:53 | |
| paulsherwood | ssam2: on mails, i knew where i was | 14:53 |
| straycat | i've been doing reviews inbetween tasks | 14:54 |
| ssam2 | paulsherwood: is that because the commits are at the bottom, and all in small text? | 14:54 |
| ssam2 | *comments, not commits | 14:54 |
| paulsherwood | straycat: yes, but you had to go through an epiphany to get there... that hasn't happened for me yet :) | 14:54 |
| straycat | paulsherwood, true :) | 14:54 |
| *** mdunford has quit IRC | 14:54 | |
| paulsherwood | ssam2: it's because gerrit's web ui ****ing s**ks big cows **** and i don't care who knows that i think that :) | 14:55 |
| paulsherwood | oops :-) | 14:55 |
| ssam2 | i think ':)' is becoming overused | 14:55 |
| paulsherwood | only by me | 14:55 |
| straycat | though, to be fair, i am basically going to stop making series and just stick to individual changes, because series > 3 are a bit annoying to review with it imo | 14:55 |
| ssam2 | I think high level discussion should still happen on the mailing list | 14:56 |
| bashrc_ | the gerrit UI makes pandas sad | 14:56 |
| straycat | bashrc_, it has vim keys though! | 14:56 |
| ssam2 | code reviews in gerrit, but discussions of new features, big changes etc. on the mailing list first (or, with a link to the patch sets) | 14:56 |
| * bashrc_ doesn't use vim | 14:56 | |
| straycat | they even added visual selection | 14:56 |
| straycat | bashrc_, ahh i guess that's where you're going wrong :p | 14:57 |
| jmacs | There are several non-vi users here | 14:57 |
| ssam2 | straycat: they added visual selection, but they broke regular copy and paste in the process! | 14:57 |
| straycat | ssam2, ahh well, can't have everything >.> | 14:58 |
| straycat | :p | 14:58 |
| straycat | it's definitely much nicer to use with some of keyboard shortcuts | 14:59 |
| straycat | you can hit '?' to get those | 14:59 |
| *** mdunford has joined #baserock | 15:10 | |
| bashrc_ | is git-review going to be in build-essential? | 15:41 |
| ssam2 | it's in one of the strata already,. but I forget which | 15:41 |
| ssam2 | build-essential is for the toolchain, so it wouldn't be that one | 15:42 |
| persia | If it isn't in devel, it ought be. | 15:46 |
| persia | But I don't know which is the right strata to choose for that. | 15:46 |
| ssam2 | it's in devel already | 15:51 |
| straycat | should be in devtools | 15:51 |
| ssam2 | in devtools, indeed | 15:51 |
| persia | There we go then :) | 15:52 |
| ssam2 | seems that Qt 5's configure script doesn't respond to SIGKILL | 16:02 |
| ssam2 | this has turned up several pretty major bugs in distbuild | 16:03 |
| ssam2 | or rather, it responds to SIGKILL, but the subprocesses that it started keep running regardless | 16:04 |
| straycat | i was about to say... | 16:04 |
| straycat | if that's cancelling, i would guess there's an assumption that after kill's been issues it's not still building :( | 16:07 |
| straycat | *issued | 16:07 |
| * richard_maw harrumphs, as the only way he knows of to reliably kill everything when you want to cancel a build involves cgroups, either directly (which may possibly be removed), or via systemd, which introduces an extra runtime dependency | 16:10 | |
| richard_maw | which would make it difficult to run in a chroot | 16:10 |
| richard_maw | you'd have to go full container | 16:11 |
| ssam2 | it seems I could create a process group | 16:11 |
| ssam2 | I've not tried that yet though | 16:11 |
| ssam2 | and yes, there's an assumption that a build stops as soon as .kill() is called | 16:11 |
| straycat | sorry, seemed like a reasonable assumption when i wrote that :/ | 16:12 |
| richard_maw | conversely waiting for it to exit is also problematic | 16:12 |
| richard_maw | as the only way I know of for getting an asynchronous notification when a process exits is with a pipe trick, and that requires the subprocess to behave | 16:14 |
| richard_maw | only in last week's lwn.net was there a discussion on a patch series that proposed to fix this by giving you a FD when you clone to start the new process, which you could select on | 16:15 |
| ssam2 | at least I can reproduce the bug with 4 lines of shell. Anything can be fixed if you have a testcase. | 16:17 |
| ssam2 | http://ptspts.blogspot.co.uk/2012/11/how-to-start-and-kill-unix-process-tree.html seems promising for killing the whole tree | 16:18 |
| ssam2 | (the second example) | 16:18 |
| franred | ssam2, I did something like that in bash, the only problem I found was if the process call other processes and they do not belongs to the group you won't kill these ones | 16:22 |
| ssam2 | oh, do forked subprocesses not get implicitly included in the group? in that case, i guess this won't work | 16:24 |
| * richard_maw wonders how setsid() factors into process hierarchy stuff | 16:25 | |
| ssam2 | the article does say 'All descendant processes of the child will be added to this process group.' | 16:25 |
| franred | ssam2, I imagine children will belong to the group but exec processes wont? | 16:31 |
| ssam2 | any idea how I might test that? if I 'exec sh -c "sleep 10; echo HELLO"' in a shell program, you expect the shell won't be killed if I kill the whole process group? | 16:32 |
| franred | ssam2, check the GPID of the sleep or if it is in the process tree? | 16:33 |
| ssam2 | i'll try that | 16:35 |
| richard_maw | ssam2: AIUI the traditional unix API way to do this would be to have the builder call setpgrp before execve, which creates a new process group with the same ID as the pid of the new process, and then use kill(-pid) to kill that process group | 16:56 |
| *** Guest58619 has quit IRC | 17:04 | |
| *** bashrc_ has quit IRC | 17:05 | |
| *** jonathanmaw has quit IRC | 17:05 | |
| *** edcragg has quit IRC | 17:05 | |
| *** zoli__ has quit IRC | 17:06 | |
| *** zoli__ has joined #baserock | 17:09 | |
| *** Zara has quit IRC | 18:07 | |
| *** perryl has quit IRC | 18:07 | |
| *** pdar has quit IRC | 18:07 | |
| *** jmacs has quit IRC | 18:07 | |
| *** kejiahu has quit IRC | 18:07 | |
| *** wdutch has quit IRC | 18:07 | |
| *** benbrown_ has quit IRC | 18:07 | |
| *** paulsherwood has quit IRC | 18:07 | |
| *** SotK has quit IRC | 18:07 | |
| *** bwh has quit IRC | 18:07 | |
| *** petefotheringham has quit IRC | 18:07 | |
| *** DavePage has quit IRC | 18:07 | |
| *** bwh has joined #baserock | 18:09 | |
| *** petefotheringham has joined #baserock | 18:09 | |
| *** rdale has quit IRC | 18:11 | |
| straycat | ssam2, does ^C not cancel anymore in distbuild? | 18:16 |
| ssam2 | should do | 18:17 |
| *** zoli___ has joined #baserock | 18:18 | |
| ssam2 | keep in mind tyrell may be running random code, as it's been being used for development by SotK and perryl | 18:18 |
| straycat | ahh good point | 18:19 |
| *** zoli__ has quit IRC | 18:21 | |
| *** gary_perkins_ has quit IRC | 18:30 | |
| *** pdar has joined #baserock | 18:33 | |
| *** franred has quit IRC | 18:37 | |
| *** zoli___ has quit IRC | 19:22 | |
| *** Albert has quit IRC | 19:46 | |
| *** ssam2 has quit IRC | 20:09 | |
| *** paulsherwood has joined #baserock | 20:57 | |
| jjardon | How do you feel about using systemd firstboot to setup root password/locales/timezone... ? | 21:03 |
| jjardon | I just discovered it recently | 21:04 |
| *** ratmice__ has quit IRC | 21:05 | |
| persia | As long as there are no changes that make it mandatory, I'm fine with it. I still hold out hope of supporting non-systemd linux (and non-linux for that matter). | 21:16 |
| *** ratmice__ has joined #baserock | 22:04 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!