Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 225135 - Include hal support in exo
Summary: Include hal support in exo
Alias: None
Product: Fedora
Classification: Fedora
Component: exo
Version: 6
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: 225083
TreeView+ depends on / blocked
Reported: 2007-01-29 10:11 UTC by Sebastian Vahl
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version: 3.2-2.fc7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-02-09 05:46:32 UTC

Attachments (Terms of Use)

Description Sebastian Vahl 2007-01-29 10:11:01 UTC
Description of problem: exo is compiled without supporting hal. thunar-volman
(atm not included in extras) does requires this.

Version-Release number of selected component (if applicable): 0.3.2-1

Additional info: Simple adding "BuildRequires: hal-devel" does the job. No
further changes are needed.

Comment 1 Kevin Fenzi 2007-01-30 05:53:58 UTC
Thanks for the bug report. I'm working on pushing out a fixed package. 
It seems that gtk-doc is broken in devel, so I am trying to work around that. 
In any case a fc6 update should be out before long. 

Comment 2 Kevin Fenzi 2007-01-30 21:35:03 UTC
I've pushed out an updated package with hal support for fc6. 
devel has gtk-doc issues currently, so I will wait and rebuild that once that
issue is fixed. 

If you would like to test an unsigned package, one is available at:

Comment 3 Sebastian Vahl 2007-02-01 10:01:00 UTC
(In reply to comment #2)
> If you would like to test an unsigned package, one is available at: 

i386-package works fine. Thanks.

Comment 4 Kevin Fenzi 2007-02-09 05:46:32 UTC
gtk-doc is all fixed in devel now, so I have pushed out a fixed exo there as
well. It should be in the next push. 

If you spot any problems with it, feel free to reopen this bug, or file a new one. 

Thanks again for the bug report. 

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