Your message dated Tue, 15 Apr 2014 15:27:22 +0900
with message-id
<caciquq8zeux7kt+bt9kv091fpcbx5-pzvvcaw2xx+cdyubw...@mail.gmail.com>
and subject line Re: Bug#735833: Bug#739598: pystache not migrating to testing
due to FTBFS
has caused the Debian Bug report #735833,
regarding pystache: FTBFS: Tests failed
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 ow...@bugs.debian.org
immediately.)
--
735833: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pystache
Version: 0.5.3-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140114 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[1]: Entering directory `/«PKGBUILDDIR»'
> nosetests -d build2 && \
> nosetests3 -d build3
>
> ----------------------------------------------------------------------
> Ran 0 tests in 0.000s
>
> OK
> ......................................................................................................................................................................................................F......................................................
> ======================================================================
> FAIL: Test that the decode_errors attribute is respected.
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "/«PKGBUILDDIR»/build3/lib/pystache/tests/test_renderer.py", line 222,
> in test_unicode__decode_errors
> self.assertEqual(renderer.str(b), 'd\\ufffd\\ufffdf')
> nose.proxy.AssertionError: 'd\ufffd\ufffdf' != 'd\\ufffd\\ufffdf'
> - d\ufffd\ufffdf
> + d\ufffd\ufffdf
>
> """Fail immediately, with the given message."""
> >> raise self.failureException("'d\ufffd\ufffdf' !=
> >> 'd\\\\ufffd\\\\ufffdf'\n- d\ufffd\ufffdf\n+ d\\ufffd\\ufffdf\n")
>
>
> ----------------------------------------------------------------------
> Ran 253 tests in 0.398s
>
> FAILED (failures=1)
> make[1]: *** [override_dh_auto_test] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/01/14/pystache_0.5.3-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Package: pystache
Version: 0.5.3-3
pystache (0.5.3-3) unstable; urgency=medium
* Fixed FTBFS Tests failed (#735833, #739598)
- Thanks to David Suárez <david.sephi...@gmail.com> for reporting,
Thomas Goirand <z...@debian.org> for advising,
Matthias Klose <d...@ubuntu.com> for reporting and providing patch.
- debian/rules:
* Removed calling 2to3.
* Removed "&& \" on each lines.
- debian/control:
* X-Python-Version: Removed ">= 3.3"
* Build-Depends: Removed python-nose and python3-nose and append quilt.
* Starndards-Version: Bump version.
--
Kouhei Maeda <mkouhei at {palmtb.net,debian.or.jp}>
KeyID 4096R/7E37CE41
2014-04-11 0:18 GMT+09:00 Thomas Goirand <z...@debian.org>:
> On 04/10/2014 05:18 AM, Kouhei Maeda wrote:
>> Hi, Thomas.
>>
>> Thanks for your advice.
>> I fixed and uploaded to mentors.d.n.
>>
>> Would you upload this package?
>> http://mentors.debian.net/debian/pool/main/p/pystache/pystache_0.5.3-3.dsc
>>
>> Best regards,
>> --
>> Kouhei Maeda <mkouhei at {palmtb.net,debian.or.jp}>
>> KeyID 4096R/7E37CE41
>
> Hi,
>
> Since your new package version fixes the FTBFS, and it's important to
> quickly fix that, I have uploaded it. However, in your debian/rules,
> there's still something to fix. You should use set -e on each of your
> for statements. For example:
>
> set -e && for py in $(shell py3versions -vr); do \
> [ ... content of your loop ... ]
>
> Note that this is a *must* imposed by the Debian policy. Please fix
> this, and reupload to mentors, then I'll sponsor your package once more.
>
> Cheers,
>
> Thomas Goirand (zigo)
--- End Message ---
