Manual review for kodi-omega

Hello,

I would like to request a review for my snap kodi-omega.

Today I updated the snapcraft.yaml and added DVD and Blu-ray related packages and interfaces (including libdvdcss, libaacs, libbdplus, optical-drive, udisks2, and a personal-files plug for ~/.config/aacs).

The snap is a desktop build of Kodi Omega with X11 and now with Wayland support. A store review is needed . Thank you for reviewing this submission.

Best regards

Yusuf75

This request has been added to the queue for review by the @reviewers team.

Hello @TibSun75,

Please fill out this review template to aid with my review of this request. Thank you!

snapcraft: link to snapcraft.yaml if publicly available
upstream: link to the upstream repository if open-source or ‘PRIVATE’ otherwise
upstream-relation: relation of the snap publisher with the upstream
plugs:
  <plug-name>:
    interface: [optional] one of https://snapcraft.io/docs/reference/interfaces/
    attributes: [optional] interface attributes if any
    request-type: installation | manual-connection | auto-connection
    reasoning: why is this interface needed
  ...
  1. name: Kodi-Omega
  2. description: Snap for Media-Center Kodi
  3. snapcraft: https://github.com/Tibsun75/kodi-omega-snap/blob/main/snapcraft.yaml
  4. upstream:https://github.com/xbmc/xbmc
  5. upstream-relation: I have no connection to the upstream project; Kodi prefers Flatpak…
  6. interfaces:
    • dot-config-aacs, personal-files

      • request-type: manual

      • Path: $HOME/.config/aacs

      • reasoning: Kodi needs read access to the AACS key database (KEYDB.cfg) for Blu-ray playback. Normaly the file is in ~/.config/aacs/. Without this access encrypted Blu-ray discs cannot be played. This is expected functionality for a media center application. Both VLC and the official Kodi .deb packages also ship with AACS support and expect the key database in the user’s home directory.

1 Like

Done—I’d forgotten about that, sorry.

I’d be happy if I could upload it to the Snap Store soon.

Hello @TibSun75,

Unfortunately, personal-files is a super-privileged interface and requires successful publisher vetting. Publisher vetting requires that you are a collaborator or maintainer of the upstream project. If you are willing, I would encourage you to reach out to upstream and offer to maintain a snap version. Without successful publisher vetting, personal-files usage cannot be granted. Thanks for your understanding.