Another lazr package (delegates), another ITP (#758828), another chance to
play with a git package regime. This time I chose git-buildpackage.
I must admit I cheated a bit at first. I started with the 2.0 tarball from
PyPI so I could test upstream updating (I released 2.0.1 earlier in the day).
I think the following bug I just noticed is significant. Unless fixed, it
means that after Django 1.7 is released Debian won't have a Mysql library
for it that works with Python3.
https://bugs.debian.org/758844
http://bugs.mysql.com/bug.php?id=72542
--
Brian May
Hello everybody,
to enable dynamic linking to a C library in a python module (instead of static
linking), an upstream author proposes me to either implement an option in
setup.py or to make it query an environment variable.
With the goal of using the most standard packaging tools, can you recomme
On Aug 20, 2014, at 03:28 PM, Barry Warsaw wrote:
>One last thing: I'm not sure I recommend going with the package name as the
>branch name. I'm tired of typing `upstream-lazr.smtptest`. The default
>git-dpm branch names are starting to make more sense. :)
I just renamed the branches both local
On 19 August 2014 18:37, Brian May wrote:
> At which point I ran out of time :-)
>
Ok, did all that. guardian does some "creative" things, am surprised it
works under any version of Django. e.g. defining conflicting DB models, and
only use one of them.
Next error:
Traceback (most recent call l
5 matches
Mail list logo
