[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Canonicalising suites

Am 1. Dezember 2014 23:59:45 MEZ, schrieb Ian Jackson <ijackson@chiark.greenend.org.uk>:
>Joerg Jaspert writes ("Re: Canonicalising suites"):
>> Not with the above two, but luckily Ansgar is also working on the
>> The madison part may be for you to ask for single packages, except
>> it currently only returns stupid plain text. Would be good if Ansgar
>> could enhance that with optional json output.
>> Current output of a package which is in the archive AND in NEW looks
>> ceph       | 0.80.7-1~bpo70+1 | wheezy-backports | source, amd64,
>armel, armhf, i386, ia64, mips, mipsel, powerpc, s390x
>> ceph       | 0.80.7-1         | testing          | source, amd64,
>arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x
>> ceph       | 0.80.7-1         | unstable         | source, amd64,
>arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x, sparc
>> ceph       | 0.87-1           | new              | source, amd64
>> So then you can have all sources we know, all sources belonging to
>> $suite and information in which suite a given package is, which
>> all kinds of policy queues (like NEW is one). (see dakweb/madison.py
>> information on how you can modify the stuff it looks for).
>> Does that look better?
>The latter is perfect, provided (a) you don't mind me parsing the
>plain text (b) you don't mind me periodically (maybe once a day?)
>querying for every package in NEW.


I DO mind parsing plain text. Thats just sick.

Ansgar already said on IRC, that adding json output isn't hard to do.

If that is there, are your needs currently all in the api?

Reply to: