On Fri, Oct 11, 2019 at 01:57:06PM +0200, Bengt Ahlgren wrote: > Baptiste Daroussin <b...@freebsd.org> writes: > > > On Fri, Oct 11, 2019 at 11:54:15AM +0200, Bengt Ahlgren wrote: > >> Baptiste Daroussin <b...@freebsd.org> writes: > >> > >> > On Fri, Oct 11, 2019 at 11:38:46AM +0200, Bengt Ahlgren wrote: > >> >> Baptiste Daroussin <b...@freebsd.org> writes: > >> >> > >> >> > On Thu, Oct 10, 2019 at 03:44:03PM +0200, Bengt Ahlgren wrote: > >> >> >> Ronald Klop <ronald-li...@klop.ws> writes: > >> >> >> > >> >> >> > Van: Bengt Ahlgren <bengt.ahlg...@ri.se> > >> >> >> > Datum: woensdag, 9 oktober 2019 23:38 > >> >> >> > Aan: sta...@freebsd.org > >> >> >> > Onderwerp: pkg thinks kernel is old > >> >> >> >> > >> >> >> >> I've ran into this on my 11.3-STABLE system: > >> >> >> >> > >> >> >> >> # uname -K > >> >> >> >> 1103500 > >> >> >> >> # pkg update -f > >> >> >> >> Updating ivyp repository catalogue... > >> >> >> >> Fetching meta.txz: 100% 560 B 0.6kB/s 00:01 Fetching > >> >> >> >> packagesite.txz: 100% 410 KiB 419.9kB/s 00:01 Processing > >> >> >> >> entries: 0% > >> >> >> >> Newer FreeBSD version for package zziplib: > >> >> >> >> To ignore this error set IGNORE_OSVERSION=yes > >> >> >> >> - package: 1103000 > >> >> >> >> - running kernel: 1102509 > >> >> >> >> Ignore the mismatch and continue? [Y/n]: > >> >> >> >> > >> >> >> >> I build my own packages with poudriere, and have just switched > >> >> >> >> from an > >> >> >> >> 11.2-REL to an 11.3-REL jail. I didn't force-upgrade everything > >> >> >> >> after > >> >> >> >> the switch, perhaps that's needed to make pkg recognise the > >> >> >> >> correct > >> >> >> >> kernel version? > >> >> >> >> > >> >> >> >> Bengt > >> >> >> > >> >> >> > This message of pkg is misleading. > >> >> >> > > >> >> >> > It looks at /bin/sh or something like that for the version. And > >> >> >> > prints > >> >> >> > that as the 'kernel' version. So if you did an incremental build > >> >> >> > and > >> >> >> > /bin/sh was not changed the version stays the same. > >> >> >> > To fix it you can do a clean buildworld/installworld. > >> >> >> > > >> >> >> > Regards, > >> >> >> > Ronald. > >> >> >> > >> >> >> That might well be it - I've done some buildworld:s with -DNO_CLEAN > >> >> >> lately. I'll test - thanks for the tip! > >> >> > > >> >> > Can you provide the uname -U information (building with -DNO_CLEAN) > >> >> > should be > >> >> > perfectly fine. > >> >> > >> >> Thanks for looking into this! > >> >> > >> >> $ uname -U > >> >> 1103500 > >> >> > >> >> Let me know if there is something else I can check before I do a full > >> >> buildworld on this system! > >> > > >> > What are the output of pkg config osversion > >> > and pkg -o ABI_FILE=/usr/bin/uname config osversion > >> > please > >> > >> $ pkg config osversion > >> 1102509 > >> $ pkg -o ABI_FILE=/usr/bin/uname config osversion > >> 1102509 > > > > It means you /usr/bin/uname binary has been built with a compiler that says > > it > > is building for 1102509. > > > > Can you show the output of file /usr/bin/uname ? > > $ uname -aKU > FreeBSD P142.sics.se 11.3-STABLE FreeBSD 11.3-STABLE #9 r353280: Mon Oct 7 > 22:16:02 CEST 2019 r...@p142.sics.se:/storage/obj/usr/src/sys/X250 amd64 > 1103500 1103500 > > no signs of 1102509 there... > > and "strings -a /usr/bin/uname |grep 110" returns nothing. > I am interested in the output of file /usr/bin/uname
Best regards, Bapt
signature.asc
Description: PGP signature
