From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: [NTG-context] Re: issue with module update
Date: Mon, 11 Mar 2024 19:22:53 +0100 [thread overview]
Message-ID: <71ac6c53-6446-ccdb-a2f7-ccc3ae67c3c9@gmx.es> (raw)
In-Reply-To: <CCA1626A-87D0-4C18-9460-125B90EACD13@bittext.nl>
On 3/11/24 17:17, Taco Hoekwater wrote:
>> On 11 Mar 2024, at 16:57, Pablo Rodriguez wrote:
>> [...]
>> Is there something I am missing here?
>
> One of your releases had “changed-name” as its release ‘number’.
>
> The modules site does not know how to deal with non-numeric release
> names all that well; it made a mess of its symlinking stage.
>
> I fixed the symlink manually, it should be fine now.
Really sorry for causing you problems when updating the modules, Taco.
I had no idea that non-numeric releases were problematic with symbolic
linking.
I made that change to avoid having two releases with the same date (I
think this also may give issues with symlinks).
Well, I realize that if I make a wrong release, I have to number the new
version with only numbers (and maybe points instead of hyphens).
Sorry again for giving problems and many thanks for your work,
Pablo
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2024-03-11 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 15:57 [NTG-context] " Pablo Rodriguez via ntg-context
2024-03-11 16:17 ` [NTG-context] " Taco Hoekwater
2024-03-11 18:22 ` Pablo Rodriguez via ntg-context [this message]
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=71ac6c53-6446-ccdb-a2f7-ccc3ae67c3c9@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).