Bug 180924 - ports-mgmt/poudriere does not write changed port config
Summary: ports-mgmt/poudriere does not write changed port config
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Bryan Drewery
URL:
Keywords:
Depends on:
Blocks: 214775 214979
  Show dependency tree / graph
 
Reported: 2013-07-29 14:10 UTC by bartsch
Modified: 2018-01-24 19:55 UTC (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description bartsch 2013-07-29 14:10:00 UTC 
I'm not able to change any port option by running "poudriere options -c -p ..."
The config dialog shows up and I'm able to change options. But these changed options never get honoured (poudriere version: 3.0.4).
They are not being saved to /usr/local/etc/poudriere.d/<portstree>-options/<uniquename>.

How-To-Repeat: poudriere options -c -p <portstree> catergory/port
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2013-07-29 14:10:09 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->bapt

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2014-03-29 04:27:04 UTC 
Responsible Changed
From-To: bapt->bdrewery

Over to new maintainer.
Comment 3 G. Paul Ziemba 2014-07-28 16:53:36 UTC 
I am seeing the same issue in 3.0.16.

In my case, the problem arises from the different methods used to compute the options directory for "poudriere bulk" vs. "poudriere options". In each case, a different options directory was used, so the options set with the "options" command did not affect the options used by "bulk".

I believe the correct way to fix this problem is to use a common routine to compute the options directory in all cases.

In the meantime, I am able to work around the problem by setting OPTIONS_SET_FORCE conditionally in the appropriate make.conf
Comment 4 O. Hartmann 2016-12-05 11:43:11 UTC 
Probably this bug Bug 214775 is also related in a way to this issue.
Comment 5 Walter Schwarzenfeld 2018-01-14 04:03:03 UTC 
I think this is solved (have no problems with options) and could be closed.
Comment 6 Bryan Drewery freebsd_committer freebsd_triage 2018-01-24 19:55:34 UTC 
Haven't had issues like this reported in years.