[Solved] Update to 19.1.r1 --> back to 19.1_r33

Started by Space, January 22, 2019, 09:41:59 AM

Previous topic - Next topic
January 22, 2019, 09:41:59 AM Last Edit: January 22, 2019, 11:07:20 AM by Space
Hi,

I tried to update to 19.1.r1 but somehow it fails. I did the following:

- switch to dev branch -> update
- now I am on OPNsense 19.1.r_33-amd64
- check for updates -> unlock 19.1.r1 -> upgrade


Updating OPNsense repository catalogue...
pkg-static: Repository OPNsense has a wrong packagesite, need to re-create database
Fetching meta.txz: 100%    1 KiB   1.5kB/s    00:01
Fetching packagesite.txz: 100%  150 KiB 153.4kB/s    00:01
Processing entries: 100%
OPNsense repository update completed. 587 packages processed.
All repositories are up to date.
Checking for upgrades (136 candidates): 100%
Processing candidates (136 candidates): 100%
uhub2: 6 ports with 6 removable, self powered
Checking integrity... done (0 conflicting)
The following 136 package(s) will be affected (of 0 checked):

Installed packages to be REINSTALLED:
        pkg-1.10.5_5
        zip-3.0_1
        wpa_supplicant-2.7
        wireguard-go-0.0.20181222
        wireguard-0.0.20181218
...
Number of packages to be reinstalled: 136
[1/136] Reinstalling indexinfo-0.3.1...
[1/136] Extracting indexinfo-0.3.1: 100%
[2/136] Reinstalling readline-7.0.5...
[2/136] Extracting readline-7.0.5: 100%
...
Using existing user 'git_daemon'.
[136/136] Extracting git-2.20.1: 100%
Message from openssl-1.0.2q,1:

Edit /usr/local/openssl/openssl.cnf to fit your needs.
Message from python27-2.7.15:
... (all the other messages)
Checking integrity... done (0 conflicting)
Nothing to do.
pkg-static: Repository OPNsense has a wrong packagesite, need to re-create database
pkg-static: Repository OPNsense cannot be opened. 'pkg update' required
Nothing to do.
Please reboot.
... (reboot messages)
>>> Invoking early script 'update'
>>> Invoking early script 'configd'
Starting configd.
uhub3: 6 ports with 6 removable, self powered
>>> Invoking early script 'php'
Configuring PHP: OK
>>> Invoking early script 'backup'
>>> Invoking backup script 'captiveportal'
>>> Invoking backup script 'dhcpleases'
>>> Invoking backup script 'duid'
>>> Invoking backup script 'netflow'
>>> Invoking backup script 'rrd'
OK
Launching the init system...done.
... (init messages)


- then after the final reboot I am back at 19.1.r_33

Do you have any idea what could have gone wrong? I have tried to switch to production again as well. Same messages, same result.

Thanks and best regards,

    Space

Hi,

As weird as it may seem, the development package never has a fully qualified release name.

To finish the upgrade set your firmware flavour to "release". Check for update and update from the blue box.


Cheers,
Franco
"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT

Hm, for "Release Type" I only see "Production" and "Development"

January 22, 2019, 10:54:10 AM #3 Last Edit: January 22, 2019, 10:56:36 AM by Space
Ah, according to package I am on 19.1.r1 already - but somehow also not


base 19.1.r1 447.8MiB BSD2CLAUSE HardenedBSD userland set
...
opnsense-devel 19.1.r_33 25.2MiB BSD2CLAUSE OPNsense development package  
opnsense-lang 18.7.8 5.80MiB BSD2CLAUSE OPNsense translations  
opnsense-update 19.1.r1 154KiB BSD2CLAUSE OPNsense update utilities


But when I ask to check for updates it again wants to install it ...

Never mind ... I found it ... I used "Upgrade now" (the lower button) instead of the "Update now" (the top button). I did not see it as blue because I was on different OS Theme :)


Right, sorry, I meant "production" indeed.


Cheers,
Franco
"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT