Problem building 19.7a

[bimmerdriver]

It's fixed.

[franco]

Yes, the new PAM stuff is all sorted now.


Cheers,
Franco

[opnsenseuser]

problem "make upgrade"

Code: [Select]

pkg: No package(s) matching php71-phpseclib

Code: [Select]

pkg: No packages available to install matching 'php71-phpseclib' have been found

[franco]

You guys need to wait for new releases sometimes... we can't always have master ready for use... or just change the makefile... but please don't always report it.

[opnsenseuser]

sorry franco.

i thought we might have to use a particular parameter or switch again just like the squid problematic recently.

from now on I'll always wait a few days to post something. thanks,

best regards, rene

[franco]

Apologies, it has been a taxing week trying to balance a 19.1.3 release on top of discussions and the day job...

19.1.3 is out in a few minutes and phpseclib package will be available then.


Cheers,
Franco

[bimmerdriver]

problem "make upgrade"

Code: [Select]

pkg: No package(s) matching php71-phpseclib

Code: [Select]

pkg: No packages available to install matching 'php71-phpseclib' have been found

I'm using hyper-v, so I can easily checkpoint a VM and revert if there is a problem. I tried building the latest version. The same error occurred, but make completed, so I rebooted and gave it a try. It seems to work fine.

[franco]

The switch to PHP 7.2 happens some time next week. To upgrade before packages are in sync use:

# make upgrade CORE_PHP=71

Unfortunately we can't do hybrid environments of PHP 7.1 and 7.2 because there are upgrade bugs in the FreeBSD package tool being utterly confused by the choices.


Cheers,
Franco

[bimmerdriver]

Thank you for the heads-up.

I'm noticing that opnsense-update updates opnsense-devel from 19.7.a_272 to 19.7.a_288, but make-upgrade reverses it. Everything is working fine, otherwise. Is this expected behaviour?

[franco]

opnsense-update operates on packages mirror which are synched with every release. The corresponding devel version in 19.1.4 is 19.7.a_288. The master branch of core.git is currently at 19.7.a_363.

"make upgrade" doesn't reverse opnsense-update, it merely installs whatever checked out version of core.git you want it to upgrade to (git describe).

opnsense-update on the other hand only forward-updates.

So what you are seeing is normal: you actually downgrade using make upgrade from 288 -> 272 so opnsense-update will bring you back to 288. If you upgrade to 363 then opnsense-update will not bring you back to 288.

Use git-pull or opnsense-code to update your core repository. I guess the full sequence is this then:

# opnsense-update; opnsense-code core; make upgrade


Cheers,
Franco

[bimmerdriver]

Hi Franco,

Thank you very much for the explanation. I know you're busy. I really appreciate that you took the time to respond.

BR,
BD

[franco]

Hi BD,

No problem.

BTW, the PHP 7.2 change is in effect. The packages for PHP 7.2 will be released next week with 19.1.5.


Cheers,
Franco

[bimmerdriver]

Just rebuilt successfully. Now running OPNsense 19.7.a_368-amd64.

[bimmerdriver]

Just finished a successful build with the new 7.2 packages.

[bimmerdriver]

Updated from OPNsense 19.7.a_555-amd64 to OPNsense 19.7.a_561-amd64 this morning. There was an error after rebooting, which I reported. The update also broke IPv6.

Reverted to OPNsense 19.7.a_555-amd64. There was also an error after rebooting, which I reported, but IPv6 was working. Not sure how I missed the error after rebooting when I previously upgraded to OPNsense 19.7.a_555-amd64.

Reverted to OPNsense 19.7.a_516-amd64. No more error after rebooting.