This is a tracking bug for Change: Rename libusb packages and deprecate old API For more details, see: https://fedoraproject.org/wiki/Changes/Rename_libusb_packages_and_deprecated_old_api Rename libusb to libusb-compat-0.1 and libusbx to libusb1. Do not provide an automated update path for the old libusb build dependency as packages should–and likely can–be updated to use libusb1.
Today we reached the Completion deadline (testable) milestone in the Fedora schedule. All approved changes should be in a testable state. If you change is testable, please indicate this by setting the status to MODIFIED. If you need to defer the change to Fedora 35 or withdraw the change entirely, please indicate this in a comment and NEEDINFO bcotton. The 100% code complete deadline is Tuesday 23 February. By that date, your change should be fully implemented and the tracking bug set to ON_QA. For other Fedora 34 milestones, see https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html
I have created packages and they are available in a copr repository for them. Currently the migration is pending on repository creation in order to upload the packages under the new name. As such, I think this complies to the requirements of the "testable" state.
Reminder: The change complete (100% complete) deadline for Fedora 34 changes is Tuesday 23 February. At that point, changes should be 100% code complete, along with supporting documentation where appropriate. Please indicate this by setting the tracker bug for your change to ON_QA.
Today is the change complete (100% complete) deadline for Fedora 34 changes. At this point, changes should be 100% code complete, along with supporting documentation where appropriate. Please indicate this by setting the tracker bug for your change to ON_QA. If you need to defer this change to Fedora 35, please set the version to 'rawhide'. As a reminder, the Beta freeze is now in effect.
This has been fixed in rawhide. However, due to delays with unretireing the old libusb1 package (I asked for the wrong thing), it will only be partially happen in F34. For F34, my plan is to still do the package renames, but I'll leave out the parts that might break existing packages (most of which should update their build dependencies). So, I depending on how one sees this, I suppose this issue can be changed to CLOSED, RAWHIDE.
Are the F34 parts done? If not, let's just push this to F35 in its entirety.
The change is completed in F35. For F34, what is needed is to submit the packages to build and update. I have not done so purely because the deadline has passed and we are in beta freeze now.
Do you intend to do that and file a freeze exception to get it into the Beta? If not, I'll adjust this to be an F35 change as we probably shouldn't introduce it after the Beta.
Setting to ON_QA for F35 per comment 7
F35 was released today. Closing the trackers.