Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 16 Feb 2021 17:38:43 +0100 (CET)
From:      Ronald Klop <ronald-lists@klop.ws>
To:        Brandon Bergren <bdragon@FreeBSD.org>
Cc:        FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: pkg vs uname troubles after upgrade to 14
Message-ID:  <910834631.23.1613493523851@localhost>
In-Reply-To: <d9254cab-cc1f-4ef0-bcbb-b7624f57adb4@www.fastmail.com>
References:  <679869967.9.1613490921704@localhost> <d9254cab-cc1f-4ef0-bcbb-b7624f57adb4@www.fastmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
libpkg/pkg_elf.c:    const char *abi_files[] = {
libpkg/pkg_elf.c-        getenv("ABI_FILE"),
libpkg/pkg_elf.c-        _PATH_UNAME,
libpkg/pkg_elf.c-        _PATH_BSHELL,
libpkg/pkg_elf.c-    };

The detection first checks "/usr/bin/uname" if it exists and ABI_FILE is not set.
Yes the base is upgraded properly. It is a BE so if I installed wrongly I would not have any base.

But base is compiled by 13. So the ELF note NT_FREEBSD_ABI_TAG of the uname binary is 1300133.

I normally compile WITHOUT_CLEAN. What is the shortcut to recompile uname with the proper version nr and not having to recompiling clang? Cleaning and rebuilding only uname does not help.

Regards,
Ronald.

 
Van: Brandon Bergren <bdragon@FreeBSD.org>
Datum: dinsdag, 16 februari 2021 17:02
Aan: FreeBSD Current <freebsd-current@freebsd.org>
Onderwerp: Re: pkg vs uname troubles after upgrade to 14
> 
> IIRC, the detection works by probing /bin/sh, make sure you upgraded your base properly.
> 
> On Tue, Feb 16, 2021, at 9:55 AM, Ronald Klop wrote:
> > Hi,
> >
> > Upgraded from 13 to 14.
> >
> > # uname -UK
> > 1400003 1400003
> >
> > But elfdump on uname gives:
> > note (.note.tag):
> >         FreeBSD 1300133 (NT_FREEBSD_ABI_TAG)
> >
> >
> > # pkg -o OSVERSION=1400003 upgrade
> > pkg: Warning: Major OS version upgrade detected.  Running "pkg
> > bootstrap -f" recommended
> > Updating FreeBSD repository catalogue...
> > FreeBSD repository is up to date.
> > All repositories are up to date.
> > Updating database digests format: 100%
> > Checking for upgrades (1 candidates): 100%
> > Processing candidates (1 candidates): 100%
> > Checking integrity... done (0 conflicting)
> > The following 1 package(s) will be affected (of 0 checked):
> >
> > Installed packages to be REINSTALLED:
> >     pkg-1.16.2 (ABI changed: 'freebsd:14:aarch64:64' -> 'freebsd:13:aarch64:64')
> >
> > Number of packages to be reinstalled: 1
> >
> >
> > How do I do this properly? Rebuilding name still gives it the ELF note
> > of 1300133.
> > It does not matter if I pass "-o OSVERSION=1400003" to pkg or not.
> > Found https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225104, but I
> > don't think it was really resolved.
> >
> > This is on aarch64. And why does pkg not use the version uname is
> > reporting by -UK instead of the ELF note?
> >
> > Regards,
> > Ronald.
> >
> >  
> > _______________________________________________
> > freebsd-current@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
> >
> 
> -- 
>   Brandon Bergren
>   bdragon@FreeBSD.org
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
> 
> 
> 
From owner-freebsd-current@freebsd.org  Tue Feb 16 17:29:45 2021
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id C9C52540C2C
 for <freebsd-current@mailman.nyi.freebsd.org>;
 Tue, 16 Feb 2021 17:29:45 +0000 (UTC)
 (envelope-from bdragon@FreeBSD.org)
Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83])
 (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 RSA-PSS (4096 bits) client-digest SHA256)
 (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 4Dg7JT57Jxz4lhK;
 Tue, 16 Feb 2021 17:29:45 +0000 (UTC)
 (envelope-from bdragon@FreeBSD.org)
Received: from auth1-smtp.messagingengine.com (auth1-smtp.messagingengine.com
 [66.111.4.227])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 (Authenticated sender: bdragon/mail)
 by smtp.freebsd.org (Postfix) with ESMTPSA id 9D9802180B;
 Tue, 16 Feb 2021 17:29:45 +0000 (UTC)
 (envelope-from bdragon@FreeBSD.org)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43])
 by mailauth.nyi.internal (Postfix) with ESMTP id 8B07E27C0054;
 Tue, 16 Feb 2021 12:29:45 -0500 (EST)
Received: from imap38 ([10.202.2.88])
 by compute3.internal (MEProxy); Tue, 16 Feb 2021 12:29:45 -0500
X-ME-Sender: <xms:CAEsYH_6SnG3Bvqjz90WKl1K_hPimoqpvj_mZuqhy5V52Z4HV1AUUg>
 <xme:CAEsYDveBPGNQJhDqbPaOEba9sMacuW2r2pM5eXU5nmrmIHr9KJixKNMptCDyNLd0
 4PyedsT1Yz4TZQy>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrjedtgddutddvucetufdoteggodetrfdotf
 fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
 uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne
 gfrhhlucfvnfffucdluddtmdenucfjughrpefofgggkfgjfhffhffvufgtsehttdertder
 redtnecuhfhrohhmpedfuehrrghnughonhcuuegvrhhgrhgvnhdfuceosggurhgrghhonh
 eshfhrvggvuefuffdrohhrgheqnecuggftrfgrthhtvghrnhepteetleffuddvtddtuedv
 hfefheejvddvgfdvkedvfeethfegkedvkeelveeuvddunecuvehluhhsthgvrhfuihiivg
 eptdenucfrrghrrghmpehmrghilhhfrhhomhepsggurhgrghhonhdomhgvshhmthhprghu
 thhhphgvrhhsohhnrghlihhthidquddtgedvfeehkeeigedqudekuddtkeehuddqsggurh
 grghhonheppefhrhgvvgeuufffrdhorhhgsehimhgrphdrtggt
X-ME-Proxy: <xmx:CAEsYFD5f_5KlMBffxD_VpBCj8lIrV_DqDwGTX21F0zIqsWn_S8YxA>
 <xmx:CAEsYDdzHtHy1-kDzfVi12QCAPdi-thveW5DIZ-7LLHUWMkNplD05w>
 <xmx:CAEsYMM8copcH7xrS14SsqGZ9tk-nt2_aP1yZ31nXU9GqT28_I9A0w>
 <xmx:CQEsYHZ98krewYxj6ovjaz0YYvC0zYCs9IIy0oA8SLGiFH1Zf218bw>
Received: by mailuser.nyi.internal (Postfix, from userid 501)
 id C6F03CA005D; Tue, 16 Feb 2021 12:29:44 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-141-gf094924a34-fm-20210210.001-gf094924a
Mime-Version: 1.0
Message-Id: <84590734-ba0b-4e06-ac79-84f76c2e2468@www.fastmail.com>
In-Reply-To: <910834631.23.1613493523851@localhost>
References: <679869967.9.1613490921704@localhost>
 <d9254cab-cc1f-4ef0-bcbb-b7624f57adb4@www.fastmail.com>
 <910834631.23.1613493523851@localhost>
Date: Tue, 16 Feb 2021 11:29:25 -0600
From: "Brandon Bergren" <bdragon@FreeBSD.org>
To: "Ronald Klop" <ronald-lists@klop.ws>
Cc: "FreeBSD Current" <freebsd-current@freebsd.org>
Subject: Re: pkg vs uname troubles after upgrade to 14
Content-Type: text/plain
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>;
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Feb 2021 17:29:45 -0000

On Tue, Feb 16, 2021, at 10:38 AM, Ronald Klop wrote:
> I normally compile WITHOUT_CLEAN. What is the shortcut to recompile 
> uname with the proper version nr and not having to recompiling clang? 
> Cleaning and rebuilding only uname does not help.

Uh, I would drop into a buildenv with "make buildenv" and do the build there to ensure it's using the toolchain from your world build.

the kernel version and the base system version are not the same thing. pkg attempts to install binaries compatible with the base system.

Are you *sure* you did installworld after rebooting into the new kernel? For that matter, are you *sure* you have the correct branch checked out in the first place? Because it's acting as if you are on the wrong branch.


-- 
  Brandon Bergren
  bdragon@FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?910834631.23.1613493523851>