Tumbleweed nightly build has wrong/mismatching package versions



  • Since some time the nightly builds of Kopano core for openSuse Tumbleweed cannot be installed due to missing dependencies or wrong / mismatched package versions.

    When trying to do a distribution upgrade (I’ve currently installed version 9.0.2) zypper complains that some packages with version 10.0.4 are missing a corresponding required kopano-common package of the same version

    Problem: nothing provides kopano-common = 10.0.4.0.b38037084 needed by kopano-search-10.0.4.0.b38037084-37.1.x86_64
    Problem: nothing provides kopano-common = 10.0.4.0.b38037084 needed by kopano-migration-pst-10.0.4.0.b38037084-37.1.x86_64
    Problem: nothing provides kopano-common = 10.0.4.0.b38037084 needed by kopano-backup-10.0.4.0.b38037084-37.1.x86_64
    Problem: nothing provides kopano-common = 10.0.4.0.b38037084 needed by kopano-backup-10.0.4.0.b38037084-37.1.x86_64
    
    

    whereas the remaining packages in the nightly build zip-archive (e.g. kopano-server) including kopano-common are delivered with a version reading 10.0.5.

     # ls *common* *server* *search*
    kopano-common-10.0.5.5.8827066e2-109.1.x86_64.rpm            kopano-server-packages-10.0.5.5.8827066e2-109.1.x86_64.rpm
    kopano-search-10.0.4.0.b38037084-37.1.x86_64.rpm             libkcserver0-10.0.5.5.8827066e2-109.1.x86_64.rpm
    kopano-server-10.0.5.5.8827066e2-109.1.x86_64.rpm            libkcserver0-debuginfo-10.0.5.5.8827066e2-109.1.x86_64.rpm
    

    I have to use the nightly build instead of the Tumbleweed distro release since I need the OIDC functionality of Kopano core which is considered experimental and not compiled into the distro release.

    Can I safely ignore the mismatched versions forcing an upgrade/install or has the nightly build to be fixed somehow?



  • An update: I’ve ignored the missing dependencies and upgraded my Tumebleweed release including the Kopano core release to version 10.0.5 first on a sandbox copy first and then on the production site and didn’t find an issue up to now.


Log in to reply