Your message dated Wed, 5 Sep 2018 21:29:04 +0100
with message-id <20180905202904.GA25633@blodeuwedd>
and subject line Digraph removed
has caused the Debian Bug report #902155,
regarding dulwich FTBFS: nicodeDecodeError: 'ascii' codec can't decode byte
0xc4 in position 48: ordinal not in range(128)
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.)
--
902155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dulwich
Version: 0.19.3-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=dulwich&suite=sid
...
/usr/bin/make check PYTHON=python3
make[2]: Entering directory '/<<PKGBUILDDIR>>'
python3 setup.py build
Traceback (most recent call last):
File "setup.py", line 96, in <module>
**setup_kwargs
File "/usr/lib/python3.6/distutils/core.py", line 121, in setup
dist.parse_config_files()
File "/usr/lib/python3.6/distutils/dist.py", line 395, in parse_config_files
parser.read(filename)
File "/usr/lib/python3.6/configparser.py", line 697, in read
self._read(fp, filename)
File "/usr/lib/python3.6/configparser.py", line 1015, in _read
for lineno, line in enumerate(fp, start=1):
File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 48:
ordinal not in range(128)
make[2]: *** [Makefile:25: build] Error 1
This can be reproduced with
LANG=C dpkg-buildpackage -B
--- End Message ---
--- Begin Message ---
Version: 0.19.4-1
There was a non-ascii character in setup.cfg, which causes disutils to
fall over because it relies on the encoding set in the users'
environment. See https://bugs.python.org/issue9561
The non-ascii character was removed in 0.19.4-1 to work around this
issue.
--
Jelmer Vernooij <jel...@jelmer.uk>
PGP Key: https://www.jelmer.uk/D729A457.asc
signature.asc
Description: PGP signature
--- End Message ---
