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

AppStream metadata allow user uninstallation of PackageKit #759

Closed
AsciiWolf opened this issue May 20, 2024 · 4 comments
Closed

AppStream metadata allow user uninstallation of PackageKit #759

AsciiWolf opened this issue May 20, 2024 · 4 comments

Comments

@AsciiWolf
Copy link
Contributor

An AppStream metainfo file was added in PackageKit v1.2.8. Unfortunately, this file causes PackageKit to show in GNOME Software, KDE Discover and other package management GUIs and allow users to click an "Uninstall" button. This fortunately does nothing in Fedora, but there may be some distributions and/or configurations that will allow this.

Please, consider reverthing the AppStream metainfo file addition until a better solution is found.

For more information see this comment in upstream GNOME Software ticket.

@ximion ximion closed this as completed in d8f84f7 May 21, 2024
@AsciiWolf
Copy link
Contributor Author

AsciiWolf commented May 23, 2024

@ximion Any chance a new version of PackageKit with this fix could be released soon?

(If the fix works correctly. I am not 100% sure whether multiple compulsory_for_desktop tags are supported.)

@sidt4
Copy link
Contributor

sidt4 commented May 23, 2024

I am not 100% sure whether multiple compulsory_for_desktop tags are supported.

Matt is the maintainer of PackageKit and Appstream. So, no worries :).

@ximion
Copy link
Collaborator

ximion commented May 23, 2024

Any chance a new version of PackageKit with this fix could be released soon?

Yes, with a bit of luck before I will be away on a trip next week, otherwise the week after. There is still some pretty nasty bugs in PK that really should be fixed before the next release happens, and @sidt4 also has a bunch of patches that I need to review - slow releases are 100% a result of me barely having any time to work on this currently, so progress is slow. Sorry for that! There will be a new release though, if it doesn't happen this month, then for sure next month :-)

@sidt4
Copy link
Contributor

sidt4 commented May 23, 2024

I would not hurry up the release especially given the lower frequency of PK releases, and the expected new fixes / commits in the coming days. It would be nice to have at least a 3 - 4 days of testing before tagging a release. And if the commit count increases soaking time would increase accordingly.

Just my opinion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants