Bug 1427318

Summary:	gmime 2.6.19 g_mime_object_write_to_stream() adds extra space in References: header
Product:	[Fedora] Fedora EPEL	Reporter:	tomi ollila <tomi.ollila>
Component:	gmime	Assignee:	Pete Walter <walter.pete>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	epel7	CC:	walter.pete
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-30 11:18:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description tomi ollila 2017-02-27 21:55:59 UTC

Description of problem:

From https://bugzilla.gnome.org/show_bug.cgi?id=711305

g_mime_object_write_to_stream() adds an extra space in the References: header after the colon.


Version-Release number of selected component (if applicable):

2.4.19


How reproducible:

Always when GmimeMessage object contains References: header


Steps to Reproduce:
1. yum -v -y install epel-release
2. yum -v -y install make gcc gcc-c++ redhat-rpm-config git xapian-core-devel gmime-devel libtalloc-devel zlib-devel
3. git clone git://notmuchmail.org/git/notmuch
4. cd notmuch && make test


Actual results:

37 tests fail since there is 2 spaces (one extra) after 'References:'.


Expected results:

Such diffs don't appear on output (some other, unrelated tests probably still fails)


Additional info:

In the repository git://git.gnome.org/gmime

the commit cc96162a47bd88ba76cece5043a93b438e48c2c7 

fixes this problem (first commit after 2.6.19 version tag).

Comment 1 tomi ollila 2018-05-30 11:01:12 UTC

Looking EPEL now (2018-05-30) the gmime package is updated to 2.6.23.

So to me it looks like this issue is resolved.

Just now I don't have a chance to test it, will do later...

Comment 2 tomi ollila 2018-05-30 11:18:47 UTC

Ok, tested, this particular case is not an issue anymore.