[LON-CAPA-admin] upgrade inquires

Guy Albertelli II guy at albertelli.com
Fri Jan 6 17:22:19 EST 2006


Hi Paul,

> > ...
> > > Compiling pwauth
> > > pwauth.c: In function ?

and

> Having now run /root/loncapa-2.1.0/UPGRADE, I note that the
> (considerable) output from that ended at:
> capaFormulaLexer.c: In function ?

Looks like in both of these cases on my Fedora Core 4 test machine,
gcc is ouputting a UNICODE single quote, probalby because the default
English LANG setting in FC4 is "en_US.UTF-8"

It seems that your ssh client isn't liking this character and causing
it to malfunction?


> Then comes the fetch and extraction of LON-CAPA files. I find
> another new "feature" of the installation that I consider a
> bug.

We mainly do this so that the install instructions can be shorter.

you can circumvent this by doing 

install.pl --nodownload_loncapa

But it's a good idea to ask the user before downloading.
http://bugs.loncapa.org/show_bug.cgi?id=4550

> Anyway, the log file does not contain the message that closes install.pl:

The last lines should be the file list of the tarball extraction.

> If that message was supposed to appear only on the terminal screen
> then I suppose it probably isn't a problem for most people whose
> terminal windows don't lock up during the compilation. At this
> point, install.pl seems to have set up httpd to start on boot, but
> not loncontrol.

Correct. At this point in the install the machine is completely ready
for the lon-capa code to be installed.  Thus loncontrol is not
expected to exist on the machine yet so we couldn't have yet set it to
start on boot up.  (In some sense install.pl would probably be most
accurately named 'prepare_machine.pl')


> My other major problem is that I don't see a way that I could have
> ended my installation with the 2.0.1 version and not gone all the
> way to 2.1.0 without having had a chance to test the OS upgrade by
> itself.

At the point in time you had retored /home and run install.pl to
completion, but before you had yet to run ./UPDATE you could have

1) restored the needed /etc files
2) fired up httpd and loncontrol
3) logged in

-- 
guy at albertelli.com   0-7-1-8-27,137



More information about the LON-CAPA-admin mailing list