Bug#714142: qdjango: New upstream release (0.3.0)

2013-06-26 Thread Pete Woods
Package: qdjango Severity: wishlist Tags: patch Dear Maintainer, I have packaged the new release of QDjango with the following bugfixes: * Fix and test unique field option. * Add a unique_together model option. * Don't crash if QDjango::database() is called before QDjango::setDatabase(). *

Bug#714142: qdjango: New upstream release (0.3.0)

2013-06-26 Thread Pete Woods
That macro is confusing, I admit. It actually enables the deprecated functions! On Wed, Jun 26, 2013 at 9:54 AM, Jeremy Lainé jeremy.la...@m4x.org wrote: Hi Pete, I'll upload the new version, but I'm not sure I understand why the Qt5-specific patch is required. How does disabling

Bug#714142: qdjango: New upstream release (0.3.0)

2013-06-26 Thread Jeremy Lainé
Hi Pete, I'll upload the new version, but I'm not sure I understand why the Qt5-specific patch is required. How does disabling deprecated functions help the build? Jeremy Le Jun 26, 2013 à 10:39 AM, Pete Woods a écrit : Package: qdjango Severity: wishlist Tags: patch Dear Maintainer,

Bug#714142: qdjango: New upstream release (0.3.0)

2013-06-26 Thread Jeremy Lainé
Pete, Le Jun 26, 2013 à 10:55 AM, Pete Woods a écrit : That macro is confusing, I admit. It actually enables the deprecated functions! As Qt5 has not landed yet in Debian/unstable, I will be uploading QDjango 0.3.0 without the Qt5 patch. As I'm also the upstream author, I will address

Bug#714142: qdjango: New upstream release (0.3.0)

2013-06-26 Thread Pete Woods
Hi Jeremy, I think that is reasonable. Is there any point patching it for qt5 support if there's no qt5 in debian? It sounds like the Ubuntu package will have to diverge here, for the moment. -Pete On Wed, Jun 26, 2013 at 9:59 AM, Jeremy Lainé jeremy.la...@m4x.org wrote: Pete, Le Jun 26,