Debian Bug report logs - #828776
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe3 in position 349: invalid continuation byte
Reported by: Rob Stone <floriparob@gmail.com>
Date: Mon, 27 Jun 2016 18:45:05 UTC
Severity: serious
Tags: d-i
Found in version debtags/2.1
Fixed in version debtags/2.1.1
Done: Enrico Rossi <e.rossi@tecnobrain.com>
Bug is archived. No further changes may be made.
Full log
🔗 View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Tue, 05 Jul 2016 16:39:43 +0000 with message-id <E1bKTNv-0006JD-KO@franck.debian.org> and subject line Bug#828776: fixed in debtags 2.1.1 has caused the Debian Bug report #828776, regarding UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe3 in position 349: invalid continuation byte 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 owner@bugs.debian.org immediately.) -- 828776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828776 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[Message part 2 (message/rfc822, inline)]
[Message part 3 (text/plain, inline)]
Package: debtags Version: 2.1 Severity: serious Tags: d-i Justification: fails to build from source (but built successfully in the past) Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? It occurs each time I do any sort of upgrade. * What exactly did you do (or not do) that was effective (or ineffective)? I ran dpkg --verify debtags. * What was the outcome of this action? It passed. * What outcome did you expect instead? I was hoping it would give me more information about the error. Note that there is no "position 349" on line number 592 in the file "/usr/lib/python3/dist-packages/apt/package.py" unless position 349 is the 349th. bit? I opened the file using ghex and line 592 appears to be "normal" IMHO. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/2 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) Versions of packages debtags depends on: ii python3-apt 1.1.0~beta2 ii python3-debian 0.1.27 pn python3:any <none> debtags recommends no packages. Versions of packages debtags suggests: pn tagcoll <none> -- no debconf information
[debtags_output.txt (text/x-c, attachment)]
[Message part 5 (message/rfc822, inline)]
Source: debtags Source-Version: 2.1.1 We believe that the bug you reported is fixed in the latest version of debtags, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 828776@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Enrico Rossi <e.rossi@tecnobrain.com> (supplier of updated debtags package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Tue, 05 Jul 2016 15:33:30 +0200 Source: debtags Binary: debtags Architecture: source Version: 2.1.1 Distribution: unstable Urgency: low Maintainer: Enrico Rossi <e.rossi@tecnobrain.com> Changed-By: Enrico Rossi <e.rossi@tecnobrain.com> Description: debtags - Debian Package Tags support tools Closes: 799584 813204 828776 Changes: debtags (2.1.1) unstable; urgency=low . * New maintainer. (Closes: #813204) * Set standards-version to 3.9.8 no changes required. * Fix UnicodeDecodeError on non-utf8 data from apt cache. (Closes: #828776, #799584) Checksums-Sha1: 811255c0a10641e7499488a38456d29be153bd5b 1716 debtags_2.1.1.dsc dbafd9dbbe3aaed6666ca2ac3ba4c9d09e946f3f 556472 debtags_2.1.1.tar.xz Checksums-Sha256: 9b6bd291b203b7b1a9bfe7ece700a93f036e25bd5a58e9d0a9bb6f0e5bd956c4 1716 debtags_2.1.1.dsc 11718669d0fa4ce4b25ad95ae6f2691c31bb6bb04c5d5e5c94f44285f11cf659 556472 debtags_2.1.1.tar.xz Files: 3fa526c5dbd5fb9b6a0c75be21f658f6 1716 admin optional debtags_2.1.1.dsc a4fd8fbc8c6e50edff573a9562b213ef 556472 admin optional debtags_2.1.1.tar.xz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJXe7rXAAoJEF4BlfryEzF2SQsQALF1v2w4YF9E2Axljh2RhyKu hajHyYq9cWra0rajICHD+fte4Y8YxYA2gn7HWSzIkBJJ2VYR/eH8JnMSu76plJ1r 82ZA0aMUmsif8PdMYgAxaFDKA1div7of43tv4p36Cur1oSt7jB+E+Fae2ws3kXBc uuBEI7pdVhx7i8Aq+B0ki5dnHgyIABLhxZ7xY52ixzjGuttkoDeaX8c2G+ZO+Owe RViXc9IPIwJvOAAWnCgGY6v+5wZUNdeELvR8JjloD2w3e/B7atqq0xoLWsl9OzPH /sU6K6pvvAE+gv7C/K64+Dska1gQzpPjRPZBc+lBOMBfdwIG8KmCO+lTTqKLMmHW DEttC4oPpBFcSHu/roUkGGaE/6QVcVaCnSkWhC7qt0zbUHBufJ0bvkSMvSil5TWe eOQap0YzMiWLx0fFS4MuBLp/vOGDKU5b7bl366P2kHFJoTcKIiMhGkoFPeGfvOOe jwJL4jJjnmQSXr87vmRrNsz8W2NB+zMw4X+SC5bUOpumhZxWr+9DQ1gDqAM5y6uB ecHZoASrxOa1hRNZ/aeAeCc9WDoNdXuQ+SSMD56ozeppbsGhm+zFeqU0bqiXh3TY VW48aTwWvl8bRKYt303vIhoOFMiX8+FT8kAQAAUB90yWwQwLixgfkKUOUdxJ65Uu wOrx5ptoqCTMMwfgfRv4 =SuUV -----END PGP SIGNATURE-----
Send a report that this bug log contains spam.
Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Thu Oct 20 11:49:53 2022 ; Machine Name: buxtehude Debian Bug tracking system
Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.
0 Response to "Utf 8 Codec Can t Decode Byte 0xe3 in Position 4 Invalid Continuation Byte"
Post a Comment