Bug 302941 - Crash launching Software Updater
Summary: Crash launching Software Updater
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: pirut
Version: 7
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-09-24 11:25 UTC by Alessandro Nazzani
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version: 1.3.20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-09-26 15:00:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dump file from error (2.12 KB, text/plain)
2007-09-24 18:05 UTC, daniel nelson
no flags Details

Description Alessandro Nazzani 2007-09-24 11:25:44 UTC
I received the following message after trying to activate the Software Updater
(after giving root password - worked fine before):

---- Log start ----
Component: pirut
Summary: TB8f5a3431 yumRepo.py:749:_getRepoXML:RepoError: Cannot retrieve
repository metadata (repomd.xml) for repository: updates. Please verify its path
and try again

Traceback (most recent call last):
  File "/usr/sbin/pup", line 650, in <module>
    main()
  File "/usr/sbin/pup", line 643, in main
    pup = PackageUpdater(not options.autoapply, options.config)
  File "/usr/sbin/pup", line 88, in __init__
    GraphicalYumBase.__init__(self, False, config)
  File "/usr/lib/python2.5/site-packages/pirut/__init__.py", line 124, in __init__
    self.reset()
  File "/usr/lib/python2.5/site-packages/pirut/__init__.py", line 223, in reset
    self.doTsSetup()
  File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 64, in doTsSetup
    return self._getTs()
  File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 78, in _getTs
    self._tsInfo.setDatabases(self.rpmdb, self.pkgSack)
  File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 521, in <lambda>
    pkgSack = property(fget=lambda self: self._getSacks(),
  File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 381, in _getSacks
    self.repos.populateSack(which=repos)
  File "/usr/lib/python2.5/site-packages/yum/repos.py", line 239, in populateSack
    sack.populate(repo, mdtype, callback, cacheonly)
  File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 142, in populate
    if self._check_db_version(repo, mydbtype):
  File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 199, in
_check_db_version
    if repo.repoXML.repoData.has_key(mdtype):
  File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 753, in <lambda>
    repoXML = property(fget=lambda self: self._getRepoXML(),
  File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 749, in _getRepoXML
    raise Errors.RepoError, (msg)
RepoError: Cannot retrieve repository metadata (repomd.xml) for repository:
updates. Please verify its path and try again

Local variables in innermost frame:
msg: Cannot retrieve repository metadata (repomd.xml) for repository: updates.
Please verify its path and try again
self: updates
e: Cannot find a valid baseurl for repo: updates
---- Log end ----

Let me know if you need further info (this is my first bug report here).

Alessandro

Comment 1 daniel nelson 2007-09-24 18:05:24 UTC
Created attachment 204351 [details]
dump file from error

Also seeing this bug. Dump is attached.

Comment 2 Jeremy Katz 2007-09-26 12:55:53 UTC
Does this happen reliably?  If so, can you try with
http://koji.fedoraproject.org/packages/pirut/1.3.20/1.fc7/noarch/pirut-1.3.20-1.fc7.noarch.rpm
(will be in updates-testing later today) and see if things work better?

Comment 3 Alessandro Nazzani 2007-09-26 14:52:53 UTC
Hi Jeremy and thanks for the reply.

> Does this happen reliably?

Are you asking if it is reproducible? In this case, no: I was able to update my
system successfully after the crash.

Regards.

Alessandro

Comment 4 Jeremy Katz 2007-09-26 15:00:00 UTC
Okay the sporadic problems should be handled better then with the package that
is now in updates-testing.


Note You need to log in before you can comment on or make changes to this bug.