Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 490316 - Port dbmail to gmime 2.4 API
Summary: Port dbmail to gmime 2.4 API
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: dbmail
Version: 15
Hardware: All
OS: Linux
high
medium
Target Milestone: ---
Assignee: Bernard Johnson
QA Contact: Fedora Extras Quality Assurance
URL: http://dbmail.org/
Whiteboard:
Depends On: 490397
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-15 08:24 UTC by Alex Lancaster
Modified: 2011-06-02 18:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-02 18:21:47 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Alex Lancaster 2009-03-15 08:24:23 UTC 
dbmail has not been rebuilt yet in F-11 and causes broken deps in rawhide:

Broken deps for i386
----------------------------------------------------------
	dbmail-2.2.11-2.fc10.i386 requires libgmime-2.0.so.2
	dbmail-auth-ldap-2.2.11-2.fc10.i386 requires libgmime-2.0.so.2
	dbmail-mysql-2.2.11-2.fc10.i386 requires libssl.so.7
	dbmail-mysql-2.2.11-2.fc10.i386 requires libcrypto.so.7
	dbmail-mysql-2.2.11-2.fc10.i386 requires libmysqlclient.so.15
	dbmail-mysql-2.2.11-2.fc10.i386 requires libgmime-2.0.so.2
	dbmail-mysql-2.2.11-2.fc10.i386 requires libmysqlclient.so.15(libmysqlclient_15)
	dbmail-pgsql-2.2.11-2.fc10.i386 requires libgmime-2.0.so.2

I attempted to force compilation against the new gmime-devel 2.4 package by patching the configure script to look for the 2.4 .pc file, but it's clear that this doesn't work, the API has changed:

 gcc -DHAVE_CONFIG_H -I. -I. -I. -I. -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/gmime-2.4 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -W -Wall -Wpointer-arith -Wstrict-prototypes -MT libdbmail_la-config.lo -MD -MP -MF .deps/libdbmail_la-config.Tpo -c config.c  -fPIC -DPIC -o .libs/libdbmail_la-config.o
dbmail-message.c: In function 'get_crlf_encoded_opt':
dbmail-message.c:111: warning: implicit declaration of function 'g_mime_stream_filter_new_with_stream'
dbmail-message.c:111: warning: assignment makes pointer from integer without a cast
dbmail-message.c:113: error: 'GMIME_FILTER_CRLF_ENCODE' undeclared (first use in this function)

full log here:

http://koji.fedoraproject.org/koji/taskinfo?taskID=1241979
http://koji.fedoraproject.org/koji/getfile?taskID=1241979&name=build.log

In any case, we somehow need to get this to build ASAP so it can be tagged into f11-beta if at all possible.  I did see the maintainer report this upstream:

http://article.gmane.org/gmane.mail.imap.dbmail.devel/10950/match=gmime+2.4

but it looks like it still fails in the 2.3.5 development version.  Have you had any further luck in getting upstream to fix this?
Comment 1 Bernard Johnson 2009-03-15 23:05:46 UTC 
The initial indication from the dbmail development mailing list was the dbmail 2.3.x would build against gmime 2.4.  This appears to not be the case.  My query on the mailing list has gone unanswered when I pointed this out.

As I see it, there are three options here:

1) Block dbmail from F-11.

2) Introduce a compat-gmime-2.2 package.

3) Port to gmime 2.4.

#3 is not an option for me at this time.  I suspect #2 would be the best at this point.  What do you think?
Comment 2 Alex Lancaster 2009-03-16 01:15:13 UTC 
(In reply to comment #1)
> The initial indication from the dbmail development mailing list was the dbmail
> 2.3.x would build against gmime 2.4.  This appears to not be the case.  My
> query on the mailing list has gone unanswered when I pointed this out.
> 
> As I see it, there are three options here:
> 
> 1) Block dbmail from F-11.
> 
> 2) Introduce a compat-gmime-2.2 package.
> 
> 3) Port to gmime 2.4.
> 
> #3 is not an option for me at this time.  I suspect #2 would be the best at
> this point.  What do you think?  

#2 might be best as there are other apps yet to be ported to gmime 2.4.  Unfortunately the gmime maintainer didn't do a full inventory of what needed to be fixed.  I think having at least one release (F-11) to allow apps to be ported before dropping the compat- package would be polite to application maintainers.
Comment 3 Bernard Johnson 2009-03-16 03:58:15 UTC 
Ok, I submitted a review for compat-gmime-2.2 (bz #490397).  It's essentially the same as the last released gmime-2.2 series minus the mono parts and files versioned to eliminate conflicts.

I did a test build of dbmail against the compat-devel-2.2 package and, as expected, it built fine.
Comment 4 Bernard Johnson 2009-03-20 03:28:51 UTC 
- gmime22 is built in rawhide
- changes to dbmail have been committed to cvs and tagged


Waiting for gmime22 to hit the buildsystems - if someone sees this before me, feel free to kick off the build.
Comment 5 Alex Lancaster 2009-03-20 07:02:01 UTC 
Rebuilt:

http://koji.fedoraproject.org/koji/buildinfo?buildID=94833

request for rel-eng tagging for f11-beta here:

http://fedorahosted.org/rel-eng/ticket/1407

Keep this bug open and retitling to be about porting dbmail to gmime 2.4.x
Comment 6 Bug Zapper 2009-06-09 12:15:13 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 7 Bug Zapper 2010-03-15 12:28:50 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 8 Bug Zapper 2011-06-02 18:12:26 UTC 
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 9 Alex Lancaster 2011-06-02 18:21:47 UTC 
According to recent build:

http://koji.fedoraproject.org/koji/rpminfo?rpmID=2521338

it looks like this has been ported to use gmime 2.6, the following dep is shown:

libgmime-2.6.so.0()(64bit)

so closing bug as FIXED.
Note You need to log in before you can comment on or make changes to this bug.