Project

General

Profile

Bug #8892

2.3.5_2 does not offer update to 2.4.4-RC

Added by James Dekker over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Category:
Upgrade
Target version:
Start date:
09/13/2018
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.3.5_2
Affected Architecture:
All

Description

A user on 2.3.5, who upgrades to 2.3.5_2, then tries to upgrade to 2.4.4-RC is not able to see 2.4.4-RC.

Even on the correct update branch, only 2.3.5_2 is offered.

History

#1 Updated by Jim Pingle over 1 year ago

  • Assignee changed from Jim Pingle to Renato Botelho
  • Affected Version set to 2.3.5_2
  • Affected Architecture All added
  • Affected Architecture deleted ()

After selecting stable 2.4.x updates:

[2.3.5-RELEASE][root@pfSense.localdomain]/root: pfSense-upgrade -d -c
>>> Updating repositories metadata... 
Updating pfSense-core repository catalogue...
pkg-static: Repository pfSense-core has a wrong packagesite, need to re-create database
Fetching meta.txz: . done
Fetching packagesite.txz: . done
Processing entries: 
pkg-static: wrong architecture: FreeBSD:11:amd64 instead of freebsd:11:x86:64
pkg-static: repository pfSense-core contains packages with wrong ABI: FreeBSD:11:amd64
Processing entries... done
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: Repository pfSense has a wrong packagesite, need to re-create database
Fetching meta.txz: . done
Fetching packagesite.txz: .......... done
Processing entries: 
pkg-static: wrong architecture: FreeBSD:11:amd64 instead of freebsd:11:x86:64
pkg-static: repository pfSense contains packages with wrong ABI: FreeBSD:11:amd64
Processing entries... done
Unable to update repository pfSense
Error updating repositories!

If you manually run a package update, then it sees it, but also complains about a mismatch on the mtr-nox11 package:

[2.3.5-RELEASE][root@pfSense.localdomain]/root: pkg update
pkg: Warning: Major OS version upgrade detected.  Running "pkg-static install -f pkg" recommended
Updating pfSense-core repository catalogue...
pkg: Repository pfSense-core has a wrong packagesite, need to re-create database
Fetching meta.txz: 100%    944 B   0.9kB/s    00:01    
Fetching packagesite.txz: 100%    2 KiB   1.8kB/s    00:01    
Processing entries: 100%
pfSense-core repository update completed. 7 packages processed.
Updating pfSense repository catalogue...
pkg: Repository pfSense has a wrong packagesite, need to re-create database
Fetching meta.txz: 100%    944 B   0.9kB/s    00:01    
Fetching packagesite.txz: 100%  134 KiB 137.1kB/s    00:01    
Processing entries:   0%
Newer FreeBSD version for package pfSense-pkg-mtr-nox11:
To ignore this error set IGNORE_OSVERSION=yes
- package: 1102000
- running kernel: 1003000
Allow missmatch now?[Y/n]: y
Processing entries: 100%
pfSense repository update completed. 499 packages processed.
All repositories are up to date.

[2.3.5-RELEASE][root@pfSense.localdomain]/root: pfSense-upgrade -d -c
>>> 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.
>>> Upgrading pfSense-repo... 
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.
New version of pkg detected; it needs to be installed first.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
    pkg: 1.10.5 -> 1.10.5_4 [pfSense]

Number of packages to be upgraded: 1

The process will require 1 MiB more space.
3 MiB to be downloaded.
[1/1] Fetching pkg-1.10.5_4.txz: .......... done
Checking integrity... done (0 conflicting)
[1/1] Upgrading pkg from 1.10.5 to 1.10.5_4...
[1/1] Extracting pkg-1.10.5_4: .......... done
You may need to manually remove /usr/local/etc/pkg.conf if it is no longer needed.
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.
The following 2 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
    pfSense-repo: 2.3.5_8 -> 2.4.4.r.20180912.1506 [pfSense]
    pfSense-upgrade: 0.27_13 -> 0.50 [pfSense]

Number of packages to be upgraded: 2

18 KiB to be downloaded.
[1/2] Fetching pfSense-repo-2.4.4.r.20180912.1506.txz: . done
[2/2] Fetching pfSense-upgrade-0.50.txz: .. done
Checking integrity... done (0 conflicting)
[1/2] Upgrading pfSense-upgrade from 0.27_13 to 0.50...
[1/2] Extracting pfSense-upgrade-0.50: ..... done
[2/2] Upgrading pfSense-repo from 2.3.5_8 to 2.4.4.r.20180912.1506...
[2/2] Extracting pfSense-repo-2.4.4.r.20180912.1506: .......... done
2.4.4.r.20180912.1506 version of pfSense is available

#2 Updated by Renato Botelho over 1 year ago

  • Status changed from New to Feedback
  • Target version set to 2.4.4

pfSense-upgrade 0.51 (2.4.x) and 0.27_14 (2.3.5) are fixed

#3 Updated by James Dekker over 1 year ago

Tested 2.3.5_2 -> 2.4.4-RC without any manual intervention. Looks good.

#4 Updated by Renato Botelho over 1 year ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF