RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1362658 - sensors-detect version and date string missing
Summary: sensors-detect version and date string missing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lm_sensors
Version: 7.3
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Martin Sehnoutka
QA Contact: Rachel Sibley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-02 19:09 UTC by Rachel Sibley
Modified: 2016-11-04 06:39 UTC (History)
2 users (show)

Fixed In Version: lm_sensors-3.4.0-4.20160601gitf9185e5.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 06:39:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2450 0 normal SHIPPED_LIVE lm_sensors bug fix update 2016-11-03 14:03:53 UTC

Description Rachel Sibley 2016-08-02 19:09:42 UTC
Description of problem:
With the latest lm_sesors rpm, I'm seeing an usual version string of 'lm_sensors-3.4.0-2.20160601gitf9185e5.el7.x86_64',
also when you run sensors-detect the date and version are missing from the beginning output, instead you will see $REVISION$
printed.

Version-Release number of selected component (if applicable):
lm_sensors-3.4.0-2.20160601gitf9185e5.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. yum install lm_sensors
2. rpm -q lm_sensors
3. sensors-detect

Actual results:
# rpm -q lm_sensors
lm_sensors-3.4.0-2.20160601gitf9185e5.el7.x86_64
# sensors-detect
# sensors-detect revision $Revision$
....

Expected results:
rpm -q lm_sensors
lm_sensors-3.4.0-2.el7.x86_64
~]# sensors-detect
# sensors-detect revision 6170 (2013-05-20 21:25:22 +0200)
....

Additional info:

Comment 6 Rachel Sibley 2016-09-07 14:13:40 UTC
ALL TESTS PASSED

Version string is now printed correctly in the lm_sensors-3.4.0-4.20160601gitf9185e5.el7 version using sensors-detect

~]# rpm -q lm_sensors
lm_sensors-3.4.0-4.20160601gitf9185e5.el7.x86_64

~]# sensors-detect
# sensors-detect revision 3.4.0-4 (2016-06-01)
# System: Dell Inc. PowerEdge R510
# Board: Dell Inc. 0W844P
# Kernel: 3.10.0-501.el7.x86_64 x86_64
# Processor: Intel(R) Xeon(R) CPU X5550 @ 2.67GHz (6/26/5)

Comment 8 errata-xmlrpc 2016-11-04 06:39:08 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2450.html


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