Project

General

Profile

Actions

Bug #7989

closed

Cannot update Nano from 2.3.4 to 2.3X snapshots

Added by Steve Wheeler over 6 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Category:
Upgrade
Target version:
Start date:
10/23/2017
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3.4_1
Affected Architecture:

Description

Testing using 2.3.4_1 Nano 64bit CE and trying to update to a 2.3.5 snapshot.

I can see the snapshot reported as avaliable once the correct branch is selected in update settings.

When I try to upgrade is the "Nanobsd is no longer supported...." error and the update quits.

Actions #1

Updated by Kill Bill over 6 years ago

You need to select the Security/Errata only branch in update settings.

Actions #2

Updated by Steve Wheeler over 6 years ago

Security/Errata is not a choice there. I have Stable, Development or Next Major Version.

Next major version obviously fails as there's no Nano in 2.4 but Dev shows the expected 2.3.5 snapshot.

[2.3.4-RELEASE][admin@xtm8.stevew.lan]/root: cat /usr/local/share/pfSense/pkg/repos/pfSense-repo-devel.conf
FreeBSD: { enabled: no }

pfSense-core: {
  url: "pkg+https://beta.pfsense.org/packages/pfSense_v2_3_amd64-core",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/local/share/pfSense/keys/pkg",
  enabled: yes
}

pfSense: {
  url: "pkg+https://beta.pfsense.org/packages/pfSense_v2_3_amd64-pfSense_v2_3",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/local/share/pfSense/keys/pkg",
  enabled: yes
}
>>> Updating repositories metadata... done.
2.3.5.a.20171022.0705 version of pfSense is available
[2.3.4-RELEASE][admin@xtm8.stevew.lan]/root: pfSense-upgrade
>>> Updating repositories metadata... 
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
**** WARNING ****

NanoBSD platform is no longer supported.

You can find instructions on how to convert it
/usr/local/libexec/pfSense-upgrade: to Full Installation at http://bit.ly/2wDinm8: not found
Actions #3

Updated by Kill Bill over 6 years ago

You have some weird system. It definitely is a choice here, and for others.

https://forum.pfsense.org/index.php?topic=138285.msg756148#msg756148

Actions #4

Updated by Jim Pingle over 6 years ago

  • Status changed from New to Confirmed
  • Assignee set to Renato Botelho

The difference appears to be in which version of pfSense-repo and pfSense-upgrade are on the box. Depending on the state of the system, it may or may not have the options you expect and even if it does, they may not work if the repo data and upgrade package are from 2.4, trying to upgrade you there.

There is some room for improvement here.

In the meantime, set the repo to "Development Snapshots" and then run this to get it to the expected state:

pkg install -fy pfSense-repo pfSense-upgrade

Actions #5

Updated by Renato Botelho over 6 years ago

  • Status changed from Confirmed to Feedback

New versions of pfSense-upgrade force to reinstall itself when version differs from remote repo. It should be enough

Actions #6

Updated by Jim Pingle over 6 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF