On Fri, Jan 23, 2015 at 08:16:46AM +0000, Matthew Seaman wrote: > 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. > > https://github.com/freebsd/pkg/commit/93d1647d0b986e4c6ad317c4e96886784477dcfe
No, I don't think it has been fixed. The bug is here: https://github.com/freebsd/pkg/issues/1151 Looks like it still needs a bit more work. Tim. -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x6C226B37FDF38D55 _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
