On 07/14/2011 01:07 PM, seth vidal wrote:
googling around gets me info on how magnet links work. Now, what tools
do we have in fedora to generate them and the Distributed Hash Tables.
Sorry for the delay again.
There's no tool required. As long as you know the hash of the torrent
you can make
On Sat, 2011-06-25 at 22:23 -0500, Jeffrey Ollie wrote:
On Wed, Jun 15, 2011 at 9:55 PM, seth vidal skvi...@fedoraproject.org wrote:
Heck, I'd be willing to accept ANY bittorrent server that can be both
tracker and primary seed and doesn't require a special apache module to
do it.
The
On Sun, 2011-06-26 at 00:22 -0500, Michael Cronenworth wrote:
On 06/15/2011 09:55 PM, seth vidal wrote:
Heck, I'd be willing to accept ANY bittorrent server that can be both
tracker and primary seed and doesn't require a special apache module to
do it.
Late to the party with this
On Wed, Jun 15, 2011 at 9:55 PM, seth vidal skvi...@fedoraproject.org wrote:
Heck, I'd be willing to accept ANY bittorrent server that can be both
tracker and primary seed and doesn't require a special apache module to
do it.
The biggest virtue of the old bittorrent client is that it is
I have now retired bittorrent in git, pkgdb and comps, and have filed
ticket https://fedorahosted.org/rel-eng/ticket/4783 to have it blocked
in koji since there were no real objections.
Anyone that would like to breathe new life into it is welcome to take it.
Paul.
--
devel mailing list
On Wed, 2011-06-15 at 13:12 +0100, Paul Howarth wrote:
I believe Mandriva solved this problem by having transmission obsolete
bittorrent-gui and just shipping the console version.
Yup. We did. Exactly nobody complained. :)
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora
On Wednesday, June 15, 2011 07:12:56 AM Paul Howarth wrote:
I propose to retire bittorrent (the original python client) for the
reasons outlined below. If anyone's interested in taking it over
instead, please apply on the package database and I'll transfer
ownership. Think carefully before
I propose to retire bittorrent (the original python client) for the
reasons outlined below. If anyone's interested in taking it over
instead, please apply on the package database and I'll transfer
ownership. Think carefully before you act though!
Dead Upstream:
==
Well, not
On 06/15/2011 01:37 PM, Jon Ciesla wrote:
I propose to retire bittorrent (the original python client) for the
reasons outlined below. If anyone's interested in taking it over
instead, please apply on the package database and I'll transfer
ownership. Think carefully before you act though!
On 06/15/2011 01:37 PM, Jon Ciesla wrote:
I propose to retire bittorrent (the original python client) for the
reasons outlined below. If anyone's interested in taking it over
instead, please apply on the package database and I'll transfer
ownership. Think carefully before you act though!
15.06.2011, 21:37, Jon Ciesla l...@jcomserv.net:
My only concern is that there be a command-line replacement available. I
currently fetch my ISOs with bittorrent-curses and screen. Can someone
with experience with any of them offer a recommendation? Python, C and
C++ clients especially.
Jon Ciesla writes:
My only concern is that there be a command-line replacement available. I
currently fetch my ISOs with bittorrent-curses and screen. Can someone
with experience with any of them offer a recommendation?
transmission-cli works for me.
transmission should be sufficient to
On Wed, Jun 15, 2011 at 2:37 PM, Jon Ciesla l...@jcomserv.net wrote:
My only concern is that there be a command-line replacement available. I
currently fetch my ISOs with bittorrent-curses and screen. Can someone
with experience with any of them offer a recommendation? Python, C and
C++
15.06.2011, 21:37, Jon Ciesla l...@jcomserv.net:
My only concern is that there be a command-line replacement available.
I
currently fetch my ISOs with bittorrent-curses and screen. Can someone
with experience with any of them offer a recommendation? Python, C and
C++ clients especially.
14 matches
Mail list logo
