GNU bug report logs - #28726
[PATCH] Update python-sqlparse and fix some dependent packages

Previous Next

Full log

Message #44 received at 28726 <at> debbugs.gnu.org (full text, mbox):

From: Christopher Baines <mail <at> cbaines.net>
To: Cyril Roelandt <tipecaml <at> gmail.com>
Cc: 28726 <at> debbugs.gnu.org
Subject: Re: [bug#28726] [PATCH 1/5] gnu: django: Fix the build for
 python-django-gravatar2.
Date: Sun, 8 Oct 2017 17:02:20 +0100

[Message part 1 (text/plain, inline)]

On Sun, 8 Oct 2017 15:52:45 +0100
Christopher Baines <mail <at> cbaines.net> wrote:

> On Sun, 8 Oct 2017 05:30:56 +0200
> Cyril Roelandt <tipecaml <at> gmail.com> wrote:
> 
> > On 10/06/2017 10:26 PM, Christopher Baines wrote:  
> > > The build was failing as the Django settings were not configured
> > > for the tests. The relevant files are missing from the release on
> > > PyPI, so switch to using a more complete source release. Also
> > > update the package at the same time.    
> > What are these missing files? Couldn't we add them using a patch? Is
> > there a reason why they were not included in PyPI, or is this a
> > bug?  
> 
> It's the example_project/settings.py file that is key. I guess this
> could be added as a patch, it's a little long at 168 lines though.

On a more practical note, I don't know of an proper way of generating
such a patch. The only approaches that come to mind are going through
Git, or writing it manually in Emacs, both of which seem bad. Any
advice on generating patches?

[Message part 2 (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.