FreeBSD sources for 2.7.0 missing?

fabricioguzzy

@rmonster Are you compiling from the sources? There are 2 problems I am facing with the new 2.7.0 code.
1- The php-pfsense-module - The build.sh script doesn't work anymore while trying to rename the php-pfsense-module. (I use a different brand name)
2- There is a new package called "pfsense-repoc" that point to an internal Netgate URL, so it's not possible to compile it. This one is critical since one of the functions to update the repository is based on that binary file.

I have opened a ticket on redmine pointing to the php-module-error - Still missing one related to that psense-repoc package now.

Regards
Fabricio.

rmonster

@fabricioguzzy Hey i just got done building my module. It's for the Mac mini Fan.

I didn't have an issue when I copied the Git source to my freebsd vm and ran make.

I copied the module to my Pfsense and it's loading up fine.

https://github.com/pfsense/FreeBSD-src/tree/RELENG_2_7_0

fabricioguzzy

@rmonster OK, so you are compiling using the pfsense name. You didn't change the brand to something else, Am I right?
The problem happens when you compile the code using a different name, not pfsense.

razzfazz

This thread is about the FreeBSD sources for 2.7.0; branding etc. isn’t relevant to those.

razzfazz

We are just building kernel modules (and, in my case, a modified miniupnpd binary).

My understanding is that rebranding is intentionally ~~made difficult~~ not being facilitated, because it’s not in Netgate’s interest; this isn’t new for 2.7.0, either.

fabricioguzzy

@razzfazz Sure, and it wasn't my intention to hijack your topic. Sorry about that.
yeah, I am aware of netgate making it difficult to rebrand, but one thing is being difficult, the other is being impossible (cause the code is not available). This is supposed to be a COMMUNITY edition, not a close-source.

NollipfSense

@rmonster said in FreeBSD sources for 2.7.0 missing?:

It's for the Mac mini Fan.

That's exactly why I jump ship on the Mac Mini to avoid the fan issue.

razzfazz

@fabricioguzzy No worries, I just meant to point out why we didn’t run I to the issue you mentioned.

AFAIK the issues with the build system referencing private repos have existed since before CE was even a thing.

NicS

@razzfazz Do the following:

git fetch origin RELENG_2_7_0
git checkout RELENG_2_7_0

git rev-parse 686c8d3c1f0
686c8d3c1f043c03afbae4aac6068cf1778b0abf

git checkout 686c8d3c1f043c03afbae4aac6068cf1778b0abf

razzfazz

@NicS ?! I mentioned above that I saw the branch had been pushed?!