Thorsten Schoel reported this a while ago at Launchpad:
"Since the update to 0.5.9 in feisty-backports hal does no longer accept fdi files which contain a merge with type="uint64". Such files are simply ignored. Usually this is not a problem since hal (i.e. hal-info in 0.5.9) doesn't come with any such fdi files but it potentially makes the use of certain user provided fdi files impossible (as in my case). Downgrading to 0.5.8.1 solved the problem for me."
After I asked him whether the bug was still present in the latest version he told me that he could still reproduce it.
He provided this example file:
<?xml version="1.0" encoding="UTF-8"?>
<match key="@info.parent:storage.cdrom.cdr" bool="true">
<match key="block.is_volume" bool="true">
<merge key="foo" type="string">foo</merge>
<merge key="bar" type="uint64">12345</merge>
Removing the uint64 merge makes HAL detect the fdi file again.
The Launchpad bug report: https://bugs.launchpad.net/ubuntu/+source/hal/+bug/116264
The latest version of HAL in Ubuntu is 0.5.11~rc2-1ubuntu8.1
Created attachment 17474 [details] [review]
fix for the bug
Without any deeper test.
I really don't understand why the Ubuntu guys (always) report such trivial bugs upstream without fixing them while you are able to confirm the bug. Sorry, but this behavior leaves bad karma!
(In reply to comment #2)
> I really don't understand why the Ubuntu guys (always) report such trivial bugs
> upstream without fixing them while you are able to confirm the bug. Sorry, but
> this behavior leaves bad karma!
I think that was my fault. I triaged the bug and reported it upstream after it was confirmed. I'm not a developer by myself, so I didn't (have the time to) look if I could find the cause. I'm just a Bug Triager. ;)
Anyway, thank you for the fast response. I'll ask if someone can test this patch.
The path has been tested and it works. It's not a very complex patch, so it isn't a surprise, but I thought it would be good to let you know.
Commited patch to git master.