On 2015/02/11 16:14, Philip Guenther wrote:
> CVSROOT:      /cvs
> Module name:  src
> Changes by:   guent...@cvs.openbsd.org        2015/02/11 16:14:46
> 
> Modified files:
>       bin/pax        : extern.h file_subs.c ftree.c pax.h tables.c 
>                        tables.h 
> 
> Log message:
> Take II, this time without an incorrect mode test.
> For directories whose times or mode will be fixed up in the clean-up pass,
> record their dev+ino and then use open(O_DIRECTORY)+fstat() to verify that
> we're updating the correct directory before using futimens() and fchmod().
> 
> ok sthen@ millert@
> 

Hmm - I'm still seeing the odd "Directory vanished" message on the i386
ports build machines, but not consistently.

This distfile seems particularly likely to trigger it (maybe about 70%
probability), http://mupdf.com/downloads/mupdf-1.6-source.tar.gz

===>  Extracting for mupdf-1.6p1
tar: Directory vanished before restoring mode and times: 
mupdf-1.6-source/thirdparty/zlib
tar: Directory vanished before restoring mode and times: 
mupdf-1.6-source/thirdparty/openjpeg
tar: Directory vanished before restoring mode and times: 
mupdf-1.6-source/thirdparty/mujs
tar: Directory vanished before restoring mode and times: 
mupdf-1.6-source/thirdparty/jpeg
tar: Directory vanished before restoring mode and times: 
mupdf-1.6-source/thirdparty/jbig2dec
tar: Directory vanished before restoring mode and times: 
mupdf-1.6-source/thirdparty/freetype
tar: Directory vanished before restoring mode and times: 
mupdf-1.6-source/thirdparty/curl
*** Error 1 in textproc/mupdf (/usr/ports/infrastructure/mk/bsd.port.mk:2575 
'do-extract': @PATH=/usr/obj/ports/mupdf-1.6/bin:/usr/bin:/bin:...)

Interesting bit: I have so far only been able to trigger it on a filesystem
mounted with softdep....

Reply via email to