Upgrading from old version (13.0-RELEASE-p4)

[Johan Helsingius]

Hi everyone,

I have a couple of servers (amd64) that have been turned off for
quite a while that I now need to reactivate. They are still running
13.0-RELEASE-p4, and when I try to update, I get "No mirrors
remaining, giving up".

Is there any way to upgrade without having to do a full reinstall?


Julf

[Eduardo Lemos de Sa]

Dear Johan

My suggestion is:

1) remove all files under /usr/src (including .git etc)

2) git clone --branch releng/13.2 https://git.FreeBSD.org/src.git /usr/src (as described in handbook)

3) cd /usr/src

4) make -j xx buildworld

5) make -j xx buildkernel

6) install them & reboot 

For future upgrades, I suggest:

cd /usr/src

git pull

followed by steps 4, 5, and so on...

My best wishes

Eduardo

--

Eduardo Lemos de Sa
Professor Titular
Dep. Quimica da Universidade Federal do Paraná
fone: +55(41)3361-3300
fax:   +55(41)3361-3186

[Dan Mahoney (Ports)]

If you’re getting the “No Mirrors Remaining” error, it may be that you’re pointing at the wrong update pool. Can you please post your /etc/freebsd-update.conf, if it’s changed from stock? (Also, any that may be in /usr/local/etc?)

I’ve used freebsd-update to update from releases as early as 8.x, there should be no need for a full buildworld (assuming you have enough disk space). Check your resolvers and firewall.

Worst case scenario, freebsd-update is a shell script. Add a -x to its shebang line as a debug.

This should be pretty easy to fix.

-Dan

[Odhiambo Washington]

On Fri, Sep 22, 2023 at 5:20 AM Eduardo Lemos de Sa <eduardo....@gmail.com> wrote:

Dear Johan

On Thu, Sep 21, 2023 at 11:40 AM Johan Helsingius <ju...@julf.com> wrote:

Hi everyone,

I have a couple of servers (amd64) that have been turned off for
quite a while that I now need to reactivate. They are still running
13.0-RELEASE-p4, and when I try to update, I get "No mirrors
remaining, giving up".

Is there any way to upgrade without having to do a full reinstall?


        Julf

My suggestion is:

1) remove all files under /usr/src (including .git etc)

2) git clone --branch releng/13.2 https://git.FreeBSD.org/src.git /usr/src (as described in handbook)

3) cd /usr/src

4) make -j xx buildworld

5) make -j xx buildkernel

6) install them & reboot 

For future upgrades, I suggest:

cd /usr/src

git pull

followed by steps 4, 5, and so on...

My best wishes

This procedure will change the version from RELEASE to STABLE. I don't think that is what the OP wants.

--

Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

[How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

[Polytropon]

On Thu, 21 Sep 2023 20:54:08 -0300, Eduardo Lemos de Sa wrote:
> [...]

> My suggestion is:
>
> 1) remove all files under /usr/src (including .git etc)
> 2) git clone --branch releng/13.2 https://git.FreeBSD.org/src.git /usr/src
> (as described in handbook)
> 3) cd /usr/src
> 4) make -j xx buildworld
> 5) make -j xx buildkernel
> 6) install them & reboot
>
> For future upgrades, I suggest:
> cd /usr/src
> git pull
> followed by steps 4, 5, and so on...

I also suggest to have a look at /usr/src/Makefile's
comment header, which is a great source for updating
procedures.


--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

[Matthew Seaman]

On 22/09/2023 08:37, Odhiambo Washington wrote:
>> 1) remove all files under /usr/src (including .git etc)

>> 2) git clone --branch releng/13.2https://git.FreeBSD.org/src.git

>> /usr/src (as described in handbook)
>> 3) cd /usr/src
>> 4) make -j xx buildworld
>> 5) make -j xx buildkernel
>> 6) install them & reboot
>>
>> For future upgrades, I suggest:
>> cd /usr/src
>> git pull
>> followed by steps 4, 5, and so on...
>>
>> My best wishes
>>
> This procedure will change the version from RELEASE to STABLE. I don't
> think that is what the OP wants.

No -- this will result in a 13.2-RELEASE-pN system as the OP wanted.
You're confusing the stable/13 branch with the releng/13.2 branch.

Cheers,

Matthew

[Johan Helsingius]

Now I feel really stupid - it was a DNS issue after all. Somehow my
/etc/resolv.conf had disappeared.

In my defence, the error message was somewhat misleading.

On 22/09/2023 02:44, Dan Mahoney (Ports) wrote:
> Check your resolvers and firewall.

That did it. Thanks!

Julf

[Graham Perrin]

On 22/09/2023 00:54, Eduardo Lemos de Sa wrote:
> 6) …

>
> For future upgrades, I suggest:
> cd /usr/src
> git pull
> followed by steps 4, 5, and so on...
>

> …
>
I'd use --ff-only for the pull.

[Kevin Oberman]

The git documentation for the pull command claims that --ff-only is the default. Is that incorrect? From "man git-pull":

      --ff-only
           Only update to the new history if there is no divergent local
           history. This is the default when no method for reconciling
           divergent histories is provided (via the --rebase=* flags).

--

Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkob...@gmail.com

PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683