just for clarification: The encoding of the file content is ANSI but the
files don´t contain clean ANSI. The commit messages are no problem.
Tom Schäfer schrieb am Montag, 26. Juni 2023 um 09:07:24 UTC+2:
> Hi Christian,
>
> yes the commits should all be using ANSI standard encoding
Hi Christian,
yes the commits should all be using ANSI standard encoding as we use
Windows the the commits but umlauts and ß/€ are non printable characters
there.
Tom
Christian Hammond schrieb am Freitag, 23. Juni 2023 um 23:24:56 UTC+2:
> Hi Tom,
>
> Do you know what character se
the ldap.initialize
ldapo.set_option(ldap.OPT_X_TLS_CACERTFILE, '/site/Root_CA.crt')
ldapo.set_option(ldap.OPT_X_TLS_NEWCTX, 0)
Then the python-ldap recognises the ca cert file and ldap is working. Not
very intuitive but good enough for us now ;)
Greetings,
Tom
Christian Hammond schrieb am
Hi all,
we use ReviewBoard 6.0 beta1 with the docker-compose setup.
We have linked our SVN repository against the Tool and run into issues with
encoding.
If we have umlauts in the commit message or the content the following error
occurs in the logsfile:
2023-06-23 09:25:45,616 - ERROR - -
Hi there,
I have the same issue now and i´m wondering if there is any solution to
this.
installed Reviewboard 6.0 beta1and tried setup LDAP authentication with
LDAPS.
*OS* : Ubuntu 22.04.2
*ReviewBoard Version* : 6.0 beta1
LDAP Config:
LDAP Server: ldaps://ldaps.mycompany.com:636
*Use TLS
ing" will also perform
the publish.
---
-e --existing VALUE existing request ID to update
---
Thanks,
Tom
--
Supercharge your Review Board with Power Pack:
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons:
https://rbcommons.com/
Ha
Hi,
Is there any way to extract the entire list of users along with their group
access, permissions, last login date, etc?
How about default reviewers?
Thanks
--
Supercharge your Review Board with Power Pack:
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check
When attempting to modify an existing repository, we're seeing the
following error: A repository with this path already exists
Currently running 2.0.13. Is this something that has been addressed in the
latest release? Otherwise any ideas on how we can get around this?
--
Supercharge your
root 4096 Nov 12 11:48 conf
drwxr-xr-x. 2 apache root 4096 Nov 12 11:42 data
drwxr-xr-x. 4 apache root 4096 Nov 12 12:21 htdocs
drwxr-xr-x. 2 apache root 4096 Nov 12 11:42 logs
drwxrwxrwx. 2 apache root 4096 Nov 12 11:42 tmp
Any help/guidance would be greatly appreciated!
-Tom
--
Get
Again, the use of this version is by choice for a class.
ok, got the svn issues figured out. Now I'm on to an email issue.
I tried to configure the smtp server to use gmail's smtp settings. I used
smtp.gmail.com and port 465. I set use TLS authentication. The username
and email are valid.
considering as I never heard of them, no I don 't think so.
On Saturday, March 22, 2014 2:02:45 PM UTC-4, Tom Moore wrote:
Again, the use of this version is by choice for a class.
ok, got the svn issues figured out. Now I'm on to an email issue.
I tried to configure the smtp server to use
First, I know that RC1 is out. We are using Beta3 for a class in QA, and
want to be using an older incomplete version.
We installed Beta 3 following all the steps and got the Reviewboard site up
and running. Added users and even had a sample (non-diff) review added.
When I add a svn
It was python-subvertpy_0.8.10-1. I'm running ubuntu 12.4 LTS and that was
the version of SubvertPy that got installed by default. I switched to
PySVN and it fixed the error. Thanks for the assist!
On Thursday, March 20, 2014 9:46:52 PM UTC-4, Christian Hammond wrote:
Hi Tom,
I really
Are there any plans to provide auto-closing of old reviews (or a way to
batch close lots at once) as a built-in feature?
On Thursday, 18 October 2012 19:53:28 UTC+1, Christian Hammond wrote:
If they're showing up in people's dashboards, people need to get in the
habit of closing their review
I need help with a problem with post-review when it's invoked within
commitinfo under CVS. CVS and RB 1.6.3 are running on separate Linux
servers. RBtools are installed on the CVS server. I have an apparently
valid repository definition in the RB admin web interface, the path
for which is:
I'm trying to use post-review in a CVS commit hook (via commitinfo).
If I run post-review manually, it works as expected. If I run the
exact same command line via the commit hook, it fails with the
message:
The current directory does not contain a checkout from a supported
source code
That's right. It's a local git clone, RB has access to it.
It's in sync and the change should be pushed using a post-commit on my local
working copy.
Tom De Vylder
On 18 Mar 2011, at 08:44, Christian Hammond wrote:
Ah, are you using a local Git clone that Review Board has access
Hm, seemed the problem was caused by the syncing.
I've fixed it using a simple git pre-commit hook:
#!/bin/sh
if git rev-parse --verify HEAD /dev/null 21
then
ssh user@server cd /repo; git pull /dev/null
fi
Thanks for the advice!
Tom De Vylder
On 18 Mar 2011, at 09:39, Christian
a/test-review.pp b/test-review.pp
index
c8d50071517379635faf795e858fb3d52a190c19..5894afa86f2b179d91df0bcb4e59713a3908ee16
100644
--- a/test-review.pp
+++ b/test-review.pp
Tom De Vylder
On 16 Mar 2011, at 23:04, Christian Hammond wrote:
Hi Tom,
Most likely, it's the short SHA1. If you
Hi everyone,
I've been struggling trying to get post-review to post a patch to the web
interface.
Each time I try to submit a patch post-review complains that it can't find a
file
The file specified with --diff-filename is uploaded each time.
So my guess is that it can't find the file that
Hi,
I was wondering if it would be possible to have a 'collapse all' (and
perhaps 'expand all') option in the header of each file diff in the
diff view? Currently, there is only a global expand-all/collapse-all
option.
If I accidentally expand a large hidden section in a file diff, the
only way
Assuming that the files are marked as Binary files in Perforce, Review-Board
should ignore them and properly say something along the lines of Binary
files differ.
-Tom
On Tue, Dec 1, 2009 at 6:51 PM, Kunjal kunjal.par...@gmail.com wrote:
Hello,
In our development environment, we have lot
Apache Solr - http://lucene.apache.org/solr/
http://wiki.apache.org/solr/SolPython
PySolr - http://code.google.com/p/pysolr/
Whether they will be less of a pain to install, I simply don't know.
-Tom
On Wed, Oct 14, 2009 at 5:09 PM, Christian Hammond chip...@chipx86.comwrote:
No, but good
Yup. What you described seems to be the case. I make sure that everyone
takes a look at the diff prior to submitting (there's an issue with
diff/patch when there isn't an ending newline that prevents it from showing)
just to make sure it works correctly.
-Tom
On Mon, Sep 28, 2009 at 10:30 AM
Correct. The Expand links that expand individual files is not working
correctly. Expand All seems to work however...
-Tom
On Fri, Sep 25, 2009 at 10:35 AM, Thilo-Alexander Ginkel
th...@ginkel.comwrote:
On Fri, Sep 25, 2009 at 17:31, Thilo-Alexander Ginkel th...@ginkel.comwrote:
can
http://www.mail-archive.com/reviewboard@googlegroups.com/msg02548.htmldescribes
the solution the P4PASSWORD issue. I'm not sure if it got much
further than that...
-Tom
On Tue, Sep 22, 2009 at 2:29 PM, Hui Lin hui@bankofamerica.com wrote:
I am confused here. What does the diff uploading
On Aug 27, 2009, at 5:05 PM, Christian Hammond chip...@chipx86.com
wrote:
Make sure for Perforce that the Path is an exact match for the
server name specified in:
p4 info
If they differ at all, it will not work.
Christian
--
Christian Hammond - chip...@chipx86.com
Review
in the same absolute location
(thus in a section of the file you expanded without any diff), rather
than remaining around the originally highlighted diff lines.
On Aug 24, 10:39 am, Christian Hammond chip...@chipx86.com wrote:
Hi Tom,
Would you mind filing a bug on this? We'll look at getting
hey Christian,
I'm on 1.0.1, with perforce as the repository.
Cheers
On Aug 23, 7:04 am, Christian Hammond chip...@chipx86.com wrote:
Hi Tom,
What version of Review Board are you running?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board -http://www.review-board.org
Plus we're really Linux guys and most of our users are installing on Linux
On a related note, I thought I'd mention the problems I had installing
with CentOS.
It comes with python 2.4, and the untar features are unavailable (2.5
and above apparently), so I had to manually work out some of the
invoked with --diff-cmd? I can't force the rest
of the company to install 'diff', and certainly when they manually
upload the diffs they are not using --diff-cmd to generate them, so
why is post-review?
Thanks for the insight!
-tree
--
Tom Emerson
tremer...@gmail.com
http://treerex.blogspot.com
On Thu, May 7, 2009 at 10:08 AM, Tom Emerson tremer...@gmail.com wrote:
[...]
Why is svn diff being invoked with --diff-cmd? I can't force the rest
of the company to install 'diff', and certainly when they manually
upload the diffs they are not using --diff-cmd to generate them, so
why
not a showstopper, it's merely an inconvenience. The simple solution
is to grab:
{'repository_path': 'perforce.oberonmedia.local:1666', 'changenum': '73292'}
and add perforce.oberonmedia.local:1666 as one of the servers in
administration.
-Tom
On Tue, May 5, 2009 at 3:09 PM, Christian Hammond chip
Is this a fresh install?
IIRC, I ran into this issue because I didn't have MinGW (sp?) tools
installed. ReviewBoard has a dependency on the GNU utils patch and diff.
-Tom
On Tue, May 5, 2009 at 9:39 PM, Noam Bunder gen...@gmail.com wrote:
Install it on Ubuntu - you will be up and running
apologies if this has been fixed post 1.0-alpha4 which I'm using, or
has been logged as a bug to fix already, but I get this when I attempt
to view changes between two posted revisions of a changeset when there
are no changes at all between them:
first_file = page.object_list[0]
IndexError: list
I get this when I attempt easy_install P4PythonInstaller
ftplib.error_perm: 550 /perforce/r08.2/tools/p4python.tgz
I think that's because the perforce ftp path has changed to
/perforce/r08.2/bin.tools/p4python.tgz
--~--~-~--~~~---~--~~
You received this
more error info.
Christian
--
Christian Hammond - [EMAIL PROTECTED]
VMware, Inc.
On Tue, Oct 28, 2008 at 5:00 AM, tom [EMAIL PROTECTED] wrote:
Hi,
Has this been resolved?
If not, this is to do with the fact that the newline character(s) are
in the name of the local file extracted
37 matches
Mail list logo
