Upgrade not normal

[yon]

I find upgrade not normal. it is not real upgrade any code.

[heper]

what is the problem exactly?

[cmb]

@heper:

what is the problem exactly?

Yeah, this. That seems all fine.

[yon]

@cmb:

@heper:

what is the problem exactly?

Yeah, this. That seems all fine.

now still not work.

Unlocking package pfSense-kernel-pfSense… done.
Downloading upgrade packages...
Checking for upgrades (2 candidates): .. done
Processing candidates (2 candidates): .. done
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
pfSense: 2.3.a.20151231.1326 -> 2.3.a.20160101.1521 [pfSense]

2 KiB to be downloaded.
Fetching pfSense-2.3.a.20160101.1521.txz: . done
Checking integrity… done (0 conflicting)
Upgrading necessary packages...
Checking for upgrades (2 candidates): .. done
Processing candidates (2 candidates): .. done
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
pfSense: 2.3.a.20151231.1326 -> 2.3.a.20160101.1521 [pfSense]
[1/1] Upgrading pfSense from 2.3.a.20151231.1326 to 2.3.a.20160101.1521…

Removing unnecessary packages... done.
Cleanup pkg cache... done.
Locking package pfSense-kernel-pfSense... done.
Success

[yon]

2.3-ALPHA (amd64)
built on Fri Jan 01 07:38:57 CST 2016
FreeBSD 10.2-STABLE

You are on the latest version.

pfSense system update

Current base system 2.3.a.20160101.1521
Latest base system 2.3.a.20160101.1521
System is up to date

[rbgarga]

@yon:

I find upgrade not normal. it is not real upgrade any code.

Since we are in alpha state now, pfSense main package version changes on every incremental build. So lets say a new version of an additional package (e.g. pfBlockerNG) was committed, then pfSense package version was incremented. If you don't have pfBlockerNG installed you will still see pfSense upgrade.