dx-packages team mailing list archive

[Brian Murray <brian@xxxxxxxxxx>]

Hello Christopher, or anyone else affected,

Accepted unity into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/unity/7.2.1+14.04.20140513-0ubuntu2
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1307748

Title:
  xpathselect attribute matching doesn't match anything other than
  object Ids

Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  I came across this issue while testing an autopilot branch of mine.

  The xpathselect server-side matching (as opposed to matching in the
  autopilot python code) is not working as expected.

  To reproduce:
    - Save this code as test_selection_attributes.py -  http://paste.ubuntu.com/7252495/ 
    - (with the unity-autopilot package installed) run: `autopilot run test_selection_attributes`

  This script contains 2 tests, one passes to prove that it can get a
  Launcher that has the monitor attribute of 0, the 2nd test attempts to
  select the Launcher object with attribute monitor=0 and fails.

  We see in the unity logs:
   -   "Unable to match 'monitor' against property of unknown integer type."

  A bit of digging suggests that GetPropertyValue is returning an array
  of values (Probably: Object type id, Value?) which means that, in
  MatchIntegerProperty for instance, the values GVariantClass will never
  be one of the Integer types.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1307748/+subscriptions