*** zoli__ has joined #baserock | 05:04 | |
*** zoli__ has quit IRC | 05:47 | |
*** zoli__ has joined #baserock | 06:06 | |
* straycat meows | 06:58 | |
*** paulw has quit IRC | 07:07 | |
*** paulw has joined #baserock | 07:07 | |
*** sambishop has joined #baserock | 07:13 | |
*** Albert_ has joined #baserock | 07:20 | |
*** a1exhughe5 has joined #baserock | 07:25 | |
*** Albert_ has quit IRC | 07:31 | |
*** Albert_ has joined #baserock | 07:33 | |
*** bashrc has joined #baserock | 07:54 | |
*** mariaderidder has joined #baserock | 07:59 | |
pedroalvarez | Ok, looks like the problem with gcc5.1 is syslinux | 08:12 |
---|---|---|
*** rdale has joined #baserock | 08:14 | |
pedroalvarez | my experiment: | 08:14 |
pedroalvarez | 1) using a 15.10 devel system, upgrade morph, override syslinux with the artifacts of syslinux built with gcc5.1, deploy a base system | 08:14 |
pedroalvarez | 2) base sytem doesn't boot | 08:14 |
juergbi | pedroalvarez: in case this helps, syslinux 6.02 works for me when built with gcc 5 but syslinux 6.03 doesn't | 08:17 |
persia | Cool. Can we use an EFI bootloader? | 08:17 |
pedroalvarez | juergbi: that might be relevant :) | 08:20 |
Kinnison | Only a minority of our systems can use EFI | 08:20 |
juergbi | pedroalvarez: i'm not sure. i wanted to do a quick bisect but had inconsistent results so i gave up for now | 08:21 |
persia | Really? I thought it worked for A9+, POWER7+, and i686+ | 08:21 |
* persia can't figure out when MIPS started supporting EFI, but at least some years back in shipping hardware | 08:22 | |
Kinnison | persia: It depends on the bootloaders | 08:22 |
Kinnison | persia: e.g. nominally the AARCH64 moonshot should support EFI, but because HP build their u-boot without the requisite support, you can't run the EFI stubs | 08:23 |
Kinnison | persia: as for x86/x86_64 - again it depends on the systems | 08:23 |
Kinnison | for virtualised systems under KVM it depends on OVMF which has licence issues | 08:24 |
* persia murmurs about flashing the desired version into the preboot environment flash, and givs up | 08:24 | |
persia | s/vs/ves/ | 08:24 |
Kinnison | Now if only all of our target systems let us affect the preboot environment | 08:24 |
Kinnison | :) | 08:24 |
* Kinnison would love it if we could move from extlinux to grub2 | 08:25 | |
*** jonathanmaw has joined #baserock | 08:25 | |
Kinnison | But again, some of our targets lack even the hooks necessary for grub2 to hook in | 08:25 |
Kinnison | again e.g. moonshot which doesn't have the u-boot API built in (or at least didn't, I've not checked the most recent firmware drop) | 08:25 |
* pedroalvarez wonders when syslinux is being used in the deployer system | 08:29 | |
Kinnison | to install the extlinux bootloader | 08:29 |
Kinnison | onto the disk image | 08:29 |
pedroalvarez | Kinnison: only extlinux.conf, right? or something else? | 08:30 |
pedroalvarez | (also menu.c32, but that is not relevant) | 08:30 |
persia | Kinnison: Hrm? What system doesn't allow one to write to the preboot environment flash? | 08:30 |
Kinnison | pedroalvarez: No, the actual boot sector IIRC | 08:31 |
Kinnison | persia: IIRC, the HP moonshot doesn't let you write the u-boot environment | 08:31 |
pedroalvarez | ah, ok, as I expected it couldn't be that easy, thanks | 08:32 |
Kinnison | persia: hence we had to jump through interesting hoops | 08:32 |
persia | Kinnison: It has no means to flash updated firmware? | 08:32 |
Kinnison | persia: Sure it does, but they're signed lumps applied by the HP iLO | 08:32 |
persia | Ah, so only HP can produce firmware contents that can be flashed? | 08:32 |
Kinnison | AFAICT | 08:32 |
Kinnison | it's possible that might not be the case, but I've not investigated | 08:33 |
Kinnison | Certainly only HP-produced firmware will be in the least bit supported | 08:33 |
Kinnison | i.e. they likely will claim user-produced firmware voids hardware warranty | 08:33 |
persia | It's worth asking. I know lots of other HP products allow you to flash arbitrary firmware, although support is only available with HP-provided firmware. | 08:35 |
radiofree | There were a couple of commands left over in the default environment that looked like you could replace the version of uboot | 08:36 |
radiofree | If you were brave enough to test them | 08:36 |
persia | That seems a sensible model. Not being brave is well understood :) | 08:37 |
persia | In other hardware (I've not used a Moonshot that way), there are often multiple versions of firmware that can be stored (or one loaded at initialisation and wiped on finalisation), making it much safer to use features like that than one might imagine. | 08:38 |
*** ssam2 has joined #baserock | 08:42 | |
*** ChanServ sets mode: +v ssam2 | 08:42 | |
* pedroalvarez sees a 'sleep(2)' call after installing extlinux, as a hack to make the install finish | 08:47 | |
*** CTtpollard has joined #baserock | 08:47 | |
Kinnison | x86 bootloaders are sadmaking | 08:48 |
pedroalvarez | hehe, sleep(10) didn't do anything :) | 08:51 |
*** tiagogomes_ has joined #baserock | 08:56 | |
tiagogomes_ | it would be nice to be able to `morph build system1 system2 …` | 08:58 |
* Kinnison remains desireous of morph build foocluster.morph [optional system list] | 09:00 | |
persia | Kinnison: What do you have against x86 bootloaders? | 09:00 |
persia | Also, +1 to `morph build foocluster.morphP | 09:01 |
* persia thinks rEFIt and Clover are both interesting projects for x86 | 09:04 | |
* richard_maw wants to sort out the build graphing code to support graphing more than one system at once | 09:19 | |
*** gary_perkins has joined #baserock | 09:27 | |
straycat | maybe we should fix the existing graphing code before thinking about additional functionality? | 09:27 |
persia | I generally try to understand the long-term goals before attempting to make the short-term fix, unless there is urgent pain, in which case the activities can be parallelised. | 09:29 |
*** ssam2 has quit IRC | 09:29 | |
richard_maw | straycat: it needs to be fixed to allow graphing multiple systems | 09:29 |
*** lachlanmackenzie has joined #baserock | 09:30 | |
*** ssam2 has joined #baserock | 09:30 | |
*** ChanServ sets mode: +v ssam2 | 09:30 | |
straycat | richard_maw, what about rationalising the source pool creation and artifact resolving stages | 09:31 |
straycat | this was the basis for blocking the merge of the fix i made a month ago to detect cycles in the build graph? | 09:31 |
richard_maw | ah yes, the inability of it handling loops | 09:32 |
straycat | to be fair, i've failed to improve the change in the past month for lack of time | 09:33 |
persia | I wonder if it might be worth having a monthly development meeting, where people talk about their priorities for the next month, so that we can have a better idea when various bits will land. | 09:34 |
persia | Or if people don7t have time to work on things, this can be reported, and if someone else wants the feature, they can pick it up without as high a burden as poking the last submitter. | 09:35 |
pedroalvarez | I like that idea | 09:35 |
* SotK does too | 09:36 | |
persia | I've seen it work well in other environments, but it depends on two things. | 09:37 |
*** rdale has quit IRC | 09:37 | |
persia | 1) someone volunteering to mangage the task list (usually on the wiki) and run the meetings [this can be a rotating role] | 09:37 |
*** rdale has joined #baserock | 09:38 | |
persia | 2) Everyone having some degree of confidence in what they will be doing over the next month | 09:38 |
persia | Note that I don't believe we can cover *all* the activities, because there are always those quick patches one does on a sunday afternoon because one doesn't want to take a fourth bath in the day, but we can probably have some idea what larger things are on the horizon. | 09:39 |
radiofree | pedroalvarez: did you ever submit http://git.baserock.org/cgi-bin/cgit.cgi/delta/genivi/persistence-client-library.git/commit/?h=baserock/v1.0.0&id=39c68df2a9ee0b089212855f64a61fbd671b1a80 upstream? | 09:39 |
pedroalvarez | radiofree: yes | 09:40 |
radiofree | pedroalvarez: it didn't seem to land | 09:41 |
pedroalvarez | radiofree: nope, let me find the bug link | 09:41 |
pedroalvarez | radiofree: http://bugs.genivi.org/show_bug.cgi?id=327 | 09:42 |
radiofree | heh | 09:44 |
radiofree | ok | 09:44 |
pedroalvarez | they actually closed the bug, but I re-opened it | 09:44 |
radiofree | and then they ignored you :( | 09:45 |
straycat | more likely they just forgot? | 09:45 |
pedroalvarez | well, they answered me 22 days after I reported the bug | 09:45 |
straycat | / were preoccupied with other things | 09:46 |
*** Krin has quit IRC | 09:47 | |
richard_maw | pedroalvarez: so… they brushed you off on a policy reason, rather than fixing the bugs that cause it to fail with -Werror set? | 09:47 |
pedroalvarez | not sure about how bad sounds "brush you off", but yes | 09:47 |
straycat | persia, seems like a good idea but in practice i'm not sure we have that level of contribution reliability | 09:48 |
pedroalvarez | I guess I should have sent a patch to fix the warnings, instead of adding --disable-werror support | 09:48 |
straycat | and then when the compiler gets updated it will just break with some new warning? | 09:49 |
persia | straycat: You mean that you don't think most of the more active developers know what they are working on that far in advance? | 09:49 |
persia | We could do more often, but that means more time from everyone, which means either finding times that everyone is off work, or getting permission from employers, etc. | 09:50 |
pedroalvarez | persia: note that I really like the idea | 09:50 |
pedroalvarez | 1 month sounds ok to me | 09:50 |
pedroalvarez | radiofree: any suggestions about what can I do with that bug report? | 09:52 |
persia | pedroalvarez: Are you up for volunteering to run it? | 09:53 |
persia | Given your contributions to the ops team, I'd think someone else might have more time, but there's the "if you want something done, ask a busy person" rule :) | 09:53 |
pedroalvarez | :) | 09:54 |
* pedroalvarez is participating in around 5 projects everyday | 09:55 | |
pedroalvarez | but I can allocate some time for this | 09:56 |
straycat | I didn't know about https://gerrit.baserock.org/#/c/219/ until April 5th when i spotted the bug | 09:56 |
pedroalvarez | persia: I'll send an email to baserock-dev to discuss the format, content and process of these meetings, is that ok? | 09:57 |
persia | Sounds reasonable to me. | 09:57 |
* straycat sighs and goes back to whatever he was doing | 09:58 | |
persia | I've gotten involved in very complex processes around such things, but I'd strongly suggest starting with something like a list of tasks, loose assignment (by volunteering), and quick status by task in the meeting. I'd further suggest having the tasklist on the wiki as a set of links into storyboard. | 09:59 |
straycat | you're not listening are you | 09:59 |
persia | Most importantly, be sure that the set of things is not intended to be all-inclusive. There's always going to be lots of stuff that can't make the list, for various reasons. | 10:00 |
persia | straycat: Right. I think there's *loads* of stuff that we'll end up doing that won't make a meeting. | 10:01 |
persia | But if there are things people want to do longer-term, I think it makes sense to share those at a time when we're all paying attention. | 10:01 |
persia | That said, if folk think it's better to do that by sending RFCs to the list, we can do it that way | 10:01 |
* persia has a tendency to do too much on IRC | 10:02 | |
straycat | A meeting would help as a forum to bring things up maybe, but I don't see what the difference would be between me raising something in a meeting and raising something on gerrit? Persistence perhaps. For example we know we need to tidy up some code, the only reason it's not been done is because no one's had the time for it, really, not because there's an absence of planning | 10:13 |
Kinnison | straycat: submitting things on gerrit quickly gets them lost in a crowd I think | 10:14 |
Kinnison | straycat: similarly to patches sent to a busy ML | 10:14 |
* straycat nods | 10:16 | |
Kinnison | A meeting, if well attended by people who attribute it with some level of authority and thus vest a level of dedication to it, might be better | 10:17 |
jjardon | persia: you can build with support for bios and/or efi when you build a (recent) syslinux | 10:21 |
straycat | Kinnison, if they have the time to dedicate then sure | 10:27 |
Kinnison | straycat: indeed | 10:28 |
Kinnison | straycat: But those without the time are unlikely to attend such a meeting, surely? | 10:28 |
*** Krin has joined #baserock | 10:28 | |
persia | I've also seen folk whose time is dedicated have time for occasional meetings, which can be useful, so that the agenda of the folk behind the scenes (who rarely emerge in open source communities) can be glimpsed, at least in part. | 10:29 |
straycat | Kinnison, i guess :) | 10:32 |
jjardon | I also agree the meeting is a good idea. I've created a skeleton page here to add topics the people are interested on: http://wiki.baserock.org/Meetings/ Maybe is a good idea to create a doodle poll to set the date? | 10:36 |
Kinnison | jjardon: I think that's rather jumping the gun | 10:41 |
Kinnison | jjardon: pedroalvarez was going to send a mail to the ML to discuss things | 10:41 |
straycat | perhaps we should have a meeting to organise our meeting | 10:41 |
straycat | :p | 10:41 |
* pedroalvarez will write the email as soon as I finish something else | 10:42 | |
jjardon | Kinnison: jumping the gun? | 10:46 |
Kinnison | http://idioms.thefreedictionary.com/jump+the+gun | 10:47 |
pedroalvarez | http://imgace.com/wp-content/uploads/2012/06/Pew-Pew-Pew-Pew-Pew-Pew-Pew-Pew-Pew.jpg | 10:48 |
persia | To date we've taken decisions on the mailing list, and more recently in gerrit. Taking a decision in IRC to take more decisions in IRC without consulting the traditional forums is likely to leave many existing members of our community feeling disenfranchised. | 10:49 |
jjardon | persia: dont think anyone is out: the meeting / doodle was meant to be announce in the mailing list | 10:52 |
persia | I'm just a bit more conservative than that: I'd like to see loose consensus that there *should* be an IRC meeting before announcing a doodle. | 10:52 |
persia | But I don't assert that my conservatism should inhibit others. | 10:53 |
mwilliams_ct | Add a "do not want" option to the doodle? | 10:55 |
*** zoli__ has quit IRC | 11:22 | |
*** zoli__ has joined #baserock | 11:23 | |
rdale | is an infinite loop in cachekeycomputer.py a known bug | 11:36 |
rdale | ? | 11:36 |
ssam2 | yes, it happens if there is a loop in the build graph | 11:40 |
ssam2 | https://gerrit.baserock.org/#/c/219/ would fix it I think | 11:40 |
rdale | all i've done is to reference the openssh chunk from a stratum, as i don't want to pull all of foundation in, just for one chunk | 11:41 |
pedroalvarez | rdale: not possible to do that atm | 11:46 |
rdale | i've renamed as 'openssh-wrt' and that's fixed it | 11:47 |
pedroalvarez | oh, so you created a stratum for openssh? | 11:48 |
pedroalvarez | or you added openssh into that stratum? | 11:48 |
rdale | i added openssh to an existing cpe-wrt stratum | 11:49 |
Zara | SotK: thanks for the fix. I've +1'd. | 11:51 |
pedroalvarez | ah, then if that gives you loop error might be because openssh is already a dependency? | 11:51 |
rdale | ah yes, i've found the problem - cpe-wrt depends on connectivity which depends on foundation | 11:52 |
*** rdale has quit IRC | 12:08 | |
*** rdale has joined #baserock | 12:10 | |
radiofree | found the cause of the vt switching issue... | 12:26 |
radiofree | using vga=... | 12:26 |
*** gary_perkins has quit IRC | 12:29 | |
*** gary_perkins has joined #baserock | 12:31 | |
*** rdale has quit IRC | 12:33 | |
*** rdale has joined #baserock | 12:38 | |
ssam2 | radiofree: so remove that and it works? | 13:02 |
SotK | Zara: thanks | 13:04 |
radiofree | ssam2: no framebuffer device then | 13:04 |
radiofree | using uvesafb instead fixed nothing | 13:05 |
ssam2 | oh, so you've found the cause but not the solution? | 13:07 |
*** pedroalvarez has quit IRC | 13:10 | |
*** pedroalvarez has joined #baserock | 13:11 | |
*** ChanServ sets mode: +v pedroalvarez | 13:11 | |
*** pedroalvarez has quit IRC | 13:11 | |
radiofree | ssam2: yeah | 13:12 |
*** pedroalvarez has joined #baserock | 13:12 | |
*** ChanServ sets mode: +v pedroalvarez | 13:12 | |
radiofree | aha | 13:12 |
radiofree | nomodeset | 13:12 |
radiofree | though that only works with uvesafb not vesafb | 13:13 |
radiofree | i think.. maybe... | 13:13 |
radiofree | didn't work this time | 13:14 |
radiofree | right so if you switch to the vt before you initilise the uvesafb driver (and i assume vesa here as well) it will work once you load the driver | 13:16 |
Kinnison | jjardon: do you care about https://gerrit.baserock.org/#/c/39/ ? It hasn't been touched in 5 or so weeks | 13:27 |
pedroalvarez | looks like tlsa updated that patch after jjardon | 13:31 |
tlsa | i doubt it; that was for manifest generation, whihc is now done differently | 13:32 |
pedroalvarez | then, can we abandon it? | 13:33 |
tlsa | I suspect so, unless anyone wants more info in the metadata | 13:33 |
*** sambishop has quit IRC | 13:37 | |
*** paulw has quit IRC | 13:40 | |
*** paulw has joined #baserock | 13:40 | |
*** sambishop has joined #baserock | 13:52 | |
radiofree | and now it's working completly fine.... | 13:55 |
pedroalvarez | well, this is baserock, redeploy and it should be broken again | 13:56 |
persia | Weren't there some patches recently that let one test reproducibility to avoid that? | 14:08 |
* radiofree has no idea wtf he did to get this working | 14:13 | |
radiofree | i didn't edit any config files.. build new software... | 14:13 |
rjek | Did you sacrifice a lower mammal? | 14:19 |
rjek | Any pentagrams? | 14:19 |
rjek | win 22 | 14:19 |
rjek | bah | 14:19 |
pedroalvarez | storyboa | 14:29 |
pedroalvarez | bah | 14:29 |
* radiofree has successfully broken it again by redeploying | 14:32 | |
rjek | Now you get to say "bah" | 14:32 |
radiofree | now this is working | 14:35 |
radiofree | and now it is not | 14:37 |
pedroalvarez | - Son, take a look at the 'turn signals' and tell me if they work | 14:40 |
pedroalvarez | - they work! | 14:40 |
pedroalvarez | - now they don't | 14:40 |
pedroalvarez | -they work! | 14:40 |
pedroalvarez | .. etc | 14:40 |
pedroalvarez | (spanish joke) | 14:40 |
* richard_maw prefers the Father Ted version with the Fairy lights on the Christmas tree | 14:41 | |
pedroalvarez | :) | 14:41 |
*** sambishop has quit IRC | 14:45 | |
*** sambishop has joined #baserock | 15:14 | |
*** zoli___ has joined #baserock | 15:17 | |
*** zoli__ has quit IRC | 15:17 | |
ssam2 | Patch to update Morph in definitions for the 15.19 release: https://gerrit.baserock.org/#/c/598/ | 15:51 |
*** a1exhughe5 has quit IRC | 16:02 | |
Zara | if I've made commits before adding gerrit as a remote and getting the commit-msg hook, is there any way to push to gerrit? or will I need to go back and make the commits again? | 16:02 |
rdale | has anyone time to review this patch before the release https://gerrit.baserock.org/#/c/587/ and corresponding 588 patch, as minimal systems won't work currently without it | 16:03 |
persia | I'd recommend doing a rebase, which will recreate all the commits. | 16:03 |
*** jonathanmaw has quit IRC | 16:09 | |
jjardon | Kinnison: Iv'e abandoned it know | 16:11 |
ssam2 | Zara: git-review fixes it for you automatically | 16:11 |
ssam2 | rdale: thanks, i'll make sure it gets in | 16:12 |
rdale | thanks a lot | 16:13 |
rdale | is there an easy way to amend a commit message for a patch on gerrit? | 16:20 |
rdale | do i amend it locally and push again? | 16:20 |
ssam2 | you can edit it in the web UI | 16:20 |
ssam2 | 'Edit Message' button just above the commit message and to the right | 16:20 |
rdale | oh yes - that's neat! | 16:21 |
ssam2 | on the subject of tagging Morph whenever it understands a new definitions version: I'll create tags named baserock-definitions-1, baserock-definitions-2 and baserock-definitions-3 unless anyone has a strong opinion on how else it should be done | 16:30 |
ssam2 | I'm not going to tag versions where support was dropped at this point because I don't have a clear idea how to do it yet, others are welcome to do it | 16:31 |
jjardon | ssam2: +1 | 16:32 |
persia | Do we have any versions where support was dropped yet? | 16:40 |
ssam2 | actually no | 16:40 |
*** tiagogomes_ has quit IRC | 16:41 | |
persia | Then I don't mind that nothing is tagged that way :) | 16:41 |
persia | +1 on the tag changes | 16:41 |
ssam2 | thanks! | 16:43 |
*** zoli___ has quit IRC | 16:45 | |
*** mariaderidder has quit IRC | 16:49 | |
ssam2 | tags complete! I'll also try to add a bit to the release process about how to do this in future | 16:55 |
*** flatmush has quit IRC | 16:59 | |
ssam2 | argh! Seems Gerrit has resumed its game of losing merged commits | 17:00 |
ssam2 | https://gerrit.baserock.org/#/c/588/ is marked as merged but is not in 'master' of morph.git on gerrit.baserock.org or git.baserock.org | 17:00 |
*** flatmush has joined #baserock | 17:00 | |
SotK | is there any chance https://gerrit.baserock.org/#/c/604/ could be merged in time for the release? | 17:01 |
*** bashrc has quit IRC | 17:01 | |
ssam2 | ha, good idea | 17:02 |
*** Krin has quit IRC | 17:03 | |
SotK | ssam2: thanks :) | 17:03 |
ssam2 | oh, part of my confusion is that 588 is for definitions.git, not morph.git | 17:08 |
ssam2 | oh! it's for fhs-dirs.git | 17:10 |
ssam2 | so actually nothing is wrong, but we need to update the ref for fhs-dirs in definitions.git | 17:11 |
ssam2 | i'll do that, update morph.git, set builds running, then go home! | 17:11 |
paulsherwood | sounds like a plan :) | 17:12 |
* SotK sends https://gerrit.baserock.org/#/c/605/ and heads off too | 17:15 | |
*** ssam2 has quit IRC | 17:30 | |
*** zoli__ has joined #baserock | 17:33 | |
*** gary_perkins has quit IRC | 17:40 | |
*** edcragg has quit IRC | 18:17 | |
*** lachlanmackenzie has quit IRC | 18:20 | |
*** zoli__ has quit IRC | 18:49 | |
*** zoli__ has joined #baserock | 19:14 | |
*** zoli__ has quit IRC | 19:23 | |
*** zoli__ has joined #baserock | 19:29 | |
*** zoli__ has quit IRC | 21:04 | |
*** Albert_ has quit IRC | 22:23 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!