On 2015-06-01 19:42, Jacco Ligthart wrote:
On 06/01/2015 08:30 PM, Gordan Bobic wrote:
On 2015-06-01 19:05, Jacco Ligthart wrote:
On 05/31/15 17:17, Gordan Bobic wrote:
On 31/05/15 16:12, Gordan Bobic wrote:
Jacco,
I think I just found a bug - the epel-release package points at
upstream
Fedora which is x86 only. The repo file should probably pointing at
ftp.redsleeve.org (or better a mirror file listing our mirrors,
same as
our other repositories).
Aaand I just found the updated fixed epel-release package under
updates.
Right, I'm not touching anything further until an appropriate amount
of coffee has been consumed, I'm clearly not firing on all
cylinders.
hmm, I was not aware that I also build the epel-release package
normally
present in epel :)
I sort of builded all that was there, blindly :)
I'll remove this one.
I would also like to propose keeping the $repo-release packages in the
base repository, like Scientific Linux does. That way running straight
from the base image you can:
# yum install epel-release
# yum install $some-epel-package
That is exactly as it is now. there is an epel-release in 7.1-extras,
which is now part of the base repo.
Hmm... Extras should really be for more experimental stuff. How about
a el7-repos repository that ships with a .repo file in
redsleeve-release,
enabled by default, that includes just the extra release files for other
repositories (e.g. epel, extra, etc.)?
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users
