Comment # 2 on bug 1201988 from Andrei Borzenkov

(In reply to Michael Andres from comment #1)
> 
> You can try `zypper se -v --requires-pkg -x libicu69` for more details.
> 

Indeed.

> `--requires-pkg libicu69` looks for packages which require something
> libicu69 provides.
> This does not necessarily mean, that libicu69 is the only provider for this.

Yes, I checked it. Anyway

v | chromium                | package | 102.0.5005.115-bp154.2.8.1 | x86_64 |
Update repository of openSUSE Backports
    requires: libicui18n.so.69()(64bit)
    requires: libicuuc.so.69()(64bit)
v | chromium                | package | 101.0.4951.64-bp154.1.2    | x86_64 |
Main Repository
    requires: libicui18n.so.69()(64bit)
    requires: libicuuc.so.69()(64bit)
v | chromium                | package | 102.0.5005.61-bp154.2.5.3  | x86_64 |
Update repository of openSUSE Backports
    requires: libicui18n.so.69()(64bit)
    requires: libicuuc.so.69()(64bit)
bor@10:~> zypper se -isx chromium
Loading repository data...
Reading installed packages...

S  | Name     | Type    | Version                     | Arch   | Repository
---+----------+---------+-----------------------------+--------+----------------------------------------
i+ | chromium | package | 103.0.5060.114-bp154.2.14.1 | x86_64 | Update
repository of openSUSE Backports
bor@10:~> 

So this is mostly presentation issue. While some available versions of chromium
do require this package, the *installed* version of chromium does not. While
output of "zypper se --requires-pkg" makes impression that this requirement is
in installed version.

Unfortunately zypper offers no way show properties of previous versions.
"zypper info" only shows information about the latest available version.

bor@10:~> zypper info chromium=102.0.5005.61-bp154.2.5.3
Loading repository data...
Reading installed packages...


package 'chromium=102.0.5005.61-bp154.2.5.3' not found.
bor@10:~> 

Which makes it basically impossible to troubleshoot such issues.

Anyway thank you for the hint. So the zypper output is not exactly wrong even
if  it is confusing. Improving it would still be helpful (and supporting exact
version in "zypper info" is something I miss for a long time).