From nobody Tue Mar 05 04:12:14 2024 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Tphwd4Jfyz5BjFq for ; Tue, 5 Mar 2024 04:12:17 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [107.204.234.170]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Tphwd0sdwz4m80 for ; Tue, 5 Mar 2024 04:12:17 +0000 (UTC) (envelope-from david@catwhisker.org) Authentication-Results: mx1.freebsd.org; none Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.18.1/8.18.1) with ESMTP id 4254CEi8015892; Tue, 5 Mar 2024 04:12:14 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.18.1/8.18.1/Submit) id 4254CEfC015891; Mon, 4 Mar 2024 20:12:14 -0800 (PST) (envelope-from david) Date: Mon, 4 Mar 2024 20:12:14 -0800 From: David Wolfskill To: Tatsuki Makino Cc: freebsd-ports@freebsd.org Subject: Re: [Solved?] Re: How do I clear no-longer-usable packages from poudriere? Message-ID: Reply-To: freebsd-ports@freebsd.org References: List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="iIunhDY3cNKbKR81" Content-Disposition: inline In-Reply-To: X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7018, ipnet:107.192.0.0/12, country:US] X-Rspamd-Queue-Id: 4Tphwd0sdwz4m80 --iIunhDY3cNKbKR81 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 05, 2024 at 12:35:33PM +0900, Tatsuki Makino wrote: > I recently saw a similar problem and thought I had looked into something,= but this was it. > https://lists.freebsd.org/archives/freebsd-ports/2024-February/005546.html >=20 > David Wolfskill wrote on 2024/03/05 10:27: > > albert(14.0-S)[14] pdf2ps pdf/bike.pdf >/tmp/bike.ps > > ld-elf.so.1: /usr/local/lib/libidn.so.12: version LIBIDN_1.0 required b= y /usr/local/lib/libgs.so.10 not defined > .... > It seems that not only fstrm but also libidn contained the same problem. Indeed. And (as far as I know), perhaps others. > This would seem to indicate that there has been a change on the part of t= he OS that reverses the availability of version-script in your environment. > However, since the package version has not changed, the actual package us= ed would not have been reinstalled. > And since a version-script availability was reversed at the same time as = some dependent package was rebuilt, all packages created in poudriere were = assumed to be so. >=20 > I guess that's how it is :) >=20 > For its part, configure seems to output the following line >=20 > checking if LD -Wl,--version-script works... yes >=20 > If you are still keeping a large amount of poudriere logs, can you check = to see if there is a mix of yes and no on the lines? >=20 > Regards. > .... I am, yeah. :-} And running: grep -r 'checking if LD -Wl,--version-script works' 20* in the parent directory of the logs (from 2023-11-26_15h39m37s - 2024-03-03_11h45m10s) shows "yes" responses consistently through: 2023-12-31_11h44m48s/logs/ImageMagick6-nox11-6.9.12.77_7,1.log:checking if = LD -Wl,--version-script works... yes the next entry is: 2024-01-21_13h15m44s/logs/gnutls-3.7.10.log:checking if LD -Wl,--version-sc= ript works... no and all of the subsequent entries are "no". Summarizing: 33 yes 43 no 76 total For the last "yes" entry, the build machine was running: FreeBSD 14.0-STABLE #33 stable/14-n266091-1e9df419f14c: Sat Dec 30 11:51:06= UTC 2023 root@freebeast.catwhisker.org:/common/S1/obj/usr/src/amd64.am= d64/sys/GENERIC amd64 1400503 1400503 For the first "no" entry, it was running: FreeBSD 14.0-STABLE #34 stable/14-n266092-ab71e3480921: Mon Jan 1 11:34:00= UTC 2024 root@freebeast.catwhisker.org:/common/S1/obj/usr/src/amd64.am= d64/sys/GENERIC amd64 1400503 1400503 (I was away from home from 01 Jan - 20 Jan; I did not attempt to update anything during that time.) The next record of a "uname string" on the build machine is: FreeBSD 14.0-STABLE #36 stable/14-n266466-9d29be87d86c: Mon Jan 22 11:52:14= UTC 2024 root@freebeast.catwhisker.org:/common/S1/obj/usr/src/amd64.am= d64/sys/GENERIC amd64 1400506 1400506 Peace, david --=20 David H. Wolfskill david@catwhisker.org Alexey Navalny was a courageous man; Putin has made him a martyr. See https://www.catwhisker.org/~david/publickey.gpg for my public key. --iIunhDY3cNKbKR81 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iNUEARYKAH0WIQSTLzOSbomIK53fjFliipiWhXYx5QUCZeabnl8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0OTMy RjMzOTI2RTg5ODgyQjlEREY4QzU5NjI4QTk4OTY4NTc2MzFFNQAKCRBiipiWhXYx 5aSLAQCo+BLk/obkzMi76TPoXoEhYF8Kjf+silDmCRTX9ZD7rwEAnja958M6GsVi mMA+zfrnhA3BDFfp5ghnvdXujP42EQk= =5rVY -----END PGP SIGNATURE----- --iIunhDY3cNKbKR81--