Bug 236850 - Kopte started from command line generates this message
Kopte started from command line generates this message
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
rawhide
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: James Antill
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-17 19:40 EDT by Bruce Barbour
Modified: 2014-01-21 17:57 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-09-13 14:02:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Report generated when Kopete started from command line (1.68 KB, application/octet-stream)
2007-04-17 19:40 EDT, Bruce Barbour
no flags Details

  None (edit)
Description Bruce Barbour 2007-04-17 19:40:17 EDT
Description of problem:
Kopete started from command line

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Bruce Barbour 2007-04-17 19:40:17 EDT
Created attachment 152863 [details]
Report generated when Kopete started from command line
Comment 2 Gianluca Varisco 2007-06-12 06:27:39 EDT
According to your report attached, seems a problem related to the YUM package
manager:

File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 312, in check
'Cannot find a valid baseurl for repo: %s' % self.id
RepoError: Cannot find a valid baseurl for repo: extras-development

If you still have problems, try to update your system to the latest version
(Fedora 7).
Comment 3 Ngo Than 2007-06-12 08:00:23 EDT
it's a yum issue. reassign to correct component
Comment 4 Jeremy Katz 2007-06-13 15:19:33 EDT
What are the contents of your /etc/yum.repos.d files?
Comment 5 Jeremy Katz 2007-09-13 14:02:16 EDT
Closing due to lack of activity; if you have further information please reopen
this report

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