linuxdcpp-team team mailing list archive

[maksis <919424@xxxxxxxxxxxxxxxxxx>]

"Of course your motive is to make it easy to move *to* Air and not away
from it (hence the import feature for the old DB format), but still..."

My motivation was to make it possible for people using older versions of
the application to upgrade without losing their data...


Regarding comment #14:

"If anyone still cares I suggest splitting this conversation and moving
comments #12 and #13 to a new feature wishlist entry as the original
report here is about the hashdata.dat cleaning process does not start in
some cases"

The way I understand the original report is that the rebuild was
performed but it didn't produce the expected results. That's what I
tried to explain in comment #12. If a tree has been used earlier during
the session, it won't be removed during rebuild. You need to restart the
application after removing the files (and all other files with the same
TTHs) from share before performing rebuild.

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to DC++.
https://bugs.launchpad.net/bugs/919424

Title:
  /rebuild does not update HashData

Status in ApexDC++:
  New
Status in DC++:
  Confirmed

Bug description:
  BCDC 0.790a. 
  Windows 7 SP1 x64.

  Summary:
  If you add a new share, hash the files, and then remove it, issue a /rebuild and then re-add the same share again, DC++ will not rehash the files. Furthermore, a /rebuild between adding/removing shares does not change the size of hashdata.dat or hasindex.xml.

  Repro:
  * add a new share. accept the default name. DC++ hashes the files.
  * open your filelist to validate share is present.
  * check the size of hashdata and hashindex.
  * remove the share you just added.
  * issue a /refresh and /rebuild.
  * note the size of hashdata and hashindex has NOT changed.
  * add the same share again, accepting the default name.  DC++ does NOT hash the files.
  * issue a /refresh. DC++ does not re-index the files from that share.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apexdc/+bug/919424/+subscriptions