stable containers use potentially outdated epic@main

[veprbl]

The @main version is the default version defined here

containers/spack-environment/xl/spack.yaml

Line 34 in 892e0b7

- epic@main # EPIC_VERSION

that is replaced in

containers/containers/eic/Dockerfile

Lines 187 to 192 in 892e0b7

	if [ "${EPIC_VERSION}" != "c1827f05430b2051df8a0b421db1cbab87165e0b" ] ; then
	export EPIC_VERSION=$(jq -r .sha /tmp/epic.json)
	sed -i "/# EPIC_VERSION$/ s/epic\s/epic@git.${EPIC_VERSION}=main /" /opt/spack-environment/${ENV}/spack.yaml
	sed -i "/# EPIC_VERSION$/ s/epic@main\s/epic@git.${EPIC_VERSION}=main /" /opt/spack-environment/${ENV}/spack.yaml
	spack deconcretize -y --all epic
	fi

that is not overridden in default/stable arguments:

containers/.gitlab-ci.yml

Lines 441 to 446 in 892e0b7

	${IF_BUILD_DEFAULT+
	${EDM4EIC_VERSION:+--build-arg EDM4EIC_VERSION=${EDM4EIC_VERSION}}
	${EICRECON_VERSION:+--build-arg EICRECON_VERSION=${EICRECON_VERSION}}
	${EPIC_VERSION:+--build-arg EPIC_VERSION=${EPIC_VERSION}}
	${JUGGLER_VERSION:+--build-arg JUGGLER_VERSION=${JUGGLER_VERSION}}
	}

This is resulting in:

singularity exec /cvmfs/singularity.opensciencegrid.org/eicweb/eic_xl:nightly spack find epic
epic@25.06.0  epic@25.06.1  epic@25.07.0  epic@25.08.0  epic@25.09.0  epic@git.dfc8b03a39d293e463be8e159cddeee0a8732356=main

but

singularity exec /cvmfs/singularity.opensciencegrid.org/eicweb/eic_xl:25.09.0-stable spack find epic
epic@25.06.0  epic@25.06.1  epic@25.07.0  epic@25.08.0  epic@25.09.0  epic@main

The reason why @main is a worser version spec compared to @git.${EPIC_VERSION}=main is that the prior may be using a cached revision, which may be out of date. A particular consequence of this is that release containers can have
/opt/detectors/epic-main that is older than the latest /opt/detectors/epic-YY.MM.X .

The epic geometry package is a particular special case because other packages like EICrecon have a version pointing to a tagged release (updated manually on each container release).