[opensuse-factory] TW 64 bit glibc-32bit lags behind glibc
glibc is 2.22-8.2 while glibc-32bit is 2.22-7.1. I thought they are built from the same source - how can versions be different? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, 2016-02-27 at 15:56 +0300, Andrei Borzenkov wrote:
glibc is 2.22-8.2 while glibc-32bit is 2.22-7.1. I thought they are built from the same source - how can versions be different?
They are built from the same source.. just you updated glibc from the update repo but not glibc-32bit it seems: S | Name | Type | Version | Arch | Repository --+------------------------------+------------+----------+--------+-- ------------------------- i | glibc | package | 2.22-8.2 | x86_64 | openSUSE-Tumbleweed-Update v | glibc | package | 2.22-7.1 | x86_64 | openSUSE-Tumbleweed-Oss i | glibc-32bit | package | 2.22-8.1 | x86_64 | openSUSE-Tumbleweed-Update v | glibc-32bit | package | 2.22-7.1 | x86_64 | openSUSE-Tumbleweed-Oss Cheers, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 27.02.2016 um 15:17 schrieb Dominique Leuenberger / DimStar:
On Sat, 2016-02-27 at 15:56 +0300, Andrei Borzenkov wrote:
glibc is 2.22-8.2 while glibc-32bit is 2.22-7.1. I thought they are built from the same source - how can versions be different?
They are built from the same source.. just you updated glibc from the update repo but not glibc-32bit it seems:
S | Name | Type | Version | Arch | Repository --+------------------------------+------------+----------+--------+-- ------------------------- i | glibc | package | 2.22-8.2 | x86_64 | openSUSE-Tumbleweed-Update v | glibc | package | 2.22-7.1 | x86_64 | openSUSE-Tumbleweed-Oss i | glibc-32bit | package | 2.22-8.1 | x86_64 | openSUSE-Tumbleweed-Update v | glibc-32bit | package | 2.22-7.1 | x86_64 | openSUSE-Tumbleweed-Oss
The 32bit packages in -Update have a different Vendor Tag, so they are not picked up automatically. susi:~ # zypper -v up --no-recommends -r repo-update Verbosity: 1 Initializing Target Checking whether to refresh metadata for repo-update Loading repository data... Reading installed packages... Force resolution: No The following 3 package updates will NOT be installed: glibc-32bit 2.22-8.1 glibc-devel-32bit 2.22-8.1 glibc-locale-32bit 2.22-8.1 Nothing to do. susi:~ # zypper -v up -r repo-update glibc-32bit Verbosity: 1 Non-option program arguments: 'glibc-32bit' Initializing Target Checking whether to refresh metadata for repo-update Loading repository data... Reading installed packages... Force resolution: No There is an update candidate for 'glibc-32bit', but it is from a different vendor. Use 'zypper install glibc-32bit-2.22-8.1.x86_64' to install this candidate. Resolving package dependencies... Force resolution: No Nothing to do. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
27.02.2016 17:21, Stefan Seyfried пишет:
Am 27.02.2016 um 15:17 schrieb Dominique Leuenberger / DimStar:
On Sat, 2016-02-27 at 15:56 +0300, Andrei Borzenkov wrote:
glibc is 2.22-8.2 while glibc-32bit is 2.22-7.1. I thought they are built from the same source - how can versions be different?
They are built from the same source.. just you updated glibc from the update repo but not glibc-32bit it seems:
S | Name | Type | Version | Arch | Repository --+------------------------------+------------+----------+--------+-- ------------------------- i | glibc | package | 2.22-8.2 | x86_64 | openSUSE-Tumbleweed-Update v | glibc | package | 2.22-7.1 | x86_64 | openSUSE-Tumbleweed-Oss i | glibc-32bit | package | 2.22-8.1 | x86_64 | openSUSE-Tumbleweed-Update v | glibc-32bit | package | 2.22-7.1 | x86_64 | openSUSE-Tumbleweed-Oss
The 32bit packages in -Update have a different Vendor Tag, so they are not picked up automatically.
How is it possible for two packages built from the same source (and presumably at the same time) to have different Vendor? We had this problem (different Vendor in update repo) but I thought it was fixed? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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
Andrei Borzenkov wrote:
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.
Done now. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Andrei Borzenkov -
Dominique Leuenberger / DimStar -
Ludwig Nussel -
Stefan Seyfried