For whatever reason tracker.piratebay.org is resolving to 127.0.0.1. I read on some other forum that piratebay might be setting it to this when their tracker goes down so that no one can attempt to connect to it. I also read that they no longer run any actual trackers. At any rate, my problem is with the bittorrent programs in the bittorrent-4.4.0-noarch-3 package and how they deal with tracker.piratebay.org resolving to localhost. I tried using all of the bittorent clients (bittorrent, bittorrent-console, bittorrent-curses, bittorrent-xterm) and none of them work with piratebay.org torrents. This is the error I get when running bittorrent-curses:
Problem connecting to tracker - <urlopen error [Errno 111] Connection refused>
If I use another bittorrent client, like transmission, I don't get this problem. The torrent eventual starts to download; it looks like it moves on after failing to connect to localhost and then tries the other trackers listed in the torrent file. I presume that this is some kind of bug in bittorrent?
BTW, I noticed that when I was running apache locally both bittorrent and transmission would fail to download the torrent, each responding with a 404 error from apache that was running on localhost.