On 02/12/2012 08:26, Ion-Mihai Tetcu wrote: > BTW, I'm seeing this on my machines: > Checking timestamps on options makefiles: cache-update: WARNING unknown > options file "/var/db/ports/rsync/options" -- ignored > cache-update: WARNING unknown options file "/var/db/ports/subversion/options" > -- ignored > cache-update: WARNING unknown options file "/var/db/ports/apr/options" -- > ignored > cache-update: WARNING unknown options file "/var/db/ports/python27/options" > -- ignored > cache-update: WARNING unknown options file "/var/db/ports/m4/options" -- > ignored > cache-update: WARNING unknown options file "/var/db/ports/help2man/options" > -- ignored > cache-update:1: Checking for category changes at www > ....
This should be harmless and should only report leftovers from removed
ports or ports that have changed where they keep their options data.
However rsync, subversion, m4, help2man at least are all very much live
ports. Not sure exactly what is happening there. I suggest re-running
cache-init and see if the problem goes away.
> # cat /var/db/ports/rsync/options
> # This file is auto-generated by 'make config'.
> # Options for rsync-3.0.9_2
> _OPTIONS_READ=rsync-3.0.9_2
> _FILE_COMPLETE_OPTIONS_LIST=ACL ATIMES FLAGS ICONV POPT_PORT RENAMED SSH
> TIMELIMIT
> OPTIONS_FILE_UNSET+=ACL
> OPTIONS_FILE_UNSET+=ATIMES
> OPTIONS_FILE_UNSET+=FLAGS
> OPTIONS_FILE_UNSET+=ICONV
> OPTIONS_FILE_UNSET+=POPT_PORT
> OPTIONS_FILE_SET+=RENAMED
> OPTIONS_FILE_SET+=SSH
> OPTIONS_FILE_UNSET+=TIMELIMIT
>
> Any hints? Is it the fact that it's in the OPTIONSng format?
If you're running 2.9 OPTIONSng should be handled correctly. It doesn't
matter much: the exact format of the OPTIONS variables doesn't make much
difference to building the INDEX, only detecting when they've been changed.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
JID: matt...@infracaninophile.co.uk
signature.asc
Description: OpenPGP digital signature
