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

Bug#694009: qa.debian.org: Please include suite version information in RDF meta data



On 11/23/2012 12:53 PM, Olivier Berger wrote:
> You mean PTS, right ?

I do, sorry for the confusion :)

>> machine-readable information about the package. However, it misses the
>> information from the versions column (i.e. the current version of a
>> package told apart per suite). It would be super handy to have that
>> information encoded in XML as well.
> 
> What kind of use case do you have ? I have thought about adding these
> kind of meta-data, but haven't yet tackled the problem.

I am trying to implement a sanity check for my dput rewrite (#691624)
which makes sure Debian revision uploads match the orig.tar.gz checksum
of the previous upload. To achieve this, I need the most current version
of a package in a branch and (a) checksum for the orig.tar.gz associated
with it. The latter is already in the RDF.

> Do you know an existing ontology that could be used to link this version
> information to the existing RDF content ?

I'm not sure what exactly you are asking me, but if you ask how to
provide the data in question: Your example data in [1] contains this
information and that would be good enough (altough the associated suite
name, e.g. "stable" would be helpful to know):

# pointer to the release in the different suites :
doap:release <apache2_2.2.16−6+squeeze7>, <apache2_2.2.22−11>,
<apache2_2.4.2−2>.


> I'd suggest a Turtle example (see
> http://www-public.telecom-sudparis.eu/~berger_o/weblog/2012/08/29/debian-package-tracking-system-now-produces-rdf-description-of-source-packages/
> for details on how to generate one using rapper) for the sake of readability.

Glad you picked my package by the way :>

> Depending on the use case, you may be interested in the SOAP interface
> of the PTS also : see http://packages.qa.debian.org/common/index.html
> for pointers.

Indeed, I didn't know about the SOAP interface. That one seems to
provide the information I need while it does not provide the other
information about file checksums it seems by reading [2].


Moreover, a SOAP interface would be much easier to implement than
parsing XML.


[1] >
http://www-public.telecom-sudparis.eu/~berger_o/weblog/2012/08/29/debian-package-tracking-system-now-produces-rdf-description-of-source-packages/
[2] http://people.debian.org/~zack/pts/soap/

-- 
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: