fedora-infrastructure

#9731 Anitya/Release monitoring database dump in JSON/XML ?
Closed: Upstream by smooge. Opened by tpetazzoni.

Closed: Upstream
Reopen Issue

We at the Buildroot project (http://www.buildroot.org) use intensively the release-monitoring.org service to verify if our packages have newer upstream releases available. In order to do this, we query release-monitoring.org through its HTTP API for our 2500+ packages.

It would be a lot nicer if we could download a dump of the database, and it would also reduce the load on release-monitoring.org: we would download a single static database dump instead of making thousands of HTTP requests. As discussed at https://github.com/fedora-infra/anitya/issues/455#issuecomment-799294790 there is already a dump of the PostgreSQL database online, but it would be a lot nicer to have a JSON/XML dump that can be easily parsed without using a PostgreSQL server. Do you think this would be possible ?

there is already a dump of the PostgreSQL database online, but it would be a lot nicer to have a JSON/XML dump that can be easily parsed without using a PostgreSQL server. Do you think this would be possible ?

Is there a way to dump a PostgreSQL database into JSON/XML via pg_dump?

Ideally, Anitya would have its own functionality to dump its complete database as a useful JSON blurb.

Ideally, Anitya would have its own functionality to dump its complete database as a useful JSON blurb.

That makes this request an upstream RFE since until it's available upstream
there is not much we can do :(

The upstream for anitya seems to be https://github.com/fedora-infra/anitya/issues . Please file this there for the developer to access

Metadata Update from @smooge:
- Issue tagged with: dev, low-gain, medium-trouble

Metadata Update from @smooge:
- Issue close_status updated to: Upstream
- Issue status updated to: Closed (was: Open)

My issue already point to an issue on the anitya tracker... which suggested to report a bug here. It feels like we're going circles here.

My issue already point to an issue on the anitya tracker... which suggested to report a bug here. It feels like we're going circles here.

Well, the infrastructure is happy to set-up a cron job that would run this script but that script needs to be written first and you've said yourself that it is probably something that anitya should provide.
Metadata
None

dev low-gain medium-trouble

None
None
Lowest
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.