Update timestamps

opencog/atomspace/Dockerfile

@@ -29,11 +29,11 @@ RUN  /tmp/octool -c && ccache -C
 
 # Update Link Grammar. This avoids having to rebuild the opencog/deps
 # This installs the latest release tarball, and NOT github master.
-ENV LAST_ATOMSPACE_UPDATE 2024-03-28
+ENV LAST_LINK_GRAMMAR_UPDATE 2024-03-28
 RUN  /tmp/octool -l default && ccache -C
 
 # Install core AtomSpace.
-ENV LAST_ATOMSPACE_UPDATE 2023-04-06
+ENV LAST_ATOMSPACE_UPDATE 2024-04-09
 RUN  /tmp/octool -a && ccache -C
 
 USER opencog

opencog/atomspace/README.md

@@ -7,11 +7,11 @@ CogStorageNode. It does *not* include nlp, unify, ure or pln.
 
 ## Building
 
-The container is build by the script in the directory below:
+The container is built by the script in the directory below:
 `../docker-build.sh -s`.
 
 ## Testing
-You can verify that the core AtomSpace is working:
+Optional. To verify that the core AtomSpace is working:
 
 * Run the container with `./run.sh`. This will put you into a prompt
   in the container.

opencog/base/Dockerfile

@@ -23,7 +23,7 @@ RUN apt-get -y install apt-transport-https software-properties-common \
 
 # Install ocpkg. Bump the date to get the latest ocpkg installed;
 # Otherwise, this docker build will be cached with an old octool.
-ENV LAST_OCPKG_UPDATE 2023-02-07
+ENV LAST_OCPKG_UPDATE 2024-04-07
 
 # The OCPKG_URL can be overridden by specifying
 # docker build --build-arg OCPKG_URL=https://some.where.else.com/ockpg

opencog/lang-pairs/README.md

@@ -76,7 +76,7 @@ and scripting system.
    `chown -R opencog:opencog text` ***IMPORTANT! Don't forget to do this!***
 3. `cd ~/experiments/run-1`
 4. Review the config files; change if desired. The defaults are fine
-   for an initial run. a Later on, you can copy them to
+   for an initial run. Later on, you can copy them to
    `experiments/run-2`, `experiments/run-3` and so on, for modified
    extended runs.
 5. `source 0-pipeline.sh`  # Load environment variables from config file.
@@ -114,6 +114,8 @@ E. Go to the `telnet` tab, and wait until the telnet stats clear ...
    after it has been submitted. Thus, you can track progress by comparing
    `find ~/text/input-pages/ |wc` to `find ~/text/pair-counted/ |wc`.
 
+XXX below is auto done already??
+
 F. Go to the `cogsrv` tab, and perform batch MI calculations.
    This may take minutes or hours, depending on the dataset.
    It is best not to start these until counting is done.