Am 13.05.21 um 17:39 schrieb bob prohaska:
> On Thu, May 13, 2021 at 08:13:07AM +0200, Jan Beich wrote:
>>>
>>> Moving to /usr/ports/json-glib and using
>>> make -DBATCH MAKE_JOBS_UNSAFE=yes MAKE_JOBS_NUMBER=4
>>> DISABLE_VULNERABILITIES=yes > make.log
>>> reports several instances of
>>>
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated,
On Fri, May 14, 2021 at 07:29:15PM -0700, Mark Millard wrote:
> bob prohaska fbsd at www.zefox.net wrote on
> Fri May 14 01:35:28 UTC 2021 :
>
> > Would use of poudriere help with this sort of problem?
> > It isn't trivial to configure, but this sort of difficulty
> > has been growing ever worse.
On 2021-May-15, at 16:37, bob prohaska wrote:
> On Fri, May 14, 2021 at 07:29:15PM -0700, Mark Millard wrote:
>> bob prohaska fbsd at www.zefox.net wrote on
>> Fri May 14 01:35:28 UTC 2021 :
>>
>>> Would use of poudriere help with this sort of problem?
>>> It isn't trivial to configure, but
On 15/05/2021 2:35 am, bob prohaska wrote:
On Fri, May 14, 2021 at 12:24:06PM +1000, Kubilay Kocak wrote:
happy to help identify the root cause if you can jump on IRC
(#freebsd-python @ freenode)
If sorting out the conflict between python versions helps the
community in general I'm willing
Something I've not asked about or otherwise referenced
is if you use non-default port options for any of the
ports that you build.
There is:
poudriere options -jmain -c -f ~root/origins/main-origins.txt
or:
poudriere options -jmain -C -f ~root/origins/main-origins.txt
where -c vs. -C is:
