incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Walgran" <jwalg...@gmail.com>
Subject Re: [jira] Closed: (COUCHDB-167) Files can not be attached to documents with forward slashes in their names to simulate a folder hierarchy
Date Tue, 30 Dec 2008 13:56:21 GMT
I saw that an item I had reported has been fixed:

  On Tue, Dec 30, 2008 at 2:06 AM, Chris Anderson (JIRA)
<jira@apache.org> wrote:
  > Chris Anderson closed COUCHDB-167.
  > ----------------------------------
  >
  >    Resolution: Fixed
  >
  > fixed in r729587
  >
  >> Files can not be attached to documents with forward slashes in
their names to simulate a folder hierarchy
  >> ---------------------------------------------------------------------------------------------------------

  https://issues.apache.org/jira/browse/COUCHDB-167

So, I updated my CouchDB source:

  $ cd couchdb/code/folder
  $ svn update
  At revision 730128.

Then ran:

  $ sudo make && sudo make install

Then launched couch with:

  $ sudo -i couchdb
  Apache CouchDB 0.9.0a729389-incubating (LogLevel=info) is starting.
  Apache CouchDB has started. Time to relax.

I ran through my repro steps and say the same issue. When starting up
CouchDB, is the bit of the version number after the "a" the SVN
revision? If so, why isn't it 730128? The release in which Chris fixed
the bug, r729587, is between 729389, reported when couch starts up,
and 730128, the r number on my checkout

To be sure, I checked my source and saw the checkin.

  $ svn log -r 729587
  ------------------------------------------------------------------------
  r729587 | jchris | 2008-12-26 22:55:18 -0500 (Fri, 26 Dec 2008) | 2 lines

  design docs use slashes. attachements with slashes in the name can
be accessed with slashes in the url

  ------------------------------------------------------------------------

Since the code has the proper changes, I must be doing something wrong
in the build/deploy step. Any thoughts on how I can fix this?

-Justin

Mime
View raw message