Hello Mark,
I have compared some of errors/warnings with amd64 build logs and they are
present in there too.
I think I found a glitch at the end of arm64 log:
---
[zstd-sys 2.0.1+zstd.1.5.2] running: "ar" "cq" "/wrkdirs/usr/ports...
(...)
"/wrkdirs/usr/ports/editors/lapce/
work/target/aarch64-un
Bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264672
Could someone please commit the updates to the net/phpldapadmin port.
Thanks!
On Nov 24, 2022, at 03:03, Nuno Teixeira wrote:
> Hello Mark,
>
> I have compared some of errors/warnings with amd64 build logs and they are
> present in there too.
>
> I think I found a glitch at the end of arm64 log:
> ---
> [zstd-sys 2.0.1+zstd.1.5.2] running: "ar" "cq" "/wrkdirs/usr/ports.
Hi!
This has been an issue for several weeks(months?) and I'm just getting
around to digging into the issue.
As of 2022-11-24 ~10:00 AM EST if you have /usr/ports made using
portsnap or poudriere tracking main
[root@firewall /usr/local/poudriere/ports/default]# git remote get-url
origin
On Thu, Nov 24, 2022 at 10:22:01AM -0500, Michael Jung wrote:
> ...
> As of 2022-11-24 ~10:00 AM EST if you have /usr/ports made using
> portsnap or poudriere tracking main
> ...
> poudriere:
>
> ===> apache24-2.4.54 : Error from apache.mk. WITH(OUT)_MODULES has been
> removed, use www_apache2
David:
I new that... I guess I'm getting old...
Indeed moving WITHOUT_MODULES to src.conf resolves the issue for both
"Make" and "poudriere".
Having said that this still appears to be an issue with the apache24 check.
Thanks for your quick response. I will be more careful in placing
kernel
Dear port maintainers,
The portscout new distfile checker has detected that one or more
unmaintained 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. Please consider also adopting this po
On Nov 24, 2022, at 07:00, Mark Millard wrote:
> On Nov 24, 2022, at 03:03, Nuno Teixeira wrote:
>
>> Hello Mark,
Hello.
>> I have compared some of errors/warnings with amd64 build logs and they are
>> present in there too.
Interesting.
>> I think I found a glitch at the end of arm64 log: