Date: Thu, 26 May 2022 01:16:17 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 264067] ldconfig: aout is not supported Message-ID: <bug-264067-227-CabxS6cnD0@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264067-227@https.bugs.freebsd.org/bugzilla/> References: <bug-264067-227@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=3D264067 p5B2EA84B3@t-online.de changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Not A Bug Status|Open |Closed --- Comment #10 from p5B2EA84B3@t-online.de --- Thank you John for clarification. Now it is clear how I run into this. After having built 13.1-RELEASE from source I wanted to switch from mergema= stet to etcupdate. So I did read our lovely FreeBSD Handbook and stumbled on this warning: When switching from mergemaster(8) to etcupdate(8), the first run might mer= ge changes incorrectly generating spurious conflicts. To prevent this, perform= the following steps _before_ updating sources and building the new world: # etcupdate extract=20 # etcupdate diff=20 But I did this not _before_ but after having built world and kernels. Why? I thought I missed an important step so I did it afterwards. Maybe the hand= book needs an additional hint what to do when having built world (and seeking ad= vice after)?=20 Now if I had not read the ouput of pkg update which I usually do not, I wou= ld not have discovered that etcupdate failed (because of my misusage). I remem= ber that there was no output while running etcupdate showing anything. Adding s= ome verboseness might be improve usability.=20 Again thank you all for "debriefing" :) --=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-264067-227-CabxS6cnD0>