SVN Conversion Related Bugs

[tlattner]

Bugzilla Link	1535
Resolution	FIXED
Resolved on	Mar 02, 2008 23:59
Version	unspecified
OS	All
CC	@asl

Extended Description

Migrating to SVN is not complete. There are many things left to do and bugs related to the conversion.
This is a generic bug to capture all todo items.

Current Todo List:

• CommandGuide doesn't exist. We should have the website behave like the old one and check out the
  docs and update/build.
• Python is throwing an exception when viewing "Path" links for changes. (ie cpp file)
• cvs is mentioned in tons of places still (ie. most docs still do)
• doxygen is still using cvs
• llvmgrep should ignore svn related directories
• llvm-test should be renamed to whatever we have it name in svn. This impacts the nightlytester
  (maybe accept scripts too) and docs.

[lattner]

llvm.org/docs/index.html still has a link to cvsweb.

[asl]

Addendum:

• Fix newline issues mentioned in
  http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20070702/050952.html

[llvmbot]

http://llvm.org/docs/GettingStarted.html#checkout says to check out the test
suite as "test-suite." This breaks the build. It should be called "llvm-test."

[lattner]

I fixed the issue in comment 3.

[lattner]

From: Harry Metcalfe h.s.metcalfe@sussex.ac.uk
To: sabre@nondot.org
Subject: LLVM Command Guide
Hi,
Just thought I'd let you know that all the links at:
http://llvm.org/docs/CommandGuide/index.html
are broken.

[llvmbot]

I have fixed a few things related to this PR:

1. Fixed default maximums for svn-mailer to be more appropraite for LLVM
   project. Chris ran into this when he committed the website/ module.

2. Fixed the svn-mailer.conf to not require a section per module.

3. Created a /home/vadve/shared/llvm-utils directory in which we will place
   standard scripts for doing llvm-related tasks.

4. Created a doxygen_update.sh script and put it in llvm-utils. This is now
   running in my crontab. CHRIS: Shut Yours Off! ;>

5. Created a commit_update.sh script in llvm-utils and caused it to be run on
   every commit. This script can be modified to do whatever we need done. Right
   now it is updating the command guide documentation. Note that this script
   should "fail fast" since its executed on each commit. Unfortunately, this
   isn't working correctly because I don't have rights to reload the web
   server's configuration. Perhaps someone could do that soonish. When it is
   reloaded (run: /etc/init.d/httpd reload) then the /cmds/ location should
   provide the index to the commands.

6. I've looked into the viewvc python exception. I can't fix this because I
   don't have root access so someone else will have to do it. It should be
   fixed by simply upgrading it to the latest version (1.0.4 ?). You should
   use yum or whatever package manager is being used for system packages.

[lattner]

I disabled my doxygen generation crontab entry.

[tlattner]

Why do you think the viewvc problem can be fixed by upgrading viewvc? Anton already looked at the diff
between versions and didn't find anything substantial.

Also:

• I think all docs should point to what we have checked out instead of directly to svn. That way the date is
  set too.

[asl]

Tanya: I can be surely wrong. Or, something was added in the dev. version, which
wasn't in release. So, it definitely worth to upgrade at first.

[lattner]

alternatively, if viewcv doesn't work well for us, is there some other package that does?

[tlattner]

cvsupdate - What do we do with this?

[llvmbot]

viewvc: I was basing my comments on email list traffic for viewvc that said the
bug was fixed. I can't see it either, however; could be I'm looking in the wrong
place.

cvsupdate: either trash it (I've never used it) or convert it to subversion.

docs: We could update the docs as we did with CVS. The commit_update.sh script is
amenable to doing this for commits that only affect docs directory(ies).

[lattner]

From Seung Jae Lee on llvmdev:

"The hyperlinks for current tools(llvm-ar, llvm-as ...) in LLVM documentation
webpage seem to be broken.
All I can see when I clicked them is "The page cannot be found."
Is this just my problem or really broken?
Have a good evening."

these issues are impacting our users.

[llvmbot]

The CommandGuide is now fixed, without a server restart.

[llvmbot]

All noted issues above have been fixed with the exception of these.

1. ViewVC needs to be upgraded. The problem is supposedly fixed. Need root
   access on Zion to do the upgrade.

2. The HowToReleaseLLVM.html document needs serious revision, but I don't think
   this is a show stopper as its really just for the administrators.

3. Possibly the accept scripts are affected by the llvm-test name change.
   I don't know about such things so I'd appreciate if if someone could look
   into it.

These tasks need people other than myself involved to complete.