Bug 1034994 - gloox::MessageSession::send(message) call is ambiguous
Summary: gloox::MessageSession::send(message) call is ambiguous
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gloox
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pavel Alexeev
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-26 20:10 UTC by Jan Včelák
Modified: 2014-01-21 05:47 UTC (History)
2 users (show)

Fixed In Version: gloox-1.0.9-1.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-21 00:39:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jan Včelák 2013-11-26 20:10:18 UTC
Description of problem:

Current version of Gloox in Fedora contains a bug which causes a compilation error when gloox::MessageSession::send() is called with one parameter. This is a regression, which was already fixed upstream.

Version-Release number of selected component (if applicable):
gloox-1.0.3-1.fc20.x86_64

How reproducible:
always


Steps to Reproduce:
1. have a look into /usr/include/gloox/messagesession.h
2.
3.

Actual results:

Two send() functions with same signature when called with one argument.

virtual void send( const std::string& message );
virtual void send( const std::string& message, const std::string& subject = EmptyString, const StanzaExtensionList& sel = StanzaExtensionList() );


Expected results:


Additional info:

Comment 1 Pavel Alexeev 2013-12-01 15:08:15 UTC
Thanks for the report. Ok, I'll try update it on 1.0.9 version.

Comment 2 Fedora Update System 2013-12-02 07:14:06 UTC
gloox-1.0.9-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/gloox-1.0.9-1.fc20

Comment 3 Pavel Alexeev 2013-12-04 07:57:52 UTC
Update unpushed from F20 because it break dependency for licq.
Meantime it in rawhide.

Comment 4 Christopher Meng 2013-12-04 09:52:35 UTC
licq maintainer here.

Please push it and I will leave karma depends on the build test results.

Comment 5 Christopher Meng 2013-12-04 09:58:56 UTC
Well, forgot one sentence:

After F20 released.

Comment 6 Jan Včelák 2013-12-04 10:00:50 UTC
Pavel, please, can you push the update and also create a build override valid for a week or so? I maintain another package (fatrat), which depends on gloox and I will have to rebuild it.

Comment 7 Pavel Alexeev 2013-12-15 09:11:55 UTC
Hi.
Sorry for the delay with answer - i have very much work on my main job place.

I ready push gloox update in Fedora 20 if you wish. Do you test licq and fatrat with new version of gloox? If you wish, I could build and push them 3 at one update (I have provenpackager rights). Is there other dependencies need to be rebuild?

Comment 8 Christopher Meng 2013-12-20 04:20:05 UTC
They work fine.

Comment 9 Pavel Alexeev 2014-01-06 19:26:57 UTC
Who? And what are you willing? Should I just push gloox update in Fedora 20 and you continue than? Or with other dependencies?

Comment 10 Christopher Meng 2014-01-07 03:50:09 UTC
gloox has 1.0.9 version and you should build it for rawhide first, congrats you've finished.

So now we want 1.0.9 in f20(not f19), because some significant changes will help improve other software's stability. You can submit as override in testing and we can build against it also.

Only these are affected:

0ad
fatrat
licq
spectrum

Comment 11 Pavel Alexeev 2014-01-07 18:17:17 UTC
Build override with gloox-1.0.9-1.fc20 submitted until 01/22/2014.

Comment 12 Fedora Update System 2014-01-10 04:16:51 UTC
licq-1.8.1-2.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/licq-1.8.1-2.fc20

Comment 13 Fedora Update System 2014-01-20 03:05:33 UTC
gloox-1.0.9-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 14 Fedora Update System 2014-01-21 05:47:36 UTC
licq-1.8.1-2.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


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