Your message dated Fri, 29 Dec 2017 04:50:25 +0000
with message-id <e1eumcj-0003ta...@fasolo.debian.org>
and subject line Bug#883577: fixed in reportbug 7.1.8
has caused the Debian Bug report #883577,
regarding reportbug 7.1.7 - severe / Debian 9.1
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.)
--
883577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 7.1.7
Severity: important
Debian version: 9.1
Kernel: Linux cmx212 2.6.32-042stab125.5 #1 SMP Tue Oct 17 12:48:22 MSK 2017
x86_64 GNU/Linux
Submitting a bug report via reportbug 7.1.7 programme produced an error:
Traceback (most recent call last):
File "/usr/bin/reportbug", line 2234, in <module>
main()
File "/usr/bin/reportbug", line 1107, in main
return iface.user_interface()
File "/usr/bin/reportbug", line 1225, in user_interface
main()
File "/usr/bin/reportbug", line 1107, in main
return iface.user_interface()
File "/usr/bin/reportbug", line 2150, in user_interface
package, severity, mode, charset=charset, tags=tags)
File "/usr/bin/reportbug", line 182, in handle_editing
editor, charset)
File "/usr/lib/python3/dist-packages/reportbug/ui/text_ui.py", line 1064, in
spawn_editor
newmessage = open(filename).read()
File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 1780:
ordinal not in range(128)
# cat .reportbugrc
# reportbug preferences file
# character encoding: us-ascii
# Version of reportbug this preferences file was written by
reportbug_version "7.1.7"
# default operating mode: one of: novice, standard, advanced, expert
mode standard
# default user interface
ui text
# offline setting - comment out to be online
#offline
# name and email setting (if non-default)
realname "Sophie L"
email "withh...@klunky.co.uk <mailto:withh...@klunky.co.uk>"
# Suppress user ID check for this user
no-check-uid
# If nothing else works, remove the # at the beginning
# of the following three lines:
#no-cc
#header "X-Debbugs-CC: withh...@klunky.co.uk <mailto:withh...@klunky.co.uk>"
#smtphost reportbug.debian.org <http://reportbug.debian.org/>
# You can add other settings after this line. See
# /etc/reportbug.conf for a full listing of options.
Full copy and paste from session, but the vi entries are missed:
# reportbug
Welcome to reportbug! Since it looks like this is the first time you have used
reportbug, we are configuring its behavior. These
settings will be saved to the file "/root/.reportbugrc", which you will be free
to edit further.
Please choose the default operating mode for reportbug.
1 novice Offer simple prompts, bypassing technical questions.
2 standard Offer more extensive prompts, including asking about things that a
moderately sophisticated user would be expected to
know about Debian.
3 advanced Like standard, but assumes you know a bit more about Debian,
including "incoming".
4 expert Bypass most handholding measures and preliminary triage routines.
This mode should not be used by people unfamiliar with
Debian's policies and operating procedures.
Select mode: [novice] 2
Will reportbug often have direct Internet access? (You should answer yes to
this question unless you know what you are doing and plan
to check whether duplicate reports have been filed via some other channel.)
[Y|n|q|?]? y
What real name should be used for sending bug reports?
[root]> Sophie L
Which of your email addresses should be used when sending bug reports? (Note
that this address will be visible in the bug tracking
system, so you may want to use a webmail address or another address with good
spam filtering capabilities.)
[r...@cmx12.klunky.co.uk <mailto:r...@cmx12.klunky.co.uk>]>
withh...@klunky.co.uk <mailto:withh...@klunky.co.uk>
Do you have a "mail transport agent" (MTA) like Exim, Postfix or SSMTP
configured on this computer to send mail to the Internet?
[y|N|q|?]?
reportbug: exiting due to user interrupt.
root@cmx12:/etc# reportbug
Welcome to reportbug! Since it looks like this is the first time you have used
reportbug, we are configuring its behavior. These
settings will be saved to the file "/root/.reportbugrc", which you will be free
to edit further.
Please choose the default operating mode for reportbug.
1 novice Offer simple prompts, bypassing technical questions.
2 standard Offer more extensive prompts, including asking about things that a
moderately sophisticated user would be expected to
know about Debian.
3 advanced Like standard, but assumes you know a bit more about Debian,
including "incoming".
4 expert Bypass most handholding measures and preliminary triage routines.
This mode should not be used by people unfamiliar with
Debian's policies and operating procedures.
Select mode: [novice] 2
Will reportbug often have direct Internet access? (You should answer yes to
this question unless you know what you are doing and plan
to check whether duplicate reports have been filed via some other channel.)
[Y|n|q|?]? y
What real name should be used for sending bug reports?
[root]> Sophie L
Which of your email addresses should be used when sending bug reports? (Note
that this address will be visible in the bug tracking
system, so you may want to use a webmail address or another address with good
spam filtering capabilities.)
[r...@cmx12.klunky.co.uk <mailto:r...@cmx12.klunky.co.uk>]>
withh...@klunky.co.uk <mailto:withh...@klunky.co.uk>
Do you have a "mail transport agent" (MTA) like Exim, Postfix or SSMTP
configured on this computer to send mail to the Internet?
[y|N|q|?]? y
Please enter the name of your proxy server. It should only use this parameter
if you are behind a firewall. The PROXY argument should
be formatted as a valid HTTP URL, including (if necessary) a port number; for
example, http://192.168.1.1:3128/ <http://192.168.1.1:3128/>. Just press ENTER
if
you don't have one or don't know.
>
Default preferences file written. To reconfigure, re-run reportbug with the
"--configure" option.
Running 'reportbug' as root is probably insecure! Continue [y|N|q|?]? y
Please enter the name of the package in which you have found a problem, or type
'other' to report a more general problem. If you
don't know what package the bug is in, please contact
debian-u...@lists.debian.org <mailto:debian-u...@lists.debian.org> for
assistance.
> redis-server
*** Welcome to reportbug. Use ? for help at prompts. ***
Note: bug reports are publicly archived (including the email address of the
submitter).
Detected character set: us-ascii
Please change your locale if this is incorrect.
Using 'Sophie <withh...@klunky.co.uk <mailto:withh...@klunky.co.uk>>' as your
from address.
Getting status for redis-server...
Will send report to Debian (per lsb_release).
Querying Debian BTS for reports on redis (source)...
6 bug reports found:
Bugs with severity serious
1) #868551 File conflict between redis-server-dbgsym and redis-tools-dbgsym
[RESOLVED]
Bugs with severity important
2) #881682 redis: FTBFS on alpha and sparc64: [err]: Memory efficiency with
values in range 16384 [RESOLVED]
3) #881683 redis: FTBFS on kFreeBSD: taskset: Command not found [RESOLVED]
4) #881684 redis: FTBFS on hurd-i386: MAXPATHLEN undeclared [RESOLVED]
Bugs with severity minor
5) #880474 redis-server: Unknown lvalue 'RunTimeDirectory' in section
'Service'
Bugs with severity wishlist
6) #876475 redis-server: Make "apt install redis" work [RESOLVED]
(6-6/6) Is the bug you found listed above [y|N|b|m|r|q|s|f|e|?]? n
Maintainer for redis-server is 'Chris Lamb <la...@debian.org
<mailto:la...@debian.org>>'.
Looking up dependencies of redis-server...
Getting changed configuration files...
Briefly describe the problem (max. 100 characters allowed). This will be the
bug email subject, so keep the summary as concise as
possible, for example: "fails to send email" or "does not start with -q option
specified" (enter Ctrl+c to exit reportbug without
reporting a bug).
> redis-server.service ExecStart=/usr/bin/redis-server /etc/redis/redis.conf
> (code=exited, status=226/NAMESPACE)
Your description is a bit long; please enter a shorter subject. (An empty
response will retain the existing subject.)
> ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited,
> status=226/NAMESPACE)
Rewriting subject to 'redis-server: ExecStart=/usr/bin/redis-server
/etc/redis/redis.conf (code=exited, status=226/NAMESPACE)'
How would you rate the severity of this problem or report?
1 critical makes unrelated software on the system (or the whole system)
break, or causes serious data loss, or introduces a
security hole on systems where you install the package.
2 grave makes the package in question unusable by most or all users,
or causes data loss, or introduces a security hole
allowing access to the accounts of users who use the package.
3 serious is a severe violation of Debian policy (that is, the problem
is a violation of a 'must' or 'required' directive);
may or may not affect the usability of the package. Note that
non-severe policy violations may be 'normal,'
'minor,' or 'wishlist' bugs. (Package maintainers may also
designate other bugs as 'serious' and thus release-
critical; however, end users should not do so.). For the
canonical list of issues worthing a serious severity you
can refer to this webpage:
http://release.debian.org/testing/rc_policy.txt
<http://release.debian.org/testing/rc_policy.txt> .
4 important a bug which has a major effect on the usability of a package,
without rendering it completely unusable to everyone.
5 does-not-build a bug that stops the package from being built from source.
(This is a 'virtual severity'.)
6 normal a bug that does not undermine the usability of the whole
package; for example, a problem with a particular option
or menu item.
7 minor things like spelling mistakes and other minor cosmetic errors
that do not affect the core functionality of the
package.
8 wishlist suggestions and requests for new features.
Please select a severity level: [normal] 4
Do any of the following apply to this report?
1 d-i This bug is relevant to the development of debian-installer.
2 ipv6 This bug affects support for Internet Protocol version 6.
3 l10n This bug reports a localization/internationalization issue.
4 lfs This bug affects support for large files (over 2 gigabytes).
5 newcomer This bug has a known solution but the maintainer requests someone
else implement it.
6 patch You are including a patch to fix this problem.
7 upstream This bug applies to the upstream part of the package.
8 none
Please select tags: (one at a time) [none] 1
- selected: d-i
Please select tags: (one at a time) [done]
Spawning vi...
Traceback (most recent call last):
File "/usr/bin/reportbug", line 2234, in <module>
main()
File "/usr/bin/reportbug", line 1107, in main
return iface.user_interface()
File "/usr/bin/reportbug", line 1225, in user_interface
main()
File "/usr/bin/reportbug", line 1107, in main
return iface.user_interface()
File "/usr/bin/reportbug", line 2150, in user_interface
package, severity, mode, charset=charset, tags=tags)
File "/usr/bin/reportbug", line 182, in handle_editing
editor, charset)
File "/usr/lib/python3/dist-packages/reportbug/ui/text_ui.py", line 1064, in
spawn_editor
newmessage = open(filename).read()
File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 1780:
ordinal not in range(128)
--- End Message ---
--- Begin Message ---
Source: reportbug
Source-Version: 7.1.8
We believe that the bug you reported is fixed in the latest version of
reportbug, 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 883...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sandro Tosi <mo...@debian.org> (supplier of updated reportbug 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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Thu, 28 Dec 2017 23:25:43 -0500
Source: reportbug
Binary: reportbug python3-reportbug
Architecture: source all
Version: 7.1.8
Distribution: unstable
Urgency: medium
Maintainer: Reportbug Maintainers <reportbug-maint@lists.alioth.debian.org>
Changed-By: Sandro Tosi <mo...@debian.org>
Description:
python3-reportbug - Python modules for interacting with bug tracking systems
reportbug - reports bugs in the Debian distribution
Closes: 695887 773346 849763 849765 863823 866596 868022 868154 871527 871769
872780 875309 877650 878420 878436 878437 878538 882130 882983 883577
Changes:
reportbug (7.1.8) unstable; urgency=medium
.
* reportbug/debbugs.py
- add `a11y` tag
- dont RFC2047-encode the Owner pseudo header when submitting a WNPP bug;
patch by Nis Martensen; Closes: #872780
* reportbug/utils.py, bin/*
- fix invalid escape sequence deprecation warnings with Python 3.6; patch
by
Ville Skyttä; Closes: #878437
- redirect stderr to stdout when running commands via get_command_output(),
and this prevents errors to be sent to the terminal; Closes: #882130
* reportbug/ui/gtk2_ui.py
- typo fix; Closes: #875309
* debian/control
- add sensible-utils to reportbug depends, since we require sensible-*
commands to be available; Closes: #871527
* man/reportbug.1
- fix reference to -A/--attach in the include-file section; patch by Alex
Muntada; Closes: #871769, #878420
* reportbug/{debbugs.py, utils.py}
- add tailing new-line when processing strings line by line; patch by Nis
Martensen; Closes: #866596
* reportbug/submit.py
- remove spurious print() of MIME type, introduced during the py3k porting;
patch by Nis Martensen; Closes: #868154
- use quoted-printable encoding for lines that are over 980 chars long;
patch by Nis Martensen; Closes: #849765
* fix some spelling errors; patch by Ville Skyttä; Closes: #878436
* bin/reportbug
- preserve attachments order; patch by Ville Skyttä; Closes: #878538
* add Linux Security Model (LSM) information to the 'System info' section of
the bug report (if any LSM is enabled on the system); patch by Laurent
Bigonville and intrigeri; Closes: #773346
* debian/source/options
- use the default XZ compression algo by removing the custom setting to use
bzip2; patch by Boyuan Yang; Closes: #863823
* use context managers to avoid leaving unclosed file descriptors (which
often
results in users losing control of their terminal windows); patch by Nis
Martensen; Closes: #695887, #849763, #882983
* prevent Unicode(De|En)codeError with most open() calls by using
'backslashreplace' in case of errors; patch by Nis Martensen;
Closes: #877650, #883577, #868022
* debian/copyright
- leave only me as Upstream-Author and Packaged-By
* debian/control
- bump Standards-Version to 4.1.2 (no changes needed)
* debian/rules
- dont call dpkg-parsechangelog directly, use dpkg/pkg-info.mk instead
Checksums-Sha1:
a2a0567f6c0e867eea588a3f86005e3b92a4714d 1818 reportbug_7.1.8.dsc
5a37448de289ef4a777065a3cab8b61f5a011db0 369944 reportbug_7.1.8.tar.xz
f96526f7050214b73a1dcbdf889e7b7c2866356b 130416 python3-reportbug_7.1.8_all.deb
143a36b32afb62f4d8370a29f5cfba7ac1bc867f 128512 reportbug_7.1.8_all.deb
c04fbe7286aa5d9b7d9dc8549d15fa5a482085bb 7219 reportbug_7.1.8_amd64.buildinfo
Checksums-Sha256:
6770032e1237534378e1f7d33fc51582a1c5c41e0b7a606347639eedb43b38b8 1818
reportbug_7.1.8.dsc
12cf48d3bdf60f0f9400c31cf7076ba3a5d445c20f47e6eba6924798ca02b0cd 369944
reportbug_7.1.8.tar.xz
f55a140f7dbbf71d383a9f4ba5db24ff4756aac500df74426a767571aef8af2c 130416
python3-reportbug_7.1.8_all.deb
ad3c6fa6162a862a48132e976eed21e249502f0cbe04e00ba9dce76df00ad29b 128512
reportbug_7.1.8_all.deb
335140ea5a521c3e468af09441c4c595a7271bf1b0b10921760dfccb357c49ae 7219
reportbug_7.1.8_amd64.buildinfo
Files:
872a8ae8a2827e9ec1e586f04d968fa0 1818 utils standard reportbug_7.1.8.dsc
d33d99e01ac3457736e9d4ba42513779 369944 utils standard reportbug_7.1.8.tar.xz
6a1ffcc9e641ae969b93a90ec0d33330 130416 python standard
python3-reportbug_7.1.8_all.deb
8fea5d646e5c2e143aedae8e29e356aa 128512 utils standard reportbug_7.1.8_all.deb
1f875e506d281d40521188f8df7ce5ec 7219 utils standard
reportbug_7.1.8_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAlpFxY0ACgkQh588mTgB
qU9BixAAz5Q8PL+Kg+NaVBMkIxLt5oLRLaM7aZk3YDsuNJdBMVqY9YYv94W1BSCr
pw9ycNpcpyAokfS5zGetGryxHFEkd0O+VEwCtbU8RukvqupaZPRtkNeVspioFNOr
xgDXCPNAjVcEc3P1gymZ+96CwDjp5/rW+QGIG3ZmuIas4fPd9ZfliAphEOzOqXEW
932W9SrDBJz15ShfKlGeqxmZaD1qIuXzCtEH931bArfZHw237QxSLEXzsYikr/cj
0jvNC7MDYS8QRe4y8sbqFUBaUnlPYEK9pNpZw4zfQzaUj//dAh5M2KIgCIC2KUYN
1zjP88o24Gt4qyA+Ok/5yFf3i3cveEuo7ZNXqij7n6mJdCCMAg5HGrnnSzSRWCNn
j6Fo1ujf69mm090Zx2XOacZXQl79crrBocxH/ajqqsNGym3ghb4kVoTGZgZh08mE
Rt5rqKZ8XN2nTxYRhXNl6rwADGRlR2ABfq6gA6wz2YVaPMU8olNMM2Nzl0IJRxyH
WhI5ZhZHnCLeqk2X75IU3bMbdsWaQIaWtB83aIW/qrsv52Rgqn2a5VdmkUnDc7kp
CZQksVG5j5WYfi4BWrEpMk5H9uuRwAkSKzbGsuwgV1ILESRT3HaD96gDin8rwdY6
ouioIhUKE4L3qqVl9/aw2CtNVMCaMRoZyeEJbiN/FUUiIqJdlMY=
=v+O4
-----END PGP SIGNATURE-----
--- End Message ---
_______________________________________________
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
