351622 - indicate reason for no update in update.xml

Status: RESOLVED INCOMPLETE

(AUS Graveyard :: General, defect)

Description

[Dave Liebreich [:davel]]

There are many reasons why update.xml served from aus might contain no updates. This makes testing hard.

Add a field to empty updates to indicate the reason.  suggestion:

<updates>
  <empty reason="no directory" />
</updates>

reason could be "no directory", "no snippet files", "update older than requestor", "unsupported os"

Comment 1

[Myk Melez [:myk] [@mykmelez]]

I ran into this problem today when I tried to tell a partner how to determine the update URL for a given build.  In theory it should be possible to construct the URL given some knowledge about its format, but since there's no way to tell if you get it wrong, it's difficult to rely on it.

It would be useful to be able to tell from the output of AUS whether there are no updates because no updates are available for the build in question or because AUS doesn't have any information about that build.

Comment 2

[Michael Morgan [:morgamic]]

(In reply to comment #1)
> It would be useful to be able to tell from the output of AUS whether there are
> no updates because no updates are available for the build in question or
> because AUS doesn't have any information about that build.
> 
I think we should make a distinction here, even:
* update not available, product/version/platform information exists but build unknown
* update not available, and product/version/platform/build/ information unknown
* update not available, all information is known but it is simply the latest build
* unknown channel or locale is also possible

Comment 3

[Takanori MATSUURA]

This bug lies at rest in the graveyard.