libarchive update SVN r299529 breaks "ezjail update"
tim at kientzle.com
Mon May 16 00:44:39 UTC 2016
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.
> On May 15, 2016, at 9:16 AM, Ian Lepore <ian at 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
>> 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 <mm at 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
>>>>> 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
>>>>> will require a flag that the old version will reject as
>>> 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.
>> freebsd-current at freebsd.org mailing list
>> To unsubscribe, send any mail to "
>> freebsd-current-unsubscribe at freebsd.org"
More information about the freebsd-current