redsleeve 7 repo

[Robert Moskowitz]

I pulled an old Pogo plug out of my dustbin and it has a rsel7  USB stick.

Got it to boot up, but I can get yum update to work as the urls are not
valid.

Can you please provide me with what I should use for mirror for base and
update or for baseurl?


thanks

And really, I am just trying to get this to work so I can give it away. 
If anyone wants it and will pay shipping....

Bob

[Gordan Bobic]

Have a look here:

https://ftp.redsleeve.org/pub/el7-devel/el7/7.9/

--
You received this message because you are subscribed to the Google Groups "redsleeve-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redsleeve-use...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/91940041-a9d0-ccab-b6e5-4b74fea178c0%40htt-consult.com.

[Robert Moskowitz]

Ok.   got yum update to run, but...

--> Processing Conflict: initscripts-9.49.53-1.el7.1.armv5tel conflicts redhat-release < 7.5-0.11
--> Finished Dependency Resolution
Error: initscripts conflicts with redsleeve-release-7-1.1503.el7.1.armv5tel
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

What should I do now?

Thanks

[Jacco Ligthart]

Hi Robert,

It looks like you are trying to update from 7.1 straight to 7.9. This should go well of course, but I don't think that it is really tested before ...

I think that you should also update the redsleeve-release package, which is in the 'extra' repo:

http://ftp.redsleeve.org/pub/el7-devel/el7/mirrors-extra

Probably easiest is update the redsleeve-release package first (manually ?) which should set all the locations for the repos right.

Jacco

To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/1d505a9e-e066-c65a-733f-fe31aa0181b4%40htt-consult.com.

[Robert Moskowitz]

Well I need a little more direction than this.

How do I just update extra by itself?  Extra is not even in my RedSleeve-base.repo yum file.

To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/535d2e0e-40c4-4366-3415-b7506f369b8d%40redsleeve.org.

[Jacco Ligthart]

this should do the trick:

yum update http://www.mirrorservice.org/sites/ftp.redsleeve.org/pub/el7-devel/el7/7.9/extra/RPMS/redsleeve-release-7-9.2009.el7.1.armv5tel.rpm

followed by a regular:

yum update

Jacco

To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/5d7c5d90-d5fb-6b83-46fa-53b8ee62f5e2%40htt-consult.com.

[Robert Moskowitz]

The extra update worked, but not the yum update.  Can't access any of the files.  Got a bunch of:

more 403
http://ftp.redsleeve.org/pub/el7-devel/el7/7.9/updates/RPMS/upstream/xz-5.2.2-2.
el7.armv5tel.rpm: [Errno 14] HTTP Error 403 - Forbidden
Trying other mirror.
xz-libs-5.2.2-2.el7.armv5tel.r FAILED                                          
http://ftp.redsleeve.org/pub/el7-devel/el7/7.9/updates/RPMS/upstream/xz-libs-5.2
.2-2.el7.armv5tel.rpm: [Errno 14] HTTP Error 403 - Forbidden
Trying other mirror.
wget-1.14-18.el7.1.armv5tel.rp FAILED                                          
http://ftp.redsleeve.org/pub/el7-devel/el7/7.9/base/RPMS/upstream/wget-1.14-18.e
l7.1.armv5tel.rpm: [Errno 14] HTTP Error 403 - Forbidden
Trying other mirror.
yum-3.4.3-168.el7.redsleeve.no FAILED                                          
http://ftp.redsleeve.org/pub/el7-devel/el7/7.9/base/RPMS/changed/yum-3.4.3-168.e
l7.redsleeve.noarch.rpm: [Errno 14] HTTP Error 403 - Forbidden
Trying other mirror.
yum-plugin-fastestmirror-1.1.3 FAILED                                          
http://ftp.redsleeve.org/pub/el7-devel/el7/7.9/base/RPMS/upstream/yum-plugin-fas
testmirror-1.1.31-54.el7.noarch.rpm: [Errno 14] HTTP Error 403 - Forbidden
Trying other mirror.
zlib-1.2.7-20.el7.armv5tel.rpm FAILED                                          
http://ftp.redsleeve.org/pub/el7-devel/el7/7.9/updates/RPMS/upstream/zlib-1.2.7-
20.el7.armv5tel.rpm: [Errno 14] HTTP Error 403 - Forbidden
Trying other mirror.

like for every file to download then:

Error downloading packages:
  e2fsprogs-libs-1.42.9-19.el7.armv5tel: [Errno 256] No more mirrors to try.
  python-slip-0.4.0-4.el7.noarch: [Errno 256] No more mirrors to try.
  policycoreutils-python-2.5-34.el7.armv5tel: [Errno 256] No more mirrors to try
.
  systemd-219-78.el7.7.armv5tel: [Errno 256] No more mirrors to try.
  bash-4.2.46-35.el7.armv5tel: [Errno 256] No more mirrors to try.
  libcap-ng-0.7.5-4.el7.armv5tel: [Errno 256] No more mirrors to try.
  rsync-3.1.2-12.el7.armv5tel: [Errno 256] No more mirrors to try.
  elfutils-default-yama-scope-0.176-5.el7.noarch: [Errno 256] No more mirrors to
 try.
  libgcc-4.8.5-44.el7.armv5tel: [Errno 256] No more mirrors to try.
  1:cups-libs-1.6.3-51.el7.armv5tel: [Errno 256] No more mirrors to try.
  32:bind-export-libs-9.11.4-26.P2.el7.13.armv5tel: [Errno 256] No more mirrors
to try.
  gtk2-2.24.31-1.el7.armv5tel: [Errno 256] No more mirrors to try.
  freetype-2.8-14.el7.1.armv5tel: [Errno 256] No more mirrors to try.
  nss-util-3.79.0-1.el7.armv5tel: [Errno 256] No more mirrors to try.
  libselinux-2.5-15.el7.armv5tel: [Errno 256] No more mirrors to try.
  1:dbus-libs-1.10.24-15.el7.armv5tel: [Errno 256] No more mirrors to try.
  acl-2.2.51-15.el7.armv5tel: [Errno 256] No more mirrors to try.
  gawk-4.0.2-4.el7.1.armv5tel: [Errno 256] No more mirrors to try.
  libnl3-3.2.28-4.el7.armv5tel: [Errno 256] No more mirrors to try.
  less-458-9.el7.armv5tel: [Errno 256] No more mirrors to try.
  glibc-common-2.17-326.el7.armv5tel: [Errno 256] No more mirrors to try.

and onward through the whole list of files.

My /etc/yum.repos.d/RedSleeve-base.repo

is:

# RedSleeve-base.repo
#
# The mirror system uses the connecting IP address of the client and the
# update status of each mirror to pick mirrors that are updated to and
# geographically close to the client.  You should use this for RedSleeve updates
# unless you are manually picking other mirrors.
#
# If the mirrorlist= does not work for you, as a fall back you can try the
# remarked out baseurl= line instead.
#
#

[base]
name=RedSleeve-$releasever - Base
#mirrorlist=http://ftp.mirrorservice.org/sites/ftp.redsleeve.org/pub/el7/packages/base/mirrors
baseurl=http://ftp.redsleeve.org/pub/el7-devel/el7/7.9/base/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-RedSleeve-7

#released updates
[updates]
name=RedSleeve-$releasever - Updates
#mirrorlist=http://ftp.mirrorservice.org/sites/ftp.redsleeve.org/pub/el7/packages/updates/mirrors
baseurl=http://ftp.redsleeve.org/pub/el7-devel/el7/7.9/updates/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-RedSleeve-7

So why the permissions problem?

thanks

To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/6f3bc2d0-4d30-1541-9428-461cde2b2af9%40redsleeve.org.

[Gordan Bobic]

I think I just fixed the problem with ftp.redsleeve.org, try it again.

You can (and probably SHOULD) also replace
baseurl=http://ftp.redsleeve.org/pub/el7-devel/el7/7.9/base/

with one of these:
baseurl=https://mirrorservice.org/sites/ftp.redsleeve.org/pub/el7-devel/el7/7.9/base/
baseurl=https://ftp.nluug.nl/pub/os/Linux/distr/redsleeve/el7-devel/el7/7.9/base/

> To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/a7d75f16-b0e6-d0c9-8be4-24a80592e99c%40htt-consult.com.

[Robert Moskowitz]

I switched to the mirrorservice url and got a bunch of:

https://mirrorservice.org/sites/ftp.redsleeve.org/pub/el7-devel/el7/7.9/base/RPMS/upstream/pcre-8.32-17.el7.armv5tel.rpm:
[Errno 14] curl#35 - "Peer reports incompatible or unsupported protocol
version."
Trying other mirror.
perl-Getopt-Long-2.40-3.el7.no FAILED
https://mirrorservice.org/sites/ftp.redsleeve.org/pub/el7-devel/el7/7.9/base/RPMS/upstream/perl-Getopt-Long-2.40-3.el7.noarch.rpm:
[Errno 14] curl#35 - "Peer reports incompatible or unsupported protocol
version."
Trying other mirror.
perl-5.16.3-299.el7.armv5tel.r FAILED
https://mirrorservice.org/sites/ftp.redsleeve.org/pub/el7-devel/el7/7.9/updates/RPMS/upstream/perl-5.16.3-299.el7.armv5tel.rpm:
[Errno 14] curl#35 - "Peer reports incompatible or unsupported protocol
version."

And it gave up.  I switched back and it is downloading and...

Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-RedSleeve-7


The GPG keys listed for the "RedSleeve-7 - Updates" repository are
already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.


 Failing package is: iwl4965-firmware-228.61.2.24-102.el7.1.noarch
 GPG Keys are configured as:
file:///etc/pki/rpm-gpg/RPM-GPG-KEY-RedSleeve-7

How can I get the right keys?

thanks

[Gordan Bobic]

That sounds like yum is too old to handle the current https protocols.
You could try http and see if that works, not sure what mirrorservice
supports. The other mirror may work better.
As for keys, I am not sure what keys Jacco uses these days. Isn't it
in the release package?

[Robert Moskowitz]

Well I did the extra update and it did not install any keys.

I changed gpgcheck=0 in the yum.conf and still got:

warning:
/var/cache/yum/arm/7/updates/packages/iwl4965-firmware-228.61.2.24-102.el7.1.noarch.rpm:
Header V4 RSA/SHA1 Signature, key ID 2ff3695b: NOKEY

Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-RedSleeve-7


The GPG keys listed for the "RedSleeve-7 - Updates" repository are
already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.


 Failing package is: iwl4965-firmware-228.61.2.24-102.el7.1.noarch
 GPG Keys are configured as:
file:///etc/pki/rpm-gpg/RPM-GPG-KEY-RedSleeve-7

[Gordan Bobic]

Not sure, it's been some years since I've last used RSEL7. Maybe Jacco
has a better idea where it's going wrong and wow to fix it.

[Jacco Ligthart]

The repofile from the 7.9 release package says:

gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redsleeve-7-testing

so that is the key that all packages are signed with.

Jacco

[Gordan Bobic]

Right, but which package contains that file in 7.9?
Looking at the error message, I think the problem is that the key is
the old key rather than the new key needed for 7.9.

> To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/e5200c58-4b5c-e959-f3bc-51b58d93c06c%40redsleeve.org.

[Jacco Ligthart]

That key is also in the same release package.
My understanding is that Robert has configured his system differently.
i.e. different keyfile that is mentioned in the repofile.
maybe the yum update did not overwrite the repofile, because the
original was changed. There might be a .rpmnew file in that directory.
If so, move it over the repofile that is now used.

Jacco

[Robert Moskowitz]

Put that in the .repo and the update is now going.

Whew!  I should get this done before I leave for a cyber symposium
tomorrow and can turn this unit off and move it my donate box...  :)

thanks!

btw, I change gpgcheck=0 in the .conf, and forgot to check that it is
set to =1 in the .repo.  grrr.

[Gordan Bobic]

On Mon, Feb 6, 2023 at 2:08 AM Robert Moskowitz <r...@htt-consult.com> wrote:

> and can turn this unit off and move it my donate box... :)

I can relate to that. I gave away all of my <= ARMv8 systems, probably
about 20 in total, with the exception of my Samsung Chromebooks (v1
and V2).