Bug 13840

Summary: nut was not shipped after libusb was updated
Product: IPFire Reporter: Adolf Belka <adolf.belka>
Component: ---Assignee: Adolf Belka <adolf.belka>
Status: CLOSED NOTABUG QA Contact:
Severity: Major Usability    
Priority: - Unknown -    
Version: 2   
Hardware: all   
OS: Unspecified   

Description Adolf Belka 2025-04-13 18:53:55 UTC 
libusb was updated in CU188 (August 2024).

It was not realised that nut has a dependency on libusb and so nut was not shipped when libusb had been updated.
 now
It was just noticed by someone on the forum.
Comment 1 Adolf Belka 2025-04-13 18:54:35 UTC 
I will submit a patch to ship nut.
Comment 2 Adolf Belka 2025-06-30 15:57:13 UTC 
Obviously dropped off my radar to submit a nut patch.

However in CU196 libusb has had another update and so has nut so when CU196 ships then nut will have been built withy the latest libusb.

https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=8ec17e164807e5232c880b55527412dd83e3cd1a

https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=756f87be320a3ecf770bc16cb51766b8876551a9
Comment 3 Adolf Belka 2025-07-01 09:23:47 UTC 
After questions raised by @ms I have realised the issue was that a regression had occurred in nut which meant that it was linking to libusb-1.0.so instead of to libusb-1.0.so.0 or libusb-1.0.so.0.4.0

libusb-1.0.so is commented out in the rootfile as those are not normally used.

In the nut re3lease 2.8.3 this issue has been fixed again and that version will be in CU196.

This bug will be closed as it is not the cause of the problem that had been experienced.