Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

package-chooser not debian/dep11 compatible #1212

Closed
apachelogger opened this issue Aug 9, 2019 · 3 comments

Comments

@apachelogger
Copy link
Contributor

commented Aug 9, 2019

Describe the bug
The package-chooser expects

# For data provided by AppData XML: the item has an *appdata*
# key which points to an AppData XML file in the local filesystem.

this is not a thing on Debian(-derived) systems where a yaml representation known as dep11 is used instead of unpacked xml files. The appstream cache contains the only "unpacked" data stream.

To Reproduce
Steps to reproduce the behavior:

  1. try to find the xml file of an appstream component on a debian system

Expected behavior
Just use appstream. e.g. appstreamcli dump org.kde.krita.desktop if you don't want to use the libraries.

Screenshots and Logs

$ file /var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_bionic_main_dep11_Components-amd64.yml.gz 
/var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_bionic_main_dep11_Components-amd64.yml.gz: symbolic link to /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_bionic_main_dep11_Components-amd64.yml.g

Additional context

@kkofler

This comment has been minimized.

Copy link
Contributor

commented Aug 9, 2019

Well, you can still write the package-chooser data directly to the YAML package-chooser.conf, using AppData XML is optional.

@adriaandegroot

This comment has been minimized.

Copy link
Contributor

commented Aug 19, 2019

The AppStream data is annoying to work with because (also):

  • translations are difficult to load
  • most screenshots are going to be remote URLs

But there's a branch issue-1212 for adding the option at least of using appstream: as a key in the configuration and getting some data from that.

adriaandegroot added a commit that referenced this issue Aug 20, 2019
@adriaandegroot

This comment has been minimized.

Copy link
Contributor

commented Aug 20, 2019

Closing this one, although I'm still following up for remote URLs in screenshots. The AppStream data is loaded (just once) if you use an appstream: entry in the config file, and uses the upstream description as-is.

@adriaandegroot adriaandegroot added this to the v3.2.13 milestone Aug 30, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.