Hi all,

When SourceForge upgraded their CVS software, some subtle change in the URL
structure broke the version check.
DQSD ver 3.1.6.0 checks against

http://cvs.sourceforge.net/viewcvs.py/*checkout*/dqsd/dqsd/version.xml?conte
nt-type=text/xml

which currently returns a revision listing of version.xml.

The correct URL (used by 3.1.8) is

http://cvs.sourceforge.net/viewcvs.py/dqsd/dqsd/version.xml?rev=HEAD&content
-type=text/xml

I have a couple of concerns with this;

a) 3.1.6 users won't get the update notification, since their version checks
consistently fail, and most of them have probably turned off automatic
update checks, since their explorer.exe locked up if Sourceforge was down
(also fixed in 3.1.8).
b) If Sourceforge/ViewCVS pulls the same stunt again, the auto-update chain
is broken once more, and we'll have this same problem.

For (a), I guess there's not much we can do... We'll have to hope most
people notice, either from the mailing lists or dqsd.net that DQSD has a new
version available.

For (b), and I think we've talked about this before, maybe we should keep a
valid copy of version.xml in a known location at dqsd.net instead? This
means more work for release management, since it has to be copied over, but
it's no big deal (I'm doing the work anyway ;)).

Ideas?

Thanks,
Kim



-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
DQSD-Devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dqsd-devel

Reply via email to