Your message dated Sat, 11 Mar 2017 08:12:00 +0000
with message-id <[email protected]>
and subject line Re: Bug#857429: unblock: django-pipeline/1.6.8-3
has caused the Debian Bug report #857429,
regarding unblock: django-pipeline/1.6.8-3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
857429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857429
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: unblock

Please unblock package django-pipeline

This fixes bug #851722 which causes random build failures. I am not sure
how serious you consider this type of bug, however the workaround is
simple.

I believe the randomness is caused by the order the tests are run, which
depends on the order the files are listed from the directory.


diff -Nru django-pipeline-1.6.8/debian/changelog 
django-pipeline-1.6.8/debian/changelog
--- django-pipeline-1.6.8/debian/changelog      2016-08-05 21:32:23.000000000 
+1000
+++ django-pipeline-1.6.8/debian/changelog      2017-03-10 18:54:37.000000000 
+1100
@@ -1,3 +1,9 @@
+django-pipeline (1.6.8-3) unstable; urgency=medium
+
+  * Work around for random build failures. Closes: #851722.
+
+ -- Brian May <[email protected]>  Fri, 10 Mar 2017 18:54:37 +1100
+
 django-pipeline (1.6.8-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru django-pipeline-1.6.8/debian/rules django-pipeline-1.6.8/debian/rules
--- django-pipeline-1.6.8/debian/rules  2016-08-05 21:32:23.000000000 +1000
+++ django-pipeline-1.6.8/debian/rules  2017-03-10 18:54:37.000000000 +1100
@@ -21,4 +21,5 @@
        dh_installchangelogs -- HISTORY.rst
 
 override_dh_auto_test:
+       PYTHONPATH=. /usr/bin/django-admin collectstatic 
--settings=tests.settings --noinput
        PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="PYTHONPATH=. python{version} 
/usr/bin/django-admin test --settings=tests.settings" dh_auto_test

unblock django-pipeline/1.6.8-3

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (100, 
'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message ---
Brian May:
> Package: release.debian.org
> Severity: normal
> User: [email protected]
> Usertags: unblock
> 
> Please unblock package django-pipeline
> 
> This fixes bug #851722 which causes random build failures. I am not sure
> how serious you consider this type of bug, however the workaround is
> simple.
> 
> I believe the randomness is caused by the order the tests are run, which
> depends on the order the files are listed from the directory.
> 
> 
> [...]
> 
> unblock django-pipeline/1.6.8-3
> 
> [...]

Unblocked, thanks.

~Niels

--- End Message ---

Reply via email to