Martin Neubauer wrote on 2020/03/01 02:00:
On 01/03/2020 00:29, Miroslav Lachman wrote:
Martin Neubauer wrote on 2020/02/29 23:44:
[...]
But I am talking about "poudriere options" taking different saved
options than "poudriere bulk".
The "poudriere options" does not show me any dialog because they are all
set in "default-php71m103-options" and then "poudriere bulk" ignore
settings in "default-php71m103-options".
That is a bug from my point of view. Both commands should work with the
same set of stored options. Otherwise if "poudriere bulk" wants options
from "11_3_amd64-default-php71m103-options" I am not able to set those
options by calling "poudriere options".
If the issued command lines were in fact those from your earlier mail,
then you did in fact request two different option sets. If you also add
"-j 11_3_amd64" to the "poudriere options" call, you should access the
same option set the "poudriere bulk" run did.
I migrated from "poudriere" to "poudriere-devel" about week ago that's
when I noticed this problem. That's why I suspect poudriere-devel.
Everything worked for me for years with poudriere.
I search my command history and I never called poudriere options with -j
It was like
poudriere options -z php71m103 -p default -c mail/dovecot
graphics/py-pillow www/nginx
poudriere options -z php71m103 -p default -c ports-mgmt/poudriere-devel
poudriere options -z php71m103 -p default -f
/usr/local/etc/poudriere.d/pkglists/php71m103
poudriere bulk -j 11_3_amd64 -z php71m103 -p default -c -f
/usr/local/etc/poudriere.d/pkglists/php71m103
I don't know when / what command exactly created
11_3_amd64-default-php71m103-options in disk.
You are right that anything after that is "expected behaviour", a bit
unexpected to me.
Kind regards
Miroslav Lachman
_______________________________________________
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
