Comment 6 for bug 1215586

I just took a quick peek to see if this is something we could support. I'm confused though; enabling the signal in s-i-dbus gives this kind of UpdateAvailableStatus:

signal sender=:1.79 -> dest=(null destination) serial=67 path=/Service; interface=com.canonical.SystemImage; membe
r=UpdateAvailableStatus
   boolean true
   boolean true
   string "41"
   int32 153477688
   string "2014-05-16 09:48:27"
   array [
      array [
         dict entry(
            string "description"
            string "ubuntu=20140516.3,device=20140513.2,version=33"
         )
      ]
      array [
         dict entry(
            string "description"
            string "ubuntu=20140516.4,device=20140513.2,version=34"
         )
      ]
      array [
         dict entry(
            string "description"
            string "ubuntu=20140517,device=20140513.2,version=35"
         )
      ]
      array [
         dict entry(
            string "description"
            string "ubuntu=20140518,device=20140513.2,version=36"
         )
      ]
      array [
         dict entry(
            string "description"
            string "ubuntu=20140519,device=20140513.2,version=37"
         )
      ]
      array [
         dict entry(
            string "description"
            string "ubuntu=20140519.1,device=20140513.2,version=38"
         )
      ]
      array [
         dict entry(
            string "description"
            string "ubuntu=20140520,device=20140513.2,version=39"
         )
      ]
      array [
         dict entry(
            string "description"
            string "ubuntu=20140521,device=20140513.2,version=41"
         )
      ]
   ]
   string ""

what are we supposed to do with those descriptions? Perhaps this means that the
server isn't providing what we want yet?