Comment 2 for bug 1050853

Having an accurate understanding of the archive state (-proposed, -updates, etc.) where the error was detected is necessary for figuring out appropriate next actions in an automated fashion. Would rather see the package origin data be included so we can be definitive and create bots to help, rather than rely on judgement from version number inferences.

A fast way to do this might be to continue to overload the tags. That is rather than adding just the tag "precise", it could be "precise-proposed" or "precise-updates" and use "precise" when its part of the released iso version.