IRC log for #gooseproject on 20111207

00:01.36herlogoose evenin'
00:30.52shalkieEvening.
00:31.21shalkieI understand that we have a little get together or something planned for this evening.
00:55.18goozbacheven' everyone
01:05.06shalkieEvening goozbach.
01:08.45shalkieherlo: You there?
01:13.36*** join/#gooseproject makfinsky (~imak@184.sub-75-203-216.myvzw.com)
01:37.37herlohi shalkie
01:39.43herloshalkie: what's up?
01:40.30*** join/#gooseproject bochecha (~bochecha@175.45.17.220)
01:40.30*** join/#gooseproject bochecha (~bochecha@fedora/bochecha)
01:46.22shalkieherlo: Nothing. Just wnated make sure your coming tonight. :-D
01:49.26herloshalkie: "you're". And yes, I am here :)
01:50.07herloshalkie: it turns out, I rarely miss a meeting where I don't notify someone first.
01:50.12herlo:P
01:52.01goozbach9 mins to meeting
01:52.48herloorly?
01:54.08herlomakfinsky: goozbach: I like *parts* of this wiki page from ascendos: http://ascendos.org/wiki/PackageNaming
01:54.09goosebotTitle: PackageNaming - Ascendos Wiki (at ascendos.org)
01:54.30herlospecifically the first part. I don't think I care for the way they do their naming convention when they change things
01:57.45makfinskyherlo: Agreed. I like the naming convention idea. Not so hot on the version convention.
01:58.14makfinskyWell... maybe.
02:00.15herlo?
02:00.35*** join/#gooseproject laroche (~laroche@dslb-178-010-033-196.pools.arcor-ip.net)
02:01.31goozbach#startmeeting
02:01.32goosebotMeeting started Wed Dec  7 02:01:31 2011 UTC.  The chair is goozbach. Information about MeetBot at http://gooseproject.org/2011/11/07/weekly-meetings.html.
02:01.32goosebotUseful Commands: #action #agreed #help #info #idea #link #topic.
02:01.38goozbach#meetingname weekly
02:01.38goosebotThe meeting name has been set to 'weekly'
02:01.50goozbach#chair herlo shalkie makfinsky Nafai
02:01.50goosebotCurrent chairs: Nafai goozbach herlo makfinsky shalkie
02:03.18makfinskyHooray!
02:03.24goozbach#topic status updates
02:03.24*** topic/#gooseproject by goosebot -> status updates
02:03.53shalkieHooray
02:04.40herloHooray!?
02:05.12makfinskyWho goes first? Me? Ok.
02:05.18herlolol, sure
02:05.24goozbachgo
02:05.26goozbachyeah sorry
02:05.31goozbachgo ahead
02:05.42makfinskyCleaned up vm hosts that weren't doing anything other than eating resources.
02:05.53makfinskyCorrected sudoers config on gooseqa1.
02:06.11makfinskyAlmost have builder #4 online.
02:06.18herlo+1
02:06.25makfinskyConfigured email notifications for koji.
02:06.57makfinskyHalfway done with a build host add script.
02:07.24*** join/#gooseproject opapo (~quassel@75-169-104-66.slkc.qwest.net)
02:07.30makfinskyKicked off a bunch of builds for m-p pkgs.
02:07.41makfinskyAnd that's it for now.
02:07.50opapoI guess I could make it
02:08.03opapoI'll go
02:08.09goozbachopapo: you're turn then
02:08.58opapoI committed my version of repoquery.py along with a README file that is fairly explanatory
02:09.24herlo+1
02:09.32opapoI would appreciate feedback, because although I think it is great it may not be perfect, nor in a usable state.
02:09.50opapoThat's all.
02:09.55goozbachherlo:
02:10.01herlooh hi
02:10.09goozbachyour turn
02:10.11herloso I've been a bit busy
02:10.19herlogot grapple working on roman
02:10.39herloand wrote a new component to auto-launch builds
02:11.09herlofinished skein 2.0 and it's currently in the release-2.0 branch, going through it's qa fixes
02:11.30herloshould be in master by end of the week
02:12.18herloI also got packages q-z imported and will be working on others ongoing until we get them all built
02:12.28herloI'm hoping for this weekend to have *most* built
02:12.30herlodone
02:12.54NafaiI'll go
02:13.12NafaiDidn't do anything this past week, but I plan on reviewing herlo's changes to grapple tonight and merging them with the main repo.
02:13.17NafaiDone.
02:14.16goozbachshalkie:
02:14.18goozbachyou're up
02:14.41shalkieI don't think I have actually done anything of interest this week for the projet.
02:14.44shalkieSorry guys.
02:15.06goozbachok my turn I guess
02:15.49goozbachI've finally got goosebot a permanent home. I've also done some work on getting autotest/autoqa installed (tis more bleeding edge than I thought)
02:16.08goozbachI've also finished the email sending feature of meetbot.
02:16.21goozbachwhich this is the first beta test of!
02:16.56goozbachI'm also making good on my promise to dump the contents of the ascendos email brainstorm on the web for forking.
02:17.02goozbachthat should be done tonight
02:19.04goozbachand that's me
02:19.39goozbach#topic Build automation
02:19.39*** topic/#gooseproject by goosebot -> Build automation
02:19.49goozbachherlo talk to us a min bout that
02:19.56goozbachI need to step afk for a moment bb
02:20.29shalkiegoozbach: What about the email to ascend?
02:20.43herlooh, build automation
02:20.43shalkiejust wants to ensure it isn't about to drop from queue.
02:21.02herloso
02:21.12herloI sent an email yesterday, I think
02:21.22herlowith the whole process, but I'll recount it here quickly
02:21.44herlothe essential part is, after a repo is granted. It will get imported to the repo
02:21.58herloan import is extract, upload and push, in that order
02:22.27herlowhen the commit happens, a post-receive hook calls grapple on roman/koji and adds it to a build queue
02:22.58herloa second 'client' component of grapple, pulls those commits down every ten minutes and launches a koji build as kojiadmin
02:23.16herloif the build succeeds, everything is peachy
02:23.38herloif the build fails, the owner (according to koji) gets an email with the link to the logs and such
02:24.16herloright now, we've probably got about 2/3 of the builds either going, completed or failed. I've personally seen around 20 failures in the packages I own
02:24.30herloso the next question is, what to do about failed builds
02:24.46herlowell, the hope is that we can just run them again when we finish the first pass
02:24.55herloand narrow down the number of unbuildable packages
02:24.56goozbach#action figure out what to do with failed builds
02:25.08herlogoozbach: I already have a plan :)
02:25.22goozbach#undo
02:25.22goosebotRemoving item from minutes: <ircmeeting.items.Action object at 0x1485c50>
02:25.30goozbach#info herlo has a plan about failed builds
02:25.35herloeventually, we'll have only a handful (probably less than 100) packages that may need some sort of intervention
02:25.40goozbach?
02:25.42goozbach??
02:25.46herlofor each of those builds
02:25.47goozbach.;/ /
02:25.49herlolol
02:26.03goozbachthat was my son saying "HI"
02:26.07herlothe owner will fix whatever problem is going on...
02:26.22goozbachI gotta go guys
02:26.26goozbachherlo: can you drive?
02:26.29herloapply patches as needed, or upload a new patch
02:26.31herlogoozbach: sure
02:26.32goozbachI'll email my update later
02:26.34opaposee ya goozbach
02:26.47herloas I was saying
02:26.55herloupload a new tar ball rather
02:27.34herloonce the package has been built successfully with koji, we'll need to make sure to send any spec file patches or other .patch files to the proper upstream
02:28.01herlomy thoughts are to file a bug in bugzilla for any sort of item we want to push upstream.
02:28.23herlowe should be able to perform this sort of thing over and over for each release.
02:28.28herlomajor or minor
02:28.33herlothoughts?
02:29.37herlomakfinsky: shalkie: Nafai: opapo ??
02:30.17opapoIt sound great, but I'm not using this so I am not one to ask.
02:30.23opapoIt is all logical though
02:30.55*** join/#gooseproject makfinsky (~imak@123.sub-75-224-117.myvzw.com)
02:31.17opapowhat if ownership is transferred?
02:31.21makfinsky+1 for the automation workflow.
02:31.31opapohow does knowledge transfer happen?
02:31.55opaposeperate issue?
02:32.10herloopapo: knowledge transfer?
02:32.47herlodo you mean, 'how do we get patches upstream and available for others to know about them'?
02:32.51opapoIf I were to work on bash, then get pulled away and need to transfer ownership to you (let's say) how do you know what I did to work on it?
02:33.17opapoI guess if everything is in the .patch files then we are ok
02:33.23herloyou should commit your patches
02:33.27herlo:) yep
02:33.31opapook
02:33.36opapo+1
02:33.38herlocool. Any other thoughts?
02:35.34makfinskyI imagine that we'll work on adding depsort into the workflow later, perhaps next year.
02:35.41herloyes
02:36.02herloI am definitely interested in the work that opapo did there. It's going to be immensely helpful I think
02:36.08opapolet's fine tune it before it is used in production
02:36.33herloopapo: of course :)
02:36.36makfinskyRight.
02:37.00herlookay next topic
02:37.30herlo#topic EOY Goals
02:37.31*** topic/#gooseproject by goosebot -> EOY Goals
02:37.56herloEssentially, I want to lay this out so we don't get blind sided by holiday plans
02:37.57makfinskyI would still like to complete alpha by eoy.
02:38.09herlome too
02:38.26makfinskyI'd also like to propose a sprint week - the week between xmas and ny.
02:38.40herloI could make parts of that for sure
02:38.45herlomostly evenings
02:39.21herlo#info makfinsky wants to have a sprint week between christmas and new years
02:39.52herloso, let's talk about steps left to get there
02:40.10herloonce we get the majority of the builds complete
02:40.53herloI'd like to target having all builds complete, even the difficult ones by 12/17
02:40.59makfinskyWe need a pungi compose.
02:41.08herlobefore that we need something else
02:41.21herlomash
02:41.41herlowe're going to need to take the repos from koji and put them together in a slightly different way
02:41.45makfinskyWhat is mash?
02:42.02herlospecifically, we need to mash together the repos from koji so that some i686 libs are in the x86_64 repos
02:42.13herloand we need to put the noarch repos in both
02:42.20herlomakfinsky: mash does that ^^
02:42.24makfinskyAh!
02:42.27makfinskyNice.
02:42.31herloonce we have that
02:42.38herlowe can start composing with pungi
02:42.55herloI suspect that the last week of the year will be daily if not twice daily composes
02:43.14herloI'd like to work toward automating that, of course.
02:43.28makfinskyOf course.
02:43.48herlowith a goal of having a reliable kickstart which will build the composes automatically when we hit beta
02:44.23herlothe folks at ascendos can definitely help us here, since they arleady have some composes in place
02:44.24makfinskyOk, so for EOY goal of alpha we need:
02:44.28herlothough they are having some difficulty with abi compliance
02:44.34makfinsky1. To complete rpms builds.
02:44.42makfinsky2. Mash installation and config.
02:44.59makfinsky3. Pungi and kickstart file for compose.
02:45.24herlosounds about right
02:46.38herlocool.
02:46.43herlo#topic Open Floor
02:46.47*** topic/#gooseproject by goosebot -> Open Floor
02:46.48herloanything else we want to discuss??
02:47.34makfinskyKeep up the blogging folks!
02:47.41herloyay!
02:47.43makfinskyGoes for me too... :P
02:47.45herlogood idea
02:48.02herlowill be writing up docs the next couple weeks for skein when he has time as well
02:49.32herlowell, I think that's it...closing the meeting shortly. Unless there's something else.
02:49.43herlo5
02:49.49herlo4
02:49.59herlo3
02:50.04herlo2
02:50.11herlo1
02:50.15herlo#endmeeting
02:50.17*** topic/#gooseproject by goosebot -> GoOSe Project - http://gooseproject.org
02:50.17goosebotGoOSeProject Meeting ended Wed Dec  7 02:50:14 2011 UTC.
02:50.17goosebotMinutes:        http://admin.gooseproject.org/goosebot/logs/2011/2011-12-07-Meeting-weekly-0201.html
02:50.17goosebotMinutes (text): http://admin.gooseproject.org/goosebot/logs/2011/2011-12-07-Meeting-weekly-0201.txt
02:50.17goosebotLog:            http://admin.gooseproject.org/goosebot/logs/2011/2011-12-07-Meeting-weekly-0201.log.html
02:50.18goosebotThank you.
02:50.18goosebotsending meeting email
02:50.40herlogoozbach: very nice!
02:56.31*** join/#gooseproject opapo (~opapo@75-169-104-66.slkc.qwest.net)
02:59.35*** join/#gooseproject opapo (~quassel@75-169-104-66.slkc.qwest.net)
03:13.25*** join/#gooseproject makfinsky1 (~imak@96.sub-75-203-137.myvzw.com)
03:43.06*** join/#gooseproject makfinsky (~imak@1.sub-75-253-214.myvzw.com)
03:58.31*** join/#gooseproject makfinsky1 (~imak@208.sub-75-202-120.myvzw.com)
04:25.14*** join/#gooseproject bochecha (~bochecha@fedora/bochecha)
04:47.10*** join/#gooseproject makfinsky (~imak@77.sub-75-253-239.myvzw.com)
04:51.09shalkieI am going to sleep... Sleep... sllleeeeeppppppp....
04:51.26herlomeh
04:51.29herlosleep is overrated
04:51.31shalkienight night folks.
04:52.54shalkieYou say that to a person that got 2.5 hous sat/sun, 5 sun/mon, 3 mon/tue. So I am tired. See ya all tomorrow.
04:54.00herlowhy?
04:54.06herloyou should sleep more :)
04:54.28makfinskyOh crud... I keep getting side tracked with the adding of new builders.
04:54.48makfinskyMore sleep gud.
04:57.43herlolol
04:57.56herloit's only midnight where you are :)
05:24.24*** join/#gooseproject opapo (~quassel@75-169-104-66.slkc.qwest.net)
05:36.10*** join/#gooseproject makfinsky (~imak@123.sub-75-253-215.myvzw.com)
06:23.19makfinskyherlo: You around?
06:25.30herlohi makfinsky
06:25.37herloI was about to head to bed
06:25.40herlobut what's up?
06:25.52makfinskyHeya, need some help with fixing the user table in koji.
06:25.57herlooh?
06:26.00makfinskyIt can wait until tomorrow.
06:26.02herlowhy?
06:26.07herloI can help ya
06:26.14herlonow is fine
06:26.33herlomakfinsky: what is wrong with the user table in koji?
06:26.42makfinskyYeah, trying to add build64f.gooselinux.org and the koji add-host is failing with the a complaint about unique user constraint.
06:26.46herloare you trying to up your stats again :)
06:27.16herloum, you don't need to add the host as a user
06:27.23herlowhen you do add-host, it does that
06:27.41herlodid you previously add a user?
06:27.45herlowith that name?
06:28.00makfinskyWasn't trying to add host as a user.
06:28.16makfinskyI did not add it as a user.
06:28.18herlojust making sure you didn't try that
06:28.24herloI did that once, bad idea!
06:28.48herlocan you look at the user table in koji and see if that user already exists?
06:28.52makfinskybuild64f.gooselinux.org, "koji add-host build64f.gooselinux.org i386 x86_64" fails with the following:
06:29.18makfinskyYeah, the user is listed, not sure how or why.
06:29.26makfinskyhttps://koji.gooselinux.org/koji/users?order=name
06:29.28herloprobably just delete it
06:29.34makfinskyHow do I delete it?
06:29.49herloin postgres
06:30.04herlohave you done a lot with it?
06:30.32makfinskyNo, haven't done much with pg.
06:30.43herlok, let's share a screen session
06:30.48herloon roman
06:30.52makfinskyOk.
06:31.42herlohave a screen in there as root
06:33.02herlowaits for makfinsky
06:33.15*** join/#gooseproject makfinsky1 (~imak@153.sub-75-251-139.myvzw.com)
06:33.30makfinsky1Am back.
06:33.37herlowaits for makfinsky
06:33.39herlohave a screen in there as root
06:43.19herlomakfinsky1: let me know if you need anything else
06:43.24makfinsky1Thanks!
06:45.56herlodid it work?
06:48.55makfinsky1Yes, it sure did.
06:49.04makfinsky1Ok, now it's really late. Time for bed.
06:49.34makfinsky1I wonder why koji list-hosts takes so damn long...
06:49.52makfinsky1It's a small table with less than two handfuls of entries... wtf.
06:51.51herlolol, yeah
12:32.37*** join/#gooseproject makfinsky (~imak@156.sub-75-251-232.myvzw.com)
12:37.04makfinskyWoot! Koji has completed all tasks assigned to it!
13:11.55*** join/#gooseproject makfinsky (~imak@152.sub-75-224-85.myvzw.com)
14:09.23herlolol, GoOSe Morning!
14:09.29herloI'm adding more to the queue :)
14:10.49*** join/#gooseproject makfinsky (~imak@226.sub-75-251-199.myvzw.com)
14:11.08*** topic/#gooseproject by herlo -> GoOSe Project - http://gooseproject.org | Alert: https://github.com/blog/1000-scheduled-maintenance-sunday-night
14:55.13*** join/#gooseproject mdomsch (~mdomsch@cl-283.dal-01.us.sixxs.net)
14:55.49*** join/#gooseproject makfinsky (~imak@145.sub-75-202-57.myvzw.com)
14:57.22makfinskyWoot! Koji has completed all tasks assigned to it! Just kicked off "L" imports.
15:06.17herlomakfinsky: hey
15:06.27herloI am doing the rest of the k and l imports
15:06.36herlobut my connection is slow
15:06.40herlomaybe you should do it
15:06.55herlowe need to do a good portion of a-l
15:13.52makfinskyI kicked off "L" this morning...
15:14.39makfinskySo, the workflow now is slightly different than before, right? I used the same loop as you sent before grapple but took out the skein build command at the end. Is that right?
15:18.07makfinskyJust kicked "A" imports. Am using the machine at home that has FIOS. Should go pretty quickly.
15:18.19makfinskyWe now have 4 builders online! Horray!
15:18.29makfinskys/Horray/Hooray/
15:21.37goozbachnice!
15:22.12makfinskyKicking off "B" imports now.
15:22.47makfinskyI really like this new process! We just need to figure out how to handle failed builds.
15:23.59herlomakfinsky: well, after we get through all of the current builds, we'll run the failed ones a couple more times until we get ones that aren't failing because of deps
15:24.10herloor are but their deps are failing for different reasons
15:24.47makfinskyRight, we need a quick way of listing the failed ones. I was looking last night to see if I could get that easily from the cli from koji and didn't see how at the time.
15:26.44makfinskyDoh! I just realized that I am only working off one of the SRPM isos. I have to go back for second set of srpms.
15:26.54herlokoji has some failed build commands
15:27.08herlomakfinsky: no you don't have to do the 2nd iso, I already imported all of those
15:29.14makfinskyErm... ok.
15:29.24makfinskyYou did the second iso, all of them?
15:30.45makfinskyOdd errors on import - git update-index --add --replace --verbose --stdin' returned exit status 128: fatal: Unable to write new index file
15:33.34makfinskyEh, screw it, am kicking off an import of all the srpms on the first iso. This'll load up koji's task list. :-D
15:34.12herloyep all
15:46.51makfinskyOk, entire srpm list from srpm iso1 is being imported now.
15:50.10herlocool. I had done a good portion of them.
15:50.21makfinskyWoot! If I am reading this correctly - dist-gl6 has 1200+ builds done out of 1800+ already!
15:50.35herlomakfinsky: can you pull down the latest release-2.0 branch into your skein checkout?
15:50.36makfinskyWe are close enough to taste the champagne!
15:50.40herloI know!
15:51.23herlomakfinsky: I changed the ordering of import so that upload happens before the commit, just in case koji gets faster in the future
15:51.38herloI also fixed a few minor bugaboos with unicode values
15:52.03herlomakfinsky: what package gives you that error above?
15:53.33makfinskyDammit... I don't know git well enough to know if I did this correctly. I think I have.
15:53.50makfinskyThere were a few pkgs that gave that error. Let me see.
15:54.16makfinskyOne example - compat-glibc.
15:56.12herlolet me try that one
15:56.51herlomakfinsky: another possible option is to perform the extract, upload and push independently, instead of import
15:57.36herlomakfinsky: also, the skein.log could help
15:58.09herlomakfinsky: compat-glibc worked perfectly for me
16:07.47makfinskyOk, so likely a local issue here.
16:08.34makfinskyI don't have latest skein on the host that's "importing". Since I used the loop from your email, I'm going through and running extract, push, and upload.
16:09.21herlooh, yes, you should update to release-2.0 branch ASAP
16:10.37makfinskyASAP? Does the old code break stuff? If I interrupt the loop, I have to restart from beginning or figure out where it left off and how to start from there.
16:11.54makfinskyI just thought of a good feature for skein, grapple, depsort, etc. - -V for version.
16:12.08herlohehe, I guess that could be useful
16:12.29herlomakfinsky: if you start the loop over, it's not too slow since it will not reimport things that have already been imported
16:13.16herlohttp://fpaste.org/Wetp/ <-- new loop I'm using
16:13.17goosebotTitle: Viewing new skein import loop (at fpaste.org)
16:14.10herlomakfinsky: I'll come up with something for version
16:14.34herlotrying to figure out the best way to do it when we're in development mode
16:14.55herloI suspect there will be another big push to get certain functionality in place down the road.
16:15.05makfinskyYea, very likely.
16:15.05herlomaybe it can spit out the latest merge commit id
16:15.14herloand a date
16:15.19makfinskyThat's an idea. Include date.
16:15.22makfinskyHeheh, jinx.
16:15.25herlolol
16:15.29herlogreat minds
16:15.51makfinskyWow, much simpler loop.
16:15.57makfinskyGreat minds indeed!
16:16.18makfinskyI tell you, only 4 days into getting regular exercise and I already have a lot more energy!
16:16.35herloneeds to start!
16:17.07Nafaiexercise might be a good idea
16:17.12herloI've been eating better, however. I do like having a bit more energy for sure
16:17.21goozbachI've been doing well with my goal to wake up at 5am
16:17.30goozbachinto my second week now
16:17.38NafaiI've been waking up early myself the last few days
16:17.42goozbachonly thing left is to find somewhere to exercise
16:17.42NafaiNot on purpose though
16:17.49goozbach:/ that's a bugger
16:18.11NafaiYeah, why wake up at 6:00-6:30 when I don't have to?
16:18.15NafaiEspecially when it's so freezing
16:18.17herlogoozbach: outside probably works
16:18.34herlonotes that goozbach is in a *warm* state compared to us Northerners :)
16:18.52goozbachwarm =! dry
16:18.59herlolol, so
16:19.01herlowimp
16:19.44makfinskyOk, loop restarted with new skein, I think... Man, I really have to learn git and irssi.
16:20.00herlohehe
16:20.09herlomakfinsky: did you use the release-2.0 branch?
16:20.41makfinskyI think I did it correctly, git pull origin release-2.0...
16:20.51makfinskyThen python setup install --user.
16:21.13makfinskyIf only skein had a print version function... :-D
16:31.16herlowell, that will work for git
16:31.38makfinskyOk, so I guessed correctly at how to do this.
16:31.44makfinskyThat's good to know.
16:31.49herloif you want to do development on skein, I'm going to suggest that you do a fork and pull request
16:31.57herlobecause I would have done it differently
16:32.17herlogit checkout --track -b release-2.0 origin/release-2.0
16:32.41herlothis sets up a new local branch called release-2.0 and will align it with the remote branch at origin/release-2.0
16:33.17herloany subsequent push/pull you do will line up the local and remote branches automatically
16:36.27makfinskyGotcha.
16:37.49makfinskyThe reason I opted not for a fork was that I am pretty far behind right now, in terms of the commits. I will be continuing to develop with you, just don't have the time at this moment to do that. Perhaps later tonight, once I am back at the hotel.
16:45.21herlohehe, no problem. I was just suggesting an alternate path so that when you do get to development stage, it'll be an easier transition
16:46.32makfinskyYea, that does sound a lot better for developing.
16:58.01makfinskyOk, all imports from iso1 done.
16:58.16herlow00t!
16:58.34herlomakfinsky: if you want to run through iso2, to be sure, I wouldn't have a problem with that :)
16:58.42makfinskyWill do.
16:59.18makfinskyWe haven't approved any git repos with incompatible licenses? I am just running through all the srpms on the iso right now and not checking any of that.
16:59.23herloman, I wish I had your connection atm
16:59.36herlomakfinsky: that should have happened at the grant level
16:59.41makfinskyOk, kool.
16:59.46herloit's part of why we do that
17:00.02makfinskyWell, I am on mifi here, ssh'd into FIOS at home and kicking off imports from there.
17:00.26herloahh, yes
17:03.43goozbachherlo: didn't you mention something about repodata errors?
17:04.04goozbachI'm still having a time getting an http install tree for centos on a f16 host
17:04.41goozbachunable to read package metadata verify that your installation directory has been created properly
17:04.41makfinskyWoot, over 300 tasks queued up on koji!
17:04.51goozbachI've done this hundreds of time
17:04.57goozbachcopy the cd to the web root
17:05.03makfinskygoozbach: That issue had to do with the compression type on the repodata.
17:05.10goozbachcreaterepo /files/to/install/tree/
17:05.16goozbachmakfinsky: so how do I get around it?
17:05.17makfinskyNot sure where that was set.
17:05.19goozbach-s sha?
17:05.30makfinskyherlo: Should have more info on that issue.
17:05.40makfinskyI was referring to herlo's repo issues.
17:05.47makfinskyNot sure if that's the same one you are having.
17:06.10goozbachmaybe
17:06.20goozbachme trys with -s sha switch
17:06.24goozbachand --no-database
17:10.40goozbachlooks like that fixed it
17:10.50goozbachmaybe
17:11.21goozbachmaybe this is what was wrong with cobbler :/
17:11.24goozbachgrr
17:11.25goozbachnow I know
17:11.31goozbachbeen a week trying to figure this out
17:38.18herlogoozbach: for el6.0, there is a further problem with yum
17:38.23herloyou should use createrepo -s sha --compress-type=bz2
17:38.32herloif you are using 6.1, it's not so much a problem
17:38.50herlosince yum is fixed
17:42.14goozbachyou're talking 6.0 6.1 from teh installing server perspective, right?
17:42.20goozbachnot as the host for the yum repo
17:42.32herloas the host of the yum repo actually
17:42.40herloand the host
17:42.44herloer installing server
17:42.51herloso yes, to both
17:43.14goozbachI'm using f16 for the cobbler server
17:43.22goozbachand trying to install centos 5.7 and 5.8
17:43.44goozbachso I've figured out that you need at least '-s sha' and maybe '--no-database' for 5.7
17:44.03goozbachyou're saying I need to add --compress-type=bz2 for centos 6.0 to be able to install?
17:44.03herloyeah, f16 needs to do the compression type
17:44.18goozbachor for both 5.7 and 6.0
17:44.21goozbachok
17:44.22herloyes, the bug is with a particular version of yum. centos doesn't have the update
17:51.19goozbachfound one bug which is supposed to be fixed in 2.x of cobbler https://fedorahosted.org/cobbler/ticket/463
17:51.20goosebotTitle: #463 (Cobbler Import does not provide a way to pass flags to createrepo) - cobbler - Trac (at fedorahosted.org)
18:20.19goozbachherlo: that did it!
18:20.24goozbachyay cobbler server working again!
18:44.42*** join/#gooseproject mdomsch (~mdomsch@2001:1938:16a::2)
18:54.55herlogoozbach: w00t!
18:55.09goozbachnow to figure out why @core and @base aren't valid groups....
18:55.14goozbachin my repos :/
18:55.21goozbachdo those still work?
18:55.40goozbachwhen I don't specifiy packages I get 86 rpms installed
18:55.45goozbachwhich doesn't include rpm or yum
18:55.48goozbach:)
18:57.11goozbachit shows up in comps.xml
19:03.50goozbachwow
19:03.53goozbachdoesn't even have ed
19:03.56goozbachnor vim
19:04.00goozbachs/vim/vi
19:06.30herlocreaterepo -g /absolute/path/to/comps.xml /path/to/repo :)
19:06.58herloor wait
19:07.00herloit's actually
19:07.16herlocreaterepo -g /relative/path/to/comps.xml/from/repofiles /path/to/repo :)
19:07.59goozbachI cut and pasted the createrepo line from the cobbler import and added the switches
19:08.06goozbachmaybe I wasn't in the right directory
19:08.19goozbachwhen I modified the kickstart to include yum
19:08.27goozbachI had to manually create an ip address, route
19:08.32goozbachand edit resolv.conf
19:08.41goozbachthen I did yum groupinstall @core @base
19:08.51goozbachthat worked. but may have used the public repos
19:08.54goozbachnot my cobbler server
19:09.40herloahh, okay
19:09.50herloso not related to the path issue of the -g switch of createrepo
19:10.01herloif you are just copying the iso, it should be fine, that is true
19:10.28goozbachcobbler copied the mounted iso
19:10.43herloright
19:11.03goozbachtries again
19:20.47goozbachstill no
19:20.49goozbach:/
19:21.09goozbachI blew away all old comps.xml files and copied the one from the iso and re-ran createrepo
19:21.16makfinskyIf you are using the iso, you still need -g flag to createrepo.
19:21.24makfinskyThere is a comps.xml on the iso.
19:21.26herloif you run createrepo, you will need the -g
19:21.30herloyes, what makfinsky said
19:21.30makfinskyRight.
19:21.34goozbachlooking in /tmp/cache on the installing system I see the comps.xml files
19:21.41goozbachand they contain Core
19:22.01goozbachthis is the creatrepo I ran:
19:22.03goozbachcreaterepo -c cache -s sha --no-database --compress-type=bz2 --groupfile /var/www/cobbler/ks_mirror/CentOS-5.7-x86_64/repodata/comps.xml /var/www/cobbler/ks_mirror/CentOS-5.7-x86_64
19:23.16herlogoozbach: no
19:23.35goozbachjust read the man page
19:23.43herlocreaterepo -c cache -s sha --no-database --compress-type=bz2 --groupfile ../repodata/comps.xml /var/www/cobbler/ks_mirror/CentOS-5.7-x86_64
19:23.46makfinskyHot sweetness. I've run through both srpm iso's and all the remaining imports should be done now!
19:23.46herloprobably
19:23.52herlonice
19:24.16herlomakfinsky: we have cleared 10000 tasks in koji :)
19:24.31goozbachhmm
19:25.08herlogoozbach: oh, wait
19:25.12makfinskyherlo: I take it you are only counting tasks we've submitted. The task id count is at 30k, of which I imagine around 20k are regen-repo tasks that kojira does automagically.
19:25.22herloyes
19:25.26makfinskyRocking!
19:26.06herlocreaterepo -c cache -s sha --no-database --compress-type=bz2 --groupfile ./repodata/comps.xml /var/www/cobbler/ks_mirror/CentOS-5.7-x86_64
19:26.10herlomaybe that will do it
19:26.20herlothe point is that the groupfile has to be relative to where the rpms live iirc
19:26.34goozbachI'm trying that now
19:26.55herlomakfinsky: I'm looking at Tasks 1 through 50 of 10377 on the tasks page
19:27.04herlothe 10377 is what I am using as a reference
19:27.27herlobut yes, I see the 30k task id number as well
19:39.38herlogoozbach: did it work?
19:40.33goozbachnot sure yet
19:40.43herlooh, still running I see
19:41.54goozbachnope
19:42.00goozbachdidn't work
19:55.11herlohmm
19:58.30herlogoozbach: maybe just repodata/comps.xml ?
19:58.37herlowithout the ./
19:58.57goozbachfigured it out
19:59.03goozbachsomething is broken with comps file
19:59.13goozbachI finally got a workable enough system to do debugging with yum
20:02.10herloahh
20:03.11herlogoozbach: this might be helpful then http://yum.baseurl.org/wiki/YumGroups
20:03.12goosebotTitle: YumGroups - yum - Trac (at yum.baseurl.org)
20:07.45goozbachtks
20:08.07goozbachthis seems to be the magic incantation
20:08.09goozbachcreaterepo -c cache -s sha --no-database --groupfile repodata/comps.xml /var/www/cobbler/ks_mirror/CentOS-5.7-x86_64
20:08.16goozbachdon't need to do gz option
20:08.18goozbachto 5.7
20:08.25goozbachbut do need --no-database
20:12.03makfinskyherlo: Is there a way to determine what channels a host is a member of?
20:12.50goozbachyup that's the one
20:13.03makfinskyAlso, I am thinking of bumping up the capacity of the builders from 2 concurrent jobs to 4.
20:16.55herlomakfinsky: capacity on most is already 4
20:17.21makfinskyYou updated the db? By default it's 2 and only way to modify that is psql.
20:17.28herloI did that a while back
20:17.29herlobut I though that was load avg, not josbs
20:17.42makfinskyYes, am referring to load avg.
20:18.16herloyes, I did that on at least the first three
20:18.42makfinskyAh, we haven't used a and b for quite some time. I'll update the db.
20:18.54makfinskyAnd add that to my add-builder.sh script.
20:19.09herlowe could eliminate them I suppose. Assuming we move the nfs mount elsewhere
20:19.31makfinskyLet's work on that after alpha.
20:19.44herlohehe, you mean when we rebuild using GoOSe Linux :)
20:21.07makfinskyIndeed!
20:23.42makfinskyHehe, you were right, you had done the rest of them. Only last night's addition needed a bump.
20:23.48makfinskyI'll see if I can get another builder online tonight.
20:23.51herlo:)
20:23.57herlovery nice
20:24.12herloI'm planning on figuring out the failed builds tonight and rerunning those
20:24.18makfinskyRocking.
20:38.22herlomakfinsky: are you getting emails when a build you own fails too then?
20:38.26herloshalkie: what about you?
20:43.22makfinskyherlo: I have not gotten any emails yet, I don't know if I own anything that's failed yet though.
20:48.19*** join/#gooseproject mdomsch_ (~mdomsch@cl-283.dal-01.us.sixxs.net)
21:33.26herlohmm, interesting
21:33.31herloI have around 70 emails
21:33.38herloand I've received a few recently
21:48.07makfinskyYeah, it seems that most of the pkgs that I own have either successful builds or perhaps the builds that we did for dist-el6 carried over into the dist-gl6 tag.
21:48.25makfinskyI am not sure how to differentiate that right now.
22:10.55herloahh
23:05.04*** join/#gooseproject makfinsky (~imak@190.sub-75-253-42.myvzw.com)

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