From nobody Fri Aug 8 23:38:39 2025 X-Original-To: freebsd-pkgbase@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 4bzL8N1d2Cz64NJV for ; Fri, 08 Aug 2025 23:39:00 +0000 (UTC) (envelope-from freebsd@gushi.org) Received: from prime.gushi.org (prime.gushi.org [IPv6:2620:137:6000:10::142]) (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-signature ECDSA (secp384r1) client-digest SHA384) (Client CN "prime.gushi.org", Issuer "E6" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bzL8L3DXZz46f6 for ; Fri, 08 Aug 2025 23:38:58 +0000 (UTC) (envelope-from freebsd@gushi.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gushi.org header.s=prime2014 header.b=YXFP8Gjz; spf=pass (mx1.freebsd.org: domain of freebsd@gushi.org designates 2620:137:6000:10::142 as permitted sender) smtp.mailfrom=freebsd@gushi.org; dmarc=pass (policy=none) header.from=gushi.org Received: from smtpclient.apple ([IPv6:2601:602:8700:2d98:5189:74ef:aa88:bcef]) (authenticated bits=0) by prime.gushi.org (8.18.1/8.18.1) with ESMTPSA id 578Nco3r014614 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT) for ; Fri, 8 Aug 2025 23:38:50 GMT (envelope-from freebsd@gushi.org) DKIM-Filter: OpenDKIM Filter v2.10.3 prime.gushi.org 578Nco3r014614 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gushi.org; s=prime2014; t=1754696331; bh=zVm3xecv5jajo7JERoe6QxwXwpNsGZUgaXcIdUCBv7k=; h=From:Subject:Date:To; z=From:=20Dan=20Mahoney=20|Subject:=20after=20up dating=20to=20latest,=20pkg=20base=20segfaults=20and=20leaves=20me =20unbootable|Date:=20Fri,=208=20Aug=202025=2016:38:39=20-0700|To: =20freebsd-pkgbase@freebsd.org; b=YXFP8GjzqZuS+6tDbCJ3CltAXEfGZvXyDom4QhrsF+0jeaZ74j6QA23PBEHGxFdrh kpZd541/EF61pcuI9cYCPr+y4bsqpcVty2X+Wa9lniyqGVeTCdN5ML4kq17HUNj7mG kw49AFuT+S3TzUYkAC8aCi1SLWC2MD2vedy3tJD+00Aj/iYJosjPj9VEpmWv6tZh5b Scda7idyi4bvoZAuEltCmS9ochCYjkzN3vPW1bAY/x5Q97NnP/3ZhrgrIN0P9oRCZm j1RrIG9STY8fP7foOCu47vtW4uYQi3tZtelC0o2hnzNPxlN/QOd7s7ZiP0P9aeF7JN P5kL3eUumltDw== X-Authentication-Warning: prime.gushi.org: Host [IPv6:2601:602:8700:2d98:5189:74ef:aa88:bcef] claimed to be smtpclient.apple Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Dan Mahoney List-Id: Packaging the FreeBSD base system List-Archive: https://lists.freebsd.org/archives/freebsd-pkgbase List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-pkgbase@FreeBSD.org Mime-Version: 1.0 (1.0) Subject: after updating to latest, pkg base segfaults and leaves me unbootable Message-Id: Date: Fri, 8 Aug 2025 16:38:39 -0700 To: freebsd-pkgbase@freebsd.org X-Mailer: iPhone Mail (23A5297m) X-Spamd-Result: default: False [-5.50 / 15.00]; DWL_DNSWL_LOW(-1.00)[gushi.org:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[gushi.org,none]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; ONCE_RECEIVED(0.20)[]; RCVD_IN_DNSWL_MED(-0.20)[2620:137:6000:10::142:from]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[gushi.org:s=prime2014]; MIME_GOOD(-0.10)[text/plain]; APPLE_IOS_MAILER_COMMON(0.00)[]; DKIM_TRACE(0.00)[gushi.org:+]; RCVD_TLS_ALL(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; ASN(0.00)[asn:393507, ipnet:2620:137:6000::/44, country:US]; MIME_TRACE(0.00)[0:+]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-pkgbase@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-pkgbase@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_XAW(0.00)[] X-Rspamd-Queue-Id: 4bzL8L3DXZz46f6 X-Spamd-Bar: ----- =EF=BB=BF =EF=BB=BF (Resending from phone after realizing my list-specific from: wasn=E2=80=99t s= et, apologies for weird formatting) Hey all, After the recent big sleep in pkgbase, I hit the following trying to upgrade= to whatever snapshot was published today: [598/1127] Deleting files for p5-MIME-Base32-1.303: 100% [599/1127] Deinstalling p5-MIME-Base64-3.16... [599/1127] Deleting files for p5-MIME-Base64-3.16: 100% Child process pid=3D21537 terminated abnormally: Segmentation fault (oh crap) root@poudriere:/home/dmahoney # pkg upgrade ELF interpreter /libexec/ld-elf.so.1 not found, error 2 Abort (double crap) root@poudriere:/home/dmahoney # pkg-static install -f pkg pkg-static: Unable to determine the ABI, none of the ABI_FILEs can be read. pkg-static: Cannot parse configuration file! root@poudriere:/home/dmahoney # /rescue/sh Cannot read termcap database; using dumb terminal settings. # pkg-static pkg: not enough arguments Usage: pkg [-v] [-d] [-l] [-N] [-j |-c |-r ] [-C ] [-R ] [-o var=3Dvalue] [-= 4|-6] [] For more information on available commands and options see 'pkg help'. # pkg-static install -f pkg pkg-static: Unable to determine the ABI, none of the ABI_FILEs can be read. Now, if this were 14.x, I'd fix this by untarring a distfile right over / to= get back up and running. Not quite an option in 15, is it? (I would encou= rage the people making this stuff to please consider keeping those built, ev= en if bsdinstall uses pkgbase). This is dayjob's poudriere system -- the build process for it is well docume= nted and the parts of it that aren't managed by puppet are easily managed be= cause I captured every command used to create every jail and ports tree (whi= ch was slow because many of them came from freebsd-archive; both old jails a= nd old copies of ports trees last known to work with given versions of FreeB= SD (kind of required when you needed to build packages in 2020 because remot= e hands were Not An Option). Like all our systems, the bits we care about (= homedirs, /usr/local/etc) are in backups as well. We kind of need it to wor= k. So this isn't an emergency. This system is really there so that me, as a po= rt maintainer, can build a debug build of something, but this machine isn't i= n our critical path. ...but What If It Was? We run Critical Stuff, out the= re on lone servers in faraway places (on bare metal) But it's *really* not instilling me with a lot of confidence in the readines= s of this pkgbase idea. (For the record, I've also had freebsd-update leave= me dead on the table in similar ways in the past. I literally called them o= ut during a BSDcan talk without trying to bash Colin too hard). I can capture more scrollback if people want, but I wasn't doing any of the c= razy -f commands people are talking about. This was literally a "pkg upgrad= e". Full command output is over at https://users.isc.org/~dmahoney/failedupgrade= .txt if devs want to have a look and try to black-box it. I'll keep the VM r= unning (and logged in, in a screen session) if there are things people want m= e to try. This begs the questions: * Is there CI for pkgbase that tries to upgrade from whatever version is imm= ediately previous to it, before publishing it? (I know that's what version I= was running, it's the version everyone's been stuck at for weeks!) * For all the debate about "pkgbase and pkg should be exactly the same", per= haps pkgbase could have an auto-bectl in it? * Is there support somewhere for having a lockstep "set" of packages that on= e knows are in /var/db/pkg and constitute a relatively concurrent install? (= Or a list of files that I could tell pkg-static to install with a glob, out o= f /var/cache/pkg) * With something like -CURRENT, is there any support for saying "Okay not th= e current-current tree, but current-minus-one" (I guess that would be if yo= u're working with the weekly builds, but that's not quite the same. Your on= ly option is "base system of the now" but it happens less frequently). * And for running -CURRENT where this kind of breakage can happen, could we g= et a statically linked version of pkg? Any questions, let me know. -Dan Sent from my iPhone=