Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 31 Jan 2025 18:45:41 +0100
From:      Jan Bramkamp <crest@rlwinm.de>
To:        Chris <chris@tellme3times.com>
Cc:        freebsd-pkgbase@freebsd.org
Subject:   Re: Helpful wiki
Message-ID:  <62816E7F-7E51-4870-BE04-14AC4C5629E8@rlwinm.de>
In-Reply-To: <5ebabf1a-4624-4fc1-91c3-a5757e5f2d76@tellme3times.com>
References:  <5ebabf1a-4624-4fc1-91c3-a5757e5f2d76@tellme3times.com>

index | next in thread | previous in thread | raw e-mail


You forgot to delete the old libraries as last step of a major release upgrade. Most likely the switch from readline to editline. Finish your upgrade(s) and ports will build again.

> Am 29.01.2025 um 23:06 schrieb Chris <chris@tellme3times.com>:
> 
> Hi,
> 
> 
> I came across  https://wiki.freebsd.org/PkgBase#setup while researching an issue I had where freebsd-update messed up a remote system. I should say I messed up the remote system by skipping releases.
> 
> My issue was that I could no longer build ports because it would fail on devel/gettext-runtime. It would also fail on builworld and buildkernel.
> 
> This is a production system which I thought I would need to rebuid. The system was upgraded to 14.2-RELEASE and I followed the wiki since I understood it would fix the issues I was having.
> 
> After the "Six steps below are essential" I issued a "shutdown -r now" since very little else was configured. The system didn't respond to ssh. When I finally got to the location I saw that the system was running but had no Internet access because the /etc/rc.firewall was also replaced.
> 
> I think that a note on the wiki to remind admins that rc.firewall may also need to be replaced, as a 7th essential step, when working on a remote system, may be helpful.
> 
> 
> All said and done this saved me having to rebuild that system. Thank you.
> 


help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?62816E7F-7E51-4870-BE04-14AC4C5629E8>