| 2012-07-26 20:32:29 |
Aimon Bustardo |
bug |
|
|
added bug |
| 2012-07-26 20:34:40 |
Aimon Bustardo |
description |
Ubuntu 12.0.4 LTS 64bit
Python converts all syslog messages to UTF8 before sending to syslog. It also prepends the Byte Order Mark (BOM) of the Unicode Standard. This prepended BOM causes bad characters when using rsyslog (have not verified with std syslog or syslog-ng).
Example log line:
Jul 25 13:36:03 mc 2012-07-25 13:36:03 INFO nova.api.openstack.wsgi [req-48a555a5-6d2a-4a38-8384-3b4684357e72 19f932a5b0b34655989f4cb761522bb3 2617e657fdf84569a6be7977318e46c8] http://mc.la-1-11.morphlabs.net:8774/v1.1/2617e657fdf84569a6be7977318e46c8/os-hosts/cn32.la-1-11.morphcloud.net.json?ignore_awful_caching1343248563 returned with HTTP 200
Note the ' ' before the date field.
Interesting find on issues from another site:
"Yes, "" is the Byte Order Mark (BOM) of the Unicode Standard. Specifically it is the hex bytes EF BB BF, which form the UTF-8 representation of the BOM, misinterpreted as ISO 8859/1 text instead of UTF-8.
Probably what it means is that you are using a text editor that is saving files in UTF-8 with the BOM, when it should be saving without the BOM. It could be PHP files that have the BOM, in which case they'd appear as literal text on your page. Or it could be translated text you pasted into Joomla! edit windows.
The Unicode Consortium's FAQ on the Byte Order Mark is at http://www.unicode.org/faq/utf_bom.html#BOM ."
Note that if I edit the file: /usr/lib/python2.7/logging/handlers.py as shown in this patch, the bad characters go away:
----------------------------------------------------------
@@ -797,9 +797,10 @@
self.mapPriority(record.levelname))
# Message is a string. Convert to bytes as required by RFC 5424
if type(msg) is unicode:
+ # Morph
msg = msg.encode('utf-8')
- if codecs:
- msg = codecs.BOM_UTF8 + msg
+ #if codecs:
+ # msg = codecs.BOM_UTF8 + msg
msg = prio + msg
try:
if self.unixsocket:
----------------------------------------------------
Perhaps something is wrong with the 'codec' condition?? |
Ubuntu 12.0.4 LTS 64bit
python2.7-minimal 2.7.3-0ubuntu3
rsyslog 5.8.6-1ubuntu8
Python converts all syslog messages to UTF8 before sending to syslog. It also prepends the Byte Order Mark (BOM) of the Unicode Standard. This prepended BOM causes bad characters when using rsyslog (have not verified with std syslog or syslog-ng).
Example log line:
Jul 25 13:36:03 mc 2012-07-25 13:36:03 INFO nova.api.openstack.wsgi [req-48a555a5-6d2a-4a38-8384-3b4684357e72 19f932a5b0b34655989f4cb761522bb3 2617e657fdf84569a6be7977318e46c8] http://mc.la-1-11.morphlabs.net:8774/v1.1/2617e657fdf84569a6be7977318e46c8/os-hosts/cn32.la-1-11.morphcloud.net.json?ignore_awful_caching1343248563 returned with HTTP 200
Note the ' ' before the date field.
Interesting find on issues from another site:
"Yes, "" is the Byte Order Mark (BOM) of the Unicode Standard. Specifically it is the hex bytes EF BB BF, which form the UTF-8 representation of the BOM, misinterpreted as ISO 8859/1 text instead of UTF-8.
Probably what it means is that you are using a text editor that is saving files in UTF-8 with the BOM, when it should be saving without the BOM. It could be PHP files that have the BOM, in which case they'd appear as literal text on your page. Or it could be translated text you pasted into Joomla! edit windows.
The Unicode Consortium's FAQ on the Byte Order Mark is at http://www.unicode.org/faq/utf_bom.html#BOM ."
Note that if I edit the file: /usr/lib/python2.7/logging/handlers.py as shown in this patch, the bad characters go away:
----------------------------------------------------------
@@ -797,9 +797,10 @@
self.mapPriority(record.levelname))
# Message is a string. Convert to bytes as required by RFC 5424
if type(msg) is unicode:
+ # Morph
msg = msg.encode('utf-8')
- if codecs:
- msg = codecs.BOM_UTF8 + msg
+ #if codecs:
+ # msg = codecs.BOM_UTF8 + msg
msg = prio + msg
try:
if self.unixsocket:
----------------------------------------------------
Perhaps something is wrong with the 'codec' condition?? |
|
| 2012-07-26 20:40:04 |
Aimon Bustardo |
description |
Ubuntu 12.0.4 LTS 64bit
python2.7-minimal 2.7.3-0ubuntu3
rsyslog 5.8.6-1ubuntu8
Python converts all syslog messages to UTF8 before sending to syslog. It also prepends the Byte Order Mark (BOM) of the Unicode Standard. This prepended BOM causes bad characters when using rsyslog (have not verified with std syslog or syslog-ng).
Example log line:
Jul 25 13:36:03 mc 2012-07-25 13:36:03 INFO nova.api.openstack.wsgi [req-48a555a5-6d2a-4a38-8384-3b4684357e72 19f932a5b0b34655989f4cb761522bb3 2617e657fdf84569a6be7977318e46c8] http://mc.la-1-11.morphlabs.net:8774/v1.1/2617e657fdf84569a6be7977318e46c8/os-hosts/cn32.la-1-11.morphcloud.net.json?ignore_awful_caching1343248563 returned with HTTP 200
Note the ' ' before the date field.
Interesting find on issues from another site:
"Yes, "" is the Byte Order Mark (BOM) of the Unicode Standard. Specifically it is the hex bytes EF BB BF, which form the UTF-8 representation of the BOM, misinterpreted as ISO 8859/1 text instead of UTF-8.
Probably what it means is that you are using a text editor that is saving files in UTF-8 with the BOM, when it should be saving without the BOM. It could be PHP files that have the BOM, in which case they'd appear as literal text on your page. Or it could be translated text you pasted into Joomla! edit windows.
The Unicode Consortium's FAQ on the Byte Order Mark is at http://www.unicode.org/faq/utf_bom.html#BOM ."
Note that if I edit the file: /usr/lib/python2.7/logging/handlers.py as shown in this patch, the bad characters go away:
----------------------------------------------------------
@@ -797,9 +797,10 @@
self.mapPriority(record.levelname))
# Message is a string. Convert to bytes as required by RFC 5424
if type(msg) is unicode:
+ # Morph
msg = msg.encode('utf-8')
- if codecs:
- msg = codecs.BOM_UTF8 + msg
+ #if codecs:
+ # msg = codecs.BOM_UTF8 + msg
msg = prio + msg
try:
if self.unixsocket:
----------------------------------------------------
Perhaps something is wrong with the 'codec' condition?? |
Ubuntu 12.0.4 LTS 64bit
python2.7-minimal 2.7.3-0ubuntu3
rsyslog 5.8.6-1ubuntu8
Python converts all syslog messages to UTF8 before sending to syslog. It also prepends the Byte Order Mark (BOM) of the Unicode Standard. This prepended BOM causes bad characters when using rsyslog (have not verified with std syslog or syslog-ng).
Example log line:
Jul 25 13:36:03 mc 2012-07-25 13:36:03 INFO nova.api.openstack.wsgi [req-48a555a5-6d2a-4a38-8384-3b4684357e72 19f932a5b0b34655989f4cb761522bb3 2617e657fdf84569a6be7977318e46c8] http://mc.la-1-11.morphlabs.net:8774/v1.1/2617e657fdf84569a6be7977318e46c8/os-hosts/cn32.la-1-11.morphcloud.net.json?ignore_awful_caching1343248563 returned with HTTP 200
Note the ' ' before the date field.
Interesting find on issues from another site:
"Yes, "" is the Byte Order Mark (BOM) of the Unicode Standard. Specifically it is the hex bytes EF BB BF, which form the UTF-8 representation of the BOM, misinterpreted as ISO 8859/1 text instead of UTF-8.
Probably what it means is that you are using a text editor that is saving files in UTF-8 with the BOM, when it should be saving without the BOM. It could be PHP files that have the BOM, in which case they'd appear as literal text on your page. Or it could be translated text you pasted into Joomla! edit windows.
The Unicode Consortium's FAQ on the Byte Order Mark is at http://www.unicode.org/faq/utf_bom.html#BOM ."
Note that if I edit the file: /usr/lib/python2.7/logging/handlers.py as shown in this patch, the bad characters go away:
----------------------------------------------------------
@@ -797,9 +797,10 @@
self.mapPriority(record.levelname))
# Message is a string. Convert to bytes as required by RFC 5424
if type(msg) is unicode:
+ # Morph
msg = msg.encode('utf-8')
- if codecs:
- msg = codecs.BOM_UTF8 + msg
+ #if codecs:
+ # msg = codecs.BOM_UTF8 + msg
msg = prio + msg
try:
if self.unixsocket:
----------------------------------------------------
Perhaps something is wrong with the 'codecs' condition?? |
|
| 2012-07-26 20:40:22 |
Aimon Bustardo |
description |
Ubuntu 12.0.4 LTS 64bit
python2.7-minimal 2.7.3-0ubuntu3
rsyslog 5.8.6-1ubuntu8
Python converts all syslog messages to UTF8 before sending to syslog. It also prepends the Byte Order Mark (BOM) of the Unicode Standard. This prepended BOM causes bad characters when using rsyslog (have not verified with std syslog or syslog-ng).
Example log line:
Jul 25 13:36:03 mc 2012-07-25 13:36:03 INFO nova.api.openstack.wsgi [req-48a555a5-6d2a-4a38-8384-3b4684357e72 19f932a5b0b34655989f4cb761522bb3 2617e657fdf84569a6be7977318e46c8] http://mc.la-1-11.morphlabs.net:8774/v1.1/2617e657fdf84569a6be7977318e46c8/os-hosts/cn32.la-1-11.morphcloud.net.json?ignore_awful_caching1343248563 returned with HTTP 200
Note the ' ' before the date field.
Interesting find on issues from another site:
"Yes, "" is the Byte Order Mark (BOM) of the Unicode Standard. Specifically it is the hex bytes EF BB BF, which form the UTF-8 representation of the BOM, misinterpreted as ISO 8859/1 text instead of UTF-8.
Probably what it means is that you are using a text editor that is saving files in UTF-8 with the BOM, when it should be saving without the BOM. It could be PHP files that have the BOM, in which case they'd appear as literal text on your page. Or it could be translated text you pasted into Joomla! edit windows.
The Unicode Consortium's FAQ on the Byte Order Mark is at http://www.unicode.org/faq/utf_bom.html#BOM ."
Note that if I edit the file: /usr/lib/python2.7/logging/handlers.py as shown in this patch, the bad characters go away:
----------------------------------------------------------
@@ -797,9 +797,10 @@
self.mapPriority(record.levelname))
# Message is a string. Convert to bytes as required by RFC 5424
if type(msg) is unicode:
+ # Morph
msg = msg.encode('utf-8')
- if codecs:
- msg = codecs.BOM_UTF8 + msg
+ #if codecs:
+ # msg = codecs.BOM_UTF8 + msg
msg = prio + msg
try:
if self.unixsocket:
----------------------------------------------------
Perhaps something is wrong with the 'codecs' condition?? |
Ubuntu 12.0.4 LTS 64bit
python2.7-minimal 2.7.3-0ubuntu3
rsyslog 5.8.6-1ubuntu8
Python converts all syslog messages to UTF8 before sending to syslog. It also prepends the Byte Order Mark (BOM) of the Unicode Standard. This prepended BOM causes bad characters when using rsyslog (have not verified with std syslog or syslog-ng).
Example log line:
Jul 25 13:36:03 mc 2012-07-25 13:36:03 INFO nova.api.openstack.wsgi [req-48a555a5-6d2a-4a38-8384-3b4684357e72 19f932a5b0b34655989f4cb761522bb3 2617e657fdf84569a6be7977318e46c8] http://MASKED:8774/v1.1/2617e657fdf84569a6be7977318e46c8/os-hosts/cn32.la-1-11.morphcloud.net.json?ignore_awful_caching1343248563 returned with HTTP 200
Note the ' ' before the date field.
Interesting find on issues from another site:
"Yes, "" is the Byte Order Mark (BOM) of the Unicode Standard. Specifically it is the hex bytes EF BB BF, which form the UTF-8 representation of the BOM, misinterpreted as ISO 8859/1 text instead of UTF-8.
Probably what it means is that you are using a text editor that is saving files in UTF-8 with the BOM, when it should be saving without the BOM. It could be PHP files that have the BOM, in which case they'd appear as literal text on your page. Or it could be translated text you pasted into Joomla! edit windows.
The Unicode Consortium's FAQ on the Byte Order Mark is at http://www.unicode.org/faq/utf_bom.html#BOM ."
Note that if I edit the file: /usr/lib/python2.7/logging/handlers.py as shown in this patch, the bad characters go away:
----------------------------------------------------------
@@ -797,9 +797,10 @@
self.mapPriority(record.levelname))
# Message is a string. Convert to bytes as required by RFC 5424
if type(msg) is unicode:
+ # Morph
msg = msg.encode('utf-8')
- if codecs:
- msg = codecs.BOM_UTF8 + msg
+ #if codecs:
+ # msg = codecs.BOM_UTF8 + msg
msg = prio + msg
try:
if self.unixsocket:
----------------------------------------------------
Perhaps something is wrong with the 'codecs' condition?? |
|
| 2012-07-26 20:40:41 |
Aimon Bustardo |
description |
Ubuntu 12.0.4 LTS 64bit
python2.7-minimal 2.7.3-0ubuntu3
rsyslog 5.8.6-1ubuntu8
Python converts all syslog messages to UTF8 before sending to syslog. It also prepends the Byte Order Mark (BOM) of the Unicode Standard. This prepended BOM causes bad characters when using rsyslog (have not verified with std syslog or syslog-ng).
Example log line:
Jul 25 13:36:03 mc 2012-07-25 13:36:03 INFO nova.api.openstack.wsgi [req-48a555a5-6d2a-4a38-8384-3b4684357e72 19f932a5b0b34655989f4cb761522bb3 2617e657fdf84569a6be7977318e46c8] http://MASKED:8774/v1.1/2617e657fdf84569a6be7977318e46c8/os-hosts/cn32.la-1-11.morphcloud.net.json?ignore_awful_caching1343248563 returned with HTTP 200
Note the ' ' before the date field.
Interesting find on issues from another site:
"Yes, "" is the Byte Order Mark (BOM) of the Unicode Standard. Specifically it is the hex bytes EF BB BF, which form the UTF-8 representation of the BOM, misinterpreted as ISO 8859/1 text instead of UTF-8.
Probably what it means is that you are using a text editor that is saving files in UTF-8 with the BOM, when it should be saving without the BOM. It could be PHP files that have the BOM, in which case they'd appear as literal text on your page. Or it could be translated text you pasted into Joomla! edit windows.
The Unicode Consortium's FAQ on the Byte Order Mark is at http://www.unicode.org/faq/utf_bom.html#BOM ."
Note that if I edit the file: /usr/lib/python2.7/logging/handlers.py as shown in this patch, the bad characters go away:
----------------------------------------------------------
@@ -797,9 +797,10 @@
self.mapPriority(record.levelname))
# Message is a string. Convert to bytes as required by RFC 5424
if type(msg) is unicode:
+ # Morph
msg = msg.encode('utf-8')
- if codecs:
- msg = codecs.BOM_UTF8 + msg
+ #if codecs:
+ # msg = codecs.BOM_UTF8 + msg
msg = prio + msg
try:
if self.unixsocket:
----------------------------------------------------
Perhaps something is wrong with the 'codecs' condition?? |
Ubuntu 12.0.4 LTS 64bit
python2.7-minimal 2.7.3-0ubuntu3
rsyslog 5.8.6-1ubuntu8
Python converts all syslog messages to UTF8 before sending to syslog. It also prepends the Byte Order Mark (BOM) of the Unicode Standard. This prepended BOM causes bad characters when using rsyslog (have not verified with std syslog or syslog-ng).
Example log line:
Jul 25 13:36:03 mc 2012-07-25 13:36:03 INFO nova.api.openstack.wsgi [req-48a555a5-6d2a-4a38-8384-3b4684357e72 19f932a5b0b34655989f4cb761522bb3 2617e657fdf84569a6be7977318e46c8] http://MASKED:8774/v1.1/2617e657fdf84569a6be7977318e46c8/os-hosts/MASKED.json?ignore_awful_caching1343248563 returned with HTTP 200
Note the ' ' before the date field.
Interesting find on issues from another site:
"Yes, "" is the Byte Order Mark (BOM) of the Unicode Standard. Specifically it is the hex bytes EF BB BF, which form the UTF-8 representation of the BOM, misinterpreted as ISO 8859/1 text instead of UTF-8.
Probably what it means is that you are using a text editor that is saving files in UTF-8 with the BOM, when it should be saving without the BOM. It could be PHP files that have the BOM, in which case they'd appear as literal text on your page. Or it could be translated text you pasted into Joomla! edit windows.
The Unicode Consortium's FAQ on the Byte Order Mark is at http://www.unicode.org/faq/utf_bom.html#BOM ."
Note that if I edit the file: /usr/lib/python2.7/logging/handlers.py as shown in this patch, the bad characters go away:
----------------------------------------------------------
@@ -797,9 +797,10 @@
self.mapPriority(record.levelname))
# Message is a string. Convert to bytes as required by RFC 5424
if type(msg) is unicode:
+ # Morph
msg = msg.encode('utf-8')
- if codecs:
- msg = codecs.BOM_UTF8 + msg
+ #if codecs:
+ # msg = codecs.BOM_UTF8 + msg
msg = prio + msg
try:
if self.unixsocket:
----------------------------------------------------
Perhaps something is wrong with the 'codecs' condition?? |
|
| 2012-07-26 20:54:10 |
Aimon Bustardo |
bug watch added |
|
http://bugzilla.adiscon.com/show_bug.cgi?id=346 |
|
| 2012-07-26 21:07:40 |
Aimon Bustardo |
bug watch added |
|
http://bugs.python.org/issue15462 |
|
| 2012-07-27 05:58:30 |
Scott Kitterman |
python2.7 (Ubuntu): status |
New |
Fix Released |
|
| 2012-07-27 05:58:55 |
Scott Kitterman |
nominated for series |
|
Ubuntu Precise |
|
| 2012-07-27 05:58:55 |
Scott Kitterman |
bug task added |
|
python2.7 (Ubuntu Precise) |
|
| 2012-07-27 05:58:55 |
Scott Kitterman |
nominated for series |
|
Ubuntu Quantal |
|
| 2012-07-27 05:58:55 |
Scott Kitterman |
bug task added |
|
python2.7 (Ubuntu Quantal) |
|
| 2012-07-27 05:59:07 |
Scott Kitterman |
python2.7 (Ubuntu Precise): milestone |
|
ubuntu-12.04.1 |
|
| 2012-07-27 05:59:14 |
Scott Kitterman |
python2.7 (Ubuntu Precise): status |
New |
Triaged |
|
| 2012-07-27 05:59:18 |
Scott Kitterman |
python2.7 (Ubuntu Precise): importance |
Undecided |
High |
|
| 2012-07-27 05:59:21 |
Scott Kitterman |
python2.7 (Ubuntu Quantal): importance |
Undecided |
High |
|
| 2012-07-28 02:41:02 |
Scott Kitterman |
python2.7 (Ubuntu Quantal): status |
Fix Released |
Triaged |
|
| 2012-07-28 02:41:07 |
Scott Kitterman |
python2.7 (Ubuntu Quantal): milestone |
|
ubuntu-12.10 |
|
| 2012-07-28 02:41:10 |
Scott Kitterman |
python2.7 (Ubuntu Quantal): milestone |
ubuntu-12.10 |
ubuntu-12.10-beta-1 |
|
| 2012-07-28 06:15:12 |
Launchpad Janitor |
python2.7 (Ubuntu Quantal): status |
Triaged |
Fix Released |
|
| 2012-07-28 06:23:39 |
Scott Kitterman |
description |
Ubuntu 12.0.4 LTS 64bit
python2.7-minimal 2.7.3-0ubuntu3
rsyslog 5.8.6-1ubuntu8
Python converts all syslog messages to UTF8 before sending to syslog. It also prepends the Byte Order Mark (BOM) of the Unicode Standard. This prepended BOM causes bad characters when using rsyslog (have not verified with std syslog or syslog-ng).
Example log line:
Jul 25 13:36:03 mc 2012-07-25 13:36:03 INFO nova.api.openstack.wsgi [req-48a555a5-6d2a-4a38-8384-3b4684357e72 19f932a5b0b34655989f4cb761522bb3 2617e657fdf84569a6be7977318e46c8] http://MASKED:8774/v1.1/2617e657fdf84569a6be7977318e46c8/os-hosts/MASKED.json?ignore_awful_caching1343248563 returned with HTTP 200
Note the ' ' before the date field.
Interesting find on issues from another site:
"Yes, "" is the Byte Order Mark (BOM) of the Unicode Standard. Specifically it is the hex bytes EF BB BF, which form the UTF-8 representation of the BOM, misinterpreted as ISO 8859/1 text instead of UTF-8.
Probably what it means is that you are using a text editor that is saving files in UTF-8 with the BOM, when it should be saving without the BOM. It could be PHP files that have the BOM, in which case they'd appear as literal text on your page. Or it could be translated text you pasted into Joomla! edit windows.
The Unicode Consortium's FAQ on the Byte Order Mark is at http://www.unicode.org/faq/utf_bom.html#BOM ."
Note that if I edit the file: /usr/lib/python2.7/logging/handlers.py as shown in this patch, the bad characters go away:
----------------------------------------------------------
@@ -797,9 +797,10 @@
self.mapPriority(record.levelname))
# Message is a string. Convert to bytes as required by RFC 5424
if type(msg) is unicode:
+ # Morph
msg = msg.encode('utf-8')
- if codecs:
- msg = codecs.BOM_UTF8 + msg
+ #if codecs:
+ # msg = codecs.BOM_UTF8 + msg
msg = prio + msg
try:
if self.unixsocket:
----------------------------------------------------
Perhaps something is wrong with the 'codecs' condition?? |
[IMPACT]
Any UTF-8 messages that are sent to syslog by a Python application are corrupted.
[TESTCASE]
Run the code in comment #9. You can either do this by running the python interpreter and pasting the code into the python shell or creating a file with the code and running it as python foo where foo is the name of the file.
Then check /var/log/syslog for the mesage "AUDIT: TEST LOGER FROM PYTHON". There will be a few characters of garbage or odd looking numbers before the word AUDIT. If you see that, you've recreated the problem.
Install the updated packages from -proposed and re-run the python code from comment #9. Now there should be now garbage or unusual characters. Something like:
root: AUDIT: TEST LOGER FROM PYTHON
If you get that, the fix is verified.
[Regression Potential]
Nil. Patch is backported from upstream and is easily visually verified as correct.
[Other Info]
I ran this by Barry Warsaw and he agreed it would be important to get into 12.04.1.
Original Bug:
Ubuntu 12.0.4 LTS 64bit
python2.7-minimal 2.7.3-0ubuntu3
rsyslog 5.8.6-1ubuntu8
Python converts all syslog messages to UTF8 before sending to syslog. It also prepends the Byte Order Mark (BOM) of the Unicode Standard. This prepended BOM causes bad characters when using rsyslog (have not verified with std syslog or syslog-ng).
Example log line:
Jul 25 13:36:03 mc 2012-07-25 13:36:03 INFO nova.api.openstack.wsgi [req-48a555a5-6d2a-4a38-8384-3b4684357e72 19f932a5b0b34655989f4cb761522bb3 2617e657fdf84569a6be7977318e46c8] http://MASKED:8774/v1.1/2617e657fdf84569a6be7977318e46c8/os-hosts/MASKED.json?ignore_awful_caching1343248563 returned with HTTP 200
Note the ' ' before the date field.
Interesting find on issues from another site:
"Yes, "" is the Byte Order Mark (BOM) of the Unicode Standard. Specifically it is the hex bytes EF BB BF, which form the UTF-8 representation of the BOM, misinterpreted as ISO 8859/1 text instead of UTF-8.
Probably what it means is that you are using a text editor that is saving files in UTF-8 with the BOM, when it should be saving without the BOM. It could be PHP files that have the BOM, in which case they'd appear as literal text on your page. Or it could be translated text you pasted into Joomla! edit windows.
The Unicode Consortium's FAQ on the Byte Order Mark is at http://www.unicode.org/faq/utf_bom.html#BOM ."
Note that if I edit the file: /usr/lib/python2.7/logging/handlers.py as shown in this patch, the bad characters go away:
----------------------------------------------------------
@@ -797,9 +797,10 @@
self.mapPriority(record.levelname))
# Message is a string. Convert to bytes as required by RFC 5424
if type(msg) is unicode:
+ # Morph
msg = msg.encode('utf-8')
- if codecs:
- msg = codecs.BOM_UTF8 + msg
+ #if codecs:
+ # msg = codecs.BOM_UTF8 + msg
msg = prio + msg
try:
if self.unixsocket:
----------------------------------------------------
Perhaps something is wrong with the 'codecs' condition?? |
|
| 2012-07-28 06:23:53 |
Scott Kitterman |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2012-07-28 06:24:07 |
Scott Kitterman |
python2.7 (Ubuntu Precise): status |
Triaged |
In Progress |
|
| 2012-07-28 06:24:10 |
Scott Kitterman |
python2.7 (Ubuntu Quantal): assignee |
|
Scott Kitterman (kitterman) |
|
| 2012-07-28 06:24:12 |
Scott Kitterman |
python2.7 (Ubuntu Precise): assignee |
|
Scott Kitterman (kitterman) |
|
| 2012-07-28 06:43:50 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/python2.7 |
|
| 2012-08-01 04:41:18 |
Adam Conrad |
python2.7 (Ubuntu Precise): status |
In Progress |
Fix Committed |
|
| 2012-08-01 04:41:22 |
Adam Conrad |
bug |
|
|
added subscriber SRU Verification |
| 2012-08-01 04:41:24 |
Adam Conrad |
tags |
|
verification-needed |
|
| 2012-08-01 05:42:42 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/precise-proposed/python2.7 |
|
| 2012-08-01 18:12:29 |
Aimon Bustardo |
python2.7 (Ubuntu Precise): status |
Fix Committed |
Confirmed |
|
| 2012-08-01 18:22:27 |
Scott Kitterman |
python2.7 (Ubuntu Precise): status |
Confirmed |
Fix Committed |
|
| 2012-08-01 18:22:37 |
Scott Kitterman |
tags |
verification-needed |
verification-done |
|
| 2012-08-08 11:58:14 |
Colin Watson |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2012-08-08 11:59:09 |
Launchpad Janitor |
python2.7 (Ubuntu Precise): status |
Fix Committed |
Fix Released |
|
