Re: poudriere-devel: ldconfig: warning: /lib32: No such file or directory
Hello, I'm trying to find where ldconfig patch is set. `ldconfig -32 -r` shows: /var/run/ld-elf32.so.hints: search directories: /usr/lib32 (...) And default values for rc.conf is: ldconfig32_paths="/usr/lib32 /usr/lib32/compat" I'm I missing something on where /lib32 path could be fixed? Thanks, Konstantin Belousov escreveu no dia quarta, 15/11/2023 à(s) 23:25: > On Wed, Nov 15, 2023 at 09:34:38PM +, Nuno Teixeira wrote: > > Hello all, > > > > Just updated poudriere jail to 2a4897bd (newer than host 14c2e0a0) and I > > spoted: > > > > poudriere-devel-3.4.99.20231113: > > --- > > [00:00:00] Starting jail 15amd64-main > > [00:00:00] Will build as nobody:nobody (65534:65534) > > ldconfig: warning: /lib32: No such file or directory > > --- > > > > No building problems. > > Any clues? > > This is innocent warning because /lib32 is included into ld-elf32.so.1 > default search path. Caused by 99132daf6f70cb0cc969c555d3612547fa3cf1db. > > Best fix is to remove /lib32 from the ld-elf32.so.1 path, but the realistic > change is to filter non-existing dirs in ldconfig script. > -- Nuno Teixeira FreeBSD Committer (ports)
Re: poudriere-devel: ldconfig: warning: /lib32: No such file or directory
On Mon, Nov 20, 2023 at 09:01:20AM +, Nuno Teixeira wrote: > Hello, > > I'm trying to find where ldconfig patch is set. > > `ldconfig -32 -r` shows: > /var/run/ld-elf32.so.hints: > search directories: /usr/lib32 > (...) > > And default values for rc.conf is: > ldconfig32_paths="/usr/lib32 /usr/lib32/compat" > > I'm I missing something on where /lib32 path could be fixed? libexec/rtld-elf/rtld_paths.h > > Thanks, > > Konstantin Belousov escreveu no dia quarta, > 15/11/2023 à(s) 23:25: > > > On Wed, Nov 15, 2023 at 09:34:38PM +, Nuno Teixeira wrote: > > > Hello all, > > > > > > Just updated poudriere jail to 2a4897bd (newer than host 14c2e0a0) and I > > > spoted: > > > > > > poudriere-devel-3.4.99.20231113: > > > --- > > > [00:00:00] Starting jail 15amd64-main > > > [00:00:00] Will build as nobody:nobody (65534:65534) > > > ldconfig: warning: /lib32: No such file or directory > > > --- > > > > > > No building problems. > > > Any clues? > > > > This is innocent warning because /lib32 is included into ld-elf32.so.1 > > default search path. Caused by 99132daf6f70cb0cc969c555d3612547fa3cf1db. > > > > Best fix is to remove /lib32 from the ld-elf32.so.1 path, but the realistic > > change is to filter non-existing dirs in ldconfig script. > > > > > -- > Nuno Teixeira > FreeBSD Committer (ports)
Re: PYTHON_DEFAULT needs to be bumped to at least 3.10, or to the latest 3.12
Charlie Li wrote: > The next bump will be to 3.11, in keeping with the n-1 cadence. 3.12 is not > ready yet, not without the setuptools overhaul amongst other things. Just out of curiosity: does a time schedule exist, yet? Regards, Michael
misc/freebsd-release-manifests is broken
Hi, after the 14.0 release announcement, port misc/freebsd-release-manifests is broken, due to legacy 'RC4' references: ===> Building package for freebsd-release-manifests-20231120 pkg-static: Unable to access file /wrkdirs/usr/ports/misc/freebsd-release-manifests/work/stage/usr/local/share/freebsd/MANIFESTS/amd64-amd64-14.0-RC4:No such file or directory pkg-static: Unable to access file /wrkdirs/usr/ports/misc/freebsd-release-manifests/work/stage/usr/local/share/freebsd/MANIFESTS/arm64-aarch64-14.0-RC4:No such file or directory pkg-static: Unable to access file /wrkdirs/usr/ports/misc/freebsd-release-manifests/work/stage/usr/local/share/freebsd/MANIFESTS/i386-i386-14.0-RC4:No such file or directory pkg-static: Unable to access file /wrkdirs/usr/ports/misc/freebsd-release-manifests/work/stage/usr/local/share/freebsd/MANIFESTS/powerpc-powerpc-14.0-RC4:No such file or directory pkg-static: Unable to access file /wrkdirs/usr/ports/misc/freebsd-release-manifests/work/stage/usr/local/share/freebsd/MANIFESTS/powerpc-powerpc64-14.0-RC4:No such file or directory pkg-static: Unable to access file /wrkdirs/usr/ports/misc/freebsd-release-manifests/work/stage/usr/local/share/freebsd/MANIFESTS/powerpc-powerpc64le-14.0-RC4:No such file or directory pkg-static: Unable to access file /wrkdirs/usr/ports/misc/freebsd-release-manifests/work/stage/usr/local/share/freebsd/MANIFESTS/powerpc-powerpcspe-14.0-RC4:No such file or directory pkg-static: Unable to access file /wrkdirs/usr/ports/misc/freebsd-release-manifests/work/stage/usr/local/share/freebsd/MANIFESTS/riscv-riscv64-14.0-RC4:No such file or directory *** Error code 1 Regards, Michael
Re: misc/freebsd-release-manifests is broken
On 11/20/23 14:05, Michael Grimm wrote: after the 14.0 release announcement, port misc/freebsd-release-manifests is broken, due to legacy 'RC4' references: Thanks, I forgot to update the plist when I updated the MANIFEST files. Should be fixed now. -- Colin Percival FreeBSD Release Engineering Lead & EC2 platform maintainer Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
Re: misc/freebsd-release-manifests is broken
Colin Percival wrote > On 11/20/23 14:05, Michael Grimm wrote: >> after the 14.0 release announcement, port misc/freebsd-release-manifests is >> broken, due to legacy 'RC4' references: > > Thanks, I forgot to update the plist when I updated the MANIFEST files. > Should be fixed now. Confirmed. Thanks for the ultrafast fix. Regards, Michael
Re: a list of the ABI which get built?
On Nov 19, 2023, at 23:17, Mark Millard wrote: > Dan Langille wrote on > Date: Sun, 19 Nov 2023 20:59:16 UTC : > >> Is there a list of the ABI which get built? >> >> For example, the last time FreeBSD:12:aarch64 was updated is: Oct 11 2018 - >> clearly not active. >> >> It would be helpful to me to have a list the ABI which the build farm >> actively builds. >> >> Thank you. >> >> Background, no need to read it: >> https://github.com/FreshPorts/freshports/issues/449 > > Quarterly is still built and updated for 12.4 aarch64: > > http://ampere1.nyi.freebsd.org/data/124arm64-quarterly/6687a67ae6e0/logs/git-2.42.0.log > > (note the "124arm64-quarterly", so 12.4 aarch64 quarterly) reports: > > =>> Building devel/git > build started at Sun Oct 22 06:01:50 UTC 2023 > port directory: /usr/ports/devel/git > package name: git-2.42.0 > building for: FreeBSD 124arm64-quarterly-job-08 12.4-RELEASE-p6 FreeBSD > 12.4-RELEASE-p6 arm64 > maintained by: ga...@freebsd.org > Makefile ident: > Poudriere version: 3.2.8-23-ga7f8d188 > Host OSVERSION: 150 > Jail OSVERSION: 1204000 > Job Id: 08 > . . . > === > ===> Building package for git-2.42.0 > === > =>> Cleaning up wrkdir > ===> Cleaning for git-2.42.0 > build of devel/git | git-2.42.0 ended at Sun Oct 22 06:06:30 UTC 2023 > build time: 00:04:41 > > > > http://ampere1.nyi.freebsd.org/build.html?mastername=124arm64-quarterly&build=a24e513f186f > started on 2023-Nov-06, 10704 package builds queued, 8910 built, 104 failed. > > http://ampere1.nyi.freebsd.org/build.html?mastername=124arm64-quarterly&build=6687a67ae6e0 > started on 2023-Oct-22, 11101 package builds queued, 9303 built, 105 failed. > > http://ampere1.nyi.freebsd.org/build.html?mastername=124arm64-quarterly&build=46c5200e9027 > started on 2023-Oct-09, 34637 package builds queued, 32836 built, 109 failed. > > and so on until: > > http://ampere1.nyi.freebsd.org/build.html?mastername=124arm64-quarterly&build=7556984ae7d8 > started on 2023-Apr-09, 33471 package builds queued, 31711 built, 144 failed. > > (Prior to that would be 123arm64 .) > > This agrees with https://pkg.freebsd.org/ that lists: > >• FreeBSD:12:aarch64 (only quarterly is updated) > > https://www.freshports.org/devel/git/ shows the > quarterly "started on 2023-Nov-06" build, but based > on its ending date: 2023-Nov-09. > > Other examples of indicating "only quarterly is updated" are from the > Tier-2 list at https://pkg.freebsd.org/ : > >• FreeBSD:12:armv6 (only quarterly is updated) >• FreeBSD:12:armv7 (only quarterly is updated) >• FreeBSD:13:powerpc (only quarterly is updated) >• FreeBSD:13:powerpc64 (only quarterly is updated) >• FreeBSD:13:powerpc64le (only quarterly is updated) >• FreeBSD:14:powerpc (only quarterly is updated) >• FreeBSD:14:powerpc64 (only quarterly is updated) >• FreeBSD:14:powerpc64le (only quarterly is updated) > > Looking around for armv6: only quarterly 132releng-armv6 has > been building since Thu, 24 Aug 2023 04:40:18 GMT : > > http://beefy8.nyi.freebsd.org/build.html?mastername=132releng-armv6-quarterly&build=cdf0ecca10dc > > The most recent gives a clue at how little is successful for > armv6: > > 34637 queued, 8276 built, 242 failed. So: 25763 skipped > Status: stopped:crashed: > Thu, 05 Oct 2023 02:37:41 GMT > http://beefy8.nyi.freebsd.org/build.html?mastername=132releng-armv6-quarterly&build=46c5200e9027 > > (The context is amd64 cross building via qemu, which does not > work well for armv6 targeting.) > > The powerpc64 builds do not seem to be inspectable for what > I've been reporting here, despite showing up on FreshPorts. > powerpc and powerpc64le I've no source of evidence of at all. > > ampere1, ampere2, and ampere3 do both aarch64 and armv7 builds > (no qemu involved), since Fri, 29 Jul 2022 05:08:58 GMT. Before > that was amd64 via qemu, like armv6 still is. But I find no > evidence of any sequence of 12.[234] builds for armv7. Turns out that the following show that powerpc64le is getting some port->package builds, at least this month: 2023-Nov-11: https://pkg.freebsd.org/FreeBSD:15:powerpc64le/latest/ 2023-Nov-15: https://pkg.freebsd.org/FreeBSD:14:powerpc64le/quarterly/ 2023-Nov-13: https://pkg.freebsd.org/FreeBSD:13:powerpc64le/quarterly/ As for powerpc64, not this month but . . . : 2023-Oct-09: https://pkg.freebsd.org/FreeBSD:15:powerpc64/latest/ 2023-Jul-05: https://pkg.freebsd.org/FreeBSD:14:powerpc64/quarterly/ 2023-Sep-30: https://pkg.freebsd.org/FreeBSD:13:powerpc64/quarterly/ As for powerpc (so: 32-bit): 2023-Jul-10: https://pkg.freebsd.org/FreeBSD:14:powerpc/quarterly/ 2023-Oct-02: https://pkg.freebsd.org/FreeBSD:13:powerpc/quarterly/ Note: https://pkg.freebsd.org/FreeBSD:15:powerpc/latest/ is empty. (I've ignored base_*/ directories: not from port builds.) The powerpc* activity (all 3) is not visibl
Unmaintained FreeBSD ports which are out of date
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 port. If any ports have already been updated, you can safely ignore the entry. An e-mail will not be sent again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ cad/ifcopenshell| 0.6.0 | blenderbim-231121 +-+ databases/sql-workbench | 127 | 131 +-+ sysutils/nix| 2.3.11 | 2.19.0 +-+ www/rubygem-passenger | 6.0.18 | 6.0.19 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout!
