Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2014-04-14

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

All times shown according to UTC.

Time Nick Message
00:01 tdasilva joined #gluster-dev
00:21 bala joined #gluster-dev
00:30 hagarth joined #gluster-dev
01:00 hagarth joined #gluster-dev
01:33 tdasilva left #gluster-dev
01:40 awheeler joined #gluster-dev
01:41 awheeler joined #gluster-dev
03:06 hchiramm__ joined #gluster-dev
03:09 bharata-rao joined #gluster-dev
03:27 kdhananjay joined #gluster-dev
03:30 shubhendu joined #gluster-dev
03:35 kanagaraj joined #gluster-dev
03:49 itisravi joined #gluster-dev
03:58 shubhendu joined #gluster-dev
04:10 ndarshan joined #gluster-dev
04:13 atinm joined #gluster-dev
04:14 deepakcs joined #gluster-dev
04:30 ndk joined #gluster-dev
04:38 spandit joined #gluster-dev
04:51 ppai joined #gluster-dev
05:29 lalatenduM joined #gluster-dev
05:39 raghu joined #gluster-dev
05:59 shubhendu joined #gluster-dev
06:50 shubhendu joined #gluster-dev
08:32 shubhendu|lunch joined #gluster-dev
08:47 Humble joined #gluster-dev
09:08 Humble joined #gluster-dev
09:19 nishanth joined #gluster-dev
09:19 nthomas joined #gluster-dev
09:47 xavih joined #gluster-dev
09:48 deepakcs ndevos, thanks for closing the mount.glusterfs bug :)
09:49 deepakcs ndevos, i had one comment tho' which i posted in the BZ
09:50 ndevos deepakcs: okay, checking now
09:51 deepakcs ndevos, also what do i need to do with community BZ (https://bugzilla.redhat.com/show_bug.cgi?id=1086421) ? Should i dup it to the RHS one or move it to POST ?
09:51 glusterbot Bug 1086421: is not accessible.
09:52 * deepakcs still learning how to relate community and product BZs ;-)
09:52 deepakcs s/community BZ/RHS BZ/
09:53 aravindavk joined #gluster-dev
09:55 ndevos deepakcs: the main thing is that we should not change bugs filed by community users to the RHS product, we need to clone community bugs to RHS, or the other way around
09:55 deepakcs ndevos, i understand that point
09:55 deepakcs ndevos, i am just asking, whats the next step for taking the RHS bug fwd ? its still as NEW
09:56 ndevos deepakcs: a future version for RHS will automatically include that change, there is nothing needed from you for all I can see
09:57 deepakcs ndevos, so then what happens to the BZ.. it remains in NEW state ?
09:57 ndevos deepakcs: I guess the RHS bug should be moved to POST, a patch has been merged upstream, and a rebase to upstream/master will include the fix
09:58 ndevos deepakcs: I do not know how the tracking is done, you could ask Bala, I think he builds the RHS packages for QA
09:58 deepakcs ndevos, sure
09:58 ndevos deepakcs: but POST sounds good to me :)
09:59 deepakcs ndevos, ok will do
09:59 ndevos deepakcs: and Gerrit now lists both emails, but I think that is just how it works
09:59 deepakcs ndevos, i replied to ur gerrit comment
09:59 ndevos :)
09:59 deepakcs ndevos, ya i hate gerrit
10:00 deepakcs ndevos, u r seeing my rh and gmail id or ?
10:00 ndevos deepakcs: no, the one you used for older patches
10:00 * deepakcs wonders if anyone know how to permanently tell gerrit to forget an email ID regd prev
10:00 * ndevos would love to know too
10:00 deepakcs ndevos, hmm ok i cudn't find a way to remove it
10:01 ndevos deepakcs: maybe we should appoint a Gettit admin of some kind, hagarth and avati know how to manage some things, but they tend to be quite busy...
10:01 deepakcs ndevos, :)
10:02 ndevos deepakcs: I have some mixup with accounts too... you need to pick my personal email, but Gerrit sends it to my @redhat.com one...
10:02 * ndevos has no idea how to fix that
10:03 deepakcs ndevos, i think u can open a/c using say gmail ID but in settings/mailign pref.. register redhat ID.. thus u login to gerrit using openID (gmail one) but notificatiosn are sent to redhat (since u changed in settigns)
10:03 deepakcs ndevos, thats all i know ^^ :)
10:04 deepakcs ndevos, i have other issues.. even after registering my ssh pub key in gerrit.. (ssh review.glsuter.org) says "perm denied (public key)". The same works when i do for review.openstack.org
10:04 ndevos deepakcs: yeah, my personal email is hosted on google
10:05 deepakcs ndevos, i was told this error is fine.. but i wonder why its setup the way it is! ssh test is a basic sanity test, which shud work if u r registering ur pubkey with gerrit..but it doesn't work for review.gluster.org
10:05 ndevos deepakcs: for ssh there may be some delay, I've heard problems with that from others too...
10:05 deepakcs ndevos, Hmm u mean i need to try after some time ?
10:05 ndevos hmm, I get that error too...
10:05 deepakcs ndevos, but i have folks local here who are able to post patches from accounts where they get pubkey error! how does that work then ?
10:06 deepakcs ndevos, thats wrong and misleadign!
10:09 ndevos deepakcs: I have no idea, I'm sure I can post patches, but logging in on git.gluster.com (the remote in my .git/config) fails
10:11 deepakcs ndevos, able to post patches when ssh says perm denied (pubkey) == misleading :)
10:12 ndevos deepakcs: wait, I *can* login, I just have to make sure to set the correct username and pubkey on the ssh-command line
10:12 ndevos deepakcs: 'ssh ndevos@review.gluster.org gerrit' show the gerrit commands for me
10:16 ndevos deepakcs: obviously you can configure defaults and exceptions in ~/.ssh/config, and that breaks or fixes things for me :)
10:17 deepakcs ndevos, works for me now too!.. so i will take some of my words back.. it does seem it took some time for the pubkey to take effect!
10:17 ndevos deepakcs: nice!
10:17 deepakcs ndevos, i created  a username too, so now review.gluster.org and <username>@review.gluster.org both works
10:36 ira_ joined #gluster-dev
11:02 ndk joined #gluster-dev
11:13 ppai joined #gluster-dev
11:24 aravindavk joined #gluster-dev
11:29 kdhananjay1 joined #gluster-dev
11:41 shubhendu|lunch joined #gluster-dev
11:53 bfoster joined #gluster-dev
12:02 itisravi_ joined #gluster-dev
12:36 hagarth joined #gluster-dev
13:01 awheeler joined #gluster-dev
13:19 tdasilva joined #gluster-dev
13:28 itisravi_ joined #gluster-dev
14:08 jobewan joined #gluster-dev
14:31 itisravi_ joined #gluster-dev
14:35 jclift ndevos: Vijay knows how to adjust email addresses in Gerrit, through the database layer.
14:35 jclift ndevos: He did so for mine a while ago.  It seems to have helped.
14:36 ndevos jclift: okay, but I think there are many people (including vijay) that have a weird account (or accounts)
14:36 jclift Heh
14:50 jobewan joined #gluster-dev
14:52 tdasilva joined #gluster-dev
15:01 lalatenduM ndevos, I definitely have plan to learn writing patches for Wireshark, I have used wireshark extensively for debugging nfsv3 and smb1 issues
15:06 ndevos lalatenduM: awesome, just put your name on the TODO list for any items that you would like to have a go at
15:06 ndevos msvbhat: ^ that counts for you too ofcourse!
15:07 ndevos wait, not msvbhat, I think
15:07 ndevos oh, yes, it was msvbhat :D
15:08 msvbhat ndevos: yeah, It's me :)
15:09 ndevos msvbhat: if you have a topic that is on the TODO at https://forge.gluster.org/wireshark/pages/Todo, just put your name next to it, or add topics you're like to do
15:09 glusterbot Title: Gluster Community Forge (at forge.gluster.org)
15:09 msvbhat ndevos: Sure. Adding it now :)
15:09 ndevos msvbhat, lalatenduM: and if you happen to have any questions on using Wireshark with Gluster, let me know and I'll explain how I'd approach the issue you're facing
15:10 ndevos (of course, anyone in this channel or on the mailinglist is free to ask me about that)
15:10 msvbhat ndevos: How do I edit the forge page?
15:11 msvbhat Sory got it
15:11 msvbhat ndevos: My bad :)
15:11 ndevos msvbhat: you got a forg... OK
15:11 ndevos :)
15:11 lalatenduM ndevos, I am occupied with meta xlator as of now, will add my name later (atleast 2 weeks later)
15:12 ndevos lalatenduM: sure, take all the time you need
15:13 ndevos I only fix things or implement new features when I hit an issue with it, there is no timeline for the items on the TODO :)
15:13 lalatenduM ndevos, I have intention of fixing smb 2 dissectors in wireshark :) once I learn how to do it
15:13 lalatenduM ndevos, it is not up2date with MS-SMB2 docs, as MS keep on changing things :)
15:14 ndevos lalatenduM: it's all very similar, implementing small changes/additions is often quite simple
15:14 ndevos lalatenduM: if you let me know (by email?) what teh current issue is, I can probably point you to the right functions and give some hints
15:15 lalatenduM ndevos, awesome :), sure I will
15:15 msvbhat ndevos: Yeah. Even I'm bit weary to commit to a timeline. I can foresee bit hectic time during upcoming release.
15:16 ndk joined #gluster-dev
15:17 ndevos msvbhat: thats no problem at all - if you start something, you can clone the repo from the forge and push your wip (work in progress) branch to it, others can then see whats done so far (even if it fails compiling etc.)
15:19 lalatenduM msvbhat, ndevos getting started and sending the 1st code patch is something we should target :)
15:20 msvbhat ndevos: Sure. Thanks for that... My first TODO will be to fix the docs and links. Then I would choose one of the two I find interesting.
15:20 ndevos lalatenduM: sure, and I am happy to help you with that - when its ready, posting to upstream wireshark is easy too, and those devs are very fast with accepting patches, its great!
15:20 msvbhat ndevos: One of the last two TODO I mean
15:20 msvbhat lalatenduM: Yeah.
15:21 ndevos msvbhat: sure, if thats in the wiki, others (if any) can keep you involved when they start with it before you
15:21 ndevos msvbhat, lalatenduM: thanks for your interest guys! I'll be heading out now, will be back tomorrow
15:22 lalatenduM ndevos, thanks to you too! you are awesome as always :)
15:22 msvbhat ndevos: Sure. Thanks... Catch you later. Have a good day :)
15:23 ndevos have a good evening, you two :)
15:24 lalatenduM good evening:)
15:29 kkeithley joined #gluster-dev
15:34 kkeithley johnmark: ping
15:35 kkeithley hagarth: ping
15:40 hagarth joined #gluster-dev
15:43 kkeithley hagarth: ping
16:08 nthomas joined #gluster-dev
16:10 nishanth joined #gluster-dev
16:15 jclift Anyone know how the Data Liberate thing yesterday went?
16:15 jclift Didn't see mention of it on Twitter from Gluster or JohnMark
16:16 lalatenduM jclift, there are some twits from Red storage handle about it
16:33 systemonkey joined #gluster-dev
16:34 systemonkey joined #gluster-dev
16:59 kkeithley joined #gluster-dev
17:26 nishanth joined #gluster-dev
17:27 nthomas joined #gluster-dev
18:01 hagarth joined #gluster-dev
18:24 lpabon joined #gluster-dev
18:32 kkeithley joined #gluster-dev
19:15 baojg joined #gluster-dev
19:17 baojg joined #gluster-dev
19:38 edward1 joined #gluster-dev
20:00 hagarth joined #gluster-dev
20:47 kkeithley joined #gluster-dev
20:58 jclift kkeithley: Thanks. :)
21:00 jclift kkeithley: I'll remember the separate-BZ-for-each-branch for next time, unless you want me to clone the BZ for this?
21:12 avati joined #gluster-dev
21:46 kkeithley joined #gluster-dev
21:57 hagarth joined #gluster-dev
22:15 kkeithley joined #gluster-dev
22:22 kkeithley jclift: don't bother cloning the bz now, but yeah, next time
22:23 jclift :)
23:25 kkeithley joined #gluster-dev
23:26 hagarth joined #gluster-dev

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