Merge-o-Matic not updating
Bryce Harrington
bryce at canonical.com
Tue Dec 22 22:09:45 GMT 2009
On Tue, Dec 22, 2009 at 01:36:24PM -0800, Kees Cook wrote:
> Hi,
>
> On Tue, Dec 22, 2009 at 09:38:13PM +0100, Lucas Nussbaum wrote:
> > On 22/12/09 at 13:25 -0500, Jordan Mantha wrote:
> > > To find what packages are likely to need a merge you can use the
> > > "Outdated in Lucid, and Lucid has local changes" section of the lists
> > > at:
> > >
> > > http://qa.ubuntuwire.com/multidistrotools/
> >
> > I've also put together a list at
> > http://udd.debian.org/cgi-bin/merges.cgi
>
> For both of these lists, I would find it valuable to include the names
> of the people who did the last upload (and their sponsor if possible),
> so it's easier to scan for stuff that needs one's attention.
Along with that, it would be great if these reports (and others like
them) could also be produced in JSON format. This would allow other
tools to be made which consume this data for use in other ways.
E.g.:
http://bryceharrington.org/X/Reports/desktop-bugs/patches.html
http://bryceharrington.org/X/Data/desktop-bugs/patches.json
Generating a json file for the data is easy (you've already done the
hard parts). Basically:
import simplejson as json
records = [ ]
for item in table:
... your logic here ...
record = {
'foo': item.foo,
'bar': item.bar + 42
}
records.append(record)
print json.dumps(records, indent=4)
Similarly handy JSON libraries exist in perl, ruby, etc. It's a good
way to share data between our various scripts, whatever languages
they're written in.
Bryce
More information about the ubuntu-devel
mailing list