Bug 136476 - Yum fails to work with Livna
Yum fails to work with Livna
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Depends On:
  Show dependency treegraph
Reported: 2004-10-20 07:54 EDT by Ivan Gyurdiev
Modified: 2014-01-21 17:50 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-20 10:47:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ivan Gyurdiev 2004-10-20 07:54:03 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041016

Description of problem:
Hi, this is getting annoying, so I thought I'd file a bug.
Yum stopped working for livna and fedora.us when Yum 2 was released.
Then fedora.us started working again, but livna is still broken. 

This unfriendly output is IMHO unacceptable, so it must be a bug
whether ot not Livna.org is misconfigured:

[root@cobra ~]# yum update
Setting up Update Process
Setting up Repo:  fedora-us-unstable
repomd.xml                100% |=========================|  903 B    00:00
Setting up Repo:  jpackage15-fc2
repomd.xml                100% |=========================|  903 B    00:00
Setting up Repo:  fedora-development
repomd.xml                100% |=========================| 1.1 kB    00:00
Setting up Repo:  livna-stable
repodata/repomd.xml: <urlgrabber.grabber.CallbackObject instance at
Traceback (most recent call last):
  File "/usr/bin/yum", line 8, in ?
  File "/usr/share/yum-cli/yummain.py", line 60, in main
    result, resultmsgs = base.doCommands()
  File "/usr/share/yum-cli/cli.py", line 380, in doCommands
    return self.updatePkgs()
  File "/usr/share/yum-cli/cli.py", line 765, in updatePkgs
  File "/usr/share/yum-cli/cli.py", line 69, in doRepoSetup
  File "/usr/lib/python2.3/site-packages/yum/repos.py", line 459, in
    result = self.get(relative=remote, local=local, copy_local=1)
  File "/usr/lib/python2.3/site-packages/yum/repos.py", line 437, in get
  File "/usr/lib/python2.3/site-packages/urlgrabber/mirror.py", line
414, in urlgrab
    return self._mirror_try(func, url, kw)
  File "/usr/lib/python2.3/site-packages/urlgrabber/mirror.py", line
400, in _mirror_try
    return func_ref( *(fullurl,), **kwargs )
  File "/usr/lib/python2.3/site-packages/urlgrabber/grabber.py", line
595, in urlgrab
    return self._retry(opts, retryfunc, url, filename)
  File "/usr/lib/python2.3/site-packages/urlgrabber/grabber.py", line
542, in _retry
    cb_func(obj, *cb_args, **cb_kwargs)
  File "/usr/share/yum-cli/output.py", line 41, in failureReport
    raise msg
urlgrabber.grabber.CallbackObject: <urlgrabber.grabber.CallbackObject
instance at 0xb7b0b60c>
[root@cobra ~]#

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

How reproducible:

Steps to Reproduce:
1. See summary

Additional info:
Comment 1 Ivan Gyurdiev 2004-10-20 07:55:44 EDT

name=Livna.org Fedora Compatible Packages (stable)
baseurl= http://rpm.livna.org/fedora/$releasever/$basearch/yum/stable

name=Livna.org Fedora Compatible Packages (unstable)
baseurl= http://rpm.livna.org/fedora/$releasever/$basearch/yum/unstable

name=Livna.org Fedora Compatible Packages (testing)
baseurl= http://rpm.livna.org/fedora/$releasever/$basearch/yum/testing
Comment 2 Seth Vidal 2004-10-20 08:37:12 EDT
So, first things, yum 2.1.10 fixes the traceback you received.
second - http://rpm.livna.org/fedora/2/i386/RPMS.stable/

that's the path to the stable tree of fedora core 2.

No fedora core 3 tree is available yet.
Comment 3 Ivan Gyurdiev 2004-10-20 10:47:11 EDT
Ok thanks. Sorry, I thought the path was correct - it used to work
before at some point, and it seemed legitimate. Yum didn't complain
either. Closing bug as Livna.org works with the modified path. It's
good to know the traceback has been fixed too.

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