From: Taco Hoekwater <taco@bittext.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: Invalid certificate for distribution.contextgarden.net
Date: Thu, 23 Nov 2023 11:32:45 +0100 [thread overview]
Message-ID: <EF57E7F2-FC89-4052-B0CE-2427B016FB2A@bittext.nl> (raw)
In-Reply-To: <20231123111408.1565fd01@homerow>
> On 23 Nov 2023, at 11:14, Marco Patzer <lists@homerow.info> wrote:
>
> On Thu, 23 Nov 2023 08:58:56 +0100
> Taco Hoekwater <taco@bittext.nl> wrote:
>
>>> probably a side effect if moving some more to the (ntg) server in
>>> the netherlands (also setting up the build there)
>>
>> Even if it used the right certificate, it would not work right now
>> because of the move: there is nothing behind the connection.
>
> I used that server to check for the latest context version. What's
> the recommended way to check for the latest version? Basically the
> output of the \contextversion command?
The command
context —version
gives the local installed version.
Not sure whether there is a clean way to see if there is a remote newer update without actually doing an update. You can check the mailing list, all new releases by Hans are now reported on the ntg-context list, but that may be less convenient than an actual test. mtx-install.sh does not have a —dry-run or —upgradable switch, afaik.
Personally, I just run “bash install.sh” when I suspect there is a relevant update (install.sh is in the top-level context installation directory).
Best wishes,
Taco
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-11-23 10:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 20:47 [NTG-context] " Marco Patzer
2023-11-23 7:49 ` [NTG-context] " Hans Hagen
2023-11-23 7:58 ` Taco Hoekwater
2023-11-23 8:13 ` Henning Hraban Ramm
2023-11-23 10:14 ` Marco Patzer
2023-11-23 10:32 ` Taco Hoekwater [this message]
2023-11-23 11:06 ` 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=EF57E7F2-FC89-4052-B0CE-2427B016FB2A@bittext.nl \
--to=taco@bittext.nl \
--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).