Bug 498359 - C-m (control+m, aka. 0x0d byte) characters in updateinfo data for RHEL-5
C-m (control+m, aka. 0x0d byte) characters in updateinfo data for RHEL-5
Status: CLOSED EOL
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Backend (Show other bugs)
rhn506
All Linux
high Severity medium
: ---
: ---
Assigned To: rhn-dev-list
Red Hat Network Quality Assurance
US=93740
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-04-29 23:48 EDT by James Antill
Modified: 2017-07-05 11:14 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description James Antill 2009-04-29 23:48:35 EDT
Description of problem:
 This might well be a RHEL rel-eng problem, not sure, so feel free to reassign somewhere else. But there are a lot of 0x0d bytes in the updateinfo for RHEL-5. RHBA-2008:0369 is one example. Eg. (from yum info-security RHBA-2008:0369):

"""NetworkManager is a network link man
ager that attempts to keep a wired or
wireless network connection active at all times.

...
"""

...this doesn't show in older versions of yum because we used textwrap, which filtered these characters. In the current 5.4 candidate we changed that code to be utf8 safe (and actual print something readable most of the time) ... and so we now try and "print" them.
 It also "helped" that in 5.3 the output was unreadable anyway, so it would have been harder to notice it going bad :).

Version-Release number of selected component (if applicable):
 Current repodata.
 yum-3.2.22-11.el5.noarch.rpm

 I've marked this as priority high, as if you can't fix it easily I'd like to know so I can put in a replace(0x0d, '') or replace(0x0d, ' ') on the client side (the later is basically what happened before, AIUI).
Comment 2 Thomas "Shea" DeAntonio 2017-07-05 11:14:02 EDT
As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. 
 
If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. 
 
Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request.  You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management).  If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support).
Comment 3 Thomas "Shea" DeAntonio 2017-07-05 11:14:34 EDT
As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. 
 
If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. 
 
Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request.  You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management).  If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support).

Note You need to log in before you can comment on or make changes to this bug.