Bug 22215

Summary:	Changelog in glibc messed up
Product:	Mageia	Reporter:	Hans Micheelsen <micheelsen>
Component:	RPM Packages	Assignee:	Base system maintainers <basesystem>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, micheelsen, tmb
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
URL:	http://www.gnu.org/software/libc/
Whiteboard:
Source RPM:	glibc-2.22-26.mga7.src.rpm	CVE:
Status comment:
Attachments:	output from rpm -q --changelog glibc

Description Hans Micheelsen 2017-12-17 20:13:21 CET

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

Hans Micheelsen 2017-12-17 20:14:16 CET

CC: (none) => micheelsen

Marja Van Waes 2017-12-18 07:52:25 CET

CC: (none) => marja11
Assignee: bugsquad => basesystem

Comment 1 Hans Micheelsen 2017-12-30 21:29:33 CET

Created attachment 9868 [details]
output from  rpm -q --changelog glibc

Comment 2 Marja Van Waes 2017-12-30 22:19:05 CET

(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

Comment 3 Marja Van Waes 2017-12-30 22:25:38 CET

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 :-)

Comment 4 Thomas Backlund 2017-12-30 22:26:32 CET

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) => WONTFIX
Status: NEW => RESOLVED