starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 12 Packages Projects Releases 10 Wiki Activity

Karakeep not updating to v0.28.0 #2002

New Issue
Closed
opened 2026-02-05 03:17:03 +03:00 by OVERLORD · 7 comments
OVERLORD commented 2026-02-05 03:17:03 +03:00
Owner
Copy Link

Originally created by @Hexus0101 on GitHub (Nov 14, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 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?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

8.4.14

📝 Provide a clear and concise description of the issue.

I try to upgrade Karakeep from 0.27.1 to 0.28.0 and get the following error.
I tried with Debian 12 and Debian 13

🔄 Steps to reproduce the issue.

Open LXC container and run the update script (either via update or bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/karakeep.sh)"

❌ Paste the full error output (if available).

  ✔️   Update available: karakeep 0.27.1 → 0.28.0
  ✔️   Stopped Services
  ⏳   Updating yt-dlpCurrent version: nightly@2025.09.16.232710 from yt-dlp/yt-dlp-nightly-builds
Latest version: nightly@2025.11.12.005349 from yt-dlp/yt-dlp-nightly-builds
Current Build Hash: fad8b7bd9eae309b8545e92138413de41eaffee047a7978f9ee375b072abc530
Updating to nightly@2025.11.12.005349 from yt-dlp/yt-dlp-nightly-builds ...
Updated yt-dlp to nightly@2025.11.12.005349 from yt-dlp/yt-dlp-nightly-builds
  ✔️   Updated yt-dlp
graphicsmagick is already the newest version (1.4+really1.3.45+hg17696-1).
ghostscript is already the newest version (10.05.1~dfsg-1+deb13u1).
The following packages were automatically installed and are no longer required:
  g++-12           libavif15      libdav1d6        libevent-2.1-7  libjxl0.7   libopenh264-7  libstdc++-12-dev  libunwind-16  libxcb-dri2-0
  libabsl20220623  libc++1-16     libdrm-nouveau2  libflac12       libllvm15   libpaper1      libsvtav1enc1     libutempter0
  libassuan0       libc++abi1-16  libdrm-radeon1   libglapi-mesa   libnsl-dev  librav1e0      libtirpc-dev      libx265-199
Use 'apt autoremove' to remove them.

Summary:
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
  ✔️   Update prepared
  ✔️   Deployed: karakeep (0.28.0)
Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://deb.debian.org/debian trixie-updates InRelease                                       
Hit:3 http://security.debian.org trixie-security InRelease                                        
Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease                                     
All packages are up to date.                         
Warning: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details

removed 27 packages, and changed 77 packages in 3s

28 packages are looking for funding
  run `npm fund` for details
  ✔️   Update Node.js 22
  ✔️   Installed Node.js modules: pnpm@9.15.9
  ⏳   Updating KarakeepScope: all 25 workspace projects
 ERR_PNPM_OUTDATED_LOCKFILE  Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with <ROOT>/packages/plugins-search-meilisearch/package.json

Note that in CI environments this setting is true by default. If you still need to run install in such cases, use "pnpm install --no-frozen-lockfile"

    Failure reason:
    specifiers in the lockfile ({}) don't match specs in package.json ({"@karakeep/prettier-config":"workspace:^0.1.0","@karakeep/tsconfig":"workspace:^0.1.0","vite-tsconfig-paths":"^4.3.1","vitest":"^3.2.4","@karakeep/shared":"workspace:*","meilisearch":"^0.45.0"})

[ERROR] in line 72: exit code 0: while executing command $STD pnpm install --frozen-lockfile

🖼️ Additional context (optional).

No response

Originally created by @Hexus0101 on GitHub (Nov 14, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 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? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 8.4.14 ### 📝 Provide a clear and concise description of the issue. I try to upgrade Karakeep from `0.27.1` to `0.28.0` and get the following error. I tried with Debian 12 and Debian 13 ### 🔄 Steps to reproduce the issue. Open LXC container and run the update script (either via `update` or `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/karakeep.sh)"` ### ❌ Paste the full error output (if available). ``` ✔️ Update available: karakeep 0.27.1 → 0.28.0 ✔️ Stopped Services ⏳ Updating yt-dlpCurrent version: nightly@2025.09.16.232710 from yt-dlp/yt-dlp-nightly-builds Latest version: nightly@2025.11.12.005349 from yt-dlp/yt-dlp-nightly-builds Current Build Hash: fad8b7bd9eae309b8545e92138413de41eaffee047a7978f9ee375b072abc530 Updating to nightly@2025.11.12.005349 from yt-dlp/yt-dlp-nightly-builds ... Updated yt-dlp to nightly@2025.11.12.005349 from yt-dlp/yt-dlp-nightly-builds ✔️ Updated yt-dlp graphicsmagick is already the newest version (1.4+really1.3.45+hg17696-1). ghostscript is already the newest version (10.05.1~dfsg-1+deb13u1). The following packages were automatically installed and are no longer required: g++-12 libavif15 libdav1d6 libevent-2.1-7 libjxl0.7 libopenh264-7 libstdc++-12-dev libunwind-16 libxcb-dri2-0 libabsl20220623 libc++1-16 libdrm-nouveau2 libflac12 libllvm15 libpaper1 libsvtav1enc1 libutempter0 libassuan0 libc++abi1-16 libdrm-radeon1 libglapi-mesa libnsl-dev librav1e0 libtirpc-dev libx265-199 Use 'apt autoremove' to remove them. Summary: Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0 ✔️ Update prepared ✔️ Deployed: karakeep (0.28.0) Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian trixie-updates InRelease Hit:3 http://security.debian.org trixie-security InRelease Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease All packages are up to date. Warning: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details removed 27 packages, and changed 77 packages in 3s 28 packages are looking for funding run `npm fund` for details ✔️ Update Node.js 22 ✔️ Installed Node.js modules: pnpm@9.15.9 ⏳ Updating KarakeepScope: all 25 workspace projects  ERR_PNPM_OUTDATED_LOCKFILE  Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with <ROOT>/packages/plugins-search-meilisearch/package.json Note that in CI environments this setting is true by default. If you still need to run install in such cases, use "pnpm install --no-frozen-lockfile" Failure reason: specifiers in the lockfile ({}) don't match specs in package.json ({"@karakeep/prettier-config":"workspace:^0.1.0","@karakeep/tsconfig":"workspace:^0.1.0","vite-tsconfig-paths":"^4.3.1","vitest":"^3.2.4","@karakeep/shared":"workspace:*","meilisearch":"^0.45.0"}) [ERROR] in line 72: exit code 0: while executing command $STD pnpm install --frozen-lockfile ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 03:17:03 +03:00
OVERLORD commented 2026-02-05 03:17:17 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 14, 2025):

try to remove the karakeep folder (but idk if there are user data inside? - if yes, just move karakeep to karakeep_bak at first), then edit /root/.karakeep and change number -> update again

@MickLesk commented on GitHub (Nov 14, 2025): try to remove the karakeep folder (but idk if there are user data inside? - if yes, just move karakeep to karakeep_bak at first), then edit /root/.karakeep and change number -> update again
OVERLORD commented 2026-02-05 03:17:22 +03:00
Author
Owner
Copy Link

@Hexus0101 commented on GitHub (Nov 14, 2025):

I wasn't sure which karakeep folder you mean, so I tried removing the following folders
/etc/karakeep
/opt/karakeep
/opt/karakeep_data
and changed the version in /root/.karakeep back to 0.27.1

But the update still fails with same error message (unless removing /opt/karakeep/ where it fails because of missing installation)

I also installed a new instance of karakeep and made an import from my data. This would work to solve my issue, but if we find a way to upgrade my old LXC it would be nice, since I could keep my lists structure in karakeep (was not imported)

@Hexus0101 commented on GitHub (Nov 14, 2025): I wasn't sure which karakeep folder you mean, so I tried removing the following folders `/etc/karakeep` `/opt/karakeep` `/opt/karakeep_data` and changed the version in `/root/.karakeep` back to 0.27.1 But the update still fails with same error message (unless removing /opt/karakeep/ where it fails because of missing installation) I also installed a new instance of karakeep and made an import from my data. This would work to solve my issue, but if we find a way to upgrade my old LXC it would be nice, since I could keep my lists structure in karakeep (was not imported)
OVERLORD commented 2026-02-05 03:17:28 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 14, 2025):

@MohamedBassem , did you need the --frozen-lockfile ? In Dockerfile & karakeep-linux.sh it exist, like our script, but we get here ERR_PNPM_OUTDATED_LOCKFILE ?

@MickLesk commented on GitHub (Nov 14, 2025): @MohamedBassem , did you need the --frozen-lockfile ? In Dockerfile & karakeep-linux.sh it exist, like our script, but we get here ERR_PNPM_OUTDATED_LOCKFILE ?
OVERLORD commented 2026-02-05 03:17:31 +03:00
Author
Owner
Copy Link

@MohamedBassem commented on GitHub (Nov 14, 2025):

@MickLesk I'd prefer if we keep the -frozen-lockfile. I think by quickly reading the update script that we're updating the code in place. With every release, we should nuke the old code directory and refetch the new zip file from github and that should eliminate this problem.

@MohamedBassem commented on GitHub (Nov 14, 2025): @MickLesk I'd prefer if we keep the `-frozen-lockfile`. I *think* by quickly reading the update script that we're updating the code in place. With every release, we should nuke the old `code` directory and refetch the new zip file from github and that should eliminate this problem.
OVERLORD commented 2026-02-05 03:17:35 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 14, 2025):

You're right, I completely overlooked that. Sorry for pinging 😄 Let's see if PR #9144 is enough.

@MickLesk commented on GitHub (Nov 14, 2025): You're right, I completely overlooked that. Sorry for pinging :smile: Let's see if PR #9144 is enough.
OVERLORD commented 2026-02-05 03:17:44 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Nov 14, 2025):

Fix merged.

@michelroegl-brunner commented on GitHub (Nov 14, 2025): Fix merged.
OVERLORD commented 2026-02-05 03:17:49 +03:00
Author
Owner
Copy Link

@Hexus0101 commented on GitHub (Nov 14, 2025):

I can confirm that the Fix works. Thank you all for your quick help! 🚀

@Hexus0101 commented on GitHub (Nov 14, 2025): I can confirm that the Fix works. Thank you all for your quick help! 🚀
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#2002
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?