Fedora Account System
Red Hat Associate
Red Hat Customer
I just happened to rebuild a package (spyder) which built fine previously. I made no changes to the package, but the build now fails with: appstreamcli validate --no-net --explain /builddir/build/BUILDROOT/spyder-6.0.0~a1-17.20240117gitv6.0.0a1.fc41.x86_64//usr/share/metainfo/org.spyder_ide.spyder.appdata.xml W: org.spyder_ide.spyder:~: url-homepage-missing This component is missing an `url` element of type `homepage` to link to the project's homepage. I: org.spyder_ide.spyder:~: content-rating-missing This component has no `content_rating` tag to provide age rating information. You can generate the tag data online by answering a few questions at https://hughsie.github.io/oars/ ✘ Validation failed: warnings: 1, infos: 1, pedantic: 2 Build log: https://download.copr.fedorainfracloud.org/results/gui1ty/updates/fedora-rawhide-x86_64/07097539-spyder/builder-live.log.gz It seems to affect users as well. On IRC a user reported (for all software): Hello! Just installed the OS but none of the software are listed on the applications menu They're installed but can't access to them Other users are reporting on the issue as well: https://forums.fedoraforum.org/showthread.php?330034-COMP-NEURO-Lab-does-not-install-the-modelling-tools&p=1867320 Reproducible: Always Steps to Reproduce: 1. Rebuild an application package that succeeded previously with updated appstream 2. Install Fedora 40 3. Actual Results: 1. Build fails 2. Installed apps not available in menu Expected Results: 1. Build succeeds as it did before. 2. Apps are visible in menu.
Proposed as a Blocker and Freeze Exception for 40-beta by Fedora user gui1ty using the blocker tracking app because: This breaks the release criteria. It also prevents packagers from rebuilding packages that built fine previously.
I was a bit hasty in concluding the issues are related. The issue with the build breaking with the updated appstream is definitely there, but doesn't warrant it being a blocker issue. I'll try to get this all fixed with regards to the blocker proposal. I hope simply removing the bugs listed in 'Blocks' will do the trick.
Apparently, appstreamcli is now stricter when validating appdata. Running the same command with appstreamcli 0.16.1 I get: appstreamcli validate --no-net --explain ./scripts/org.spyder_ide.spyder.appdata.xml I: org.spyder_ide.spyder:~: content-rating-missing This component has no `content_rating` tag to provide age rating information. You can generate the tag data online by answering a few questions at https://hughsie.github.io/oars/ ✔ Validation was successful: infos: 1, pedantic: 2 It seems URL is now mandatory.
Similarly, with agenda: /builddir/build/BUILDROOT/agenda-1.1.2-19.fc41.x86_64//usr/share/metainfo/com.github.dahenson.agenda.appdata.xml: OK + appstreamcli validate --no-net --explain /builddir/build/BUILDROOT/agenda-1.1.2-19.fc41.x86_64//usr/share/metainfo/com.github.dahenson.agenda.appdata.xml W: com.github.dahenson.agenda:15: developer-id-missing The `developer` element is missing an `id` property, containing a unique string ID for the developer. Consider adding a unique ID. This is not a packaging issue, but the upstream practice of exiting with nonzero status for warnings (effectively making warnings errors) and frequently adding new warnings is pretty hard to deal with. I suspect I have a dozen or so upstreams to ask about adding a developer ID now…
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.