[OBSOLETE] How to test the development version

[mmorev]

Thanks!
I have a new issue when building:

Code Select Expand

>>> Setting up /usr/core copy in /usr/obj/usr/tools/config/17.1/OpenSSL:amd64
fatal: ambiguous argument 'stable/17.1': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
*** Error code 128

Stop.
make: stopped in /usr/tools

There is core folder mentioned, i have forked its master branch to my own repo and made some minor changes in code. Could that be a cause of tools build failure?

[franco]

core.git's stable/17.1 branch was added a few days ago, simply do:

# cd /usr/core && git pull


Cheers,
Franco

[Solaris17]

core.git's stable/17.1 branch was added a few days ago, simply do:

# cd /usr/core && git pull


Cheers,
Franco

Thanks I am also going to give this a shot because my beta install is having issues updating every way thats posted.

EDIT:: Bah my main fear is not being able to upgrade into the RC or stable editions. currently checking for firmware updates yeilds no results (Im assuming this is intended) and git pull / make install requests are now failing. Bind910 among other dependencies it says it needs.

Should I really be going line by line and deleting these? Can I download a fresh copy of the file without the old entries.

[franco]

Hey Solaris,

Some packages changed, some got renamed in FreeBSD (openvpn -> openvpn23), which can only be tied together in points where we release a version like 17.1.b or the upcoming 17.1.r1 next week.

I think most of your trouble can be fixed with:

# make upgrade CORE_ABI=17.1

I expect the shifting of build bits to stop once 17.1.r1 (17.1-RC1) is out, because then it will be a full build like 16.7 has been for the last couple of months.


Cheers,
Franco

[Solaris17]

Hey Solaris,

Some packages changed, some got renamed in FreeBSD (openvpn -> openvpn23), which can only be tied together in points where we release a version like 17.1.b or the upcoming 17.1.r1 next week.

I think most of your trouble can be fixed with:

# make upgrade CORE_ABI=17.1

I expect the shifting of build bits to stop once 17.1.r1 (17.1-RC1) is out, because then it will be a full build like 16.7 has been for the last couple of months.


Cheers,
Franco

Hey Frano,

I appreciate the advice and I have seen that in the OP. Unfortunetely I have the same issues even with core ABI updates. IE

Code Select Expand

root@TDE-Core-Router:/usr/core # 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: openvpn23
*** Error code 1

Stop.
make[1]: stopped in /usr/core
*** Error code 1

Stop.
make: stopped in /usr/core
root@TDE-Core-Router:/usr/core #


I run into the same issues via

git pull
make install

I also cant (obviously) update via the firmware section in th GUI itself. What concerns me is that both of the GIT methodes fail and im concerned I won't be able to dig myself out to get into the RC and Stable builds.

EDIT:: I have even tried updating from console and reinstalling 17.1_b in the hopes it would fix whatever issues I was having.

[franco]

It's really not an issue to fix this...

The package updates we provide will work when they are published.

In the meantime there cannot be a guarantee that all repositories, in this case ports and core are always 100% in sync. You are currently relying on an older ports repository, but core wants a newer ports repository. In fact, it prevents you from upgrading into a yet unknown state, which is good.

I said it just then, openvpn got renamed to openvpn23, because openvpn package is now version 2.4 but we need to stay on 2.3 a bit longer:

https://github.com/opnsense/core/commit/1d694b2f29db6

In anything we try to do, we try not to brick installs for users. Errors like these are a healthy sign and with a bit of context they do make sense. :)


Cheers,
Franco

[Solaris17]

Awesome that makes much more sense thank you!

[Julien]

Done the update from17.7 however the Suricada is not starting.
this update is on a home box and not a productions
OPNsense 18.1.a_203-amd64
FreeBSD 11.0-RELEASE-p12
OpenSSL 1.0.2l 25 May 2017

[DanMc85]

I keep getting a Missing dependency: hostapd error when trying to run the make upgrade command.

[DanMc85]

I edited the Makefile to bypass the missing files (wpa_supplicant) was also missing.

OPNsense 18.1.a_261-amd64
FreeBSD 11.0-RELEASE-p12
OpenSSL 1.0.2l 25 May 2017

I thought it was supposed to include FreeBSD 11.1 ?

[franco]

Hi Dan,

We haven't fully updated the instructions yet. Normally, going through core.git upgrades the core UI/API package, nothing more.

The preferred method to do this now is simply:

# opnsense-update -t opnsense-devel

Which gives you no trouble with missing dependencies. We update the opnsense-devel package with each release.

This time around, the operating system will be shipped as a separate component to be installed at will. Since we can easily interchange 11.0 for 11.1, you can either choose the opnsense-devel package with it, or the normal release version.

Switching back to the release version:

# opnsense-update -t opnsense

We're still waiting for 17.7.6 to hit (tomorrow) because of an opnsense-update tweak that allows to lock the operating system updates in case people want to make sure they stay on the 18.1-BETA code during subsequent firmware updates. After that is out we will publish the remaining info as an official CFT.


Cheers,
Franco

[Julien]

Hi Franco,
any suggestions why the IDS won't start after the update?

[franco]

Which update do you speak of?

Maybe simply this bug?

https://github.com/opnsense/core/issues/1848

Fix via:

# rm /var/run/suricata.pid

We are fixing this in FreeBSD very soon. Suricata also needs updating to 4.0.1.


Cheers,
Franco

[Julien]

Which update do you speak of?

Maybe simply this bug?

https://github.com/opnsense/core/issues/1848

Fix via:

# rm /var/run/suricata.pid

We are fixing this in FreeBSD very soon. Suricata also needs updating to 4.0.1.


Cheers,
Franco

Thank you Franco, yes updating to V18.
just want to inform you about the Suricata it won't start.
Can we update Suricata to 4.0.1 or its not on yet ?
thank you for the great job.

[franco]

Did you delete the PID file and try to start it? ;)