Re: btdownload errors (FC4 isos)
Dag Wieers <[email protected]>
| Newsgroups | gmane.linux.freshrpms.user |
|---|---|
| Organization | 3TI Web Hosting Services |
| Message-ID | <[email protected]> |
On Sat, 18 Jun 2005, Phil Schaffner wrote: > On Thu, 2005-06-16 at 15:48 -0400, Phil Schaffner wrote: > > On Tue, 2005-06-14 at 22:56 +0800, Jeff Pitman wrote: > > > On Tuesday 14 June 2005 22:40, Matthias Saou wrote: > > > > I just saw on the fedora-devel list that someone who was having > > > > similar issues got bittorrent working after upgrading from 4.1.1 to > > > > 4.1.2. Upstream bugs apparently. > > > > > > me! ;) > > > > > > And it's true. Ran it for the whole day without one traceback. (Though, > > > either way doesn't make a difference. It still download with 4.1.1 and > > > the speed wasn't really affected that much. I presume it would just > > > count as an occasional packet error.) > > > > Another data point - tried to download CentOS 4.1 i386 DVD with > > btdownloadcurses.py and it hung with ~99% cpu usage and with the > > terminal window "frozen" - no refresh, no response to q, Ctrl-C, Ctrl-Z. > > > > Killed from another window, restarted at it hung similarly at ~35% > > through checking the existing file. Did yum remove "yum remove python- > > khashmir bittorrent bittorrent-gui" and installed the "Official" version > > from http://www.bittorrent.com/dl/BitTorrent-4.1.2-1.noarch.rpm > > > > Restarted btdownloadcurses.py, check file and DL finished short order, > > and am now seeding the file from here. > > > > Moral of the story - upgrade is in order. > > Just ran updates on home machine after installing BitTorrent-4.1.2-1 > earlier today. Dag bittorrent-4.1.1-2.1.fc3.rf wants to obsolete it > even though the other version is higher: > > # yum update > ... > Dependencies Resolved > Transaction Listing: > Install: bittorrent.noarch 0:4.1.1-1.1.fc3.rf - dag > Update: bzip2.i386 0:1.0.2-13.FC3.1 - updates-released > Update: bzip2-devel.i386 0:1.0.2-13.FC3.1 - updates-released > Update: bzip2-libs.i386 0:1.0.2-13.FC3.1 - updates-released > Update: checkpolicy.i386 0:1.17.5-1.2 - updates-released > Update: gzip.i386 0:1.3.3-14.fc3 - updates-released > Update: selinux-policy-targeted.noarch 0:1.17.30-3.9 - updates-released > Update: spamassassin.i386 0:3.0.4-1.fc3 - updates-released > Update: util-linux.i386 0:2.12a-24.3 - updates-released > > Performing the following to resolve dependencies: > Install: python-khashmir.noarch 0:4.1.1-2.1.fc3.rf - dag > > Other Transactions: > Obsoleting: BitTorrent.noarch 0:4.1.2-1 with bittorrent.noarch 0:4.1.1-1.1.fc3.rf > > Total download size: 2.8 M > Is this ok [y/N]: n > Exiting on user Command > Complete! > # > > Disabled Dag repo for now. :-( Or uninstall python-khashmir. The bittorrent people made it themselves easier by providing python-khashmir inside the bittorrent package. Which is nice for the users that download it from the website, as they only have to download 1 file. But that's not very good packaging, as no other package can depend on python-khashmir. -- dag wieers, [email protected], http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]