Summary
The template-Exasol-all-python-3.10 flavor pins exact apt package versions that have since been removed from the Ubuntu 22.04 (jammy) archive. Ubuntu publishes rolling security updates and drops superseded point-releases, so a fresh build of this flavor today fails at exaslpm install with Version 'X' for 'Y' was not found.
This is the same recurring class as the previously-fixed #839 / #247 / #250 ("Update ubuntu packages").
Affected version
- Repo:
exasol/script-languages-release
- Tag: 11.1.1 (commit
d4e183d95d7c4ba977d7508f32eead75d9d01bc9)
- Flavor:
template-Exasol-all-python-3.10
Concrete failures (fresh build, no cache)
Build step udfclient_deps:
E: Version '3.0.2-0ubuntu1.21' for 'libssl-dev' was not found
apt-cache madison libssl-dev in a current ubuntu:22.04 now offers only 3.0.2-0ubuntu1.25 (jammy-updates / jammy-security) and the base 3.0.2-0ubuntu1 — …1.21 is gone.
Build step build_deps:
E: Version '7.81.0-1ubuntu1.23' for 'curl' was not found
E: Version '11.0.30+7-1ubuntu1~22.04' for 'openjdk-11-jdk-headless' was not found
Both pinned point-releases have likewise been superseded and removed from the archive.
Pins found in the flavor:
flavors/template-Exasol-all-python-3.10/packages.yml
flavors/template-Exasol-all-python-3.10/flavor_base/udfclient_deps/packages/apt_get_packages
flavors/template-Exasol-all-python-3.10/flavor_base/build_deps/packages/apt_get_packages
Impact
A from-scratch SLC build of this flavor fails. This surfaces in the Exasol AI Lab script_languages_container/export_as_is.ipynb notebook (slc.export()), which builds the flavor locally when the prebuilt images are not pulled from a registry.
Suggested fix
Refresh the pinned apt versions for jammy to the currently-available point-releases (e.g. libssl-dev=3.0.2-0ubuntu1.25), or relax the exact-version pinning for packages that only receive security point-releases. Related: the long-standing request in #557 to fail the build with a clearer message when a requested version is unavailable.
Notes
Reproduced while running the flavor build under rootless Podman (Exasol AI Lab on Ubuntu 22.04). The failure is environment-independent — it reproduces under stock Docker as well, since the pinned versions are simply no longer in the Ubuntu archive.
Summary
The
template-Exasol-all-python-3.10flavor pins exact apt package versions that have since been removed from the Ubuntu 22.04 (jammy) archive. Ubuntu publishes rolling security updates and drops superseded point-releases, so a fresh build of this flavor today fails atexaslpm installwithVersion 'X' for 'Y' was not found.This is the same recurring class as the previously-fixed #839 / #247 / #250 ("Update ubuntu packages").
Affected version
exasol/script-languages-released4e183d95d7c4ba977d7508f32eead75d9d01bc9)template-Exasol-all-python-3.10Concrete failures (fresh build, no cache)
Build step
udfclient_deps:apt-cache madison libssl-devin a currentubuntu:22.04now offers only3.0.2-0ubuntu1.25(jammy-updates / jammy-security) and the base3.0.2-0ubuntu1—…1.21is gone.Build step
build_deps:Both pinned point-releases have likewise been superseded and removed from the archive.
Pins found in the flavor:
flavors/template-Exasol-all-python-3.10/packages.ymlflavors/template-Exasol-all-python-3.10/flavor_base/udfclient_deps/packages/apt_get_packagesflavors/template-Exasol-all-python-3.10/flavor_base/build_deps/packages/apt_get_packagesImpact
A from-scratch SLC build of this flavor fails. This surfaces in the Exasol AI Lab
script_languages_container/export_as_is.ipynbnotebook (slc.export()), which builds the flavor locally when the prebuilt images are not pulled from a registry.Suggested fix
Refresh the pinned apt versions for jammy to the currently-available point-releases (e.g.
libssl-dev=3.0.2-0ubuntu1.25), or relax the exact-version pinning for packages that only receive security point-releases. Related: the long-standing request in #557 to fail the build with a clearer message when a requested version is unavailable.Notes
Reproduced while running the flavor build under rootless Podman (Exasol AI Lab on Ubuntu 22.04). The failure is environment-independent — it reproduces under stock Docker as well, since the pinned versions are simply no longer in the Ubuntu archive.