| 02:39.22 | *** join/#gooseproject bochecha_ (~bochecha@175.45.17.220) |
| 02:39.23 | *** join/#gooseproject bochecha_ (~bochecha@fedora/bochecha) |
| 04:27.52 | herlo | bochecha_: hola |
| 04:28.09 | bochecha_ | hi herlo |
| 04:28.26 | herlo | sorry I wasn't around last night. So tired... |
| 04:28.42 | herlo | bochecha_: ooh, that png looks good... |
| 04:28.58 | herlo | I like where you are going with this. I'm seriously going to have to actually try it out soon now :) |
| 04:29.09 | bochecha_ | :D |
| 04:29.32 | bochecha_ | make sure your clone is up to date |
| 04:29.44 | bochecha_ | I pushed some stuff yesterday, that you'll need |
| 04:30.20 | bochecha_ | (when you forked the repo, the app would only work with some data inside the DB, and the form to add data was broken :P) |
| 04:31.02 | herlo | sure |
| 04:31.14 | herlo | I plan to pull in your changes (upstream) and push them to mine (origin) :) |
| 04:31.26 | herlo | I do this with several other git repos |
| 04:31.32 | bochecha_ | yeah, me too |
| 04:31.41 | herlo | seems common enough |
| 04:31.53 | bochecha_ | I just wanted to give you a heads up that what you had at the time you forked was known to not work :P |
| 04:32.20 | herlo | oh, I figured it would not be perfect, at least :) |
| 04:32.26 | herlo | bochecha_: I appreciate the heads up :) |
| 04:32.37 | bochecha_ | it's far from perfect |
| 04:32.48 | bochecha_ | for example, the admin forms have no error handling whatsoever |
| 04:33.09 | bochecha_ | if something bad happens, you get a traceback in the terminal running the app, and the whole web UI stops reacting correctly |
| 04:33.17 | bochecha_ | that obviously needs to be fixed :) |
| 04:33.52 | bochecha_ | but right now, I'd like to finish the prototype so I can start dog-fooding it, and see how well it helps me keeping my distro up to date, what features would be missing, etc... |
| 04:36.43 | herlo | sure, I'm liking where this is going. |
| 04:37.08 | herlo | bochecha_: how does the git dir stuff matter? Do I need to have my repos more like what you are doing? |
| 04:37.16 | bochecha_ | ah |
| 04:37.24 | bochecha_ | it doesn't right now |
| 04:37.33 | herlo | it doesn't work? |
| 04:37.39 | bochecha_ | it's not used |
| 04:37.45 | herlo | oh, ok |
| 04:37.53 | herlo | so how do I track updates? |
| 04:38.20 | bochecha_ | the git stuff is something I will need here, but I'm not sure yet how to implement that correctly, so I haven't committed it yet |
| 04:38.33 | herlo | ok |
| 04:38.36 | bochecha_ | wait, where did you see that git stuff actually? |
| 04:38.51 | herlo | I didn't |
| 04:38.55 | bochecha_ | ah |
| 04:38.57 | bochecha_ | good :) |
| 04:38.57 | herlo | I was just asking how it got updates |
| 04:39.06 | bochecha_ | so |
| 04:39.09 | bochecha_ | is it running? |
| 04:39.23 | herlo | because I thought it was against your git repo. Now I'm thinking it's against koji or your mashed repositories |
| 04:39.33 | herlo | bochecha_: no, I'm not tinkering with it at all yet |
| 04:39.37 | bochecha_ | ah |
| 04:39.49 | herlo | sorry if I gave that impression |
| 04:39.51 | bochecha_ | so the way it works is that when you log in, you can access the admin interface |
| 04:39.58 | herlo | right |
| 04:40.01 | bochecha_ | in there, you configure your "distros" |
| 04:40.15 | herlo | k |
| 04:40.24 | bochecha_ | if you look at that overview screenshot, I have configured the "NBRS 5.0" and "Experimental" distros |
| 04:41.17 | herlo | oh, ok |
| 04:41.21 | bochecha_ | each distro needs: a name (duh!) |
| 04:41.28 | bochecha_ | a koji tag (the stable tag) |
| 04:41.31 | bochecha_ | a git branch (crap, I committed that, it's unused for now) |
| 04:41.43 | bochecha_ | a list of dist tags used in the packages (more on that later) |
| 04:41.52 | bochecha_ | a downstream prefix (more on that later) |
| 04:42.08 | herlo | I love the 'more on that later' branches |
| 04:42.18 | bochecha_ | an optional upstream id (that's if all the packages in your distro come from the same upstream) |
| 04:42.27 | bochecha_ | then you can configure your "upstreams" |
| 04:42.47 | bochecha_ | on the overview screenshots, the upstreams I configured are e.g "RHEL 6", "EPEL 6", or "Fedora 16" |
| 04:43.03 | bochecha_ | each upstream needs: a name (seems a common pattern ;) ) |
| 04:43.08 | herlo | I could see configuring the first two |
| 04:43.15 | bochecha_ | a git branch (wow, why did I commit this!?!?!) |
| 04:43.23 | herlo | lol |
| 04:43.29 | bochecha_ | a list of dist tags (again, we're getting to this) |
| 04:43.34 | herlo | bochecha_: because you want someone to write that :) |
| 04:43.55 | bochecha_ | and a list of base urls (the urls to the SRPMS upstream repositories) |
| 04:44.08 | bochecha_ | no, it's written, just not committed yet until I figure out how I want it to look ;) |
| 04:44.15 | bochecha_ | so |
| 04:44.21 | bochecha_ | once you've configured all this |
| 04:44.35 | bochecha_ | there is a script, which should probably be run as a cron job or something |
| 04:44.47 | bochecha_ | what it does is as follows |
| 04:45.13 | bochecha_ | for each configured distro: |
| 04:45.33 | bochecha_ | <PROTECTED> |
| 04:45.47 | bochecha_ | <PROTECTED> |
| 04:46.00 | bochecha_ | <PROTECTED> |
| 04:46.24 | bochecha_ | <PROTECTED> |
| 04:46.55 | herlo | why not evra? |
| 04:46.56 | bochecha_ | <PROTECTED> |
| 04:47.06 | bochecha_ | because the arch is irrelevant for source packages ;) |
| 04:47.20 | bochecha_ | and that's it for the synchro script |
| 04:47.31 | herlo | oh, you aren't comparing binary pkgs here, I see |
| 04:48.00 | bochecha_ | no, we're building a distro, so we build source packages, hence all we need to compare are source packages :) |
| 04:48.09 | herlo | bochecha_: I'm suspecting I'll have time this weekend to tinker with it. If you have a moment to write this up in a READMe (if you haven't already), I'll definitely read it. |
| 04:48.11 | bochecha_ | and koji builds correspond to source packages |
| 04:48.23 | herlo | right, I understand |
| 04:48.35 | bochecha_ | yeah, I absolutely need to document it |
| 04:48.43 | herlo | w00t! |
| 04:48.44 | bochecha_ | I'll try to do that today |
| 04:48.59 | herlo | even if it's just a terse tutorial, I'm sure I can figure out parts |
| 04:49.11 | bochecha_ | so then, when you display the overview, the app will get all the packages in the DB, grouped by distro then by upstream (because in my case, each package can come from a different upstream) |
| 04:49.14 | herlo | or ask you on Sunday night (your monday) |
| 04:49.27 | bochecha_ | and then the package evr is compared to the upstream evr |
| 04:49.38 | bochecha_ | that's where we get to the "more on that later" parts ;) |
| 04:50.01 | herlo | lol |
| 04:50.03 | bochecha_ | you can't compare "1.0-1.el6_0.1" with "1.0-1.nb5.0.1" |
| 04:50.04 | herlo | yep |
| 04:50.11 | bochecha_ | (nb5.0 is my dist tag) |
| 04:50.13 | herlo | I'm aware how that's problematic |
| 04:50.27 | bochecha_ | because then, my packages always appear as newer, simply because my dist tag is evaluated as "bigger" |
| 04:50.39 | bochecha_ | so the code will stripp the evrs of the dist tags |
| 04:50.49 | bochecha_ | which is why they need to be specified in the admin for the distros and releases |
| 04:50.50 | herlo | yeah, same here |
| 04:51.00 | bochecha_ | finally, there are downstream changes |
| 04:51.00 | herlo | gl6 is greater than el6 :) |
| 04:51.10 | bochecha_ | stuff you have to change to get the packageto build for example |
| 04:51.27 | herlo | is entranced...paying attention... |
| 04:51.34 | bochecha_ | you mark them by ".gooseX" with X the revision of the change, right? |
| 04:51.53 | bochecha_ | just appended to the Release: tag if I understood correctly |
| 04:52.37 | bochecha_ | well, then when you configure your distro in the admin interface, you'd specify that ".goose" is the "downstream prefix" |
| 04:52.44 | bochecha_ | the code will strip that out of the evr too |
| 04:52.52 | bochecha_ | and compare things correctly |
| 04:53.01 | herlo | yes |
| 04:53.04 | bochecha_ | and that's why my latest screenshot finally has some up to date packages :) |
| 04:53.09 | herlo | .goose.1 I think |
| 04:53.09 | githubie | herlo: Error: "goose.1" is not a valid command. |
| 04:53.09 | goosebot` | herlo: Error: "goose.1" is not a valid command. |
| 04:53.12 | herlo | lol |
| 04:53.15 | bochecha_ | (inmy case, the downstream prefix is a simple '.') |
| 04:53.20 | bochecha_ | ah |
| 04:53.28 | bochecha_ | so your downstream prefix would be '.goose.' |
| 04:53.29 | herlo | has to look now |
| 04:53.33 | bochecha_ | simple enough :) |
| 04:54.02 | bochecha_ | technically, I just do: release = release.rsplit(downstream_prefix, 1)[0] |
| 04:54.17 | bochecha_ | there you go, you know everything there is to know about the app :) |
| 04:54.21 | herlo | lol |
| 04:54.23 | herlo | sure I do |
| 04:54.29 | bochecha_ | including the "ignore the git stuff for now" caveat :P |
| 04:54.39 | herlo | will need a refresher just to get started, I think. |
| 04:56.50 | bochecha_ | herlo: here's what the admin UI looks like: http://bochecha.fedorapeople.org/tmp/admin_distros.png |
| 04:56.59 | herlo | looks |
| 04:57.07 | bochecha_ | eventually, I'd like that to display some explanations of each field |
| 04:57.24 | herlo | bochecha_: what browser do you use? |
| 04:57.35 | bochecha_ | (yes, it does look a lot like the "Online accounts" panel in GNOME Control Center :P) |
| 04:57.36 | bochecha_ | Firefox |
| 04:57.43 | bochecha_ | tweaked to make it look like GNOME Web :) |
| 04:57.44 | herlo | nice looking distro there |
| 04:57.57 | herlo | bochecha_: ahh, I was wondering. I see that you search with duckduckgo. :) |
| 04:58.09 | bochecha_ | yes |
| 04:58.39 | herlo | oh, and what is uptrack? |
| 04:58.52 | bochecha_ | I don't bore you with screenshots of the rest of the admin UI, they all look the same (I reuse the same code for all the parts of the admin :P) |
| 04:58.57 | bochecha_ | the name of that app :) |
| 04:59.04 | bochecha_ | didn't you see that you cloned it? ^_^ |
| 04:59.21 | herlo | oh, lol |
| 04:59.30 | herlo | http://www.uptrack.com/ <-- I saw this |
| 04:59.37 | bochecha_ | I am a very creative person, so my artsy senses made me find this unbelievably original name |
| 04:59.50 | bochecha_ | up(stream)track(er) :P |
| 05:00.01 | bochecha_ | oh, crap |
| 05:00.14 | bochecha_ | seems like a bad idea to have chosen this name :-/ |
| 05:00.19 | herlo | lol |
| 05:00.27 | herlo | good thing it's still new |
| 05:00.43 | bochecha_ | yeah |
| 05:00.44 | herlo | maybe streamtrack or upstream |
| 05:00.52 | bochecha_ | but given how Pyramid works, renaming would be a bit of a pain |
| 05:00.53 | herlo | do you know of any app called upstream? |
| 05:00.59 | bochecha_ | (have to rename the module, all the imports, etc...) |
| 05:00.59 | herlo | oh, bummer |
| 05:01.05 | bochecha_ | but it's doable anyway |
| 05:01.05 | herlo | yeah, I get it |
| 05:01.13 | bochecha_ | if you find a good name, just send me a pull request :D |
| 05:01.16 | herlo | hasn't used pyramid yet, though I've heard good things |
| 05:01.20 | herlo | will do |
| 05:01.21 | bochecha_ | it's awesome |
| 05:01.50 | bochecha_ | it's really cool, both for rapid prototyping and more robust highly-scalable stuff |
| 05:01.50 | herlo | yes, it is awesome |
| 05:02.12 | herlo | if you can do this sort of thing so quickly, I am definitely interested |
| 05:02.19 | bochecha_ | it nicely guides you towards doing the right thing, without being opinionated (so you can choose your orm, etc...) |
| 05:02.39 | herlo | hmm, I like opinionated software though. :) |
| 05:02.54 | bochecha_ | what's really cool about pyramid is that the architecture is all very lightweight |
| 05:02.55 | herlo | especially since I'm an opinionated sysadmin. |
| 05:02.58 | bochecha_ | so a view is just a method |
| 05:03.19 | bochecha_ | you have a pyramid shell, and you can just import your views, and call them with dummy requests |
| 05:03.29 | bochecha_ | which is awesome for both debugging and unit testing :) |
| 05:03.41 | bochecha_ | yeah, me too |
| 05:04.04 | bochecha_ | but I have my opinions on the choice of an orm for example, so I don't mind that Pyramid doesn't make the decision for me |
| 05:04.46 | bochecha_ | I think they struck the right balance into making some decision (the web stack, the overall architecture,...) and leaving developers some freedom (the template system, the orm, etc...) |
| 05:05.23 | bochecha_ | I haven't done any kind of web stuff for a few years now, so it's pretty refreshing :) |
| 05:05.46 | bochecha_ | (haha, my overvie wpage now shows this "GoOSe Linux 6" distro, with no packages inside :P) |
| 05:05.51 | herlo | yeah, that's fair |
| 05:06.01 | herlo | nice |
| 05:06.22 | bochecha_ | drops it, nobody cares about that distro anyway :P |
| 05:06.32 | herlo | wait? whoa! |
| 05:06.41 | herlo | prepares the /kick :) |
| 05:06.52 | bochecha_ | anyway, today I want to finish the status pages (up to date packages, and "problematic" packages) |
| 05:07.02 | bochecha_ | and then try to start documenting the whole thing a bit, so others can start playing with it |
| 05:07.23 | bochecha_ | by the way, not all dependencies are in Fedora/EL yet |
| 05:07.28 | herlo | cool. I'm definitely intrigued |
| 05:07.30 | bochecha_ | so you'll need a virtualenv |
| 05:07.41 | herlo | not a problem |
| 05:08.01 | bochecha_ | and some deps are not available in Pypi (rpm, koji, yum) so it has to be a --system-site-packages virtualenv |
| 05:08.16 | bochecha_ | which is a bit nasty as it mixes the stacks :( |
| 05:08.25 | bochecha_ | but not really other choice for now |
| 05:08.39 | bochecha_ | wonders if he wrote that in the README |
| 05:09.00 | herlo | bochecha_: that's actually how I always do my virtualenv. I don't like python taking over my system |
| 05:09.04 | herlo | even in a virtualenv |
| 05:09.12 | bochecha_ | oh, what the hell, that could be someone's first pull request *wink wink* |
| 05:09.40 | herlo | bochecha_: it's not mixing stacks if they are already packaged. It's just avoiding duplication in my mind. |
| 05:09.48 | bochecha_ | not really |
| 05:09.49 | herlo | lol, I could possibly do that soonish... |
| 05:10.07 | bochecha_ | you quickly end up with stuff both installed system-wide and in the virtualenv |
| 05:10.11 | bochecha_ | which can cause all sorts of fun |
| 05:10.28 | bochecha_ | e.g right now deform is not in Fedora, so it's not in the system site-packages |
| 05:10.39 | bochecha_ | but if I ever install it for something else, it's going to be in both |
| 05:10.58 | herlo | right, I get that it works that way. I just find that I *only* have to install things that are not in rpms |
| 05:11.06 | bochecha_ | I usually try to not use virtualenvs at all, but when I have to, I really prefer isolating them completely |
| 05:11.35 | herlo | hmm, I guess I feel differently, though I hate virtualenv most of the time anyway. |
| 05:12.50 | bochecha_ | by the way, I've been talking a lot about "admin UI" |
| 05:13.06 | bochecha_ | if you haven't realized it, it's the "Distros", "Upstreams" and "Users" links in the top bar |
| 05:13.12 | bochecha_ | they only appear once you're logged in |
| 05:13.28 | bochecha_ | and the permission system is incredibly simple (which I'd like to keep that way) |
| 05:13.30 | herlo | right |
| 05:13.40 | herlo | like one admin user? |
| 05:13.45 | bochecha_ | everyone can see the status pages (even ulogged in users) |
| 05:13.57 | bochecha_ | all logged in users are admin and can do everything |
| 05:14.01 | herlo | I don't see what harm there is in keeping most of this public |
| 05:14.08 | bochecha_ | you can create more users, though |
| 05:14.13 | herlo | hmm, interesting. |
| 05:14.13 | bochecha_ | me neither |
| 05:14.16 | herlo | I don't hate that |
| 05:14.38 | bochecha_ | there's also absolutely no reason to show the admin stuff, even in a read-only way (it's completely uninteresting to non-admins) |
| 05:15.01 | herlo | right |
| 05:15.02 | bochecha_ | and it makes the whole permission handling **much** simpler :) |
| 05:15.46 | bochecha_ | (especially all those ajaxy thingies, which I'm not the most comfortable with :P) |
| 05:15.59 | herlo | yeah, me either |
| 05:22.28 | herlo | bochecha_: thanks for the detail, I'm excited! |
| 05:22.35 | bochecha_ | :) |
| 05:23.02 | herlo | one more day of work, then I can play with it. |
| 05:23.02 | bochecha_ | for the first time in the last two years, yesterday I had a global overview of all the package sin our distro, where they came from, and how outdated they are |
| 05:23.09 | bochecha_ | it feels awesome |
| 05:23.35 | herlo | I bet |
| 05:23.40 | bochecha_ | I mean it's all info I could have anyway (from our koji, our git, from upstream repos,...) |
| 05:23.50 | bochecha_ | but seeing it all in one place is a different thing |
| 05:24.13 | herlo | sure. You know, I think this may be interesting to Fedora / RHEL / CentOS folks in some way. |
| 05:24.29 | bochecha_ | Fedora I don't think so |
| 05:24.40 | bochecha_ | Fedora doesn't have an upstream (in the sense of a distro they rebuild) |
| 05:24.42 | herlo | I know a bit of it will likely be useless to Fedora, but there seems to be some possibility of getting data from upstream git repos maybe |
| 05:24.53 | bochecha_ | not really |
| 05:24.58 | herlo | or 'scm' |
| 05:24.59 | bochecha_ | at least not right now |
| 05:25.04 | herlo | right, not 'yet' |
| 05:25.04 | bochecha_ | upstreams are yum repositories |
| 05:25.08 | herlo | just see the potential |
| 05:25.16 | bochecha_ | because that's what I need, and what you guys need |
| 05:25.22 | bochecha_ | maybe later, we'll see |
| 05:26.06 | herlo | right |
| 05:26.14 | herlo | no need to expand beyond for now |
| 05:26.25 | herlo | I'm definitely going to dig in on this and have a look |
| 05:27.07 | bochecha_ | I won't be available over the week-end though |
| 05:27.26 | bochecha_ | my parents are coming to visit me in Hong Kong for the next two weeks, starting Sunday |
| 05:27.41 | bochecha_ | so obviously, spare time won't be used for geeky stuff ;) |
| 05:28.09 | herlo | that's okay |
| 05:28.19 | herlo | I'm sure I can email you with questions and you respond at your leisure. |
| 05:28.29 | herlo | It's not like this is mission critical or anything for goose. :) |
| 05:28.34 | bochecha_ | :) |
| 09:00.10 | *** join/#gooseproject bochecha_ (~bochecha@175.45.17.220) |
| 09:00.10 | *** join/#gooseproject bochecha_ (~bochecha@fedora/bochecha) |
| 16:06.02 | *** join/#gooseproject herlo (~clints@fedora/herlo) |
| 16:13.25 | herlo | goozbach: mind fixing goosebot`'s nick? |
| 16:54.28 | shalkie | GoOSe Morning! |
| 22:26.45 | nb | lol |
| 22:28.04 | herlo | hi shalkie |
| 22:28.10 | herlo | nb: what's up?! :) |
| 22:29.05 | nb | how are you herlo |
| 22:29.18 | nb | greets gooseboot :) |
| 22:30.43 | nb | herlo, hows 6.0-updates going? |
| 22:31.30 | herlo | nb: it's still in the same place as when we last chatted |
| 22:31.41 | herlo | nb: I have been swamped with work. |
| 22:31.43 | herlo | but |
| 22:31.50 | herlo | I think I might have some time this weekend. :) |
| 22:32.21 | herlo | nb: goozbach mentioned that he'd mash the repos, but I've not heard whether it happened or not... |
| 22:32.28 | herlo | that was last week... |
| 22:32.45 | nb | oh |
| 22:33.08 | herlo | nb: I'd like to move forward on this |
| 22:33.28 | herlo | we need a more open way of doing it. But the most important thing is documenting the process... |
| 23:18.59 | nb | yeah, id help with mashing but 1) idk how, and 2) I don't have access |
| 23:19.10 | nb | wonders if he can go ahead and build 6.1 |
| 23:19.45 | herlo | nb: so the trick here is this |
| 23:20.11 | herlo | if we update the goose-release to 6.1 in the proper tag, we can move forward. |
| 23:20.19 | herlo | but you have to add-pkg all the packages, right? |
| 23:21.29 | nb | herlo, i think i already did that |
| 23:21.40 | herlo | yeah, I thought you did too |
| 23:21.43 | nb | add-pkg i mean |
| 23:21.47 | nb | got stuck on goose-release i think |
| 23:21.52 | nb | was waiting for you to do it :) |
| 23:21.53 | herlo | nb: go ahead and try to build goose-release for 6.1 target |
| 23:22.06 | herlo | it'll be a good learning experience. |
| 23:22.59 | herlo | nb: does that sound good? |
| 23:23.03 | nb | wonders what he clonse |
| 23:23.10 | nb | https://github.com/gooselinux/goose-release.git? |
| 23:23.19 | nb | doesn't need to change anything in gooseproject/goose-release.git |
| 23:25.10 | herlo | no |
| 23:25.18 | herlo | or wait |
| 23:25.22 | herlo | I don't remember now |
| 23:25.34 | herlo | looks |
| 23:26.08 | herlo | nb: yeah, gooselinux |
| 23:26.23 | herlo | just have to change the spec file from what I can tell. But I know what the problem was now... |
| 23:26.27 | nb | herlo, i think i was a admin? |
| 23:26.30 | nb | i thought i mean |
| 23:26.36 | herlo | I think you are too |
| 23:26.39 | nb | ERROR: Permission to gooselinux/goose-release.git denied to nbebout. |
| 23:26.45 | herlo | looks |
| 23:27.07 | herlo | k, try again |
| 23:27.15 | herlo | I think I did it on gooseproject, but not on gooselinux |
| 23:27.37 | nb | [nb@desktop goose-release]$ git push |
| 23:27.37 | nb | ERROR: Permission to gooselinux/goose-release.git denied to nbebout. |
| 23:27.37 | nb | fatal: The remote end hung up unexpectedly |
| 23:27.45 | herlo | nb: I know the problem of building 6.1 before 6.0-updates is finished... |
| 23:27.57 | herlo | hmm, I just granted you admin |
| 23:28.22 | herlo | gah! |
| 23:28.32 | herlo | fixes more |
| 23:28.40 | nb | herlo, it is git@github.com:gooselinux/goose-release.git right? |
| 23:28.50 | nb | cloned it as https for some reason, so i fixed it by editing .git/config |
| 23:29.04 | herlo | I don't see that... |
| 23:29.10 | herlo | hmm, hang on. This is strange |
| 23:29.50 | herlo | nb: k, try now |
| 23:30.07 | nb | herlo, worked |
| 23:30.09 | nb | what was wrong? |
| 23:30.16 | nb | herlo, oh, should i have done that on a gl6.1 branch? |
| 23:30.19 | herlo | cool, I had to add the admin group to the gooselinux/goose-release.git repo |
| 23:30.35 | herlo | nb: what branch did you do it on? |
| 23:30.46 | herlo | hopes master |
| 23:30.49 | nb | herlo, you could use Owners and it does it automatically :) although that gives people access to delete stuff and all that which i guess is not good |
| 23:30.51 | nb | herlo, master |
| 23:31.20 | herlo | nb: right, I wanted a separate admins group |
| 23:31.28 | herlo | but I need to make sure it's added to all the repos |
| 23:31.31 | nb | herlo, yeah, sounds like a good idea |
| 23:31.46 | nb | herlo, how is it i build in koji without skein? or will skein work ok now that i manually committed? |
| 23:32.00 | herlo | nb: it should |
| 23:32.09 | nb | but i thought skein built from the release branch? |
| 23:32.12 | herlo | nb: but |
| 23:32.17 | herlo | you need to do some stuff with skein |
| 23:32.20 | nb | oh |
| 23:32.21 | herlo | right |
| 23:32.37 | herlo | skein push -h |
| 23:32.54 | herlo | nb: so I'm planning on redoing skein this summer |
| 23:33.20 | herlo | beacause you should be able to use git in a better way. I've realized some of the flaws of it |
| 23:33.26 | herlo | it == skein |
| 23:33.28 | herlo | anyway, for now |
| 23:33.31 | herlo | just do this |
| 23:33.42 | herlo | git branch gl6.1 |
| 23:33.46 | herlo | git co gl6.1 |
| 23:33.52 | herlo | git push -u origin gl6.1 |
| 23:34.01 | herlo | that should fix the problem for skein to build from the branch |
| 23:34.15 | nb | ugh |
| 23:34.22 | herlo | nb: tha'ts what skein push does |
| 23:34.25 | nb | it doesn't like it because i don't have the git repo in skein's directory |
| 23:34.35 | herlo | what? |
| 23:34.44 | nb | i cloned the gooselinux/goose-release.git myself |
| 23:34.51 | nb | instead of doing it skein's way |
| 23:34.56 | herlo | nb: oh, it just expects it to be in a specific directory |
| 23:35.11 | herlo | yeah, another thing I'm planning to fix. My idea there was bad |
| 23:35.18 | nb | oh, i'll just put it there |
| 23:35.22 | herlo | sorry man... |
| 23:35.40 | herlo | nb: of course, you can configure the dir to be wherever at least :) |
| 23:35.54 | nb | herlo, oh, i just fixed it the easy way |
| 23:35.59 | herlo | :D |
| 23:36.06 | nb | i just moved my git clone of it into the place skein wanted it :) |
| 23:36.30 | herlo | right |
| 23:36.40 | herlo | starts making tickets to fix skein |
| 23:38.14 | githubie | Issue OPENED - gooseproject/skein: #16 (Skein shouldn't care about where the repo lives ) <https://github.com/gooseproject/skein/issues/16> |
| 23:38.20 | herlo | nb: can you give input on this issue? |
| 23:39.06 | nb | sure |
| 23:39.07 | herlo | no rush... just sometime soonish |
| 23:40.06 | herlo | thanks |
| 23:46.35 | herlo | yay! done working for the weekend !! :D |
| 23:46.53 | herlo | nb: gotta go grill some foods, but I should be back on later to hack on things... |
