ports-mgmt/poudriere-devel does not follow options
I am using Poudriere for a long time. I switched to poudriere-devel few days ago because I want to test ports overlay. I run poudriere options -z php71m103 -p default -f /usr/local/etc/poudriere.d/pkglists/php71m103 just to be sure everything is set. No options dialog appeared because all options was set few week ago on regular update. Now I am running poudriere bulk -j 11_3_amd64 -z php71m103 -p default -c -f /usr/local/etc/poudriere.d/pkglists/php71m103 There were some error on ports like "You are using OpenSSL from ports and have selected GSSAPI from base, please select another GSSAPI value" It is strange because all ports have GSSAPI set to NONE from the beginning. No changes done. I tried to find what is going on and I found that all ports are built with default options instead of what I have stored in /usr/local/etc/poudriere.d/default-php71m103-options Just a wild guess... "poudriere options" read options from default-php71m103-options but "poudriere bulk" are trying to read 11_3_amd64-default-php71m103-options. Is it possible? For example From the log of cyrus-sasl built few weeks ago: ---Begin OPTIONS List--- ===> The following configuration options are available for cyrus-sasl-2.1.27: ALWAYSTRUE=off: Alwaystrue password verifier (discouraged) AUTHDAEMOND=on: Use of authdaemon DOCS=off: Build and/or install documentation KEEP_DB_OPEN=off: Keep handle to Berkeley DB open OBSOLETE_CRAM_ATTR=off: cmusaslsecretCRAM-MD5 auxprop property OBSOLETE_DIGEST_ATTR=on: cmusaslsecretDIGEST-MD5 auxprop property > Options available for the group PLUGIN ANONYMOUS=off: ANONYMOUS authentication CRAM=off: CRAM-MD5 authentication DIGEST=off: DIGEST-MD5 authentication LOGIN=on: LOGIN authentication NTLM=off: NTLM authentication OTP=off: OTP authentication PLAIN=on: PLAIN authentication SCRAM=off: SCRAM authentication > SASLdb auxprop plugin: you can only select none or one of them BDB1=on: Berkeley DB 1.85 support BDB=off: Berkeley DB support GDBM=off: GNU dbm library support LMDB=off: OpenLDAP Lightning Memory-Mapped Database support ===> Use 'make config' to modify these settings ---End OPTIONS List--- From the log of cyrus-sasl built today ---Begin OPTIONS List--- ===> The following configuration options are available for cyrus-sasl-2.1.27: ALWAYSTRUE=off: Alwaystrue password verifier (discouraged) AUTHDAEMOND=on: Use of authdaemon DOCS=off: Build and/or install documentation KEEP_DB_OPEN=off: Keep handle to Berkeley DB open OBSOLETE_CRAM_ATTR=on: cmusaslsecretCRAM-MD5 auxprop property OBSOLETE_DIGEST_ATTR=on: cmusaslsecretDIGEST-MD5 auxprop property > Options available for the group PLUGIN ANONYMOUS=on: ANONYMOUS authentication CRAM=on: CRAM-MD5 authentication DIGEST=on: DIGEST-MD5 authentication LOGIN=on: LOGIN authentication NTLM=on: NTLM authentication OTP=on: OTP authentication PLAIN=on: PLAIN authentication SCRAM=on: SCRAM authentication > SASLdb auxprop plugin: you can only select none or one of them BDB1=on: Berkeley DB 1.85 support BDB=off: Berkeley DB support GDBM=off: GNU dbm library support LMDB=off: OpenLDAP Lightning Memory-Mapped Database support ===> Use 'make config' to modify these settings ---End OPTIONS List--- Both built with the same commands (the same poudriere options & poudriere bulk) 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"
Re: ports-mgmt/poudriere-devel does not follow options
On 28/02/2020 17:20, Miroslav Lachman wrote: > I am using Poudriere for a long time. I switched to poudriere-devel few > days ago because I want to test ports overlay. > I run > poudriere options -z php71m103 -p default -f > /usr/local/etc/poudriere.d/pkglists/php71m103 > just to be sure everything is set. No options dialog appeared because > all options was set few week ago on regular update. > > Now I am running > poudriere bulk -j 11_3_amd64 -z php71m103 -p default -c -f > /usr/local/etc/poudriere.d/pkglists/php71m103 [snip] > I tried to find what is going on and I found that all ports are built > with default options instead of what I have stored in > /usr/local/etc/poudriere.d/default-php71m103-options > > Just a wild guess... "poudriere options" read options from > default-php71m103-options but "poudriere bulk" are trying to read > 11_3_amd64-default-php71m103-options. > Is it possible? It isn't such a wild guess at all, considering that documentation does state that the most specific set of options gets used with higher priority. More details at: https://github.com/freebsd/poudriere/wiki/poudriere.8-devel#custom--build-options signature.asc Description: OpenPGP digital signature
Re: ports-mgmt/poudriere-devel does not follow options
Martin Neubauer wrote on 2020/02/29 23:44: On 28/02/2020 17:20, Miroslav Lachman wrote: I am using Poudriere for a long time. I switched to poudriere-devel few days ago because I want to test ports overlay. I run poudriere options -z php71m103 -p default -f /usr/local/etc/poudriere.d/pkglists/php71m103 just to be sure everything is set. No options dialog appeared because all options was set few week ago on regular update. Now I am running poudriere bulk -j 11_3_amd64 -z php71m103 -p default -c -f /usr/local/etc/poudriere.d/pkglists/php71m103 [snip] I tried to find what is going on and I found that all ports are built with default options instead of what I have stored in /usr/local/etc/poudriere.d/default-php71m103-options Just a wild guess... "poudriere options" read options from default-php71m103-options but "poudriere bulk" are trying to read 11_3_amd64-default-php71m103-options. Is it possible? It isn't such a wild guess at all, considering that documentation does state that the most specific set of options gets used with higher priority. More details at: 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". 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"
Re: ports-mgmt/poudriere-devel does not follow options
On 01/03/2020 00:29, Miroslav Lachman wrote: > Martin Neubauer wrote on 2020/02/29 23:44: >> >> >> On 28/02/2020 17:20, Miroslav Lachman wrote: >>> I am using Poudriere for a long time. I switched to poudriere-devel few >>> days ago because I want to test ports overlay. >>> I run >>> poudriere options -z php71m103 -p default -f >>> /usr/local/etc/poudriere.d/pkglists/php71m103 >>> just to be sure everything is set. No options dialog appeared because >>> all options was set few week ago on regular update. >>> >>> Now I am running >>> poudriere bulk -j 11_3_amd64 -z php71m103 -p default -c -f >>> /usr/local/etc/poudriere.d/pkglists/php71m103 >> >> [snip] >> >>> I tried to find what is going on and I found that all ports are built >>> with default options instead of what I have stored in >>> /usr/local/etc/poudriere.d/default-php71m103-options >>> >>> Just a wild guess... "poudriere options" read options from >>> default-php71m103-options but "poudriere bulk" are trying to read >>> 11_3_amd64-default-php71m103-options. >>> Is it possible? >> It isn't such a wild guess at all, considering that documentation does >> state that the most specific set of options gets used with higher >> priority. More details at: > > 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. Good luck, Martin signature.asc Description: OpenPGP digital signature
Re: ports-mgmt/poudriere-devel does not follow options
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"
Re: ports-mgmt/poudriere-devel does not follow options
On 01/03/2020 10:06, Miroslav Lachman wrote: > 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. I admit that's looking odd, but even if the exact command that led to the presence of that directory can't be reconstructed, it should at least be possible to gather some information regarding the time that happened. "ls -lU" should give at least some starting point. signature.asc Description: OpenPGP digital signature
