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 13 Packages Projects Releases 10 Wiki Activity

Kimai update fails in various ways #973

New Issue
Closed
opened 2026-02-04 22:23:01 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-04 22:23:01 +03:00
Owner
Copy Link

Originally created by @jamezpolley on GitHub (May 17, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Kimai

📂 What was the exact command used to execute the script?

update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

Update: As per instructions this one "bug" is now about several completely unrelated issues, and as such it's not possible to provide a "clear and concise description" of the issue. See #4247 and #4550 and #4552 for some of the details I'd provided. I'm not going to bother with any other details, as that doesn't seem to be wanted, I'll just keep tacking on unrelated fixes to the same branch

I think I first installed kimai around Sep 2024; probably haven't done an update since then.

Trying to run the update script gives the output below.

Source of the error seems to be (L35)[67feae778e/ct/kimai.sh (L35)] - script assumes lsb-release is already installed.

🔄 Steps to reproduce the issue.

update

❌ Paste the full error output (if available).

(Reading database ... 30881 files and directories currently installed.)
Preparing to unpack .../debsuryorg-archive-keyring.deb ...
Unpacking debsuryorg-archive-keyring (2025.03.13) over (2025.03.13) ...
Setting up debsuryorg-archive-keyring (2025.03.13) ...
⠸ Migrating PHP 8.2 to 8.4sh: 1: lsb_release: not found
E: Malformed entry 1 in list file /etc/apt/sources.list.d/php.list (Component)
E: The list of sources could not be read.
⠴ Migrating PHP 8.2 to 8.4
[ERROR] in line 36: exit code 0: while executing command $STD apt-get update

🖼️ Additional context (optional).

No response

Originally created by @jamezpolley on GitHub (May 17, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Kimai ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Update: As per [instructions](https://github.com/community-scripts/ProxmoxVE/issues/4552#issuecomment-2888087496) this one "bug" is now about several completely unrelated issues, and as such it's not possible to provide a "clear and concise description" of the issue. See #4247 and #4550 and #4552 for some of the details I'd provided. I'm not going to bother with any other details, as that doesn't seem to be wanted, I'll just keep tacking on unrelated fixes to the same branch ----- I think I first installed kimai around Sep 2024; probably haven't done an update since then. Trying to run the update script gives the output below. Source of the error seems to be (L35)[https://github.com/community-scripts/ProxmoxVE/blob/67feae778edb280a7b1ae5e333f9b82f90e0e98d/ct/kimai.sh#L35] - script assumes lsb-release is already installed. ### 🔄 Steps to reproduce the issue. > update ### ❌ Paste the full error output (if available). (Reading database ... 30881 files and directories currently installed.) Preparing to unpack .../debsuryorg-archive-keyring.deb ... Unpacking debsuryorg-archive-keyring (2025.03.13) over (2025.03.13) ... Setting up debsuryorg-archive-keyring (2025.03.13) ... ⠸ Migrating PHP 8.2 to 8.4sh: 1: lsb_release: not found E: Malformed entry 1 in list file /etc/apt/sources.list.d/php.list (Component) E: The list of sources could not be read. ⠴ Migrating PHP 8.2 to 8.4 [ERROR] in line 36: exit code 0: while executing command $STD apt-get update ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 22:23:01 +03:00
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#973
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?