Messages

1

Development and Code Review / Re: questions about contributing binary package repo and release engineering toolkit

« on: December 11, 2018, 01:57:00 pm »

Hello Franco

I have generated packages by using "make ports" command.

1.

I see these files on SETSDIR directory.

Code: [Select]

ls /usr/local/opnsense/build/19.1/amdb64/sets/
base-19.1.b_19-amd64.obsolete
base-19.1.b_19-amd64.txz
kernel-19.1.b_19-amd64.txz
packages-18.7.8_138-OpenSSL-amd64.tar

Looks like base and kernel packages are ready, but I am not sure about plugins, core build outputs.

Ports are ready on /usr/ports

Do you think that there is a missing file on sets directory?

2.

Without having an iso installation image file, how can I generate opnsense platform (including os) on a running freebsd 11.x system?

I am not sure but I have two ideas.

a) First one is installing it by using make buildkernel,buildworld,installkernel,installworlds commands.
https://people.freebsd.org/~rodrigc/doc/handbook/makeworld.html

following guide for building world and kernel on /usr/src directory.

b) Installing files in the /usr/local/opnsense/build/19.1/amdb64/sets/ directory.
If so how should install those files?

base-19.1.b_19-amd64.txz
kernel-19.1.b_19-amd64.txz
packages-18.7.8_138-OpenSSL-amd64.tar

I think I can install *.txz files by using pkg tool. What about packages-*.tar?
Is there a missing file?

3.

I built for 19.1 but package filename (packages-18.7.8_138-OpenSSL-amd64.tar
) includes 18.7.8, is that normal?


4.

I see comment char at the begining of the line which includes elasticsearch5 in config/19.1/ports.conf file.

If the futureproof is successful, we should remove comment char only and commit it. That will be enough for adding elasticsearch and its depends to installation right?

Cheers

2

Development and Code Review / Re: questions about contributing binary package repo and release engineering toolkit

« on: December 10, 2018, 06:45:34 pm »

Hello Franco,

I know I'm bugging you, but looks like I need more help.

I edited tools.git/Makefile and changed SETTINGS variable to 19.1 and when I run

Code: [Select]

make update
make release

command I got "Package file lists do not match" error. As per the on-screen instructions,
I executed "cd /usr/core; make plist-fix" command. This also did not fix the error.


I'm attaching some screenshots. Maybe they can shed more light.

I will try to delete src, tools, plugins, ports and core directories and I will try to build it again from scratch.

Maybe you advise another solution so I wanted to ask.

Your help much appreciated.

Cheers

3

Development and Code Review / Re: questions about contributing binary package repo and release engineering toolkit

« on: December 06, 2018, 08:58:15 pm »

Hello Franco,

1.

I want to build packages on the correct platform for 19.1 release, before you release it. So I understand that I need to compile opnsense master branch when its state came to 19.1 release candidate.

When Opnsense's src repo (base system and kernel) will be ready for opnsense 19.1 release candidate? Or is it ready now? (base system and kernel)

If it s not ready how should I test /usr/ports package creation tasks for 19.1 release. On which platform?

2.

You have 19.1b iso file. Do you think that I should use it for package creation tests of 19.1 release? If you confirm, I will checkout /usr/ports and I will try to run "make package-recursive" for elasticsearch5 on 19.1b system.

If it is suitable platform for the release (base system and kernel). I won't waste time with compiling whole OS.

3.

I think I should install latest state of master branch on opnsense/src repo for creating 19.1 beta platform.

How can I do that by using build system on the "FreeBSD 11.1"?

I tried to do that by using:

Code: [Select]

make update SETTINGS=19.1
make release VERSION=19.1

commands.

I got some errors with these commands. If my method is correct, and if you want I can share errors with you. If my method is not correct can you share correct commands?

4.

What kind of platform are you using for build task, each rebuild task is taking too much time you know

Thank you

Kind regards

4

Development and Code Review / Re: questions about contributing binary package repo and release engineering toolkit

« on: November 20, 2018, 02:27:45 pm »

Hello Ad and Franco,

Thank you for answers.

My first goal in this study is building elasticsearch5 package on the correct platform by using the correct port tree for opnsense 19.1. After built it I want to perform installation tests on the latest 19.1 iso version and if any problem happens I will try to fix it.

I have new questions.

1.

When I checked OS version on 19.1b installation I see:

Code: [Select]

11.2-RELEASE-p4-HBSD 4b21e5691ff

Which hardenedbsd installer iso is used for this version "11.2-RELEASE-p4-HBSD 4b21e5691ff"?

I am asking it becase if the version changes, I think we should rebuild and retest elasticsearch5 package on the new version as well.

2.

Do you think that should I use hardenedbsd latest stable 11 version for package build/installatıon tests for an option?  We are planning to use these packages on opnsense 19.1 version.

3.

For building elasticsearch5 package on opnsense 19.1b setup, I need a port tree.

a)
So for installing port tree I can use this repo:
https://github.com/HardenedBSD/hardenedbsd-ports

or

b)
this repo:
https://github.com/opnsense/ports

If you advise to use option b) https://github.com/opnsense/ports. I can't see any 19.1 version tag on the releases section (https://github.com/opnsense/ports/releases). Should I use master branch?

Which port tree should I use building elasticsearch5 on 19.1b version?

4.

I can't see any tags for 19.1 on core,ports repo, how can I build 19.1b version by using "make dvd" command on the build toolskit. Is it posible?

5.

I have discovered this repo for 19.1 version: https://github.com/opnsense/src/releases/tag/19.1.a
Do you advise building latest dvd iso from strach for elasticsearch5 depended package installation tests? If you think, dvd iso is not necessary for package installation tests maybe I should skip this requirement.






Kind regards

5

Development and Code Review / Re: questions about contributing binary package repo and release engineering toolkit

« on: November 16, 2018, 08:52:07 am »

Hello,

Which HardenedBSD version are we using on OpnSense 18.7 and 19.1?

    hardenedbsd-11-stable-20180808-1/   2018-08-08 17:08   -   
    hardenedbsd-11-stable-20180814-1/   2018-08-14 18:53   -   
    hardenedbsd-11-stable-20180826-1/   2018-08-26 21:16   -   
    hardenedbsd-11-stable-20180913-1/   2018-09-12 23:12   -   
    hardenedbsd-11-stable-20180927-1/   2018-09-27 18:51   -   
    hardenedbsd-11-stable-20181018-1/   2018-10-17 22:31   -   
    hardenedbsd-11-stable-20181104-1/   2018-11-04 21:11   -   
    HardenedBSD-11-STABLE-v1100056.8-amd64-disc1.iso (Latest stable)

I think on Opnsense 18.7 we are only using ports tree? or base system as well? What about 19.1? Is it completelty HardenBSD? I am asking it because I want to generate elasticsearch5 port/packages on the correct version for testing on OpnSense.

Kind regards

6

Development and Code Review / Re: questions about contributing binary package repo and release engineering toolkit

« on: November 13, 2018, 09:23:51 pm »

Hello Franco,

I want to ask some questions again.

1.

This pkg repo url is for latest 18.7 version I think:
https://pkg.opnsense.org/FreeBSD:11:amd64/18.7/latest/All/

And these are for specific tags:
https://pkg.opnsense.org/FreeBSD:11:amd64/18.7/MINT/18.7.6/OpenSSL/All/
https://pkg.opnsense.org/FreeBSD:11:amd64/18.7/MINT/18.7.5/OpenSSL/All/

Am I right?

2.

I need 18.7.6, 18.7.5, 18.7.4 iso files.
Where can I find old iso downloads?

3.

I want to build release iso file for a specific version.

I tried to build dvd with these commands on FreeBSD 11.10

Code: [Select]


# cd /usr
# git clone https://github.com/opnsense/tools.git
# cd tools
# git checkout 18.7.5

# cd /usr
# git clone https://github.com/opnsense/ports.git
# cd ports
# git checkout 18.7.5

# cd /usr
# cd tools
# make dvd


and I got this error:

Code: [Select]

>>> /usr/ports does not match expected branch: 18.7.5
>>> To continue anyway set PORTSBRANCH=HEAD

I passed it with:

Code: [Select]

make PORTSBRANCH=HEAD dvd

command. But I want to be sure I am running correct commands for generating native release dvd iso file for a specific tag.

I need i386 and amd64 iso files. If you can share correct commands I will be glad.

Thanks

Kind regards

7

General Discussion / old release download links

« on: November 13, 2018, 09:06:15 pm »

Hello,

Where can I find download links of iso images for old releases?

For instance: 18.7.4, 18.7.5, 18.7.6

I need those files for testing.

Kind regards

8

Development and Code Review / Re: questions about contributing binary package repo and release engineering toolkit

« on: November 10, 2018, 10:12:24 pm »

I discovered "Development manual" page on https://docs.opnsense.org/development/workflow.html, but I couldn't see any information about package repo management policy

Kind regards

9

Development and Code Review / questions about contributing binary package repo and release engineering toolkit

« on: November 10, 2018, 09:16:27 pm »

Hello,

I have some questions about contributing package repo for specific packages and engineering toolkit.

1.

If I want to contribute to this binary package repo:
https://pkg.opnsense.org/FreeBSD:11:amd64/18.7/latest/All/

Is there a specific procedure for this?

2.

Which repo address should be used for commiting packages?

3.

I have found this repo:
https://github.com/opnsense/ports

Do you generate all packages on the port tree?  Or how do you decide which packages will be published on the binary package repo?

4.

All minor versions are using the same repo?  For instance: 18.7.5 and 18.7.6 are using the same repo?

https://pkg.opnsense.org/FreeBSD:11:amd64/18.7/latest/All/


5.
I am trying to discover release engineering toolkit.

For generating 18.7.5 dvd .iso image I am running these steps on FreeBSD 11.10 x86_64:

Code: [Select]

cd /usr
# git clone https://github.com/opnsense/tools.git
# cd tools
# make update
# git checkout 18.7.5
# make iso

Is it correct method to do that?

6.


https://github.com/opnsense/tools

On the main documentation I see different commands like:
# make step OPTION="value"
# make base
# make nano
...

If I want to modify base system and create a dvd, can I do that with this tool? If you give an example, I will be glad. For instance: If I want to create a file on the base system like: /etc/egghunter-test what should I do?


Kind regards