[OBSOLETE] How to test the development version

[franco]

Instructions in the original post have been updated.

[Dean E. Weimer]

My system doesn't seem to want to update, if I do the make upgrade CORE_ABI=17.1 step I get this.

Code: [Select]

#make upgrade CORE_ABI=17.1
/usr/core/+POST_INSTALL -> /usr/core/work/src/+POST_INSTALL
/usr/core/+PRE_DEINSTALL -> /usr/core/work/src/+PRE_DEINSTALL
>>> Missing dependency: bind911
*** Error code 1
when I did the opnsense-update -t opnsense-devel it did install some updates, the system reports its up-to-date and even shows 17.1.b14 as the version, but its still running 10.3, and still has PHP 5.6 packages instead of the php 7.0

[franco]

Delete bind911 dependency line from Makefile and rerun. The system will fix itself, although it may be that more steps are needed since it's not on 11.0 yet.

What does this do:

# opnsense-verify -a


Cheers,
Franco

[Dean E. Weimer]

root@opnsense:/usr/core # opnsense-verify -a
FreeBSD:10:amd64

[Dean E. Weimer]

It appears to be stopping on everything uses the variable ${CORE...} that is missing, so the bigger question is why isn't it updating the base OS when switching to the devel branch?

[franco]

Because the vital step is missing?

Console Option 12, type "17.1.b".

Make sure you have pkg 1.9.3_1 installed, pkg 1.9.3 is buggy:

# pkg query %v pkg


Cheers,
Franco

[Dean E. Weimer]

OK, when doing option 12 it had 17.1.b listed, but apparently typing yes didn't suffice, I typed 17.1.b instead of y and it downloaded and installed the rest of the updates. so its running normally now after the reboot.

[franco]

Perfect

[tillsense]

hi franco,

Instructions in the original post have been updated.

from the second time the howto should be supplemented: (if this is your preferred way)

Code: [Select]

# cd /usr/core/
# git pull
# make upgrade CORE_ABI=17.1

cheers till

[franco]

I added the git pull in there, thanks!

[Julien]

is the 17.1 will fix the multi wan issue?
hopefully it will.

[franco]

Yes, we have started a new test round yesterday for IPv4 only. We need to see if it is reliable enough for 17.1 in the next week.

The same work is going into FreeBSD as well, but covers more use cases so that work progresses a lot slower (hopefully FreeBSD 12.0).

[franco]

Here is a test kernel, participation welcome.... https://forum.opnsense.org/index.php?topic=4170

[mmorev]

Hi! I want to try develop some additions to opnsense Web Proxy module and append sssd package/plugin. How should I build current 17.1 images from sources for testing? There are instructions for building 16.7 on github.com/opnsense/tools page, when I follow them, make cdrom says:

Code: [Select]

>>> Running build step: ports
>>> /usr/src does not match expected branch: stable/16.7
>>> To contunue anyway set SRCBRANCH=master
*** Error code 1And if I set SRCBRANCH to master, build fails on ngattach, which afaik shouldn't be there for 17.1 (link).

Btw, 2 more questions:
- Should building vm have exactly 6 GB of RAM as said on tools page, or I can assign, for example, 5,5? My pc has only 8 and goes slow.
- For building 17.1 should I use FreeBSD 10.3 or 11.0?

[franco]

# make cdrom SETTINGS=17.1

Or edit tools.git/Makefile to default to 17.1 there.

16.7 is the release branch, so the build tools still build it by default. I recently added safeguards to see whether branches match because things like ngattach clashed from time to time with users. As for ngattach itself, it was a very ancient workaround that has since been removed, restoring binary compatibility with FreeBSD.

You can try with less RAM. 6 GB was for building "make nano" in RAM, it needed 4 GB for the image. These days it doesn't require RAM anymore, I will change the documentation to say "at least 4 GB" right now.

For 17.1 you can use FreeBSD 10.3 or 11.0, but since 17.1 is based on 11.0 building the initial FreeBSD sets (base and kernel) is faster on 11.0. I recommend 11.0 as it should also build 16.7 if need be.


Cheers,
Franco