I am trying to get the x86_64 isos of CentOS-5.2. I wish to use bittorrent. The last time that I did this I required the bittorent package from Dag's repository. I have configured /etc/yum.repos.d/DagWieers.repo thus:
[dag] name=Dag Wieers RPM Repository for Red Hat Enterprise Linux #Also see URL http://dag.wieers.com/home-made/apt/ baseurl=http://apt.sw.be/redhat/el$releasever/en/$basearch/dag gpgcheck=1 # This repo often does not respond in a timely fashion so turned off # by default. Use yum --enablerepo=dag to use. enabled=0 gpgkey=http://dag.wieers.com/packages/RPM-GPG-KEY.dag.txt includepkgs=bittorrent* perl* # priority requires yum-priorities. Must also be enabled in /etc/yum.conf # and /etc/yum/pluginconf.d/priorities.conf. priority=20
Then I run yum thus:
# yum --enablerepo=dag whatprovides bittorent
But yum cannot find bittorrent.
Loading "fastestmirror" plugin Loading mirror speeds from cached hostfile * epel: mirror.unl.edu * dag: apt.sw.be * base: centos.mirror.iweb.ca * updates: centos.mirror.iweb.ca * addons: centos.mirror.iweb.ca * extras: centos.mirror.iweb.ca dag 100% |=========================| 1.1 kB 00:00 Reducing Extra Packages for Enterprise Linux 5 - x86_64 to included packages only Finished Reducing Dag Wieers RPM Repository for Red Hat Enterprise Linux to included packages only Finished No Matches found
What am I doing wrong?
On Mon, Dec 29, 2008 at 10:44 AM, James B. Byrne byrnejb@harte-lyne.ca wrote:
I am trying to get the x86_64 isos of CentOS-5.2. I wish to use bittorrent. The last time that I did this I required the bittorent package from Dag's repository.
Try rpmforge - https://rpmrepo.org/RPMforge
It's there:
bittorrent.noarch 4.4.0-1.el5.rf rpmforge bittorrent-gui.noarch 4.4.0-1.el5.rf rpmforge
mhr
On Mon, 2008-12-29 at 11:07 -0800, MHR wrote:
On Mon, Dec 29, 2008 at 10:44 AM, James B. Byrne byrnejb@harte-lyne.ca wrote:
I am trying to get the x86_64 isos of CentOS-5.2. I wish to use bittorrent. The last time that I did this I required the bittorent package from Dag's repository.
Try rpmforge - https://rpmrepo.org/RPMforge
It's there:
bittorrent.noarch 4.4.0-1.el5.rf rpmforge bittorrent-gui.noarch 4.4.0-1.el5.rf rpmforge
Just be aware that that version doesn't have the latest "in the wild" features. When I looked into porting the latest some months back, I found too many changes need for my experience level (python. gtk2?, ... and more).
If you don't need all the "glitz", maybe one of the others would do? I use and like rtorrent, but there's also this stuff
Available Packages ctorrent.i386 1.3.4-3.dnh2.1.el5.kb kbs-CentOS-Testi ktorrent.i386 2.2.1-1.el5.rf rpmforge libtorrent-devel.i386 0.12.0-1.el5.rf rpmforge torrentzip.i386 0.2-1.el5.rf rpmforge
There's others that don't have torrent in the package name, but I can't recall them ATM. I saw them when I was running rtorrent to share my 5.2 images though.
A browse of the rpmforge site should lead you to alternatives if you have the interest in them.
mhr
<snip sig stuff>
On Mon, 2008-12-29 at 13:44 -0500, James B. Byrne wrote:
I am trying to get the x86_64 isos of CentOS-5.2. I wish to use bittorrent. The last time that I did this I required the bittorent package from Dag's repository. I have configured /etc/yum.repos.d/DagWieers.repo thus:
[dag] name=Dag Wieers RPM Repository for Red Hat Enterprise Linux #Also see URL http://dag.wieers.com/home-made/apt/ baseurl=http://apt.sw.be/redhat/el$releasever/en/$basearch/dag gpgcheck=1 # This repo often does not respond in a timely fashion so turned off # by default. Use yum --enablerepo=dag to use. enabled=0 gpgkey=http://dag.wieers.com/packages/RPM-GPG-KEY.dag.txt includepkgs=bittorrent* perl* # priority requires yum-priorities. Must also be enabled in /etc/yum.conf # and /etc/yum/pluginconf.d/priorities.conf. priority=20
I'm 386, but that shouldn't be all that different. Is it possible that bittorrent is only available as a 386 package?
$ yum list installed *torrent* Loaded plugins: allowdowngrade, changelog, downloadonly, fastestmirror, : fedorakmod, kernel-module, priorities, tsflags, versionlock Installed Packages bittorrent.noarch 4.4.0-1.el5.rf installed bittorrent-gui.noarch 4.4.0-1.el5.rf installed libtorrent.i386 0.12.0-1.el5.rf installed rtorrent.i386 0.8.0-1.el5.rf installed
The above makes me think (being essentially ignorant about all this rpm stuff) that you might need to over-ride your architecture? And I got then from rpmforge, not Dag's place so I don't know if it's there or not.
I'm not sure how current that dag repo is. I know that Dag has been involved in trying to get rpmforge going, some kind of involvement with other repos, etc.
FWIW, I've this rpmforge setup.
$ cat /etc/yum.repos.d/rpmforge.repo # Name: RPMforge RPM Repository for Red Hat Enterprise 5 - dag # URL: http://rpmforge.net/ [rpmforge] name = Red Hat Enterprise $releasever - RPMforge.net - dag #baseurl = http://apt.sw.be/redhat/el5/en/$basearch/dag mirrorlist = http://apt.sw.be/redhat/el5/en/mirrors-rpmforge #mirrorlist = file:///etc/yum.repos.d/mirrors-rpmforge enabled = 1 protect = 0 gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dag gpgcheck = 1 priority=10 # includepkgs=rtorrent.i386 libtorrent.i386 libsigc++20.i386 nvidia-x11-drv
Note that the "protect=0" is needed for priorities to work.
Then I run yum thus:
# yum --enablerepo=dag whatprovides bittorent
But yum cannot find bittorrent.
I only use the rtorrent, which has the DHT feature, so I really can't offer any more than what I have above.
Sorry.
HTH
On Mon, Dec 29, 2008 at 11:22 AM, William L. Maltby CentOS4Bill@triad.rr.com wrote:
I'm 386, but that shouldn't be all that different. Is it possible that bittorrent is only available as a 386 package?
$ yum list installed *torrent* Loaded plugins: allowdowngrade, changelog, downloadonly, fastestmirror, : fedorakmod, kernel-module, priorities, tsflags, versionlock Installed Packages bittorrent.noarch 4.4.0-1.el5.rf installed bittorrent-gui.noarch 4.4.0-1.el5.rf installed libtorrent.i386 0.12.0-1.el5.rf installed rtorrent.i386 0.8.0-1.el5.rf installed
This is what you'll see on a 32-bit machine - the bittorrent package itself is a no-arch package, which means it doesn't care what the underlying architecture is (translation: probably a scripting language - shell, perl, python, etc.). The 64-bit entries usually show only if you are actually running a 64 bit machine. There are also some switches you can use that show more, but I'm not familiar with them (DKDC :-).
Note that the "protect=0" is needed for priorities to work.
This is only true if you have both the yum-protectbase and yum-priorities plugins installed, in which case you should remove the protectbase plugin - it is recommended that you _not_ run both together.
HTH
mhr
On Mon, 2008-12-29 at 12:23 -0800, MHR wrote:
On Mon, Dec 29, 2008 at 11:22 AM, William L. Maltby
<snip>
Note that the "protect=0" is needed for priorities to work.
This is only true if you have both the yum-protectbase and yum-priorities plugins installed, in which case you should remove the protectbase plugin - it is recommended that you _not_ run both together.
Yeah, but I'm all for flexibility. I tested and found I could leave both installed. I tested and found that just disabling protect and setting priorities worked as I wanted.
So I ignored the "remove it" suggestions that abound and just disabled. AFAICT, this is equivalent to "remove it" except that I can switch modes more easily.
<snip>
On Mon, December 29, 2008 13:44, James B. Byrne wrote:
I am trying to get the x86_64 isos of CentOS-5.2. I wish to use bittorrent. The last time that I did this I required the bittorent package from Dag's repository. I have configured /etc/yum.repos.d/DagWieers.repo thus:
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?
On Mon, Dec 29, 2008 at 12:36 PM, James B. Byrne byrnejb@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
MHR wrote:
On Mon, Dec 29, 2008 at 12:36 PM, James B. Byrne byrnejb@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@mavis ~]# wget http://dag.wieers.com/rpm/packages/bittorrent/bittorrent-4.4.0-1.el5.rf.noar... --15:24:45-- http://dag.wieers.com/rpm/packages/bittorrent/bittorrent-4.4.0-1.el5.rf.noar... 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.el... [following] --15:24:45-- http://rpmforge.sw.be/redhat/el5/en/i386/rpmforge/RPMS/bittorrent-4.4.0-1.el... 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.... [following] --15:22:41-- http://rpmforge.sw.be/redhat/el5/en/x86_64/rpmforge/RPMS/ktorrent-2.2-1.el5.... 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?
On Mon, December 29, 2008 15:36, James B. Byrne wrote:
These suggestions are interesting but they do not address my question, which is: Why does yum not find bittorrent at Dag?
This problem has disappeared, with evidently no action on my part. It may have been a transient network issue. In any case, yum now finds bittorrent.noarch in the dag repository.
-
James B. Byrne -
MHR -
Robert -
William L. Maltby