Thanks you.
Yes I did fix it for the first error.
For the permission I did follow the technote before and also others
setting. As I was using the apache user (added to the correct group) I have
to chmod everything, which I did. I finally found that I was missing one
chmod in one folder.
It's
Hi Laurent,
Yeah, it's been a while since the community has made improvements to the
ClearCase implementation. We've considered completely redoing it, but
haven't been clear on how many people are still using it, and I'm not sure
how those people who still are are using it in production.
I know
Hi Karthik,
I am facing the same upload diff hanging issue with
post-review and webUI both. Any idea how to resolve this? My
repository type is ClearCase and path is K:/ (clearcase drive).
Please let me know how to resolve this issue.
Regards,
Shambhu.
On Aug 11 2009, 11:15
Hi Karthik,
I followed the link, but didn't get it working. I
have put K:/ as drive letter.
Regards,
Shambhu.
On Tue, Aug 10, 2010 at 1:16 PM, Karthikeyan S karthikeyan1...@gmail.comwrote:
Hi Shambhu,
Please look at the last mail sent by Dan Savilonis in the
I think I got it from here,
http://sourceforge.net/projects/gnuwin32/files/patch/
Karthik
On Thu, Aug 6, 2009 at 8:37 AM, jianquan bianjianq...@gmail.com wrote:
hi Karthik
where can i download the GNU-Patch.exe file? I meet the same issue as
you.
On Jul 22, 10:43 pm, Karthik
Jianquan,
You can follow the link in the windows installation instructions here:
http://review-board.org/docs/manual/dev/admin/installation/windows/
Dan
On Aug 5, 11:07 pm, jianquan bianjianq...@gmail.com wrote:
hi Karthik
where can i download the GNU-Patch.exe file? I meet the same issue as
I've only deployed RB with Clearcase for local testing, but the base
path should just point to the server's view. It doesn't matter locally
that that drive may or may not exist. Clearcase doesn't really fit
into the model of the other supported scms where you can query it to
find out the 'remote'
Hi Dan,
We have given the view drive (Y:/) as a base path directory in the
post-review script and in the review board admin location. Does it
hold good if we are going to run the common centralized review board
server which will be used by group of people? What is the base path we
can give in
Hi Dan,
I have done the changes to make it work with Clearcase. I have
followed all the steps you have mentioned. I am using dynamic
clearcase view only. When I run the post-review script, it hangs when
it tries to post the diff content. But I can see the diff content if I
use output-diff
Well, it looks like you are having the same problem as in another
thread, however both have Clearcase in common. Everything is working
okay in the post-review half of things, so my guess is something is
going wrong trying to access the base files from Clearcase on the
server side.
It looks like
Hi Dan,
I have some questions about post review.
Should we install cygwin for post-review in order to make it work with
Clearcase?
On Jul 17, 9:32 am, Dan Savilonis d...@n-cube.org wrote:
I went through a fresh installation of reviewboard with Clearcase
today and recorded the steps.
Here's
It is not required. post-review simply includes support for cygwin
(i.e. path translation since cleartool does not understand cygwin
paths). My example used sed and xargs to make it easier, so that's the
only reason I suggested having the tools in your path. This feature
can eventually be added
请教一下，你装起来用了没有？
On Jul 17, 10:23 pm, Dan Savilonis d...@n-cube.org wrote:
It is not required. post-review simply includes support for cygwin
(i.e. path translation since cleartool does not understand cygwin
paths). My example used sed and xargs to make it easier, so that's the
only reason I
The requirements to use post-review with clearcase are the same as
with any other version control system. The only difference is you pass
a list of filenames as arguments to the script that you want to
review:
python post-review --server=http://example.com/ file1.c file2.c
file3.c
If
I went through a fresh installation of reviewboard with Clearcase
today and recorded the steps.
Here's what you need to do to get up and running. For the purpose of
this test, I used a dynamic view and was running the server on the
same machine as I had the view and did a review of checked out
Hi Dan,
We did have to modify one line of code in post-review to get it to run
Could you check if those changes are not similar to mine
(http://reviews.review-board.org/r/906/)? I know I had difficulties
submitting a diff for a clearcase repo and those changes fixed it.
I think that we should
Yes, split_lines=True is what I needed to add to get it to work. I'm
less sure about the other changes. They seem like they might be a
problem with your version of python on Windows. I'll add comments to
the review.
Dan
On Jul 10, 11:22 am, Bartlomiej Celary bartlomiej.cel...@gmail.com
wrote:
I will try to write up my experience as I can. (Un)fortunately, we're
not using RB with Clearcase right now, as I run a rogue Clearcase-to-
git system, and use RB with git :)
At minimum right now, we need to get the the line from Bartek's patch
to add split_line=TRUE committed or post-review
18 matches
Mail list logo
