On 16 December 2015 at 20:02, Christian Hammond
wrote:
> That certainly shouldn't be necessary. Sounds like maybe there was a bad
> package?
>
> If it ever happens again, please let me know. I want to be sure we figure
> out what's causing that.
>
> Christian
>
> --
>
That certainly shouldn't be necessary. Sounds like maybe there was a bad
package?
If it ever happens again, please let me know. I want to be sure we figure
out what's causing that.
Christian
--
Christian Hammond - christ...@beanbaginc.com
Review Board - https://www.reviewboard.org
Beanbag,
On 15 December 2015 at 19:15, Christian Hammond wrote:
> Hi,
>
> collectstatic isn't meant to be run by end users. It's intended only for
> the packaging steps, and running it manually can cause problems. I want to
> better understand the need to run this command, though.
On Tue, Dec 15, 2015 at 10:18 AM Ken Erickson wrote:
> Done
>
> On Tuesday, December 15, 2015 at 4:19:50 AM UTC-7, Stephen Gallagher wrote:
>>
>> Ken, Cian and Sean: since you have had positive experiences, would you
>> mind signing into Bodhi (instructions in the original
Hi,
collectstatic isn't meant to be run by end users. It's intended only for
the packaging steps, and running it manually can cause problems. I want to
better understand the need to run this command, though. Can you go into
this a bit more?
Christian
--
Christian Hammond - chip...@chipx86.com
Ken, Cian and Sean: since you have had positive experiences, would you mind
signing into Bodhi (instructions in the original message for this thread)
and providing positive karma? If all three of you did so, this can go to
the stable repo immediately. Otherwise, I have to wait until Friday to push
Done
On Tuesday, December 15, 2015 at 4:19:50 AM UTC-7, Stephen Gallagher wrote:
>
> Ken, Cian and Sean: since you have had positive experiences, would you
> mind signing into Bodhi (instructions in the original message for this
> thread) and providing positive karma? If all three of you did
I just found it already posted under another
thread https://groups.google.com/forum/#!topic/reviewboard/uXxkNePzSTs
On Thursday, December 10, 2015 at 3:00:57 PM UTC-7, Stephen Gallagher wrote:
>
>
>
> On Thu, Dec 10, 2015 at 4:22 PM Ken Erickson > wrote:
>
>> I just
On Thu, Dec 10, 2015 at 4:22 PM Ken Erickson wrote:
> I just installed 2.5.2 on CentOS 7 for testing, other than comments below
> I haven't found anything.
> I do have a question, I installed the Comment Categorization extension and
> added 4 types to it but when I try to
I just installed 2.5.2 on CentOS 7 for testing, other than comments below I
haven't found anything.
I do have a question, I installed the Comment Categorization extension and
added 4 types to it but when I try to use it the list is empty on review
comments? It acted the same under 2.0 as
As it turns out the webpage reporting an older version was a non restarted
fastcgi instance and unrelated to the webapi evolution.
On Monday, December 7, 2015 at 5:17:51 PM UTC+1, se...@m2mobi.com wrote:
>
> Hello Stephen,
>
> I've been patiently waiting for this for weeks now. Glad to see it's
(Didn't have coffee yet.) It resolves the dependency issue but not the
rb-site upgrade issue.
The log was done after installing django evolution from epel-testing
(otherwise it broke on version dependency before ever attempting to run the
upgrade)
On Tuesday, December 8, 2015 at 10:00:18 AM
Should've mentioned running exactly that got me past this error already.
On Monday, December 7, 2015 at 5:21:16 PM UTC+1, Stephen Gallagher wrote:
>
> Hmm, I thought I fixed that version. I'll push an update immediately. If
> you manually run `yum update python-django-evolution
>
On Mon, Dec 7, 2015 at 11:21 AM Stephen Gallagher
wrote:
> Hmm, I thought I fixed that version. I'll push an update immediately. If
> you manually run `yum update python-django-evolution
> --enablerepo=epel-testing` and then attempt the upgrade, does that resolve
>
On Sat, Dec 5, 2015 at 10:29 AM Paul Fee wrote:
> Hi Stephen,
>
> That's great news, I had been wondering if Fedora/RHEL users would be
> seeing RB2.5 soon.
>
> On Fedora, it looks like the Django packages have moved ahead to 1.8, but
> RB still needs 1.6. Hence
Hmm, I thought I fixed that version. I'll push an update immediately. If
you manually run `yum update python-django-evolution
--enablerepo=epel-testing` and then attempt the upgrade, does that resolve
your upgrade issue? What version of django-evolution do you have right now?
0.7.5?
On Mon, Dec
Hello Stephen,
I've been patiently waiting for this for weeks now. Glad to see it's
getting close.
Some issues I found upgrading from EPEL 2.0.18:
The RPM requires: python-django-evolution >= 0.7.1
ReviewBoard requires: django-evolution>=0.7.6,<=0.7.999
*and during the rb-site upgrade I get
Hi Stephen,
That's great news, I had been wondering if Fedora/RHEL users would be
seeing RB2.5 soon.
On Fedora, it looks like the Django packages have moved ahead to 1.8, but
RB still needs 1.6. Hence ReviewBoard has disappeared from Fedora from F22
onwards :(
Nice to see that the situation
Hello, folks! It's time for a big update. As many of you are probably
aware, I maintain the RPMs of Review Board that live in Fedora's EPEL
project[1] (Extra Packages for Enterprise Linux).
For some time now, EPEL 7 (which provides community-supported add-on
software for RHEL 7 and CentOS 7) has
19 matches
Mail list logo