Re: [Modules] When the version string naturally contains the variant delimiter "+"

[Xavier D. <xav...@gm...>]

Hi Martin,

I would suggest to disable the advanced_version_spec configuration
option [1] as your module names are not compatible with the variant
specification syntax.

module config advanced_version_spec 0

This command could be set in global initrc file [2]

Regards,
Xavier

[1] https://modules.readthedocs.io/en/latest/module.html#mconfig-advanced_version_spec
[2] https://modules.readthedocs.io/en/latest/INSTALL.html#configuration

Le mar. 20 juin 2023 à 20:15, D'Anjou, Martin via Modules-interest
<mod...@li...> a écrit :
>
> Hi,
>
>
>
> I am trying to upgrade environment modules and I am running into an issue with the variant feature.
>
> Java version strings contain the “+” plus sign, for example: openjdk-hs-17.0.1+12
>
>
>
> When I load it with --debug, I get:
>
> DEBUG setModuleVersSpec: Set module 'openjdk-hs/17.0.1' (escglob 'openjdk-hs/17.0.1'),  module name 'openjdk-hs' (re ''), module root 'openjdk-hs', version cmp 'eq', version(s) '', variant(s) '{12 1 1}' and module name version spec 'openjdk-hs/17.0.1' for argument 'openjdk-hs/17.0.1+12'
>
> ..
>
> ERROR: Unable to locate a modulefile for 'openjdk-hs/17.0.1+12'
>
>
>
> I can see the file exists and load just fine with the older version of modules, but not when I upgrade to 5.0.1.
>
>
>
> In the code, I see the split on the “+” sign happening in modules/tcl/modspec.tcl/setModuleVersSpec line 1561, so it looks baked in and unavoidable.
>
>
>
> I am trying to avoid any disruption to the users, does anyone have advice on how to approach this problem?
>
> Or maybe add something non-disturbing to my existing installation so the upgrade could be seamless, and my users would not have to modify their code?
>
>
>
> Thanks,
>
> Martin
>
>
>
>
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest