Bug 1492

Summary:	CVS Tree, can't enter xfree86 directory
Product:	freedesktop.org	Reporter:	Konstantin Filtschew <mailoperator>
Component:	Website	Assignee:	fd.o Admin Massive <sitewranglers>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	high
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Linux (All)
URL:	http://freedesktop.org/cgi-bin/viewcvs.cgi/xc/programs/Xserver/hw/?root=xorg
Whiteboard:
i915 platform:		i915 features:

Description Konstantin Filtschew 2004-09-29 03:12:35 UTC

if you choose after that 

xfree86, there is an error:

http://freedesktop.org/cgi-bin/viewcvs.cgi/xc/programs/Xserver/hw/xfree86/?root=xorg

Comment 1 Konstantin Filtschew 2004-09-29 03:17:43 UTC

(dir) xfree68/ 	  	  	  	 
(dir) xfree86/ 	  	  	  	 
(dir) xfree98/ 	  	  	  	 
(dir) xnest/
(dir) sunAmoeba/
(dir) hp/

have problems

the fault for xfree86 directory:


An Exception Has Occurred
Python Traceback

Traceback (most recent call last):
  File "/usr/lib/python2.3/site-packages/viewcvs/viewcvs.py", line 3226, in main
    request.run_viewcvs()
  File "/usr/lib/python2.3/site-packages/viewcvs/viewcvs.py", line 356, in
run_viewcvs
    self.view_func(self)
  File "/usr/lib/python2.3/site-packages/viewcvs/viewcvs.py", line 1356, in
view_directory
    request.repos.dirlogs(request.path_parts, file_data, options)
  File "/usr/lib/python2.3/site-packages/viewcvs/vclib/bincvs/__init__.py", line
160, in dirlogs
    alltags = _get_logs(self, dirpath, entries, tag, subdirs)
  File "/usr/lib/python2.3/site-packages/viewcvs/vclib/bincvs/__init__.py", line
795, in _get_logs
    raise vclib.Error('Error parsing rlog output. Expected RCS file "%s"'
Error: Error parsing rlog output. Expected RCS file
"/cvs/xorg/xc/programs/Xserver/hw/xfree86/XF86_Acc.man,v", found
"/cvs/xorg/xc/programs/Xserver/hw/xfree86/XF86Conf.man,v"

Comment 2 Matthieu Herrb 2004-09-29 12:56:00 UTC


*** This bug has been marked as a duplicate of 1486 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.