Camelia, the Perl 6 bug

IRC log for #gluster-dev, 2013-04-04

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

All times shown according to UTC.

Time Nick Message
00:52 puebele joined #gluster-dev
01:04 __Bryan__ joined #gluster-dev
01:06 bala joined #gluster-dev
02:51 portante joined #gluster-dev
03:09 vshankar joined #gluster-dev
03:13 bulde joined #gluster-dev
03:34 sgowda joined #gluster-dev
03:57 bulde joined #gluster-dev
03:58 mohankumar joined #gluster-dev
04:04 lalatenduM joined #gluster-dev
04:25 rastar joined #gluster-dev
04:26 hagarth joined #gluster-dev
04:45 yinyin joined #gluster-dev
05:05 aravindavk joined #gluster-dev
05:07 bulde joined #gluster-dev
05:20 bala joined #gluster-dev
05:40 lkoranda joined #gluster-dev
05:45 hagarth joined #gluster-dev
05:55 raghu joined #gluster-dev
05:56 bharata joined #gluster-dev
05:59 puebele1 joined #gluster-dev
06:58 mohankumar joined #gluster-dev
07:01 bala joined #gluster-dev
07:23 yinyin_ joined #gluster-dev
07:24 mohankumar joined #gluster-dev
08:01 hagarth joined #gluster-dev
08:07 _ilbot joined #gluster-dev
08:17 yinyin_ joined #gluster-dev
08:37 yinyin- joined #gluster-dev
09:32 edward1 joined #gluster-dev
09:56 sripathi joined #gluster-dev
10:03 ndevos a2: right, I've filed Bug 948205 for that fusermount change now
10:03 glusterbot Bug http://goo.gl/1PgIL medium, medium, ---, ndevos, ASSIGNED , fusermount-glusterfs should be used instead of fuse's fusermount
10:04 bulde ndevos: isn't it same as http://review.gluster.org/4773
10:04 ndevos bulde: hmm, looks like it
10:07 ndevos bulde: hmm, but bug 811217 that related to that review is an RHS bug
10:07 glusterbot Bug http://goo.gl/tKJ7N is not accessible.
10:12 bulde we need plugin to verify the BUG Id's product before accepting
10:12 ndevos definitely
10:12 bala joined #gluster-dev
10:13 aravindavk joined #gluster-dev
10:24 hagarth joined #gluster-dev
10:26 bulde ndevos: sent the mail
10:30 ndevos bulde: thanks :)
10:39 yinyin joined #gluster-dev
11:09 kkeithley1 joined #gluster-dev
11:27 lalatenduM joined #gluster-dev
11:30 lpabon joined #gluster-dev
11:30 aravindavk joined #gluster-dev
11:35 noche_ joined #gluster-dev
11:40 yinyin joined #gluster-dev
11:48 bala joined #gluster-dev
11:53 aravindavk joined #gluster-dev
11:53 lpabon joined #gluster-dev
11:54 sgowda joined #gluster-dev
12:23 bala joined #gluster-dev
12:26 deepakcs joined #gluster-dev
12:43 hagarth joined #gluster-dev
13:20 portante kkeithley, kkeithly1: either of you there?
13:24 hagarth joined #gluster-dev
13:32 jclift joined #gluster-dev
13:47 hagarth joined #gluster-dev
14:13 wushudoin joined #gluster-dev
14:20 jdarcy joined #gluster-dev
14:31 portante joined #gluster-dev
15:20 portante` joined #gluster-dev
15:25 portante kkeithley, kkeithley1: have you started work on tox?
15:26 kkeithley1 I have not
15:27 portante I am running in to a problem where the tox environment is not able to install the greenlet package due to it compiling it for 32 bits on a 64 bit machine
15:41 hagarth joined #gluster-dev
15:44 aravindavk joined #gluster-dev
16:25 portante kkeithley1: mostly have it solved, just need to address our handling of xattr to accommodate both 0.5.1 and 0.6.4
16:25 portante that will also be the better fix instead of removing the pip-requires line
16:26 portante we'll still need that on Fedora and RHEL since those ship with 0.5.1
17:11 bala joined #gluster-dev
17:34 kkeithley1 is "pip-requires line" the same thing as the /usr/lib/python2.7/site-packages/swi​ft-1.x.x-py2.7.egg-info/requires.txt xattr>=0.4 line?
17:39 bala joined #gluster-dev
18:06 lpabon joined #gluster-dev
18:08 lpabon is there a c style guide for the gluster code?
18:09 lpabon tab size, etc?
18:11 kkeithley1 no tabs, use spaces. indent 8 spaces. Follow the style in (most) of the source.
18:11 lpabon cool, thx
18:20 hagarth joined #gluster-dev
18:23 portante kkeithley1: working on the tox thing, it has become apparent that some of the unit tests are not relying on existing installs of UFO on the host system, which should not be the case, so I am going to fix that before I commit the tox stuff.
18:24 kkeithley1 okay. What about the pip-requires ^^^
18:25 portante I am also fixing the code to work with both pyxattr and xattr
18:26 kkeithley1 huh? pyxattr is xattr, no? The only xattr on my boxes is pyxattr.
18:27 portante there are two competing packages out there: pyxattr and xattr, and while they share a compatibility layer, we don't use it. mea culpa
18:29 portante pip looks xattr on pypi web site and installs that, which is not the same as pyxattr
18:29 portante one could probably change that to pyxattr
18:29 kkeithley1 I'm missing a piece to the puzzle.    I have the pyxattr RPM on my box. During the build the `python setup.py build` conses up the egg_info/requires.txt with xattr>=0.4.
18:30 portante yes, that requires is satified by looking up xattr on pypi, not pyxattr ... see:
18:30 kkeithley1 you're telling me that the egg_info is going to pypi to come up with requires.txt/xattr>=0.4
18:30 kkeithley1 s/telling me/saying/
18:30 portante https://pypi.python.org/pypi?%3Aaction=​search&term=xattr&submit=search
18:30 portante yes
18:32 kkeithley1 But but but. If you untar the swift-1.8.0.tar.gz dled from Launchpad (or even the 1.7.6) it's got an egg_info/requires.txt that has xattr>=0.4, so even the OpenStack people are getting it wrong
18:32 portante I am not sure about that, I think they intend to use xattr from pypi, not pyxattr
18:33 portante the two happen to have a common set of interfaces which let you switch between the two
18:33 portante our use of pyxattr has less overhead, but not sure folks who don't care about performance care
18:33 kkeithley1 The Fedora yum repo only has pyxattr, not xattr
18:34 portante yes
18:36 kkeithley1 so where are we supposed to get an xattr.rpm that's not pyxattr?
18:36 portante we can recode so that our code can work with both
18:36 portante that is part of what I am working on now
18:37 kkeithley1 But what about the egg_info creating the requires.txt with xattr>=0.4?
18:39 kkeithley1 Or are you saying you can make the run-time check for xattr>=0.4 work with the xattr we get from the pyxattr.rpm?
18:39 portante I think you can try changing that to pyxattr, and if that works, not sure what to do. ;)
18:39 kkeithley1 But that's in swift, not in ufo
18:39 portante have not gotten that far yet
18:39 portante details
18:39 portante ;)
18:40 portante What do the Fedora folks do when they package openstack swift?
18:41 kkeithley1 Same thing we do. The swift part of the glusterfs.spec is cut-and-paste from the openstack-swift.spec
18:41 kkeithley1 mostly
18:41 portante and they don't change the requires files?
18:44 kkeithley1 Nope. I tried patching the one that comes out of the tarball, but then when the rpmbuild does `python setup.py install` it regenerates the requires.txt (with xattr>=0.4)
20:15 rastar joined #gluster-dev
22:17 noche_ hi, when I type gluster --mode=script volume status --xml I get two individual XML instead only one XML, it is normal? (gluster 3.3.1-1 rpm for centos6)
22:25 noche_ well, really I get one XML per volume
22:29 badone joined #gluster-dev
23:16 a2 kkeithley, ndevos: /bin/sh: line 0: [: too many arguments
23:16 a2 looks like from rpm.t
23:28 kkeithley1 okay, I'll take a look. I don't think rpm.t has changed. extras/LinuxRPMS/Makefile.am maybe?
23:29 a2 kkeithley - http://build.gluster.org/j​ob/regression/1039/console
23:29 a2 that's where I saw
23:29 kkeithley1 yup, it's there in the swift rebase regression I just ran too

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