Package: viewcvs
Severity: normal

Note that the system this is being reported from is not the system on which
the issue has been noted, infact viewcvs is not installed.

Reference:  http://gna.org/support/?func=detailitem&item_id=1058

The link generated for 'diff' is partially missing the URI escaping. As an 
example, the following link:

http://svn.gna.org/viewcvs/gnustep?rev=22800&view=rev

includes the 'diff to previous) link:

http://svn.gna.org/viewcvs/gnustep/libs/gui/trunk/Source/NSBitmapImageRep%2BJPEG.m?rev=22800&view=diff&r1=22800&r2=22799&p1=libs/gui/trunk/Source/NSBitmapImageRep+JPEG.m&p2=/libs/gui/trunk/Source/NSBitmapImageRep+JPEG.m

which results in an "Invalid path(s) or revision(s) passed to diff" Exception. 
If you hand edit the URI replacing the '+' with '%2B' in the parameters to read:

http://svn.gna.org/viewcvs/gnustep/libs/gui/trunk/Source/NSBitmapImageRep%2BJPEG.m?rev=22800&view=diff&r1=22800&r2=22799&p1=libs/gui/trunk/Source/NSBitmapImageRep%2BJPEG.m&p2=/libs/gui/trunk/Source/NSBitmapImageRep%2BJPEG.m

the expected results are presented.

Note that this has probably been resolved upstream and the issue tracker 
contains a patch (yet I don't know whether that's the patch that solved the 
issue upstream):
http://viewvc.tigris.org/issues/show_bug.cgi?id=99

So the question is, does this bug have security implications that would allow 
it to be fixed in sarge?  It seems that even the unstable versions of the 
viewcvs package are still using an old snapshot (unstable: 
0.9.2+cvs.1.0.dev.2004.07.28-4):
http://packages.debian.org/cgi-bin/search_packages.pl?keywords=viewcvs&searchon=names&subword=1&version=all&release=all

So I suppose this package is not being maintained any longer (last 'unstable' 
ChangeLog Thu, 21 Jul 2005) and I haven't found any 'viewvc' package.

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-386
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to