Hello Maitland, * Chris Hofstaedtler <z...@debian.org> [231205 20:01]: > * Maitland Bottoms <m...@rf.org> [231203 14:57]: > > Helmut Grohne <hel...@subdivi.de> writes: > > > Then when you retry it, please go for experimental first. Then have > > > Chris or me check your upload is ok and only then proceed with uploading > > > to unstable. > > > > hackrf_2023.01.1-6 now in experimental is the retry with upstream > > updates and the udev rules handling.
As Helmut already wrote, hackrf_2023.01.1-6 is good and can go to unstable. Thanks! > Do you think you could upload the other packages (rtl-sdr, > bladerf, libmirisdr, libiio, libosmosdr) to experimental soon, too? I checked these: * bladerf 0.2023.02-3 * libiio 0.25-2 * libmirisdr 0.0.4.59ba37-6 * libosmosdr 0.1.8.effcaa7-8 And they are all good and can go to unstable. rtl-sdr 2.0.1-1 is a bit different. librtlsdr changed its soname to librtlsdr2. With the soname and package name change, the udev rules also changed their name (to 60-librtlsdr2.rules). In this case, the protective diversions are unnecessary, _if_ the rules file always gets installed into /usr/lib, _and_ librtlsdr2 never gets introduced in bookworm or earlier. So, you have this choice: 1) librtlsdr2 is exclusive to trixie and newer, then you can drop the postinst/preinst/postrm fragments 2) you want the option of having librtlsdr2 in bookworm(-backports) or earlier, then you need to keep these fragments. Anyway, from my PoV it can also go into unstable now. Please upload these packages to unstable soon, so we can proceed with the udev migration. Thanks, Chris
