LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Fedora (https://www.linuxquestions.org/questions/fedora-35/)
-   -   Pidora YUM EXT errors. (https://www.linuxquestions.org/questions/fedora-35/pidora-yum-ext-errors-4175467045/)

jfbooth 06-22-2013 10:44 PM

Pidora YUM EXT errors.
 
Running Pidora on Raspberry Pi. First time with this OS. Running YUM EXT gives the following as it 'gets available updates':

Quote:

failure: repodata/repomd.xml from pidora-updates: [Errno 256] No more mirrors to try.
http://pidora.proximity.on.ca/pidora...ta/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden : http://pidora.proximity.on.ca/pidora...ata/repomd.xml
http://downloads.raspberrypi.org/pid...ta/repomd.xml: [Errno 14] HTTP Error 404 - Not Found : http://downloads.raspberrypi.org/pid...ata/repomd.xml

You can try starting 'yumex -n' from a command line
and deselecting the repositories causing problems
and try again.
I found a similar thread dated 2008 .. but it's content doesn't exactly match up to my situation. I am also a Linux rookie with most of my experience with Ubuntu.

Here is the content of /home/wacojohn/.config/yumex/yumex.config:

Code:

[yumex]
autorefresh = 1
recentdays = 14
proxy =
exclude =
debug = 0
color_install = darkgreen
color_update = red
color_normal = black
color_obsolete = blue
plugins = 1
yumdebuglevel = 2

I do not see yum.config .. or know where to look. Thank you in advance for any help.

EDIT: and here is output from terminal command:

Code:

[wacojohn@raspi ~]$ yumex -n

** (process:2154): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'

** (process:2154): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags'

** (process:2154): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags'
22:16:05 : INFO - Using config file : /home/wacojohn/.config/yumex/yumex.conf
22:16:05 : INFO - Using config file : /home/wacojohn/.config/yumex/yumex.conf
22:16:08 : DEBUG - network interface wlan0 (rt2800usb) is connected
22:16:09 : INFO - Connected to an network
22:16:09 : INFO - Starting yum child process
22:16:25 : INFO - YUM: Yum Version : 3.4.3
22:16:26 : INFO - YUM: Loaded plugins: presto
22:17:26 : INFO - Using config file : /home/wacojohn/.config/yumex/yumex.conf
22:17:26 : INFO - Using config file : /home/wacojohn/.config/yumex/yumex.conf
22:17:50 : INFO - Closing rpm db and releasing yum lock
22:17:50 : INFO - yum backend process is ended
22:17:50 : INFO - exitcode from backend : 0
[wacojohn@raspi ~]$]


slipstreamed 06-23-2013 03:27 AM

Yum config file is generally located in /etc you can open it using vim, gedit, nano etc
Code:

vim /etc/yum.conf
run
Code:

yum grouplist
and see if you're provided with any package categories.

Quote:

failure: repodata/repomd.xml from pidora-updates: [Errno 256] No more mirrors to try.
.repo files are stored in /etc/yum.repos.d and repomd.xml in /var/cache/yum/ (in fedora) since pidora is a fedora spin its only fair to assume that they'll be present in the same location in pidora as well, above failure is caused because yum ran out of available download locations or mirrors while installing or updating software.
It's strange that you're getting a 403 and 404 error from above locations, it is a possibility that the admin may have moved the repository to another location. Try http://pidora.ca/pidora/releases/18/packages/armhfp/os/
http://rpmfusion.org/Architectures/ARM
http://zenit.senecac.on.ca/wiki/inde...oving_Software

your yumex config and output from yumex -n looks ok
you can try deselecting the repos namely the ones with 403 and 404 and try running yum again also check you .repo files for any errors

jfbooth 06-23-2013 09:10 AM

Quote:

Originally Posted by slipstreamed (Post 4976941)
Yum config file is generally located in /etc you can open it using vim, gedit, nano etc
Code:

vim /etc/yum.conf

Got it yum.conf:

Code:

[main]
cachedir=/var/cache/yum/$basearch/$releasever
keepcache=0
debuglevel=2
logfile=/var/log/yum.log
exactarch=1
obsoletes=1
gpgcheck=1
plugins=1
installonly_limit=3

#  This is the default, if you make this bigger yum won't see if the metadata
# is newer on the remote and so you'll "gain" the bandwidth of not having to
# download the new metadata and "pay" for it by yum not having correct
# information.
#  It is esp. important, to have correct metadata, for distributions like
# Fedora which don't keep old packages around. If you don't like this checking
# interupting your command line usage, it's much better to have something
# manually check the metadata once an hour (yum-updatesd will do this).
# metadata_expire=90m

# PUT YOUR REPOS HERE OR IN separate files named file.repo
# in /etc/yum.repos.d

Quote:

run
Code:

yum grouplist
and see if you're provided with any package categories.
Code:

[wacojohn@raspi ~]$ yum grouplist
Loaded plugins: langpacks, presto, refresh-packagekit
http://pidora.proximity.on.ca/pidora/updates/18/armhfp/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden : http://pidora.proximity.on.ca/pidora/updates/18/armhfp/repodata/repomd.xml
Trying other mirror.
http://downloads.raspberrypi.org/pidora/updates/18/armhfp/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found : http://downloads.raspberrypi.org/pidora/updates/18/armhfp/repodata/repomd.xml
Trying other mirror.
http://pidora.proximity.on.ca/pidora/updates/18/armhfp/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden : http://pidora.proximity.on.ca/pidora/updates/18/armhfp/repodata/repomd.xml
Trying other mirror.
http://downloads.raspberrypi.org/pidora/updates/18/armhfp/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found : http://downloads.raspberrypi.org/pidora/updates/18/armhfp/repodata/repomd.xml
Trying other mirror.
Error: failure: repodata/repomd.xml from pidora-updates: [Errno 256] No more mirrors to try.
http://pidora.proximity.on.ca/pidora/updates/18/armhfp/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden : http://pidora.proximity.on.ca/pidora/updates/18/armhfp/repodata/repomd.xml
http://downloads.raspberrypi.org/pidora/updates/18/armhfp/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found : http://downloads.raspberrypi.org/pidora/updates/18/armhfp/repodata/repomd.xml
[wacojohn@raspi ~]$


Quote:

.repo files are stored in /etc/yum.repos.d and repomd.xml in /var/cache/yum/ (in fedora) since pidora is a fedora spin its only fair to assume that they'll be present in the same location in pidora as well, above failure is caused because yum ran out of available download locations or mirrors while installing or updating software.

I can provide quotes on the 5 files in /etc/yum.repos.d/ at your request.

/var/cache/yum involves a pretty extensive tree structure .. lots of folders/levels/files. I found a repomd.xml file in /var/cache/yum/armhfp/18/pidora/

If you want to see it, I will provide its content.

Quote:

It's strange that you're getting a 403 and 404 error from above locations, it is a possibility that the admin may have moved the repository to another location. Try http://pidora.ca/pidora/releases/18/packages/armhfp/os/
http://rpmfusion.org/Architectures/ARM
http://zenit.senecac.on.ca/wiki/inde...oving_Software
By that, you mean browse to those URLs ... like with a web browser? OK:

Quote:

Not Found

The requested URL /pidora/releases/18/packages/armhfp/os/"]http://pidora.ca/pidora/releases/18/packages/armhfp/os/ was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
I get a login page at http://rpmfusion.org/Architectures/ARM

I get a Wiki page at:

http://zenit.senecac.on.ca/wiki/inde...oving_Software

Quote:

your yumex config and output from yumex -n looks ok
you can try deselecting the repos namely the ones with 403 and 404 and try running yum again also check you .repo files for any errors
If I deselect a repository which is unavailable and don't select one that is .. how will I get updates etc?

I REALLY appreciate your help. I just wanted to update a new installation of Pidora ... yes brand new install.

slipstreamed 06-23-2013 01:25 PM

Ok, your yum.conf looks alright run
Code:

yum clean all
and now try again installing or updating a package, what this command will do is clear all previously cached info, metadata, package rpms from respective databases and directories.
Again
Code:

yum grouplist
fails to provide any available package groups and the reason is straightforward, yum is not able to access any content on the URL provided. The URL don't provide any info related to packages/updates whatsoever i opened http://pidora.proximity.on.ca/pidora/updates/18/ in my browser and there are no directories regarding updates on that server same with http://downloads.raspberrypi.org/pidora/updates/18/ have you tried installing/updating via yum before you encountered this problem? and did it work?
I did find some repos at http://downloads.raspberrypi.org/pid...tes/18/armhfp/ and http://pidora.proximity.on.ca/pidora...tes/18/armhfp/
Post the contents of all the files present in your yum.repos.d so i can have a look at it but judging by the yum output the problem is non-availability of valid download locations i think.

Code:

/var/cache/yum
caches and saves info regarding yum transactions(any metadata, repomd.xml files, headers and rpms if you've enabled it yum.conf etc) with a subdirectory for each configured repository. The directory
Code:

packages/
inside of each subdirectory maintains the packages in the cache. For example, /var/cache/yum/x86_64/18/fedora/packages maintains the downloaded packages of the fedora repository. The URLs i provided in my previous post may contain some helpful information about architecture and package management.
Quote:

If I deselect a repository which is unavailable and don't select one that is .. how will I get updates etc?
what i meant was that you could deselect the repositories that are giving you trouble and select only those which are available and try updating/installing packages.

jfbooth 06-23-2013 03:49 PM

Quote:

Originally Posted by slipstreamed (Post 4977155)
Ok, your yum.conf looks alright run
Code:

yum clean all
and now try again installing or updating a package, what this command will do is clear all previously cached info, metadata, package rpms from respective databases and directories.

Code:

[wacojohn@raspi ~]$ yum clean all
Loaded plugins: langpacks, presto, refresh-packagekit
Cleaning repos: pidora pidora-rpfr-updates pidora-updates
Cleaning up Everything
Cannot remove rpmdb file /var/lib/yum/rpmdb-indexes/version
No delta-package files removed by presto
[wacojohn@raspi ~]$

then I tried to update again ... no fix.

Again:

Quote:

failure: repodata/repomd.xml from pidora-updates: [Errno 256] No more mirrors to try.
http://pidora.proximity.on.ca/pidora...ta/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden : http://pidora.proximity.on.ca/pidora...ata/repomd.xml
http://downloads.raspberrypi.org/pid...ta/repomd.xml: [Errno 14] HTTP Error 404 - Not Found : http://downloads.raspberrypi.org/pid...ata/repomd.xml

You can try starting 'yumex -n' from a command line
and deselecting the repositories causing problems
and try again.
I am about brain dead with all the tutelage ...appreciate it ...just lettin you know I may have trouble following you from here on out. It's not you, ... it's me. Guess I am saying I may not be able to 'keep up' .... but I will try. Thank you immensely for your help.


EDIT: Just found this thread at another forum ... looks like the same situation. Would you take a look at it, please ... and tell me what you think?

http://www.raspberrypi.org/phpBB3/vi...0e6bae#p375193

knudfl 06-23-2013 04:35 PM

# 3 .
Quote:

If I deselect a repository .... .. how will I get updates etc ?
There are no updates, and there is no "repodata" for updates :
http://pidora.proximity.on.ca/pidora/updates/18/


So far you can just disable "updates" : enabled=0
.. in /etc/yum.repos.d/<file.repo>
( May be check at a later time, if the folder "repodata/" appears again ..
http://pidora.proximity.on.ca/pidora/updates/18/ )

-

jfbooth 06-23-2013 04:46 PM

Quote:

Originally Posted by knudfl (Post 4977228)
# 3 .

There are no updates, and there is no "repodata" for updates :
http://pidora.proximity.on.ca/pidora/updates/18/


So far you can just disable "updates" : enabled=0
.. in /etc/yum.repos.d/<file.repo>
( May be check at a later time, if the folder "repodata/" appears again ..
http://pidora.proximity.on.ca/pidora/updates/18/ )

-

??? Remember, I am a rookie . are you saying there are no updates to Pidora at this time and that is why all the 'errors'? Are you saying when there are some, .. YUM EXT will get them instead of erroring? If yes ... I'm good with that. If I got that right, thank you, .. if not, please explain. Thank you in any case.

knudfl 06-23-2013 05:01 PM

# 7 .

Click the link to check for the presence of "repodata" :
If repodata for updates ever appears again, then you can do # yum update

slipstreamed 06-23-2013 06:26 PM

@jfbooth
Quote:

are you saying there are no updates to Pidora at this time and that is why all the 'errors'?
yes that is exactly what knudfl is implying, when you update/install any package via command line or GUI(Yum Extender), yum reads .repo files from /etc/yum.repos.d to determine which locations to look at for a specified package, for example a .repo file from my system looks like

Code:

[rpmfusion-nonfree] 
name=RPM Fusion for Fedora $releasever - Nonfree 
#baseurl=http://download1.rpmfusion.org/nonfree/fedora/releases/$releasever/Everything/$basearch/os/ 
mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree-fedora-$releasever&arch=$basearch   
enabled=1
metadata_expire=7d
gpgcheck=0

Code:

[rpmfusion-nonfree]
--> repository identifier, must be unique
Code:

name=RPM Fusion for Fedora $releasever - Nonfree
--> a friendly name for the repository
Code:

#baseurl=http://download1.rpmfusion.org/nonfree/fedora/releases/$releasever/Everything/$basearch/os/
--> yum searches for packages at this address, but this address is commented out (see # before baseurl) this also points to the directory where 'repodata' is. In your case you are getting errors 404,403 because there is no repodata directory present on the servers. As pointed out by knudfl there are no updates currently available for your system.
Code:

mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree-fedora-$releasever&arch=$basearch
--> as 'baseurl' is commented out yum will use this URL for packages.
Code:

enabled=1
--> valid values are 0 or 1, tells yum whether to use this repository or not (1 for enabled, 0 for disabled)
Code:

metadata_expire=7d
--> specifies duration for which yum will store the metadata here it is 7 days.
Code:

gpgcheck=0
--> can be '1 'or '0', tells yum whether or not to perform a GPG verification on packages obtained from this repository.

The repo URLs also have all the packages available for download so a user may download them manually without using yum or other package managers. See http://download1.rpmfusion.org/nonfr...ing/x86_64/os/
Again in your case the URLs which your yum searches for updates currently have no listed updates that's why you are getting those errors, you can check them from time to time from your browser to see if any new updates have been published or not.
Also yum will not automatically update your packages you can either do it via command line
Code:

yum update <packagename>
or via Yum extender.

jfbooth 06-23-2013 09:01 PM

well, .. between knudfl's input (the man is obviously a genius) and this latest genius gem ... I think I understand. Thank you both. One thing though:

When I run Yum Extender, it tries to get updates .... when it fails, it closes. So that is because there aren't any ... I get that.

But Yum Extender is supposed to also do other things ... right? Like offer different packages to install as desired ... or UNinstall if no longer desired ... much like Synaptic Package Manager in Debian. Right? At the moment, it appears to default to UPDATES and when that errs, it closes. So how do I get it to ... oh, ... offer Bleachbit (for example) ... or a printer package, or, or, or?

I just now clicked on http://download1.rpmfusion.org/nonfr...ing/x86_64/os/ and this is what I got (from OPEN DNS on a WINDOWS machine):

Quote:

Hmm, pidora.proximity.on.ca isn't loading right now.

The servers that run pidora.proximity.on.ca are having some trouble. This is usually just a temporary problem, so you might want to try again in a few minutes.
EDIT: With input from another forum on this issue, I have come to the conclusion that the 'Pidora organization' is lax in managing the project ... and this issue has been an ongoing thing. On that note, I am going to replace it with the Debian OS for the Raspberry Pi known as Raspbian. Thank you all .. immensely .. for your wisdom, valuable time, attitude, and help. I have learned more than is evident thanks to you.

Thank you again.


All times are GMT -5. The time now is 05:11 AM.