#7291 mdapi files API endpoint fails for f29
Closed: Fixed 5 years ago Opened 5 years ago by cverna.

  • Describe what you need us to do:

it looks like all the requests to https://apps.fedoraproject.org/mdapi/f29/files/<name_of_the_package> are failing when it seems to be working fine for f28

For example https://apps.fedoraproject.org/mdapi/f28/files/qgis works https://apps.fedoraproject.org/mdapi/f29/files/qgis fails

  • When do you need this? (YYYY/MM/DD)
    This is a low priority, this endpoint is used during fedora-packages indexing and the error is not blocking
  • When is this no longer needed or useful? (YYYY/MM/DD)

  • If we cannot complete your request, what is the impact?


So I think this is because f29 branch is not available in mdapi see https://apps.fedoraproject.org/mdapi/branches

Metadata Update from @bowlofeggs:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

5 years ago

Metadata Update from @pingou:
- Issue assigned to pingou

5 years ago

Start to look into this, the issue seems to be that the f29 tree does not contain the sqlite database in the metadata, for example: https://dl.fedoraproject.org/pub/fedora/linux/development/29/Everything/x86_64/os/repodata/

Do someone know why that is?

This is a change in pungi apparently.

There's a config option: createrepo_database which we do not set. If it's not set, it looks to see if you are using dnf or yum, and if using dnf it does NOT create this.

So, we could enable this in pungi configs or is there some other way to get the data?

So, we could enable this in pungi configs or is there some other way to get the data?

Maybe we could get mdapi to re-generate the sqlite database from the XML files not sure if it's doable (could pungi do it?).
Otherwise getting the data outside of the sqlite database would mean parsing the XML and that pretty much means re-writing mdapi :(

The above PR's were merged, so hopefully this should just start working with tomorrows rawhide/branched composes.

Leaving it open to check that.

ok, this should be fixed from the repodata side. Do we need to do anything to get mdapi or packages to refresh?

mdapi seems happy now, I ll run packages indexing process tomorrow that should fix it.

I am closing this. Thanks

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

5 years ago

Login to comment on this ticket.

Metadata