| 00:06.38 | *** part/#gooseproject josephpagoda (~josephpag@144.35.32.97) |
| 00:45.59 | *** join/#gooseproject makfinsky (~imak@237.sub-75-215-170.myvzw.com) |
| 01:59.05 | goozbach | how did the project day go? |
| 01:59.20 | herlo | really well, I got a template |
| 01:59.25 | goozbach | nice |
| 01:59.35 | herlo | I'm actually working on it now |
| 01:59.41 | goozbach | I just built up the content from your png wireframes in yaml builder |
| 01:59.47 | goozbach | just to see if I still remember it |
| 01:59.52 | herlo | okay |
| 01:59.59 | herlo | goozbach: you'll have to show me how that works |
| 02:00.04 | goozbach | I will |
| 02:00.06 | herlo | my theory is this |
| 02:00.48 | herlo | We do most things that are non-static by pulling in some sort of rss or xml feed |
| 02:01.06 | *** join/#gooseproject josephpagoda (~josephpag@65.100.192.66) |
| 02:01.09 | herlo | the yaml will provide simple functionality to do static components... |
| 02:01.20 | herlo | and possible blog posts, too |
| 02:01.35 | goozbach | the status bar for example? |
| 02:01.38 | herlo | yeah |
| 02:01.47 | Nafai | is working |
| 02:01.50 | goozbach | what did you end up with when you say template? |
| 02:01.56 | goozbach | you have html wireframes now? |
| 02:01.59 | herlo | an html mockup |
| 02:02.00 | herlo | yeah |
| 02:02.08 | goozbach | css class definitions? colors fonts etc? |
| 02:02.18 | herlo | not all of them, just one with static content. I need to clean it up and put template stuff in it |
| 02:02.30 | herlo | yes, css, colors, etc. Though I want to change the fonts |
| 02:02.35 | goozbach | cool |
| 02:02.41 | herlo | but nothing too problematic |
| 02:02.55 | herlo | let me throw it up and you can see the awesomeness Velda built for us |
| 02:03.17 | goozbach | it wont be too hard to cut in the stuff you and Velda built with the YAML framework |
| 02:03.26 | goozbach | herlo: I was thinking something similur |
| 02:03.42 | goozbach | we can have a cronjob run the xml feed stuff (dynamic content) |
| 02:03.46 | goozbach | git ci and git push |
| 02:03.52 | herlo | yeah, or on load |
| 02:04.13 | goozbach | and voilá poof we're good |
| 02:04.14 | herlo | I think the git commit and push should only be for static content changes and bugfixes |
| 02:04.31 | herlo | all of the rest should be dynamically pulled in with ajax or something |
| 02:04.37 | goozbach | does your thinking use iframes or ajax |
| 02:04.39 | goozbach | ahh ajax |
| 02:04.45 | goozbach | that's a good idea |
| 02:04.54 | goozbach | so it can still be hosted on github |
| 02:05.01 | goozbach | that I think it a very good goal |
| 02:05.01 | herlo | http://sexysexypenguins.com/misc/goose_template.html |
| 02:05.23 | herlo | the stuff with AJAX is not coded right now |
| 02:05.28 | herlo | so we'll migrate to that over time |
| 02:05.46 | herlo | we can be pretty static for the time being |
| 02:06.39 | herlo | but I was thinking something like http://www.ubuntustats.com/ |
| 02:06.49 | herlo | josephpagoda: http://sexysexypenguins.com/misc/home_layout.png |
| 02:06.54 | herlo | compare the html to that |
| 02:07.41 | *** join/#gooseproject makfinsky (~imak@128.sub-75-215-122.myvzw.com) |
| 02:08.00 | herlo | goozbach: more realtime |
| 02:08.44 | goozbach | ok yeah I like that |
| 02:08.52 | goozbach | the ubuntustats that is |
| 02:09.43 | herlo | indeed |
| 02:10.11 | herlo | so I'll be back in a bit, going to template the html for the home page and see if we can't get something basic up shortly |
| 02:10.22 | goozbach | herlo: let me run with cutting this into yaml |
| 02:10.33 | goozbach | shouldn't take more than an hour or so |
| 02:10.58 | herlo | umm |
| 02:11.07 | herlo | I want to change the css some first |
| 02:11.13 | herlo | so hang on |
| 02:11.15 | goozbach | ok |
| 02:11.20 | goozbach | I'm just building structure |
| 02:14.55 | herlo | cool |
| 02:15.02 | herlo | I'll have the css done shortly I think |
| 02:15.49 | Nafai | man, I suck at css |
| 02:16.21 | herlo | Nafai: me too |
| 02:16.40 | goozbach | I never saw an html entity called an aside |
| 02:16.42 | goozbach | hmm |
| 02:20.57 | herlo | goozbach: me neither |
| 02:21.00 | herlo | but it's kind of cool |
| 02:21.42 | herlo | goozbach: I think I've got the page a little more like what I want it |
| 02:23.46 | herlo | goozbach: I'm still going to play with the layouts a bit since I have no real basis for this stuff, but want to kind of figure it out a little better |
| 02:25.08 | makfinsky | herlo: I know you're working on something else right now, where should I document this? Here's a long cmd line on how to find the srpm of the skein deplist: |
| 02:25.24 | makfinsky | for i in $(skein deplist publican-2.1-0.el6.src.rpm | grep perl | grep -v ==) ; do yumdownloader --urls --source "$i" ; done | grep rpm$ | sort | uniq | sed 's/.*\/\/\(.*\)/\1/' |
| 02:26.18 | makfinsky | Could use a bit more string manipulation to remove the NVR at the end, which could then be piped back into a check in koji for build existence. |
| 02:26.42 | makfinsky | Hmm, I should also remove the perl grep... |
| 02:30.06 | herlo | makfinsky: I don't do it that way because my sources are local |
| 02:30.30 | herlo | but I suppose a cp $i |
| 02:30.37 | herlo | or something |
| 02:30.54 | makfinsky | No, this doesn't download anything. |
| 02:30.57 | herlo | makfinsky: probably put it in the ml, but should get documented on the wiki eventually, methinks |
| 02:31.10 | makfinsky | It just resolves which srpms are required. |
| 02:31.27 | herlo | makfinsky: yes, yum api can do that for sure |
| 02:31.30 | makfinsky | yumdownloader --urls only resolves. |
| 02:31.35 | herlo | needs to figure that out at some point |
| 02:32.08 | makfinsky | Ok, I'll write an email on why I did this. |
| 02:32.15 | makfinsky | And how it works... for some value of works. |
| 02:32.17 | makfinsky | :) |
| 02:33.05 | herlo | k |
| 02:58.42 | herlo | goozbach: so the jekyll layout is a bit interesting. took me a bit to figure out what exactly is happening |
| 02:59.27 | goozbach | jekyll is pretty different from what I'm used to as well |
| 02:59.33 | herlo | but it's not bad |
| 02:59.38 | herlo | just a bit backward from what I was thinking |
| 03:02.21 | herlo | gotta step out, bbiab |
| 04:05.13 | herlo | goozbach: so, whatcha got? |
| 04:12.56 | herlo | well, this is what it looks like so far: http://gooseproject.github.com/ |
| 04:57.57 | makfinsky | Wow, if we can tie the banner into koji for the stats, that'd be awesome. |
| 04:59.48 | herlo | :) |
| 05:07.16 | makfinsky | Alright, xorg-x11-server complete! |
| 05:08.34 | herlo | w00t! |
| 05:53.04 | makfinsky | Ah, added another sed regex to remove v-r from n-v-r. |
| 06:52.31 | *** join/#gooseproject makfinsky (~imak@11.sub-75-209-136.myvzw.com) |
| 07:51.29 | *** join/#gooseproject makfinsky (~imak@244.sub-75-215-23.myvzw.com) |
| 10:13.24 | makfinsky | Woo doggy! |
| 10:24.56 | makfinsky | Dozy of a deplist. |
| 16:07.50 | *** join/#gooseproject makfinsky (~imak@208.sub-75-215-220.myvzw.com) |
| 16:42.59 | herlo | fun |
| 16:59.37 | makfinsky | Goose morning. |
| 16:59.48 | herlo | hi |
| 17:12.34 | makfinsky | Got a monster chain build going for publican and it's deps. |
| 17:19.52 | herlo | I see that :) |
| 17:20.15 | *** join/#gooseproject josephpagoda (~josephpag@168-103-130-183.bois.qwest.net) |
| 17:20.58 | herlo | I've made some progress on the website. Need to redo a few things to make it more flexible. |
| 17:21.10 | makfinsky | Rocking. I like the new web site. |
| 17:21.14 | herlo | :) |
| 17:21.41 | herlo | I actually have mockups for the entire thing and need to get them all configured and going. Hopefully I can do that today. |
| 17:37.57 | makfinsky | No!!! A build in the monster chain failed... |
| 17:41.38 | makfinsky | Oh damn... when a chain build fails, it can leave builds untagged...!! |
| 18:05.38 | *** part/#gooseproject josephpagoda (~josephpag@168-103-130-183.bois.qwest.net) |
| 18:46.00 | makfinsky | Man... I thought I disliked perl before... |
| 18:53.25 | makfinsky | Ok, I think I've tied almost all of the remaining failed builds to a chain build. This should be interesting. |
| 18:53.58 | makfinsky | I suspect that there will be a few more failed perl builds along the way to getting these done. |
| 19:07.53 | shalkie | Goose afternoon all. |
| 19:13.04 | shalkie | herlo: Sorry to miss you yesterday. Back has been problematic the past week or so. Thought some good bed rest would be helpful. |
| 19:22.01 | shalkie | Sweet. Valgind built. |
| 19:24.07 | shalkie | s/valgind/valgrind |
| 19:25.51 | shalkie | Ah sweet, you have system tap in the chainbuild. And here I was going to wait for publican to finish and then try to rebuild again. :-) |
| 19:36.01 | herlo | shalkie: your loss |
| 19:36.23 | shalkie | herlo: True enough. |
| 19:36.39 | herlo | makfinsky: what? builds get untagged when a chainbuild fails? |
| 19:36.44 | herlo | It really shouldn't |
| 19:48.22 | shalkie | herlo: How goes your Sunday? |
| 19:51.48 | herlo | it goes |
| 19:52.06 | herlo | just relaxing at home, working on the website |
| 20:13.35 | shalkie | Cool Cool. |
| 20:19.11 | *** join/#gooseproject josephpagoda (~josephpag@71-37-173-215.bois.qwest.net) |
| 20:24.13 | makfinsky | herlo: Yeah, if the chain build fails before the tag task completes, that gets canceled. The builds completed before the cancel and so you end up with builds that aren't tagged. |
| 20:24.35 | makfinsky | shalkie: Yeah, I looked at the deps on everything and just decided to lump it all together. |
| 20:24.59 | herlo | makfinsky: hmm... |
| 20:25.09 | makfinsky | Yeah, I was surprised by that too. |
| 20:25.21 | makfinsky | Logically, it makes sense... somewhat. |
| 20:26.07 | herlo | well, it's only because the build succeeded but wasn't tagged before the whole task was cancelled |
| 20:26.23 | makfinsky | Right. |
| 20:26.38 | makfinsky | I think that's what I said... ? |
| 20:27.00 | herlo | yeah, was just reiterating my understanding |
| 20:27.04 | makfinsky | Gotcha. |
| 20:27.31 | makfinsky | Yeah, so lesson - when chain builds fail, check for untagged builds and tag them before retrying chain build. |
| 20:27.47 | herlo | indeed |
| 20:27.54 | makfinsky | Make sure to wait for regen-repo task to complete as well. |
| 20:28.12 | makfinsky | That is, before re-submitting the chain build. |
| 20:28.56 | makfinsky | Goose gravy! First pass of the chain build succeeded! |
| 20:29.35 | makfinsky | Found another buildreq missing in a perl pkg... issue ticket created. |
| 20:30.01 | makfinsky | Is there a way to get a list of the issues open for all gooseproject git repos? |
| 20:30.32 | herlo | sure |
| 20:30.36 | herlo | use the api |
| 20:31.50 | makfinsky | I was afraid that was going to be the answer. |
| 20:32.52 | herlo | :) |
| 20:37.34 | shalkie | has to leard |
| 20:39.08 | shalkie | has to learn to stop fiddling with the wifij ap when flat on his back in another room. And typing apparently... |
| 21:35.17 | herlo | and an update! http://gooseproject.github.com/ |
| 21:37.33 | herlo | and... It's easy to change! |
| 21:45.28 | josephpagoda | herlo: that's looking good |
| 21:48.24 | herlo | yay |
| 21:48.28 | herlo | glad you made it... |
| 21:54.07 | *** join/#gooseproject makfinsky (~imak@47.sub-75-215-43.myvzw.com) |
| 22:00.14 | *** part/#gooseproject josephpagoda (~josephpag@71-37-173-215.bois.qwest.net) |
| 22:21.33 | shalkie | here here |
| 22:22.06 | herlo | is sad that shalkie has back problems and couldn't make Project Day |
| 22:28.08 | shalkie | eh. Life moves on. Sometimes its just more painful then others. ;-) |
| 22:28.47 | shalkie | Hopefully I can make the next one. And this next week I am working from home so I have a nice comfy lazy boy to work from. :-) |
| 22:28.56 | herlo | I suppose. |
| 22:29.21 | shalkie | But I do think the page is working out nicely. |
| 22:29.58 | shalkie | At this rate we makfinsky might have the lead in successful package builds. Wow. |
| 22:30.00 | herlo | shalkie: in the near future, it'll be easy to show you all how to update it, too! |
| 22:31.09 | herlo | shalkie: it just means that we have more than one person to look to when trying to build stuff. It's great to not be a single point of failure :) |
| 22:35.59 | shalkie | Hooray for debusification. |
| 22:41.26 | makfinsky | Debusification? Is that an official term? |
| 22:41.28 | makfinsky | ;) |
| 22:42.12 | makfinsky | I've gotten a nearly automated process worked out. Needs to be codified though, right now it relies on a handful of manual steps. |
| 22:42.27 | herlo | makfinsky: k, we can probably work on that this week |
| 22:42.37 | makfinsky | And the for loops are definitely hacks. |
| 22:42.46 | herlo | :) |
| 22:43.07 | makfinsky | Then again, I've never claimed to be any good at writing code. |
| 23:29.47 | shalkie | You write code outside of bash. That puts you a couple steps ahead of me. ;-) |
| 23:30.06 | shalkie | c'yall later. Time to drive by a house. see if it looks as pretty in person as on line. |
| 23:36.37 | makfinsky | Holy crap... publican has been built! |
| 23:37.19 | herlo | w00t! |
| 23:59.09 | makfinsky | Dang... systemtap failed... |
