Go ahead and update django_evolution:
$ sudo easy_install -U django_evolution
The 0.7.2 release should hopefully fix these issues.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On Mon, Jun 2, 2014
Looks like there was a similar bug in the Postgres backend. I'm working on
a fix now, and will reply when there's a new Django Evolution version for
you to try.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.co
I'm attempting a Reviewboard 1.6.9->2.0 migration. This is on Ubuntu 12.04
and I'm using postgresql as the database.
I've updated review-board with this command:
> sudo easy_install -U ReviewBoard
Based on the release notes, I went ahead and removed PIL and installed
pillow, but then rb-site
On 06/02/2014 11:58 AM, Stephen Gallagher wrote:
> On 06/02/2014 11:46 AM, Paul Fee wrote:
>> Hi Stephen,
>>
>> Comparing the HTML using Firefox/Firebug, I see both good and bad pages
>> have the correct HTML to display the "Edit columns" heading. However
>> the bad page has missing CSS styling.
>
publishing actually works fine, so not related as you said.
These are actual warnings not errors anyway
On Mon, Jun 2, 2014 at 3:31 PM, Christian Hammond
wrote:
> Nothing in those logs are related, so I don't actually have anything to go
> on. Those are just harmless warnings that everybody wil
Can you tell us what's in the "Encoding" field (under "Advanced Settings")
in the repository admin?
-David
On Mon, Jun 2, 2014 at 7:53 AM, Roudaille77 wrote:
> Hello,
>
> I have just updated my ReviewBoard site but I can't visualize the
> Subversion diff anymore...
> I can see :
>
> There was
Nothing in those logs are related, so I don't actually have anything to go
on. Those are just harmless warnings that everybody will see.
While TortoiseSVN should be compatible, it's not actively tested. Still, it
should *never* cause an issue with publishing.
Adrien, are you also unable to publis
getting the same logs using tortoisesvn as well
On Tuesday, May 27, 2014 11:10:31 PM UTC-4, MoonWalker wrote:
>
> No, we are using tortoisesvn to generate an unified diffs. We are using
> SVN only
>
> On Wednesday, May 28, 2014 12:21:18 PM UTC+10, Christian Hammond wrote:
>>
>> Hi,
>>
>> Those ar
We made a number of improvements to the Mercurial support in RBTools 0.6. I
don't have personal experience with hg subversion myself, so I don't know
whether it's still at all necessary for any workflows. Certainly, we'd
rather time be spent updating RBTools for any missing functionality.
Christia
Hi Bruce,
Most of the developers at my company are still using postreview with RB
2.0. We've always seen the error you reported in the bug, both with and
without postreview. It seems to be a reviewboard issue. As a workaround,
you might be able to make your parent diff include more changesets.
I'm investigating upgrading our installation to Review Board 2.x and one
issue I've come across is that with the existing code, "hg postreview"
doesn't work correctly. I've submitted a ticket to
https://bitbucket.org/ccaughie/hgreviewboard, but I was wondering - are
people still planning to use the
Hello,
I have just updated my ReviewBoard site but I can't visualize the
Subversion diff anymore...
I can see :
There was an error displaying this diff.
Traceback (most recent call last):
File
"/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.1-py2.7.egg/reviewboard/diffviewer/views.py
On 06/02/2014 11:46 AM, Paul Fee wrote:
> Hi Stephen,
>
> Comparing the HTML using Firefox/Firebug, I see both good and bad pages
> have the correct HTML to display the "Edit columns" heading. However
> the bad page has missing CSS styling.
>
> On Fedora rawhide, with an up to date "locate" data
Hi Stephen,
Comparing the HTML using Firefox/Firebug, I see both good and bad pages
have the correct HTML to display the "Edit columns" heading. However the
bad page has missing CSS styling.
On Fedora rawhide, with an up to date "locate" database, I can see an empty
CSS file that looks suspiciou
I indeed have a couple long html strings in that file, I will wrap and see
if it happens again (long being a couple 300ish lines and one 500ish line)
I'll update you if it happens on files with shorter lines, in the mean time
I will assume that this is the source of the problem (and should be fi
15 matches
Mail list logo
