Camelia, the Perl 6 bug

IRC log for #gluster-dev, 2012-10-16

| Channels | #gluster-dev index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:13 hagarth joined #gluster-dev
02:25 sunus joined #gluster-dev
02:44 sgowda joined #gluster-dev
02:45 hagarth joined #gluster-dev
03:17 kshlm joined #gluster-dev
03:17 kshlm joined #gluster-dev
03:28 hagarth joined #gluster-dev
04:14 sripathi joined #gluster-dev
04:15 vpshastry joined #gluster-dev
04:43 sripathi joined #gluster-dev
04:58 bala1 joined #gluster-dev
05:00 kshlm joined #gluster-dev
05:00 kshlm joined #gluster-dev
05:17 raghu joined #gluster-dev
05:35 wushudoin joined #gluster-dev
05:44 sripathi joined #gluster-dev
06:05 sripathi joined #gluster-dev
06:13 mdarade joined #gluster-dev
06:20 vpshastry joined #gluster-dev
06:24 badone_home joined #gluster-dev
06:25 badone_ why does the native client use ports below 1024?
06:58 puebele joined #gluster-dev
07:12 hagarth joined #gluster-dev
07:17 puebele1 joined #gluster-dev
07:45 mdarade left #gluster-dev
08:26 spn joined #gluster-dev
08:29 lkoranda joined #gluster-dev
08:30 mdarade1 joined #gluster-dev
08:31 mdarade2 joined #gluster-dev
08:50 kp_ joined #gluster-dev
09:17 badone_home joined #gluster-dev
09:29 kp_ joined #gluster-dev
09:33 bulde1 joined #gluster-dev
10:01 badone_home joined #gluster-dev
10:03 bulde1 joined #gluster-dev
10:14 kp joined #gluster-dev
10:18 sripathi joined #gluster-dev
10:19 sgowda joined #gluster-dev
10:25 badone_home joined #gluster-dev
10:38 sripathi joined #gluster-dev
10:38 sgowda joined #gluster-dev
10:54 mdarade joined #gluster-dev
11:02 mdarade joined #gluster-dev
11:03 mdarade left #gluster-dev
11:05 dobber joined #gluster-dev
11:15 sunus left #gluster-dev
11:19 kkeithley1 joined #gluster-dev
11:21 badone_home joined #gluster-dev
11:33 edward1 joined #gluster-dev
11:47 mdarade1 joined #gluster-dev
11:47 mdarade1 left #gluster-dev
11:49 bulde1 joined #gluster-dev
11:53 sripathi joined #gluster-dev
12:12 mdarade joined #gluster-dev
12:20 sripathi joined #gluster-dev
12:24 mdarade1 joined #gluster-dev
12:31 the-me joined #gluster-dev
12:31 the-me johnmark: ^
12:32 the-me oh and I forget semiosis :)
14:39 semiosis hi the-me
14:40 semiosis i think johnmark has some questions for you, but i have one as well
14:40 semiosis is there a service for debian like launchpad ppas?  something where I can upload source packages and have the binaries built for different releases & architectures?
14:41 johnmark herro
14:41 johnmark ?
14:42 johnmark semiosis: ah, that would be cool
14:42 johnmark the-me: oh hai!
14:42 johnmark the-me: took me a while :)
14:50 johnmark the-me: so yeah, let me know how we can put together debian builds. do you know if the opensuse build server is a good option? or some other way to automate the process? because our in-house debian knowledge is woefully inadequate
14:51 semiosis johnmark: opensuse build server, you say?
14:52 semiosis looks interesting
14:52 semiosis from their wiki page... "No 'compiler farms' of different hardware needed to build packages for different architectures and multiple Linux distributions like Fedora, Debian, Ubuntu, and more."
14:52 semiosis yay!
14:54 johnmark semiosis: heh
14:54 johnmark well, I tried to get it to work once, with less-than-inspiring results
14:54 johnmark if you're able to get anything out of it, I'll give you a gold star :)
14:54 semiosis also, suse is rpm based, so i wonder if they really can build deb packages
14:54 johnmark semiosis: they claim to, but I never got it to actually work
14:55 johnmark I suspect there aren't enough people using it for that
14:55 johnmark the-me: just saw your blog post - thanks
14:55 johnmark the-me: I guess the next question is 2-fold: how difficult is it to create builds for stable and unstable
14:56 johnmark part of me wants to download live images for both and just build it on them
14:56 johnmark but I also want to automate the process
14:57 semiosis there's a program called pbuilder which *should* be able to do the builds for different debian releases and architectures, but i could not get it to build for any targets besides what the running OS was
14:58 johnmark ha, ok
14:59 kkeithley_wfh I'm surprised that debian and ubuntu don't have some equivalent of the Fedora koji build system.
15:00 johnmark kkeithley_wfh: ubuntu does
15:00 johnmark but there is no binary compatibility between ubuntu and debian
15:01 semiosis kkeithley_wfh: ubuntu does, launchpad ppas
15:01 semiosis kkeithley_wfh: it's free & public.
15:01 kkeithley_wfh I wasn't suggesting that there was or should be. Just surprised then that Debian doesn't have something like it.
15:01 johnmark kkeithley_wfh: yeah, as am I. and yes, there should be
15:01 semiosis kkeithley_wfh: and for debian afaik there's one for debian developers, but i dont know of any open to the public
15:03 kkeithley_wfh It may be possible for anyone do do scratch builds in Koji, but I believe you have to be a package maintainer to do official builds in Koji.
15:03 hagarth joined #gluster-dev
15:04 kkeithley_wfh semiosis: I thought, when you said you had launchpad ppas, that those were sets of apt get-able .debs. Is launchpad ppas a service for building them then?
15:05 semiosis kkeithley_wfh: yes it's both a cluster of build servers (and supporting automation infra.) as well as a distribution platform
15:05 semiosis kkeithley_wfh: I upload a GPG-signed source package and launchpad does the build & distribution
15:06 johnmark hagarth: greetings
15:06 hagarth_ joined #gluster-dev
15:06 semiosis which imho is great because it ensures the binaries have not been tampered with
15:06 kkeithley_wfh indeed.
15:06 johnmark semiosis: agreed. it's pretty nice
15:06 hagarth johnmark: hello there
15:06 * johnmark mulls standing up our own launchpad
15:07 johnmark hagarth: good to see you :)
15:07 kkeithley_wfh are the .debs gpg signed by launchpad when they're done?
15:08 hagarth johnmark: :)
15:08 kkeithley_wfh not sure I understand the value of gluster.org having its own launchpad
15:08 johnmark kkeithley_wfh: eventually, we're going to host a bunch of related projects
15:08 johnmark and being able to spit out multiple builds for each would be tres sweet
15:09 semiosis kkeithley_wfh: yes.  when someone adds my ppa to their system (using add-apt-repository) they get my public key installed
15:09 johnmark hagarth: we were wondering about tagging 3.3.1
15:09 semiosis kkeithley_wfh: or one owned by launchpad specifically for my ppa... i'm not really sure how that works
15:09 kkeithley_wfh launchpad adds your signature to the .debs? How does that work?
15:10 semiosis kkeithley_wfh: http://pastie.org/5068202
15:10 hagarth johnmark: sure, that got missed because of the build.gluster.org upgrade
15:10 semiosis kkeithley_wfh: i'm not totally sure :)
15:10 johnmark hagarth: ah, ok
15:10 johnmark hagarth: so for build.gluster.org, is it up to date? we don't need to migrate it for now, right?
15:11 hagarth johnmark: it's good for now
15:11 semiosis kkeithley_wfh: https://help.launchpad.net/Packaging/PPA#Your_PPA.27s_key
15:11 johnmark hagarth: ok. are there still issues with the version of the OS and tools?
15:12 johnmark hagarth: because we can instantiate a new VM and update all of that
15:14 hagarth johnmark: i think the version of the OS is good now.. I was blocked from doing 3.4.0 qa releases because of the OS version
15:14 hagarth I should be able to get it going with this new version
15:16 kkeithley_wfh build.gluster.org is newly updated? What is it running? (And why didn't I know that was happening?)
15:17 hagarth kkeithley_wfh: jenkins on build.gluster.org needed an overhaul
15:19 hagarth kkeithley_wfh: avati upgraded that over the weekend to CentOS 6.x - not sure of the version ( even I got to know around the time of the upgrade)
15:19 johnmark ha
15:20 kkeithley_wfh CentOS? When we can use real RHEL? C'est la vie.
15:20 hagarth kkeithley_wfh: as soon as we can find a better home for *.gluster.org
15:20 johnmark *sigh*
15:21 johnmark hagarth: speaking of, I didn't see a response from sampath
15:21 johnmark I'm hating life at the moment
15:21 johnmark I can't do anything until we resolve the infrastructure problems
15:21 hagarth johnmark: i was busy with the oVirt workshop today, hence could not catch up with sampath
15:22 johnmark hagarth: ah, ok
15:22 hagarth johnmark: will do so tomorrow
15:22 johnmark hagarth: thank you
15:23 kkeithley_wfh oh, gluster.com->gluster.org. The repo files I put up are wrong
15:23 kkeithley_wfh let me fix that
15:23 johnmark kkeithley_wfh: heh :)
15:23 johnmark thanks. yes, preferably before I send out a general announcement
15:25 kkeithley_wfh done
15:31 bala1 joined #gluster-dev
15:31 kkeithley_wfh hmmm. that's weird. When I `ssh username@50.57.69.89` it uses my key and doesn't prompt for a password, but when I `ssh username@download...` I'm prompted for my password. Even though my ~/.ssh/config says use my key for *.gluster.org
15:32 johnmark doh
15:33 kkeithley_wfh did we just lose power in Westford?
15:33 kkeithley_wfh nope
15:34 kkeithley_wfh network glitch?
15:36 johnmark yikes
15:36 kkeithley_wfh que?
15:37 Venkat joined #gluster-dev
15:38 kkeithley_wfh oh, looks like we did lose power in Westford
15:38 johnmark kkeithley_wfh: everyone from westford DIED
15:38 johnmark er... network-speaking at least
15:38 kkeithley_wfh my desktop uptime is five minutes. Must have taken a power hit
15:46 bfoster joined #gluster-dev
16:01 kkeithley_wfh wait, everyone in Westford DIED? That's terrible
16:01 kkeithley_wfh Good thing I'm not there today.
16:33 johnmark :)
16:59 Venkat joined #gluster-dev
17:09 raghu joined #gluster-dev
17:43 hagarth joined #gluster-dev
18:09 kkeithley_wfh semiosis: how do you make your source package for ubuntu launchpad (ppa)?
18:19 jdarcy joined #gluster-dev
18:49 johnmark I have a request for fuse sources
18:49 johnmark where do we keep those?
18:51 a2 johnmark, can you please add "jenkins@build.gluster.org" to gluster-devel and gluster-users in "silent" mode (not receive any mails, but just permitted to send mails to)?
18:51 johnmark a2: sure. will do
18:53 a2 fuse sources? who asks? what exactly is being asked? we have only glusterfs sources..
19:00 johnmark a2: see gluster-users. someone was asking for it. I know we had fuse packages available on the download server
19:00 johnmark but I thought that was a legacy thing
19:03 a2 very very legacy thing.. it stopped compiling against the current kernel 3 years ago (maybe longer)
19:04 johnmark ok. no idea why it was requested. I'll point them to their respective distro sources
19:10 johnmark a2: jenkins@build.gluster.org is now on both lists
19:11 johnmark a2: can gerritt send email to gluster-devel whenever someone submits a patch for review?
19:20 jdarcy Hey, where did build.gluster.whatever go?  I'm getting a generic "Apache was installed here" page.
19:26 a2 jdarcy, yikes.. let me check
19:26 a2 still working on its httpd.conf
19:26 jdarcy Builds seem to be happening, getting reported back to Gerrit, but the web UI is missing.  Not a high priority in the grand scheme of things, actually.
19:27 a2 johnmark, you sure you want that? it's a LOT of noise..
19:29 johnmark a2: I only see about 2-3 per day
19:29 jdarcy I do *NOT* want every patch going to gluster-devel.  Anybody who wants that kind of notification can already get it via their Gerrit watched-project settings.
19:29 johnmark jdarcy: I want it for logging purposes
19:29 johnmark jdarcy: but I'll defer to you guys
19:30 a2 johnmark, 2-3 per day of what?
19:30 johnmark a2: requests for review
19:30 johnmark if that many
19:31 jdarcy Logs might already exist, or we could send commit email to a pseudo-user that formats them for web viewing or something, but IMO sending them to gluster-devel would make that list unusable without setting filters.
19:31 johnmark a2: just for clarification, you want bits.gluster.* and build.gluster.* pointing to the same IP? 184.107.76.12?
19:31 johnmark jdarcy: ok
19:32 a2 johnmark, i don't think you have tried "watch" on glusterfs project in gerrit.. there are atleast 25-30 mails/day
19:32 a2 all that going to gluster-devel is a waste
19:32 johnmark a2: huh. Ok. now I'm wondering what I am watching, because I don't get that many
19:32 johnmark a2: and yeah, if it's that many, forget it
19:33 jdarcy I have 650 Gerrit emails so far this month, 865 for September, etc.
19:33 johnmark ok, so I think the answer to that was a resounding "no" :)
19:33 jdarcy Mmmm, horseburgers.
19:34 a2 oh maybe because johnmark has ticked only "new changes" in his watch settings
19:34 jdarcy Hm.  Let me see if I can filter for those.
19:34 johnmark a2: ok, that would explain it.
19:35 * johnmark is checking settings
19:36 johnmark ah, yup. there are 2 other boxes for "all comments" and "submitted changes"
19:36 johnmark which I left blank
19:37 jdarcy 65 so far this month, so 4+ per day (including weekends).
19:37 a2 johnmark, if you want messages to come to gluster-devel, you will have to register gluster-devel as yet another user/email in gerrit and apply those watch changes for that user
19:38 a2 it is completely outside gerrit administration
19:38 johnmark oh ok
19:38 jdarcy I guess I could live with new-commit changes, though there might still be better ways to achieve the goal of having them logged.
19:38 johnmark jdarcy: fair enough. I'll try to figure something out
19:39 jdarcy It shouldn't be too hard, as such things go, to make up a gluster-watcher@wherever pseudo-user, then scrape their mailbox into whatever format we want.
19:39 johnmark hmm... no, shouldn't be too hard.
19:40 jdarcy Looks like regression takes ~30 minutes to run.
19:41 a2 really.. currently it is still the same sub-10mins test
19:41 semiosis jdarcy: badass shirts!
19:41 a2 the job queue is single threaded.. so maybe the job got scheduled later?
19:42 johnmark semiosis: wha???
19:42 semiosis https://twitter.com/Obdurodo​n/status/258197713156468736
19:43 semiosis don't mess with that guy!
19:43 a2 jdarcy, eventually regression will be a longer test.. smoke will be invoked for every submission (quick and dirty test) and post review, regression will be spawned just pre-commit -- which will be a longer full fledged test
19:43 johnmark semiosis: ha!
19:43 jdarcy a2: OK, which one should trigger Verify+1?
19:43 a2 smoke test gives a +0/-1 verified, regression pass will give a +1/-1 verified
19:44 a2 that's the goal.. i'm still working on the configuration and scripts.. hopefully everything should be good to go live in a day or two
19:46 a2 giving a review +2 will then start off the regression test.. the intention being, not to spend a 30+minute expensive test unless we find it worth merging.. the tests which are being run till today on every submission will continue to do its job, except a pass is +0 and not a +1
19:47 a2 there is a also a plan to make regression test include a test script provided in 'tests/' top level directory as part of the patch.. that way we also get to review the test case too
19:47 johnmark a2: can we make sure to document that somewhere? and do you need any help doing that?
19:48 jdarcy I guess I'll need to figure out how to run carefully-staged test cases across several machines in that infrastructure.
19:48 a2 johnmark, yeah, all this will get reflected in the workflow wiki page
19:48 johnmark a2: excellent
19:49 a2 jdarcy, yeah, a sample multi-node test script pre-shipped in tests/ should help as a template too
19:57 * a2 gets on a customer call
21:29 wushudoin joined #gluster-dev
21:31 spn joined #gluster-dev

| Channels | #gluster-dev index | Today | | Search | Google Search | Plain-Text | summary