treydock

For Ubuntu we deploy nodejs repos specific to a given nodejs version so not using what comes from OS. This seems very do-able for 2.0 release.

It's actually a lot more work to cut 2.1 than to just backport to 2.0, especially given we've been working in 2.1 repos from master branch. From my perspective a...

Just FYI that 2.0.29 is not yet in 2.0 repos. We don't put new RPMs into the release repos, like 2.0, until it's been tested for a little bit at...

Yep, that's how OSC installs OnDemand, from latest. This maybe redundant information but I always like to warn people of the dangers of using the "latest" repo since it does...

That exclude rule we use (in my previous comment) would wok with those since it excludes anything beginning with ondemand and container 2.1. Those passenger RPMs are built for OnDemand...

Ah might have to adjust the rule to be `onemand*-2.1* ondemand*ood2.1*`, just noticed the wildcards might not catch that passenger RPM. So far we've not had issues with those packages...

The gridmap usage in OnDemand was only ever used by OSC, and it requires tools that we have archived on Github for years. There is nothing to update I would...

Those errors look like issues contacting Rocky Linux repos, nothing to do with OnDemand. Sometimes that happens. Container networking is far different than how curl works outside the container so...

Looks like networking issues with Docker. One way to likely debug and see if really an issue with Docker is something like this: ``` docker run --rm -it rockylinux:8 /bin/bash...

I think multiline strings are the wrong approach, we should just support array of lines. Multiline strings for things like Puppet would be ugly to implement especially in Hiera. It's...