IRC log for #gooseproject on 20130402

01:08.40herlotime for 'q' packages
01:08.47herloalmost done with these
01:33.34shalkie:-)
01:33.37shalkieHey herlo
01:57.21herlohey shalkie
01:59.48shalkieherlo: How goes it?
02:00.36herlogetting there
02:00.48shalkieYou mean on the packages?
02:01.45herloyep
02:01.54shalkieI've noticed. :-)
02:01.55herlowatching mlb opening day, also
02:02.18shalkieSeems much faster then it was last time around too!
02:02.39herlosure, many less issues
02:02.44herloand many less rpms
02:03.02herlowhen we 7.0, it'll be similar in difficulty to 6.0
02:03.10herlomost of the rest of this should be pretty straightforward.
02:04.15*** join/#gooseproject bochecha_ (~bochecha@175.45.17.220)
02:04.15*** join/#gooseproject bochecha_ (~bochecha@fedora/bochecha)
02:04.36shalkiehmmm, yes. 7.0.
02:04.40shalkieThat is right around the corner.
02:05.06herlosoonish, I would suspect
02:08.16*** join/#gooseproject makfinsky (~imak@fedora/makfinsky)
02:10.02shalkieI believe that the beta is expected this summer.
02:10.22shalkieProbably announced at a particular event.
02:13.04herloyeah, I would think so
02:27.48shalkieDude! I love the treasure map overlay at maps.google.com
03:34.48herloman, sometimes the git pull from github sucks
04:38.55*** join/#gooseproject bochecha_ (~bochecha@fedora/bochecha)
04:42.44*** join/#gooseproject bochecha__ (~bochecha@175.45.17.220)
04:44.12*** join/#gooseproject bochecha_ (~bochecha@fedora/bochecha)
05:56.59herlobochecha_: how's things?
05:57.12bochecha_herlo: same old, same old
05:58.06bochecha_just back from a long easter week-end (both friday and monday are public holidays here!)
05:58.26bochecha_but work didn't clear itself magically in my absence :(
05:59.59herlolol, sounds familiar
06:00.31bochecha_the 4 days-long week-end? or the pile of work never lowering down? :P
06:00.46bochecha_thursday is again a public holiday here
06:01.10herlothe work
06:01.16bochecha_I guess it's what you get when you live in a country with two cultural traditions: double ste of public holidays \o/
06:01.21herlowow, the chinese take a lot of holidays?
06:01.41bochecha_no idea about the Chinese
06:02.11bochecha_but here in HK, we have public holidays for big Christian celebrations (Christmas, Easter,...), which I guess come from the British
06:02.57bochecha_and we also have public holidays for Chinese celebrations (Day of the Dead, Anniversary of Buddha, ...), which I guess come from China
06:03.01herlooh Hong Kong, that's like china, isn't it these days?
06:03.11bochecha_"it's complicated" ;)
06:03.32herloyeah, sounds so
06:04.15herlobochecha_: I figured out one of the fun bugs you told me about a while back
06:04.20bochecha_it's officially a "Special Administrative Region", which means it's both inside China or outside, depending on the topic (and how dear to Beijing that topic is)
06:04.29herlo~logs
06:04.29ibotAll conversations are logged to http://ibot.rikers.org/%23gooseproject/ Lines starting with spaces are not logged. Logs are updated daily.
06:04.30bochecha_oh, what was it?
06:05.08herlolooking it up
06:05.35bochecha_I mean, what was the bug? :D
06:05.49herlofrom 20120426 irc log
06:05.51herlo04:01.10bochechayou guys never had any issue building libuser in koji?
06:05.58bochecha_oh
06:06.03bochecha_you figured that out?
06:06.16bochecha_I still haven't managed to rebuild that package :x
06:06.28bochecha_(although I haven't tried for a while)
06:06.29herloI can tell you what is up
06:07.22bochecha_I was about to go out for lunch, but I guess you're hoping to go to bed soon, so I'm listening :)
06:07.25herloI found a bug somewhere that points out you need to run the tests on separate machines
06:08.11herloso if you lower the hosts capacity to around 1.0
06:08.16herlowell, 1.1 is the minimum
06:08.32herloit will build on separate machines and the sockets won't cause each other issues
06:08.58herlothey've supposedly fixed it in newer versions
06:08.58bochecha_oh
06:09.06bochecha_you mean the builds for each arch?
06:09.26herloyes
06:10.01bochecha_ouch
06:10.05bochecha_I only have one builder here :P
06:10.16herlothat explains why
06:10.21bochecha_I guess so
06:10.32bochecha_I'll have a look at the latest package, to see if it finally builds
06:10.36herloyou could probably lower the capacity still and maybe they will build one at a time
06:10.40bochecha_and if it doesn't, I'll... disable the unit tests :(
06:10.48bochecha_ah, that's a possibility, yes
06:11.01bochecha_how do you change the capacity? I did it in the past, but forgot
06:11.02herlowe have four builders, but that was my thought
06:12.51herlogood luck
06:26.42bochecha_thanks, will have a look at it after lunch
06:30.08herlotake care
14:13.48*** join/#gooseproject makfinsky (~imak@fedora/makfinsky)
20:59.43nbherlo, you around?
21:02.02herlonb: I am
21:05.00herlonb: what's up?
21:12.21nbherlo, hey, what packages are left for me to work on?
21:17.01nbherlo, and, are we building the other stuff under ftp://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/ that isn't under os, and what about 6Client and ComputeNotde and stuff
21:18.28herlonb: atm, we're not
21:18.58nbok
21:18.59herlonb: as for what's left. I've been working from A through S. I am stuck on a couple in the Ss so I haven't moved forward
21:19.07nbso i will start on t i guess?
21:19.12nbor do you want me to start with z?
21:19.13herlonah, start on y
21:19.16herloer x
21:19.22herloy is done already, as it's only yum
21:19.24nbok
21:19.31herlothe way to tell if something is done is to search on koji
21:19.40herloso let's do one together, if you think that will help
21:20.38herlohttp://paste.fedoraproject.org/6527/37628136 <-- have a look at this
21:21.01herlosince I know some of the xulrunner packages are installed, you might want to check to see which ones
21:21.20herlohttps://kojiweb.gooselinux.org/koji/packageinfo?packageID=460 <-- looks like this
21:22.27nbso you already did some of them
21:22.29herlocomparing that with what is in the paste, it looks like a few failed to build
21:22.34herloI only completed one
21:22.38nbso i need to try to figure out why the ones that failed failed
21:22.43herlolook under 'state'
21:22.51herloyeah. we'll eventually need to build them all
21:23.26herloI have been turning kojira on and off so we only generate repos as needed. You can do this on koji.gooselinux.org. Let me get you sudo rights to do that.
21:24.07nbok
21:24.26nbherlo, and i can fire off regen-repos manually if you give me admin in koji
21:24.35nbso we could do without kojira at all if you wanted
21:24.41nbat least for now
21:25.09nbherlo, so gl6.0-updates-candidate automatically is in gl6.0-build, correct?
21:25.13nbit looks like it according to koji latest-pkg
21:25.50herloeh, it's probably easier to give you rights to restart kojira
21:25.57herloalmost there anyway
21:26.28nbok
21:36.25herlonb: okay, try ssh roman.gooselinux.org
21:36.42herloyou should then be able to perform any of the following service kojira {start,stop,status}
21:36.57nbyeah, it works according to sudo -l
21:37.17herlocool
21:40.26nbherlo, 6.0-updates-candidate is in buildroot, right?
21:42.10herloyes
21:42.16herlonb: you can see that in tags
21:42.26herlohave a look at gl6.0-build tag
21:43.25nboh ok
21:43.43herlonb: that make sense?
21:44.17nbherlo, yeah
21:44.24herlocool
21:44.54nboh ok, so since it says Inheritance:
21:44.54nb<PROTECTED>
21:44.57nbthen that means it is
21:44.58nbok great
21:51.02herloyep
21:52.53nbherlo, how much ram/disk/cpu does a builder need?
21:53.00nbwonders if prgmr could give goose a VPS to use for one
21:54.02herlonb: we'd love that!
21:54.07herlothey don't need a lot
21:54.47nblike what?
21:54.52herloI think our builders have 4G ram, need a bit of disk, probably 25G or so for mock. 1 vcpu is plenty, though more give us faster builds
21:55.01nbhmm
21:55.03herlolet me see what we're using actually
21:55.59herloregular builders don't need the nfs share, but they do need a space to install from.
21:58.48nbok
21:59.45herlonb: so I just looked, my guesses above are accurate
22:01.46nbherlo, i'm going to change the vps i made for fedora web of trust into a gooselinux one
22:01.52nbsince sparks doesn't need it anymore
22:02.04nb4096M ram, 96G disk will work?
22:02.11herlolol, yes!
22:02.17herlohow many cpus?
22:02.35nb6 i think
22:02.43herlonb: build it as a centos box for the moment, we'll convert it to goose when we have updates to match.
22:02.58herlohopes that's in a month or two at most.
22:03.00nbherlo, it's going to be a $68/month package from prgmr.com
22:03.06herlowhoa!
22:03.14nbherlo, do we have a sponsors page on our website or anything?
22:03.17herlois glad he's not paying the bill :)
22:03.25nbwe don't have to, but it'd be nice to link to prgmr.com somewhere
22:03.30herlonb: yep, we can most definitely add one. I need to add one for Endosys too
22:03.51herlonb: there is this: http://gooseproject.org/downloads.html
22:04.06herlobut I'd love to have a 'sponsors' or 'thanks' page for sure.
22:05.40herlonb: is that a physical box? Could we split it up into a couple of builders?
22:08.45nbherlo, it is a xen vps
22:09.01nbwith 4096mb ram and 96gb disk
22:11.35nbalthough i could make it as something different possibly?
22:11.49herlowell, I think we're probably fine
22:11.54herlothat's a good size
22:12.48herloI just wish we could make that the createrepo box. Unfortunately, that one needs direct access to the nfs share. Doing data transfer over nfs between California and Virginia would be a bitch
22:13.12herloit'll probably be slower to start too, but building big packages it should be much faster
22:16.46nbyeah
22:17.05nbherlo, hey, what should i call it? gooselinux or gooseproject?
22:18.14herlogooselinux
22:18.17nbhmm, /me debates whether he should put it under his account or have you set up a new account to put it under and me set it to comp'ed
22:18.21herloproject is our forward facing
22:18.38nbherlo, can you sign up for a new account on billing-external?
22:18.46nbor actually just go in and order a new 4096mb package
22:18.59herlonb: probably good to call it something like build64-prgmr.gooselinux.org or somesuch.
22:19.02nbunder a new account (not under your herlo account
22:19.13herlosure, I'll make a gooseproject account
22:19.17nbherlo, well, i mean what we call it (everything is username.xen.prgmr.com)
22:19.34nbherlo, but you can change hostname to whatever
22:20.10herlonb: right, I'm saying it'll be gooseproject.xen.prgmr.com :)
22:20.36nbok
22:20.36herlonb: as for what we call things, gooselinux is for infrastructure, gooseproject is forward facing stuff, like the website and our projects.
22:21.13nbok
22:22.32herlonb: done
22:24.15nband now i just set you to complimentary
22:24.27nbnow i just need to set it up
22:24.30nbherlo, where's your key
22:25.05herlonb: um...
22:25.14herloLet me see if it's on my site
22:25.25nbi'll add you a console user
22:25.46herlono worries
22:34.39nbherlo, gooseproject.xen.prgmr.com is up
22:34.43nbi'm updating it now
22:40.59herlow00t!
22:49.06nbherlo, just let me know about your key and i'll give you access
22:49.15herlonb: oh, I have a key
22:49.42herlonb: http://sexysexypenguins.com/misc/prgmr_rsa.pub
22:50.45nbherlo, ok, try ssh gooseproject@council.prgmr.com
22:51.42herloI'm in
22:51.49nbok
22:51.52nbyou should be able to console
22:51.55herloyep
22:51.57nbchange the root password
22:52.00nbit is password at the moment
22:52.44herlonb: we should setup lastpass for this
22:53.16nbtrue
22:55.23nbnice, i didn't know i had signed up for lastpass
22:59.18herlohehe
23:22.48nbherlo, xulrunner is having issues
23:22.52nbit says it can't checkout
23:23.08nbhttps://koji.gooselinux.org/koji/taskinfo?taskID=44237
23:23.35herlonb: hmm
23:23.52herlonb: btw, I was thinking about it and koji 1.8.0 just came out
23:24.19herlomaybe we should use the new prgmr server as a test bed for that
23:25.34herlonb: it's because the commit hash you are trying doesn't exist
23:25.37herlohttps://github.com/gooselinux/xulrunner/commits/gl6.0-updates
23:25.45herlowhich one are you trying??
23:25.54herlois realizing that we need more descriptive commit messages
23:26.11herloprobably related to the actual rpm version-release values
23:26.52herloalso, it looks like I need to update skein build to allow for git hashes with targets
23:26.56herlofiles a ticket
23:28.38goosebotIssue CLOSED - gooseproject/skein: #13 (Skein exits ungracefully when expected information is not found in issues.) <https://github.com/gooseproject/skein/issues/13>
23:29.05goosebotIssue OPENED - gooseproject/skein: #15 (skein build needs to support -h &lt;git_commit_hash&gt;) <https://github.com/gooseproject/skein/issues/15>

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.