On Wed, Apr 27, 2016 at 11:21:59AM +0200, Aurelien Jarno wrote: >On 2016-04-26 00:33, Steve McIntyre wrote: >> >> >- local-soname-hack.diff >> >> Can go away easily I think, yes. The old soname should already be >> history now. > >Ok. > >> >- unsubmitted-ldconfig-cache-abi.diff >> >> Should go away after stretch, agreed. >> >> >- unsubmitted-ldso-abi-check.diff >> >- unsubmitted-ldso-multilib.diff >> >> Ummmm. I don't think these two can go away *at all* without breaking >> multi-arch on ARM. >> >> The first one could do with updating to use the new ARM ABI float >> flags in preference to the old, slow ARM attributes scan (as an >> optimisation), but the concept isn't going to change. >> >> The second one is also necessary to deal with finding two different >> float ABIs in the ld.so cache. > >Ok. Do you think these patches can be upstreamed then? Yes, that's the right answer I think. Adam: would you agree? I'll try to find some time to add the flags optimisation for unsubmitted-ldso-abi-check.diff; I doubt upstream will accept it in its current form. We'd then need a local modifier for the no-flags fallback case until we fix our binaries (see below). >> >Could you please ensure that all the binaries in the archive that still >> >needs these patches are rebuilt? >> >> I'll look again for broken/old stuff. I thought you'd already pushed >> binNMUs for everything outstanding, though?? > >I have done that for the local-soname-hack.diff patch. According to my >list the only remaining binaries are the following ones: > > argus-client_2.0.6.fixes.1-3 > cuba_3.0+20111124-2 > icebreaker_1.21-11 > ipkungfu_0.6.1-6 > isakmpd_20041012-7.2 > libprinterconf_0.5-12 > nget_0.27.1-11 My own scan shows the following binaries in unstable this week still needing fixed/removed: argus-client_2.0.6.fixes.1-3_armhf.deb wrong_loader:17 cuba-partview_3.0+20111124-2_armhf.deb wrong_loader:1 icebreaker_1.21-11_armhf.deb wrong_loader:1 nget_0.27.1-11_armhf.deb wrong_loader:2 pconf-detect_0.5-12_armhf.deb wrong_loader:1 so I guess some have been updated/rebuilt/removed since your list. In terms of binaries with FP ABI flags, however, there are still a lot with the flags missing: steve@jack:/mirror/tmp/armhf-check$ grep no_hf_flags sid-summary | wc -l 1016 and (worse) a few with the *wrong* flags: steve@jack:/mirror/tmp/armhf-check$ grep flags_wrong sid-summary cpuburn_1.4a-6_armhf.deb hf_flags_wrong:2 doublecmd-plugins_0.7.1-2_armhf.deb hf_flags_wrong:6 fp-compiler-3.0.0_3.0.0+dfsg-4_armhf.deb hf_flags_wrong:4 fp-ide-3.0.0_3.0.0+dfsg-4_armhf.deb hf_flags_wrong:1 fp-utils-3.0.0_3.0.0+dfsg-4_armhf.deb hf_flags_wrong:28 gearhead_1.300-1_armhf.deb hf_flags_wrong:1 mricron_0.20140804.1~dfsg.1-1_armhf.deb hf_flags_wrong:1 pasdoc_0.14.0-1_armhf.deb hf_flags_wrong:1 (ignoring false positives and noise in u-boot binaries) I'm about to file bugs against these packages to get those fixed. For the rest of the packages without flags at all, we should start binNMUs as well I guess - it'll take a while to churn. I'll grab out a list of source packages for that. I'm attaching my scan output and summaries here too, for both sid and stretch, in case they're useful. -- Steve McIntyre, Cambridge, UK. steve@einval.com "I suspect most samba developers are already technically insane... Of course, since many of them are Australians, you can't tell." -- Linus Torvalds
Attachment:
sid-summary.xz
Description: application/xz
Attachment:
sid.xz
Description: application/xz
Attachment:
stretch-summary.xz
Description: application/xz
Attachment:
stretch.xz
Description: application/xz