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

Microsoft YUM repositories are missing AppStream metadata #4

Open
Conan-Kudo opened this issue Mar 20, 2022 · 2 comments
Open

Microsoft YUM repositories are missing AppStream metadata #4

Conan-Kudo opened this issue Mar 20, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@Conan-Kudo
Copy link

I noticed with the Microsoft Edge and Microsoft Visual Studio Code YUM repositories that AppStream metadata is not present in the YUM repository metadata. This makes it impossible for software centers like GNOME Software and Plasma Discover to advertise the availability of those applications when the repositories are enabled on the system.

In particular, Fedora is considering shipping the repository definitions for Visual Studio Code (pagureio#fedora-workstation#283) and Edge (pagureio#fedora-workstation#291), but the lack of proper repository metadata makes it a non-starter.

From a practical perspective, what needs to happen after you create the repository metadata with createrepo_c is:

  1. Generate AppStream repodata from the RPMs
  2. Append the AppStream repodata to the YUM repository

Step 1 is done by using appstream-builder:

appstream-builder			\
	--origin=Microsoft		\
	--basename=appstream		\
	--cache-dir=/tmp/asb-cache	\
	--enable-hidpi			\
	--max-threads=1			\
	--min-icon-size=32		\
	--output-dir=/tmp/asb-md	\
	--packages-dir=x86_64/		\
	--temp-dir=/tmp/asb-icons

Step 2 is done with modifyrepo_c:

modifyrepo_c				\
	/tmp/asb-md/appstream.xml.gz	\
	x86_64/repodata/
modifyrepo_c				\
	/tmp/asb-md/appstream-icons.tar.gz	\
	x86_64/repodata/

Once this is done, you now have YUM repository metadata with AppStream repository metadata for software centers to leverage for showing your applications for users to install.

@daviddavis
Copy link
Member

Hi @Conan-Kudo! Good to see you. I will take a look into this and report back. Thanks for opening an issue.

@daviddavis
Copy link
Member

daviddavis commented Mar 21, 2022

We're evaluating Pulp to potentially handle publishing our rpm metadata and it looks like it currently doesn't support this. I opened an issue though:

pulp/pulp_rpm#2432

@daviddavis daviddavis added the enhancement New feature or request label Mar 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants