Someone just pointed out that the change also affected cpio's -p pass-through mode. That was not intentional. I just accepted Martin's pull request to revert the behavior for -p mode.
Cheers, Tim > On May 15, 2016, at 9:16 AM, Ian Lepore <i...@freebsd.org> wrote: > > On Sun, 2016-05-15 at 01:57 +0200, Martin Matuska wrote: >> That switch is "--insecure" and is supported in all libarchive >> versions >> freebsd ever used. >> > > Oh, well that will make handling the new version easier. It doesn't > change the fact that the new libarchive stuff will break long-working > existing software, but at least it'll be easy to fix. > > -- Ian > >> >> On 15.05.2016 01:36, Ngie Cooper (yaneurabeya) wrote: >>>> On May 14, 2016, at 16:29, Martin Matuska <m...@freebsd.org> wrote: >>>> >>>> Ian, we are here talking about cpio, not libarchive. The flag in >>>> libarchive is not active by default. >>>> >>>> On 14.05.2016 22:08, Ian Lepore wrote: >>>>> The real damage will happen to out-of-tree users. I think this >>>>> will >>>>> impact our software updater for $work for example, and it has >>>>> to work >>>>> with both old and new versions of libarchive, and now the new >>>>> version >>>>> will require a flag that the old version will reject as >>>>> unknown. >>>>> >>>>> Ick. >>> Ian’s comment was valid.. cpio doesn’t recognize the new switch on >>> older versions, so something like cpio `cpio --help | grep -- >>> switch && echo switch` would need to be employed everywhere for >>> backwards compatibility — ew. >>> Thanks, >>> -Ngie >> >> _______________________________________________ >> firstname.lastname@example.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to " >> freebsd-current-unsubscr...@freebsd.org" _______________________________________________ email@example.com mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"