Bug 18655 - TP_ERRORS is now auto-registered breaking the API semantics
Summary: TP_ERRORS is now auto-registered breaking the API semantics
Status: RESOLVED NOTABUG
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-glib (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-21 10:36 UTC by Olivier Crête
Modified: 2008-12-02 01:55 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Olivier Crête 2008-11-21 10:36:49 UTC 
Since TP_ERRORS is now automatically registered, it breaks the API semantics (and stream-engine) which used to have to register it directly.

And causes this warning:
** WARNING **: Metadata for error domain "tp_errors" already registered

I guess either we accept the ABI break, up the tp-glib requirement on stream-engine and live on our lives...

Or you can revert the change...
Comment 1 Simon McVittie 2008-12-02 01:55:40 UTC 
I don't think provoking a warning, but then working correctly, on non-connection-managers that export objects (CMs never needed to register TP_ERRORS, the library did it) is a major problem. The bug was that TP_ERRORS was *not* auto-registered, IMO. So I'd suggest just increasing s-e's dependency on telepathy-glib.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.