| *** inara has quit IRC | 04:04 | |
| *** inara has joined #baserock | 04:11 | |
| *** inara has quit IRC | 04:27 | |
| *** zoli__ has joined #baserock | 05:53 | |
| *** zoli__ has quit IRC | 05:54 | |
| *** zoli__ has joined #baserock | 05:58 | |
| *** inara has joined #baserock | 06:03 | |
| *** inara has quit IRC | 06:13 | |
| *** inara has joined #baserock | 06:24 | |
| *** zoli__ has quit IRC | 06:30 | |
| *** inara has quit IRC | 06:37 | |
| *** inara has joined #baserock | 06:38 | |
| *** zoli__ has joined #baserock | 06:47 | |
| *** zoli__ has quit IRC | 06:49 | |
| *** zoli__ has joined #baserock | 06:57 | |
| *** zoli__ has quit IRC | 07:20 | |
| *** zoli__ has joined #baserock | 07:46 | |
| *** zoli__ has quit IRC | 08:06 | |
| *** grahamfinney_ has joined #baserock | 08:16 | |
| *** grahamfinney has joined #baserock | 08:16 | |
| *** grahamfinney_ has quit IRC | 08:18 | |
| *** grahamfinney has quit IRC | 08:18 | |
| *** grahamfinney_ has joined #baserock | 08:19 | |
| *** grahamfinney has joined #baserock | 08:19 | |
| *** mariaderidder has joined #baserock | 08:21 | |
| *** CTtpollard has joined #baserock | 08:30 | |
| *** franred has joined #baserock | 08:35 | |
| *** ssam2 has joined #baserock | 08:52 | |
| *** ChanServ sets mode: +v ssam2 | 08:52 | |
| *** bashrc has joined #baserock | 09:03 | |
| ssam2 | i'm a bit worried that 2 stories on https://storyboard.baserock.org/ show up as being created by me, even though they weren't. | 09:04 |
|---|---|---|
| mwilliams_ct | which stories ssam2 ? | 09:05 |
| ssam2 | the only ones | 09:05 |
| ssam2 | https://storyboard.baserock.org/#!/story/1 and https://storyboard.baserock.org/#!/story/2 | 09:05 |
| ssam2 | i'm sure paul created them (since he told me he had created some stories, and those are the only ones) | 09:05 |
| mwilliams_ct | could he have done it on your laptop? If not, maybe CTtpollard can help, I know he's worked on Storyboard a bit | 09:06 |
| radiofree | Those links don't work on Firefox mobile | 09:06 |
| ssam2 | radiofree: interesting. they don't work for me either unless I enable Javascript | 09:06 |
| ssam2 | so maybe it's Javascript-related | 09:07 |
| radiofree | Might be certificate related! | 09:07 |
| ssam2 | the certificate is just some self-signed one I generated, yeah | 09:07 |
| radiofree | Managed to get it to show the "not trusted" page now | 09:08 |
| * radiofree doesn't trust storyboard, so will go no further | 09:08 | |
| *** edcragg has joined #baserock | 09:08 | |
| ssam2 | radiofree: I don't think it means you any harm | 09:08 |
| CTtpollard | I never saw it relate posts to the wrong user | 09:08 |
| ssam2 | ok. could be a problem in the OpenID provider then | 09:09 |
| mwilliams_ct | ssam2: also, logging in I get "The site https://storyboard.baserock.org has requested verification of your OpenID. I have failed to reach it and thus cannot vouch for its authenticity. Perhaps it is on your local network." -- maybe timeout or something, but it's not an ideal error description | 09:09 |
| mwilliams_ct | also, those stories now appear to have been created by me! | 09:10 |
| *** rdale has joined #baserock | 09:10 | |
| ssam2 | mwilliams_ct: about the warning: see story #2 ;) | 09:10 |
| ssam2 | very interesting that they show as being yours though. | 09:10 |
| mwilliams_ct | hehe sorry | 09:10 |
| ssam2 | they show up as yours for me too | 09:11 |
| mwilliams_ct | But then since I'm listed as having reported it clearly I knew that ;) | 09:11 |
| ssam2 | this is weird. | 09:11 |
| CTtpollard | I presume it's associating the current http remote user as story creator | 09:11 |
| ssam2 | I'm wondering if it somehow gets the same OpenID URL for all of us | 09:12 |
| petefoth | IS there / will there be any link to the OpenId provider from w.b.o? | 09:12 |
| ssam2 | petefoth: might make sense, yeah | 09:13 |
| petefoth | ssam2: I would add such a link, but I have no idea where the OpenID provider lives :) | 09:13 |
| ssam2 | http://openid.baserock.org/ | 09:14 |
| ssam2 | the 'users' table in Storyboard has only one entry which is mwilliams_ct. And it has your OpenID as http://specs.openid.net/auth/2.0/identifier_select | 09:14 |
| ssam2 | so I guess it's somehow getting the same OpenID for all of us. I must have configured it wrong | 09:14 |
| mwilliams_ct | Yeah that sounds like a bug in the openID provider. is there any source code for that I can look at? | 09:15 |
| * pedroalvarez logs in storyboard to see what happens | 09:15 | |
| pedroalvarez | yay! I'm the stories creator now | 09:15 |
| ssam2 | mwilliams_ct: https://github.com/ssssam/test-baserock-infrastructure/tree/master/baserock_openid_provider | 09:15 |
| mwilliams_ct | pedroalvarez: congrats! | 09:15 |
| mwilliams_ct | thanks ssam2 | 09:15 |
| pedroalvarez | can anybody log in using a different openid? | 09:16 |
| ssam2 | no, storyboard ties you to one openid provider | 09:16 |
| ssam2 | we could point it to e.g. launchpad | 09:16 |
| ssam2 | but then we'd be tied to launchpad | 09:16 |
| petefoth | at the meetup it was suggested that we should modify StoryBoard to support any OpneID provider, but I guess that will be some way off | 09:18 |
| *** jonathanmaw has joined #baserock | 09:18 | |
| ssam2 | we do have some people at Codethink who are familiar with the Storyboard codebase, I think | 09:18 |
| petefoth | We can investigate how we go about asking them to have a look at this issue | 09:20 |
| *** tiagogomes_ has joined #baserock | 09:20 | |
| paulsherwood | mwilliams_ct: didn't you look at that earlier? | 09:20 |
| mwilliams_ct | paulsherwood: petefoth: Yes, we looked briefly into having multiple openID providers in previous work I did. From memory, it was concluded that it was a lot of effort for not much reward on our part (though I think upstream would be grateful for it, though they'd be unlikely to use it themselves) | 09:21 |
| petefoth | the 'reward' would be for Baserock, which would then have a defect and story tracker which can be used by anyone without having to register with openid.baserock.org/ | 09:24 |
| radiofree | What is baserock using storyboard for? | 09:26 |
| mwilliams_ct | petefoth: sure, but when I said reward I meant relative to what we were doing at the time, not to Baserock - apologies for being unclear | 09:27 |
| ssam2 | radiofree: we want an issue tracker and task tracker | 09:27 |
| persia | radiofree: To report problems with morph, lorry-controller, lorry-minions, system-version-manager, definitions, infrastructure definitions, etc. | 09:27 |
| paulsherwood | radiofree: issue logging, for example, since yesterday i think | 09:27 |
| petefoth | mwilliams_ct: I did understand :) | 09:27 |
| radiofree | Does storyboard email you now? | 09:28 |
| CTtpollard | radiofree: no | 09:28 |
| radiofree | So you're just expected to constantly refresh? | 09:29 |
| radiofree | What about attachments? | 09:29 |
| CTtpollard | they're working on email, but for the time being yes | 09:29 |
| ssam2 | radiofree: out of interest, how do you feel about Trac ? | 09:29 |
| radiofree | ssam2: it's better than storyboard | 09:30 |
| CTtpollard | These are the current patches in jenkins https://review.openstack.org/#/q/project:openstack-infra/storyboard,n,z | 09:30 |
| CTtpollard | *gerrit sorry | 09:31 |
| petefoth | Mention of Trac in the meetup summary session caused robtaylor to cry out in anguiush - 'Nooooooo!'' was what he said iirc :) | 09:31 |
| CTtpollard | There's email patches up for review | 09:31 |
| petefoth | Can we have a defect tracker war now? ;) | 09:31 |
| ssam2 | eventually we'll get to using Bugzilla like everyone else. But we can spend more time setting up new instances of different things for a while yet. | 09:32 |
| Kinnison | petefoth: Trac often invokes horror in people, but it's actually a fairly competent project organisation system -- it kinda wants to take over your world though which is likely why robtaylor didn't like the idea | 09:32 |
| radiofree | I didn't say it was good, I said it was better than storyboard | 09:32 |
| paulsherwood | petefoth: if you want. in the meantime, i've logged a couple of things in storyboard | 09:32 |
| * paulsherwood has better things to do than participate in wars | 09:32 | |
| Kinnison | ssam2: It is indeed a sorry indication of the state of the defect/issue tracking world that people still misuse a bug tracker for it in preference to the dedicated solutions | 09:32 |
| Kinnison | ssam2: But I fear you may be right | 09:32 |
| petefoth | paulsherwood: I really *don't* want! Yesterday's 'decision' was storyboard | 09:33 |
| * Kinnison makes some peas for paulsherwood | 09:33 | |
| paulsherwood | whirled peas? please? can we have whirled peas? | 09:33 |
| Kinnison | sure | 09:34 |
| * Kinnison spins 'em around | 09:34 | |
| * petefoth is now the author of the two storyboard stories :) How long will that last? | 09:36 | |
| ssam2 | til someone else logs in, sadly | 09:36 |
| ssam2 | i'm looking at that problem | 09:36 |
| petefoth | ssam2: do you think we should link to storyboard from w.b.o now, or should we wait for a few wrinkles to be ironed out? | 09:39 |
| persia | I think we should iron before hanging | 09:39 |
| ssam2 | yes | 09:39 |
| ssam2 | we should wait | 09:39 |
| petefoth | okeydokey | 09:40 |
| CTtpollard | is any of the bootstrap theme going to be changed to match w.b.o? | 09:41 |
| ssam2 | CTtpollard: what bootstrap theme? | 09:41 |
| tiagogomes_ | why do we have kexec in tools? Are we making us of it? | 09:42 |
| CTtpollard | it uses bower bootstrap for the theme, you can over ride it though | 09:44 |
| * pedroalvarez likes storyboard webpage being responsive | 09:44 | |
| ssam2 | cttpollard: storyboard does? ok. I don't have a clue about theming, personally, I'd appreciate help | 09:45 |
| ssam2 | same goes for openid.baserock.org -- I'll go crazy if I try to write a proper .css for it | 09:45 |
| CTtpollard | I've only changed stuff such as the navbar colour, storyboard icon & favicon though | 09:46 |
| CTtpollard | nothing major | 09:46 |
| persia | CTtpollard: Even changing that stuff would be lovely :) | 09:46 |
| ssam2 | cttpollard: how do you change those things? | 09:46 |
| * persia wonders if that sort of change is just a patch vs. defintions, or whether we end up forking storyboard, and then patching definitions to use the fork | 09:46 | |
| ssam2 | the current storyboard isn't cleanly deployed from the infrastructure repo | 09:47 |
| CTtpollard | how are you running the instance ssam2, via vagrant or tox+grunt? | 09:48 |
| persia | In that case, I suppose I'm wondering what that sort of change *should* be, rather than *would* be :) | 09:48 |
| *** Krin has joined #baserock | 09:48 | |
| ssam2 | persia: we can get there in stages. committing /etc/storyboard/storyboard.conf to git would be the first step, I guess | 09:48 |
| ssam2 | CTtpollard: I don't think it's using either of those things | 09:49 |
| ssam2 | I ran the puppet scripts, and then fixed up some bits that had failed to work manually | 09:49 |
| ssam2 | apache is runnig the storyboard workers | 09:49 |
| persia | ssam2: That's a sensible first step, I expect. Configuration management of declarative systems is something that probably needs more thought though, so I'm undecided if that ends up as part of a final solution. | 09:50 |
| * persia has not managed to reconcile "declarative system definition" with "ability to adjust configuration to reflect operational requirements" yet | 09:50 | |
| ssam2 | the model I've been trying in the infrastructure.git repo is to have 2 ansible scripts, one for 'image-config' and one for 'instance-config' | 09:51 |
| ssam2 | the 'instance-config' one is run *after* instantion, and can be edited and rerun whenever you want | 09:51 |
| ssam2 | it's far from perfect, but I think it's the right model | 09:52 |
| CTtpollard | I've found my instance where I changed the favicon and brand colour | 09:52 |
| *** Krin has quit IRC | 09:53 | |
| pedroalvarez | ssam2: just to add info to your debugging - storyboard thinks I'm you | 09:53 |
| *** petefotheringham has quit IRC | 09:53 | |
| *** simonh_ has quit IRC | 09:53 | |
| *** mwilliams_ct has quit IRC | 09:53 | |
| persia | That does sound like a sensible model. | 09:53 |
| *** mwilliams_ct has joined #baserock | 09:54 | |
| *** petefotheringham has joined #baserock | 09:54 | |
| ssam2 | pedroalvarez: it thinks we're all the same user, identified by http://specs.openid.net/auth/2.0/identifier_select | 09:54 |
| ssam2 | Storyboard requests that OpenID from openid.baserock.org, which is a special OpenID that means 'let the user choose what OpenID they want to use' | 09:55 |
| ssam2 | so I guess Storyboard expects the OpenID provider to return http://openid.baserock.org/openid/samthursfield but instead it returns the identifier_select URL again | 09:55 |
| pedroalvarez | good debugging | 09:56 |
| ssam2 | seems like a bug in django_openid_provider so far | 09:56 |
| petefoth | please can we have a projcet in storyboard for w.b.o? The UI / Documentation session at the meetup decided that we need some 'What I do with baserockm and how do I do it' stories. I would likie to be able to track the progess of getting those written | 09:57 |
| ssam2 | ok. what should it be called? | 09:57 |
| pedroalvarez | petefoth: "please don't spend hours filing new issues in there yet" | 09:58 |
| petefoth | ssam2: 'BAserock wikiw'? | 09:58 |
| ssam2 | unconventional, but I like it | 09:58 |
| petefoth | pedroalvarez: I won't spend hopurs, but we need to use it a bit | 09:58 |
| petefoth | ssam2: or you could spll ittt writttte | 09:59 |
| ssam2 | I now realise the bug in django_openid_provider was introduced by me. :( | 09:59 |
| ssam2 | in https://github.com/ssssam/test-baserock-infrastructure/commit/afe90669f1012c25bce416a5c21da3f92c2f07e9 in case you are curious | 10:01 |
| pedroalvarez | lines 94 95, right? | 10:02 |
| *** inara has quit IRC | 10:02 | |
| ssam2 | yeah. the reason for that was that if the user requested 'foo' and the provider returned 'foo/' it'd trigger an assertion | 10:04 |
| ssam2 | so i changed it to return whatever was requested | 10:04 |
| ssam2 | but that breaks the 'identifier_select' case. | 10:04 |
| petefoth | ssam2: looking again , I guess it should be 'baserock/wiki', or we could use the baserock/infrastructure project. Personally I would prefer it to have its own project | 10:05 |
| ssam2 | projects are cheap, baserock/wiki sounds good to me | 10:05 |
| ssam2 | or would baserock/documentation be better? | 10:06 |
| ssam2 | i guess part of the point of storyboard is you don't need 'catch-all' projects like 'documentation' though | 10:06 |
| ssam2 | since stories can span multiple projects | 10:06 |
| *** Krin has joined #baserock | 10:06 | |
| *** simonh_ has joined #baserock | 10:07 | |
| petefoth | ssam2: where would I then put stories to do wwith updating the documentation of morph? | 10:07 |
| Zara | pedroalvarez: yeah, I was worried about the maintenance side of things. One option I see is to make the tutorial very small (eg: walks through the wiki instructions from launching the baserock vm up to the end of the 'upgrade your vm to a devel vm' stage). | 10:07 |
| ssam2 | petefoth: good question. | 10:07 |
| ssam2 | I think ideally Morph's docs would live in morph.git and would be tracked in the Morph project | 10:07 |
| ssam2 | so I think tasks for morphs docs should go in baserock/morph ... | 10:07 |
| franred | that sounds sensible to me | 10:08 |
| petefoth | ssam2: agreed. I think wiki should be a separate project. Some dcoumentation stories mu=ight involve tasks in both wiki and morph | 10:08 |
| pedroalvarez | Zara: my idea (when i had it) was to start the tutorial within a "fresh baserock vm" | 10:08 |
| petefoth | the wiki is a separate entity and deserves its own project I think | 10:09 |
| ssam2 | petefoth: fair enough. i'll create baserock/wiki once I've fixed this openid provider bug | 10:09 |
| pedroalvarez | Zara: so you go through basic morph commands | 10:09 |
| ssam2 | actually, I may as well do it now | 10:09 |
| petefoth | ssam2: thank you :) | 10:10 |
| CTtpollard | I think i've tracked down the location of the icon as well | 10:11 |
| ssam2 | cool, where is it? | 10:11 |
| Zara | pedroalvarez: Ah, I see, so the tutorial would be within baserock itself, and thus easier to update? Sounds good. I'd like some way to make it simpler to set up the vm in the first place, though, because my goal here is to make it really easy for someone to quickly play around with baserock (even a skeletal version of baserock) and feel familiar with it. | 10:12 |
| CTtpollard | for the favicon and brand colour in the webclient go to /src/theme/custom and take a look at the readme | 10:13 |
| CTtpollard | for storyboard icon it's to do with /src/fonts/custom_icons | 10:14 |
| ssam2 | ok, ta | 10:14 |
| CTtpollard | which I think points to src/fonts/src/storyboard.svg | 10:15 |
| pedroalvarez | Zara: this if from the creator of that tutorial: http://blog.docker.com/2013/08/introducing-an-interactive-docker-tutorial/ | 10:15 |
| CTtpollard | @brand-primary in theme.less will let you change the top bar colour, and placing a favicon in that directory will override the default one | 10:16 |
| pedroalvarez | Zara: he says that the best option would be to create a container somewhere for every user accessing the tutorial, but he didn't do that because docker doesn't work inside of docker | 10:17 |
| ssam2 | cool. anyone have a favourite colour for the top bar? | 10:17 |
| ssam2 | i'd like to replace it with a picture of some bikes or something | 10:17 |
| ssam2 | :) | 10:18 |
| CTtpollard | :P | 10:18 |
| pedroalvarez | #002B36 | 10:20 |
| pedroalvarez | (wich is the background colour of paste.baserock.org) | 10:21 |
| Zara | pedroalvarez: does this mean that we'd need the user to get baserock running on docker, first? because (going from the wiki), that seems like it could be complicated itself. | 10:21 |
| ssam2 | baserock in Docker is simple, actually | 10:21 |
| *** lachlanmackenzie has joined #baserock | 10:21 | |
| ssam2 | cat baserock-15.02-chroot-x86_64.tar.gz | docker import - baserock/15.02 | 10:21 |
| pedroalvarez | Zara: no, the idea is that the user opens a webpage, and in that webpage he has a shellinabox (shell emulator) running accessing to a baserock instance, which behind the scenes is baserock in docker | 10:22 |
| pedroalvarez | crazy uh/ | 10:22 |
| pedroalvarez | ? | 10:22 |
| Kinnison | ssam2: ARGH, I KILL YOU | 10:22 |
| Kinnison | ssam2: Pointless use of 'cat' | 10:22 |
| ssam2 | it's not pointless. it's sending the file to docker! | 10:23 |
| Kinnison | docker import - baserock/15.02 < baserock-15.02-chroot-x86_64.tar.gz | 10:23 |
| * Kinnison also whines that docker says "URL" and then only claims to only accept URLs whose scheme == "http" | 10:24 | |
| * richard_maw is looking forward to the next systemd release, as he would be able to nspawn all this stuff | 10:25 | |
| *** bashrc has quit IRC | 10:32 | |
| *** bashrc has joined #baserock | 10:33 | |
| simonh_ | How does morph behave if there is no `build-commands` e.g. in http://paste.baserock.org/abebixizan does it do `make` and `make install` knowing it's autotools? | 10:38 |
| *** simonh_ is now known as mauricemoss_ | 10:39 | |
| Kinnison | mauricemoss_: Basically it depends on the autodetected (or specified) build system | 10:40 |
| Kinnison | mauricemoss_: it can detect (by presence of configure.{in,ac}) autotools | 10:40 |
| nowster | "build-system: autotools" | 10:41 |
| nowster | if there's only a configure-commands: stanza, the rest is defaulted? | 10:41 |
| pedroalvarez | nowster: yes, and the configure-commands would be overriding the default one | 10:42 |
| pedroalvarez | defaults are here: http://git.baserock.org/cgi-bin/cgit.cgi/baserock/baserock/morph.git/tree/morphlib/buildsystem.py | 10:42 |
| nowster | right | 10:42 |
| mauricemoss_ | Kinnison, pedroalvarez thanks! | 10:43 |
| pedroalvarez | mauricemoss_: btw, have you seen the "Native baserock for CB5-311 guide" mail in baserock-dev? | 10:44 |
| mauricemoss_ | pedroalvarez, I've seen it, figured out the issue and will reply by the end of the day. | 10:44 |
| pedroalvarez | mauricemoss_: thanks :) | 10:46 |
| Zara | pedroalvarez: I see, it sounded complicated to me, at first, but might not be complicated in practice. Where would we put the baserock-in-docker instance that the user accesses? | 10:46 |
| pedroalvarez | Zara: sounds really complicated to me :) | 10:47 |
| pedroalvarez | I'd be interested on ideas about how to implement this | 10:47 |
| Zara | Heh, if I were implementing it, I'd probably just go the docker route and tweak their JS emulator, without a real baserock instance being involved anywhere in the process, but that's mainly because I don't have the know-how to do something more complicated. But I think I'll look into Docker more, today. | 10:50 |
| pedroalvarez | I'm having problems with iptables + openstack + baserock and I wonder where would be the best place to ask | 11:12 |
| ssam2 | I've fixed the OpenID provider. Storyboard should now be able to tell people apart | 11:18 |
| ssam2 | the old user account that we wrongly shared is now called 'Storyboard Monkey' | 11:19 |
| Zara | :D | 11:19 |
| CTtpollard | :) | 11:19 |
| jjardon | tiagogomes_: hey! did you, by any chance, have time to test the automake 1.15 patch? | 11:20 |
| jjardon | I can not connect to http://storybooard.baserock.org/, known issue? | 11:25 |
| ssam2 | use https:// | 11:25 |
| ssam2 | http:// doesn't forward there, need to fix the apache config | 11:25 |
| persia | Is there a potential to autoredirect that? | 11:25 |
| persia | Ah, cool. | 11:25 |
| jjardon | ssam2: still not connecting | 11:27 |
| tiagogomes_ | jjardon in which archs have you tested so far? | 11:28 |
| jjardon | tiagogomes_: x86_64 | 11:28 |
| petefoth | jjardon: you have an extra 'o' in yiur url | 11:29 |
| jjardon | petefoth: oh, good catch! thanks! (sorry ssam2) | 11:29 |
| franred | which documentation I can read to know what is in /src/tmp/{deployments,chuncks,staging,failed} directories? | 11:29 |
| jjardon | mmm, now I can not login in http://openid.baserock.org | 11:30 |
| jjardon | "This account is inactive" | 11:31 |
| pedroalvarez | jjardon: create an account first? | 11:31 |
| jjardon | pedroalvarez: I did that | 11:31 |
| pedroalvarez | :) | 11:31 |
| pedroalvarez | that sounds like: "the account is being activated" | 11:32 |
| *** gary_perkins has joined #baserock | 11:37 | |
| *** lachlanmackenzie has quit IRC | 11:38 | |
| jjardon | pedroalvarez: any idea how much time until it gets activated? | 11:43 |
| ssam2 | jjardon: you need to click the link sent to you in an email | 11:46 |
| pedroalvarez | ssam2: oh really? is that wokring? | 11:49 |
| ssam2 | should be | 11:49 |
| pedroalvarez | that's amazing :) | 11:49 |
| ssam2 | django.registration :) | 11:49 |
| CTtpollard | all hail django | 11:50 |
| *** lachlanmackenzie has joined #baserock | 11:55 | |
| *** persia_ has quit IRC | 12:00 | |
| *** rdale_ has joined #baserock | 12:08 | |
| *** persia_ has joined #baserock | 12:12 | |
| *** persia_ has joined #baserock | 12:12 | |
| *** rdale__ has joined #baserock | 12:13 | |
| *** rdale_ has quit IRC | 12:16 | |
| *** rdale has quit IRC | 12:19 | |
| *** dabukalam has quit IRC | 12:19 | |
| *** perryl has quit IRC | 12:19 | |
| *** dabukalam has joined #baserock | 12:20 | |
| *** perryl has joined #baserock | 12:20 | |
| *** mdunford has quit IRC | 12:22 | |
| *** mdunford has joined #baserock | 12:23 | |
| *** lachlanmackenzie has quit IRC | 12:27 | |
| jjardon | I can not assign tasks in storyboard, is this a known issue? | 12:32 |
| * jjardon thinks mayb its better to report this in the storyboard instance instead ;) | 12:32 | |
| ssam2 | jjardon: hmm, i'm not sure why | 12:34 |
| ssam2 | maybe there are permissions that need to be set up | 12:35 |
| ssam2 | I'll have a look later | 12:35 |
| ssam2 | I've written descriptions for all the baserock/ repos at <http://git.baserock.org/>: could everyone check that they're sane, and that the repos I've marked as obsolete are indeed obsolete ? | 12:35 |
| *** lachlanmackenzie has joined #baserock | 12:42 | |
| Zara | they seem fine to me | 12:46 |
| jjardon | ssam2: I can assign now: it works if you press enter instead click in the pop up | 12:48 |
| jjardon | ssam2: about the repo description, Id change "Baserock Robotic Integration Engineer" for "Baserock CI/CD system" | 12:51 |
| Kinnison | firehose isn't CI?CD | 12:52 |
| Kinnison | it's a robotic integration engineer | 12:52 |
| jjardon | my misunderstanding, nevermind then | 12:53 |
| petefoth | jjardon ssam2 persia - I've created the "What *I* do with Baserock" stories on the wiki" story in storyboard, with tasks fro thoise who volunteered in yesterday's UI & Docs session https://storyboard.baserock.org/#!/story/6 | 12:53 |
| petefoth | I have also copied the text for the story in case it disappears :) | 12:54 |
| ssam2 | cool | 12:54 |
| jjardon | petefoth: assigned myself already ;) | 12:54 |
| ssam2 | I find it really bizarre how when I loaded that page in Storyboard it said 'No title' for a while, then the content appeared | 12:54 |
| radiofree | are you Storyboard Monkey petefoth | 12:54 |
| ssam2 | hmm, petefoth maybe you need to log out and back in | 12:55 |
| petefoth | radiofree: looks that way, but there'll be another ID along in a moment | 12:55 |
| ssam2 | Could you log out and log back in? You should appear as yourself then | 12:55 |
| * petefoth does as he is told, for the second time today | 12:55 | |
| ssam2 | if you still show up as 'storyboard monkey' then something is broken | 12:56 |
| jjardon | the stories have a "start" when you can "subscribe". What that really means? I will get mail notifications of changes? | 12:56 |
| ssam2 | (the story you already made will still have been created by 'storyboard monkey' but new actions should occur under your name) | 12:56 |
| petefoth | ssam2: I'm now showing up as me, the stories are still credited to Mr Monkey, which is fine by me | 12:57 |
| ssam2 | cool | 12:57 |
| petefoth | ssam2: and thanks for getting this working :) | 12:57 |
| Kinnison | paulsherwood: thank you for the writeup on declarative definitions, I have referenced it in my writeup about build/deploy time service configuration | 13:02 |
| * Kinnison now nips off | 13:02 | |
| Zara | re: the UI meetup notes, who's sending those to the mailing list? perryl wrote them by hand and Krin announced them | 13:18 |
| Krin | Zara, i am intending to do a write-up but i'd also like to pass them around and ensure that everyone remembers thm the same as i do :) | 13:19 |
| Zara | cool, and thanks :) Just wanted to make sure it wasn't a case where we all thought someone else was doing it! | 13:19 |
| petefoth | Krin: send them to the list - if anyone disagrees they can disagree there :) | 13:19 |
| jjardon | Krin: send to the list, if there is some mistake the people will crrect them | 13:20 |
| Krin | ok, havent goten round to writing them up yet, been going through what IS on the list, but it'll be up before end of day | 13:20 |
| * SotK is in the process of writing up notes from the licence tracking chat | 13:22 | |
| jjardon | red in http://mason-x86-64.baserock.org/ ! the only error I see is "2015-02-06 12:42:16 Build failed: git-misc" more no more info. Would it be possible to get more logs? | 13:37 |
| ssam2 | jjardon: I think the git build didn't actually fail, something else is broken | 13:38 |
| ssam2 | when you see 'Progress: Transferring git-misc to shared artifact cache' and *then* 'Build failed: git-misc' it means something went wrong when transferring the artifact to the cache | 13:39 |
| ssam2 | should give a better error there really | 13:39 |
| ssam2 | /home on cache.baserock.org is full again | 13:39 |
| ssam2 | we really need to write the tool that cleans out old artifacts. | 13:40 |
| jjardon | ah, ok, thanks for looking into this! | 13:40 |
| ssam2 | i removed all the system artifacts and there is 26G free now | 13:40 |
| * jjardon was worried he has broken the build | 13:40 | |
| jjardon | can anyone take a look why the GTK+ mirror is not up-to-date? http://git.baserock.org/cgi-bin/cgit.cgi/delta/gtk+.git/ | 13:56 |
| ssam2 | jjardon: the logs show an error from git ' error: src refspec refs/heads/places-sidebar does not match any.' | 13:59 |
| ssam2 | one of git's characteristic user-friendly messages | 13:59 |
| ssam2 | actually, that's coming frm the .lorry file: http://git.baserock.org/cgi-bin/cgit.cgi/baserock/local-config/lorries.git/tree/open-source-lorries/gtk+.lorry | 14:00 |
| ssam2 | seems that a while back, we added certain 'allow force pushes to these refs' rules to the .lorry | 14:01 |
| ssam2 | these days I think we just allow force-pushing everything, because it's too hard to predict how upstreams will use git | 14:01 |
| ssam2 | so, you could fix this by sending a patch for gtk+.lorry that changes the 'refspecs' field to ["+refs/heads/*", "+refs/tags/*"] | 14:03 |
| tiagogomes_ | jjardon, you are updating again chunks which I already had updated in a branch :) | 14:08 |
| jjardon | tiagogomes_: sorry, I didn't see any branch in definitions repo | 14:10 |
| jjardon | ssam2: will do, thanks to looking into this! | 14:11 |
| *** grahamfinney has quit IRC | 14:12 | |
| *** grahamfinney_ has quit IRC | 14:12 | |
| *** grahamfinney_ has joined #baserock | 14:19 | |
| *** grahamfinney has joined #baserock | 14:19 | |
| *** grahamfinney_ has quit IRC | 14:22 | |
| *** grahamfinney has quit IRC | 14:24 | |
| *** grahamfinney has joined #baserock | 14:24 | |
| *** bashrc has quit IRC | 14:27 | |
| *** bashrc has joined #baserock | 14:27 | |
| *** CTtpollard has quit IRC | 14:45 | |
| *** CTtpollard has joined #baserock | 14:48 | |
| jjardon | every how many minutes is http://mason-x86-64.baserock.org/ refreshed? Seems it got stuck at 13:36:27 | 15:26 |
| SotK | jjardon: its probably in the middle of doing a build | 15:28 |
| rdale__ | bother, i just send the wrong patch by accident to the baserock-dev list, so i tried to say 'please ignore' to the wrong email, making the mess even worse. my apologies | 15:29 |
| pedroalvarez | jjardon: it is building 'attr' now | 15:30 |
| paulsherwood | rdale__: i'm assuming you mean the one that has a /baserock/james/0.10 unpetrify ref? | 15:31 |
| rdale__ | yes, that one should be ignored, javier's is fine | 15:32 |
| jjardon | rdale__: :) | 15:35 |
| rdale__ | sorry jjardon | 15:35 |
| jjardon | SotK: pedroalvarez sorry for my impatience ;) | 15:35 |
| jjardon | rdale__: np! | 15:35 |
| pedroalvarez | jjardon: you are right, it would be nice to know what is going on | 15:36 |
| jjardon | pedroalvarez: should I open a story in storyboard? | 15:36 |
| pedroalvarez | jjardon: given that this implementation of mason is going to be obsolete... I don't know | 15:39 |
| ssam2 | the new Mason will need to satisfy that story too though | 15:40 |
| ssam2 | if it does, we get to close the story :) | 15:40 |
| jjardon | we can create a "Improve CI reports" | 15:40 |
| jjardon | yah,, what Sam said | 15:40 |
| jjardon | :) | 15:40 |
| SotK | +1 to a story for better CI reporting :) | 15:42 |
| jjardon | done: https://storyboard.baserock.org/#!/story/7 | 15:42 |
| ssam2 | jjardon: I'm not sure your gtk+ patch is correct | 15:43 |
| ssam2 | you changed it to use whatever the default value of 'refspecs' is | 15:43 |
| ssam2 | I don't know where the default value of 'refspecs' is documented | 15:44 |
| rdale__ | it's in the trove reference manual - i was reading that this morning | 15:44 |
| ssam2 | but if it defaults to ["refs/heads/*", "refs/tags/*"] then the .lorry still won't work, it'll break the first time someone force-updates a branch or tag | 15:44 |
| ssam2 | ah, cool | 15:44 |
| ssam2 | it says 'Default is all.' | 15:45 |
| ssam2 | but I don't think 'all' is even a valid value for a git refspec | 15:45 |
| ssam2 | 'man git push' doesn't say anything about it | 15:46 |
| ssam2 | I think you should set refspecs to ["+refs/heads/*", "+refs/tags/*"] so that all force-updates are allowed though | 15:46 |
| *** CTtpollard has quit IRC | 15:46 | |
| pedroalvarez | ssam2: hm... I think it will fail to push whatever needs a force push, but everything else will be ok. This is only a problem with some upstream projects where master and tags are rebased. | 15:47 |
| ssam2 | ah, ok | 15:48 |
| ssam2 | so force-pushed refs would not get updated, but it wouldn't actually raise errors and cause the whole repo to stop being updated | 15:48 |
| pedroalvarez | I think | 15:49 |
| ssam2 | this needs to be clearer in the trove reference manual | 15:49 |
| ssam2 | but I can't do that until I actually understand how it works :/ | 15:49 |
| pedroalvarez | as a thought: should we create branches to anchor commits used in definitions on those repos where we allow force pushing? | 15:50 |
| pedroalvarez | (I hope 'anchor commits' makes sense) | 15:51 |
| ssam2 | i'm planning on a command for Morph which creates 'anchor tags' for every ref involved in the build of a given system | 15:51 |
| paulsherwood | ? | 15:51 |
| paulsherwood | i'm just a bit worried we may flood repos with tags... before realizing that's a bad idea, and be unable to clean them up because policy | 15:52 |
| pedroalvarez | so, whenever you do a release, and you want it to be reproducible over the years, you do that to create a branch in every repo used? | 15:52 |
| ssam2 | yes, that's possible | 15:52 |
| ssam2 | it might be that we decide not to use it on git.baserock.org yet | 15:52 |
| ssam2 | yes | 15:52 |
| ssam2 | a customer has asked for this to use in their trove, and hopefully it'll be useful for the baserock project too | 15:53 |
| pedroalvarez | yeah, it can be really useful for some people | 15:53 |
| jjardon | ssam2: +1000 | 15:54 |
| *** CTtpollard has joined #baserock | 15:57 | |
| *** mdunford has quit IRC | 15:59 | |
| paulsherwood | i'm not against it, i just hope folks try it out properly and get feedback from realistic situations so we don't actually damage user experience.... | 15:59 |
| paulsherwood | for example http://git.baserock.org/cgi-bin/cgit.cgi/delta/DLT-daemon.git/ | 15:59 |
| paulsherwood | our default Tag view shows upstream tags, which is nice. would be a shame to flood those off the page with temporary or user/specific tags | 16:00 |
| ssam2 | I agree that we need to be careful about that | 16:00 |
| ssam2 | if I was writing a policy for this, I'd say we only use the command when making releases of the baserock reference systems | 16:00 |
| ssam2 | so there'd be at most 1 new tag a week | 16:00 |
| ssam2 | but that still means we'd lose upstream tags | 16:01 |
| paulsherwood | within 10 weeks :) | 16:01 |
| pedroalvarez | I wouldn't use it in g.b.o :) | 16:01 |
| ssam2 | one possibility is we could do this in a different git server | 16:01 |
| ssam2 | great minds think alike :) | 16:01 |
| pedroalvarez | but I think is a useful thing to have for some user | 16:11 |
| pedroalvarez | is there a way to anchor commits without creating noise? | 16:11 |
| pedroalvarez | (tags or branches) | 16:11 |
| ssam2 | we could create 'hidden' refs | 16:15 |
| ssam2 | like refs/anchor/foo | 16:15 |
| ssam2 | but there might be corner cases with using those | 16:16 |
| ssam2 | worth investigating | 16:16 |
| *** mdunford has joined #baserock | 16:26 | |
| Kinnison | It'd also need checking on mirror tactics etc | 16:38 |
| SotK | In which project should I put the CI story on storyboard? baserock/infrastructure maybe? | 16:41 |
| paulsherwood | +1 | 16:43 |
| tiagogomes_ | jjardon, !! vala now? | 16:49 |
| tiagogomes_ | tiagogomes_ jjardon I was planning to update that one, but thanks for doing it for me :) | 16:49 |
| SotK | jjardon: I was going to update FUSE soon too :P | 16:50 |
| jjardon | tiagogomes_: :) you should submit patches upstream as soon as possible | 16:50 |
| jjardon | SotK: ^ | 16:50 |
| tiagogomes_ | jjardon the patches are not ready. | 16:50 |
| SotK | jjardon: :) | 16:51 |
| *** CTtpollard has quit IRC | 16:54 | |
| tiagogomes_ | jjardon, I updated in a branch gdb, make, lzo, file, gdbm, texinfo, libexpat, btrfs-progs, strace | 16:54 |
| *** mariaderidder has quit IRC | 17:01 | |
| *** tiagogomes_ has quit IRC | 17:05 | |
| *** gary_perkins has quit IRC | 17:07 | |
| *** petefoth has quit IRC | 17:07 | |
| *** tiagogomes_ has joined #baserock | 17:07 | |
| *** petefoth has joined #baserock | 17:08 | |
| *** gary_perkins has joined #baserock | 17:09 | |
| *** ssam2 has quit IRC | 17:22 | |
| *** inara has joined #baserock | 17:23 | |
| *** mauricemoss_ has quit IRC | 17:23 | |
| *** flatmush has quit IRC | 17:23 | |
| *** Krin has quit IRC | 17:23 | |
| *** bashrc has quit IRC | 17:23 | |
| *** mauricemoss_ has joined #baserock | 17:24 | |
| *** bashrc has joined #baserock | 17:24 | |
| *** flatmush has joined #baserock | 17:24 | |
| *** Krin has joined #baserock | 17:24 | |
| *** jonathanmaw has quit IRC | 17:29 | |
| jjardon | tiagogomes_: branch in definitions? Send it to the list! | 17:50 |
| *** bashrc has quit IRC | 17:58 | |
| *** inara has quit IRC | 17:58 | |
| tiagogomes_ | jjardon baserock/tiagogomes/armv8l64 | 17:59 |
| *** Krin has quit IRC | 17:59 | |
| *** inara has joined #baserock | 18:02 | |
| jjardon | tiagogomes_: nice | 18:03 |
| tiagogomes_ | jjardon do you now how can I update the config.{guess,sub} scripts when they are not in the top directory of the project | 18:05 |
| jjardon | tiagogomes_: they should be generated by autoreconf, they should normally be in the git tree | 18:06 |
| jjardon | should not* | 18:07 |
| *** inara has quit IRC | 18:13 | |
| tiagogomes_ | jjardon nope, most projects have them in the git tree | 18:14 |
| jjardon | tiagogomes_: The one in the tree are not needed if you are bootstrapping the project (which is what you want to do if you compile from git) config.guess and config.sub are created by automake (which is called in the appropiate order by autoreconf). The fact that some project include them in the git tree doesnt mean they are needed. | 18:19 |
| jjardon | Some project include them in case you dont want to bootstrap, but use ./configure directly. (similar as if they have the contents of the tarball in the git tree) | 18:21 |
| pedroalvarez | jjardon: if you are wondering: Feb 06 18:21:20 mason-x86-64 mason-report.sh[15374]: 2015-02-06 18:21:20 Progress: Transferring xorg-lib-libXdamage-misc to shared artifact cache | 18:21 |
| *** mauricemoss_ has quit IRC | 18:22 | |
| jjardon | pedroalvarez: nice! | 18:22 |
| *** rdale__ has quit IRC | 18:24 | |
| tiagogomes_ | jjardon autotools is a pita, most projects have already have a configure script and makefiles even in git; I need to update config.guess and config.sub scripts but autoreconf rarely works | 18:39 |
| jjardon | tiagogomes_: or you use autogen.sh/autoreconf, so you dont need config.sub/guess or you use configure and you dont have to change the config.guess/sub | 18:40 |
| jjardon | every project should build with autoreonf, if not its a bug | 18:41 |
| tiagogomes_ | jjardon configure calls config.guess and config.sub | 18:41 |
| tiagogomes_ | jjardon, then I can assure you that almost every project has a bug. The thing here is, automake doesn't have backwards compatibility | 18:42 |
| jjardon | tiagogomes_: yes, autoreconf call the toold that generate configure, config.guess and config.sub | 18:42 |
| tiagogomes_ | jjardon, yep, but autoreconf almost never succeeds | 18:43 |
| jjardon | tiagogomes_: thats probably a bug | 18:44 |
| jjardon | tiagogomes_: with what packages are you have problems? | 18:44 |
| tiagogomes_ | which gives me two choices, or either I download the scripts from here: https://www.gnu.org/software/gettext/manual/html_node/config_002eguess.html; or either I copy them from /usr/share/automake1.4 | 18:44 |
| jjardon | tiagogomes_: both are bad ideas | 18:44 |
| tiagogomes_ | the first introduces a delta -> meh; the second breaks when we update automake -> meh | 18:44 |
| tiagogomes_ | I agree | 18:44 |
| jjardon | tiagogomes_: so with what packages are you having problems so I can take a look? | 18:45 |
| *** inara has joined #baserock | 18:45 | |
| jjardon | tiagogomes_: 3 option is to fix the package if needed and sent the patch upstream ;) | 18:45 |
| tiagogomes_ | jjardon cvs-tarball, distcc, ncurses, groff, openssh | 18:46 |
| jjardon | cvs-tarball? why you need that for? | 18:47 |
| *** grahamfinney has quit IRC | 18:48 | |
| tiagogomes_ | jjardon it is on devel system | 18:48 |
| * jjardon looking | 18:48 | |
| jjardon | tiagogomes_: ok, if its a tarball you should use ./configure | 18:50 |
| *** grahamfinney has joined #baserock | 18:51 | |
| tiagogomes_ | jjardon again, config.guess and config.sub are tool old, they don't recognize aarch64 | 18:51 |
| *** edcragg has quit IRC | 18:52 | |
| jjardon | tiagogomes_: oh! you should bootstrap then | 18:54 |
| *** inara has quit IRC | 18:54 | |
| tiagogomes_ | jjardon, I know! but our version of automake doesn't understand some old Makefile.am's and configure.in ':( | 18:55 |
| *** grahamfinney has quit IRC | 18:55 | |
| jjardon | tiagogomes_: I fear you have to be more specific about the problems you are having ;) | 18:56 |
| jjardon | tiagogomes_: do you have any logs around? | 18:56 |
| *** tiagogomes_ has quit IRC | 19:00 | |
| jjardon | mmm, we are using tarballs in most of those packages: first step would be to use the git repo. Also openssh mirror is not up-to-date | 19:01 |
| *** HoloIRCUser1 has joined #baserock | 19:02 | |
| jjardon | would be ok this patch to update the openssh lorry?: http://paste.baserock.org/noviyofoco | 19:04 |
| *** lachlanmackenzie has quit IRC | 19:24 | |
| *** gary_perkins has quit IRC | 19:31 | |
| *** HoloIRCUser3 has joined #baserock | 19:37 | |
| *** HoloIRCUser1 has quit IRC | 19:38 | |
| *** HoloIRCUser1 has joined #baserock | 19:43 | |
| *** HoloIRCUser3 has quit IRC | 19:46 | |
| *** inara has joined #baserock | 19:50 | |
| *** inara has quit IRC | 19:55 | |
| *** inara has joined #baserock | 19:59 | |
| *** inara has quit IRC | 20:04 | |
| *** inara has joined #baserock | 20:07 | |
| *** inara has quit IRC | 20:16 | |
| *** inara has joined #baserock | 20:26 | |
| *** inara has quit IRC | 20:43 | |
| *** HoloIRCUser1 has quit IRC | 21:02 | |
| paulsherwood | jjardon: i think that would lead to different refs vs the cvs convert we have been using? | 21:03 |
| paulsherwood | maybe best to call it openssh-git for this, stop lorrying the cvs? | 21:04 |
| *** tiagogomes_ has joined #baserock | 21:24 | |
| *** tiagogomes_ has quit IRC | 21:29 | |
| paulsherwood | 2015-02-06 20:13:26 [Build 82/209] [systemd] Elapsed time 00:29:59 | 21:42 |
| paulsherwood | seems like a lot longer than last time i checked | 21:43 |
| *** zoli__ has joined #baserock | 21:47 | |
| *** zoli__ has quit IRC | 21:53 | |
| *** zoli__ has joined #baserock | 21:53 | |
| *** zoli__ has quit IRC | 22:34 | |
| *** zoli__ has joined #baserock | 22:35 | |
| *** zoli__ has joined #baserock | 22:36 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!