Menu

Problems with dependencies while migrating an extension from 2.7 to 3.2

3 days ago
2 days ago
  • Kevin Joubert

    Kevin Joubert - 3 days ago

    Greetings, I am trying to migrate a customer from v2.7 to v3.2 and I keep getting the following error message in the setup wizard.

    The following modules have unmet dependencies:
    ZA01 Country Master, South Africa (Country-Master-ZA01/1.0.0):
    ✅ itop-structure/2.7.1
    ✅ itop-tickets/3.2.1
    ❌ itop-service-mgmt/3.2.1
    ✅ itop-config-mgmt/3.2.1**

        My extension module has the following dependencies set
    
            'label' => 'ZA01 Country Master, South Africa',
            'category' => 'business',
    
                // Setup
                //
                'dependencies' => array(
                'itop-structure/3.2.1',
                'itop-tickets/3.2.1',           
                'itop-service-mgmt/3.2.1',
                'itop-config-mgmt/3.2.1',
    
        ),
        'mandatory' => false,
        'visible' => true,
    

    I can't see any other dependencies listed in these modules and I have tried changing the order of the dependency list to see if that makes a difference.

    What am I doing wrong?

    Thank you,
    Kevin Joubert

     
  • Vincent @ Combodo

    Hi Kevin,
    Most of the iTop modules do not change their version in minor version, so explicitly requiring the version 3.2.1 on all modules is rather weird.
    If you are interested in a particular iTop minor version, so a ".1" use the module "itop-structure" it is always present, regardless of your installation options.
    Apart from the .0 and the .1, it is never be useful to require a particular minor version, because new datamodel and new features are never brought outside of those versions.
    On my iTop 3.2.2, "itop-service-mgmt" module version was raised to 3.2.1, so it should be on yours as well.

     
  • Kevin Joubert

    Kevin Joubert - 2 days ago

    Hi Vincent, thanks for getting back to me. OK so if I'm understanding correctly, the module version number in my dependencies don't have to be exactly the same as the ones in the files as long as the files are later versions. And by making mine match exactly I've limited the files that can be used. I hope that's correct? I'll make the changes and let you know .
    Thanks again for the help.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.