You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266771 I had to lock bash with pkg lock -y bash otherwise portmaster would bindly upgrade bash and fail the build. Now when I apply the Bastille template in the middle of the build portmaster asks me interactively how to proceed with the locked port.
Since -i isn't provided and according to --no-confirm it should assume the default value (no) would be used.
Output:
# portmaster -dG -m -s --no-confirm --no-term-title shells/bash
===>>> bash-5.1.16 has an +IGNOREME file or the package is locked
===>>> Update anyway? y/n [n]
# Need to use echo. See https://github.com/freebsd/portmaster/issues/74
CMD echo | env PAGER="/usr/bin/true" portmaster -dG -m -s --no-confirm --no-term-title $(cat /files/software)
I am on Portmaster 3.22 running in a Bastille jail 12.3-RELEASE-p7 on jailhost: FreeBSD 12.3-STABLE 53bc9be1c
My usecase is to automate jail creation with Bastillefiles and one file contains:
Due to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266771 I had to lock bash with
pkg lock -y bash
otherwise portmaster would bindly upgrade bash and fail the build. Now when I apply the Bastille template in the middle of the build portmaster asks me interactively how to proceed with the locked port.Since
-i
isn't provided and according to--no-confirm
it should assume the default value (no) would be used.Output:
This is the section in question:
portmaster/portmaster
Lines 3221 to 3255 in f273c91
The text was updated successfully, but these errors were encountered: