Merge lp:~mardy/reminders-app/new-api into lp:reminders-app
| Status: | Needs review |
|---|---|
| Proposed branch: | lp:~mardy/reminders-app/new-api |
| Merge into: | lp:reminders-app |
| Diff against target: |
408 lines (+97/-89) 8 files modified
CMakeLists.txt (+4/-0) com.ubuntu.reminders_reminders.accounts.in (+8/-0) debian/control (+5/-6) manifest.json.in (+2/-4) src/account-plugin/CMakeLists.txt (+5/-0) src/account-plugin/com.ubuntu.reminders_evernote-account-plugin.accounts.in (+22/-0) src/app/qml/Reminders.qml (+44/-62) src/app/qml/ui/AccountSelectorPage.qml (+7/-17) |
| To merge this branch: | bzr merge lp:~mardy/reminders-app/new-api |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| David Planella | 2015-09-17 | Needs Information on 2016-03-17 | |
| Jenkins Bot | continuous-integration | Needs Fixing on 2016-03-08 | |
| Ubuntu Phone Apps Jenkins Bot | continuous-integration | Needs Fixing on 2015-09-24 | |
|
Review via email:
|
|||
Commit Message
Use the new Online Accounts API and hook format
Description of the Change
Use the new Online Accounts API and hook format
Note that I've also added ubuntu-
Please let me know if the added dependency is acceptable; if it isn't, we might remove it along with the qml-module-
| Alberto Mardegan (mardy) wrote : | # |
Thanks Michael for creating the MP. I didn't create it myself because this is still in a very early stage.
However, I'm happy to have some feedback on it, especially about the future of the .deb version. Do you intend to keep it?
The reason why I'm asking this, is because with the new Online Accounts hook, the .application, .service and .provider files are no longer necessary: they are automatically generated by the hook processor. However, if you want reminders-app to continue to live as a .deb as well, then we cannot remove these files (unless, maybe, we run the hook processor as part of the .deb build process -- sounds weird but it should work).
FAILED: Continuous integration, rev:497
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https:/
http://
Executed test runs:
FAILURE: http://
Click here to trigger a rebuild:
http://
FAILED: Continuous integration, rev:498
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https:/
http://
Executed test runs:
FAILURE: http://
Click here to trigger a rebuild:
http://
FAILED: Continuous integration, rev:499
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https:/
http://
Executed test runs:
FAILURE: http://
Click here to trigger a rebuild:
http://
FAILED: Continuous integration, rev:500
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https:/
http://
Executed test runs:
FAILURE: http://
Click here to trigger a rebuild:
http://
FAILED: Continuous integration, rev:500
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https:/
https:/
Executed test runs:
None: https:/
Click here to trigger a rebuild:
https:/
| Alan Pope πΊπ§π± π¦ (popey) wrote : | # |
Mardy: Is this still desired/required?
| Alberto Mardegan (mardy) wrote : | # |
> Mardy: Is this still desired/required?
Yes, but it cannot be merged yet, there are yet changes to be made on apparmor for this new API to work (bug #1512667).
Note that I didn't propose this MP myself. This MP should either be deleted or set to WIP.
FAILED: Continuous integration, rev:508
https:/
Executed test runs:
None: https:/
Click here to trigger a rebuild:
https:/
| David Planella (dpm) wrote : | # |
Bug #1512667 seems to have been fixed right now. Are we in a position to land this branch?
| Alberto Mardegan (mardy) wrote : | # |
Please read carefully this MP's description, as there's a problem with the deb version (I've tested the click and it seems to work fine).
Let me know how to proceed.
Unmerged revisions
- 508. By Alberto Mardegan on 2016-03-08
-
Update debian dependencies
- 507. By Alberto Mardegan on 2016-03-08
-
restore application file
- 506. By Alberto Mardegan on 2016-03-07
-
re-revert
- 505. By Alberto Mardegan on 2016-03-07
-
fix hook
- 504. By Alberto Mardegan on 2016-03-07
-
revert
- 503. By Alberto Mardegan on 2016-03-07
-
Fix service names
- 502. By Alberto Mardegan on 2016-03-07
-
Update plugin hook
- 501. By Alberto Mardegan on 2016-03-07
-
from trunk
- 500. By Alberto Mardegan on 2015-09-24
-
Set hostname as setting
- 499. By Alberto Mardegan on 2015-09-23
-
Accounts are always enabled


FAILED: Continuous integration, rev:496 /code.launchpad .net/~mardy/ reminders- app/new- api/+merge/ 271505/ +edit-commit- message
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https:/
http:// 91.189. 93.70:8080/ job/reminders- app-ci/ 784/ 91.189. 93.70:8080/ job/reminders- app-vivid- amd64-ci/ 206/console
Executed test runs:
FAILURE: http://
Click here to trigger a rebuild: 91.189. 93.70:8080/ job/reminders- app-ci/ 784/rebuild
http://