• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved Exception: Failed to solve dependencies: requires perl(:MODULE_COMP_5.10.1)

luc

New Pleskian
Scenario: new installation of plesk 12.5 on centOS 7 into an OpenVZ container (proxmox):
While installing Plesk 12.5 I get the following error:

1: perl-JSON-XS-2.27-2.el6.x86_64 requires perl ( : MODULE_COMPAT_5.10.1 )
Contact support

any tips?
 
Last edited:
Maybe I'm wrong but the main problem is due to the missing "perl:)MODULE_COMP_5.10.1)", looks like it is installed a next version without retro compatibility.
 
Maybe I'm wrong but the main problem is due to the missing ...
... and that's exactly the point here. You have MISSING packages, which you should consider to INSTALL, in order to avoid such dependencies issues. ;)

looks like it is installed
??? What makes you think, that it IS installed, when the error message states clear:
requires perl ( : MODULE_COMPAT_5.10.1 )

I'll help you again, by QUOTING parts of the previous linked example site:
Code:
...
Requires :
perl(:MODULE_COMPAT_5.10.1)
perl(common::sense)
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(VersionedDependencies) <= 3.0.3-1
libc.so.6()(64bit)
libc.so.6(GLIBC_2.2.5)(64bit)
libc.so.6(GLIBC_2.3.4)(64bit)
libc.so.6(GLIBC_2.4)(64bit)
perl(common::sense)
perl(Encode)
perl(Exporter)
perl(Getopt::Long)
perl(JSON::XS)
perl(Storable)
perl(strict)
perl(XSLoader)
rpmlib(VersionedDependencies) <= 3.0.3-1
rtld(GNU_HASH)
/usr/bin/perl
rpmlib(PayloadIsXz) <= 5.2-1
...
Each required package is as well linked to another site, where you are able to DOWNLOAD the required package, in order to MANUALLY install the *.rpm with yum. :)

If you don't like the idea of installing perl - modules with yum, you are as well able to install them with CPAN or CPANminus ( cpanm ), if you like.
 
Last edited by a moderator:
Hi,
I already did the following steps:
1) yum install perl
-> as result : perl already installed and updated, nothing to do

2) yum install cpan -> that's ok

3) yum install cpanminus
--> Processing Dependency: perl:)MODULE_COMPAT_5.10.1) for package: perl-Module-Signature-0.79-1.el6.noarch
---> Package perl-Net-LibIDN.x86_64 0:0.12-15.el7 will be installed
---> Package perl-Net-SSLeay.x86_64 0:1.55-3.el7 will be installed
--> Finished Dependency Resolution
Error: Package: perl-Module-Signature-0.79-1.el6.noarch (epel)
Requires: perl:)MODULE_COMPAT_5.10.1)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

3) cpan JSON
-> CPAN.pm requires configuration, but most of it can be done automatically.
If you answer 'no' below, you will enter an interactive dialog for each
configuration option instead.
Would you like to configure as much as possible automatically? [yes] yes
<install_help>
Warning: You do not have write permission for Perl library directories.
To install modules, you need to configure a local Perl library directory or
escalate your privileges. CPAN can help you by bootstrapping the local::lib
module or by configuring itself to use 'sudo' (if available). You may also
resolve this problem manually if you need to customize your setup.
What approach do you want? (Choose 'local::lib', 'sudo' or 'manual')
[local::lib]

thanks for your help, now I'll try what your suggested and will keep you updated
 
Back
Top