Re: THRIFT-71 - Debian Packaging

2009-05-11 Thread Eric Evans
[ Michael Greene ] I would also like this, although I'm not sure it's necessary for 0.1. As long as the tarball is correct for 0.1, I would think we could still package it for the various distributions after-the-fact. I'm not sure if the differences between Esteve and Todd's work have been

Re: Thrift 0.1.0-RC1

2009-05-11 Thread Todd Lipcon
On Sat, May 9, 2009 at 7:14 PM, Kevin Clark kevin.cl...@gmail.com wrote: No ivy:settings found for the default reference 'ivy.instance'. A default instance will be used no settings file found, using default... [ivy:retrieve] :: Ivy 2.0.0-rc2 - 20081028224207 :: http://ant.apache.org/ivy/ ::

Re: Thrift 0.1.0-RC1

2009-05-11 Thread David Reiss
It was checked in: http://gitweb.thrift-rpc.org/?p=thrift.git;a=commitdiff;h=f08c0a3 Todd Lipcon wrote: On Sat, May 9, 2009 at 7:14 PM, Kevin Clark kevin.cl...@gmail.com wrote: No ivy:settings found for the default reference 'ivy.instance'. A default instance will be used no settings file

Re: Thrift 0.1.0-RC1

2009-05-11 Thread David Reiss
Oh, but it wasn't added to EXTRA_DIST, so it isn't in the tarball. Will fix. David Reiss wrote: It was checked in: http://gitweb.thrift-rpc.org/?p=thrift.git;a=commitdiff;h=f08c0a3 Todd Lipcon wrote: On Sat, May 9, 2009 at 7:14 PM, Kevin Clark kevin.cl...@gmail.com wrote: No ivy:settings

Re: Thrift 0.1.0-RC1

2009-05-11 Thread Kevin Clark
On Mon, May 11, 2009 at 11:17 AM, David Reiss dre...@facebook.com wrote: Oh, but it wasn't added to EXTRA_DIST, so it isn't in the tarball. Will fix. I *didn't* tag the RC since you were bundling it up. Should we tag it before we merge in changes from trunk? -- Kevin Clark http://glu.ttono.us

Re: Thrift 0.1.0-RC1

2009-05-11 Thread David Reiss
Are we even supposed to tag RCs? Seems like a pain. Kevin Clark wrote: On Mon, May 11, 2009 at 11:17 AM, David Reiss dre...@facebook.com wrote: Oh, but it wasn't added to EXTRA_DIST, so it isn't in the tarball. Will fix. I *didn't* tag the RC since you were bundling it up. Should we tag it

[jira] Updated: (THRIFT-496) Pure python reader/writer

2009-05-11 Thread Alexander Shigin (JIRA)
[ https://issues.apache.org/jira/browse/THRIFT-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Shigin updated THRIFT-496: Attachment: thrift-python-pure-rw.patch Pure python reader/writer

[jira] Created: (THRIFT-496) Pure python reader/writer

2009-05-11 Thread Alexander Shigin (JIRA)
Pure python reader/writer - Key: THRIFT-496 URL: https://issues.apache.org/jira/browse/THRIFT-496 Project: Thrift Issue Type: Improvement Components: Library (Python) Reporter: Alexander Shigin

[jira] Commented: (THRIFT-335) Compact Protocol for Python

2009-05-11 Thread Alexander Shigin (JIRA)
[ https://issues.apache.org/jira/browse/THRIFT-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12708174#action_12708174 ] Alexander Shigin commented on THRIFT-335: - Please, check THRIFT-496. Compact

[jira] Created: (THRIFT-497) TSocket read/peek fails on OS X

2009-05-11 Thread Rush Manbert (JIRA)
TSocket read/peek fails on OS X --- Key: THRIFT-497 URL: https://issues.apache.org/jira/browse/THRIFT-497 Project: Thrift Issue Type: Bug Components: Library (C++) Affects Versions: 0.1

[jira] Updated: (THRIFT-497) TSocket read/peek fails on OS X

2009-05-11 Thread Rush Manbert (JIRA)
[ https://issues.apache.org/jira/browse/THRIFT-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rush Manbert updated THRIFT-497: Attachment: 497-TSocket.cpp.patch Patch fr TSocket.cpp. TSocket read/peek fails on OS X

[jira] Resolved: (THRIFT-493) Stopping TNonblockingServer when it hasn't been starting results in an exception

2009-05-11 Thread Bryan Duxbury (JIRA)
[ https://issues.apache.org/jira/browse/THRIFT-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Duxbury resolved THRIFT-493. -- Resolution: Fixed Committed. Stopping TNonblockingServer when it hasn't been starting

Library versioning

2009-05-11 Thread Eric Evans
Has there been any discussion of how versioning is going to work? In particular, the C++ and C# libraries (at least) use versioning as a means of indicating compatibility. For example, given libthrift.so.0.1.0, libthrift.so.0.2.0, and libthrift.so.0.3.0, one would assume binary compatibility,

[jira] Commented: (THRIFT-491) Ripping raw pthreads out of TFileTransport and associated test issues

2009-05-11 Thread Rush Manbert (JIRA)
[ https://issues.apache.org/jira/browse/THRIFT-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12708245#action_12708245 ] Rush Manbert commented on THRIFT-491: - The changes to Monitor look good and work as

[jira] Created: (THRIFT-498) Compact and Binary native protocols, used at the same time, can cause some issues

2009-05-11 Thread Bryan Duxbury (JIRA)
Compact and Binary native protocols, used at the same time, can cause some issues - Key: THRIFT-498 URL: https://issues.apache.org/jira/browse/THRIFT-498 Project: Thrift

Re: Library versioning

2009-05-11 Thread Chad Walters
I think the general convention is that if the major version number is 0, you should assume binary incompatibility for minor version changes. Once the major version moves to 1, then you can assume that incompatibility will be indicated by a major version revision. Does this match other folks'

[jira] Commented: (THRIFT-495) If you inadvertently try to send without first opening you get a useless exception

2009-05-11 Thread Michael Robellard (JIRA)
[ https://issues.apache.org/jira/browse/THRIFT-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12708297#action_12708297 ] Michael Robellard commented on THRIFT-495: -- Looks appropriate to me traceback now