Broken (glibc) dependencies in f19 update-repository metadata

[Dennis Gilmore]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, 06 Jul 2013 13:31:48 +0300
Panu Matilainen <pmatilai at laiskiainen.org> wrote:

> 
> Something is broken wrt f19 updates and updates-testing repo
> metadata, note the required glibc version between the rpm version in
> main repo vs updates-testing:
> 
> [root at mursu ~]# repoquery --releasever=19
> --enablerepo=updates-testing --requires
> rpm-build-4.11.0.1-2.fc19.x86_64|grep ^libc.so
> libc.so.6(GLIBC_2.17)(64bit) [root at mursu ~]# repoquery
> --releasever=19 --enablerepo=updates-testing --requires
> rpm-build-4.11.1-1.fc19.x86_64|grep ^libc.so
> libc.so.6(GLIBC_2.8)(64bit) [root at mursu ~]#
> 
> rpm-build-4.11.1-1.fc19 from updates-testing does require much newer 
> glibc than 2.8 though, just like 4.11.0.1 does:
> 
> [root at mursu packages]# rpm -qp --requires 
> rpm-build-4.11.1-1.fc19.x86_64.rpm |grep ^libc.so
> libc.so.6()(64bit)
> libc.so.6(GLIBC_2.14)(64bit)
> libc.so.6(GLIBC_2.17)(64bit)
> libc.so.6(GLIBC_2.2.5)(64bit)
> libc.so.6(GLIBC_2.3)(64bit)
> libc.so.6(GLIBC_2.3.4)(64bit)
> libc.so.6(GLIBC_2.4)(64bit)
> libc.so.6(GLIBC_2.8)(64bit)
> [root at mursu packages]#
> 
> This isn't specific to that rpm package either, NONE of the packages
> in current updates or updates-testing require glibc version > 2.9,
> which really cannot be true:
> 
> [root at mursu packages]# repoquery --releasever=19 --disablerepo="*" 
> --enablerepo=updates --requires -a|grep ^libc.so|sort -u
> libc.so.6(GLIBC_2.1.3)
> libc.so.6(GLIBC_2.2)
> libc.so.6(GLIBC_2.2.5)(64bit)
> libc.so.6(GLIBC_2.3)
> libc.so.6(GLIBC_2.3.2)
> libc.so.6(GLIBC_2.3.2)(64bit)
> libc.so.6(GLIBC_2.3.4)
> libc.so.6(GLIBC_2.3.4)(64bit)
> libc.so.6(GLIBC_2.3)(64bit)
> libc.so.6(GLIBC_2.4)
> libc.so.6(GLIBC_2.4)(64bit)
> libc.so.6(GLIBC_2.5)
> libc.so.6(GLIBC_2.5)(64bit)
> libc.so.6(GLIBC_2.6)(64bit)
> libc.so.6(GLIBC_2.7)
> libc.so.6(GLIBC_2.7)(64bit)
> libc.so.6(GLIBC_2.8)
> libc.so.6(GLIBC_2.8)(64bit)
> libc.so.6(GLIBC_2.9)
> libc.so.6(GLIBC_2.9)(64bit)
> [root at mursu packages]# repoquery --releasever=19 --disablerepo="*" 
> --enablerepo=updates-testing --requires -a|grep ^libc.so|sort -u
> libc.so.6(GLIBC_2.0)
> libc.so.6(GLIBC_2.1.3)
> libc.so.6(GLIBC_2.2)
> libc.so.6(GLIBC_2.2.5)(64bit)
> libc.so.6(GLIBC_2.3)
> libc.so.6(GLIBC_2.3.2)
> libc.so.6(GLIBC_2.3.2)(64bit)
> libc.so.6(GLIBC_2.3.4)
> libc.so.6(GLIBC_2.3.4)(64bit)
> libc.so.6(GLIBC_2.3)(64bit)
> libc.so.6(GLIBC_2.4)
> libc.so.6(GLIBC_2.4)(64bit)
> libc.so.6(GLIBC_2.7)
> libc.so.6(GLIBC_2.7)(64bit)
> libc.so.6(GLIBC_2.8)
> libc.so.6(GLIBC_2.8)(64bit)
> libc.so.6(GLIBC_2.9)
> libc.so.6(GLIBC_2.9)(64bit)
> [root at mursu packages]#
> 
> The main f19 repodata seems ok though, and I wasn't able to reproduce 
> this locally so perhaps it has something to do with the way the f19 
> update-repositories metadata is created/updated rather than
> createrepo bug wrt glibc collapsing, but dunno. Also f18 update-repos
> dont seem to be affected, the libc.so requires there seem sane to me.

repoquery --enablerepo updates-testing --requires
rpm-build-4.11.0.1-2.fc19.x86_64|grep libc.so
libc.so.6(GLIBC_2.17)(64bit)

is what i get.

Dennis

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEYEARECAAYFAlHXzWkACgkQkSxm47BaWfdg/wCbBZ2ticaFgGQafq9GL29uVu7+
8fEAn3uvVWYLzTgnq+hzpmf2+xs18mrD
=yqhO
-----END PGP SIGNATURE-----