Jacco and I are working on cleaning up the EL6 repositories at the
moment to remove duplicate versions of different packages, make
sure that the directory tree is more sensibly arranged, and that
the packages are signed and the relevant keys in the new release
files.

Give us a few days to finalize it (and then a few extra days for
the mirrors to update, it may take a while as it will probably end
up involving all the mirrors pulling down anything up to 80GB
of data as all the paths change).

The current EL6 file set is about 80GB. I'm hoping it will
reduce by about half as we prune out the duplicates and remove
the old versions of packages.

Gordan

On 2016-02-24 18:35, Franchisseur Robert wrote:
-- Le (On) 2016-02-18 -0500 à (at) 12:32:51 Marc Curry écrivit (wrote): --

Yes, sorry -- the package locations/repos are confusing sometimes. I was
using:

baseurl=http://ftp.redsleeve.org/pub/el6/6.7/Redsleeve6.7/

in my repo file.

Gordan: can you sign the glibc packages when you get a chance?


       Yes, it is quite confusing. I found Jaco *signed* glibc in :


http://ftp.redsleeve.org/pub/el6/6.7/Redsleeve6.7-updates/Redsleeve6.7-updates/base/RPMS/changed/armv5tel/

       and a *not signed* in :

       http://ftp.redsleeve.org/pub/el6/packages/update/RPMS/armv5tel/

       There is also one signed in :

http://ftp.redsleeve.org/pub/el6/6.7/Redsleeve6.7/Redsleeve6.7/new

       but not in :

http://ftp.redsleeve.org/pub/el6/6.7/Redsleeve6.7/Redsleeve6.7/update

       nor in :


http://ftp.redsleeve.org/pub/el6/6.7/Redsleeve6.7/Redsleeve6.7/updates-testing


       So  in  order  to  get the good signed updates  I  put  the  4
       following  files in my /etc/yum.repo.d and a 'yum update'  was
       fine.


#------- 8><-------- /etc/yum.repos.d/el67.repo --------------

[el67]
name=RSEL 6.7
failovermethod=priority
mirrorlist=file:///etc/yum.repos.d/mirrors67
enabled=1
metadata_expire=0s
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redsleeve-release


#------- 8><-------- /etc/yum.repos.d/update67.repo ----------

[el67-update]
name=RSEL 6.7 Updates
failovermethod=priority
mirrorlist=file:///etc/yum.repos.d/mirrors67update
enabled=1
metadata_expire=0s
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redsleeve-6-testing


#------- 8><-------- /etc/yum.repos.d/mirrors67 --------------

http://www.mirrorservice.org/sites/ftp.redsleeve.org/pub/el6/6.7/Redsleeve6.7/
http://ftp.redsleeve.org/pub/el6/6.7/Redsleeve6.7/
http://ftp.nluug.nl/pub/os/Linux/distr/redsleeve/el6/6.7/Redsleeve6.7/

#------- 8><-------- /etc/yum.repos.d/mirrors67update --------

http://www.mirrorservice.org/sites/ftp.redsleeve.org/pub/el6/6.7/Redsleeve6.7-updates/Redsleeve6.7-updates/
http://ftp.redsleeve.org/pub/el6/6.7/Redsleeve6.7-updates/Redsleeve6.7-updates/
http://ftp.nluug.nl/pub/os/Linux/distr/redsleeve/el6/6.7/Redsleeve6.7-updates/Redsleeve6.7-updates/

       HTH.

<snip>


On Thu, Feb 18, 2016 at 11:53 AM, Jacco Ligthart <[email protected]>
wrote:

> <snip>
>
> apparently it's not my package your checking, but Gordan's :)
> mine does check:
> rpm -K glibc-2.12-1.166.el6.7.0.armv5tel.rpm
> glibc-2.12-1.166.el6.7.0.armv5tel.rpm: rsa sha1 (md5) pgp md5 OK
>
> Jacco

_______________________________________________
users mailing list
[email protected]
https://lists.redsleeve.org/mailman/listinfo/users

_______________________________________________
users mailing list
[email protected]
https://lists.redsleeve.org/mailman/listinfo/users

Reply via email to