Bug 591809

Summary:	Completly remove hal code from rhn-client-tools
Product:	Red Hat Enterprise Linux 6	Reporter:	Miroslav Suchý <msuchy>
Component:	rhn-client-tools	Assignee:	Miroslav Suchý <msuchy>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Sklenar <psklenar>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.0	CC:	psklenar
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	rhn-client-tools-1.0.0-7.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	591798	Environment:
Last Closed:	2010-07-02 19:49:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	591798
Bug Blocks:	564352

Description Miroslav Suchý 2010-05-13 08:23:02 UTC

+++ This bug was initially created as a clone of Bug #591798 +++

Description of problem:
Currently rhn-client prefer python-gudev if presented. If not it will fallback to hal. We want to remove that hal completly. 
We will keep it in git due rhel5, but for Fedora and RHEL6 we will not package it into rpm.

--- Additional comment from msuchy on 2010-05-13 04:21:07 EDT ---

Commited to git as 31eb96a2f9cfa4413b161057f4aa3164fc7dd997

Comment 1 RHEL Program Management 2010-05-13 09:14:37 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 Miroslav Suchý 2010-05-19 15:07:49 UTC

cherrypicked to satellite.git as commit 6b4bd23cc6d2cf512e123aeb22a7807cbc26d367

Comment 5 Petr Sklenar 2010-06-17 12:58:11 UTC

its not in dependency anymore
tried minimal platform, all works as expected

Comment 6 releng-rhel@redhat.com 2010-07-02 19:49:03 UTC

Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.