Re: r313938 breaks portsnap

From: Ben Woods <woodsb02_at_gmail.com>
Date: Tue, 21 Feb 2017 23:44:51 +0000
On Tue, 21 Feb 2017 at 10:44 pm, Vladimir Zakharov <zakharov.vv_at_gmail.com>
wrote:

> Hello
>
> After recent upgrade portsnap doesn't work anymore:
>
> # portsnap fetch update
> Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
> Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done.
> Fetching snapshot metadata... done.
> Updating from Tue Feb 21 16:05:39 MSK 2017 to Tue Feb 21 16:59:30 MSK 2017.
> Fetching 5 metadata patches.lam: unable to limit stdio: Capabilities
> insufficient
>  done.
> Applying metadata patches... done.
> Fetching 5 metadata files... lam: unable to limit stdio: Capabilities
> insufficient
> /usr/sbin/portsnap: cannot open
> 8c94d2c3f8fcea20eb1fd82021566c99c63a010e6b3702ee11e7a491795bcfb8.gz: No
> such file or directory
> metadata is corrupt.
>
> Reverting r313938 fixes the problem.



As it wasn't immediately clear to me:

The r313938 being referred to is the change to base to capsicumize lam(1).

https://svnweb.freebsd.org/base?view=revision&revision=313938

Regards,
Ben

-- 

--
From: Benjamin Woods
woodsb02_at_gmail.com
Received on Tue Feb 21 2017 - 22:45:02 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:10 UTC