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…
yes…rspamd-1.8.3 brings some UI enhancements, it is good too
It’s exiting seeing it grow and become factual 
Do I understand correctly the arm packges are uploaded (as example) to arm-base/armhfp/Packages and installed form base/armhfp/Packages ?
2 Likes
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.
1 Like
Ops! I forgot epel is not handled by mirrorlist.nethserver.org 
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.
1 Like
Sorry to be unclear
I meant a package containing repo-settings. in /etc/yum.repos.d/ for “epel”.
1 Like
getting closer
Install from new repositories 
hurdles on first site:
- the already mentioned comps groups, not all modules showing up in software center are available
- nextcloud being a noarch which differs from x86_64 (remi php72)
- probably a lot more…
2 Likes
great! 
let me know if i can help in testing…
1 Like
well here is problem…
I did import all keys upfront
rpm --import /etc/pki/rpm-gpg/*
a manual install
yum install @nethserver-directory
answering y to all key suggestions and its oke…
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-NethServer-7
Importing GPG key 0x39BAF5C1:
Userid : "NethServer 7 (NethServer 7 Official Signing Key) <security@nethserver.org>"
Fingerprint: 594c 3fd8 fae1 8ff5 32fe ae23 9cb2 8ea0 39ba f5c1
Package : nethserver-release-7-11.ns7.noarch (@nethserver-arm-base/$releasever)
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-NethServer-7
Is this ok [y/N]: y
nethserver-base/7/armhfp/signature | 2.9 kB 00:00:14 !!!
nethserver-updates/7/armhfp/signature | 836 B 00:00:00
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-NethServer-7
Importing GPG key 0x39BAF5C1:
Userid : "NethServer 7 (NethServer 7 Official Signing Key) <security@nethserver.org>"
Fingerprint: 594c 3fd8 fae1 8ff5 32fe ae23 9cb2 8ea0 39ba f5c1
Package : nethserver-release-7-11.ns7.noarch (@nethserver-arm-base/$releasever)
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-NethServer-7
Is this ok [y/N]: y
After this installs work form the software center too.
Probably uname -m doesn’t work as expected here
1 Like
good catch !
# uname -m
armv7l
Did I mention naming of arm32 bit is mess before ? (just kidding although true… 
)
1 Like
We need to extract the YUM arch… 
# python -c 'import yum, pprint; yb = yum.YumBase(); pprint.pprint(yb.conf.yumvar, width=1)'
Loaded plugins: fastestmirror, nethserver_events
{'arch': 'armv7hnl',
'basearch': 'armhfp',
'contentdir': 'altarch',
'infra': 'stock',
'kvariant': 'rpi2',
'nsrelease': '',
'releasever': '7',
'uuid': 'a0cc8187-be28-43ab-a87f-9e05463a0a9b'}
does this help?
1 Like
or if you have proxmox 5.3, a good server and (a lot of) patience 
you can use proxmox for aarch64, or at least i just managed to install centos 7.6 aarch64… a little bit slow but it seems to work
3 Likes
To manage this nethserver-arm-epel with exclusive arch armv7hl is provided. To “fool” yum this package provides “epel-release”. This breaks with the old caution not to imply a official epel-release is available. Opted for this to be compatible with nethserver-release.
Since we shifted to zram, we have a noarch package to set zram-swap up. I wonder if this package could live in the x86_64 too? And with this in all repo’s which would make image creation a bit more straight forward. Not a big deal just a bit cleaner…
EDIT:
If we can agree on the above i would like to ship ownership of the git repository’s to nethserver.
Yes, I think we can put it also on x86_64.
Can you give me the pointer to the RPM or repo, just to make a couple of checks?