Forum .LRN Q&A: Okay, I think I am getting really good at failing to install dotLRN

Request notifications

For my latest fun;

Since the release of the 4.6 tarball, I pretty much
tossed everything, got the tarballs of Postgresql
7.2.3 built it with-tcl without-tk, built AOLserver
3.3.1+ad13 stock, built the 4.6 beta1 tarball stock, everything works just great.

However, when I add the dotLRN packages via cvs as
instructed by the docs at

and try to follow along as instructed by the line that
states: "Go the the "ACS Package Manager" (APM) on your system at http://yourserver/acs-admin/apm and hit the "Install packages" link. After the installer loads,"

Well, I never get to the "After" part, as the
installer is loading, this happens:

-----------include error---------------------------------

Please wait while the installer loads ........

HTTP/1.0 200 OK Server: AOLserver/3.3.1+ad13 Content-Type: text/html; charset=iso-8859-1 MIME-Version: 1.0 Date: Fri, 27 Dec 2002 18:48:53 GMT Content-Length: 2722 Connection: close
Request Error

Invalid file type "message_catalog"
    while executing
"error "Invalid file type \"$type\"""
    (procedure "apm_read_package_info_file" line 151)
    invoked from within
"apm_read_package_info_file $spec_file"
    ("foreach" body line 2)
    invoked from within
"foreach spec_file $all_spec_files {
    array set version [apm_read_package_info_file $spec_file]
    set version_name $version(name)
    set package_..."
    ("uplevel" body line 37)
    invoked from within
"uplevel {
          ad_page_contract {

    Select, dependency check, install and enable packages.

    @author Bryan Quinn (
    (procedure "code::tcl::/web/another_test/packages/acs-admin/www/apm/pack..." line 2)
    invoked from within
    invoked from within
"if { [file exists $__adp_stub.tcl] } {

      # ensure that data source preparation procedure exists and is up-to-date
      adp_init tcl $__adp_stub
    ("uplevel" body line 3)
    invoked from within
"uplevel {

    if { [file exists $__adp_stub.tcl] } {

      # ensure that data source preparation procedure exists and is up-to-date
      adp_init t..."
    (procedure "adp_prepare" line 2)
    invoked from within
"adp_prepare "
    (procedure "template::adp_parse" line 30)
    invoked from within
"template::adp_parse [file root [ad_conn file]] {}"
    (procedure "adp_parse_ad_conn_file" line 7)
    invoked from within
    ("uplevel" body line 2)
    invoked from within
"uplevel $code"
    invoked from within
"ad_try {
      } ad_script_abort val {
    # do nothing
    invoked from within
"rp_serve_concrete_file [ad_conn file]"
    (procedure "rp_serve_abstract_file" line 60)
    invoked from within
"rp_serve_abstract_file "$root/$path""
    ("uplevel" body line 2)
    invoked from within
"uplevel $code"
    invoked from within
"ad_try {
    rp_serve_abstract_file "$root/$path"
    set tcl_url2file([ad_conn url]) [ad_conn file]
    set tcl_url2path_info([ad_conn url]) [ad_conn path_inf..."

--------------------end include-------------------------

the installer loads just fine in 4.6 beta 1 stock.

This error is most likely because you are mixing incompatible version of oacs and dotlrn. Either you can use oacs-4-6 (which happens to be the version that the tarball is based on) together with dotlrn-1-0, or HEAD from both.

Did you really follow, especially the paragraph where it says:

If you are installing OpenACS, follow the extensive installation documentation. Stop at the point  where the OpenACS installation instructions tell you to "download OpenACS". Don't use the "Quick Downloads"! Continue on with this document.

      cvs -d login
      (just hit return for the password)
      cvs -z3 -d checkout acs-core

Also have a look at the comment at the bottom of the installation instructions.

Hi Tilmann;

Thanks kindly for the reply.

Having failed at doing "it" the way you
described a week ago, I bailed on it when
the tarball appeared. Which of course didn't
work as remarked above.

So, with your prompting, I went BACK to
the original proceedure, got all the
stuff from cvs head, and suprise suprise!
It worked this time!

So, just in case anyone is curious, this day,
20021228, the dotlrn installation works just
fine as described in the original document.

Thanks again.

Now on to the next phase of the adventure.

Sorry I didn't see this post sooner. I also want to report that I successfully installed the 4.6 openacs and dotlrn Dec 18th or so at: and it went as described in the documentation.

There's not as many navigational items by default which makes it a bit harder to get around unless you know where things are located. But several of the things that didn't work in the older (Oct) version which I still have online at: work in the current release.

I'd like to find a way to migrate the data from the Oct version to the Dec version.

If anyone has suggestions on how to proceed beyond the installation to work with the dotlrn I'd appreciate hearing from you.