Control: tags -1 -moreinfo
Ok, it has now been accepted.
--
Brian May b...@debian.org
On 8 December 2014 at 08:33, Ivo De Decker iv...@debian.org wrote:
Please upload this to unstable. Once the upload is accepted, please remove
the
moreinfo tag.
Version 0.2 was uploaded to unstable. Not yet accepted.
This is identical to version 0.1, with the exception that I fixed the
Control: tags -1 confirmed moreinfo
Hi,
On Mon, Dec 01, 2014 at 09:10:56AM +1100, Brian May wrote:
On 27 November 2014 at 11:33, Brian May b...@debian.org wrote:
I uploaded a fix for #763222 to experimental, in version
1.2.4+git20141127-0.1.
The diff is rather large, but it looks more or
On 27 November 2014 at 11:33, Brian May b...@debian.org wrote:
I uploaded a fix for #763222 to experimental, in
version 1.2.4+git20141127-0.1.
The changelog refers to the wrong bug number; #763222 is the bug fixed
directly by this change.
#769216 is a result of #763222 causing
I uploaded a fix for #763222 to experimental, in
version 1.2.4+git20141127-0.1.
It is almost exactly the same as the patch I previously gave,
except python32.patch and add_migration.patch have been incorporated
upstream and are no longer required.
diff -u
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
python-django-guardian was RC bug #763222. I believe this is a just a
technical bug in the tests, the actual package should work fine.
However, it means the package won't build.
This in
Or put another, the question is do we continue with the Debian fork, with
extensive changes that have no testing outside Debian, or do we switch to
the upstream git version where changes receive much better testing.
I have prepared (but not uploaded) the package using the git version, and
7 matches
Mail list logo
