ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Marco Patzer <lists@homerow.info>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: ConTeXt version stuck at 2020.01.30
Date: Tue, 5 May 2020 20:26:06 +0200	[thread overview]
Message-ID: <20200505202606.37d0dfb7@homerow> (raw)

Hi!

Has something changed regarding the installation/update procedure?
ConTeXt seems to be stuck at 2020.01.30 and downloading the newest
version results in that very version.

Steps to reproduce:

  rsync -ptv rsync://contextgarden.net/minimals/setup/first-setup.sh .
  sh ./first-setup.sh
  . tex/setuptex
  context --version
  → current version: 2020.01.30 14:13

According to

  https://minimals.contextgarden.net/current/context/

the directory “latest” seems to contain the latest version, rather
than the “beta”. first-setup.sh however uses the “beta” directory.

Has something changed and first-setup.sh hasn't been updated to
reflect that change? Or is something else going on? Adapting
first-setup.sh to mirror from the “latest” directory seems to fetch
the latest version:

  rsync -ptv rsync://contextgarden.net/minimals/setup/first-setup.sh .
  sed -s '/\/bin\/mtxrun/s/--context=beta/--context=latest/' first-setup.sh
  sh ./first-setup.sh
  . tex/setuptex
  context --version
  → current version: 2020.04.30 11:10

Marco
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2020-05-05 18:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-05 18:26 Marco Patzer [this message]
2020-05-05 18:38 ` Wolfgang Schuster
2020-05-05 19:38   ` Marco Patzer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200505202606.37d0dfb7@homerow \
    --to=lists@homerow.info \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).