29.02.2016 11:23, Ludwig Nussel пишет:
Andrei Borzenkov wrote:
[...] How is it possible for two packages built from the same source (and
27.02.2016 17:21, Stefan Seyfried пишет: presumably at the same time) to have different Vendor?
glibc is special. The -32bit package actually comes from glibc.i686 which is a source link to glibc.
We had this problem (different Vendor in update repo) but I thought it was fixed?
It is fixed but as usual glibc.i686 fell through the cracks when triggering the rebuild of glibc that fixed the vendor string.
Anyways, the glibc with the security fix was released in snapshot 20160222 so the glibc package in the update repo is no longer required.
While it may well contain security fix, the current situation is TW OSS contains: glibc-2.22-7.1, glibc-32bit-2.22-7.1 dated 22 Feb TW OSS Update contains: glibc-2.22-8.2, glibc-32bit-2.22-8.1 dated 18 (19) Feb. Additionally glibc-32bit here has wrong Vendor. I assume TW OSS packages are newer. In this case could someone finally remove packages from update repo to avoid confusion. Currently zypper dup will *not* install packages from main repo and insists on vendor change for glibc-32bit. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org