Red Hat Bugzilla – Bug 432297
Repository Manager mishandles repo paths with spaces
Last modified: 2009-01-06 05:13:19 EST
Description of problem: if the Repository Manager is given a repo url, such as
"file://mnt/repo data/repomd.xml" is given as the location for a repository, it
will work fine for that session of Package Manager (PM, or Add/Remove
Software), but when you try to fire up PM again, it errors out (see attached
Version-Release number of selected component (if applicable): pirut-1.3.25-2.fc8
How reproducible: always
Steps to Reproduce:
1. See description
Actual results: See description
Expected results: Error from Repository manager that the url is invalid
Additional info: In this example, "file://mnt/repo%20data/repomd.xml", would
Created attachment 294530 [details]
Dump of PM when you try to start it after setting the bad repo url
Sorry for the redundant "is given" in the description.
Also, I'd like to suggest that the debug output could display the path, such as
"/etc/yum.repos.d/Fedora-install-media.repo", of the config file containing the
invalid url. Since I'm relatively unfamiliar with yum/pirut, it took a bit of
doing to nose out the location of this file, so I could fix it and start PM
What version of yum, pirut and python-iniparse do you have installed?
'file://mnt/repo data/repomd.xml' is not a valid URL. IMO
Why is this an iniparse error ?
I hope this question was not for me... it was originally entered as a pirut bug,
since pirut accepted the invalid URL in the first place, or at least didn't
massage it into a legal URL. Incidentally, it would work for the session during
which the invalid URL was set, just not for any later ones.
However, I didn't feel qualified to comment when Jeremy refiled it as an
iniparse bug. I'm not really 100% sure which packages are "driving" the various
parts of the Add/Remove Software GUI.
(In reply to comment #6)
> I hope this question was not for me... it was originally entered as a pirut bug,
> since pirut accepted the invalid URL in the first place, or at least didn't
> massage it into a legal URL. Incidentally, it would work for the session during
> which the invalid URL was set, just not for any later ones.
> However, I didn't feel qualified to comment when Jeremy refiled it as an
> iniparse bug. I'm not really 100% sure which packages are "driving" the various
> parts of the Add/Remove Software GUI.
No, the question was to Jeremy.
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
I will close this one as F8 is EOL and pirut dont exist in F9 & F10.
And the problem is not a iniparse problem as far as i can see.