SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Paymenter Script fails with composer error #923

New Issue
Closed
opened 2025-11-20 04:56:35 -05:00 by saavagebueno · 8 comments
saavagebueno commented 2025-11-20 04:56:35 -05:00
Owner
Copy Link

Originally created by @maccaspro on GitHub (Apr 13, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Paymenter

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/paymenter.sh)"

📝 Provide a clear and concise description of the issue.

Script runs, accepts choices, defaults or custom settings, privileged or unprivileged, doesn't matter. After the stage "Installed Paymenter" it errors saying Composter plugins have been disabled for safety in this non-interactive session. Set COMPOSER_ALLOW_SUPERUSER=1 if you want to allow plugins to run as root/super user.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Run script, privileged or unprivileged, default settings or custom, doesn't matter.

❌ Paste the full error output (if available).

[ERROR] in line 56: exit code 0: while executing command $STD composer install --no-dev --optimize-autoloader --no-interaction

⠴Composer plugins have been disabled for safety in this non-interactive session.
Set COMPOSER_ALLOW_SUPERUSER=1 if you want to allow plugins to run as root/super user.
Do not run Composer as root/super user! See https://getcomposer.org/root for details
Installing dependencies from lock file
Verifying lock file contents can be installed on current platform.
⠦Your lock file does not contain a compatible set of packages. Please run composer update.

Problem 1
- Root composer.json requires PHP extension ext-intl * but it is missing from your system. Install or enable PHP's intl extension.
Problem 2
- filament/support is locked to version v3.3.8 and an update of this package was not requested.
- filament/support v3.3.8 requires ext-intl * -> it is missing from your system. Install or enable PHP's intl extension.
Problem 3
- openspout/openspout is locked to version v4.29.1 and an update of this package was not requested.
- openspout/openspout v4.29.1 requires php ~8.3.0 || ~8.4.0 -> your php version (8.2.28) does not satisfy that requirement.
Problem 4
- filament/widgets is locked to version v3.3.8 and an update of this package was not requested.
- filament/support v3.3.8 requires ext-intl * -> it is missing from your system. Install or enable PHP's intl extension.
- filament/widgets v3.3.8 requires filament/support v3.3.8 -> satisfiable by filament/support[v3.3.8].

Image

🖼️ Additional context (optional).

No response

Originally created by @maccaspro on GitHub (Apr 13, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Paymenter ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/paymenter.sh)" ### 📝 Provide a clear and concise description of the issue. Script runs, accepts choices, defaults or custom settings, privileged or unprivileged, doesn't matter. After the stage "Installed Paymenter" it errors saying Composter plugins have been disabled for safety in this non-interactive session. Set COMPOSER_ALLOW_SUPERUSER=1 if you want to allow plugins to run as root/super user. ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Run script, privileged or unprivileged, default settings or custom, doesn't matter. ### ❌ Paste the full error output (if available). [ERROR] in line 56: exit code 0: while executing command $STD composer install --no-dev --optimize-autoloader --no-interaction ⠴Composer plugins have been disabled for safety in this non-interactive session. Set COMPOSER_ALLOW_SUPERUSER=1 if you want to allow plugins to run as root/super user. Do not run Composer as root/super user! See https://getcomposer.org/root for details Installing dependencies from lock file Verifying lock file contents can be installed on current platform. ⠦Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - Root composer.json requires PHP extension ext-intl * but it is missing from your system. Install or enable PHP's intl extension. Problem 2 - filament/support is locked to version v3.3.8 and an update of this package was not requested. - filament/support v3.3.8 requires ext-intl * -> it is missing from your system. Install or enable PHP's intl extension. Problem 3 - openspout/openspout is locked to version v4.29.1 and an update of this package was not requested. - openspout/openspout v4.29.1 requires php ~8.3.0 || ~8.4.0 -> your php version (8.2.28) does not satisfy that requirement. Problem 4 - filament/widgets is locked to version v3.3.8 and an update of this package was not requested. - filament/support v3.3.8 requires ext-intl * -> it is missing from your system. Install or enable PHP's intl extension. - filament/widgets v3.3.8 requires filament/support v3.3.8 -> satisfiable by filament/support[v3.3.8]. ![Image](https://github.com/user-attachments/assets/e8c70062-3349-4d8b-9acb-502215a7be31) ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 04:56:35 -05:00
saavagebueno commented 2025-11-20 04:56:36 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 13, 2025):

Can you Upgrade your PHP and Test again?

@MickLesk commented on GitHub (Apr 13, 2025): Can you Upgrade your PHP and Test again?
saavagebueno commented 2025-11-20 04:56:36 -05:00
Author
Owner
Copy Link

@maccaspro commented on GitHub (Apr 13, 2025):

upgrade PHP on proxmox host or the LXC container?

@maccaspro commented on GitHub (Apr 13, 2025): upgrade PHP on proxmox host or the LXC container?
saavagebueno commented 2025-11-20 04:56:36 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 13, 2025):

On the LXC

@MickLesk commented on GitHub (Apr 13, 2025): On the LXC
saavagebueno commented 2025-11-20 04:56:36 -05:00
Author
Owner
Copy Link

@maccaspro commented on GitHub (Apr 13, 2025):

I've updated the LXC to php8.2-intl but I don't know how I can restart the script - it detects the existing failed installation and just ends saying it's up to date.

@maccaspro commented on GitHub (Apr 13, 2025): I've updated the LXC to php8.2-intl but I don't know how I can restart the script - it detects the existing failed installation and just ends saying it's up to date.
saavagebueno commented 2025-11-20 04:56:37 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 13, 2025):

Php8.3 or 8.4 please.

You need to update the txt File in /opt

@MickLesk commented on GitHub (Apr 13, 2025): Php8.3 or 8.4 please. You need to update the txt File in /opt
saavagebueno commented 2025-11-20 04:56:37 -05:00
Author
Owner
Copy Link

@maccaspro commented on GitHub (Apr 13, 2025):

Ok, updated to 8.4 and edited the version in the /opt file to induce the upgrade, but it ran with this error similar to the original:

Image

@maccaspro commented on GitHub (Apr 13, 2025): Ok, updated to 8.4 and edited the version in the /opt file to induce the upgrade, but it ran with this error similar to the original: ![Image](https://github.com/user-attachments/assets/332bd1c6-e7bc-46bc-8d50-7a4256cfe030)
saavagebueno commented 2025-11-20 04:56:37 -05:00
Author
Owner
Copy Link

@maccaspro commented on GitHub (Apr 13, 2025):

The original script didn't complete after it got stuck at the stage of creating the database.

I'm not sure how to re-run the script as a whole on an LXC already created with updated PHP - the script will only create a new LXC or update an existing one. I think the script needs review since it's a completely fresh LXC it creates and then cannot complete on.

@maccaspro commented on GitHub (Apr 13, 2025): The original script didn't complete after it got stuck at the stage of creating the database. I'm not sure how to re-run the script as a whole on an LXC already created with updated PHP - the script will only create a new LXC or update an existing one. I think the script needs review since it's a completely fresh LXC it creates and then cannot complete on.
saavagebueno commented 2025-11-20 04:56:37 -05:00
Author
Owner
Copy Link

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

done with https://github.com/community-scripts/ProxmoxVE/pull/3825

@MickLesk commented on GitHub (Apr 14, 2025): done with https://github.com/community-scripts/ProxmoxVE/pull/3825
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#923
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?