Pushed to my github:
commit 257ef06364e224bc2af9edafb28449b0d2784521
Author: James Cammarata
Date: Thu Jun 30 17:19:47 2011 -0500
Setting TIME_ZONE to None in web/settings.py causes a 500 error on a
RHEL5 system with python 2.4 and django 1.1. Commenting out the config
line has the
On Thu, 30 Jun 2011 17:23:58 -0500, James Cammarata wrote:
> Pushed to my github:
Merged. I also picked up your mongodb serializer. Thanks.
--
Scott Henson
Red Hat SOC Operator
WVU Alum BSAE/BSME
pgpUv69WydNPF.pgp
Description: PGP signature
___
cobb
On Tue, Jul 5, 2011 at 2:01 PM, Scott Henson wrote:
> On Thu, 30 Jun 2011 17:23:58 -0500, James Cammarata wrote:
>> Pushed to my github:
>
> Merged. I also picked up your mongodb serializer. Thanks.
>
Ok, I didn't think I had committed that, but oh well :)
___
On Wed, Jul 6, 2011 at 2:34 AM, James Cammarata wrote:
> On Tue, Jul 5, 2011 at 2:01 PM, Scott Henson wrote:
>> On Thu, 30 Jun 2011 17:23:58 -0500, James Cammarata wrote:
>>> Pushed to my github:
>>
>> Merged. I also picked up your mongodb serializer. Thanks.
>>
>
> Ok, I didn't think I had comm
No I did not. I sent in a patch but it was only in email and not in my
repo.
As for the pymongo, that should be wrapped in a try block and disabled if
not available. I can fix that.
On Jul 28, 2011 1:30 PM, "Jonathan Sabo" wrote:
> On Wed, Jul 6, 2011 at 2:34 AM, James Cammarata wrote:
>> On Tu
It would be nice if the fix for the /etc/cobbler/settings.json stuff
could me applied asap.
The tree is broken and it frustrates my testing efforts ;-)
Thanks!
Regard,
Jorgen Maas
On Thu, Jul 28, 2011 at 8:45 PM, James Cammarata wrote:
> No I did not. I sent in a patch but it was only in email
>
> commit 257ef06364e224bc2af9edafb28449b0d2784521
> Author: James Cammarata
> Date: Thu Jun 30 17:19:47 2011 -0500
>
> Setting TIME_ZONE to None in web/settings.py causes a 500 error on a
> RHEL5 system with python 2.4 and django 1.1. Commenting out the config
> line has the same eff
Perhaps they fixed this in 1.1.4? I can't reproduce it now on my home
system. I'll check on my work system today, but that was definitely
the issue at the time.
On Tue, Aug 2, 2011 at 1:54 AM, Jörgen Maas wrote:
>
>>
>> commit 257ef06364e224bc2af9edafb28449b0d2784521
>> Author: James Cammarata
I finally found it:
Changed in Django 1.1.2: None was added as an allowed value
Grtz,
Jorgen Maas
On Tue, Aug 2, 2011 at 1:58 PM, James Cammarata wrote:
> Perhaps they fixed this in 1.1.4? I can't reproduce it now on my home
> system. I'll check on my work system today, but that was definitely
Btw, Django 1.1.4 is in EPEL4.
On Tue, Aug 2, 2011 at 2:21 PM, Jörgen Maas wrote:
> I finally found it:
>
> Changed in Django 1.1.2: None was added as an allowed value
>
> Grtz,
> Jorgen Maas
>
> On Tue, Aug 2, 2011 at 1:58 PM, James Cammarata wrote:
>> Perhaps they fixed this in 1.1.4? I can't
10 matches
Mail list logo