Skip to content

Repository Health Check Failed #26935

Closed
Closed
Repository Health Check Failed#26935
Assignees
thunder-coding
Labels
health-checkApt repository health related issues. Usually created automatically by GitHub actions

Description

@termuxbot2
termuxbot2
opened on Oct 19, 2025

Errors found for aarch64

Errors: 
"command-not-found" "3.1-16" (in apt repository) != "3.1-17" (in termux-packages)
"crystal" "1.18.0" (in apt repository) != "1.18.1" (in termux-packages)
"libwebp" "1.6.0-rc1-0" (in apt repository) != "1.6.0-1" (in termux-packages)
"libxml2-python-static" 2.14.6: static package should not exist as parent package "libxml2-python" has TERMUX_PKG_NO_STATICSPLIT=true
"libxml2-static" "2.14.6" != 2.15.0 as expected by parent package. The -static package probably stopped existing after an update.
"luarocks" "3.12.2-1" (in apt repository) != "3.12.2-2" (in termux-packages)
"valkey-static" "8.1.4" != 8.1.4-1 as expected by parent package. The -static package probably stopped existing after an update.
Proposed Automated fixes: 
aptly repo remove "termux-main" "libxml2-python-static (=2.14.6) {aarch64}"
aptly repo remove "termux-main" "libxml2-static (=2.14.6) {aarch64}"
aptly repo remove "termux-main" "valkey-static (=8.1.4) {aarch64}"
Proposed Manual fixes: 
The package "command-not-found" in "termux-main" may not be up to date on the apt repository or a bogus version may be present
The package "crystal" in "termux-main" may not be up to date on the apt repository or a bogus version may be present
The package "libwebp" in "termux-main" may not be up to date on the apt repository or a bogus version may be present
The package "luarocks" in "termux-main" may not be up to date on the apt repository or a bogus version may be present

Errors found for arm

Errors: 
"command-not-found" "3.1-16" (in apt repository) != "3.1-17" (in termux-packages)
"libwebp" "1.6.0-rc1-0" (in apt repository) != "1.6.0-1" (in termux-packages)
"libxml2-python-static" 2.14.6: static package should not exist as parent package "libxml2-python" has TERMUX_PKG_NO_STATICSPLIT=true
"libxml2-static" "2.14.6" != 2.15.0 as expected by parent package. The -static package probably stopped existing after an update.
"luarocks" "3.12.2-1" (in apt repository) != "3.12.2-2" (in termux-packages)
"valkey-static" "8.1.4" != 8.1.4-1 as expected by parent package. The -static package probably stopped existing after an update.
Proposed Automated fixes: 
aptly repo remove "termux-main" "libxml2-python-static (=2.14.6) {arm}"
aptly repo remove "termux-main" "libxml2-static (=2.14.6) {arm}"
aptly repo remove "termux-main" "valkey-static (=8.1.4) {arm}"
Proposed Manual fixes: 
The package "command-not-found" in "termux-main" may not be up to date on the apt repository or a bogus version may be present
The package "libwebp" in "termux-main" may not be up to date on the apt repository or a bogus version may be present
The package "luarocks" in "termux-main" may not be up to date on the apt repository or a bogus version may be present

Errors found for i686

Errors: 
"command-not-found" "3.1-16" (in apt repository) != "3.1-17" (in termux-packages)
"libwebp" "1.6.0-rc1-0" (in apt repository) != "1.6.0-1" (in termux-packages)
"libxml2-python-static" 2.14.6: static package should not exist as parent package "libxml2-python" has TERMUX_PKG_NO_STATICSPLIT=true
"libxml2-static" "2.14.6" != 2.15.0 as expected by parent package. The -static package probably stopped existing after an update.
"luarocks" "3.12.2-1" (in apt repository) != "3.12.2-2" (in termux-packages)
"valkey-static" "8.1.4" != 8.1.4-1 as expected by parent package. The -static package probably stopped existing after an update.
Proposed Automated fixes: 
aptly repo remove "termux-main" "libxml2-python-static (=2.14.6) {i686}"
aptly repo remove "termux-main" "libxml2-static (=2.14.6) {i686}"
aptly repo remove "termux-main" "valkey-static (=8.1.4) {i686}"
Proposed Manual fixes: 
The package "command-not-found" in "termux-main" may not be up to date on the apt repository or a bogus version may be present
The package "libwebp" in "termux-main" may not be up to date on the apt repository or a bogus version may be present
The package "luarocks" in "termux-main" may not be up to date on the apt repository or a bogus version may be present

Errors found for x86_64

Errors: 
"command-not-found" "3.1-16" (in apt repository) != "3.1-17" (in termux-packages)
"libwebp" "1.6.0-rc1-0" (in apt repository) != "1.6.0-1" (in termux-packages)
"libxml2-python-static" 2.14.6: static package should not exist as parent package "libxml2-python" has TERMUX_PKG_NO_STATICSPLIT=true
"libxml2-static" "2.14.6" != 2.15.0 as expected by parent package. The -static package probably stopped existing after an update.
"luarocks" "3.12.2-1" (in apt repository) != "3.12.2-2" (in termux-packages)
"valkey-static" "8.1.4" != 8.1.4-1 as expected by parent package. The -static package probably stopped existing after an update.
Proposed Automated fixes: 
aptly repo remove "termux-main" "libxml2-python-static (=2.14.6) {x86_64}"
aptly repo remove "termux-main" "libxml2-static (=2.14.6) {x86_64}"
aptly repo remove "termux-main" "valkey-static (=8.1.4) {x86_64}"
Proposed Manual fixes: 
The package "command-not-found" in "termux-main" may not be up to date on the apt repository or a bogus version may be present
The package "libwebp" in "termux-main" may not be up to date on the apt repository or a bogus version may be present
The package "luarocks" in "termux-main" may not be up to date on the apt repository or a bogus version may be present

Activity

  1. termuxbot2
    assigned
    thunder-coding
    on Oct 19, 2025
  2. termuxbot2
    added
    health-checkApt repository health related issues. Usually created automatically by GitHub actions
    on Oct 19, 2025

  3. robertkirkman commented on Oct 19, 2025

    @robertkirkman
    robertkirkman
    on Oct 19, 2025
    Member

    "valkey-static" "8.1.4" != 8.1.4-1 as expected by parent package. The -static package probably stopped existing after an update.

    I can confirm that valkey-static does not exist anymore after an update and it's intentional, as a result of this:

    valkey-static used to contain a libhiredis.a that was part of the libhiredis that valkey was installing into itself, after I made it stop doing that the valkey-static package disappeared and I forgot to ask for it to be removed from the server.

    luarocks

    I'm not sure exactly what the problem is that caused this one, but the author of the relevant update to luarocks believes that it's necessary to run a rebuild of luarocks here in workflow_dispatch, maybe someone can check that

    Image

    crystal

    GitHub Actions bumped this, but then experienced the error "this job was cancelled by a higher-priority job". When I manually triggered a rerun of the failed job just now, it succeeded and all enabled architectures of crystal (one) are now uploaded to the repository. It seems like @termuxbot2 might have queued bumps too soon after each other, but I haven't seen that happen in a long time so I'm not sure. I thought that @termuxbot2 was configured to wait a substantial delay in between committing bumps.

    Image

    There was a delay of 4 minutes in between crystal and llama-cpp, which seems appropriate, but the build of crystal took 13 minutes to complete and reach the upload stage, so unfortunately it might have been "cancelled by a higher-priority job" that started some time within those 13 minutes.

  4. robertkirkman commented on Oct 19, 2025

    @robertkirkman
    robertkirkman
    on Oct 19, 2025
    Member

    "libxml2-python-static" 2.14.6: static package should not exist as parent package "libxml2-python" has TERMUX_PKG_NO_STATICSPLIT=true
    "libxml2-static" "2.14.6" != 2.15.0 as expected by parent package. The -static package probably stopped existing after an update.

    I believe that after

    libxml2 has been switched from Autotools to Meson, which probably no longer builds the static libraries by default, explaining the removal+disappearance of the static subpackages of libxml2.

  5. termuxbot2
    closed this as completedon Nov 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

health-checkApt repository health related issues. Usually created automatically by GitHub actions

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions