Tested compiling locally, and pushed 5.0.2-2ubuntu1~raring1~test4 now to qt5-beta-proper PPA. It should get compiled in a couple of hours, in case this is aimed to be had on raring device images (is it?). To test on raring device:
1. Have the latest image installed on your device phablet-flash, adb shell / ubuntu_chroot or ssh in and do apt-get update && apt-get dist-upgrade on the device
2. apt-add-repository ppa:canonical-qt5-edgers/qt5-beta-proper
3. apt-get update
4. apt-get dist-upgrade (check that you get the 5.0.2-2ubuntu1~raring1~test4 version of qtdeclarative related packages)
5. reboot
6. Test
I'd again like two independent confirmations of no regressions, since the raring images are in finalization stage.
If this is however targeted for saucy only, it will automatically come as part of 5.1 later on, or a 5.0.2 update if needed.
Tested compiling locally, and pushed 5.0.2-2ubuntu1~ raring1~ test4 now to qt5-beta-proper PPA. It should get compiled in a couple of hours, in case this is aimed to be had on raring device images (is it?). To test on raring device:
1. Have the latest image installed on your device phablet-flash, adb shell / ubuntu_chroot or ssh in and do apt-get update && apt-get dist-upgrade on the device qt5-edgers/ qt5-beta- proper raring1~ test4 version of qtdeclarative related packages)
2. apt-add-repository ppa:canonical-
3. apt-get update
4. apt-get dist-upgrade (check that you get the 5.0.2-2ubuntu1~
5. reboot
6. Test
I'd again like two independent confirmations of no regressions, since the raring images are in finalization stage.
If this is however targeted for saucy only, it will automatically come as part of 5.1 later on, or a 5.0.2 update if needed.