From owner-freebsd-ports@FreeBSD.ORG Fri Feb 25 12:22:11 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7340106564A for ; Fri, 25 Feb 2011 12:22:11 +0000 (UTC) (envelope-from Johan@double-l.nl) Received: from smtp-vbr11.xs4all.nl (smtp-vbr11.xs4all.nl [194.109.24.31]) by mx1.freebsd.org (Postfix) with ESMTP id 6284F8FC16 for ; Fri, 25 Feb 2011 12:22:10 +0000 (UTC) Received: from w2003s01.double-l.local (double-l.xs4all.nl [80.126.205.144]) by smtp-vbr11.xs4all.nl (8.13.8/8.13.8) with ESMTP id p1PC9fiJ040190; Fri, 25 Feb 2011 13:09:41 +0100 (CET) (envelope-from Johan@double-l.nl) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 25 Feb 2011 13:09:37 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Message-ID: <57200BF94E69E54880C9BB1AF714BBCBDD318A@w2003s01.double-l.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: py-django from 1.2.4 to 1.2.5 breaks Baruwa. Thread-Index: AcvPx2jg8TYDfLK8RP+6r7gWbfj8zgFHTDpg References: <57200BF94E69E54880C9BB1AF714BBCBDD314B@w2003s01.double-l.local> <87lj1csxtf.fsf@gmail.com> From: "Johan Hendriks" To: "Raphael Kubo da Costa" X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-ports@freebsd.org Subject: RE: py-django from 1.2.4 to 1.2.5 breaks Baruwa. X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Feb 2011 12:22:11 -0000 >"Johan Hendriks" writes: >> Downgrading py-django to 1.2.4 makes things happy again. >> >> So i wonder could it be something with the latest py-django port. >A few backwards incompatible changes were made indeed [1], but, >according to the team, they had to be made for the sake of security. >Maybe the application you're talking about was (ab)using some of these >features which have changed? >[1] http://docs.djangoproject.com/en/1.2/releases/1.2.5/ Thanks for your answer. Indeed it was baruwa who was at fault here. The maintainer fixed the issue with django. Thank you for your work. Regards, Johan