Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2014-02-11

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

All times shown according to UTC.

Time Nick Message
00:22 hagarth joined #gluster-dev
00:29 overclk joined #gluster-dev
01:07 bala joined #gluster-dev
01:59 shyam joined #gluster-dev
02:16 shyam joined #gluster-dev
02:25 bharata-rao joined #gluster-dev
02:29 shyam joined #gluster-dev
03:05 ilbot3 joined #gluster-dev
03:05 Topic for #gluster-dev is now Gluster Development Channel - http://gluster.org | For general chat go to #gluster | Patches - http://review.gluster.org/ | Channel Logs - https://botbot.me/freenode/gluster-dev/ & http://irclog.perlgeek.de/gluster-dev/
03:05 johnmark joined #gluster-dev
03:20 shubhendu joined #gluster-dev
03:28 kshlm joined #gluster-dev
03:29 kanagaraj joined #gluster-dev
03:38 itisravi joined #gluster-dev
03:46 kanagaraj joined #gluster-dev
03:50 badone__ joined #gluster-dev
04:34 kdhananjay joined #gluster-dev
04:40 ndarshan joined #gluster-dev
04:44 ira joined #gluster-dev
04:44 ppai joined #gluster-dev
04:53 bala joined #gluster-dev
05:06 shyam joined #gluster-dev
05:17 lalatenduM joined #gluster-dev
05:29 hagarth joined #gluster-dev
05:31 spandit joined #gluster-dev
05:56 aravindavk joined #gluster-dev
05:58 raghu joined #gluster-dev
06:03 bulde joined #gluster-dev
06:14 pk1 joined #gluster-dev
06:41 surabhi joined #gluster-dev
06:55 kshlm joined #gluster-dev
09:57 bulde joined #gluster-dev
10:18 bulde joined #gluster-dev
10:55 ppai joined #gluster-dev
11:13 ira joined #gluster-dev
11:19 kkeithley1 joined #gluster-dev
11:55 ndevos kkeithley_: is it not common practise to set "fixed in version" when moving a bug from MODIFIED to ON_QA?
11:56 kkeithley_ oops, yes, it should be
11:56 ndevos MODIFIED being, a patch committed to (dist-)git, and ON_QA a request to test a specific version (or newer)?
11:57 ndevos anyway, for that client_t change, I was going to wait for the nightly build and see if it succeeds now :)
11:58 kkeithley_ which reminds me why I don't like using the same BZ for fixes on multiple branches/versions.
11:59 kkeithley_ and okay wrt waiting for nightly build.
12:02 itisravi_ joined #gluster-dev
12:13 itisravi joined #gluster-dev
12:17 pk1 left #gluster-dev
12:21 surabhi joined #gluster-dev
13:47 bfoster joined #gluster-dev
13:52 hagarth joined #gluster-dev
14:00 ppai joined #gluster-dev
15:19 jclift_ Just registered glusterflow.org/.com.  I'll try to setup GitHub pages for it at some point.
15:22 wushudoin joined #gluster-dev
15:30 johnmark jclift_: sweet!
15:56 * hagarth starts 3.5.0beta3
16:10 hagarth and beta3 is out!
16:15 kkeithley_ No tarball on http://bits.gluster.org/pub/gluster/glusterfs/src/   ?
16:15 shyam joined #gluster-dev
16:15 kkeithley_ But we got RPMs? I thought we were dropping the RPMs?
16:17 kkeithley_ no, sorry, no RPMs. I was looking at something else.
16:26 kkeithley_ I copied it from .../work/releases to /d/pub/..../src
17:48 jobewan joined #gluster-dev
18:08 * semiosis wants tarball
18:33 jclift_ semiosis: https://github.com/gluster/glusterfs/archive/v3.5.0beta3.tar.gz
18:33 semiosis woo!
18:33 jclift_ semiosis: Does that help?
18:33 semiosis no
18:33 semiosis haha
18:33 semiosis you had me for a second
18:34 johnmark wait, that should be feasible
18:34 jclift_ semiosis: As a possible gotcha, that's just GitHub's autotarring of releases.  It's not a specially made tarball that includes a configure run.
18:34 johnmark oh right... meh
18:34 semiosis bingo
18:35 semiosis will there be an "official" release tarball, like usual?
18:35 semiosis that's what i use to make my packages
18:35 jclift_ Well, if we commit the bits that the configure run creates, these generated ones would work.
18:35 semiosis although i *can* use the git tree, i dont normally
18:35 jclift_ We'd prob want to keep them in a separate branch or something to not pollute the main master branch tho.
18:36 jclift_ semiosis: Understood.  You're wanting a canonical (heh) URL you can always refer to or similar yeah?
18:36 semiosis jclift_: every gluster release (qa/beta/ga) so far has included a tarball with autogen.sh already run, all that was left was to run configure and make
18:36 semiosis why is this releaase different?
18:37 semiosis jclift_: i'm not asking for anything special or new
18:37 jclift_ Hmmmm, the "make glusterrpms" process that I'm guessing was used to generate the rpms creates such a tarball on the way through.
18:37 jclift_ semiosis: At a guess, I'm thinking something didn't upload it, or someone forgot.
18:37 semiosis http://download.gluster.org/pub/gluster/glusterfs/3.4/3.4.2/ -- there is a tarball
18:38 semiosis http://download.gluster.org/pub/gluster/glusterfs/qa-releases/3.5.0beta2/ -- there is a tarball
18:38 semiosis etc etc
18:38 jclift_ hagarth: ^^^ Any idea where the tarball for 3.5.0beta3 got to?  The lack of it is delaying the build of Ubuntu packages.
18:38 semiosis just want to know if it's coming, i'll wait
18:38 semiosis if it's never coming then I'll get along without it
18:38 semiosis just want to know
18:39 jclift_ semiosis: Screw waiting, how easy is it to adapt to working with a git checkout and tag?
18:39 semiosis easy
18:40 semiosis i just like having a consistent policy i can point to when people ask how 'official' my packages are
18:40 semiosis i can tell them "I just drop in the official tarball you get on download.gluster.org, and you can verify the md5sums yourself to prove it"
18:42 semiosis if i do the git thing then they have to diff the whole tree to verify my package doesn't have anything extra or missing
18:43 jclift_ Yeah, I understand where you're coming from.  tarball's are far more widely accepted/used.
18:44 jclift_ Saying "Built from git commit [sdfasfasdf]" works, but is understandable by a smaller set of the population
18:45 semiosis jclift_: launchpad makes one of these for each build: https://launchpadlibrarian.net/163958327/glusterfs_3.5.0beta2-ubuntu1~trusty2_source.changes
18:46 semiosis which clearly shows the checksum of the orig.tar.gz, which is the same file as found on download.gluster.org...  pretty much anyone can verify this without knowing anything about git or packaging
18:46 semiosis so it's a nice benefit
18:53 johnmark ugh... more bugs in the beta process. I'm sure we'll figure out by 3.6 :)
19:02 kkeithley_ semiosis: http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.5.0beta3.tar.gz
19:02 semiosis kkeithley_: sweet
19:03 semiosis you know i just realized, i have write access to download.gluster.org now, maybe i dont need to be so paranoid about verifying my packages
19:03 semiosis lol
19:03 semiosis about others* verifying my packages
19:03 kkeithley_ That's the "official" tarball. ttp://download.gluster.org/pub/gluster/glusterfs/qa-releases/3.5.0beta3/ will be there as soon as I put it there.
19:03 wushudoin left #gluster-dev
19:04 kkeithley_ s/ttp/http/
19:05 jclift_ kkeithley_: thx :)
20:54 jclift_ That's weird.  Was the volume status command only added after 3.2>
20:54 jclift_ ?
20:55 * jclift_ wonders where the code for that might be, to git blame it...
20:55 jclift_ Looking...
20:55 semiosis yes
20:55 semiosis 3.3 iirc
20:57 jclift_ thx
20:57 jclift_ Too bad for the guy on 3.2. :(
20:57 semiosis lol yep
21:16 jclift_ semiosis: Do you have a gluster volume around, with NFS running, that you can do an netstat -nltp on?
21:16 * jclift_ wants to know the name of the process that's binding to the NFS port
21:16 semiosis only my 3.1.7 prod cluster :/
21:16 jclift_ My suspicion is that it's glusterfs, but I'm not sure
21:16 jclift_ Heh, k, ignore that.  I'll figure something out.
21:17 jclift_ Aha, I'll just spin up a different vm, and put 3.4 on it then check
21:17 jclift_ semiosis: Hmmmm, does your 3.1.x cluster export NFS?
21:17 semiosis yep
21:18 * jclift_ is wondering if the NFS export thing might be more recent than 3.2.
21:18 jclift_ Oh well, guess not. :)
21:18 semiosis thats how we did the initial data load moving from rackspace to ec2 :)
21:18 jclift_ :)
21:18 semiosis rsync over nfs over openvpn
21:18 semiosis worked great
21:19 jclift_ Interesting.
21:53 kkeithley_ 3.5.0beta3 RPMs for Fedora, RHEL, and CentOS are up in YUM repo at http://download.gluster.org/pub/gluster/glusterfs/qa-releases/3.5.0beta3/
22:32 jobewan joined #gluster-dev

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