Wrong metainfo at https://apps.fedoraproject.org/packages/fips

[matwey]

Hello,

I have package https://src.fedoraproject.org/rpms/fips

When I use 'Packages' badge on the page, I am redirected to https://apps.fedoraproject.org/packages/fips where I see description from other package, but released versions for my package. What could be wrong with all this?

[JimBreton]

Hi, @matwey , are you finding this to still be the case? Unless I'm mistaken, the description on the 'Packages' page looks correct now?

I'm curious about this as I have seen a similar issue with a random other package, https://apps.fedoraproject.org/packages/webkitgtk appears to be loading the description for libproxy. Is the Packages listing totally unreliable? I'm quite sure the description for webkitgtk is wrong, it doesn't even match the description in the .spec files of downloaded RPMs, so the data must be coming from someplace else.

[matwey]

Hi @JimBreton , currently everything is ok with Fips package. I thought that it had already been fixed. But webkitgtk is indeed wrong currently!

[pypingou]

Thanks for your report but this is however, the wrong place for such bug report.

This issue tracker is about the web application running at: https://apps.fedoraproject.org/packages/

Your ticket should be open in https://bugzilla.redhat.com

Sorry, I'm misread your initial ticket and put in the wrong comment

It does seem that this is closed now so let's keep it as such (or re-open if you disagree) :)

[JimBreton]

Hi @pypingou , thanks for following up on this!

I don't want to speak for @matwey but I do think the issue is closed for his specific package in question, but, I think there is still a problem with the 'Packages' app itself as manifested in the wrong description for the webkitgtk package. It may be the same underlying cause, I am not sure; but Packages is definitely showing the wrong description for webkitgtk. Would it make sense to keep this open until the cause for that is found?

[pypingou]

The packages apps is one of the apps that we have that needs more man power than we can give it at this time :(

I'll re-open the ticket so we can use it to track this issue, but there is no ETA on getting it fixed, sorry :(