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

flatpak packages not able to install when packagekit is not present #142

Open
philmmanjaro opened this issue Aug 18, 2024 · 6 comments
Open

Comments

@philmmanjaro
Copy link

On Manjaro Immutable I created a COSMIC profile. There we normally preferred flatpaks. So we don't install packagekit, since installing packages via pacman won't work, unless the rootfs is unlocked.

image

Also when packagekit got installed, the store seems to be confused still:

image

The following PKGBUILD was used to build the package. I might check on my end what will happen if packagekit is not used as a build dependency.

@philmmanjaro
Copy link
Author

I've tested it a little further. Due to the package archlinux-appstream-data the store only knows about native packages. Therefore it doesn't browse flathub. So installing packagekit will work after a pacman -Syy was done once to sync the databases.

Also it doesn't matter if packagekit was availble on build time, the store still asks for it.

@philmmanjaro
Copy link
Author

Seems you have to call flatpak remote-add --user flathub https://flathub.org/repo/flathub.flatpakrepo to add it as a user. So adding it as system-wide via flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo is not working.

@mmstick
Copy link
Member

mmstick commented Aug 18, 2024

system flatpaks are not implemented #37

@yochananmarqos
Copy link

yochananmarqos commented Aug 18, 2024

@philmmanjaro

Due to the package archlinux-appstream-data the store only knows about native packages. Therefore it doesn't browse flathub.

It turns out it's an Arch / AUR packaging issue. archlinux-appstream-data should be optional along with packagekit.

You already found the solution:

Seems you have to call flatpak remote-add --user flathub https://flathub.org/repo/flathub.flatpakrepo to add it as a user.

I can install Flatpaks fine with COSMIC Store after doing that on Arch via my cosmic AUR packages. Installing packagekit is not required.

On Arch, COSMIC Store can be used to install Flatpaks and Pacman should be used to install Arch packages. No need for packagekit at all.

As far as the Manjaro immutable edition, it seems COSMIC Store should only be used for Flatpaks since neither Pacman nor Packagekit are applicable.

@mmstick It appears we've resolved this, I'm sure it can be closed.

EDIT: Sorry, made several edits for clarification.

@philmmanjaro
Copy link
Author

Well, the question is more on how this should work. If archlinux-appstream-data or any distro data for appstream is given, Then of course it should be also possible to choose and install those, when logical. Additionally if flathub appstream data, now only per user, is given, does that override the distro specific appstream data, which is mostly system wide?

Arch for example provides Telegram, flathub too. As in my screenshots shown, the Telegram suggest the user it will get downloaded from flathub, but actually archlinux-appstream-data, which was the only appstream data when doing so, will request to install the native ALPM package from the system repos.

@yochananmarqos
Copy link

@philmmanjaro I think what you're referring to is the confusion about what COSMIC Store is installing. For example, GNOME Software will show whether one will be installing a system package (i.e, RPM, DEB, etc.) or Flatpak.

Remember, this is Alpha software, not every feature is implemented yet.

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