On Wed, 14 Oct 2009, Bastian Venthur wrote: > I'm trying my best to parse the SOAP replies provided by debbugs, > but now I'm kind of stucked. > > A general and probably very easy question first: what is the difference > between: > > fixed_versions and fixed > found_versions and found
fixed and found are hashrefs which indicate when a bug was marked fixed and found; currently that's not implemented, so they are hashrefs which have a key of the version, and a value of ''. Eventually I'll probably make it work, though. fixed_versions and found_versions are arrayrefs which just have the version that things are fixed and found in. It's probably what you actually want. > id and bug_num These are the same; it's basically repeated because some things in the code refer to a bug by id, and others by bug_num. I'm going to be standardizing on bug_num, so if you can avoid using ID, that'd be optimal. > summary and subject -- here also: why is summary always empty? It's not, actually. See http://www.debian.org/Bugs/server-control#summary and FE: $ bts status 441151|grep summary summary It's already fixed in my tree and will be fixed in the BTS the next time that I sync things up. > The second and currently most urgent question: Some fields like > "found" are very hard to parse. Usually found is a dictionary > (pardon my Python :) containing a key "item" which contains a single > or a list of dictionaries containing a "key" key which has the > version as value. Vice versa, actually. The version is the key, and the timestamp at which the version was marked or the empty string is the value. Don Armstrong -- There is no more concentrated form of evil than apathy. http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
