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

Hoarder Script Fails during package installation #144

New Issue
Closed
opened 2026-02-04 16:49:24 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-04 16:49:24 +03:00
Owner
Copy Link

Originally created by @esworp on GitHub (Dec 7, 2024).

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

✓ Updated Container OS
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
ca-certificates is already the newest version (20230311).
\Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
| chromium : Depends: libc++1-19 (>= 1:19.1.4) but it is not installable
Depends: libc++abi1-19 (>= 1:19.1.4) but it is not installable
Depends: libunwind-19 (>= 1:19.1.4) but it is not installable
Depends: chromium-common (= 131.0.6778.108-1~deb12u1) but it is not going to be installed
Recommends: chromium-sandbox but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

[ERROR] in line 17: exit code 0: while executing command $STD apt-get install -y g++ build-essential curl git sudo gnupg ca-certificates chromium mc
root@pve:~#

What settings are you currently utilizing?

  • Default Settings
  • Advanced Settings

Which Linux distribution are you employing?

Debian 12

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

No response

Please provide detailed steps to reproduce the issue.

Just kick off the script... : ]

Originally created by @esworp on GitHub (Dec 7, 2024). ### Please verify that you have read and understood the guidelines. yes ### A clear and concise description of the issue. > ✓ Updated Container OS > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > ca-certificates is already the newest version (20230311). > \Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > | chromium : Depends: libc++1-19 (>= 1:19.1.4) but it is not installable > Depends: libc++abi1-19 (>= 1:19.1.4) but it is not installable > Depends: libunwind-19 (>= 1:19.1.4) but it is not installable > Depends: chromium-common (= 131.0.6778.108-1~deb12u1) but it is not going to be installed > Recommends: chromium-sandbox but it is not going to be installed > E: Unable to correct problems, you have held broken packages. > > [ERROR] in line 17: exit code 0: while executing command $STD apt-get install -y g++ build-essential curl git sudo gnupg ca-certificates chromium mc > root@pve:~# ### What settings are you currently utilizing? - [X] Default Settings - [X] Advanced Settings ### Which Linux distribution are you employing? Debian 12 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. _No response_ ### Please provide detailed steps to reproduce the issue. Just kick off the script... : ]
OVERLORD commented 2026-02-04 16:49:37 +03:00
Author
Owner
Copy Link

@vhsdream commented on GitHub (Dec 7, 2024):

Sadly I can confirm this 😦

It's the Chromium package update. Working on a fix, just gotta test it.

@vhsdream commented on GitHub (Dec 7, 2024): Sadly I can confirm this 😦 It's the Chromium package update. Working on a fix, just gotta test it.
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
question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label
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#144
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?