On 16.09.2021 18:36, Alexander Graul wrote:
Hi Daniel,
I think this is related to / has the same cause as https://github.com/openSUSE/software-o-o/issues/996
No, it looks different.
I only looked at it briefly, but it seems that software.o.o is taking the version from the openSUSE:Leap:15.3/glibc.XZY (patchinfo) package and not from openSUSE:Leap:15.3/glibc.
Thanks for reporting this, I'll add it to the existing issue.
Best, Alex
Daniel Noga <noga.dany@gmail.com> writes:
I tried to search glibc via https://software.opensuse.org/package/glibc , but it shows wrong version for Leap 15.3. It shows 2.26 instead of 2.31 Is it known bug?
It returns 2.26 because this is the only version that matches repositories list for Leap 15.3: $ osc bse glibc | grep 15.3 | grep -v home $ osc bse glibc | grep SLE | grep -v home SUSE:SLE-15:Update glibc.18276 SUSE:/SLE-15:/Update/pool/i586/glibc-2.26-13.56.1.i586.rpm SUSE:SLE-15:Update glibc.18276 SUSE:/SLE-15:/Update/pool/s390x/glibc-2.26-13.56.1.s390x.rpm SUSE:SLE-15:Update glibc.18276 SUSE:/SLE-15:/Update/pool/src/glibc-2.26-13.56.1.src.rpm SUSE:SLE-15:Update glibc.18276:i686 SUSE:/SLE-15:/Update/pool/i686/glibc-2.26-13.56.1.i686.rpm SUSE:SLE-15:Update glibc.18276:i686 SUSE:/SLE-15:/Update/pool/nosrc/glibc-2.26-13.56.1.nosrc.rpm SUSE:SLE-15:Update patchinfo.18276 SUSE:/SLE-15:/Update/pool/aarch64/glibc-2.26-13.56.1.aarch64.rpm SUSE:SLE-15:Update patchinfo.18276 SUSE:/SLE-15:/Update/pool/ppc64le/glibc-2.26-13.56.1.ppc64le.rpm SUSE:SLE-15:Update patchinfo.18276 SUSE:/SLE-15:/Update/pool/x86_64/glibc-2.26-13.56.1.x86_64.rpm $ So the only binary glibc version that is found is from SLES 15 GA update while $ osc se glibc | grep SLE | grep -v home SUSE:SLE-12-SP1:GA glibc SUSE:SLE-12-SP1:Update glibc SUSE:SLE-12-SP2:GA glibc SUSE:SLE-12-SP2:Update glibc SUSE:SLE-12-SP4:GA glibc SUSE:SLE-12-SP4:Update glibc SUSE:SLE-12:GA glibc SUSE:SLE-12:Update glibc SUSE:SLE-15-SP3:GA glibc ^^^^^^^^^^^^^^^^^^ This is missing SUSE:SLE-15:GA glibc SUSE:SLE-15:Update glibc $ I do not think it is s.o.o bug, it looks like OBS issue as demonstrated by using osc to get the same wrong result. P.S. did not we just recently had yet another heated discussion invlving top posting? This is good example why top posting is bad - it makes commenting in context near to impossible.