What | Removed | Added |
---|---|---|
CC | adrian.schroeter@suse.com | |
Flags | needinfo?(adrian.schroeter@suse.com) |
I just checked the xfce4-session-lang package as an example in Leap (15.0-15.3) and TW > $ for f in xfce4-session-lang-*; do echo "=== $f"; rpm -qp $f --provides; done > === xfce4-session-lang-4.12.1-lp150.3.7.noarch.rpm > xfce4-session-lang = 4.12.1-lp150.3.7 > xfce4-session-lang-all = 4.12.1 > === xfce4-session-lang-4.12.1-lp151.6.1.noarch.rpm > xfce4-session-lang = 4.12.1-lp151.6.1 > xfce4-session-lang-all = 4.12.1 > === xfce4-session-lang-4.14.2-lp152.1.3.noarch.rpm > xfce4-session-lang = 4.14.2-lp152.1.3 > xfce4-session-lang-all = 4.14.2 > === xfce4-session-lang-4.16.0-lp153.1.20.noarch.rpm > xfce4-session-lang = 4.16.0-lp153.1.20 > xfce4-session-lang-all = 4.16.0 > === xfce4-session-lang-4.16.0-1.7.noarch.rpm > locale(xfce4-session:ar) > ...AND MANY MORE... > locale(xfce4-session:zh_TW) > xfce4-session-lang = 4.16.0-1.7 > xfce4-session-lang-all = 4.16.0 @Adrian: It's claimed that the packages (basically all xfce4-*-lang packages) are built from the same spec. Is there an explanation why all the LEAP packages lack the 'locale(...)' provides, while the TW package has them?