IRC log for #gooseproject on 20110615

00:04.11*** join/#gooseproject makfinsky (~imak@c-76-104-102-89.hsd1.va.comcast.net)
00:41.36goozbachherlo: ping
00:41.54herlogoozbach: pong
00:42.11herlogoozbach: eating twizzlers now :)
00:42.34goozbachtwizzlers!
00:42.37goozbachwhatcha got for me?
00:42.48herlotwizzlers are good!
00:43.29herlogoozbach: so, I've been writing a python script to import all of the srpms
00:43.59herloit extracts them and copies the spec and patches into a git repository
00:44.13herloand creates an origin which points to the github repo
00:44.30herloit also creates a github repo if it doesn't already exist
00:44.55herlothe creating of github repo and the local git repo are done in separate python scripts which I import in the import_srpms.py
00:45.53herloI'm trying to think through the process of importing a bit further
00:46.07herlospecifically branching
00:47.41herlofor this import, I'm just using master
00:48.10herlobut for 6.1 and beyond, we probably need to have a el6.1 branch or whatever.
00:48.26herloMy debate right now is whether this should already go into the el6.0 branch during import
00:48.51goozbachhow are you getting the SRPMS?
00:49.03goozbachI'm assuming there will be some x-over between 6.0 and 6.1
00:49.03herlorhel6 iso
00:49.15goozbachahh so isos would make sure they match the release
00:49.17goozbachgood
00:49.21herlo:)
00:49.28herloyup
00:49.36goozbachwhat are both sides of the question?
00:49.45herlothe crossover is simple in my opinion
00:50.09herlojust branch the repo and call it good. Imports could eventually check for diffs, I guess
00:50.34herloboth sides of what question? branching?
00:50.53herloare you looking for arguments for and against for each?
00:52.21goozbachyesh
00:52.29goozbachI don't understand the question in other words
00:52.33herlookay
00:52.43herloso
00:53.35herloI'm just thinking of how we deal with current release
00:53.46herlosince 6.0 is already out, we're going to have a 6.0 branch
00:53.46goozbachoh master vs 6.0 branch
00:53.52goozbachwe should have 6.0 branch
00:54.03herlobut what goes in master in the meantime?
00:57.13goozbachlet's use master till all are imported then create a branch
00:58.28herloso, you realize that means creating branches for several hundred packages, right?
00:58.50goozbachohh it's not one repo
00:58.56herlono way
00:59.04goozbachhence your original question
00:59.07herloI guess it could be
00:59.24herlobut I was thinking that each of the packages should have their own repo. Maybe they shouldn't however.
00:59.59herlogoozbach: https://github.com/gooseproject <-- has a few new repos already
01:01.10goozbachhow does fedora do it?
01:03.32herloseparate repos
01:03.57herlobut it doesn't mean it's right
01:04.25herloin fact, I'm kind of thinking one repo makes a bunch of sense. Since we're just pulling in srpms and not really modifying them too much.
01:04.40goozbachand we're just using the spec file right?
01:04.47herlowell, the spec file and patches
01:04.54herloand a makefile
01:05.03herlohmm, oh I know why
01:05.15herlowe should use a git repo per package
01:05.27goozbachyeah
01:05.29goozbachmakes sense
01:05.31herlobecause koji has to build from source and I don't want to checkout a 100MB
01:05.34goozbachmakefile koji
01:05.39herlorepo each time
01:05.40herloyeah
01:12.26herlookay, so I guess I'll write another piece for branching
01:16.59herlogoozbach: I'll get the buildroot imported this week and we'll see how it goes from there...
01:17.11goozbachnice
01:17.44herlogoozbach: if you get time, have a look at the scripts directory in the bootstrapping repo
01:17.59herlogoozbach: do you mind if I rename the bootstrapping repo to just bootstrap?
01:18.59goozbachcan do
01:19.16herlocool
01:19.29goozbachrenamed
01:19.35goozbachyou'll have to change your git configs
01:19.44herlono problemo
01:19.56herloI could have renamed it,but that's cool :)
01:21.16herlogoozbach: lol, all lowercase :)
01:22.16herlok, renamed lowercase :)
01:22.16goozbachdoh
04:25.29herlomakfinsky: ping-a-ling
04:25.50makfinskyherlo!
04:25.55makfinskyHeya sir.
04:26.28makfinskyI have not yet had a chance to work on the server here. Tomorrow I will be getting the hard drives, I'll have time to work on it either Thursday or Friday.
04:27.09makfinskyHave to take care of a few chores right now. I might be back tonight, I might just pass out too.
04:27.31herlomakfinsky: cool. ATM, I'm just waiting on a place to have the makefile point :)
04:27.35herlothanks for the update
04:27.44makfinsky:)
04:28.07herlogo get your *chores* done
05:09.16*** join/#gooseproject fozzmoo (~fozz@209.41.95.5)
12:23.01*** join/#gooseproject makfinsky (~imak@c-76-104-102-89.hsd1.va.comcast.net)
15:20.57*** join/#gooseproject shalkie (~weechat@li172-53.members.linode.com)
15:37.01*** join/#gooseproject makfinsky (~imak@c-76-104-102-89.hsd1.va.comcast.net)
15:52.12herlomorning
16:59.36*** join/#gooseproject makfinsky (~imak@c-76-104-102-89.hsd1.va.comcast.net)
17:35.48goozbachhttp://people.cs.uu.nl/henkp/mirmon/
17:35.53goozbachfor mirrors when we get there
17:43.25herlogoozbach: I was thinking of using MirrorManager
17:43.35herlowhich I think has monitoring built in
17:43.41herloit's what Fedora uses...
17:45.11herlohttps://fedorahosted.org/mirrormanager/
17:46.08goozbacheeentresting
17:47.30herlo:)
17:55.35goozbachnow I have twizlers!
18:00.28jsmithgoozbach: Curse you!
18:00.43jsmithgoozbach: I've been craving twizzlers since I saw a commercial on TV last night :-p
18:07.19goozbachthe RWC offices have them!
18:07.21goozbachin bulk!
18:07.27goozbachindividually wrapped :(
18:07.39goozbachthat sure rate-limits you
18:11.02jsmith-awayAye... probably better for my diet
18:26.57goozbachneeds food
18:31.33herlogoozbach: w00t! twizzlers!
18:31.45herlogoozbach: we have those here too
23:59.45*** join/#gooseproject fozzmoo (~fozz@209.41.95.5)

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