Re: Poudriere: when fetching a package with porttree from a git source, the generation of logs is slow

On 4/11/26 08:06, Roger Marquis wrote:
> On Thu, 9 Apr 2026, Mark Millard wrote:
>> My understanding was that when the ports tree ( /usr/ports/ above ) does
>> not match the upstream version that can be fetched, including for any
>> dependency mismatches or option mismatches ...
> 
> Is this new behavior for 'make fetch'?  Asking because we recently have
> had a relatively large number of poudriere fetch failures, most without
> sufficient logging of the cause.  As we reuse /usr/ports/distfiles
> across architectures and versions it would be helpful if these
> intentional but unnecessary conditional failures could be overridden.
> 
> Roger Marquis
> 
> 

poudriere has  no way of keeping the build coherent unless it follows
such rules --and with its existing rules may not always be able to do so.

(Note, poudriere-devel context used:)
poudriere bulk-s -b documentation in the poudriere-bulk man page reports:

QUOTE
              poudriere will only use packages that:
              •   come from a repository having the same or older version of
                  pkg.
              •   do not have a locally fetched package already.
              •   are not IGNORED.
              •   match the expected local version.
              •   match the expected ABI.
              •   match the expected runtime and library dependencies.
              •   match the expected OPTIONS when CHECK_CHANGED_OPTIONS is
                  enabled (default: on).
              •   is NOT listed in PACKAGE_FETCH_BLACKLIST.
              •   is NOT listed with -C, or -c, when -t is used.
              The -v flag can be used to show these decisions during build.
              Specifing twice will show more details on why some are
skipped.


              WARNING: poudriere has no way of determining differences
outside
              of the above list.  That is, if the local ports framework, or
              port, has custom patches or special WITH_FOO knobs (not
OPTIONS)
              then it is required to add its name into
              PACKAGE_FETCH_BLACKLIST.  Otherwise a package may be
fetched and
              used that lacks the custom patch or knob.

              See PACKAGE_FETCH_BRANCH, PACKAGE_FETCH_URL,
              PACKAGE_FETCH_BLACKLIST, and PACKAGE_FETCH_WHITELIST in
              poudriere.conf.sample.  The entries in the lists will be
matched
              against package names without versions.
END QUOTE

-- 
===
Mark Millard
marklmi at yahoo.com