First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 39754
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Alastair Tse (RETIRED) <liquidx@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Alex Holland <ah160@student.cs.york.ac.uk>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 39754 depends on: Show dependency tree
Show dependency graph
Bug 39754 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2004-01-29 06:10 0000 
Just a minor change - /etc/hotplug/usb/bluefw points to /sbin/bluefw to find
the bluefw executable, while the bluefw ebuild puts it in /usr/sbin/bluefw.

Cloney

------- Comment #1 From Alex Holland 2004-02-29 06:01:40 0000 ------- 
I note this is assigned to the kernel team - it's actually just an ebuild
issue. All that needs doing is either amending the config file or making bluefw
install to /sbin instead of /usr/sbin (or using a symlink).

This is a really trivial fix, and bluefw actually doesn't work out of the box
without it. Could someone fix it please?

Cloney

------- Comment #2 From Alastair Tse (RETIRED) 2004-03-28 18:15:09 0000 ------- 
sorry its taken so long, fixed in bluez-bluefw-1.0.ebuild now.
First Last Prev Next    No search results available      Search page      Enter new bug