ARM development: next steps


(Davide Principi) #21

@stephdl can we go with 1.8.3 for x86_64 too?

(Davide Principi) #22

Conditionals could be acceptable, but I’m not sure they’re really required. Instead, I think the mirrorlist nethserver.php script requires some changes for additional architectures.

(Mark Verlinde) #23

Agreed, works for me!

Yes some modules need to be blacklisted / or greylisted:

  • not all packages are ported, mainly those depending on a kmod package
  • some modules may turn out not to be feasible, this could be controlled with the comps file to.: meaning they are in the repo for those who want to install them but wont show up in the software-center
  • if a module has newer dependencies (rspamd as an example) they need to be held back until this dependency is in place. IIRC this works automatic with a repo closure method.

For simplicity I tend to be in favor to drop the (ns) epel mirror. Until now no update did actually cause to break something. Moreover maintenance of the repository has improved lately.

However the packages will remain unsigned and updates are released untested.

To keep momentum we can opt to omit the epel mirror in this stage, reaching in epel-pass-1 directly and decide how to handle this later (IIRC @dz00te suggesting this all along) .

I will proceed with some early testing; however my preference is to release the 7.6 alpha image based on the final repositories with corresponding packages for nethserver-realease and nethserver-mock.

(Stéphane de Labrusse) #24

we know a little issue, the history tab (in the UI is filled by the learn spam errors), I need to ask upstream.

This is just cosmetic, not blocking for the spam filtering

(Robert Moskowitz) #25

I now have my Odroid HC1 ready for testing. If I have figured this out right, the boot partition (and all the bootloader and uboot) cruft on the uSD card can stay in place, and I can just reimage the sata drive and test and reimage…

Is there a ‘simple’ way for me to get a working Nethserver going on it? Obviously the first thing will be to work it up as a mail server. As much as I need to replace my ClearOS PDC, I need to upgrade my public-facing (and public accessed) mail server.

I run a split-zone DNS (External and Internal) and for starters, I can do all my testing internally before I let it out loose on wild.

(Mark Verlinde) #26

Sorry, at the moment it is a bit stale because of the update to 7.6.1810.
I hope we have an offer end of the week.

(Mark Verlinde) #27

Found the issue why rspamd 1.8.2 does not compile with gcc 4.8.5. i’ll patch it to build.

(Stéphane de Labrusse) #28

1.8.2 gets the same issue, will try today to ask upstream

@davidep we should fix on rspamd-1.8.1 if it is not too late for NS7.6

(Giacomo Sanchietti) #29

Too late :slight_smile:

I don’t see any problem on using 1.8.1 or 1.8.3 for ARM.
Binary packages will differ for sure even for other applications.

(Davide Principi) #30

I’m setting up the repoclosure configurations. I’d need an rsync mirror :frowning:

Do you know if it (already) exists?

(Mark Verlinde) #31

As said before I do not know much (understatement) about repo mirror’s.
Can you try to explain what a rsync mirror is?

(Davide Principi) #32

Sorry for being too generic!

I’d need an rsync mirror of armhfp EPEL7. I couldn’t find one and I’m considering to fetch required data via http. I just need repodata/ contents to run repoclosure…

(Mark Verlinde) #33


(Stéphane de Labrusse) #34

yes…rspamd-1.8.3 brings some UI enhancements, it is good too

(Mark Verlinde) #35

It’s exiting seeing it grow and become factual :grinning:

Do I understand correctly the arm packges are uploaded (as example) to arm-base/armhfp/Packages and installed form base/armhfp/Packages ?

(Giacomo Sanchietti) #36

I’d say yes … let’s see if @davidep confirm if we both correctly understood how it work :wink:

(Davide Principi) #37

A post was split to a new topic: NethServer armhfp and aarch64 repositories

(Davide Principi) #38

I hope the new repositories work well. I’d expect some bugs, however I have to complete the mirrorlist fix now. I’d like to avoid forking the nethserver-release package and retain it as arch-independent.

Ok, I will handle it from mirrorlist.

NethServer armhfp and aarch64 repositories
(Davide Principi) #39

Ops! I forgot epel is not handled by :innocent:

I guess an ARM device must override epel-release by other means. For instance the basic image could provide a customized /etc/yum.repos.d/epel.repo.

(Mark Verlinde) #40

Sorry to be unclear

I meant a package containing repo-settings. in /etc/yum.repos.d/ for “epel”.