What permission to be given to added to group in reviewboard
Hi All, Sorry to bug you guys. We want to allow reviewer to attach or add file to review id he/she is part of reviewer list. what permission should be added to group. Regards, CJ -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: What permission to be given to added to group in reviewboard
Thank you David. Surprise that this is not possible, Can you please let us know what we need to do, to allow permission to add a file to reviewer. On Tuesday, October 8, 2013 12:20:33 PM UTC+5:30, David Trowbridge wrote: This is currently not possible. -David On Mon, Oct 7, 2013 at 11:41 PM, chuck j cjerr...@gmail.com javascript: wrote: Hi All, Sorry to bug you guys. We want to allow reviewer to attach or add file to review id he/she is part of reviewer list. what permission should be added to group. Regards, CJ -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: How to get details for number of times changes are done for review id
Dear All, Please let us know answers for the queries below. Regards, Chuck On Tuesday, October 1, 2013 2:56:36 PM UTC+5:30, chuck j wrote: Dear All, I tried to find below queries to forum, but could not found them, hence asking to experts. 1. Can you please let me know how to fetch number of time the review id has been used to re-raise for review. 2. is there any count of diff-r1 count in database, if yes can you please let me know which tables i can find this details. 3. How to reject the review id, is there any thing present in the reviewbaord. Cheers, Chuck. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Reviewboard: Need to fetch reviewer list and reviewer comments for the review id
Hello Chris, This is urgent requirement. Since I am not good at database and I don't know how mapping of review board database tables are done. Please help me get a query which will fetch me reviewer list and reviewer comments for the review id from reviewboard database from back end. Appreciate your help. Cheers, Chuck -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
How to get details for number of times changes are done for review id
Dear All, I tried to find below queries to forum, but could not found them, hence asking to experts. 1. Can you please let me know how to fetch number of time the review id has been used to re-raise for review. 2. is there any count of diff-r1 count in database, if yes can you please let me know which tables i can find this details. 3. How to reject the review id, is there any thing present in the reviewbaord. Cheers, Chuck. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Can RB client post review request to replica server perforce server.
Thanks Christian for asking more details. Here is how i can explain about the scenario. We have master perforce server ( PF1 ) placed in site 1 ( used as license server) and another perforce server PF2 placed at site 1 having ssl enabled. There is another perforce server PF3 ( ssl enable) which is replica server of PF2, Since this PF3 placed in some remote location (site2) which requires highly security for some reason. The developer at site 2 checkin any changes to PF3 (site2) server, gets replicated back to perforce server at site 1 on PF2 and changes made on PF2 at site 1 gets synced/replicated to perforce server PF3 at site 2. hence I used the term replica server. Our RB server is placed at Site 1 which has two perforce repository registered, 1) PF1 and 2) PF2 with ssl enabled. The transaction between PF2 and PF1 happens over SSL. Since our RB server is common between two sites, when user at site 1 performs review request on any of perforce server i.e PF1 or PF2, RBTools works fine, since I know that PF2 and PF1 is known repository to RB server. Now user at site to also want to perform posting of review request, but since they use PF3 server which is unknown to review board server posting is not happening which i guess is expected. 1. Do we need to add this PF3 server as well in RB server to make posting happen? I know it requires. 2. Does review board support such feature where if we add PF2 as repository, since PF2 is replica of PF3 it will automatically reads server and let us proceed with posting. am i missing something.? -Chuck this master master server is accessible to all the location On Tuesday, June 18, 2013 12:59:56 PM UTC+5:30, Christian Hammond wrote: Hi Chuck, What do you mean by a replica server? Can you go into more detail on the scenario? Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On June 17, 2013 at 10:52:40 PM, chuck j (cjerr...@gmail.com javascript:) wrote: Dear All, We need to know if review board support posting a review request to replica perforce server. we also wants to know what configuration we need to make in review board server to make such posting possible. Any document would be appreciated. I tried to find in our KB but could find any. Thanks in advance. -Chuck. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Can RB client post review request to replica server perforce server.
Dear All, We need to know if review board support posting a review request to replica perforce server. we also wants to know what configuration we need to make in review board server to make such posting possible. Any document would be appreciated. I tried to find in our KB but could find any. Thanks in advance. -Chuck. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Review request reports:Unknown repository paths found
Thanks Chris, rbt works fine for the first instance but failed during re-posting the review request for same change list. why it failed need to look into. but i have made the changes in post-review and its working fine, i see it more stable at this point. Thanks again for help your and you are fabulous person. Cheers, Chuck Jerry On Tuesday, April 23, 2013 3:30:29 PM UTC+5:30, chuck j wrote: Thank you Chris appreciated. I will try this out. On Tuesday, April 23, 2013 3:22:11 PM UTC+5:30, Christian Hammond wrote: Hi, Please try using 'rbt post' instead of post-review, and see if that works better. It has different logic for this than post-review does, and will be replacing post-review completely in a future release. post-review at this point is deprecated. Christian -- Christian Hammond - chi...@chipx86.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Tue, Apr 23, 2013 at 2:45 AM, chuck j cjerr...@gmail.com wrote: Its seems for ssl enabled and configured list present in the reviewboard is not handled in the post-review tool. if isinstance(self.info.path, list): repositories = self.get_repositories() debug(Repositories on Server: %s % repositories) debug(Server Aliases: %s % self.info.path) for repository in repositories: if repository['path'] in self.info.path: self.info.path = repository['path'] break Reviewboard Admin guide says to register ssl enable repository use ssl: prefix, when it gets registered with name ssl:perforce:1234, but self.info.path will give you list of repositories without ssl: prefix hence it die reporting all these messages. Just to let you know that p4 info output gives you Server Address without ssl prefix i.e perforce:1234. Do you guys think the logic to handle multiple repository having ssl enable perforce repository configured needs changes, please let me know if i am wrong. -Chuck On Tuesday, April 23, 2013 1:01:40 PM UTC+5:30, chuck j wrote: Hi All, posting of review request shows Unknown repository paths found but review board server configured with two repositories. List of configured repositories: pf-sa.company.com:1666 ssl:pf-sa-svr1:19773 Unknown repository paths found: p4-area:19773 p4-area.company.com:19773 pf-sa-svr1:19773 pf-sa-svr1.company.com:19773 All the above unknown reported by post-review tool are Server Aliases and are one which is configured with ssl. Following argument passed with post-review tool. post-review --bugs-closed=TAI2343 --branch=MAIN --server= https://svrrb1.na.**company.com/svrrbhttps://svrrb1.na.company.com/svrrb--submit-as=chuck --description-file=/tmp/ **tmpVwAGQY 191269 --p4-port=ssl:pf-sa-svr1:**19773 --repository-url=ssl:pf-sa-**svr1:19773 Why post-review unknown repository even when they are configured properly. What is missing? -Chuck -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Review request reports:Unknown repository paths found
Hi All, posting of review request shows Unknown repository paths found but review board server configured with two repositories. List of configured repositories: pf-sa.company.com:1666 ssl:pf-sa-svr1:19773 Unknown repository paths found: p4-area:19773 p4-area.company.com:19773 pf-sa-svr1:19773 pf-sa-svr1.company.com:19773 All the above unknown reported by post-review tool are Server Aliases and are one which is configured with ssl. Following argument passed with post-review tool. post-review --bugs-closed=TAI2343 --branch=MAIN --server= https://svrrb1.na.company.com/svrrb --submit-as=chuck --description-file=/tmp/tmpVwAGQY 191269 --p4-port=ssl:pf-sa-svr1:19773 --repository-url=ssl:pf-sa-svr1:19773 Why post-review unknown repository even when they are configured properly. What is missing? -Chuck -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Review request reports:Unknown repository paths found
Its seems for ssl enabled and configured list present in the reviewboard is not handled in the post-review tool. if isinstance(self.info.path, list): repositories = self.get_repositories() debug(Repositories on Server: %s % repositories) debug(Server Aliases: %s % self.info.path) for repository in repositories: if repository['path'] in self.info.path: self.info.path = repository['path'] break Reviewboard Admin guide says to register ssl enable repository use ssl: prefix, when it gets registered with name ssl:perforce:1234, but self.info.path will give you list of repositories without ssl: prefix hence it die reporting all these messages. Just to let you know that p4 info output gives you Server Address without ssl prefix i.e perforce:1234. Do you guys think the logic to handle multiple repository having ssl enable perforce repository configured needs changes, please let me know if i am wrong. -Chuck On Tuesday, April 23, 2013 1:01:40 PM UTC+5:30, chuck j wrote: Hi All, posting of review request shows Unknown repository paths found but review board server configured with two repositories. List of configured repositories: pf-sa.company.com:1666 ssl:pf-sa-svr1:19773 Unknown repository paths found: p4-area:19773 p4-area.company.com:19773 pf-sa-svr1:19773 pf-sa-svr1.company.com:19773 All the above unknown reported by post-review tool are Server Aliases and are one which is configured with ssl. Following argument passed with post-review tool. post-review --bugs-closed=TAI2343 --branch=MAIN --server= https://svrrb1.na.company.com/svrrb --submit-as=chuck --description-file=/tmp/tmpVwAGQY 191269 --p4-port=ssl:pf-sa-svr1:19773 --repository-url=ssl:pf-sa-svr1:19773 Why post-review unknown repository even when they are configured properly. What is missing? -Chuck -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Review request reports:Unknown repository paths found
Thank you Chris appreciated. I will try this out. On Tuesday, April 23, 2013 3:22:11 PM UTC+5:30, Christian Hammond wrote: Hi, Please try using 'rbt post' instead of post-review, and see if that works better. It has different logic for this than post-review does, and will be replacing post-review completely in a future release. post-review at this point is deprecated. Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Tue, Apr 23, 2013 at 2:45 AM, chuck j cjerr...@gmail.com javascript: wrote: Its seems for ssl enabled and configured list present in the reviewboard is not handled in the post-review tool. if isinstance(self.info.path, list): repositories = self.get_repositories() debug(Repositories on Server: %s % repositories) debug(Server Aliases: %s % self.info.path) for repository in repositories: if repository['path'] in self.info.path: self.info.path = repository['path'] break Reviewboard Admin guide says to register ssl enable repository use ssl: prefix, when it gets registered with name ssl:perforce:1234, but self.info.path will give you list of repositories without ssl: prefix hence it die reporting all these messages. Just to let you know that p4 info output gives you Server Address without ssl prefix i.e perforce:1234. Do you guys think the logic to handle multiple repository having ssl enable perforce repository configured needs changes, please let me know if i am wrong. -Chuck On Tuesday, April 23, 2013 1:01:40 PM UTC+5:30, chuck j wrote: Hi All, posting of review request shows Unknown repository paths found but review board server configured with two repositories. List of configured repositories: pf-sa.company.com:1666 ssl:pf-sa-svr1:19773 Unknown repository paths found: p4-area:19773 p4-area.company.com:19773 pf-sa-svr1:19773 pf-sa-svr1.company.com:19773 All the above unknown reported by post-review tool are Server Aliases and are one which is configured with ssl. Following argument passed with post-review tool. post-review --bugs-closed=TAI2343 --branch=MAIN --server= https://svrrb1.na.**company.com/svrrbhttps://svrrb1.na.company.com/svrrb--submit-as=chuck --description-file=/tmp/ **tmpVwAGQY 191269 --p4-port=ssl:pf-sa-svr1:**19773 --repository-url=ssl:pf-sa-**svr1:19773 Why post-review unknown repository even when they are configured properly. What is missing? -Chuck -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: post-review is it mandatory to pass ssl prefix in --p4-port option.
Hi David, As you mentioned that adding prefix ssl to --p4-port is not required, i did that but i got message which ask me add ssl to P4PORT. DEBUG:root:Checking for a Perforce repository... DEBUG:root:Running: p4 info DEBUG:root:Running: diff --version DEBUG:root:repository info: Path: pf-sa-perforce:19773, Base path: None, Supports changesets: True INFO:root:Generating diff for changenum 191316 DEBUG:root:Running: p4 describe -s 191316 post-review.exe -o --bugs-closed=TAI3039 --branch=MAIN --server=http://svrrb1.company.com/svr--submit-as=chuck --description-file=c:\users\chuck\appdata\local\temp\tmpgqtcfa 191316 --p4-port=pf-sa-perforce:19773 posting review request... RBTools 0.4.3 Python 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32 bit (Intel)] Running on Windows-Vista-6.1.7601 Home = C:\Users\chuck\AppData\Roaming Current Directory = d:\pf_ch_ws Checking the repository type. Errors shown below are mostly harmless. Finished checking the repository type. HTTP GETting api/info/ Failed to execute command: ['p4', 'describe', '-s', '191316'] ['Failed client connect, server using SSL.\n', 'Client must add SSL protocol prefix to P4PORT.\n'] Please help. -Chuck On Saturday, April 20, 2013 12:11:00 AM UTC+5:30, David Trowbridge wrote: If the p4port on the client matches that on the server, it will use that to figure out which repository to post against. If it doesn't (which is what you're describing), you need to specify it manually, either with command-line arguments or a .reviewboardrc file. -David On Fri, Apr 19, 2013 at 11:38 AM, chuck j cjerr...@gmail.comjavascript: wrote: Hi David, But while posting to non ssl base reviewboard i didn't require .reviewbaordrc. why it's require for this? where this file should be present. What should be content of .reviewboardrc. -chuck. On Friday, April 19, 2013 2:05:56 PM UTC+5:30, David Trowbridge wrote: post-review (and rbt post) shouldn't require the ssl: prefix, but you probably will want to create a .reviewboardrc with the repository name. -David On Fri, Apr 19, 2013 at 1:31 AM, chuck j cjerr...@gmail.com wrote: Hi All, For ssl enabled perforce, while posting a review request, is it mandatory to pass --p4-port='ssl:pf-server:1234' or normal port i.e --p4-port=pf-sserver:1234' will work? Regards, Chuck. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: post-review is it mandatory to pass ssl prefix in --p4-port option.
But adding ssl gives me
HTTP POSTing to http://svrb1.company.com/svrb/api/review-requests/:
{'changenum': '191316', 'submit_as': 'chuck', 'repository':
'pf-sa-perforce:19773'}
Got API Error 206 (HTTP code 400): The repository path specified is not
in the list of known repositories
Error data: {u'stat': u'fail', u'repository': u'pf-sa-perforce:19773',
u'err': {u'msg': u'The repository path specified is not in the list of
known repositories', u'code': 206}}
just let you know in reviewboard server repository is added with name *
ssl:pf-sa-perforce:19773*
Then its seems that somehow rbt is searching the repository with name
pf-sa-perforce:19773 which is incorrect. Any other solution you want me to
try.
On Saturday, April 20, 2013 12:43:00 PM UTC+5:30, David Trowbridge wrote:
post-review will execute the 'p4' command using the port that you're
passing into --p4-port. If you have a valid P4PORT environment variable
that you'd prefer to use, don't pass --p4-port. Since it looks like the
server at pf-sa-perforce:19773 refuses non-SSL connections, then you
probably do need the ssl: prefix.
-David
On Sat, Apr 20, 2013 at 12:10 AM, chuck j cjerr...@gmail.comjavascript:
wrote:
Hi David,
As you mentioned that adding prefix ssl to --p4-port is not required, i
did that but i got message which ask me add ssl to P4PORT.
DEBUG:root:Checking for a Perforce repository...
DEBUG:root:Running: p4 info
DEBUG:root:Running: diff --version
DEBUG:root:repository info: Path: pf-sa-perforce:19773, Base path: None,
Supports changesets: True
INFO:root:Generating diff for changenum 191316
DEBUG:root:Running: p4 describe -s 191316
post-review.exe -o --bugs-closed=TAI3039 --branch=MAIN --server=
http://svrrb1.company.com/svr--submit-as=chuck--description-file=c:\users\chuck\appdata\local\temp\tmpgqtcfa;
191316
--p4-port=pf-sa-perforce:19773
posting review request...
RBTools 0.4.3
Python 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32 bit
(Intel)]
Running on Windows-Vista-6.1.7601
Home = C:\Users\chuck\AppData\Roaming
Current Directory = d:\pf_ch_ws
Checking the repository type. Errors shown below are mostly harmless.
Finished checking the repository type.
HTTP GETting api/info/
Failed to execute command: ['p4', 'describe', '-s', '191316']
['Failed client connect, server using SSL.\n', 'Client must add SSL
protocol prefix to P4PORT.\n']
Please help.
-Chuck
On Saturday, April 20, 2013 12:11:00 AM UTC+5:30, David Trowbridge wrote:
If the p4port on the client matches that on the server, it will use that
to figure out which repository to post against. If it doesn't (which is
what you're describing), you need to specify it manually, either with
command-line arguments or a .reviewboardrc file.
-David
On Fri, Apr 19, 2013 at 11:38 AM, chuck j cjerr...@gmail.com wrote:
Hi David,
But while posting to non ssl base reviewboard i didn't require
.reviewbaordrc. why it's require for this? where this file should be
present. What should be content of .reviewboardrc.
-chuck.
On Friday, April 19, 2013 2:05:56 PM UTC+5:30, David Trowbridge wrote:
post-review (and rbt post) shouldn't require the ssl: prefix, but you
probably will want to create a .reviewboardrc with the repository name.
-David
On Fri, Apr 19, 2013 at 1:31 AM, chuck j cjerr...@gmail.com wrote:
Hi All,
For ssl enabled perforce, while posting a review request, is it
mandatory to pass --p4-port='ssl:pf-server:1234' or normal port i.e
--p4-port=pf-sserver:1234' will work?
Regards,
Chuck.
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/**donate/http://www.reviewboard.org/donate/
Happy user? Let us know at
http://www.reviewboard.org/**users/http://www.reviewboard.org/users/
-~--~~~~--**~~--~--~---
To unsubscribe from this group, send email to
reviewboard...@googlegroups.**com
For more options, visit this group at http://groups.google.com/**
group/reviewboard?hl=enhttp://groups.google.com/group/reviewboard?hl=en
---
You received this message because you are subscribed to the Google
Groups reviewboard group.
To unsubscribe from this group and stop receiving emails from it,
send an email to reviewboard...@googlegroups.**com.
For more options, visit
https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/**donate/http://www.reviewboard.org/donate/
Happy user? Let us know at
http://www.reviewboard.org/**users/http://www.reviewboard.org/users/
-~--~~~~--**~~--~--~---
To unsubscribe from this group, send email to reviewboard...@**
googlegroups.com
For more options, visit this group at http://groups.google.com/**
group/reviewboard?hl=enhttp://groups.google.com/group/reviewboard?hl=en
---
You
Re: post-review is it mandatory to pass ssl prefix in --p4-port option.
Thanks i will try that option too.
Please correct me if the .reviewboardrc content are correct.
REPOSITORY = 'http://ssl:pf-sa-perforce:19773/'
On Saturday, April 20, 2013 12:59:52 PM UTC+5:30, David Trowbridge wrote:
This is where you'd use a .reviewboardrc file with the REPOSITORY setting
or the --repository-url parameter. Please read the post-review
documentation for details.
-David
On Sat, Apr 20, 2013 at 12:26 AM, chuck j cjerr...@gmail.comjavascript:
wrote:
But adding ssl gives me
HTTP POSTing to http://svrb1.company.com/svrb/api/review-requests/:
{'changenum': '191316', 'submit_as': 'chuck', 'repository':
'pf-sa-perforce:19773'}
Got API Error 206 (HTTP code 400): The repository path specified is
not in the list of known repositories
Error data: {u'stat': u'fail', u'repository':
u'pf-sa-perforce:19773', u'err': {u'msg': u'The repository path specified
is not in the list of known repositories', u'code': 206}}
just let you know in reviewboard server repository is added with name *
ssl:pf-sa-perforce:19773*
Then its seems that somehow rbt is searching the repository with name
pf-sa-perforce:19773 which is incorrect. Any other solution you want me to
try.
On Saturday, April 20, 2013 12:43:00 PM UTC+5:30, David Trowbridge wrote:
post-review will execute the 'p4' command using the port that you're
passing into --p4-port. If you have a valid P4PORT environment variable
that you'd prefer to use, don't pass --p4-port. Since it looks like the
server at pf-sa-perforce:19773 refuses non-SSL connections, then you
probably do need the ssl: prefix.
-David
On Sat, Apr 20, 2013 at 12:10 AM, chuck j cjerr...@gmail.com wrote:
Hi David,
As you mentioned that adding prefix ssl to --p4-port is not required, i
did that but i got message which ask me add ssl to P4PORT.
DEBUG:root:Checking for a Perforce repository...
DEBUG:root:Running: p4 info
DEBUG:root:Running: diff --version
DEBUG:root:repository info: Path: pf-sa-perforce:19773, Base path:
None, Supports changesets: True
INFO:root:Generating diff for changenum 191316
DEBUG:root:Running: p4 describe -s 191316
post-review.exe -o --bugs-closed=TAI3039 --branch=MAIN --server=
http://svrrb1.**company.com/svr--submit-as=**chuckhttp://svrrb1.company.com/svr--submit-as=chuck--description-file=c:\users\
**chuck\appdata\local\temp\**tmpgqtcfa 191316
--p4-port=pf-sa-perforce:**19773
posting review request...
RBTools 0.4.3
Python 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32 bit
(Intel)]
Running on Windows-Vista-6.1.7601
Home = C:\Users\chuck\AppData\Roaming
Current Directory = d:\pf_ch_ws
Checking the repository type. Errors shown below are mostly
harmless.
Finished checking the repository type.
HTTP GETting api/info/
Failed to execute command: ['p4', 'describe', '-s', '191316']
['Failed client connect, server using SSL.\n', 'Client must add SSL
protocol prefix to P4PORT.\n']
Please help.
-Chuck
On Saturday, April 20, 2013 12:11:00 AM UTC+5:30, David Trowbridge
wrote:
If the p4port on the client matches that on the server, it will use
that to figure out which repository to post against. If it doesn't
(which
is what you're describing), you need to specify it manually, either with
command-line arguments or a .reviewboardrc file.
-David
On Fri, Apr 19, 2013 at 11:38 AM, chuck j cjerr...@gmail.com wrote:
Hi David,
But while posting to non ssl base reviewboard i didn't require
.reviewbaordrc. why it's require for this? where this file should be
present. What should be content of .reviewboardrc.
-chuck.
On Friday, April 19, 2013 2:05:56 PM UTC+5:30, David Trowbridge wrote:
post-review (and rbt post) shouldn't require the ssl: prefix, but
you probably will want to create a .reviewboardrc with the repository
name.
-David
On Fri, Apr 19, 2013 at 1:31 AM, chuck j cjerr...@gmail.com wrote:
Hi All,
For ssl enabled perforce, while posting a review request, is it
mandatory to pass --p4-port='ssl:pf-server:1234' or normal port i.e
--p4-port=pf-sserver:1234' will work?
Regards,
Chuck.
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/**don**ate/http://www.reviewboard.org/donate/
Happy user? Let us know at
http://www.reviewboard.org/**use**rs/http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to
reviewboard...@googlegroups.**co**m
For more options, visit this group at http://groups.google.com/**
group**/reviewboard?hl=enhttp://groups.google.com/group/reviewboard?hl=en
---
You received this message because you are subscribed to the Google
Groups reviewboard group.
To unsubscribe from this group and stop receiving emails from it,
send an email to reviewboard...@googlegroups.**co**m.
For more options, visit https://groups.google.com/**grou**
ps/opt_out https
Re: post-review is it mandatory to pass ssl prefix in --p4-port option.
Thanks David and I really appreciate your responses. I did searched review
board forum to get the response for such basic questions when there are
complex system are in place. Failing to get the answer we have emailed you
for the answer. Unless we start using the tool within the organization and
demonstrate to actual end user, how i can propose for the support contract
to my company. I am doing POC and making it strong case within an
organization to use such feature provided by this fabulous tool.
But its unfair to say that we are wasting your time.
Thanks again apologies for wasting your precious time.
On Saturday, April 20, 2013 1:31:51 PM UTC+5:30, David Trowbridge wrote:
The contents within the quotes on that line should be the name that you
assigned to your repository entry in the reviewboard admin. If you named
the repository http://ssl:pf-sa-perforce:19773/ then that would be correct,
but that's kind of a funny name. I really can't say whether or not it's
correct, because it depends on what you put into the admin form.
Please, please try things out and read the documentation before asking
your questions here. It would only take 30 seconds for you to have tested
if it's correct. You're really starting to waste our time, and unless you'd
like to enter into a support contract and pay us for our time, we can't
keep answering these sorts of basic questions.
-David
On Sat, Apr 20, 2013 at 12:56 AM, chuck j cjerr...@gmail.comjavascript:
wrote:
Thanks i will try that option too.
Please correct me if the .reviewboardrc content are correct.
REPOSITORY = 'http://ssl:pf-sa-perforce:19773/'
On Saturday, April 20, 2013 12:59:52 PM UTC+5:30, David Trowbridge wrote:
This is where you'd use a .reviewboardrc file with the REPOSITORY
setting or the --repository-url parameter. Please read the post-review
documentation for details.
-David
On Sat, Apr 20, 2013 at 12:26 AM, chuck j cjerr...@gmail.com wrote:
But adding ssl gives me
HTTP POSTing to http://svrb1.company.com/svrb/**
api/review-requests/http://svrb1.company.com/svrb/api/review-requests/:
{'changenum': '191316', 'submit_as': 'chuck', 'repository':
'pf-sa-perforce:19773'}
Got API Error 206 (HTTP code 400): The repository path specified is
not in the list of known repositories
Error data: {u'stat': u'fail', u'repository':
u'pf-sa-perforce:19773', u'err': {u'msg': u'The repository path specified
is not in the list of known repositories', u'code': 206}}
just let you know in reviewboard server repository is added with name *
ssl:pf-sa-perforce:19773*
Then its seems that somehow rbt is searching the repository with name
pf-sa-perforce:19773 which is incorrect. Any other solution you want me to
try.
On Saturday, April 20, 2013 12:43:00 PM UTC+5:30, David Trowbridge
wrote:
post-review will execute the 'p4' command using the port that you're
passing into --p4-port. If you have a valid P4PORT environment variable
that you'd prefer to use, don't pass --p4-port. Since it looks like the
server at pf-sa-perforce:19773 refuses non-SSL connections, then you
probably do need the ssl: prefix.
-David
On Sat, Apr 20, 2013 at 12:10 AM, chuck j cjerr...@gmail.com wrote:
Hi David,
As you mentioned that adding prefix ssl to --p4-port is not required,
i did that but i got message which ask me add ssl to P4PORT.
DEBUG:root:Checking for a Perforce repository...
DEBUG:root:Running: p4 info
DEBUG:root:Running: diff --version
DEBUG:root:repository info: Path: pf-sa-perforce:19773, Base path:
None, Supports changesets: True
INFO:root:Generating diff for changenum 191316
DEBUG:root:Running: p4 describe -s 191316
post-review.exe -o --bugs-closed=TAI3039 --branch=MAIN --server=
http://svrrb1.**company**.com/svr--submit-as=**chuckhttp://svrrb1.company.com/svr--submit-as=chuck--description-file=c:\users\
**c**huck\appdata\local\temp\**tmpgqt**cfa 191316
--p4-port=pf-sa-perforce:**1977**3
posting review request...
RBTools 0.4.3
Python 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32
bit (Intel)]
Running on Windows-Vista-6.1.7601
Home = C:\Users\chuck\AppData\Roaming
Current Directory = d:\pf_ch_ws
Checking the repository type. Errors shown below are mostly
harmless.
Finished checking the repository type.
HTTP GETting api/info/
Failed to execute command: ['p4', 'describe', '-s', '191316']
['Failed client connect, server using SSL.\n', 'Client must add SSL
protocol prefix to P4PORT.\n']
Please help.
-Chuck
On Saturday, April 20, 2013 12:11:00 AM UTC+5:30, David Trowbridge
wrote:
If the p4port on the client matches that on the server, it will use
that to figure out which repository to post against. If it doesn't
(which
is what you're describing), you need to specify it manually, either
with
command-line arguments or a .reviewboardrc file.
-David
On Fri, Apr 19, 2013 at 11:38 AM, chuck j cjerr
post-review is it mandatory to pass ssl prefix in --p4-port option.
Hi All, For ssl enabled perforce, while posting a review request, is it mandatory to pass --p4-port='ssl:pf-server:1234' or normal port i.e --p4-port=pf-sserver:1234' will work? Regards, Chuck. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
HELP: post-review tools report Got API Error 206 (HTTP code 400) for ssl enabled perforce.
Dear All,
I googled it for the above error message for ssl enabled repository but
could found any appropriate help need please ..
We have now attached ssl enabled perforce to review board server, now
posting of review request gives us error what is missing... please see
debug output log.
Note: On the same server posting of review request on non ssl perforce
server are working fine.
DEBUG:root:Checking for a Perforce repository...
DEBUG:root:Running: p4 info
DEBUG:root:Running: diff --version
DEBUG:root:repository info: Path: pf-sa-perforce:19773, Base path: None,
Supports changesets: True
INFO:root:Generating diff for changenum 191316
DEBUG:root:Running: p4 describe -s 191316
DEBUG:root:Processing edit of //path/to/depot/tools/assembly/README.txt
DEBUG:root:Writing //path/to/depot/tools/assembly/README.txt#1 to
c:\users\chuck\appdata\local\temp\tmp-s6buh
DEBUG:root:Running: p4 print -o c:\users\chuck\appdata\local\temp\tmp-s6buh
-q //path/to/depot/tools/assembly/README.txt#1
DEBUG:root:Running: diff -urNp c:\users\chuck\appdata\local\temp\tmp-s6buh
D:/pf_ch_ws\depot\tools\MAIN\tools\assembly\README.txt
post-review.exe -o --bugs-closed=TAI3039 --branch=MAIN --server=
http://company.com/svrb --submit-as=chuck
--description-file=c:\users\chuck\appdata\local\temp\tmpsghdd6 191316
--p4-port=ssl:pf-sa-perforce:19773
posting review request...
RBTools 0.4.3
Python 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32 bit
(Intel)]
Running on Windows-Vista-6.1.7601
Home = C:\Users\chuck\AppData\Roaming
Current Directory = d:\pf_ch_ws
Checking the repository type. Errors shown below are mostly harmless.
Finished checking the repository type.
HTTP GETting api/info/
Warning: //path/to/depot/tools/assembly/README.txt in your changeset is
unmodified
HTTP GETting api/
HTTP GETting http://company.com/svrb/api/info/
Using the new web API
Attempting to create review request on pf-sa-perforce:19773 for 191316
Submitting the review request as chuck
HTTP POSTing to http://company.com/svrb/api/review-requests/:
{'changenum': '191316', 'submit_as': 'chuck', 'repository':
'pf-sa-perforce:19773'}
Got API Error 206 (HTTP code 400): The repository path specified is not
in the list of known repositories
Error data: {u'stat': u'fail', u'repository': u'pf-sa-perforce:19773',
u'err': {u'msg': u'The repository path specified is not in the list of
known repositories', u'code': 206}}
There was an error creating this review request.
The repository path pf-sa-perforce:19773 is not in the
list of known repositories on the server.
Ask the administrator to add this repository to the Review Board server.
For information on adding repositories, please read
http://www.reviewboard.org/docs/manual/dev/admin/configuration/repositories/
-Chuck
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/reviewboard?hl=en
---
You received this message because you are subscribed to the Google Groups
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: post-review is it mandatory to pass ssl prefix in --p4-port option.
Hi David, But while posting to non ssl base reviewboard i didn't require .reviewbaordrc. why it's require for this? where this file should be present. What should be content of .reviewboardrc. -chuck. On Friday, April 19, 2013 2:05:56 PM UTC+5:30, David Trowbridge wrote: post-review (and rbt post) shouldn't require the ssl: prefix, but you probably will want to create a .reviewboardrc with the repository name. -David On Fri, Apr 19, 2013 at 1:31 AM, chuck j cjerr...@gmail.com javascript: wrote: Hi All, For ssl enabled perforce, while posting a review request, is it mandatory to pass --p4-port='ssl:pf-server:1234' or normal port i.e --p4-port=pf-sserver:1234' will work? Regards, Chuck. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
www.reviewboard.org not accessible.
Do you guys noticed? -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Error during adding Repository to SSL enabled perforce.
Sorry for multiple mails but i have no option to fetch help from you expect. How to make review board point to new P4API.so I have noticed that after p4python build it generates library libssl.so.1.0.0, I googled it and could not found any relevant answer but i guess that's the expected behavior. Its seems review board reporting the below message. P4.connect()] Connect to server failed; check $P4PORT. SSL library must be at least version 1.0.1. now that i have deleted the older version P4.* files, still i no success. -Chuck On Tuesday, April 9, 2013 11:46:21 AM UTC+5:30, chuck j wrote: All the P4 files present at /usr/local/lib/python2.7/site-packages On Tuesday, April 9, 2013 11:11:39 AM UTC+5:30, Christian Hammond wrote: Yeah, it's possible it's grabbing that one instead. If p4python is successfully built using OpenSSL, the only thing I can think of to cause that error would be Review Board using an older copy somehow. Where's the new P4.* files? Christian -- Christian Hammond - chi...@chipx86.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Apr 8, 2013, at 10:39 PM, chuck j cjerr...@gmail.com wrote: Here are some more information: I can see there was old P4Python-2008.2-py2.7.egg-info file present at site-packages folder, But i had make sure this version's P4.py, P4.pyc, P4.pyo, P4API.so are moved to some safe place. Will this file make any difference. cat easy-install.pth import sys; sys.__plen = len(sys.path) ./setuptools-0.6c11-py2.7.egg ./python_memcached-1.47-py2.7.egg ./recaptcha_client-1.0.6-py2.7.egg ./python_dateutil-1.5-py2.7.egg ./flup-1.0.3.dev_20110405-py2.7.egg ./PIL-1.1.6-py2.7-linux-x86_64.egg ./python_ldap-2.3.13-py2.7-linux-x86_64.egg ./MySQL_python-1.2.3-py2.7-linux-x86_64.egg ./ReviewBoard-1.7.6-py2.7.egg ./pytz-2013b-py2.7.egg ./Pygments-1.6-py2.7.egg ./paramiko-1.10.0-py2.7.egg ./mimeparse-0.1.3-py2.7.egg ./Markdown-2.3.1-py2.7.egg ./docutils-0.10-py2.7.egg ./django_pipeline-1.2.24-py2.7.egg ./Djblets-0.7.11-py2.7.egg ./django_evolution-0.6.9-py2.7.egg ./Django-1.4.5-py2.7.egg ./pycrypto-2.6-py2.7-linux-x86_64.egg ./feedparser-5.1.3-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) On Tuesday, April 9, 2013 10:39:52 AM UTC+5:30, chuck j wrote: Hi Chris, Reviewboard is using the same version of python for which i have provided example as below [GCC 4.1.2 20080704 (Red Hat 4.1.2-46)] on linux2 Type help, copyright, credits or license for more information. import P4 There are no Two version of p4python installed, how do i figure it out. i can see my site-packages contains following files after p4python build and install i.e P4.py, P4.pyc, P4.pyo, P4API.so On Tuesday, April 9, 2013 12:45:35 AM UTC+5:30, Christian Hammond wrote: Is Review Board using the same version of Python? Any chance there are now two copies of p4python installed? Christian On Apr 8, 2013, at 4:01, chuck j cjerr...@gmail.com wrote: Dear All, This is very critical, I am still not able to add SSL enabled perforce repository to reviewboard, Please help me. Since my machine was not having openssl 1.0.1, i need to build and install this version of openssl. I followed the instruction from document, downloaded openssl 1.0.1e ./config --prefix=/usr/local --openssldir=/usr/local/openssl zlib zlib-dynamic shared make make test make install Then i did following step Edit /etc/ld.so.conf add to paths... /usr/local/lib64 Update the run-time linker... # ldconfig verified with below command: ldd /usr/local/bin/openssl libssl.so.1.0.0 = /usr/local/lib64/libssl.so.1.0.0 (0x2b08a088c000) libcrypto.so.1.0.0 = /usr/local/lib64/libcrypto.so.1.0.0 (0x2b08a0af1000) libdl.so.2 = /lib64/libdl.so.2 (0x003b2ac0) libc.so.6 = /lib64/libc.so.6 (0x003b2a40) /lib64/ld-linux-x86-64.so.2 (0x003b2a00) /usr/local/bin/openssl version OpenSSL 1.0.1e 11 Feb 2013 Then I build p4python with --ssl swtich. python setup.py build --apidir /root/work/src/p4api-2012.2.585708 --ssl /usr/local/lib64 API Release 2012.2 running build running build_py creating build creating build/lib.linux-x86_64-2.7 copying P4.py - build/lib.linux-x86_64-2.7 running build_ext building 'P4API' extension creating build/temp.linux-x86_64-2.7 gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DID_OS=LINUX26X86_64 -DID_REL=2012.2 -DID_PATCH=549493 -DID_API=2012.2/585708 -DID_Y=2012 -DID_M=11 -DID_D=05 -I/root/work/src/p4api-2012.2.585708 -I/root/work/src/p4api-2012.2.585708/include/p4 -I/usr/local/include/python2.7 -c P4API.cpp -o build/temp.linux-x86_64-2.7/P4API.o -DOS_LINUX -DOS_LINUX26 -DOS_LINUXX86_64 -DOS_LINUX26X86_64 cc1plus
Re: Error during adding Repository to SSL enabled perforce.
As i said since my machine was not having openssl1.0.1 installed, hence we need to build openssl first from source which gets installed at /usr/local/ where these libssl.so gets placed at /usr/local/lib64 and its link also gets created with the name libcrypto.so.1.0.0, libssl.so.1.0.0 I restarted my Apache before adding the repository, its seems review board when try to perform p4.connect and it couldn't per that steps and reports errors. If am able to perform p4.connect from outside, which P4API.so does review board referring to. On Tuesday, April 9, 2013 12:38:26 PM UTC+5:30, Christian Hammond wrote: These e-mails keep ending up directed to me. Let's be sure they're all on the mailing list. Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Apr 9, 2013, at 12:05 AM, Christian Hammond chi...@chipx86.comjavascript: wrote: Sorry, but what generates libssl.so? Just to be sure, did you restart Apache before adding a repository? Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Apr 8, 2013, at 11:09 PM, chuck j cjerr...@gmail.com javascript: wrote: Ok All the P4.* files are present in /usr/local/lib/python2.7/site-packages The libssl.so placed at /usr/local/lib64/libcrypto.so /usr/local/lib64/libssl.so Do i need to do some manually changes in reviewboard setting which should pick correct P4API.so On Tuesday, April 9, 2013 11:11:39 AM UTC+5:30, Christian Hammond wrote: Yeah, it's possible it's grabbing that one instead. If p4python is successfully built using OpenSSL, the only thing I can think of to cause that error would be Review Board using an older copy somehow. Where's the new P4.* files? Christian -- Christian Hammond - chi...@chipx86.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Apr 8, 2013, at 10:39 PM, chuck j cjerr...@gmail.com wrote: Here are some more information: I can see there was old P4Python-2008.2-py2.7.egg-info file present at site-packages folder, But i had make sure this version's P4.py, P4.pyc, P4.pyo, P4API.so are moved to some safe place. Will this file make any difference. cat easy-install.pth import sys; sys.__plen = len(sys.path) ./setuptools-0.6c11-py2.7.egg ./python_memcached-1.47-py2.7.egg ./recaptcha_client-1.0.6-py2.7.egg ./python_dateutil-1.5-py2.7.egg ./flup-1.0.3.dev_20110405-py2.7.egg ./PIL-1.1.6-py2.7-linux-x86_64.egg ./python_ldap-2.3.13-py2.7-linux-x86_64.egg ./MySQL_python-1.2.3-py2.7-linux-x86_64.egg ./ReviewBoard-1.7.6-py2.7.egg ./pytz-2013b-py2.7.egg ./Pygments-1.6-py2.7.egg ./paramiko-1.10.0-py2.7.egg ./mimeparse-0.1.3-py2.7.egg ./Markdown-2.3.1-py2.7.egg ./docutils-0.10-py2.7.egg ./django_pipeline-1.2.24-py2.7.egg ./Djblets-0.7.11-py2.7.egg ./django_evolution-0.6.9-py2.7.egg ./Django-1.4.5-py2.7.egg ./pycrypto-2.6-py2.7-linux-x86_64.egg ./feedparser-5.1.3-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) On Tuesday, April 9, 2013 10:39:52 AM UTC+5:30, chuck j wrote: Hi Chris, Reviewboard is using the same version of python for which i have provided example as below [GCC 4.1.2 20080704 (Red Hat 4.1.2-46)] on linux2 Type help, copyright, credits or license for more information. import P4 There are no Two version of p4python installed, how do i figure it out. i can see my site-packages contains following files after p4python build and install i.e P4.py, P4.pyc, P4.pyo, P4API.so On Tuesday, April 9, 2013 12:45:35 AM UTC+5:30, Christian Hammond wrote: Is Review Board using the same version of Python? Any chance there are now two copies of p4python installed? Christian On Apr 8, 2013, at 4:01, chuck j cjerr...@gmail.com wrote: Dear All, This is very critical, I am still not able to add SSL enabled perforce repository to reviewboard, Please help me. Since my machine was not having openssl 1.0.1, i need to build and install this version of openssl. I followed the instruction from document, downloaded openssl 1.0.1e ./config --prefix=/usr/local --openssldir=/usr/local/openssl zlib zlib-dynamic shared make make test make install Then i did following step Edit /etc/ld.so.conf add to paths... /usr/local/lib64 Update the run-time linker... # ldconfig verified with below command: ldd /usr/local/bin/openssl libssl.so.1.0.0 = /usr/local/lib64/libssl.so.1.0.0 (0x2b08a088c000) libcrypto.so.1.0.0 = /usr/local/lib64/libcrypto.so.1.0.0 (0x2b08a0af1000) libdl.so.2 = /lib64/libdl.so.2 (0x003b2ac0) libc.so.6 = /lib64/libc.so.6 (0x003b2a40) /lib64/ld-linux-x86-64.so.2
Error during adding Repository to SSL enabled perforce.
Dear All, This is very critical, I am still not able to add SSL enabled perforce repository to reviewboard, Please help me. Since my machine was not having openssl 1.0.1, i need to build and install this version of openssl. I followed the instruction from document, downloaded openssl 1.0.1e ./config --prefix=/usr/local --openssldir=/usr/local/openssl zlib zlib-dynamic shared make make test make install Then i did following step Edit /etc/ld.so.conf add to paths... /usr/local/lib64 Update the run-time linker... # ldconfig verified with below command: ldd /usr/local/bin/openssl libssl.so.1.0.0 = /usr/local/lib64/libssl.so.1.0.0 (0x2b08a088c000) libcrypto.so.1.0.0 = /usr/local/lib64/libcrypto.so.1.0.0 (0x2b08a0af1000) libdl.so.2 = /lib64/libdl.so.2 (0x003b2ac0) libc.so.6 = /lib64/libc.so.6 (0x003b2a40) /lib64/ld-linux-x86-64.so.2 (0x003b2a00) /usr/local/bin/openssl version OpenSSL 1.0.1e 11 Feb 2013 Then I build p4python with --ssl swtich. python setup.py build --apidir /root/work/src/p4api-2012.2.585708 --ssl /usr/local/lib64 API Release 2012.2 running build running build_py creating build creating build/lib.linux-x86_64-2.7 copying P4.py - build/lib.linux-x86_64-2.7 running build_ext building 'P4API' extension creating build/temp.linux-x86_64-2.7 gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DID_OS=LINUX26X86_64 -DID_REL=2012.2 -DID_PATCH=549493 -DID_API=2012.2/585708 -DID_Y=2012 -DID_M=11 -DID_D=05 -I/root/work/src/p4api-2012.2.585708 -I/root/work/src/p4api-2012.2.585708/include/p4 -I/usr/local/include/python2.7 -c P4API.cpp -o build/temp.linux-x86_64-2.7/P4API.o -DOS_LINUX -DOS_LINUX26 -DOS_LINUXX86_64 -DOS_LINUX26X86_64 cc1plus: warning: command line option -Wstrict-prototypes is valid for Ada/C/ObjC but not for C++ gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DID_OS=LINUX26X86_64 -DID_REL=2012.2 -DID_PATCH=549493 -DID_API=2012.2/585708 -DID_Y=2012 -DID_M=11 -DID_D=05 -I/root/work/src/p4api-2012.2.585708 -I/root/work/src/p4api-2012.2.585708/include/p4 -I/usr/local/include/python2.7 -c PythonClientAPI.cpp -o build/temp.linux-x86_64-2.7/PythonClientAPI.o -DOS_LINUX -DOS_LINUX26 -DOS_LINUXX86_64 -DOS_LINUX26X86_64 cc1plus: warning: command line option -Wstrict-prototypes is valid for Ada/C/ObjC but not for C++ gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DID_OS=LINUX26X86_64 -DID_REL=2012.2 -DID_PATCH=549493 -DID_API=2012.2/585708 -DID_Y=2012 -DID_M=11 -DID_D=05 -I/root/work/src/p4api-2012.2.585708 -I/root/work/src/p4api-2012.2.585708/include/p4 -I/usr/local/include/python2.7 -c PythonClientUser.cpp -o build/temp.linux-x86_64-2.7/PythonClientUser.o -DOS_LINUX -DOS_LINUX26 -DOS_LINUXX86_64 -DOS_LINUX26X86_64 cc1plus: warning: command line option -Wstrict-prototypes is valid for Ada/C/ObjC but not for C++ gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DID_OS=LINUX26X86_64 -DID_REL=2012.2 -DID_PATCH=549493 -DID_API=2012.2/585708 -DID_Y=2012 -DID_M=11 -DID_D=05 -I/root/work/src/p4api-2012.2.585708 -I/root/work/src/p4api-2012.2.585708/include/p4 -I/usr/local/include/python2.7 -c SpecMgr.cpp -o build/temp.linux-x86_64-2.7/SpecMgr.o -DOS_LINUX -DOS_LINUX26 -DOS_LINUXX86_64 -DOS_LINUX26X86_64 cc1plus: warning: command line option -Wstrict-prototypes is valid for Ada/C/ObjC but not for C++ gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DID_OS=LINUX26X86_64 -DID_REL=2012.2 -DID_PATCH=549493 -DID_API=2012.2/585708 -DID_Y=2012 -DID_M=11 -DID_D=05 -I/root/work/src/p4api-2012.2.585708 -I/root/work/src/p4api-2012.2.585708/include/p4 -I/usr/local/include/python2.7 -c P4Result.cpp -o build/temp.linux-x86_64-2.7/P4Result.o -DOS_LINUX -DOS_LINUX26 -DOS_LINUXX86_64 -DOS_LINUX26X86_64 cc1plus: warning: command line option -Wstrict-prototypes is valid for Ada/C/ObjC but not for C++ gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DID_OS=LINUX26X86_64 -DID_REL=2012.2 -DID_PATCH=549493 -DID_API=2012.2/585708 -DID_Y=2012 -DID_M=11 -DID_D=05 -I/root/work/src/p4api-2012.2.585708 -I/root/work/src/p4api-2012.2.585708/include/p4 -I/usr/local/include/python2.7 -c PythonMergeData.cpp -o build/temp.linux-x86_64-2.7/PythonMergeData.o -DOS_LINUX -DOS_LINUX26 -DOS_LINUXX86_64 -DOS_LINUX26X86_64 cc1plus: warning: command line option -Wstrict-prototypes is valid for Ada/C/ObjC but not for C++ gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DID_OS=LINUX26X86_64 -DID_REL=2012.2 -DID_PATCH=549493 -DID_API=2012.2/585708 -DID_Y=2012 -DID_M=11 -DID_D=05 -I/root/work/src/p4api-2012.2.585708 -I/root/work/src/p4api-2012.2.585708/include/p4 -I/usr/local/include/python2.7 -c P4MapMaker.cpp -o
Re: Error during adding Repository to SSL enabled perforce.
Hi Chris, Reviewboard is using the same version of python for which i have provided example as below [GCC 4.1.2 20080704 (Red Hat 4.1.2-46)] on linux2 Type help, copyright, credits or license for more information. import P4 There are no Two version of p4python installed, how do i figure it out. i can see my site-packages contains following files after p4python build and install i.e P4.py, P4.pyc, P4.pyo, P4API.so On Tuesday, April 9, 2013 12:45:35 AM UTC+5:30, Christian Hammond wrote: Is Review Board using the same version of Python? Any chance there are now two copies of p4python installed? Christian On Apr 8, 2013, at 4:01, chuck j cjerr...@gmail.com javascript: wrote: Dear All, This is very critical, I am still not able to add SSL enabled perforce repository to reviewboard, Please help me. Since my machine was not having openssl 1.0.1, i need to build and install this version of openssl. I followed the instruction from document, downloaded openssl 1.0.1e ./config --prefix=/usr/local --openssldir=/usr/local/openssl zlib zlib-dynamic shared make make test make install Then i did following step Edit /etc/ld.so.conf add to paths... /usr/local/lib64 Update the run-time linker... # ldconfig verified with below command: ldd /usr/local/bin/openssl libssl.so.1.0.0 = /usr/local/lib64/libssl.so.1.0.0 (0x2b08a088c000) libcrypto.so.1.0.0 = /usr/local/lib64/libcrypto.so.1.0.0 (0x2b08a0af1000) libdl.so.2 = /lib64/libdl.so.2 (0x003b2ac0) libc.so.6 = /lib64/libc.so.6 (0x003b2a40) /lib64/ld-linux-x86-64.so.2 (0x003b2a00) /usr/local/bin/openssl version OpenSSL 1.0.1e 11 Feb 2013 Then I build p4python with --ssl swtich. python setup.py build --apidir /root/work/src/p4api-2012.2.585708 --ssl /usr/local/lib64 API Release 2012.2 running build running build_py creating build creating build/lib.linux-x86_64-2.7 copying P4.py - build/lib.linux-x86_64-2.7 running build_ext building 'P4API' extension creating build/temp.linux-x86_64-2.7 gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DID_OS=LINUX26X86_64 -DID_REL=2012.2 -DID_PATCH=549493 -DID_API=2012.2/585708 -DID_Y=2012 -DID_M=11 -DID_D=05 -I/root/work/src/p4api-2012.2.585708 -I/root/work/src/p4api-2012.2.585708/include/p4 -I/usr/local/include/python2.7 -c P4API.cpp -o build/temp.linux-x86_64-2.7/P4API.o -DOS_LINUX -DOS_LINUX26 -DOS_LINUXX86_64 -DOS_LINUX26X86_64 cc1plus: warning: command line option -Wstrict-prototypes is valid for Ada/C/ObjC but not for C++ gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DID_OS=LINUX26X86_64 -DID_REL=2012.2 -DID_PATCH=549493 -DID_API=2012.2/585708 -DID_Y=2012 -DID_M=11 -DID_D=05 -I/root/work/src/p4api-2012.2.585708 -I/root/work/src/p4api-2012.2.585708/include/p4 -I/usr/local/include/python2.7 -c PythonClientAPI.cpp -o build/temp.linux-x86_64-2.7/PythonClientAPI.o -DOS_LINUX -DOS_LINUX26 -DOS_LINUXX86_64 -DOS_LINUX26X86_64 cc1plus: warning: command line option -Wstrict-prototypes is valid for Ada/C/ObjC but not for C++ gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DID_OS=LINUX26X86_64 -DID_REL=2012.2 -DID_PATCH=549493 -DID_API=2012.2/585708 -DID_Y=2012 -DID_M=11 -DID_D=05 -I/root/work/src/p4api-2012.2.585708 -I/root/work/src/p4api-2012.2.585708/include/p4 -I/usr/local/include/python2.7 -c PythonClientUser.cpp -o build/temp.linux-x86_64-2.7/PythonClientUser.o -DOS_LINUX -DOS_LINUX26 -DOS_LINUXX86_64 -DOS_LINUX26X86_64 cc1plus: warning: command line option -Wstrict-prototypes is valid for Ada/C/ObjC but not for C++ gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DID_OS=LINUX26X86_64 -DID_REL=2012.2 -DID_PATCH=549493 -DID_API=2012.2/585708 -DID_Y=2012 -DID_M=11 -DID_D=05 -I/root/work/src/p4api-2012.2.585708 -I/root/work/src/p4api-2012.2.585708/include/p4 -I/usr/local/include/python2.7 -c SpecMgr.cpp -o build/temp.linux-x86_64-2.7/SpecMgr.o -DOS_LINUX -DOS_LINUX26 -DOS_LINUXX86_64 -DOS_LINUX26X86_64 cc1plus: warning: command line option -Wstrict-prototypes is valid for Ada/C/ObjC but not for C++ gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DID_OS=LINUX26X86_64 -DID_REL=2012.2 -DID_PATCH=549493 -DID_API=2012.2/585708 -DID_Y=2012 -DID_M=11 -DID_D=05 -I/root/work/src/p4api-2012.2.585708 -I/root/work/src/p4api-2012.2.585708/include/p4 -I/usr/local/include/python2.7 -c P4Result.cpp -o build/temp.linux-x86_64-2.7/P4Result.o -DOS_LINUX -DOS_LINUX26 -DOS_LINUXX86_64 -DOS_LINUX26X86_64 cc1plus: warning: command line option -Wstrict-prototypes is valid for Ada/C/ObjC but not for C++ gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict
Re: Error during adding Repository to SSL enabled perforce.
Here are some more information: I can see there was old P4Python-2008.2-py2.7.egg-info file present at site-packages folder, But i had make sure this version's P4.py, P4.pyc, P4.pyo, P4API.so are moved to some safe place. Will this file make any difference. cat easy-install.pth import sys; sys.__plen = len(sys.path) ./setuptools-0.6c11-py2.7.egg ./python_memcached-1.47-py2.7.egg ./recaptcha_client-1.0.6-py2.7.egg ./python_dateutil-1.5-py2.7.egg ./flup-1.0.3.dev_20110405-py2.7.egg ./PIL-1.1.6-py2.7-linux-x86_64.egg ./python_ldap-2.3.13-py2.7-linux-x86_64.egg ./MySQL_python-1.2.3-py2.7-linux-x86_64.egg ./ReviewBoard-1.7.6-py2.7.egg ./pytz-2013b-py2.7.egg ./Pygments-1.6-py2.7.egg ./paramiko-1.10.0-py2.7.egg ./mimeparse-0.1.3-py2.7.egg ./Markdown-2.3.1-py2.7.egg ./docutils-0.10-py2.7.egg ./django_pipeline-1.2.24-py2.7.egg ./Djblets-0.7.11-py2.7.egg ./django_evolution-0.6.9-py2.7.egg ./Django-1.4.5-py2.7.egg ./pycrypto-2.6-py2.7-linux-x86_64.egg ./feedparser-5.1.3-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) On Tuesday, April 9, 2013 10:39:52 AM UTC+5:30, chuck j wrote: Hi Chris, Reviewboard is using the same version of python for which i have provided example as below [GCC 4.1.2 20080704 (Red Hat 4.1.2-46)] on linux2 Type help, copyright, credits or license for more information. import P4 There are no Two version of p4python installed, how do i figure it out. i can see my site-packages contains following files after p4python build and install i.e P4.py, P4.pyc, P4.pyo, P4API.so On Tuesday, April 9, 2013 12:45:35 AM UTC+5:30, Christian Hammond wrote: Is Review Board using the same version of Python? Any chance there are now two copies of p4python installed? Christian On Apr 8, 2013, at 4:01, chuck j cjerr...@gmail.com wrote: Dear All, This is very critical, I am still not able to add SSL enabled perforce repository to reviewboard, Please help me. Since my machine was not having openssl 1.0.1, i need to build and install this version of openssl. I followed the instruction from document, downloaded openssl 1.0.1e ./config --prefix=/usr/local --openssldir=/usr/local/openssl zlib zlib-dynamic shared make make test make install Then i did following step Edit /etc/ld.so.conf add to paths... /usr/local/lib64 Update the run-time linker... # ldconfig verified with below command: ldd /usr/local/bin/openssl libssl.so.1.0.0 = /usr/local/lib64/libssl.so.1.0.0 (0x2b08a088c000) libcrypto.so.1.0.0 = /usr/local/lib64/libcrypto.so.1.0.0 (0x2b08a0af1000) libdl.so.2 = /lib64/libdl.so.2 (0x003b2ac0) libc.so.6 = /lib64/libc.so.6 (0x003b2a40) /lib64/ld-linux-x86-64.so.2 (0x003b2a00) /usr/local/bin/openssl version OpenSSL 1.0.1e 11 Feb 2013 Then I build p4python with --ssl swtich. python setup.py build --apidir /root/work/src/p4api-2012.2.585708 --ssl /usr/local/lib64 API Release 2012.2 running build running build_py creating build creating build/lib.linux-x86_64-2.7 copying P4.py - build/lib.linux-x86_64-2.7 running build_ext building 'P4API' extension creating build/temp.linux-x86_64-2.7 gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DID_OS=LINUX26X86_64 -DID_REL=2012.2 -DID_PATCH=549493 -DID_API=2012.2/585708 -DID_Y=2012 -DID_M=11 -DID_D=05 -I/root/work/src/p4api-2012.2.585708 -I/root/work/src/p4api-2012.2.585708/include/p4 -I/usr/local/include/python2.7 -c P4API.cpp -o build/temp.linux-x86_64-2.7/P4API.o -DOS_LINUX -DOS_LINUX26 -DOS_LINUXX86_64 -DOS_LINUX26X86_64 cc1plus: warning: command line option -Wstrict-prototypes is valid for Ada/C/ObjC but not for C++ gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DID_OS=LINUX26X86_64 -DID_REL=2012.2 -DID_PATCH=549493 -DID_API=2012.2/585708 -DID_Y=2012 -DID_M=11 -DID_D=05 -I/root/work/src/p4api-2012.2.585708 -I/root/work/src/p4api-2012.2.585708/include/p4 -I/usr/local/include/python2.7 -c PythonClientAPI.cpp -o build/temp.linux-x86_64-2.7/PythonClientAPI.o -DOS_LINUX -DOS_LINUX26 -DOS_LINUXX86_64 -DOS_LINUX26X86_64 cc1plus: warning: command line option -Wstrict-prototypes is valid for Ada/C/ObjC but not for C++ gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DID_OS=LINUX26X86_64 -DID_REL=2012.2 -DID_PATCH=549493 -DID_API=2012.2/585708 -DID_Y=2012 -DID_M=11 -DID_D=05 -I/root/work/src/p4api-2012.2.585708 -I/root/work/src/p4api-2012.2.585708/include/p4 -I/usr/local/include/python2.7 -c PythonClientUser.cpp -o build/temp.linux-x86_64-2.7/PythonClientUser.o -DOS_LINUX -DOS_LINUX26 -DOS_LINUXX86_64 -DOS_LINUX26X86_64 cc1plus: warning: command line option -Wstrict-prototypes is valid for Ada/C/ObjC
Re: patch upload error message
diff, size: 471
HTTP POSTing to
http://rb.company.com/rb/api/review-requests/45465/diffs/: {}
Review request #45465 posted.
http://rb.company.com/rb/r/45465/
On Thu, Apr 4, 2013 at 2:36 AM, Christian Hammond chip...@chipx86.comwrote:
Can you provide the entire debug log when using post-review to upload a
broken change?
What version of RBTools?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On Wed, Apr 3, 2013 at 11:50 AM, chuck j cjerry2...@gmail.com wrote:
Hi Chris,
Its seems my response are getting overlapped, sorry for inconvenience.
Diff get generated using rbtools, repository used is perforce. I guess
rbtools using diff util to generate diff.
Also there is another issue also. When single line change RB web console
view diff shows complete file as change.
Please let me know if you need any other information.
-Chuck
On Wed, Apr 3, 2013 at 4:30 PM, chuck j cjerry2...@gmail.com wrote:
Diff get generated using rbtools, repository used is perforce. I guess
rbtools using diff util to generate diff.
Also there is another issue also. When single line change RB web console
view diff shows complete file as change.
On Saturday, March 30, 2013 2:13:09 AM UTC+5:30, Christian Hammond wrote:
Hi,
How are the diffs being generated? What type of repository?
This is generally due to generating a diff incorrectly, so we should
find out what's being done.
Christian
On Mar 29, 2013, at 2:13, chuck j cjerr...@gmail.com wrote:
Dear All,
This is frustrating developer reporting every second day with patch not
getting upload in reviewboard.
can somebody help me resolve or tell me how to resolve such issue.
Diff currently unavailable. *Error:* The patch to
'//path/to/depot/file/**bodypair_appregion.pcl' didn't apply cleanly.
The temporary files have been left in '/tmp/reviewboard.uUq6zC' for
debugging purposes. `patch` returned: patching file
/tmp/reviewboard.uUq6zC/
**tmpYlQESK Hunk #3 FAILED at 2153. 1 out of 3 hunks FAILED -- saving
rejects to file /tmp/reviewboard.uUq6zC/**tmpYlQESK-new.rej
Detailshttp://mscrb.mscsoftware.com/mscrb/r/45177/diff/#
Traceback (most recent call last):
File
/usr/local/lib/python2.7/**site-packages/ReviewBoard-1.7.**5-py2.7.egg/reviewboard/**diffviewer/views.py,
line 383, in view_diff_fragment
file = get_requested_diff_file()
File
/usr/local/lib/python2.7/**site-packages/ReviewBoard-1.7.**5-py2.7.egg/reviewboard/**diffviewer/views.py,
line 309, in get_requested_diff_file
Regards,
Chuck
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/**donate/http://www.reviewboard.org/donate/
Happy user? Let us know at
http://www.reviewboard.org/**users/http://www.reviewboard.org/users/
-~--~~~~--**~~--~--~---
To unsubscribe from this group, send email to reviewboard...@**
googlegroups.com
For more options, visit this group at http://groups.google.com/**
group/reviewboard?hl=enhttp://groups.google.com/group/reviewboard?hl=en
---
You received this message because you are subscribed to the Google
Groups reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send
an email to reviewboard...@**googlegroups.com.
For more options, visit
https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/reviewboard?hl=en
---
You received this message because you are subscribed to a topic in the
Google Groups reviewboard group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/reviewboard/l4DVzR4_H6U/unsubscribe?hl=en
.
To unsubscribe from this group and all its topics, send an email to
reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/reviewboard?hl=en
---
You received this message because you are subscribed to the Google Groups
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an
email to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
Want to help
Re: patch upload error message
Dear All, Do we have solution to avoid such issues. -Chuck. On Fri, Mar 29, 2013 at 2:43 PM, chuck j cjerry2...@gmail.com wrote: Dear All, This is frustrating developer reporting every second day with patch not getting upload in reviewboard. can somebody help me resolve or tell me how to resolve such issue. Diff currently unavailable. *Error:* The patch to '//path/to/depot/file/bodypair_appregion.pcl' didn't apply cleanly. The temporary files have been left in '/tmp/reviewboard.uUq6zC' for debugging purposes. `patch` returned: patching file /tmp/reviewboard.uUq6zC/tmpYlQESK Hunk #3 FAILED at 2153. 1 out of 3 hunks FAILED -- saving rejects to file /tmp/reviewboard.uUq6zC/tmpYlQESK-new.rej Traceback (most recent call last): File /usr/local/lib/python2.7/site-packages/ReviewBoard-1.7.5-py2.7.egg/reviewboard/diffviewer/views.py, line 383, in view_diff_fragment file = get_requested_diff_file() File /usr/local/lib/python2.7/site-packages/ReviewBoard-1.7.5-py2.7.egg/reviewboard/diffviewer/views.py, line 309, in get_requested_diff_file Regards, Chuck -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: patch upload error message
Diff get generated using rbtools, repository used is perforce. I guess rbtools using diff util to generate diff. Also there is another issue also. When single line change RB web console view diff shows complete file as change. On Saturday, March 30, 2013 2:13:09 AM UTC+5:30, Christian Hammond wrote: Hi, How are the diffs being generated? What type of repository? This is generally due to generating a diff incorrectly, so we should find out what's being done. Christian On Mar 29, 2013, at 2:13, chuck j cjerr...@gmail.com javascript: wrote: Dear All, This is frustrating developer reporting every second day with patch not getting upload in reviewboard. can somebody help me resolve or tell me how to resolve such issue. Diff currently unavailable. *Error:* The patch to '//path/to/depot/file/bodypair_appregion.pcl' didn't apply cleanly. The temporary files have been left in '/tmp/reviewboard.uUq6zC' for debugging purposes. `patch` returned: patching file /tmp/reviewboard.uUq6zC/tmpYlQESK Hunk #3 FAILED at 2153. 1 out of 3 hunks FAILED -- saving rejects to file /tmp/reviewboard.uUq6zC/tmpYlQESK-new.rej Detailshttp://mscrb.mscsoftware.com/mscrb/r/45177/diff/# Traceback (most recent call last): File /usr/local/lib/python2.7/site-packages/ReviewBoard-1.7.5-py2.7.egg/reviewboard/diffviewer/views.py, line 383, in view_diff_fragment file = get_requested_diff_file() File /usr/local/lib/python2.7/site-packages/ReviewBoard-1.7.5-py2.7.egg/reviewboard/diffviewer/views.py, line 309, in get_requested_diff_file Regards, Chuck -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: patch upload error message
Hi Chris, Its seems my response are getting overlapped, sorry for inconvenience. Diff get generated using rbtools, repository used is perforce. I guess rbtools using diff util to generate diff. Also there is another issue also. When single line change RB web console view diff shows complete file as change. Please let me know if you need any other information. -Chuck On Wed, Apr 3, 2013 at 4:30 PM, chuck j cjerry2...@gmail.com wrote: Diff get generated using rbtools, repository used is perforce. I guess rbtools using diff util to generate diff. Also there is another issue also. When single line change RB web console view diff shows complete file as change. On Saturday, March 30, 2013 2:13:09 AM UTC+5:30, Christian Hammond wrote: Hi, How are the diffs being generated? What type of repository? This is generally due to generating a diff incorrectly, so we should find out what's being done. Christian On Mar 29, 2013, at 2:13, chuck j cjerr...@gmail.com wrote: Dear All, This is frustrating developer reporting every second day with patch not getting upload in reviewboard. can somebody help me resolve or tell me how to resolve such issue. Diff currently unavailable. *Error:* The patch to '//path/to/depot/file/ **bodypair_appregion.pcl' didn't apply cleanly. The temporary files have been left in '/tmp/reviewboard.uUq6zC' for debugging purposes. `patch` returned: patching file /tmp/reviewboard.uUq6zC/**tmpYlQESK Hunk #3 FAILED at 2153. 1 out of 3 hunks FAILED -- saving rejects to file /tmp/reviewboard.uUq6zC/**tmpYlQESK-new.rej Detailshttp://mscrb.mscsoftware.com/mscrb/r/45177/diff/# Traceback (most recent call last): File /usr/local/lib/python2.7/**site-packages/ReviewBoard-1.7.**5-py2.7.egg/reviewboard/**diffviewer/views.py, line 383, in view_diff_fragment file = get_requested_diff_file() File /usr/local/lib/python2.7/**site-packages/ReviewBoard-1.7.**5-py2.7.egg/reviewboard/**diffviewer/views.py, line 309, in get_requested_diff_file Regards, Chuck -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/**donate/ http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/**users/http://www.reviewboard.org/users/ -~--~~~~--**~~--~--~--- To unsubscribe from this group, send email to reviewboard...@** googlegroups.com For more options, visit this group at http://groups.google.com/** group/reviewboard?hl=enhttp://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@**googlegroups.com. For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to a topic in the Google Groups reviewboard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/reviewboard/l4DVzR4_H6U/unsubscribe?hl=en . To unsubscribe from this group and all its topics, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Error while adding perforce 2012.2 repository to reviewboard 1.7.4
Hi David, I didnt get what you need, are you saying that my p4python is not build properly. if yes then can you please provide me steps which i can ran get it done. But i have used the RELNOTES.txt present in p4python.tar to build. Any pre-requiste i need to do to make p4python build with ssl support enable. -Chuck On Thu, Mar 14, 2013 at 5:42 AM, David Trowbridge trowb...@gmail.comwrote: Chuck, This seems to be missing most of the p4python build. In particular I'd like to see the output (and any output files) from the configure step. -David On Tue, Feb 26, 2013 at 1:53 AM, chuck j cjerry2...@gmail.com wrote: Thanks David, please find the attached log file for the below steps. do let me know if any thing is missing from my end, -Chuck On Tue, Feb 26, 2013 at 12:51 AM, David Trowbridge trowb...@gmail.comwrote: Can you get full logs of the output of all of those steps and attach them/pastebin them somewhere? -David On Wed, Feb 20, 2013 at 2:27 AM, chuck j cjerry2...@gmail.com wrote: Thanks David for responding my email. Here are the steps which i followed. My Linux box has el5 has following openssl package. openssl097a-0.9.7a-9.el5_2.1 openssl-devel-0.9.8e-12.el5 openssl097a-0.9.7a-9.el5_2.1 openssl-0.9.8e-12.el5 openssl-0.9.8e-12.el5 openssl-devel-0.9.8e-12.el5 To compile p4python, i need to have openssl 1.0.1 So i downloaded openssl 1.0.1c, ./config make make test make install Openssl gets installed at /usr/local/ssl location. I downloaded p4python and p4api from perforce.org site. python setup.py build --apidir /home/me/p4api --ssl /usr/local/ssl/lib python setup.py install Then i assume that p4python gets installed. I tested with the steps in python prompt import P4 p4 = P4.P4() p4.connect() Traceback (most recent call last): File stdin, line 1, in module File /usr/local/lib/python2.7/site -packages/P4.py, line 642, in connect P4API.P4Adapter.connect( self ) P4.P4Exception: [P4.connect()] Connect to server failed; check $P4PORT. SSL library must be at least version 1.0.1. Please let me know if you need any thing else. Regards, Chuck On Tue, Feb 19, 2013 at 6:25 AM, David Trowbridge trowb...@gmail.comwrote: Can you show me a log of exactly which commands you used to build and install p4python? -David On Wed, Feb 13, 2013 at 12:00 PM, chuck j cjerry2...@gmail.comwrote: Dear All, Its seems i have got some success while configuring ssl. Now that our perforce server is running on ssl I am try to add the repository, while doing so i am getting below error message. - *The specified Perforce port includes ssl:, but the p4python library was built without SSL support or the system library path is incorrect. * As we have not able to find rpm for RHEL 2.6 OpenSSL 1.0.1, we have to build openssl 1.0.1, which eventually got installed at /usr/local/ssl/bin/ /usr/local/ssl/ then we have build p4python with --ssl option. But its seems that still reviewboard reports about the above error message. Please help us know where to add the path of new build openssl library for which reviewboard server is looking for, if some pointer will be highly appreciated. -Chuck On Wed, Feb 13, 2013 at 7:24 AM, chuck j cjerry2...@gmail.comwrote: Does my p4 info output gave expected output. [root@svrrb1 works]# p4 info User name: chuckj Client name: svrrb1 Client host: svrrb1.na.software.com Client unknown. Current directory: /works Peer address: 182.16.43.144:42238 Client address: my ip address Server address: some ip:1666 Server root: /PFMETA/p4root Server date: 2013/02/12 01:09:47 -0800 PST Server uptime: 286:15:29 Server version: P4D/LINUX26X86_64/2012.2/50 (2013/01/18) Server encryption: encrypted Server cert expires: Jan 31 10:22:47 2015 GMT Server license: Software Corporation users (expires 2013/02/21) Server license-ip: some ip:1666 Case Handling: sensitive On Tuesday, February 12, 2013 4:49:40 PM UTC+5:30, chuck j wrote: Since i couldn't find openssl 1.0.1 rpm, I have to manually compile and build then install it to the default path, then later i have build p4python. root@svrrb1 p4python-2012.2.549493# python setup.py build --apidir /works/p4api-2012.2.585708/ --ssl /usr/local/ root@svrrb1 p4python-2012.2.549493# python setup.py install --apidir /works/p4api-2012.2.585708/ Assuming everything above working fine i test by providing below command line. import P4 p4 = P4.P4() p4.connect() Traceback (most recent call last): File stdin, line 1, in module File /usr/local/lib/python2.7/**site-packages/P4.py, line 642, in connect P4API.P4Adapter.connect( self ) P4.P4Exception: [P4.connect()] Connect to server failed; check $P4PORT. SSL library must be at least version 1.0.1. Does my P4Python is build with OpenSSL.1.0.1 libarary, What is missing in my setup? I know this is not the right forum for above queries
patch upload error message
Dear All, This is frustrating developer reporting every second day with patch not getting upload in reviewboard. can somebody help me resolve or tell me how to resolve such issue. Diff currently unavailable. *Error:* The patch to '//path/to/depot/file/bodypair_appregion.pcl' didn't apply cleanly. The temporary files have been left in '/tmp/reviewboard.uUq6zC' for debugging purposes. `patch` returned: patching file /tmp/reviewboard.uUq6zC/tmpYlQESK Hunk #3 FAILED at 2153. 1 out of 3 hunks FAILED -- saving rejects to file /tmp/reviewboard.uUq6zC/tmpYlQESK-new.rej Detailshttp://mscrb.mscsoftware.com/mscrb/r/45177/diff/# Traceback (most recent call last): File /usr/local/lib/python2.7/site-packages/ReviewBoard-1.7.5-py2.7.egg/reviewboard/diffviewer/views.py, line 383, in view_diff_fragment file = get_requested_diff_file() File /usr/local/lib/python2.7/site-packages/ReviewBoard-1.7.5-py2.7.egg/reviewboard/diffviewer/views.py, line 309, in get_requested_diff_file Regards, Chuck -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: How to get review id before publishing a review request
Thanks,
Yes i am using wrapper over post-review script. I am already using stdout
of post-review to get the review id. I wanted to know if there is any API
which will help me get the review id before publishing the review request?
which i can use in my wrapper.
Regards,
Chuck
On Wed, Feb 20, 2013 at 11:10 PM, Matthew Woehlke
mwoehlke.fl...@gmail.comwrote:
On 2013-02-20 12:31, chuck j wrote:
how to get review request id after successful posting of review request
and
before publishing the review request.
Can you be more specific? How are you posting the review request? In what
form do you need the ID?
If you are writing a wrapper over post-review and need the request ID
(e.g. my git-rb script does this), you can redirect the output to a
temporary file, and find the ID from that like so:
matchexpr='Review request #[0-9][0-9]* posted'
request=$(sed -n /^$matchexpr/'{s/^.*#//;s/ .*$//;p}' $log)
(...where 'log' is a shell variable with the name of the temporary file
containing the output of post-review.)
Don't forget to check the exit status of post-review to know if it
succeeded.
If you are using the web interface, the ID is part of the URI as soon as
you create a new request; just look at your address bar.
If you generically know that there exists a review request draft, the best
you will be able to do is list all requests, query the status of each, and
note any that are drafts.
--
Matthew
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/reviewboard?hl=en
---
You received this message because you are subscribed to the Google Groups
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Error while adding perforce 2012.2 repository to reviewboard 1.7.4
Thanks David for responding my email. Here are the steps which i followed. My Linux box has el5 has following openssl package. openssl097a-0.9.7a-9.el5_2.1 openssl-devel-0.9.8e-12.el5 openssl097a-0.9.7a-9.el5_2.1 openssl-0.9.8e-12.el5 openssl-0.9.8e-12.el5 openssl-devel-0.9.8e-12.el5 To compile p4python, i need to have openssl 1.0.1 So i downloaded openssl 1.0.1c, ./config make make test make install Openssl gets installed at /usr/local/ssl location. I downloaded p4python and p4api from perforce.org site. python setup.py build --apidir /home/me/p4api --ssl /usr/local/ssl/lib python setup.py install Then i assume that p4python gets installed. I tested with the steps in python prompt import P4 p4 = P4.P4() p4.connect() Traceback (most recent call last): File stdin, line 1, in module File /usr/local/lib/python2.7/site -packages/P4.py, line 642, in connect P4API.P4Adapter.connect( self ) P4.P4Exception: [P4.connect()] Connect to server failed; check $P4PORT. SSL library must be at least version 1.0.1. Please let me know if you need any thing else. Regards, Chuck On Tue, Feb 19, 2013 at 6:25 AM, David Trowbridge trowb...@gmail.comwrote: Can you show me a log of exactly which commands you used to build and install p4python? -David On Wed, Feb 13, 2013 at 12:00 PM, chuck j cjerry2...@gmail.com wrote: Dear All, Its seems i have got some success while configuring ssl. Now that our perforce server is running on ssl I am try to add the repository, while doing so i am getting below error message. - *The specified Perforce port includes ssl:, but the p4python library was built without SSL support or the system library path is incorrect. * As we have not able to find rpm for RHEL 2.6 OpenSSL 1.0.1, we have to build openssl 1.0.1, which eventually got installed at /usr/local/ssl/bin/ /usr/local/ssl/ then we have build p4python with --ssl option. But its seems that still reviewboard reports about the above error message. Please help us know where to add the path of new build openssl library for which reviewboard server is looking for, if some pointer will be highly appreciated. -Chuck On Wed, Feb 13, 2013 at 7:24 AM, chuck j cjerry2...@gmail.com wrote: Does my p4 info output gave expected output. [root@svrrb1 works]# p4 info User name: chuckj Client name: svrrb1 Client host: svrrb1.na.software.com Client unknown. Current directory: /works Peer address: 182.16.43.144:42238 Client address: my ip address Server address: some ip:1666 Server root: /PFMETA/p4root Server date: 2013/02/12 01:09:47 -0800 PST Server uptime: 286:15:29 Server version: P4D/LINUX26X86_64/2012.2/50 (2013/01/18) Server encryption: encrypted Server cert expires: Jan 31 10:22:47 2015 GMT Server license: Software Corporation users (expires 2013/02/21) Server license-ip: some ip:1666 Case Handling: sensitive On Tuesday, February 12, 2013 4:49:40 PM UTC+5:30, chuck j wrote: Since i couldn't find openssl 1.0.1 rpm, I have to manually compile and build then install it to the default path, then later i have build p4python. root@svrrb1 p4python-2012.2.549493# python setup.py build --apidir /works/p4api-2012.2.585708/ --ssl /usr/local/ root@svrrb1 p4python-2012.2.549493# python setup.py install --apidir /works/p4api-2012.2.585708/ Assuming everything above working fine i test by providing below command line. import P4 p4 = P4.P4() p4.connect() Traceback (most recent call last): File stdin, line 1, in module File /usr/local/lib/python2.7/**site-packages/P4.py, line 642, in connect P4API.P4Adapter.connect( self ) P4.P4Exception: [P4.connect()] Connect to server failed; check $P4PORT. SSL library must be at least version 1.0.1. Does my P4Python is build with OpenSSL.1.0.1 libarary, What is missing in my setup? I know this is not the right forum for above queries but this may provide some hint why adding repository to reviewboard is giving error. Please let me know if you need any more info, log for the same. - Chuck On Tuesday, February 12, 2013 2:51:15 PM UTC+5:30, chuck j wrote: Hi , This is what i get for p4 info [root@svrrb1 works]# export P4USER=chuckj [root@svrrb1 works]# export P4PORT=ssl:some ip:1666 [root@svrrb1 works]# p4 login Enter password: User chuckj logged in. [root@svrrb1 works]# p4 info User name: chuckj Client name: svrrb1 Client host: svrrb1.na.software.com Client unknown. Current directory: /works Peer address: 182.16.43.144:42238 Client address: my ip address Server address: some ip:1666 Server root: /PFMETA/p4root Server date: 2013/02/12 01:09:47 -0800 PST Server uptime: 286:15:29 Server version: P4D/LINUX26X86_64/2012.2/**50 (2013/01/18) Server encryption: encrypted Server cert expires: Jan 31 10:22:47 2015 GMT Server license: Software Corporation users (expires 2013/02/21) Server license-ip: some ip:1666 Case Handling: sensitive The authentication
How to get review id before publishing a review request
Hi, how to get review request id after successful posting of review request and before publishing the review request. I tried to search a lot in reviewbaord forum but couldn't find relevant response, do we have such api which will help our need. Thanks, Chuck -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Error while adding perforce 2012.2 repository to reviewboard 1.7.4
Dear All, Its seems i have got some success while configuring ssl. Now that our perforce server is running on ssl I am try to add the repository, while doing so i am getting below error message. - *The specified Perforce port includes ssl:, but the p4python library was built without SSL support or the system library path is incorrect. * As we have not able to find rpm for RHEL 2.6 OpenSSL 1.0.1, we have to build openssl 1.0.1, which eventually got installed at /usr/local/ssl/bin/ /usr/local/ssl/ then we have build p4python with --ssl option. But its seems that still reviewboard reports about the above error message. Please help us know where to add the path of new build openssl library for which reviewboard server is looking for, if some pointer will be highly appreciated. -Chuck On Wed, Feb 13, 2013 at 7:24 AM, chuck j cjerry2...@gmail.com wrote: Does my p4 info output gave expected output. [root@svrrb1 works]# p4 info User name: chuckj Client name: svrrb1 Client host: svrrb1.na.software.com Client unknown. Current directory: /works Peer address: 182.16.43.144:42238 Client address: my ip address Server address: some ip:1666 Server root: /PFMETA/p4root Server date: 2013/02/12 01:09:47 -0800 PST Server uptime: 286:15:29 Server version: P4D/LINUX26X86_64/2012.2/50 (2013/01/18) Server encryption: encrypted Server cert expires: Jan 31 10:22:47 2015 GMT Server license: Software Corporation users (expires 2013/02/21) Server license-ip: some ip:1666 Case Handling: sensitive On Tuesday, February 12, 2013 4:49:40 PM UTC+5:30, chuck j wrote: Since i couldn't find openssl 1.0.1 rpm, I have to manually compile and build then install it to the default path, then later i have build p4python. root@svrrb1 p4python-2012.2.549493# python setup.py build --apidir /works/p4api-2012.2.585708/ --ssl /usr/local/ root@svrrb1 p4python-2012.2.549493# python setup.py install --apidir /works/p4api-2012.2.585708/ Assuming everything above working fine i test by providing below command line. import P4 p4 = P4.P4() p4.connect() Traceback (most recent call last): File stdin, line 1, in module File /usr/local/lib/python2.7/**site-packages/P4.py, line 642, in connect P4API.P4Adapter.connect( self ) P4.P4Exception: [P4.connect()] Connect to server failed; check $P4PORT. SSL library must be at least version 1.0.1. Does my P4Python is build with OpenSSL.1.0.1 libarary, What is missing in my setup? I know this is not the right forum for above queries but this may provide some hint why adding repository to reviewboard is giving error. Please let me know if you need any more info, log for the same. - Chuck On Tuesday, February 12, 2013 2:51:15 PM UTC+5:30, chuck j wrote: Hi , This is what i get for p4 info [root@svrrb1 works]# export P4USER=chuckj [root@svrrb1 works]# export P4PORT=ssl:some ip:1666 [root@svrrb1 works]# p4 login Enter password: User chuckj logged in. [root@svrrb1 works]# p4 info User name: chuckj Client name: svrrb1 Client host: svrrb1.na.software.com Client unknown. Current directory: /works Peer address: 182.16.43.144:42238 Client address: my ip address Server address: some ip:1666 Server root: /PFMETA/p4root Server date: 2013/02/12 01:09:47 -0800 PST Server uptime: 286:15:29 Server version: P4D/LINUX26X86_64/2012.2/**50 (2013/01/18) Server encryption: encrypted Server cert expires: Jan 31 10:22:47 2015 GMT Server license: Software Corporation users (expires 2013/02/21) Server license-ip: some ip:1666 Case Handling: sensitive The authentication of user is done using LDAP. Regards Chuck. On Tuesday, February 12, 2013 2:27:33 PM UTC+5:30, Christian Hammond wrote: Hi Chuck, I just wanted to give you a quick response. The person who would know the best on the project would be David, but he's out for the night (1AM here), so there will be a delay before he can respond. One thing to verify is that, on the command line (with that version of p4), you can do: P4PORT=ssl:blah p4 info Also, what sort of authentication mechanism are you using for Perforce? Christian -- Christian Hammond - chi...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Feb 12, 2013, at 12:52 AM, chuck j cjerr...@gmail.com wrote: Dear All, Now that we have made the RB server works with 1.7.4 + RBTools to work. We need to add perforce repository to reviewboard, when i add normal repository its gets added but when i add perforce repository will prefixing ssl: i am getting error message A repository was not found at the specified path. Following steps has been done from my end. Build P4Python with --ssl option providing the path of ssl libaray Updated the p4 client to 2012.2 Anybody encountered such issues, am i missing something. Regards, Chuck -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/**donate
Error while adding perforce 2012.2 repository to reviewboard 1.7.4
Dear All, Now that we have made the RB server works with 1.7.4 + RBTools to work. We need to add perforce repository to reviewboard, when i add normal repository its gets added but when i add perforce repository will prefixing ssl: i am getting error message A repository was not found at the specified path. Following steps has been done from my end. Build P4Python with --ssl option providing the path of ssl libaray Updated the p4 client to 2012.2 Anybody encountered such issues, am i missing something. Regards, Chuck -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Error while adding perforce 2012.2 repository to reviewboard 1.7.4
Hi , This is what i get for p4 info [root@svrrb1 works]# export P4USER=chuckj [root@svrrb1 works]# export P4PORT=ssl:some ip:1666 [root@svrrb1 works]# p4 login Enter password: User chuckj logged in. [root@svrrb1 works]# p4 info User name: chuckj Client name: svrrb1 Client host: svrrb1.na.software.com Client unknown. Current directory: /works Peer address: 182.16.43.144:42238 Client address: my ip address Server address: some ip:1666 Server root: /PFMETA/p4root Server date: 2013/02/12 01:09:47 -0800 PST Server uptime: 286:15:29 Server version: P4D/LINUX26X86_64/2012.2/50 (2013/01/18) Server encryption: encrypted Server cert expires: Jan 31 10:22:47 2015 GMT Server license: Software Corporation users (expires 2013/02/21) Server license-ip: some ip:1666 Case Handling: sensitive The authentication of user is done using LDAP. Regards Chuck. On Tuesday, February 12, 2013 2:27:33 PM UTC+5:30, Christian Hammond wrote: Hi Chuck, I just wanted to give you a quick response. The person who would know the best on the project would be David, but he's out for the night (1AM here), so there will be a delay before he can respond. One thing to verify is that, on the command line (with that version of p4), you can do: P4PORT=ssl:blah p4 info Also, what sort of authentication mechanism are you using for Perforce? Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Feb 12, 2013, at 12:52 AM, chuck j cjerr...@gmail.com javascript: wrote: Dear All, Now that we have made the RB server works with 1.7.4 + RBTools to work. We need to add perforce repository to reviewboard, when i add normal repository its gets added but when i add perforce repository will prefixing ssl: i am getting error message A repository was not found at the specified path. Following steps has been done from my end. Build P4Python with --ssl option providing the path of ssl libaray Updated the p4 client to 2012.2 Anybody encountered such issues, am i missing something. Regards, Chuck -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Error while adding perforce 2012.2 repository to reviewboard 1.7.4
Since i couldn't find openssl 1.0.1 rpm, I have to manually compile and build then install it to the default path, then later i have build p4python. root@svrrb1 p4python-2012.2.549493# python setup.py build --apidir /works/p4api-2012.2.585708/ --ssl /usr/local/ root@svrrb1 p4python-2012.2.549493# python setup.py install --apidir /works/p4api-2012.2.585708/ Assuming everything above working fine i test by providing below command line. import P4 p4 = P4.P4() p4.connect() Traceback (most recent call last): File stdin, line 1, in module File /usr/local/lib/python2.7/site-packages/P4.py, line 642, in connect P4API.P4Adapter.connect( self ) P4.P4Exception: [P4.connect()] Connect to server failed; check $P4PORT. SSL library must be at least version 1.0.1. Does my P4Python is build with OpenSSL.1.0.1 libarary, What is missing in my setup? I know this is not the right forum for above queries but this may provide some hint why adding repository to reviewboard is giving error. Please let me know if you need any more info, log for the same. - Chuck On Tuesday, February 12, 2013 2:51:15 PM UTC+5:30, chuck j wrote: Hi , This is what i get for p4 info [root@svrrb1 works]# export P4USER=chuckj [root@svrrb1 works]# export P4PORT=ssl:some ip:1666 [root@svrrb1 works]# p4 login Enter password: User chuckj logged in. [root@svrrb1 works]# p4 info User name: chuckj Client name: svrrb1 Client host: svrrb1.na.software.com Client unknown. Current directory: /works Peer address: 182.16.43.144:42238 Client address: my ip address Server address: some ip:1666 Server root: /PFMETA/p4root Server date: 2013/02/12 01:09:47 -0800 PST Server uptime: 286:15:29 Server version: P4D/LINUX26X86_64/2012.2/50 (2013/01/18) Server encryption: encrypted Server cert expires: Jan 31 10:22:47 2015 GMT Server license: Software Corporation users (expires 2013/02/21) Server license-ip: some ip:1666 Case Handling: sensitive The authentication of user is done using LDAP. Regards Chuck. On Tuesday, February 12, 2013 2:27:33 PM UTC+5:30, Christian Hammond wrote: Hi Chuck, I just wanted to give you a quick response. The person who would know the best on the project would be David, but he's out for the night (1AM here), so there will be a delay before he can respond. One thing to verify is that, on the command line (with that version of p4), you can do: P4PORT=ssl:blah p4 info Also, what sort of authentication mechanism are you using for Perforce? Christian -- Christian Hammond - chi...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Feb 12, 2013, at 12:52 AM, chuck j cjerr...@gmail.com wrote: Dear All, Now that we have made the RB server works with 1.7.4 + RBTools to work. We need to add perforce repository to reviewboard, when i add normal repository its gets added but when i add perforce repository will prefixing ssl: i am getting error message A repository was not found at the specified path. Following steps has been done from my end. Build P4Python with --ssl option providing the path of ssl libaray Updated the p4 client to 2012.2 Anybody encountered such issues, am i missing something. Regards, Chuck -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Error while adding perforce 2012.2 repository to reviewboard 1.7.4
Does my p4 info output gave expected output. [root@svrrb1 works]# p4 info User name: chuckj Client name: svrrb1 Client host: svrrb1.na.software.com Client unknown. Current directory: /works Peer address: 182.16.43.144:42238 Client address: my ip address Server address: some ip:1666 Server root: /PFMETA/p4root Server date: 2013/02/12 01:09:47 -0800 PST Server uptime: 286:15:29 Server version: P4D/LINUX26X86_64/2012.2/50 (2013/01/18) Server encryption: encrypted Server cert expires: Jan 31 10:22:47 2015 GMT Server license: Software Corporation users (expires 2013/02/21) Server license-ip: some ip:1666 Case Handling: sensitive On Tuesday, February 12, 2013 4:49:40 PM UTC+5:30, chuck j wrote: Since i couldn't find openssl 1.0.1 rpm, I have to manually compile and build then install it to the default path, then later i have build p4python. root@svrrb1 p4python-2012.2.549493# python setup.py build --apidir /works/p4api-2012.2.585708/ --ssl /usr/local/ root@svrrb1 p4python-2012.2.549493# python setup.py install --apidir /works/p4api-2012.2.585708/ Assuming everything above working fine i test by providing below command line. import P4 p4 = P4.P4() p4.connect() Traceback (most recent call last): File stdin, line 1, in module File /usr/local/lib/python2.7/site-packages/P4.py, line 642, in connect P4API.P4Adapter.connect( self ) P4.P4Exception: [P4.connect()] Connect to server failed; check $P4PORT. SSL library must be at least version 1.0.1. Does my P4Python is build with OpenSSL.1.0.1 libarary, What is missing in my setup? I know this is not the right forum for above queries but this may provide some hint why adding repository to reviewboard is giving error. Please let me know if you need any more info, log for the same. - Chuck On Tuesday, February 12, 2013 2:51:15 PM UTC+5:30, chuck j wrote: Hi , This is what i get for p4 info [root@svrrb1 works]# export P4USER=chuckj [root@svrrb1 works]# export P4PORT=ssl:some ip:1666 [root@svrrb1 works]# p4 login Enter password: User chuckj logged in. [root@svrrb1 works]# p4 info User name: chuckj Client name: svrrb1 Client host: svrrb1.na.software.com Client unknown. Current directory: /works Peer address: 182.16.43.144:42238 Client address: my ip address Server address: some ip:1666 Server root: /PFMETA/p4root Server date: 2013/02/12 01:09:47 -0800 PST Server uptime: 286:15:29 Server version: P4D/LINUX26X86_64/2012.2/50 (2013/01/18) Server encryption: encrypted Server cert expires: Jan 31 10:22:47 2015 GMT Server license: Software Corporation users (expires 2013/02/21) Server license-ip: some ip:1666 Case Handling: sensitive The authentication of user is done using LDAP. Regards Chuck. On Tuesday, February 12, 2013 2:27:33 PM UTC+5:30, Christian Hammond wrote: Hi Chuck, I just wanted to give you a quick response. The person who would know the best on the project would be David, but he's out for the night (1AM here), so there will be a delay before he can respond. One thing to verify is that, on the command line (with that version of p4), you can do: P4PORT=ssl:blah p4 info Also, what sort of authentication mechanism are you using for Perforce? Christian -- Christian Hammond - chi...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Feb 12, 2013, at 12:52 AM, chuck j cjerr...@gmail.com wrote: Dear All, Now that we have made the RB server works with 1.7.4 + RBTools to work. We need to add perforce repository to reviewboard, when i add normal repository its gets added but when i add perforce repository will prefixing ssl: i am getting error message A repository was not found at the specified path. Following steps has been done from my end. Build P4Python with --ssl option providing the path of ssl libaray Updated the p4 client to 2012.2 Anybody encountered such issues, am i missing something. Regards, Chuck -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com
Re: RB server upgrade from 1.6.1 to 1.7.4
Hi Christian, I would like to thank you for your response about upgrade. I went through with your comments and i was able to bring my server to 1.7.4. Also also want to bring to your notice regarding below warning i got after while upgrading my site. /usr/local/lib/python2.7/site-packages/pycrypto-2.6-py2.7-linux-x86_64.egg/Crypto/Util/number.py:57: PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild using libgmp = 5 to avoid timing attack vulnerability. How to resolve this? Do i need to build it libgmp again as message shows, will it make RB server report more issues. Thanks, -Chuck On Fri, Feb 1, 2013 at 6:58 PM, chuck j cjerry2...@gmail.com wrote: Thanks Christian for the response. Good to hear that upgrade is possible from 1.6.1 to 1.7.4 RB version, apart from the database backup do we need to take care of any thing else which will disturb our production setup and in case of any issue we should be able to go back to our original state, if you point us action item it would be really great. Few queries though 1. How does upgrade takes place, does it replace files by files ( I mean python scripts etc ) apart from db. 2. The Release note of 1.7.2 its been mentioned about below However, this requires that p4python is specially compiled with OpenSSL support, and that the system has development headers for OpenSSL 1.0.1. P4PythonInstaller doesn’t do this, so users who need this feature will currently have to compile p4python manually, providing the path to the SSL directory using --ssl Do we have any tech note for the above steps which end user needs to perform. Cheers, Chuck On Thu, Jan 31, 2013 at 2:50 PM, Christian Hammond chip...@chipx86.comwrote: Hi Chuck, I always recommend backing up your database first, but you should be able to upgrade from 1.6.1 to 1.7.4 without any real problems. There is a bug that some people hit a while back in older versions that introduced some stale upgrade data in the database. I meant to get a final fix out in 1.7.4, but it slipped. If your 'rb-site upgrade' complains about fields that already exist or something, e-mail and I'll give you the solution. Otherwise, you shouldn't have any problems. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 31, 2013 at 2:47 PM, chuck j cjerry2...@gmail.com wrote: Dear All, There has been lots of improvement done on RB server from version 1.6.1 till date, hence i would like to know if the upgrade from 1.6.1 to latest version is supported? If not then how should I bring my RB server 1.6.1 to latest state without loosing the existing data from my existing database. We need to upgrade because 1.7.2 has SSL feature implement and we have planned to upgrade perforce server to 2012.2. Please help. Appreciated your response and help Cheers, Chuck. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: RB server upgrade from 1.6.1 to 1.7.4
While sent an email to you, I face one issue. When i clicked to any of the old review request i see error message: Something broke! (Error 500) It appears something broke when you tried to go to here. This is either a bug in Review Board or a server configuration error. Please report this to your administrator. What is this weird messagehas upgrade went fine? Thanks, - Chuck On Wed, Feb 6, 2013 at 1:40 PM, chuck j cjerry2...@gmail.com wrote: Hi Christian, I would like to thank you for your response about upgrade. I went through with your comments and i was able to bring my server to 1.7.4. Also also want to bring to your notice regarding below warning i got after while upgrading my site. /usr/local/lib/python2.7/site-packages/pycrypto-2.6-py2.7-linux-x86_64.egg/Crypto/Util/number.py:57: PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild using libgmp = 5 to avoid timing attack vulnerability. How to resolve this? Do i need to build it libgmp again as message shows, will it make RB server report more issues. Thanks, -Chuck On Fri, Feb 1, 2013 at 6:58 PM, chuck j cjerry2...@gmail.com wrote: Thanks Christian for the response. Good to hear that upgrade is possible from 1.6.1 to 1.7.4 RB version, apart from the database backup do we need to take care of any thing else which will disturb our production setup and in case of any issue we should be able to go back to our original state, if you point us action item it would be really great. Few queries though 1. How does upgrade takes place, does it replace files by files ( I mean python scripts etc ) apart from db. 2. The Release note of 1.7.2 its been mentioned about below However, this requires that p4python is specially compiled with OpenSSL support, and that the system has development headers for OpenSSL 1.0.1. P4PythonInstaller doesn’t do this, so users who need this feature will currently have to compile p4python manually, providing the path to the SSL directory using --ssl Do we have any tech note for the above steps which end user needs to perform. Cheers, Chuck On Thu, Jan 31, 2013 at 2:50 PM, Christian Hammond chip...@chipx86.comwrote: Hi Chuck, I always recommend backing up your database first, but you should be able to upgrade from 1.6.1 to 1.7.4 without any real problems. There is a bug that some people hit a while back in older versions that introduced some stale upgrade data in the database. I meant to get a final fix out in 1.7.4, but it slipped. If your 'rb-site upgrade' complains about fields that already exist or something, e-mail and I'll give you the solution. Otherwise, you shouldn't have any problems. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 31, 2013 at 2:47 PM, chuck j cjerry2...@gmail.com wrote: Dear All, There has been lots of improvement done on RB server from version 1.6.1 till date, hence i would like to know if the upgrade from 1.6.1 to latest version is supported? If not then how should I bring my RB server 1.6.1 to latest state without loosing the existing data from my existing database. We need to upgrade because 1.7.2 has SSL feature implement and we have planned to upgrade perforce server to 2012.2. Please help. Appreciated your response and help Cheers, Chuck. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: RB server upgrade from 1.6.1 to 1.7.4
. return compiled_parent._render(context) File /usr/local/lib/python2.7/site-packages/Django-1.4.3-py2.7.egg/django/template/base.py in _render 134. return self.nodelist.render(context) File /usr/local/lib/python2.7/site-packages/Django-1.4.3-py2.7.egg/django/template/base.py in render 823. bit = self.render_node(node, context) File /usr/local/lib/python2.7/site-packages/Django-1.4.3-py2.7.egg/django/template/debug.py in render_node 74. return node.render(context) File /usr/local/lib/python2.7/site-packages/django_pipeline-1.3.0-py2.7.egg/pipeline/templatetags/compressed.py in render 34. paths = self.packager.compile(package.paths) File /usr/local/lib/python2.7/site-packages/django_pipeline-1.3.0-py2.7.egg/pipeline/packager.py in compile 95. return self.compiler.compile(paths, force=force) File /usr/local/lib/python2.7/site-packages/django_pipeline-1.3.0-py2.7.egg/pipeline/compilers/__init__.py in compile 40. compiler.compile_file(infile, outfile, outdated=outdated, force=force) File /usr/local/lib/python2.7/site-packages/django_pipeline-1.3.0-py2.7.egg/pipeline/compilers/less.py in compile_file 22. return self.execute_command(command, cwd=dirname(infile)) File /usr/local/lib/python2.7/site-packages/django_pipeline-1.3.0-py2.7.egg/pipeline/compilers/__init__.py in execute_command 101. raise CompilerError(error) Exception Type: CompilerError at /svrrb/dashboard/ Exception Value: /usr/bin/env: lessc: No such file or directory Please help. On Wed, Feb 6, 2013 at 1:47 PM, chuck j cjerry2...@gmail.com wrote: While sent an email to you, I face one issue. When i clicked to any of the old review request i see error message: Something broke! (Error 500) It appears something broke when you tried to go to here. This is either a bug in Review Board or a server configuration error. Please report this to your administrator. What is this weird messagehas upgrade went fine? Thanks, - Chuck On Wed, Feb 6, 2013 at 1:40 PM, chuck j cjerry2...@gmail.com wrote: Hi Christian, I would like to thank you for your response about upgrade. I went through with your comments and i was able to bring my server to 1.7.4. Also also want to bring to your notice regarding below warning i got after while upgrading my site. /usr/local/lib/python2.7/site-packages/pycrypto-2.6-py2.7-linux-x86_64.egg/Crypto/Util/number.py:57: PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild using libgmp = 5 to avoid timing attack vulnerability. How to resolve this? Do i need to build it libgmp again as message shows, will it make RB server report more issues. Thanks, -Chuck On Fri, Feb 1, 2013 at 6:58 PM, chuck j cjerry2...@gmail.com wrote: Thanks Christian for the response. Good to hear that upgrade is possible from 1.6.1 to 1.7.4 RB version, apart from the database backup do we need to take care of any thing else which will disturb our production setup and in case of any issue we should be able to go back to our original state, if you point us action item it would be really great. Few queries though 1. How does upgrade takes place, does it replace files by files ( I mean python scripts etc ) apart from db. 2. The Release note of 1.7.2 its been mentioned about below However, this requires that p4python is specially compiled with OpenSSL support, and that the system has development headers for OpenSSL 1.0.1. P4PythonInstaller doesn’t do this, so users who need this feature will currently have to compile p4python manually, providing the path to the SSL directory using --ssl Do we have any tech note for the above steps which end user needs to perform. Cheers, Chuck On Thu, Jan 31, 2013 at 2:50 PM, Christian Hammond chip...@chipx86.comwrote: Hi Chuck, I always recommend backing up your database first, but you should be able to upgrade from 1.6.1 to 1.7.4 without any real problems. There is a bug that some people hit a while back in older versions that introduced some stale upgrade data in the database. I meant to get a final fix out in 1.7.4, but it slipped. If your 'rb-site upgrade' complains about fields that already exist or something, e-mail and I'll give you the solution. Otherwise, you shouldn't have any problems. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 31, 2013 at 2:47 PM, chuck j cjerry2...@gmail.com wrote: Dear All, There has been lots of improvement done on RB server from version 1.6.1 till date, hence i would like to know if the upgrade from 1.6.1 to latest version is supported? If not then how should I bring my RB server 1.6.1 to latest state without loosing the existing data from my existing database. We need to upgrade because 1.7.2 has SSL feature implement and we have planned to upgrade perforce server
Re: RB server upgrade from 1.6.1 to 1.7.4
yes you are correct i followed the upgrade instruction from www.reviewboard.org To verify, when you upgraded using easy_install -U ReviewBoard, you then ran 'rb-site upgrade /path/to/site' I also saw below message, [root@svrrb1 www]# rb-site upgrade /var/www/svrrb /usr/local/lib/python2.7/site-packages/pycrypto-2.6-py2.7-linux-x86_64.egg/Crypto/Util/number.py:57: PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild using libgmp = 5 to avoid timing attack vulnerability. Rebuilding directory structure Upgrading site settings_local.py Updating database. This may take a while. The log output below, including warnings and errors, can be ignored unless upgrade fails. -- begin log output -- Creating tables ... Creating table extensions_registeredextension Creating table diffviewer_filediffdata Creating table hostingsvcs_hostingserviceaccount Upgrading Review Board from 1.6.1 to 1.7.4 There are unapplied evolutions for auth. There are unapplied evolutions for accounts. There are unapplied evolutions for diffviewer. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. Adding baseline version for new models Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) Evolution successful. --- end log output --- I am using linux: 2.6.18-164.el5 #1 SMP Tue Aug 18 15:51:48 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux [root@svrrb1 rb]# pwd /var/www/svrrb/htdocs/static/rb [root@svrrb1 rb]# ls -l total 12 drwxr-xr-x 2 root root 4096 Feb 5 23:15 css drwxr-xr-x 5 root root 4096 Feb 5 23:15 images drwxr-xr-x 5 root root 4096 Feb 5 23:15 js [root@svrrb1 static]# pwd /var/www/svrrb/htdocs/static [root@svrrb1 static]# ls -lrt total 16 lrwxrwxrwx 1 root root 95 Feb 5 23:18 rb - /usr/local/lib/python2.7/site-packages/ReviewBoard-1.7.4-py2.7.egg/reviewboard/htdocs/static/rb lrwxrwxrwx 1 root root 96 Feb 5 23:18 lib - /usr/local/lib/python2.7/site-packages/ReviewBoard-1.7.4-py2.7.egg/reviewboard/htdocs/static/lib lrwxrwxrwx 1 root root 77 Feb 5 23:18 djblets - /usr/local/lib/python2.7/site-packages/Djblets-0.7.9-py2.7.egg/djblets/static lrwxrwxrwx 1 root root 98 Feb 5 23:18 admin - /usr/local/lib/python2.7/site-packages/ReviewBoard-1.7.4-py2.7.egg/reviewboard/htdocs/static/admin What to do !! On Wed, Feb 6, 2013 at 2:12 PM, Christian Hammond chip...@chipx86.comwrote: Yep, it's looking for lessc, which it shouldn't be. That means it's not finding the generated static media files, probably. Or some other strange configuration problem. Probably an installation problem. To verify, when you upgraded using easy_install -U ReviewBoard, you then ran 'rb-site upgrade /path/to/site', correct? If you did do the rb-site upgrade when you installed 1.7.4, then can you show me what's in your $sitedir/htdocs/static/rb/css/ and $sitedir/htdocs/static/djblets/css/ directories? What version of what distro are you using? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Feb 6, 2013 at 2:04 PM, chuck j cjerry2...@gmail.com wrote: Here are the logs its seems it searching for lessc executable. Environment: Request Method: GET Request URL: http://scrrb1.na.software.com/svrrb/dashboard/?view=to-me Django Version: 1.4.3 Python Version: 2.7.2 Installed Applications: ['django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.markup', 'django.contrib.sites', 'django.contrib.sessions', 'django.contrib.staticfiles', 'djblets.datagrid', 'djblets.extensions', 'djblets.feedview', 'djblets.gravatars', 'djblets.log', 'djblets.pipeline', 'djblets.siteconfig', 'djblets.util', 'djblets.webapi', 'pipeline', 'reviewboard.accounts', 'reviewboard.admin', 'reviewboard.attachments', 'reviewboard.changedescs', 'reviewboard.diffviewer', 'reviewboard.extensions', 'reviewboard.hostingsvcs', 'reviewboard.notifications', 'reviewboard.reviews', 'reviewboard.reviews.ui', 'reviewboard.scmtools', 'reviewboard.site', 'reviewboard.ssh', 'reviewboard.webapi', 'django_evolution'] Installed Middleware: ['django.middleware.gzip.GZipMiddleware', 'reviewboard.admin.middleware.InitReviewBoardMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.doc.XViewMiddleware', 'django.middleware.http.ConditionalGetMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'djblets.siteconfig.middleware.SettingsMiddleware', 'reviewboard.admin.middleware.LoadSettingsMiddleware', 'djblets.extensions.middleware.ExtensionsMiddleware', 'djblets.log.middleware.LoggingMiddleware
Re: RB server upgrade from 1.6.1 to 1.7.4
Yes, i have restarted the Apache afterward. Here you go: here is the content of ccs /var/www/svrrb/htdocs/static/rb/css admin.1f278e6382ef.css admin.min.c8a349cc3f7d.css dashboard.cb3f25c48eb7.cssdiffviewer.css js-tests.70d6ede4e69e.css reviews.css syntax.5f96383e25b8.css admin.60fbb7d18d8e.lessadmin.min.css dashboard.cebe4c36b08b.less diffviewer.less js-tests.9844a908a7ed.less reviews.less syntax.css admin.css common.2273b0c06c33.css dashboard.css docs.css js-tests.css reviews.min.af2c67b6345a.css admin-dashboard.0d89aa70a294.less common.7ace5f78ab0a.less dashboard.lessdocs.d72d2b5acebd.css js-tests.less reviews.min.css admin-dashboard.38adf3895ca1.css common.css defs.d9851fd5c124.lessie_hacks.css js-tests.min.70d6ede4e69e.css search.0553e42c0d00.less admin-dashboard.csscommon.less defs.less ie_hacks.e31a795a9b81.css js-tests.min.css search.47a5f4d644fe.css admin-dashboard.less common.min.8d7bf2d2a824.css diffviewer.0df7f678336d.less iphone.css reviews.222d0930c962.less search.css admin.less common.min.css diffviewer.b6c23a8b7583.css iphone.e915fbaf08c1.css reviews.6b97b76026b7.css search.less /var/www/svrrb/htdocs/static/djblets/css [root@svrrb1 css]# ls admin.67612c83bb86.css admin.css datagrid.1a0aafea202a.css datagrid.css extensions.43c3ee635a23.css extensions.css *Linux distribution:* Red Hat Enterprise Linux Server release 5.4 (Tikanga) Kernel \r on an \m Thank you for you help. Please let me know if you need actual files to look into, i will sent it to you. -CJ On Wed, Feb 6, 2013 at 2:33 PM, Christian Hammond chip...@chipx86.comwrote: And you restarted Apache afterward? I'll need to see the contents of the css directories. I also still need to know what version of what Linux distro you're using. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Feb 6, 2013 at 2:24 PM, chuck j cjerry2...@gmail.com wrote: yes you are correct i followed the upgrade instruction from www.reviewboard.org To verify, when you upgraded using easy_install -U ReviewBoard, you then ran 'rb-site upgrade /path/to/site' I also saw below message, [root@svrrb1 www]# rb-site upgrade /var/www/svrrb /usr/local/lib/python2.7/site-packages/pycrypto-2.6-py2.7-linux-x86_64.egg/Crypto/Util/number.py:57: PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild using libgmp = 5 to avoid timing attack vulnerability. Rebuilding directory structure Upgrading site settings_local.py Updating database. This may take a while. The log output below, including warnings and errors, can be ignored unless upgrade fails. -- begin log output -- Creating tables ... Creating table extensions_registeredextension Creating table diffviewer_filediffdata Creating table hostingsvcs_hostingserviceaccount Upgrading Review Board from 1.6.1 to 1.7.4 There are unapplied evolutions for auth. There are unapplied evolutions for accounts. There are unapplied evolutions for diffviewer. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. Adding baseline version for new models Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) Evolution successful. --- end log output --- I am using linux: 2.6.18-164.el5 #1 SMP Tue Aug 18 15:51:48 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux [root@svrrb1 rb]# pwd /var/www/svrrb/htdocs/static/rb [root@svrrb1 rb]# ls -l total 12 drwxr-xr-x 2 root root 4096 Feb 5 23:15 css drwxr-xr-x 5 root root 4096 Feb 5 23:15 images drwxr-xr-x 5 root root 4096 Feb 5 23:15 js [root@svrrb1 static]# pwd /var/www/svrrb/htdocs/static [root@svrrb1 static]# ls -lrt total 16 lrwxrwxrwx 1 root root 95 Feb 5 23:18 rb - /usr/local/lib/python2.7/site-packages/ReviewBoard-1.7.4-py2.7.egg/reviewboard/htdocs/static/rb lrwxrwxrwx 1 root root 96 Feb 5 23:18 lib - /usr/local/lib/python2.7/site-packages/ReviewBoard-1.7.4-py2.7.egg/reviewboard/htdocs/static/lib lrwxrwxrwx 1 root root 77 Feb 5 23:18 djblets - /usr/local/lib/python2.7/site-packages/Djblets-0.7.9-py2.7.egg/djblets/static lrwxrwxrwx 1 root root 98 Feb 5 23:18 admin - /usr/local/lib/python2.7/site-packages/ReviewBoard-1.7.4-py2.7.egg/reviewboard/htdocs/static/admin What to do !! On Wed, Feb 6, 2013 at 2:12 PM, Christian Hammond chip...@chipx86.comwrote: Yep, it's looking for lessc, which it shouldn't be. That means it's not finding the generated static media files, probably. Or some other strange configuration problem. Probably an installation problem. To verify, when you
Re: RB server upgrade from 1.6.1 to 1.7.4
Thank you !!, yes it is happening for all the review request, also after restart i am not able to open login page also and it crashed with the same compilation error. CompilerError at /svrrb/dashboard/ /usr/bin/env: lessc: No such file or directory Request Method: GET Request URL: http://svrrb1.na.software.com/svrrb/dashboard/ Django Version: 1.4.3 Exception Type: CompilerError Exception Value: /usr/bin/env: lessc: No such file or directory Exception Location: /usr/local/lib/python2.7/site-packages/django_pipeline-1.3.0-py2.7.egg/pipeline/compilers/__init__.py in execute_command, line 101 Python Executable: /usr/bin/python One question though while we try to fix this issue. Can we install reviewboard fresh and then perform database base upgrade, do we have such option? in case we land up no where :( Thing are looking dark now On Wed, Feb 6, 2013 at 3:10 PM, Christian Hammond chip...@chipx86.comwrote: All the files match correctly, so I'm left to believe that Review Board/Apache's unable to open them, and is trying to fall back on creating new ones (using lessc). Does this happen for all review requests? I'd imagine it'd have to. Is SELinux turned on? Try turning it off. You also may want to try restarting memcached, in case something bad is cached somewhere. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Feb 6, 2013 at 2:44 PM, chuck j cjerry2...@gmail.com wrote: Yes, i have restarted the Apache afterward. Here you go: here is the content of ccs /var/www/svrrb/htdocs/static/rb/css admin.1f278e6382ef.css admin.min.c8a349cc3f7d.css dashboard.cb3f25c48eb7.cssdiffviewer.css js-tests.70d6ede4e69e.css reviews.css syntax.5f96383e25b8.css admin.60fbb7d18d8e.lessadmin.min.css dashboard.cebe4c36b08b.less diffviewer.less js-tests.9844a908a7ed.less reviews.less syntax.css admin.css common.2273b0c06c33.css dashboard.css docs.css js-tests.css reviews.min.af2c67b6345a.css admin-dashboard.0d89aa70a294.less common.7ace5f78ab0a.less dashboard.lessdocs.d72d2b5acebd.css js-tests.less reviews.min.css admin-dashboard.38adf3895ca1.css common.css defs.d9851fd5c124.lessie_hacks.css js-tests.min.70d6ede4e69e.css search.0553e42c0d00.less admin-dashboard.csscommon.less defs.less ie_hacks.e31a795a9b81.css js-tests.min.css search.47a5f4d644fe.css admin-dashboard.less common.min.8d7bf2d2a824.css diffviewer.0df7f678336d.less iphone.css reviews.222d0930c962.less search.css admin.less common.min.css diffviewer.b6c23a8b7583.css iphone.e915fbaf08c1.css reviews.6b97b76026b7.css search.less /var/www/svrrb/htdocs/static/djblets/css [root@svrrb1 css]# ls admin.67612c83bb86.css admin.css datagrid.1a0aafea202a.css datagrid.css extensions.43c3ee635a23.css extensions.css *Linux distribution:* Red Hat Enterprise Linux Server release 5.4 (Tikanga) Kernel \r on an \m Thank you for you help. Please let me know if you need actual files to look into, i will sent it to you. -CJ On Wed, Feb 6, 2013 at 2:33 PM, Christian Hammond chip...@chipx86.comwrote: And you restarted Apache afterward? I'll need to see the contents of the css directories. I also still need to know what version of what Linux distro you're using. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Feb 6, 2013 at 2:24 PM, chuck j cjerry2...@gmail.com wrote: yes you are correct i followed the upgrade instruction from www.reviewboard.org To verify, when you upgraded using easy_install -U ReviewBoard, you then ran 'rb-site upgrade /path/to/site' I also saw below message, [root@svrrb1 www]# rb-site upgrade /var/www/svrrb /usr/local/lib/python2.7/site-packages/pycrypto-2.6-py2.7-linux-x86_64.egg/Crypto/Util/number.py:57: PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild using libgmp = 5 to avoid timing attack vulnerability. Rebuilding directory structure Upgrading site settings_local.py Updating database. This may take a while. The log output below, including warnings and errors, can be ignored unless upgrade fails. -- begin log output -- Creating tables ... Creating table extensions_registeredextension Creating table diffviewer_filediffdata Creating table hostingsvcs_hostingserviceaccount Upgrading Review Board from 1.6.1 to 1.7.4 There are unapplied evolutions for auth. There are unapplied evolutions for accounts. There are unapplied evolutions for diffviewer. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. Adding baseline
Re: RB server upgrade from 1.6.1 to 1.7.4
Also SElinux is turned off. #selinuxenabled echo enabled || echo disabled disabled On Wed, Feb 6, 2013 at 3:22 PM, chuck j cjerry2...@gmail.com wrote: Thank you !!, yes it is happening for all the review request, also after restart i am not able to open login page also and it crashed with the same compilation error. CompilerError at /svrrb/dashboard/ /usr/bin/env: lessc: No such file or directory Request Method: GET Request URL: http://svrrb1.na.software.com/svrrb/dashboard/ Django Version: 1.4.3 Exception Type: CompilerError Exception Value: /usr/bin/env: lessc: No such file or directory Exception Location: /usr/local/lib/python2.7/site-packages/django_pipeline-1.3.0-py2.7.egg/pipeline/compilers/__init__.py in execute_command, line 101 Python Executable: /usr/bin/python One question though while we try to fix this issue. Can we install reviewboard fresh and then perform database base upgrade, do we have such option? in case we land up no where :( Thing are looking dark now On Wed, Feb 6, 2013 at 3:10 PM, Christian Hammond chip...@chipx86.comwrote: All the files match correctly, so I'm left to believe that Review Board/Apache's unable to open them, and is trying to fall back on creating new ones (using lessc). Does this happen for all review requests? I'd imagine it'd have to. Is SELinux turned on? Try turning it off. You also may want to try restarting memcached, in case something bad is cached somewhere. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Feb 6, 2013 at 2:44 PM, chuck j cjerry2...@gmail.com wrote: Yes, i have restarted the Apache afterward. Here you go: here is the content of ccs /var/www/svrrb/htdocs/static/rb/css admin.1f278e6382ef.css admin.min.c8a349cc3f7d.css dashboard.cb3f25c48eb7.cssdiffviewer.css js-tests.70d6ede4e69e.css reviews.css syntax.5f96383e25b8.css admin.60fbb7d18d8e.lessadmin.min.css dashboard.cebe4c36b08b.less diffviewer.less js-tests.9844a908a7ed.less reviews.less syntax.css admin.css common.2273b0c06c33.css dashboard.css docs.css js-tests.css reviews.min.af2c67b6345a.css admin-dashboard.0d89aa70a294.less common.7ace5f78ab0a.less dashboard.lessdocs.d72d2b5acebd.css js-tests.less reviews.min.css admin-dashboard.38adf3895ca1.css common.css defs.d9851fd5c124.lessie_hacks.css js-tests.min.70d6ede4e69e.css search.0553e42c0d00.less admin-dashboard.csscommon.less defs.less ie_hacks.e31a795a9b81.css js-tests.min.css search.47a5f4d644fe.css admin-dashboard.less common.min.8d7bf2d2a824.css diffviewer.0df7f678336d.less iphone.css reviews.222d0930c962.less search.css admin.less common.min.css diffviewer.b6c23a8b7583.css iphone.e915fbaf08c1.css reviews.6b97b76026b7.css search.less /var/www/svrrb/htdocs/static/djblets/css [root@svrrb1 css]# ls admin.67612c83bb86.css admin.css datagrid.1a0aafea202a.css datagrid.css extensions.43c3ee635a23.css extensions.css *Linux distribution:* Red Hat Enterprise Linux Server release 5.4 (Tikanga) Kernel \r on an \m Thank you for you help. Please let me know if you need actual files to look into, i will sent it to you. -CJ On Wed, Feb 6, 2013 at 2:33 PM, Christian Hammond chip...@chipx86.comwrote: And you restarted Apache afterward? I'll need to see the contents of the css directories. I also still need to know what version of what Linux distro you're using. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Feb 6, 2013 at 2:24 PM, chuck j cjerry2...@gmail.com wrote: yes you are correct i followed the upgrade instruction from www.reviewboard.org To verify, when you upgraded using easy_install -U ReviewBoard, you then ran 'rb-site upgrade /path/to/site' I also saw below message, [root@svrrb1 www]# rb-site upgrade /var/www/svrrb /usr/local/lib/python2.7/site-packages/pycrypto-2.6-py2.7-linux-x86_64.egg/Crypto/Util/number.py:57: PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild using libgmp = 5 to avoid timing attack vulnerability. Rebuilding directory structure Upgrading site settings_local.py Updating database. This may take a while. The log output below, including warnings and errors, can be ignored unless upgrade fails. -- begin log output -- Creating tables ... Creating table extensions_registeredextension Creating table diffviewer_filediffdata Creating table hostingsvcs_hostingserviceaccount Upgrading Review Board from 1.6.1 to 1.7.4 There are unapplied evolutions for auth
Re: RB server upgrade from 1.6.1 to 1.7.4
Sure please see below:
# Site-specific configuration settings for Review Board
# Definitions of these settings can be found at
# http://docs.djangoproject.com/en/dev/ref/settings/
# Database configuration
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.mysql',
'NAME': 'svrrb',
'USER': 'username',
'PASSWORD': 'password',
'HOST': 'localhost',
'PORT': '',
},
}
# Unique secret key. Don't share this with anybody.
SECRET_KEY = 'key value '
# Cache backend settings.
CACHES = {
'default': {
'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
'LOCATION': 'localhost:11211',
},
}
# Extra site information.
SITE_ID = 1
SITE_ROOT = '/svrrb/'
FORCE_SCRIPT_NAME = ''
DEBUG = True
On Wed, Feb 6, 2013 at 3:32 PM, Christian Hammond chip...@chipx86.comwrote:
Can you provide your settings_local.py file? Make sure to remove your
database information and your SECRET_KEY first!
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Feb 6, 2013 at 3:28 PM, chuck j cjerry2...@gmail.com wrote:
Also SElinux is turned off.
#selinuxenabled echo enabled || echo disabled
disabled
On Wed, Feb 6, 2013 at 3:22 PM, chuck j cjerry2...@gmail.com wrote:
Thank you !!,
yes it is happening for all the review request, also after restart i am
not able to open login page also and it crashed with the same compilation
error.
CompilerError at /svrrb/dashboard/
/usr/bin/env: lessc: No such file or directory
Request Method: GET
Request URL: http://svrrb1.na.software.com/svrrb/dashboard/
Django Version: 1.4.3
Exception Type: CompilerError
Exception Value:
/usr/bin/env: lessc: No such file or directory
Exception Location:
/usr/local/lib/python2.7/site-packages/django_pipeline-1.3.0-py2.7.egg/pipeline/compilers/__init__.py
in execute_command, line 101
Python Executable: /usr/bin/python
One question though while we try to fix this issue.
Can we install reviewboard fresh and then perform database base upgrade,
do we have such option? in case we land up no where :(
Thing are looking dark now
On Wed, Feb 6, 2013 at 3:10 PM, Christian Hammond chip...@chipx86.comwrote:
All the files match correctly, so I'm left to believe that Review
Board/Apache's unable to open them, and is trying to fall back on creating
new ones (using lessc).
Does this happen for all review requests? I'd imagine it'd have to.
Is SELinux turned on? Try turning it off.
You also may want to try restarting memcached, in case something bad is
cached somewhere.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Feb 6, 2013 at 2:44 PM, chuck j cjerry2...@gmail.com wrote:
Yes, i have restarted the Apache afterward.
Here you go:
here is the content of ccs /var/www/svrrb/htdocs/static/rb/css
admin.1f278e6382ef.css admin.min.c8a349cc3f7d.css
dashboard.cb3f25c48eb7.cssdiffviewer.css
js-tests.70d6ede4e69e.css reviews.css
syntax.5f96383e25b8.css
admin.60fbb7d18d8e.lessadmin.min.css
dashboard.cebe4c36b08b.less diffviewer.less
js-tests.9844a908a7ed.less reviews.less syntax.css
admin.css common.2273b0c06c33.css
dashboard.css docs.css
js-tests.css reviews.min.af2c67b6345a.css
admin-dashboard.0d89aa70a294.less common.7ace5f78ab0a.less
dashboard.lessdocs.d72d2b5acebd.css
js-tests.less reviews.min.css
admin-dashboard.38adf3895ca1.css common.css
defs.d9851fd5c124.lessie_hacks.css
js-tests.min.70d6ede4e69e.css search.0553e42c0d00.less
admin-dashboard.csscommon.less
defs.less ie_hacks.e31a795a9b81.css
js-tests.min.css search.47a5f4d644fe.css
admin-dashboard.less common.min.8d7bf2d2a824.css
diffviewer.0df7f678336d.less iphone.css
reviews.222d0930c962.less search.css
admin.less common.min.css
diffviewer.b6c23a8b7583.css iphone.e915fbaf08c1.css
reviews.6b97b76026b7.css search.less
/var/www/svrrb/htdocs/static/djblets/css
[root@svrrb1 css]# ls
admin.67612c83bb86.css admin.css datagrid.1a0aafea202a.css
datagrid.css extensions.43c3ee635a23.css extensions.css
*Linux distribution:*
Red Hat Enterprise Linux Server release 5.4 (Tikanga)
Kernel \r on an \m
Thank you for you help.
Please let me know if you need actual files to look into, i will sent it
to you.
-CJ
On Wed, Feb 6, 2013 at 2:33 PM, Christian Hammond
chip...@chipx86.comwrote:
And you restarted Apache afterward?
I'll need to see the contents of the css directories.
I also still need to know what version of what Linux distro you're using.
Christian
--
Christian
posting few files instead of all files present in changes list to reviewboard.
Dear All, I am using RBTools 0.4.3, I want to post fewer files to reviewboard instead of all the files present in the changes list. How can i do this? Are we supporting such features in RBTools. Please let us know which option i shall be using. Regards, Chuck -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: RB server upgrade from 1.6.1 to 1.7.4
Thanks Christian for the response. Good to hear that upgrade is possible from 1.6.1 to 1.7.4 RB version, apart from the database backup do we need to take care of any thing else which will disturb our production setup and in case of any issue we should be able to go back to our original state, if you point us action item it would be really great. Few queries though 1. How does upgrade takes place, does it replace files by files ( I mean python scripts etc ) apart from db. 2. The Release note of 1.7.2 its been mentioned about below However, this requires that p4python is specially compiled with OpenSSL support, and that the system has development headers for OpenSSL 1.0.1. P4PythonInstaller doesn’t do this, so users who need this feature will currently have to compile p4python manually, providing the path to the SSL directory using --ssl Do we have any tech note for the above steps which end user needs to perform. Cheers, Chuck On Thu, Jan 31, 2013 at 2:50 PM, Christian Hammond chip...@chipx86.comwrote: Hi Chuck, I always recommend backing up your database first, but you should be able to upgrade from 1.6.1 to 1.7.4 without any real problems. There is a bug that some people hit a while back in older versions that introduced some stale upgrade data in the database. I meant to get a final fix out in 1.7.4, but it slipped. If your 'rb-site upgrade' complains about fields that already exist or something, e-mail and I'll give you the solution. Otherwise, you shouldn't have any problems. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 31, 2013 at 2:47 PM, chuck j cjerry2...@gmail.com wrote: Dear All, There has been lots of improvement done on RB server from version 1.6.1 till date, hence i would like to know if the upgrade from 1.6.1 to latest version is supported? If not then how should I bring my RB server 1.6.1 to latest state without loosing the existing data from my existing database. We need to upgrade because 1.7.2 has SSL feature implement and we have planned to upgrade perforce server to 2012.2. Please help. Appreciated your response and help Cheers, Chuck. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RB server upgrade from 1.6.1 to 1.7.4
Dear All, There has been lots of improvement done on RB server from version 1.6.1 till date, hence i would like to know if the upgrade from 1.6.1 to latest version is supported? If not then how should I bring my RB server 1.6.1 to latest state without loosing the existing data from my existing database. We need to upgrade because 1.7.2 has SSL feature implement and we have planned to upgrade perforce server to 2012.2. Please help. Appreciated your response and help Cheers, Chuck. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RB server doing caching a lot
Hi All, We have installed RB server in one of the Linux machine with 8GB of Ram, when i tried free -m command i can see that lots of memory is been consumed for caching due to which the free memory are getting reduced very fast. I have read somewhere that RB does lots of caching, How to avoid this issue. Regards, Chuck -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Email not getting to the users
Hi All, I have been using Review board server from one year with very less issues, thanks for this wonderful tool, but recently many of the users from my company reported they are not getting email notification after successful raising a review request and publish the review id to approver, even if any comments added to the review id. E-Mail setting has the email server name which we have provided with port 25. I tried to Google, but could not get much information also could not get much info in forum site. May i know what could be the reason for this email issue. Regards, Chuck -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
