ports/171799: astro/py-metar: OptionsNG issue: config options not saved
Craig Leres
leres at ee.lbl.gov
Thu Sep 20 02:00:23 UTC 2012
>Number: 171799
>Category: ports
>Synopsis: astro/py-metar: OptionsNG issue: config options not saved
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Sep 20 02:00:22 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator: Craig Leres
>Release: FreeBSD 8.2-RELEASE amd64
>Organization:
Lawrence Berkeley National Laboratory
>Environment:
System: FreeBSD hot.ee.lbl.gov 8.2-RELEASE FreeBSD 8.2-RELEASE #13: Wed
Jun 13 18:31:18 PDT 2012
leres at hot.ee.lbl.gov:/usr/src/8.2-RELEASE/sys/amd64/compile/LBLIPV6 amd64
>Description:
The py-metar package always fires up the "make config" dialog.
>How-To-Repeat:
This sequence shows the problem:
make config
make
rm -rf work
make
Notice that dialog starts up again and that any options
changed earlier have reverted to their port defaults.
I used ktrace/kdump and found that make is looking in two
different directories for the options file:
ktrace -di make
kdump | fgrep NAMI | fgrep /var/db/ports
11049 make NAMI "/var/db/ports/metar/options"
11049 make NAMI "/var/db/ports/metar/options.local"
11049 make NAMI "/var/db/ports/metar/options"
11049 make NAMI "/var/db/ports/metar/options.local"
11049 make NAMI "/var/db/ports/py27-metar/options"
11069 make NAMI "/var/db/ports/metar/options"
11069 make NAMI "/var/db/ports/metar/options.local"
11069 make NAMI "/var/db/ports/metar/options"
11069 make NAMI "/var/db/ports/metar/options.local"
11069 make NAMI "/var/db/ports/py27-metar/options"
11085 mkdir NAMI "/var/db/ports"
11085 mkdir NAMI "/var/db/ports"
11085 mkdir NAMI "/var/db/ports/py27-metar"
11085 mkdir NAMI "/var/db/ports/py27-metar"
I see other ports that set OPTIONSFILE but I'm not sure if
the problem is with the OptionsNG in py-metar's Makefile
or with OptionsNG itself.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list