Citeren Michael Ströder <michael@stroeder.com>:
so this is already fixed. What is the exect problem with rouncubemail ?
Please re-read boo#1180132.
And Arjen has raised general objections against these Provides.
Indeed: packages almost never depend on a random webserver, in almost all cases there are webserver specific configuration files that need to be written (roundcubemail is no exception here). So although it may be tempting to require a 'generic' webserver and let the user choose which, unless you're only serving static HTML, this almost never is what you want. Or you need to prepare your package for this by putting webserver or PHP specific files in subpackages that depend on specific PHP versions or webservers. I also noticed a problem in the way we build roundcubemail now and I suspect this will be a problem with other packages as well. In order to start building extensions, php8 is now also in Factory (and Tumbleweed). This is a problem for packages that use the PHP version agnostic Requires/Recommends/Suggests (for instance, php-session). The intended use for these, was for cases where we want to determine during package build which PHP version is used, so we can upgrade to a newer PHP version by changing the Project Config which version is used. This allows to make this change in a single location, rather than in lots of individual packages. This now seems to backfire, as there are packages that use these also for Requires/Recommends/Suggests. When there is no choice, this will install the same version as used in the build. But if there are (like now) two versions available and the package *really* requires a specific one (because it expects files to be in certain locations), this can fail. So although the BuildRequires can (and should) still be using PHP version agnostic php-<whatever>, the Requires/Recommends/Suggests must depend on the PHP version used during the build. See https://build.opensuse.org/request/show/866107.