[Bug 287738] ports-mgmt/pkg: pkg-static upgrade -f segmentation fault

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287738

--- Comment #19 from Mark Millard <marklmi26-fbsd@yahoo.com> ---
(In reply to Lukas Engelhardt from comment #18)

Thanks much for the procedure notes.

Interesting mix of official builds and personal builds
of base packages. (No claim that such is supposed to
have problems.)

The below are just my notes/questions for reference.

> Freshly installed Host with FreeBSD 14.2-RELEASE.
> Used pkgbasify to convert it to pkgbased.

So: official, upstream pkgbase 14.2 installation as of here.

> Upgraded to 14.3p2 using packages built from releng/14.3 using `make buildworld && > make buildkernel && make packages` with commit Hash 5982521fe3dd3f1627bbe29ee8c3b190a24e3963

So: personal build of pkgbase is available to install
here to establish a 14.3p2 that is not just an install
of the official upstream pkgbase 14.3p2 . (Why were the
upstream, official 14.3p2 pkgbase materials not used?)

I'll note that your personal build may or may not have
had equivalent /etc/src.conf /etc/make.conf and
such configuration materials to whatever the details
are for the official pkgbase builds.

There is no explicit mention of rebooting to use the new
kernel or to to have the system and services running the
new world. Was a reboot done before the below?

> Created a FreeBSD 14.3 Jail with poudriere and built pkg, vim, tmux and htop.

So, above: possibly a system booted with a 14.2 kernel ran a 14.3p2 jail.
Otherwise a personal 14.3p2 build ran the 14.3p2 jail. Unsure.

> Configured my repository on the client

"client"? Is there some sort of context switch here? (I'm guessing: no.
So: the-booted-system instead of a jail?)

> and installed these.

I presume "these" are: pkg, vim, tmux and htop

Note: Still unsure of the boot system version here.

> Pkg Version 2.3.1.
> Built packages with stable/15, commit hash c2427a67c7af60bd4d07acce0ab4f0c4be2258c2

Built pkgbase packages? Built ports packages? Both?
I'm guessing pkgbse packages via buildworld buildkernel
and then packages activity. Was this 14.3p2 building
stable/15 ?

I'll note that your personal build may or may not have
had equivalent /etc/src.conf /etc/make.conf and
such configuration materials to whatever the details
are for the official pkgbase builds.

However, it appears to take extraction of official 15.0-ALPHA2
pkgbase packages from its *boot1.iso or *memstick.img to avoid
doing a personal build of such:

url: "pkg+http://pkg.FreeBSD.org/FreeBSD:15:amd64/base_latest",

and the like are not being updated to have 15.0-ALPHA*
materials and the .

Note: bootonly.iso and mini-memstack.img do not have the
15.0-ALPHA2 pkgbase materials and can install only what
is distributed upstream.

> 
> installed the kernel package using 
> `env ABI=FreeBSD:15:amd64 pkg-static upgrade -r FreeBSD-base -g 'FreeBSD-kernel*'`

Was FreeBSD-base at this point defined via use of:

url: "pkg+http://pkg.FreeBSD.org/${ABI}/base_latest",

vs. via something else? That url would not lead to installing
a 15.0-APLHA* group of kernel(s). It would install a main 15
group of kernels from 2025-Sep-04 or so. Upstream
http://pkg.FreeBSD.org/FreeBSD:15:amd64/base_latest/ and the
like are not being updated to have 15.0-APLHA* materials.

(Looks like the below implicitly answers the above question.)

> 
> rebooted, now: 

That booted a 15.0-APLHA2 kernel (1500064) based on a
personal build:

> `uname -apKU
> FreeBSD pkgbase 15.0-ALPHA2 FreeBSD 15.0-ALPHA2 stable/15-n280148-c2427a67c7af GENERIC amd64 amd64 1500064 1403000`

Hmm. That 1403000 suggests that a 14.3(p2) world
was installed at some earlier point --but not
answering when it was first booted.

> upgraded the other packages:
> `env ABI=FreeBSD:15:amd64 pkg-static upgrade -r FreeBSD-base`

That lead to the:

QUOTE
[20/413] Upgrading FreeBSD-zoneinfo from 14.3p2 to 15.0.a2.20250916101338...
[20/413] Extracting FreeBSD-zoneinfo-15.0.a2.20250916101338: 100%
Child process pid=1109 terminated abnormally: Segmentation fault
END QUOTE

Again, I just made notes/questions as I try to understand the
full sequence. Nothing above identifies a specific problem as
having occured. That could depend on answers to questions.

-- 
You are receiving this mail because:
You are the assignee for the bug.