ARM development: next steps

arm

(Giacomo Sanchietti) #81

Just did a quick test using curl, seems good:

curl 'http://mirrorlist.nethserver.org/?release=7&repo=ce-updates&arch=aarch64&nsrelease=7.6.1810'
curl 'http://mirrorlist.nethserver.org/?release=7&repo=ce-updates&arch=armhfp&nsrelease=7.6.1810'

#82

it seems ok to me, for aarch64 and armhfp. tnx!

ops… i talked too early… i’ve done a full update, but now i got error on sclo which didn’t exist for aarch64

more tests, later…


(Davide Principi) #83

Please give me the official URLs [or open a PR for them]!


(Michael Träumner) #84

This is from nethserver repo file:

```
[ce-sclo-sclo]
name=CE-SCLo-sclo-$nsrelease
mirrorlist=http://mirrorlist.nethserver.org/?release=$releasever&repo=ce-sclo-s$
#baseurl=http://mirror.centos.org/centos/$nsrelease/sclo/$basearch/sclo/
gpgcheck=1
repo_gpgcheck=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-SCLo
enabled=0

[ce-sclo-rh]
name=CE-SCLo-rh-$nsrelease
mirrorlist=http://mirrorlist.nethserver.org/?release=$releasever&repo=ce-sclo-r$
#baseurl=http://mirror.centos.org/centos/$nsrelease/sclo/$basearch/rh/
gpgcheck=1
repo_gpgcheck=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-SCLo
enabled=0

Disabled it manually, like @dz00te said.


#85

sorry I do not think I understood :thinking:
the problem is that ther is no official url… i mean if you check a mirrror:
http://dallas.tx.mirror.xygenhosting.com/centos-altarch/7.6.1810/sclo/aarch64/
only sclo-rh exixst for aarch64, while for armhfp there is no sclo* at all

i don’t know if it’s possible to manage this from mirrorlist (that will be probably the best solution), otherwise the only solution i see is to change
“/etc/e-smith/templates/etc/yum.repos.d/NethServer.repo/10base”
check the arch and and enable/disable [ce-sclo-sclo]
and [ce-sclo-rh] depending on the arch… but probably i miss something… :sweat_smile:


(Davide Principi) #86

Yes, I forgot that …it’s the kind of input I need :smile:

IIRC packages that we recompile from EPEL and SCLo as dependencies for our modules will go to nethserver-updates/armhfp. Wherever an upstream mirror exists, mirrorlist will point to it.

Otherwise it could point to an empty/dummy repo and its packages are expected to be in nethserver-updates (or nethserver-base).