Got the initial repo built. You can access it by:
cat <<EOF>/etc/yum.repos.d/epel.repo || exit 1 [epel] name=Extra Packages for Enterprise Linux 7 - noarch baseurl=http://repo.medon.htt-consult.com/epel7/noarch enabled=1 #gpgcheck=1 #gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7 EOF
Note that is is on the 1st known production Centos7-arm server!
I don't know if the gpg signing done for epel carried over to my createrepo, and am not going to take the time to test it, but others can and tell me :)
I will set up a cron job to update this repo weekly. For example, roundcubemail is 1.1.3 with 1.1.4 in testing. At some point it will get moved, and I will pick it up on my weekly repo update.
This is TEMPORARY!
I do have a 3Mb uplink, but I really don't want to be the long-running home for this. At some point we want to get the epel team to at least provide a noarch repo, but prefereably the armv7 repo.
Now on to see if I now have everything, or if I DO need some specific armv7 rpms...
And of course, let me know if there are any problems, or any kudos....
Oh and if someone whats to take this over, I will share whatever help they need to do that!
On 30 decembrie 2015 16:44:33 EET, Robert Moskowitz rgm@htt-consult.com wrote:
Got the initial repo built. You can access it by:
cat <<EOF>/etc/yum.repos.d/epel.repo || exit 1 [epel] name=Extra Packages for Enterprise Linux 7 - noarch baseurl=http://repo.medon.htt-consult.com/epel7/noarch enabled=1 #gpgcheck=1 #gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7 EOF
Note that is is on the 1st known production Centos7-arm server!
I don't know if the gpg signing done for epel carried over to my createrepo, and am not going to take the time to test it, but others can and tell me :)
I will set up a cron job to update this repo weekly. For example, roundcubemail is 1.1.3 with 1.1.4 in testing. At some point it will get moved, and I will pick it up on my weekly repo update.
This is TEMPORARY!
I do have a 3Mb uplink, but I really don't want to be the long-running home for this. At some point we want to get the epel team to at least provide a noarch repo, but prefereably the armv7 repo.
Of course things would be different if you'd include arm packages, not only mirrored noarch content but for now if all you want is a public epel/noarch repo, the much more reliable approach is to edit the standard yum repo definitions as installed by epel-release and add includepkgs = noarch. You will retain access to everything that fedora's mirror system provides.
On 12/30/2015 10:13 AM, Manuel Wolfshant wrote:
On 30 decembrie 2015 16:44:33 EET, Robert Moskowitz rgm@htt-consult.com wrote:
Got the initial repo built. You can access it by:
cat <<EOF>/etc/yum.repos.d/epel.repo || exit 1 [epel] name=Extra Packages for Enterprise Linux 7 - noarch baseurl=http://repo.medon.htt-consult.com/epel7/noarch enabled=1 #gpgcheck=1 #gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7 EOF
Note that is is on the 1st known production Centos7-arm server!
I don't know if the gpg signing done for epel carried over to my createrepo, and am not going to take the time to test it, but others can and tell me :)
I will set up a cron job to update this repo weekly. For example, roundcubemail is 1.1.3 with 1.1.4 in testing. At some point it will get moved, and I will pick it up on my weekly repo update.
This is TEMPORARY!
I do have a 3Mb uplink, but I really don't want to be the long-running home for this. At some point we want to get the epel team to at least provide a noarch repo, but prefereably the armv7 repo.
Of course things would be different if you'd include arm packages, not only mirrored noarch content but for now if all you want is a public epel/noarch repo, the much more reliable approach is to edit the standard yum repo definitions as installed by epel-release and add includepkgs = noarch. You will retain access to everything that fedora's mirror system provides.
ARGH!!!
that simple? Shows what I don't know about yum; which is actually quite a lot!
It would actually be a bit more that that. You have to replace the $basearch with 'x86_64' as otherwise it would be looking for the armv7h repo!
Do you do that by having the 1st line in epel.repo be:
basearch=x86_64
?
Anyway, I learned a lot setting this up. And based on what happened when I set up my mailserver on RSEL6, I really expect to hit rpms from epel that I have to build for armv7h (or convince someone else to do it!).
You DO need gpg enabled here:
cat <<EOF>/etc/yum.repos.d/epel.repo || exit 1 [epel] name=Extra Packages for Enterprise Linux 7 - noarch baseurl=http://repo.medon.htt-consult.com/epel7/noarch enabled=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7 EOF
Works fine for what is there.
On 12/30/2015 09:44 AM, Robert Moskowitz wrote:
Got the initial repo built. You can access it by:
cat <<EOF>/etc/yum.repos.d/epel.repo || exit 1 [epel] name=Extra Packages for Enterprise Linux 7 - noarch baseurl=http://repo.medon.htt-consult.com/epel7/noarch enabled=1 #gpgcheck=1 #gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7 EOF
Note that is is on the 1st known production Centos7-arm server!
I don't know if the gpg signing done for epel carried over to my createrepo, and am not going to take the time to test it, but others can and tell me :)
I will set up a cron job to update this repo weekly. For example, roundcubemail is 1.1.3 with 1.1.4 in testing. At some point it will get moved, and I will pick it up on my weekly repo update.
This is TEMPORARY!
I do have a 3Mb uplink, but I really don't want to be the long-running home for this. At some point we want to get the epel team to at least provide a noarch repo, but prefereably the armv7 repo.
Now on to see if I now have everything, or if I DO need some specific armv7 rpms...
And of course, let me know if there are any problems, or any kudos....
Oh and if someone whats to take this over, I will share whatever help they need to do that!
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
-
Manuel Wolfshant -
Robert Moskowitz