KAT 110.1.2 fails to build

Omniverse Core Platform Kit App Template / SDK
1

Operating System:
Windows
Linux
Kit Version:
110 (Kit App Template)
109 (Kit App Template)
108 (Kit App Template)
107 (Kit App Template)
106 (Kit App Template)
105 (Launcher)
Kit Template:
USD Composer
USD Explorer
USD Viewer
Custom
GPU Hardware:
A series (Blackwell)
A series (ADA)
A series
50 series
40 series
30 series
GPU Driver:
Latest
Recommended (573.xx)
Other
Work Flow: create new KAT template app
**Main Issue:

  • regression from KAT 110.1.1
    -** repo template new (and any repo command) fails during packman pull.
  • repo_docs 2.8.1 is pinned in tools/deps/repo-deps-nv.packman.xml, but isn’t resolvable from the configured cloudfront remote. The first dep in the same file (repo_ci 0.9.1) pulls fine, proving it’s a package-publishing gap, not a client-side connectivity/auth problem.

**Reproduction Steps:

  1. clone** GitHub - NVIDIA-Omniverse/kit-app-template: Omniverse Kit App Template · GitHub
  2. git checkout 110.1.2
  3. repo template new
    Error Code:
    Traceback (most recent call last):
    File “C:\work\nv\kat\tools\repoman\repoman.py”, line 40, in
    bootstrap()
    File “C:\work\nv\kat\tools\repoman\repoman.py”, line 31, in bootstrap
    deps = packmanapi.pull(file.as_posix())
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File “C:\packman-repo\packman-common\8.3.0\packman\utils.py”, line 515, in wrapper_message_block
    return func(*args, **kwargs)
    dep_map = pull_with_variable_file(
    ^^^^^^^^^^^^^^^^^^^^^^^^
    File “C:\packman-repo\packman-common\8.3.0\packman\main.py”, line 1124, in pull_with_variable_file
    pull_map = pull_dependencies(
    ^^^^^^^^^^^^^^^^^^
    File “C:\packman-repo\packman-common\8.3.0\packman\main.py”, line 1329, in pull_dependencies
    raise errors.PackmanErrorFileNotFound(
    packman.errors.PackmanErrorFileNotFound: Package not found on specified remote servers! (name: repo_docs, version: 2.8.1)
2

Yes we are aware of a temporary loss in service for Packman, just for kit 110.1.2. Please use 110.1.1 at the moment.