β
Have you read and understood the above guidelines?
yes
π Did you run the script with verbose mode enabled?
Yes, verbose mode was enabled and the output is included below
π What is the name of the script you are using?
Karakeep
π What was the exact command used to execute the script?
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/karakeep.sh)"
βοΈ What settings are you using?
π₯οΈ Which Linux distribution are you using?
Debian 13
π Which Proxmox version are you on?
9.1.6
π Provide a clear and concise description of the issue.
Bug: KaraKeep update writes wrong SERVER_VERSION to karakeep.env
Description
When updating KaraKeep via the Proxmox community script, the script writes the wrong version into:
/etc/karakeep/karakeep.env
The issue appears to be caused by the variable CHECK_UPDATE_RELEASE being reused globally.
The script first checks the Karakeep GitHub release:
if check_for_gh_release "karakeep" "karakeep-app/karakeep"; then
Then it deploys KaraKeep:
CLEAN_INSTALL=1 fetch_and_deploy_gh_release "karakeep" "karakeep-app/karakeep" "tarball"
Later, the script calls:
setup_meilisearch
After that, it writes the version to karakeep.env using:
sed -i "s/^SERVER_VERSION=.*$/SERVER_VERSION=${CHECK_UPDATE_RELEASE#v}/" /etc/karakeep/karakeep.env
The problem is that CHECK_UPDATE_RELEASE no longer necessarily contains the Karakeep release at this point. It seems to have been overwritten by the Meilisearch (current version 1.43.0) update/check logic.
π Steps to reproduce the issue.
Update Karakeep and check the Version in the karakeep.env
β Paste the full error output (if available).
πΌοΈ Additional context (optional).
No response
β Have you read and understood the above guidelines?
yes
π Did you run the script with verbose mode enabled?
Yes, verbose mode was enabled and the output is included below
π What is the name of the script you are using?
Karakeep
π What was the exact command used to execute the script?
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/karakeep.sh)"
βοΈ What settings are you using?
π₯οΈ Which Linux distribution are you using?
Debian 13
π Which Proxmox version are you on?
9.1.6
π Provide a clear and concise description of the issue.
Bug: KaraKeep update writes wrong
SERVER_VERSIONtokarakeep.envDescription
When updating KaraKeep via the Proxmox community script, the script writes the wrong version into:
/etc/karakeep/karakeep.envThe issue appears to be caused by the variable
CHECK_UPDATE_RELEASEbeing reused globally.The script first checks the Karakeep GitHub release:
if check_for_gh_release "karakeep" "karakeep-app/karakeep"; thenThen it deploys KaraKeep:
CLEAN_INSTALL=1 fetch_and_deploy_gh_release "karakeep" "karakeep-app/karakeep" "tarball"Later, the script calls:
setup_meilisearchAfter that, it writes the version to karakeep.env using:
sed -i "s/^SERVER_VERSION=.*$/SERVER_VERSION=${CHECK_UPDATE_RELEASE#v}/" /etc/karakeep/karakeep.envThe problem is that
CHECK_UPDATE_RELEASEno longer necessarily contains the Karakeep release at this point. It seems to have been overwritten by the Meilisearch (current version1.43.0) update/check logic.π Steps to reproduce the issue.
Update Karakeep and check the Version in the
karakeep.envβ Paste the full error output (if available).
πΌοΈ Additional context (optional).
No response