Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2014-03-19

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

All times shown according to UTC.

Time Nick Message
00:29 bala joined #gluster-dev
01:06 yinyin joined #gluster-dev
02:51 shubhendu joined #gluster-dev
03:02 hagarth joined #gluster-dev
03:54 itisravi joined #gluster-dev
04:05 ndarshan joined #gluster-dev
04:11 yinyin joined #gluster-dev
04:12 kanagaraj joined #gluster-dev
04:47 kshlm joined #gluster-dev
04:49 bala joined #gluster-dev
05:03 deepakcs joined #gluster-dev
05:07 lalatenduM joined #gluster-dev
05:10 kdhananjay joined #gluster-dev
05:19 yinyin joined #gluster-dev
05:43 aravindavk joined #gluster-dev
06:13 lalatenduM can somebody point me to the 3.5 tracker bug?
06:38 hagarth lalatenduM: https://bugzilla.redhat.co​m/show_bug.cgi?id=1049981
06:38 glusterbot Bug 1049981: unspecified, unspecified, ---, vbellur, NEW , 3.5.0 Tracker
06:38 lalatenduM hagarth, thanks
06:40 hagarth jclift: was wondering if you got a chance to look into this - http://review.gluster.org/#/c/6979/
07:05 lalatenduM joined #gluster-dev
08:47 hagarth joined #gluster-dev
09:01 kanagaraj joined #gluster-dev
09:01 raghu joined #gluster-dev
09:02 ndevos jclift: lol, every time the APLS touchpad people post kernel patches, they put us on CC - I blame you for that!
09:13 ndarshan joined #gluster-dev
09:28 kanagaraj joined #gluster-dev
09:32 badone joined #gluster-dev
09:34 hagarth joined #gluster-dev
10:15 badone joined #gluster-dev
10:31 jclift ndevos: Heh.  It's actually been really useful for related issues.
10:32 jclift ndevos: You can ask them to not CC you on them.  They're very flexible. :)
10:32 jclift hagarth: It's on my list of stuff to get back into tomorrow
10:33 hagarth jclift: cool, thanks .. we seem to be in the final lap for 3.5.0
10:33 ndevos jclift: I guess/hope they'll just drop me from CC if I do not respond to them anymore - now it's just CTRL+a to remove them from my INBOX :D
10:33 jclift ndevos: Just ask them.
10:35 ndevos jclift: most people will just add me on CC for other things I dont care about too, these guys are just one drop in a thunderstorm
10:45 jclift hagarth: Should I submit a patch to release-3.5 for disabling geo-rep on EL5?  The patch that's applied atm is only on master
10:45 jclift ndevos: Pretty sure that's what you were trying to point out to me the other day, but I didn't understand at the time
10:46 hagarth jclift: we can do that
10:46 jclift Er...
10:46 jclift hagarth: "we can do that" == "yes, please or that", or "no, we'll do that"  ?
10:47 ndevos jclift: I'm surely missing some details?
10:47 hagarth jclift: yes, please do that :)
10:47 jclift hagarth: :)
10:47 jclift ndevos: You were saying to me the other day that disabling geo-rep on EL5 won't have effect for ages
10:47 jclift ndevos: eg until 3.6
10:48 ndevos jclift: step 1: get a patchs approved+merged in the master branch, step 2: cherry-pick the merged commit into a release-3.* branch, git --ammend the Change-ID and add a reference to the master-branch review
10:48 jclift ndevos: I guess you were meaning "dude, submit that to 3.5 release branch as well"
10:48 jclift ndevos: Yeah
10:48 jclift ndevos: Thanks, I would have missed the "amend the change ID bit"
10:49 ndevos jclift: ah, rigth, yes, if you have the geo-rep disabled in master (3.6), it will still be enabled in 3.5
10:49 ndevos jclift: if geo-rep in 3.5 does not work on el5, you should 'backport' the master change to 3.5 too (with the above cherry-pick)
10:49 jclift Yeah
10:50 jclift There's no chance it'll work for 3.5, so I'll do that today
10:50 ndevos jclift: *and*, 3.4 will still have geo-rep for el5 until it goes EOL - the 3.5 release notes should be very clear about dropping geo-rep support for el5
10:51 jclift ndevos: Should we call it out in the release notes?  It's not a new change, we're just disabling building of it on a platform where it can't work
10:51 * ndevos will be back later
10:51 jclift sure
10:51 ndevos jclift: yes, in the release notes of 3.5, warning any geo-rep users that still run on el5
10:52 jclift k
10:56 jclift hagarth: Btw, added this one to the 3.5 blockers list the other day: https://bugzilla.redhat.co​m/show_bug.cgi?id=1077159
10:56 glusterbot Bug 1077159: high, unspecified, ---, vshastry, ASSIGNED , Quota hard limit not being enforced consistently
10:56 jclift hagarth: Guessing that Varun's already working on it, but I'm not sure.  You might want to confirm with him, just to be safe. :)
11:04 tdasilva left #gluster-dev
11:14 kdhananjay1 joined #gluster-dev
11:19 kanagaraj joined #gluster-dev
11:22 bala joined #gluster-dev
11:24 ndarshan joined #gluster-dev
11:48 hagarth joined #gluster-dev
11:55 jclift Gah.  geo-rep disabling patch for EL5 failed on release-3.5 branch.  Looking into it now
11:56 jclift Seems like it needs the related patch to create the rpmbuild/BUILD directory in place first, so I've submitted that as well
12:10 itisravi joined #gluster-dev
12:45 edward1 joined #gluster-dev
13:04 jclift kshlm: Cool, wasn't sure if the REST server was duplicating or something
13:05 jclift kshlm: Also kind of wondering if they should both use the same Python framework for operating, so people who work on one can easily understand/improve the other?
13:09 kshlm we should get them both talking to each other.
13:10 jclift kshlm: That was the point of my email. ;)
13:12 kshlm Ah, I should have read it completely before speaking further.
13:17 kanagaraj joined #gluster-dev
13:18 ndarshan joined #gluster-dev
13:19 tdasilva joined #gluster-dev
13:23 bala joined #gluster-dev
13:25 jclift kshlm: Hmmm, it's probably a good idea to specifically encourage Aravinda + RJ to discuss using a common framework.  Will email to do that in a sec
13:29 ndk joined #gluster-dev
13:29 jclift hagarth: You around?  Just wondering if the item on Community agenda about 3.6 go/no-go meeting is still relevant
13:30 jclift We had the planning meeting, but I'm not sure what the go/no-go meeting is in relation to that
13:53 tdasilva jclift: very good point on the common framework idea...
13:54 jclift :)
14:18 wushudoin| joined #gluster-dev
14:35 rakkaus_ joined #gluster-dev
14:40 jobewan joined #gluster-dev
14:41 * ndevos looks for lpabon...
14:48 ndevos lalatenduM: I have changed the PATCH_TO_REVIEW state in the bug-life-cycle to POST and added the MODIFIED state
14:49 ndevos lalatenduM: can you edit the diagram to reflect that too>
14:49 ndevos ?
14:49 lalatenduM ndevos, thanks :)
14:50 lalatenduM ndevos, yup, Will create a new image
14:50 * lalatenduM checking the page
14:50 ndevos lalatenduM: thanks!
14:52 ndevos lalatenduM: have you seen https://fedoraproject.org/wiki​/BugZappers/BugStatusWorkFlow ?
14:52 ndevos lalatenduM: I'm wondering about the ON_QA status for our bugs
14:52 lalatenduM ndevos, nope. checking it now
14:54 semiosis :O
14:54 lalatenduM ndevos, yes, I missed it
14:55 lalatenduM ndevos, also the "RESOLVED" part needs to be fixed
14:55 ndevos lalatenduM: but the thing is, we dont know when to move a bug to ON_QA
14:55 ndevos well, we know: it should happen when a release is made
14:56 lalatenduM ndevos, yeah, as of now there is no automated way
14:56 ndevos but, we dont know which bugs are fixed in which release (not automated)
14:56 ndevos lalatenduM: hey, I like your thinking :D
14:57 lalatenduM ndevos, :), I can understand , I am sure we can findout something ( I mean automated way)
14:58 ndevos lalatenduM: it cant be very difficult :)
14:59 kdhananjay joined #gluster-dev
15:00 lalatenduM ndevos, we can put that in the page, it might encourage someone to fix that (including us :) )
15:00 jclift *** Community Meeting in #gluster-meeting time ***
15:00 lalatenduM ndevos, I mean we should have a automated ayy
15:21 sahina joined #gluster-dev
15:37 lpabon joined #gluster-dev
16:01 lalatenduM ndevos, I have put the ON_QA stuff in the doc
16:02 hagarth joined #gluster-dev
16:05 ndevos lalatenduM: thanks!
16:05 ndevos lalatenduM: btw, that bug is different from the <xlator>.so.0.0.0 issue
16:06 lalatenduM ndevos, did you go through all the comments in the bug
16:06 ndevos lalatenduM: yeah, it's about libgfapi.so.6 instead of libgfapi.so.0
16:07 ndevos lalatenduM: its more like https://bugzilla.redhat.com​/show_bug.cgi?id=1077816#c2
16:07 glusterbot Bug 1077816: unspecified, unspecified, ---, gdeschner, NEW , samba-vfs-gluster needs filterrequires for libgfapi.so.6
16:07 lalatenduM ndevos, yeah, the naming change of libgfapi.so.6 happened because .so.0.0.0 is not correct according to standards
16:08 lalatenduM ndevos, yes, u r right
16:09 ndevos lalatenduM: libgfapi.so.0 was wrong, I'm not sure why it was picked to be 6, but the value does not really matter
16:11 lalatenduM ndevos, I think u r in the correct track, sorry for the wrong bug
16:11 ndevos lalatenduM: no problem!
16:12 ndevos lpabon: btw, I've approved your package :)
16:14 lalatenduM ndevos, so the AI abt the so.0.0.0 is abt fixing it?
16:17 lalatenduM ndevos, we should have bug on it, so it will be easy to track
16:21 ndevos lalatenduM: can you file a bug for that and assign it to me?
16:22 lalatenduM ndevos, yeah I can , but not sure if I understand the issue correctly yet
16:23 ndevos lalatenduM: oh, dont worry about it then, I'll file a bug and post a patch
16:24 lalatenduM ndevos, thanks, we have to make the 3.5 release bug depended on it too
16:24 ndevos lalatenduM: sure, I'll do that
16:25 lalatenduM ndevos, thanks :)
16:26 ndevos lalatenduM: you're welcome!
16:37 ndevos lalatenduM: filed as bug 1078365
16:37 glusterbot Bug https://bugzilla.redhat.com:​443/show_bug.cgi?id=1078365 unspecified, unspecified, ---, ndevos, ASSIGNED , New xlators are linked as versioned .so files, creating <xlator>.so.0.0.0
16:38 lalatenduM ndevos, awesome!! thanks
16:42 sas_ joined #gluster-dev
17:15 kanagaraj joined #gluster-dev
17:18 sas_ joined #gluster-dev
17:28 ndevos hagarth: both patches for bug 1078365 are now in regression testing, there should be no problem with including them in release-3.5
17:28 glusterbot Bug https://bugzilla.redhat.com:​443/show_bug.cgi?id=1078365 unspecified, unspecified, ---, ndevos, POST , New xlators are linked as versioned .so files, creating <xlator>.so.0.0.0
17:31 ndevos (well, one of them is for master, the other one for release-3.5)
17:33 [o__o] joined #gluster-dev
19:14 kkeithley joined #gluster-dev
21:13 badone joined #gluster-dev
21:15 badone_ joined #gluster-dev
21:20 yinyin joined #gluster-dev
21:51 tdasilva left #gluster-dev
22:28 yinyin joined #gluster-dev

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