From nobody Sun Mar 03 18:33:05 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 4Tnr6r4Mf6z5C4J2 for ; Sun, 3 Mar 2024 18:33:08 +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 4Tnr6q3y6nz4kwN for ; Sun, 3 Mar 2024 18:33:07 +0000 (UTC) (envelope-from david@catwhisker.org) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of david@catwhisker.org designates 107.204.234.170 as permitted sender) smtp.mailfrom=david@catwhisker.org Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.18.1/8.18.1) with ESMTP id 423IX5TA048873 for ; Sun, 3 Mar 2024 18:33:05 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.18.1/8.18.1/Submit) id 423IX5sR048872 for freebsd-ports@freebsd.org; Sun, 3 Mar 2024 10:33:05 -0800 (PST) (envelope-from david) Date: Sun, 3 Mar 2024 10:33:05 -0800 From: David Wolfskill To: freebsd-ports@freebsd.org Subject: How do I clear no-longer-usable packages from poudriere? Message-ID: Reply-To: freebsd-ports@freebsd.org 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="QT7NY3DP5lP4HMNR" Content-Disposition: inline X-Spamd-Bar: / X-Spamd-Result: default: False [0.60 / 15.00]; REPLYTO_EQ_TO_ADDR(5.00)[]; SIGNED_PGP(-2.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; R_SPF_ALLOW(-0.20)[+ip4:107.204.234.170:c]; RCPT_COUNT_ONE(0.00)[1]; FREEFALL_USER(0.00)[david]; DMARC_NA(0.00)[catwhisker.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; MISSING_XM_UA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:7018, ipnet:107.192.0.0/12, country:US]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[freebsd-ports@freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-ports@freebsd.org]; R_DKIM_NA(0.00)[]; HAS_REPLYTO(0.00)[freebsd-ports@freebsd.org] X-Rspamd-Queue-Id: 4Tnr6q3y6nz4kwN --QT7NY3DP5lP4HMNR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I have a local package-builder that's (generally) been working quite well for me since Jul 2015 (through a couple of hardware replacements, sure, but the approach remains the same). Today, in trying to chase down what was causing my central "hub" machine to whine: ld-elf.so.1: /usr/local/lib/libtasn1.so.6: version LIBTASN1_0_3 required by= /usr/local/lib/libgnutls.so.30 not defined I found (via the "pkg_libchk" script from ports-mgmt/bsdadminscripts2) that some just-installed packages are apparently expecting to use libc.so.6, which hasn't existed on anything here since 18 February. (My machines run stable/14 for getting things done; the development machines also track head, so I have some clue what's coming.) The package-builder also builds FreeBSD for its "client" machines. The package-builder (and my laptop) track stable/14 daily; the package-builder does a 2-pass weekend run of package-building (first pass on Saturday, after updating FreeBSD; second on Sunday). Once the packages are built, the client machines update FreeBSD (to the latest snapshot from the package-builder, which is already running that code). The package-builder is thus running the same revision of FreeBSD that the clients are about to run. And poudriere is using the package-builder's /usr/src and /usr/ports to construct jails & build stuff. I am trying to ensure a certain level of consistency, here. And today appears to show that I have failed to do that. Is there something less drastic than clearing all poudriere caches of packages and rebuilding all packages all over again??!? (that will get me a set of packages consistent with the current state of FreeBSD sources and ports (stable/14-n266921-8a7d5d73b849 and main-n654175-6928d3a11398, respectively (at the moment)))? At least name resolution isn't broken this time, but printing seems to have been a casualty. 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. --QT7NY3DP5lP4HMNR Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iNUEARYKAH0WIQSTLzOSbomIK53fjFliipiWhXYx5QUCZeTCYV8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0OTMy RjMzOTI2RTg5ODgyQjlEREY4QzU5NjI4QTk4OTY4NTc2MzFFNQAKCRBiipiWhXYx 5VYcAQCFUyb+t0jh5vdeZrQ8VH8bjEpQuh6ZWb3mjKu00nudTgEA3rPphcuxwQDQ ks/EajGMOeqDE2jirAzj0R4HF+EQIgY= =Jc/T -----END PGP SIGNATURE----- --QT7NY3DP5lP4HMNR--