bittorrent-4.20.0 was recently released changes in the ebuild: - added patch for bittorrent-curses (missing import) (patch in latter post here) - requirement of twisted library
Created attachment 89764 [details] bittorrent-4.20.0.ebuild
Created attachment 89765 [details, diff] patch to fix missing import from bittorrent-curses
This version depends on wxpython, not pygtk.
and wxpython need to be compiled with unicode support as wxGTK as well.
Created attachment 89821 [details] bittorrent-4.20.0.ebuild (with gtk + unicode fixes) I don't use the gtk version, only the curses; if someone wants to test this new ebuild, it should error out if you don't have wxGTK and/or wxpython built with unicode.
Created attachment 90594 [details] bittorrent-4.20.2 The newest version.
This is over a month old and the latest version is 4.20.4. Anyone in the net-p2p herd alive?
I tested it and to be honest I do not like it. It safes to my homedir by default instead of to the current directory and saves the uncompleted file in my home dir unless I specify otherwise. I have switched to rtorrent now and I noticed (or imagined?) a speedup and love the interface of rtorrent :) Sorry guys, and good luck in finding another developer to commit this
That is very mature of you.
(In reply to comment #8) > Sorry guys, and good luck in finding another developer to commit this > LOL! This is a joke? This is still hanging here... Anyboby with privilidges that can take care of this bug?
That comment is probably the silliest thing I've ever heard. However, if net-p2p/bittorrent is unmaintained, it should be removed from the tree. If people cannot file bugs such as a version bump request, with the reasonable expectation that they will be resolved, then that is a sign of terrible (and terrifying!) QA. A version bump request shouldn't have 10 comments on it! For e.g: Bug - version bump for cat/foo comment #1 = Thanks! Committed. Please, someone with rights, remove net-p2p/bittorrent from tree, or version bump the ebuild with the patches and newer ebuilds found here.
It is still maintained, I'm just busy with classes. Don't worry, it's on my schedule for Tuesday.
*** Bug 145964 has been marked as a duplicate of this bug. ***
Which tuesday? :)
The one I don't have a family emergency come up in ;). I do appologize, but it was out of my control. Everything appears to work fine, except for the init script. It appears that it changed during a revision bump, but the revised init script was never added to portage. Thus, the install of bttrack.rc-4.1 doesn't work. If you could please go ahead and fix and test this, it will speed me up greatly.
May we get information about current status of this bump?
(In reply to comment #10) > (In reply to comment #8) > > Sorry guys, and good luck in finding another developer to commit this > > > > LOL! This is a joke? > > This is still hanging here... > Anyboby with privilidges that can take care of this bug? > You all bitch and complain instead of getting off your ass and becoming a dev that is interested in the package. Until you become a dev you have no room to speak your still just an end user who has no ideal what it is like behind the scene of gentoo.
(In reply to comment #17) > You all bitch and complain instead of getting off your ass and becoming a dev > that is interested in the package. Until you become a dev you have no room to > speak your still just an end user who has no ideal what it is like behind the > scene of gentoo. Woah, chill dude. You're the only one getting hyped about this. Comment 10 was, IMHO, completely without aggression. Even a Gentoo dev wondered about this bug in comment 16. "is that a joke" was a valid question. Comment 8 could have very well been a joke (albeit one in poor taste).
http://download.bittorrent.com/dl/BitTorrent-4.24.2.tar.gz was uploaded 10/10 just thinking so that you dont get that long-awaited bump with and old version :p
4.26.0 is the latest version.
(In reply to comment #20) > 4.26.0 is the latest version. > thats correct, it was uploaded 11-Oct-2006 15:09
bumped in portage; again, I appologize for the extended inactivity to resolve this issue. Thank you for your patience!
