Date: Wed, 14 Feb 2018 17:55:11 +0000 From: bugzilla-noreply@freebsd.org To: pkg@FreeBSD.org Subject: [Bug 225104] ports-mgmt/pkg: "pkg update" fails to update package database saying that kernel too old for some package Message-ID: <bug-225104-32340-kDXuVfk5gz@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-225104-32340@https.bugs.freebsd.org/bugzilla/> References: <bug-225104-32340@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225104 --- Comment #19 from Nils Beyer <nbe@renzel.net> --- (In reply to Trond.Endrestol from comment #18) As far as I understand; the responsible file would be: ${OBJTOP}/host-osreldate.h But that doesn't matter because the "osversion" tag within the ELF files is always lagging behind. Example: you're running osversion=3D1101508 and building a new world/kernel= with osversion=3D1101509. All of your ELF files are tagged with what is in /usr/include/osreldate.h at the moment when you build world. So, after finishing building and instal= ling world you have all ELF files tagged with 1101508 although you're running 1101509. Furthermore, "host-osreldate.h" is never updated (here on my machi= ne using NO_CLEAN), even if I build the same world with the up-to-date install= ed world; it just says "`host-osreldate.h' is up to date." which is not true. Perhaps it would be better for "libpkg" to rely on what "sysctl" or "getosreldate()" are saying. But that's just my simple-minded user's point of view... --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-225104-32340-kDXuVfk5gz>