[CentOS] yum cannot find bittorent rpm at dag

Robert kerplop at sbcglobal.net
Mon Dec 29 21:40:10 UTC 2008



MHR wrote:
> On Mon, Dec 29, 2008 at 12:36 PM, James B. Byrne <byrnejb at harte-lyne.ca> wrote:
>   
>> These suggestions are interesting but they do not address my question,
>> which is:  Why does yum not find bittorrent at Dag?
>>
>> I was able to install bittorrent from Dag's repository using the gnome
>> graphical package installer so the package exists.   Yum finds the
>> repository for it obtains the package database from there.  So why does
>>
>> yum --enablerepo=dag install bittorrent
>>
>> report: package not found?
>>
>>     
>
> Maybe it's not there any more???
>
> Go to rpmforge.
>
> mhr
>   
It's still available from Dag. Without removing my working client, I can 
prove it with wget:

    [root at mavis ~]# wget
    http://dag.wieers.com/rpm/packages/bittorrent/bittorrent-4.4.0-1.el5.rf.noarch.rpm
    --15:24:45-- 
    http://dag.wieers.com/rpm/packages/bittorrent/bittorrent-4.4.0-1.el5.rf.noarch.rpm
    Resolving dag.wieers.com... 62.213.193.164
    Connecting to dag.wieers.com|62.213.193.164|:80... connected.
    HTTP request sent, awaiting response... 302 Found
    Location:
    http://rpmforge.sw.be/redhat/el5/en/i386/rpmforge/RPMS/bittorrent-4.4.0-1.el5.rf.noarch.rpm
    [following]
    --15:24:45-- 
    http://rpmforge.sw.be/redhat/el5/en/i386/rpmforge/RPMS/bittorrent-4.4.0-1.el5.rf.noarch.rpm
    Resolving rpmforge.sw.be... 130.133.35.16
    Connecting to rpmforge.sw.be|130.133.35.16|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 1121680 (1.1M) [application/x-rpm]
    Saving to: `bittorrent-4.4.0-1.el5.rf.noarch.rpm'

    100%[=========================================================>]
    1,121,680    307K/s   in 4.0s

    15:24:51 (274 KB/s) - `bittorrent-4.4.0-1.el5.rf.noarch.rpm' saved
    [1121680/1121680]

Ktorrent both either 32 or 64 bit are there, too.  I tried only the 64 
bit version:

    # wget
    http://dag.wieers.com/rpm/packages/ktorrent/ktorrent-2.2-1.el5.rf.x86_64.rpm
    --15:22:41-- 
    http://dag.wieers.com/rpm/packages/ktorrent/ktorrent-2.2-1.el5.rf.x86_64.rpm
    Resolving dag.wieers.com... 62.213.193.164
    Connecting to dag.wieers.com|62.213.193.164|:80... connected.
    HTTP request sent, awaiting response... 302 Found
    Location:
    http://rpmforge.sw.be/redhat/el5/en/x86_64/rpmforge/RPMS/ktorrent-2.2-1.el5.rf.x86_64.rpm
    [following]
    --15:22:41-- 
    http://rpmforge.sw.be/redhat/el5/en/x86_64/rpmforge/RPMS/ktorrent-2.2-1.el5.rf.x86_64.rpm
    Resolving rpmforge.sw.be... 130.133.35.16
    Connecting to rpmforge.sw.be|130.133.35.16|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 11995092 (11M) [application/x-rpm]
    Saving to: `ktorrent-2.2-1.el5.rf.x86_64.rpm'

    100%[=========================================================>]
    11,995,092   310K/s   in 38s

    15:23:20 (305 KB/s) - `ktorrent-2.2-1.el5.rf.x86_64.rpm' saved
    [11995092/11995092]

What are the chances of the O.P. having a yum config file screwed up? 



More information about the CentOS mailing list