$ sudo appstream-compose -verbose -origin=audacity audacity Processing application Įrror loading AppData file: no file found for $ sudo appstream-compose -verbose -origin=audacity ![]() I guess the only way to understand is building the appstream-data rpm? Which id is appstream-compose using for Audacity?ĪppData file is called, but its id is The interface is translated into many languages.You can use Audacity to:Record live audioConvert tapes and records into digital recordings or CDsEdit WAV, AIFF, FLAC, MP2, MP3 or Ogg Vorbis sound filesCut, copy, splice or mix sounds togetherChange the speed or pitch of a recordingApply a wide range of other effects to audio recordings $ zcat audacity_files/usr/share/app-info/xmls/|headĪudacity® is a free, easy-to-use, multi-track audio editor and recorder for Windows, Mac OS X, GNU/Linux and other operating systems. Saving AppStream /home/drusek/Downloads/audacity_files/usr/share/app-info/xmls/ Saving icon audacity_files/usr/share/app-info/icons/128x128/audacity.png Saving icon audacity_files/usr/share/app-info/icons/64圆4/audacity.png WARNING: Metadata origin not set, using 'example' $ appstream-compose -prefix audacity_files/usr/ audacity However, when I tried running appstream-compose on manually extracted content of the audacity-2.3.86_64.rpm package, everything was fine: What command should I use? The appstream-compose one does not seem to understand -logdir switch. I will move this back to the Audacity component and take Which releases should this be fixed in? I will definitely fix it in Rawhide, but is it worth backporting the fix to f31/32 and EPEL7/8, or are no new runs of the appstream-builder going to be done for those branches now that they are released? So it looks like Audacity should be using the "desktop-id" type in its appdata file instead of "desktop" and appstream-util-validate is failing to recognize that "desktop" is an invalid type when it is used - with any of the validate options - so there is a bug in both those packages. So apparently appstream-builder requires the tag to be "desktop-id" specifically, but the validation programs don't flag that the "desktop" tag is incorrect (I looked at the spec - and it lists "desktop-id" but not "desktop", so I think "desktop-id" is the standard form, but this says the spec was most recently updated in May of this year). Makes the warning about no desktop file go away. After some experimenting, this looks to be caused by the line having an incorrect type. So apparently it wasn't finding the desktop file. (appstream-builder:313832): Asb-DEBUG: 23:52:32.120: WARNING: Ignoring: a desktop file is required for The log of a run of the appstream-builder utility shows the following: I did some digging into this tonight, and a small change in Audacity's appdata.xml file can fix this I believe. ![]() There were also some GNOME Software related issues with Audacity and other packages, but they are already fixed, see: You can try replacing the AppData file in Fedora with upstream version: ![]() Click the result and see if there is a RPM source displayed in the drop-down Source list in window header. Version-Release number of selected component (if applicable):ģ. The Flathub and Fedora Flatpak sources of Audacity are displayed without any issue. ![]() The Fedora package version of Audacity is not displayed in GNOME Software at all. Audacity seems to have something wrong in its AppData file.
0 Comments
Leave a Reply. |