|
1
|
>>> Updating repositories metadata...
|
|
2
|
Updating pfSense-core repository catalogue...
|
|
3
|
pfSense-core repository is up-to-date.
|
|
4
|
Updating pfSense repository catalogue...
|
|
5
|
pfSense repository is up-to-date.
|
|
6
|
All repositories are up-to-date.
|
|
7
|
>>> Unlocking package pfSense-kernel-pfSense... done.
|
|
8
|
>>> Downloading upgrade packages...
|
|
9
|
Updating pfSense-core repository catalogue...
|
|
10
|
pfSense-core repository is up-to-date.
|
|
11
|
Updating pfSense repository catalogue...
|
|
12
|
pfSense repository is up-to-date.
|
|
13
|
All repositories are up-to-date.
|
|
14
|
Checking for upgrades (5 candidates): ..... done
|
|
15
|
Processing candidates (5 candidates): ..... done
|
|
16
|
The following 5 package(s) will be affected (of 0 checked):
|
|
17
|
|
|
18
|
Installed packages to be UPGRADED:
|
|
19
|
pfSense-repo-devel: 2.3.b.20160129.1031 -> 2.3.b.20160129.1948 [pfSense-core]
|
|
20
|
pfSense-rc: 2.3.b.20160129.1031 -> 2.3.b.20160129.1948 [pfSense-core]
|
|
21
|
pfSense-kernel-pfSense: 2.3.b.20160129.1031 -> 2.3.b.20160129.1948 [pfSense-core]
|
|
22
|
pfSense-default-config: 2.3.b.20160129.1031 -> 2.3.b.20160129.1948 [pfSense-core]
|
|
23
|
pfSense-base: 2.3.b.20160129.1031 -> 2.3.b.20160129.1948 [pfSense-core]
|
|
24
|
|
|
25
|
The process will require 19 KiB more space.
|
|
26
|
41 MiB to be downloaded.
|
|
27
|
Fetching pfSense-repo-devel-2.3.b.20160129.1948.txz: . done
|
|
28
|
Fetching pfSense-rc-2.3.b.20160129.1948.txz: . done
|
|
29
|
Fetching pfSense-kernel-pfSense-2.3.b.20160129.1948.txz: .......... done
|
|
30
|
Fetching pfSense-default-config-2.3.b.20160129.1948.txz: . done
|
|
31
|
Fetching pfSense-base-2.3.b.20160129.1948.txz: .......... done
|
|
32
|
Checking integrity... done (0 conflicting)
|
|
33
|
>>> Upgrading pfSense kernel...
|
|
34
|
Updating pfSense-core repository catalogue...
|
|
35
|
pfSense-core repository is up-to-date.
|
|
36
|
Updating pfSense repository catalogue...
|
|
37
|
pfSense repository is up-to-date.
|
|
38
|
All repositories are up-to-date.
|
|
39
|
Checking integrity... done (0 conflicting)
|
|
40
|
The following 2 package(s) will be affected (of 0 checked):
|
|
41
|
|
|
42
|
Installed packages to be UPGRADED:
|
|
43
|
pfSense-kernel-pfSense: 2.3.b.20160129.1031 -> 2.3.b.20160129.1948 [pfSense-core]
|
|
44
|
pfSense-rc: 2.3.b.20160129.1031 -> 2.3.b.20160129.1948 [pfSense-core]
|
|
45
|
|
|
46
|
The process will require 1 B more space.
|
|
47
|
[1/2] Upgrading pfSense-rc from 2.3.b.20160129.1031 to 2.3.b.20160129.1948...
|
|
48
|
[1/2] Extracting pfSense-rc-2.3.b.20160129.1948: . done
|
|
49
|
[2/2] Upgrading pfSense-kernel-pfSense from 2.3.b.20160129.1031 to 2.3.b.20160129.1948...
|
|
50
|
===> Keeping a copy of current kernel in /boot/kernel.old
|
|
51
|
[2/2] Extracting pfSense-kernel-pfSense-2.3.b.20160129.1948: .......... done
|
|
52
|
Upgrade is complete. Rebooting in 10 seconds.
|
|
53
|
>>> Locking package pfSense-kernel-pfSense... done.
|
|
54
|
__RC=0 __REBOOT_AFTER=10
|
|
55
|
Upgrading necessary packages...
|
|
56
|
Updating pfSense-core repository catalogue...
|
|
57
|
pkg: http://beta.pfsense.org/packages/pfSense_master_amd64_amd64-core/meta.txz: No address record
|
|
58
|
repository pfSense-core has no meta file, using default settings
|
|
59
|
pkg: http://beta.pfsense.org/packages/pfSense_master_amd64_amd64-core/packagesite.txz: No address record
|
|
60
|
Unable to update repository pfSense-core
|
|
61
|
Updating pfSense repository catalogue...
|
|
62
|
pkg: http://beta.pfsense.org/packages/pfSense_master_amd64_amd64-pfSense_master/meta.txz: No address record
|
|
63
|
repository pfSense has no meta file, using default settings
|
|
64
|
pkg: http://beta.pfsense.org/packages/pfSense_master_amd64_amd64-pfSense_master/packagesite.txz: No address record
|
|
65
|
Unable to update repository pfSense
|
|
66
|
All repositories are up-to-date.
|
|
67
|
Checking for upgrades (3 candidates): ... done
|
|
68
|
Processing candidates (3 candidates): ... done
|
|
69
|
|
|
70
|
pfSense-kernel-pfSense-2.3.b.20160129.1948 is locked and may not be modified
|
|
71
|
Checking integrity... done (0 conflicting)
|
|
72
|
The following 3 package(s) will be affected (of 0 checked):
|
|
73
|
|
|
74
|
Installed packages to be UPGRADED:
|
|
75
|
pfSense-repo-devel: 2.3.b.20160129.1031 -> 2.3.b.20160129.1948 [pfSense-core]
|
|
76
|
pfSense-default-config: 2.3.b.20160129.1031 -> 2.3.b.20160129.1948 [pfSense-core]
|
|
77
|
pfSense-base: 2.3.b.20160129.1031 -> 2.3.b.20160129.1948 [pfSense-core]
|
|
78
|
|
|
79
|
The process will require 19 KiB more space.
|
|
80
|
[1/3] Upgrading pfSense-repo-devel from 2.3.b.20160129.1031 to 2.3.b.20160129.1948...
|
|
81
|
[1/3] Extracting pfSense-repo-devel-2.3.b.20160129.1948: . done
|
|
82
|
[2/3] Upgrading pfSense-default-config from 2.3.b.20160129.1031 to 2.3.b.20160129.1948...
|
|
83
|
[2/3] Extracting pfSense-default-config-2.3.b.20160129.1948: . done
|
|
84
|
[3/3] Upgrading pfSense-base from 2.3.b.20160129.1031 to 2.3.b.20160129.1948...
|
|
85
|
===> Keeping a copy of current version mtree
|
|
86
|
[3/3] Extracting pfSense-base-2.3.b.20160129.1948: .. done
|
|
87
|
===> Removing schg flag from base files
|
|
88
|
===> Extracting new base tarball
|
|
89
|
===> Removing static obsoleted files
|
|
90
|
>>> Removing unnecessary packages... done.
|
|
91
|
>>> Cleanup pkg cache... done.
|
