[Debtorrent-commits] r44 - in /debtorrent/trunk: DebTorrent/parsedir.py TODO

[camrdale-guest at users.alioth.debian.org]

Author: camrdale-guest
Date: Thu May 10 05:22:48 2007
New Revision: 44

URL: http://svn.debian.org/wsvn/debtorrent/?sc=1&rev=44
Log:
Minor changes

Modified:
    debtorrent/trunk/DebTorrent/parsedir.py
    debtorrent/trunk/TODO

Modified: debtorrent/trunk/DebTorrent/parsedir.py
URL: http://svn.debian.org/wsvn/debtorrent/debtorrent/trunk/DebTorrent/parsedir.py?rev=44&op=diff
==============================================================================
--- debtorrent/trunk/DebTorrent/parsedir.py (original)
+++ debtorrent/trunk/DebTorrent/parsedir.py Thu May 10 05:22:48 2007
@@ -16,7 +16,7 @@
     True = 1
     False = 0
 
-NOISY = False
+NOISY = True
 
 def _errfunc(x):
     print ":: "+x

Modified: debtorrent/trunk/TODO
URL: http://svn.debian.org/wsvn/debtorrent/debtorrent/trunk/TODO?rev=44&op=diff
==============================================================================
--- debtorrent/trunk/TODO (original)
+++ debtorrent/trunk/TODO Thu May 10 05:22:48 2007
@@ -43,7 +43,7 @@
 
 Modifications need to be made to the debian archive management program 
 apt-ftparchive to support some of the upcoming features of debtorrent. Primarily, 
-the large files in a Packages file need to be broken up into sub-pieces, and a 
+the large files in a Packages file need to be broken up into sub-pieces, and 
 SHA1 hashes of the sub-pieces created. These would need to be cached, so as to 
 minimize the computation needed to generate a Packages file. Then, the tracker
 address needs to be added to Release files, along with any other needed metainfo. 
@@ -61,8 +61,8 @@
 means the directory will need to be changed/redownloaded if a mirror is changed. 
 Using the origin field from the Release file could cause problems if another 
 archive uses the same origin, and means that multiple torrents will download to 
-the same directory. Something like "<origin>_<codename>_<section>_binary-<arch>" 
-might work. That will result in duplicate downloads, if someone stracks both
+the same directory. Something like "<mirror>_<codename>_<section>_binary-<arch>" 
+might work. That will result in duplicate downloads, if someone tracks both
 sid and testing, for example. However, before downloading, the file could be 
 searched for in other directories, and hardlinked if found (and SHA1 sum 
 matches.