Date: Sat, 30 Jul 2022 06:41:43 +0900 From: Tatsuki Makino <tatsuki_makino@hotmail.com> To: freebsd-ports <ports@freebsd.org> Subject: Re: make config stopped working Message-ID: <PSAPR03MB5639A4A8199ADEEB0B220FC9FA999@PSAPR03MB5639.apcprd03.prod.outlook.com> In-Reply-To: <3qr83rr0-70s3-6864-6r99-93756222849n@mx.roble.com> References: <B32C5C29-4AD2-47E5-9B6E-AAF8277AFF2C@cs.huji.ac.il> <YuKuOaEsME/futKc@home.opsec.eu> <3qr83rr0-70s3-6864-6r99-93756222849n@mx.roble.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello.
poudriere will work more reliably if the following are written in /usr/local/etc/poudriere.d/make.conf
OPTIONS_SET+=GSSAPI_HEIMDAL
security_ca_root_nss_UNSET+=ETCSYMLINK
To begin with, poudriere options are cumbersome :)
For example, the options created below are used for both of the following:
poudriere options -p $BRANCH -j $FBSDVER $pkgname
# ... option is used for both of the following
poudriere bulk -p $BRANCH -j $FBSDVER $pkgname
poudriere bulk -z $BRANCH -j $FBSDVER $pkgname
Priorities exist, but be sure to check for strange matches.
ls -d /usr/local/etc/poudriere.d/{*-options,options}
Or, poudriere options do not use -j, -p, -z at all.
Regards.
Roger Marquis wrote on 2022/07/30 01:04:
> I have a similar issue with Poudriere:
>
> poudriere options -p $BRANCH -j $FBSDVER $pkgname
>
> If there's an existing options file poudriere exists without calling
> dialog4ports. Workaround so far as been to either maintain options
> outside of poudriere and rsync or edit the poudriere options file
> directly. Perhaps there's a poudriere logging option I'm not familiar
> with?
>
> Roger
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?PSAPR03MB5639A4A8199ADEEB0B220FC9FA999>