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 #739598,
regarding pystache tests fail with python3.4
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.)


-- 
739598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739598
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pystache
Version: 0.5.3-2
Severity: important
Tags: sid jessie
User: [email protected]
Usertags: python3.4

python3.4 as the default python3 can be found in experimental.

   debian/rules override_dh_auto_test
make[1]: Entering directory `/build/buildd/pystache-0.5.3'
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
"/build/buildd/pystache-0.5.3/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.336s

FAILED (failures=1)

--- 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 <[email protected]> for reporting,
      Thomas Goirand <[email protected]> for advising,
      Matthias Klose <[email protected]> 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 <[email protected]>:
> 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 ---

Reply via email to