How did packages I built on 9.3 end up being built for 9.0?

kc9udx

Like the title says, I just got done (re) building a list of packages from source, on my Pinebook Pro running NetBSD 9.3 (aarch64). Upon installing them, I get warnings that they were built for 9.0. How could that happen? (I don't think I've ever run 9.0 anywhere on anything; I ran 8.x till upgrading to 9.2, I think)

Jay

kc9udx I think this is due to osabi package

Jay

You will probably need to

CHECK_OSABI "no" in pkg_install.conf

Jay

Here : https://www.unitedbsd.com/d/490-netbsd-package-branches/4

kc9udx

Well, they're only warnings, so I'm not worried. I thought OSABI always returns the OS version from when it was built. If that's the way it works, then mine should be 9.3. So it must not work that way.

rvp

kc9udx This is really my buddy @pin's dept., but... I just built a simple package on 10.99.10, and it shows 10.99.10:

CoreBook# tar -C/usr -xf /tmp/pkgsrc-2023Q4.tar.xz
CoreBook# cd /usr/pkgsrc/shells/dash
CoreBook# make show-var VARNAME=OS_VERSION
10.99.10
CoreBook# make package
[...]
=> Creating binary package /usr/pkgsrc/shells/dash/work/.packages/dash-0.5.11.4.tgz
===> Building binary package for dash-0.5.11.4
=> Creating binary package /usr/pkgsrc/packages/All/dash-0.5.11.4.tgz
CoreBook# mkdir /tmp/X; tar -C/tmp/X -xf /usr/pkgsrc/packages/All/dash-0.5.11.4.tgz
CoreBook# fgrep OS_VERSION /tmp/X/+BUILD_INFO
OS_VERSION=10.99.10
CoreBook#

How did you build your packages? Did something make use of pkgtools/libkver?

kc9udx

rvp libkver is not installed, so I presume no.

OS_VERSION is 9.3

It seems most packages are "built for 9.3" but a large number for 9. 0

Did you pull any pre-built binaries at some point? If so, what repository?

kc9udx

pin not that I recall. I wiped out everything and rebuilt everything I have from source. But I did this twice, and reused binaries from the last time (also 9.3). So something could have got mixed up; I don't know how else to explain this.

Anything strange on any of these?

pkg_info | grep osabi
cat /usr/pkg/etc/pkgin/repositories.conf
uname -a

and any weird lines in /etc/mk.conf?

kc9udx

I'll check. I don't believe I've used pkgin for installation. (I do use it to unkeep and delete, which I probably shouldn't).

My mk.conf is huge, but I'll take another look at it. If I get a chance, I'll post it here.

kc9udx I don't believe I've used pkgin for installation. (I do use it to unkeep and delete, which I probably shouldn't).

Nah, why not? I build everything from source these days but, pkgin is nice and handles dependencies well.

kc9udx

pin because once in a while, using pkgin causes a database mismatch; pkg_admin rebuild-tree solves.

kc9udx

Well, I found out that osabi 9.0 was installed on one of the two machines I've been using to build packages. I don't know how or why, but at least that explains why some packages were built for 9.0

And the other machine seems to have a failing SOC.