Please drop hal dependency
Bug #708502 reported by
Martin Pitt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Client |
Fix Released
|
High
|
Thomas Herve | ||
landscape-client (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Karmic |
Won't Fix
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned | ||
Maverick |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: landscape-client
HAL has been deprecated and totally unsupported for several years now. landscape-client is one of the very few packages which still depend on it, and keep it in main.
It should be dropped, and hardware info should be taken from sysfs and libudev. There are gobject-
Thanks!
Related branches
lp:~therve/landscape-client/hal-soft-dep
- Jamu Kakar (community): Approve
- Free Ekanayaka (community): Approve
-
Diff: 243 lines (+91/-14)8 files modifieddebian/control (+2/-2)
debian/landscape-client.init (+2/-2)
debian/rules (+10/-4)
landscape/monitor/hardwareinventory.py (+11/-2)
landscape/monitor/mountinfo.py (+29/-2)
landscape/monitor/tests/test_mountinfo.py (+30/-0)
landscape/monitor/tests/test_service.py (+1/-0)
landscape/service.py (+6/-2)
Changed in landscape-client (Ubuntu): | |
importance: | Undecided → High |
Changed in landscape-client: | |
assignee: | nobody → Thomas Herve (therve) |
Changed in landscape-client (Ubuntu): | |
status: | New → Triaged |
Changed in landscape-client: | |
status: | New → In Progress |
Changed in landscape-client: | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done removed: verification-needed |
Changed in landscape-client: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Martin and I talked about it. The proposed idea of making 'hal' a
'Suggests' and conditionally enabling the hardware plugin if HAL is
available sounds like the best path forward until we have the time to
migrate to something better (udev, for example).
<jkakar> pitti: We're just talking about what to do about the HAL dependency in landscape-client. /launchpad. net/bugs/ 708502
Re: bug #708502
<ubottu> Launchpad bug 708502 in landscape-client (Ubuntu) "Please drop hal dependency" [High,New] https:/
<jkakar> pitti: We don't really have the time/capacity to migrate to udev right now.
pitti: We're wondering about making hal a 'Suggests', so that the client can be installed without it, and making some tweaks to the code so it won't blow up if HAL isn't there.
pitti: The question is, will the hal package be moving to universe?
<pitti> jkakar: I was actually quite surprised that it still used it; I thought we already talked about it many years ago
jkakar: I hope that we can move it to universe in natty or n+1
<jkakar> pitti: We did, we just haven't made time for it... too many bigger fires to deal with. :(
<persia> Riddell, Looks like upstream 1.1 is out, but still has the dependency on HAL, and I don't see any halsectomy related items on the 1.2 roadmap. qtmobility can be compiled to not use HAL, with "reduced functionality". I don't know of anyone actively using these APIs though, so I'd be tempted to compile with the reduced functionality (unless you know a user my apt-cache isn't finding).
<jkakar> pitti: Okay, so there's a chance it won't make it for natty.
<pitti> persia: it's not a compile-time thing; it only talks to the dbus interface
<persia> pitti, Is there a reason to move to universe, or can we just drop it?
<jkakar> pitti: I guess very few packages actually use it, right?
<pitti> persia: i. e. simply runtime
<persia> pitti, There's a compile-time option to tell it not to ask DBus about HAL.
(or else I'm reading the docs wrong)
<pitti> jkakar: it's qtmobility and landscape-client, the rest was fixed or will be in the next days
<pitti> persia: right, but ideally it would just fail gracefully if hal isn't running (I haven't checked)
<pitti> jkakar: out of interest, what do you use it for?
<jkakar> I suppose one option for us is to make hal a Suggests and do a conditional import... if hal is unavailable (because the package is gone entirely) the hardware inventory will be simply unavailable.
pitti: We pull the entire HAL device tree and send it to the server. We provide a view of that data to our users.
<pitti> jkakar: is that merely for display purposes, or do you actually do something with the data?
<jkakar> pitti: Honestly, the functionality we have isn't so useful.
pitti: Merely for display purposes.
pitti: But we don't have the time to replace it with something better right now, so we're trying to figure out how to keep it working if possible.
<pitti> jkakar: the hal tree is by and large the sysfs tree
<jkakar> pitti: True.
<pitti> an udevadm info --export-db usually gives enough info about the hardware, at least in the bugs that I am looking into
<jkakar> pitti: One issue is that udev provides really crappy data on <lucid.
...