strange pkg upgrade problems

Matthew Seaman matthew at
Fri Jan 23 08:17:16 UTC 2015

On 23/01/2015 07:59, Don Lewis wrote:
> The EPERM errors seem to be kind of random.  If I go and look at the
> "from" file for the rename() using "ls -lo", I see all sorts of random
> flags, like opaque, archive, uunlnk, etc.  I booted single user and ran
> fsck, which came back totally clean.  Then I used chflags -R to clear
> all the flags, did pkg upgrade again, and ran into the exact same
> problems.  If I rerun pkg upgrade, it may fail on the same port again,
> ir it might pick another.  I can go in an manually clear the flags, nuke
> the temporary file that pkg created and upgrade the failed package.  I
> never had that fail.  But running pkg upgrade without specifying a
> package will then fail elsewhere.

This has been fixed in pkg(8) GitHub, and the fix will appear in the
next release (1.4.7) due out within a few days.



Dr Matthew J Seaman MA, D.Phil.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 971 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the freebsd-ports mailing list