#1133 2008-12-10 updates not tagged correctly?
Closed: Fixed None Opened 15 years ago by mtasaka.

For example:

https://www.redhat.com/archives/fedora-package-announce/2008-December/msg00638.html
glibc-2.9-3 is released as F-10 updates, however currently

$ koji latest-pkg dist-f10-build glibc
/usr/lib/python2.6/site-packages/koji/init.py:34: DeprecationWarning: the md5 module is deprecated; use hashlib instead
import md5
Build Tag Built by


glibc-2.9-2 dist-f10 jakub


This should be fixed in the next updates push (later today)

Still seems not good.
Moreover, it seems some 2008-12-11 updates are not correctly tagged,
for example:
https://admin.fedoraproject.org/updates/F10/FEDORA-2008-11078

Luke fixed that this morning.

Replying to [comment:2 mtasaka]:

Still seems not good.
Moreover, it seems some 2008-12-11 updates are not correctly tagged,
for example:
https://admin.fedoraproject.org/updates/F10/FEDORA-2008-11078

This update seems to have landed in the updates mirrors indeed:

{{{

w3m -dump http://download.fedora.redhat.com/pub/fedora/linux/updates/10/x86_64/ | grep -F PackageKit-0.3

[ ] PackageKit-0.3.12-1.fc10.x86_64.rpm 09-Dec-2008 361K
}}}

However none of the 2008-12-10 updates have (except for cups somehow), including glibc with resolver and unsetenv fixes, iproute2, etc.

The previous comment was submitted by me as anonymous unintentionally.

This issue should be resolved with the next push of updates.

I see the packages here. Not some others, though, but I'll address that in the pre-existing Infrastructure ticket. https://fedorahosted.org/fedora-infrastructure/ticket/1011

Login to comment on this ticket.

Metadata