Description of problem: When I inspect the changelog of glibc it seems that the release dates are missing. The changelogs from all the previous versions have been merged together in one very long text Version-Release number of selected component (if applicable): glibc-devel-2.22-26.mga7 glibc-2.22-26.mga7 Steps to Reproduce: rpm -q --changelog glibc | less
CC: (none) => micheelsen
CC: (none) => marja11Assignee: bugsquad => basesystem
Created attachment 9868 [details] output from rpm -q --changelog glibc
(In reply to Hans Micheelsen from comment #1) > Created attachment 9868 [details] > output from rpm -q --changelog glibc Yeah, that's the same weird changelog as in the last changelog mail for glibc in cauldron, from December 16 https://ml.mageia.org/l/arc/changelog/2017-12/msg00475.html But when I do "mgarepo log glibc", the changelog looks ok, apart from the fact that the last enty is from December 8, eight days earlier. So revision 1182752 is missing there. CC'ing tmb.
CC: (none) => tmb
ah, I think mgarepo shows the log for glibc as it got pushed to cauldron/core/backports_testing I should check the cauldron testing repos more often :-)
It comes from a bug in the BS that does not properly do markreleases in updates tree and this cauldron update is from a branch copied from updates to get the 2.22 security updates done in cauldron as I already have 2.25+ in svn while still fixing updgrade issues from 2.22 to 2.25 in cauldron, So while it looks uggly, its not something to waste time on as I have way more important work to fix
Resolution: (none) => WONTFIXStatus: NEW => RESOLVED