Bug 62635 - accountsservice git build error
Summary: accountsservice git build error
Status: RESOLVED MOVED
Alias: None
Product: accountsservice
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Matthias Clasen
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-22 13:02 UTC by Asif Ali Rizvan
Modified: 2018-08-07 09:30 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
jhbuildrc (1.99 KB, text/plain)
2013-03-22 13:02 UTC, Asif Ali Rizvan
Details
full jhbuild build accountsserivce output (14.10 KB, text/plain)
2013-03-22 13:02 UTC, Asif Ali Rizvan
Details

Description Asif Ali Rizvan 2013-03-22 13:02:36 UTC
Created attachment 76903 [details]
jhbuildrc

AccountsService-1.0.gir:1136.11-1136.10: error: expected end element of `parameter'
AccountsService-1.0.gir:710.7-710.27: warning: Signal `Act.UserManager.user_added' conflicts with method of the same name
AccountsService-1.0.gir:723.7-723.31: warning: Signal `Act.UserManager.user_changed' conflicts with method of the same name
AccountsService-1.0.gir:736.7-736.57: warning: Signal `Act.UserManager.user_is_logged_in_changed' conflicts with method of the same name
AccountsService-1.0.gir:749.7-749.31: warning: Signal `Act.UserManager.user_removed' conflicts with method of the same name
make[5]: *** [accountsservice.vapi] Error 1
Comment 1 Asif Ali Rizvan 2013-03-22 13:02:58 UTC
Created attachment 76904 [details]
full jhbuild build accountsserivce output
Comment 2 GitLab Migration User 2018-08-07 09:30:36 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/accountsservice/accountsservice/issues/12.


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.