From nobody Sat Sep 2 14:11:04 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RdGzG0PqSz4rQG7 for ; Sat, 2 Sep 2023 14:11:22 +0000 (UTC) (envelope-from dim@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 4RdGzF75R1z3TXM; Sat, 2 Sep 2023 14:11:21 +0000 (UTC) (envelope-from dim@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1693663882; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=onaET3NMJD9RMYWiohwuOIrc9hv81k0qPhOrRJuxY+0=; b=ftZ5oeKIVrP/fxdAFQGAx13bGdvgchWihacTdoHW4+sYLoywoC7ckYb8msxyXCXXfXYYUW Dfk28KjbeWs49sykk6ixaLTKCHof8mA9UmHtBceYuAlsoGoqRI6ztwBi2lR6yhH7x1y/Mv cKvMJTfGl9xl/RgY1K2hKXryApvPSLFnIYTyCBrvZ1KUiEOaalgV6On+VzAc1psZX4ZTCk Id3rq7+3Pkl1nMCiuySMUZhkvyIbVskJCClfjNt8r79sAUsZXHV/vfJkfA8xVLxHmPqbRC dXA4RwQG5eorJen9NlEjZ+sK+inrlXW0FKI5A9U0O/tLisrd5/574EweZVEaFA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1693663882; a=rsa-sha256; cv=none; b=DeLgFGHzwsqN47UqgTrZPYTo3kh6zhG37WTeNwq6G1XaYi9d8cWyDtRz2NPhCYg5vglH5N glya3IzHH5v0EMKR9h3gT/5x/5UITcHynikbry+85M+C6fm0OlgjsW6OGCD3EQUlUBKXP5 LL2hmdyjYjp1F97IcwW0f7aEHmKWmr+CF94DT9zKkTtX7pHXmArg8R9myEw55aB7YENP+y 7zJBlA+ggoxQjhN8lag/c2FBQseEntNNsw+q2wsIijMO2TIMMR+5AE3JTOsgu5Wl2fnM48 nS18R/a0G6AKK82KSGLMNXfLQoHJPsah140FxyMWWxH8NA+9Fwoen2pqZgNG7Q== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1693663882; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=onaET3NMJD9RMYWiohwuOIrc9hv81k0qPhOrRJuxY+0=; b=lD27kTis7LJj4mpvVWHpG3vhEhvGxT+1YMpHVrUgKGZ34ixfynpH7x9e0Yr7RtuxTLvG8z iAGb6f8WPz5BXndkWbPMk7Da381f9kotUaWOuJnSrY8rYrwVro6gt6T2Jg21v5KnMcndwR KIj5L/peNTNhPPFCm4Cn8Is9TGUEx/YAtLt3TIkH6caJ2kuyiDdMAENGi841y4QMeQcBey LWDtVVfw1RbEMa2p1ezQEgu6ORLoOPTnQ54tORhuZYyeuZPA0/dZuMwZbfPpV1a4GUvO7+ KpOTeE40z3jYndU+3nUbcAJFmg7EQmJos4eaUQlUIor61nk1SMbVcntI2RskRQ== Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (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 (2048 bits) client-digest SHA256) (Client CN "tensor.andric.com", Issuer "R3" (verified OK)) (Authenticated sender: dim) by smtp.freebsd.org (Postfix) with ESMTPSA id 4RdGzF5JG2zvNl; Sat, 2 Sep 2023 14:11:21 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from smtpclient.apple (longrow.home.andric.com [192.168.0.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id C9F0965DA5; Sat, 2 Sep 2023 16:11:19 +0200 (CEST) Content-Type: multipart/signed; boundary="Apple-Mail=_D8920F38-DD76-4DA7-B6F1-03324CC36EE2"; protocol="application/pgp-signature"; micalg=pgp-sha1 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\)) Subject: Re: user problems when upgrading to v15 From: Dimitry Andric In-Reply-To: Date: Sat, 2 Sep 2023 16:11:04 +0200 Cc: freebsd-current@freebsd.org Message-Id: <7CDB341A-F9E1-4816-8443-E4C349A86C84@FreeBSD.org> References: <5c5c3ea5-5b14-d969-f55f-b894e4983359@sonicboom.org> <46ee9e3b-adeb-4cd1-5fcc-43547c5c7231@gmail.com> <222e96ba-70b6-e976-8e32-d3726dde18b1@sonicboom.org> To: brian whalen X-Mailer: Apple Mail (2.3731.700.6) --Apple-Mail=_D8920F38-DD76-4DA7-B6F1-03324CC36EE2 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 1 Sep 2023, at 03:42, brian whalen wrote: >=20 > Repeating the entire process: >=20 > I created a 13.2 vm with 6 cores and 8GB of ram. >=20 > Ran freebsd-update fetch and install. >=20 > Ran pkg install git bash ccache open-vm-tools-nox11 >=20 > Used git clone to get current and ports source files. >=20 > Edited /etc/make.conf to use ccache >=20 > Ran make -j6 buildworld && make -j6 kernel >=20 > I then rebooted in single user mode and did the next steps saving = output to a file with > filename. >=20 > etcupdate -p was pretty uneventful. It did show the below and did not = prompt to edit. >=20 > root@f15:~ # less etcupdatep > C /etc/group > C /etc/master.passwd This is a problem: the "C" characters mean there were conflicts, and = it's indeed very unfortunate that etcupdate does not immediately force = you to resolve them. Because now you basically have mangled group and = master.passwd files, with conflict markers in them! Immediately after this, you should run "etcupdate resolve", and fix any = conflicts that it has found. Note that recently there was a lot of churn due to the removal of = $FreeBSD$ keywords, and this almost always creates conflicts in the = group and passwd files. For lots of other files in /etc, the conflicts = are resolved automatically, but unfortunately not for the files that are = essential to log in! > make installworld seemed mostly error free though I did see a nonzero = status for a man page failed inn the man4 directory. >=20 > etcupdate -B only showed the below. This was my first build after = install. >=20 > root@f15:~ # less etcupdateB > Conflicts remain from previous update, aborting. Yes, that is indeed the problem. You must first resolve conflicts from = any previous etcupdate run, before doing anything else. As to why it = does not immediately forces you to do so, and delegates this to a = separate step, which can easily be forgotten, I have no idea. >=20 > If I type exit in single user mode to go multi user mode, the local = user still works. After a reboot the local user still works. This local = user can also sudo as expected. This wasn't the case for the previous = build when I first reported this. However, if I run etcupdate resolve it = is still presenting /etc/group and /etc/master/passwd as problems. >=20 > If this is is expected behavior for current then no big deal. I just = wasn't sure. The conflicts themselves are expected, alas. But you _must_ resolve = them, otherwise you can end up with a mostly-bricked system. -Dimitry --Apple-Mail=_D8920F38-DD76-4DA7-B6F1-03324CC36EE2 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCZPNCeAAKCRCwXqMKLiCW oxKVAJ9AZue/5lyC9boIuNQ/E0CAOL1K/gCg4wfzwmYahtROcaL7n6hdZ3szBiQ= =bRNx -----END PGP SIGNATURE----- --Apple-Mail=_D8920F38-DD76-4DA7-B6F1-03324CC36EE2--