[Patch] Fix wrong initial position of delegates when using loaders and sections

Bug #1183350 reported by Albert Astals Cid
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qtdeclarative-opensource-src (Ubuntu)
Fix Released
Undecided
Timo Jyrinki

Bug Description

Bug reported at https://bugreports.qt-project.org/browse/QTBUG-28403

Change already merged upstream for 5.1 https://codereview.qt-project.org/#change,56583

Will attach a mergeable patch against our 5.0.x packages

Tags: patch
Revision history for this message
Albert Astals Cid (aacid) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "The said patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Changed in qtdeclarative-opensource-src (Ubuntu):
assignee: nobody → Timo Jyrinki (timo-jyrinki)
status: New → In Progress
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

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.

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

This is available for saucy in qt5-beta2 PPA (https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-beta2). I'd like to have before/after testing done on device, but using saucy on device is at the moment hard before the images generation is in full speed and network is working. The updated package also includes the fix for qtdeclarative bug #1187746 (and the PPA contains newer qtpim and qtbase).

The test procedure is: 1. Have the latest saucy image installed on your device. Log in, and do apt-get update && apt-get dist-upgrade on the device 2. apt-add-repository ppa:canonical-qt5-edgers/qt5-beta2 3. apt-get update && apt-get dist-upgrade (check that you get the PPA versions of the packages) 4. Reboot. Test!

After testing has been done, the updated version can be uploaded to saucy from lp:~kubuntu-packagers/kubuntu-packaging/qtdeclarative-opensource-src_5.0.2 (orig tarball already in saucy archives)

Changed in qtdeclarative-opensource-src (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package qtdeclarative-opensource-src - 5.0.2-1ubuntu2

---------------
qtdeclarative-opensource-src (5.0.2-1ubuntu2) saucy; urgency=low

  [ Timo Jyrinki ]
  * debian/patches/8a3d48915c29484c9ffb2fb8f0e3b569a9fe9b44_backport.patch:
    - Cherry-pick from upstream
      https://codereview.qt-project.org/#change,56583 (LP: #1183350)
  * debian/patches/0001-Fallback-to-QMetaObject-for-properties-not-in-QQmlPr.patch:
    - Cherry-pick from upstream
      https://codereview.qt-project.org/#change,57392 (LP: #1187746)
 -- Ken VanDine <email address hidden> Thu, 20 Jun 2013 15:24:17 -0400

Changed in qtdeclarative-opensource-src (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.