Artix Linux => Applications & Software => Topic started by: Rainbow Sun on 24 January 2022, 23:17:18
Title: Flatpak extension in Pamac possible
Post by: Rainbow Sun on 24 January 2022, 23:17:18
Hello Community, About 7 months ago this still worked with the old Artix version where you could install Pamac without any problems. With the current version I get difficulties as described. I hope you can help me. The goal: Install Pamac with Flatpak (plugin) support on an Artix KDE Plasma runit. The problem: With the terminal command
# By default, pacman accepts packages signed by keys that its local keyring # trusts (see pacman-key and its man page), as well as unsigned packages. SigLevel = Required DatabaseOptional LocalFileSigLevel = Optional #RemoteFileSigLevel = Required
# NOTE: You must run `pacman-key --init` before first using pacman; the local # keyring can then be populated with the keys of all official Artix Linux # packagers with `pacman-key --populate artix`.
# # REPOSITORIES # - can be defined here or included from another file # - pacman will search repositories in the order defined here # - local/custom mirrors can be added here or in separate files # - repositories listed first will take precedence when packages # have identical names, regardless of version number # - URLs will have $repo replaced by the name of the current repo # - URLs will have $arch replaced by the name of the architecture # # Repository entries are of the format: # [repo-name] # Server = ServerName # Include = IncludePath # # The header [repo-name] is crucial - it must be present and # uncommented to enable the repo. #
# The gremlins repositories are disabled by default. To enable, uncomment the # repo name header and Include lines. You can add preferred servers immediately # after the header, and they will be used before the default mirrors.
# An example of a custom package repository. See the pacman manpage for # tips on creating your own repositories. #[custom] #SigLevel = Optional TrustAll #Server = file:///home/custompkgs
[universe] Server = https://universe.artixlinux.org/$arch Server = https://mirror1.artixlinux.org/universe/$arch Server = https://mirror.pascalpuffke.de/artix-universe/$arch Server = https://artixlinux.qontinuum.space:4443/universe/os/ Server = https://mirror1.cl.netactuate.com/artix/universe/$arch
[omniverse] Server = http://omniverse.artixlinux.org/$arch
# Arch [extra] Include = /etc/pacman.d/mirrorlist-arch
[community] Include = /etc/pacman.d/mirrorlist-arch
[multilib] Include = /etc/pacman.d/mirrorlist-arch
In the pamac search it finds 3 times pamac-flatpaks. When trying to install one of them, the error message appears for each of them
Failed to prepare transaction could not satisfy dependencies: - removing pamac-cli breaks dependency 'pamac-cli=10.2.2-1' required by pamac-gtk, - if possible, remove pamac-gtk and retry - removing libpamac breaks dependency 'libpamac>=11.1' required by pamac-gtk, - if possible, remove pamac-gtk and retry - removing libpamac breaks dependency 'libpamac<11.2' required by pamac-gtk, - if possible, remove pamac-gtk and retry
removed the packages after error message, then it removes me the complete pamac and can't start it anymore and in the terminal it doesn't find me the pamac-flatpak package either. After that I installed yay with Pacman and tried again with yay to install pamac-full to get flatpak and snap support (although only flatpak is my goal) and this didn't work either because the system need to run a systemd on a systemd free distro. About 7 months ago I was able to install Pamac with Flatpak on the notebook of my acquaintances without any problems (with positive conviction) and currently I have problems to install Pamac on my own computer despite the activation in the config except the testing mirrors. What am I doing wrong or missing or belongs corrected? Thank you for your time/ear given to me. Thanks Translated with DeepL
Title: Re: Flatpak extension in Pamac possible
Post by: Chris Cromer on 25 January 2022, 02:20:27
# By default, pacman accepts packages signed by keys that its local keyring # trusts (see pacman-key and its man page), as well as unsigned packages. SigLevel = Required DatabaseOptional LocalFileSigLevel = Optional #RemoteFileSigLevel = Required
# NOTE: You must run `pacman-key --init` before first using pacman; the local # keyring can then be populated with the keys of all official Artix Linux # packagers with `pacman-key --populate artix`.
# # REPOSITORIES # - can be defined here or included from another file # - pacman will search repositories in the order defined here # - local/custom mirrors can be added here or in separate files # - repositories listed first will take precedence when packages # have identical names, regardless of version number # - URLs will have $repo replaced by the name of the current repo # - URLs will have $arch replaced by the name of the architecture # # Repository entries are of the format: # [repo-name] # Server = ServerName # Include = IncludePath # # The header [repo-name] is crucial - it must be present and # uncommented to enable the repo. #
# The gremlins repositories are disabled by default. To enable, uncomment the # repo name header and Include lines. You can add preferred servers immediately # after the header, and they will be used before the default mirrors.
# An example of a custom package repository. See the pacman manpage for # tips on creating your own repositories. #[custom] #SigLevel = Optional TrustAll #Server = file:///home/custompkgs
[universe] Server = https://universe.artixlinux.org/$arch Server = https://mirror1.artixlinux.org/universe/$arch Server = https://mirror.pascalpuffke.de/artix-universe/$arch Server = https://artixlinux.qontinuum.space:4443/universe/os/ Server = https://mirror1.cl.netactuate.com/artix/universe/$arch
[omniverse] Server = http://omniverse.artixlinux.org/$arch
# Arch [extra] Include = /etc/pacman.d/mirrorlist-arch
[community] Include = /etc/pacman.d/mirrorlist-arch
[multilib] Include = /etc/pacman.d/mirrorlist-arch
and i see no Flatpak options in the Pamac options. I think i get no AUR results in consol. Why? I use KDE Runit
Title: Re: Flatpak extension in Pamac possible
Post by: just on 25 January 2022, 11:06:52
...i see no Flatpak options in the Pamac options. I think i get no AUR results in consol. Why?..
1. As mentioned by @conky60 , pamac-flatpak is found in AUR
2. The package name is pamac-flatpak, not pamac-flatpack
3. pacman never searches anything and doesn't work at all with AUR
4. To work with AUR, an AUR helper(s) must be installed
5. Artix has yaourt(ix) and yay in the [universe] repo; both are good AUR helpers and may be installed with pacman
6. Once one or another, or both, are installed, use them to find and install aur/pamac-flatpak package
7. Both yaourt and yay must be run by a regular user, i.e. elevated (root) privileges aren't required; you'll be asked for root password when | if needed:
1. As mentioned by @conky60 , pamac-flatpak is found in AUR
2. The package name is pamac-flatpak, not pamac-flatpack
3. pacman never searches anything and doesn't work at all with AUR
4. To work with AUR, an AUR helper(s) must be installed
5. Artix has yaourt(ix) and yay in the [universe] repo; both are good AUR helpers and may be installed with pacman
6. Once one or another, or both, are installed, use them to find and install aur/pamac-flatpak package
7. Both yaourt and yay must be run by a regular user, i.e. elevated (root) privileges aren't required; you'll be asked for root password when | if needed:
$ pamac search pamac-flatpak libpamac-flatpak 11.1.0-1 AUR Library for Pamac package manager based on libalpm - flatpak support enabled pamac-flatpak-gnome 10.2.0-1 AUR A Gtk3 frontend for libalpm (with AUR, Flatpak, AppIndicator support, and GNOME integration) pamac-flatpak 10.2.0-1 AUR A Gtk3 frontend for libalpm (with AUR, Flatpak and AppIndicator support) $
Title: Re: Flatpak extension in Pamac possible
Post by: Rainbow Sun on 26 January 2022, 11:34:59
I am sorry. I mistyped for the forum with flatpak. Often the fingers are faster than the head. :) Aah Okay, and I thought we could also download AUR packages with pacman because pamac can also display them without problems. I also thought pamac was the graphical user interface for pacman. Didn't know that we can't download AURs with pacman and that we need little helpers. Okay, I have now tried reinstalling pamac to get the console error messages. Here is the progress. First I uninstalled pamac via the console, then I have restarted the operating system (Artix Linux KDE Runit) and opened the console to start the new installation of pamac. This was followed by the installation of pamac-flatpak via yay.
User:[home]:~$ sudo pacman -S pamac [sudo] password for home: resolving dependencies... looking for conflicting packages... :: libpamac and libpamac-flatpak are in conflict. Remove libpamac-flatpak? [y/N] n error: unresolvable package conflicts detected error: failed to prepare transaction (conflicting dependencies) :: libpamac and libpamac-flatpak are in conflict
User:[home]:~$ sudo pacman -S pamac resolving dependencies... looking for conflicting packages... :: libpamac and libpamac-flatpak are in conflict. Remove libpamac-flatpak? [y/N] y
Total Installed Size: 4,38 MiB Net Upgrade Size: 1,10 MiB
:: Proceed with installation? [Y/n] y (3/3) checking keys in keyring [##############################################################] 100% (3/3) checking package integrity [##############################################################] 100% (3/3) loading package files [##############################################################] 100% (3/3) checking for file conflicts [##############################################################] 100% (4/4) checking available disk space [##############################################################] 100% :: Processing package changes... (1/1) removing libpamac-flatpak [##############################################################] 100% (1/3) installing libpamac [##############################################################] 100% ==> An authentication agent is required Cinnamon, Deepin, GNOME, GNOME Flashback, KDE, LXDE, LXQt, MATE and Xfce have an authentication agent already. See https://wiki.archlinux.org/index.php/Polkit#Authentication_agents for other desktop environments. ==> You had an old /etc/pamac.conf.pacsave file. We restore it for you. ==> You can find your new pamac.conf saved as `/etc/pamac-new-01264902.conf` Optional dependencies for libpamac libpamac-flatpak-plugin archlinux-appstream-data [installed] (2/3) installing pamac-cli [##############################################################] 100% >>> THIS TOOL IS NOT SUPPORTED BY ARTIX (NOR BY ARCH) THE USE OF AUR HELPERS CAN RESULT IN A BROKEN SYSTEM MAKE SURE TO HAVE A VALID BACKUP FIRST AND USE AT YOUR OWN RISK (3/3) installing pamac-gtk [##############################################################] 100% >>> THIS TOOL IS NOT SUPPORTED BY ARTIX (NOR BY ARCH) THE USE OF AUR HELPERS CAN RESULT IN A BROKEN SYSTEM MAKE SURE TO HAVE A VALID BACKUP FIRST AND USE AT YOUR OWN RISK ==> Enable Pamac Updates Indicator via Gnome Tweak Optional dependencies for pamac-gtk pamac-gnome-integration: for integration into Gnome libpamac-flatpak-plugin: for Flatpak support :: Running post-transaction hooks... (1/3) Updating the MIME type database... (2/3) Updating icon theme caches... (3/3) Updating the desktop file MIME type cache... User:[home]:~$ yay -Syu pamac-flatpak :: Synchronizing package databases... system is up to date world is up to date galaxy is up to date lib32 is up to date universe is up to date omniverse 72,6 KiB 303 KiB/s 00:00 [##############################################################] 100% extra is up to date community 6,0 MiB 1698 KiB/s 00:04 [##############################################################] 100% multilib is up to date :: Starting full system upgrade... warning: python-packaging: local (21.0-1) is newer than world (20.9-7) there is nothing to do :: Searching databases for updates... :: Searching AUR for updates... -> python-packaging: local (21.0-1) is newer than world (20.9-7) -> Flagged Out Of Date AUR Packages: jdownloader2 :: 1 Packages to upgrade. 1 aur/jack 0.125.0-9 -> 0.126.0-3 ==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name) ==> 1 :: Checking for conflicts... :: Checking for inner conflicts... -> Package conflicts found: -> Installing pamac-flatpak will remove: pamac-gtk, pamac-gtk (pamac), pamac-cli -> Installing libpamac-flatpak will remove: libpamac -> Conflicting packages will have to be confirmed manually [Aur:2] libpamac-flatpak-11.1.0-1 pamac-flatpak-10.2.0-1
2 libpamac-flatpak (Build Files Exist) 1 pamac-flatpak (Build Files Exist) ==> Packages to cleanBuild? ==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4) ==> a :: Deleting (1/2): /home/home/.cache/yay/libpamac-flatpak :: Deleting (2/2): /home/home/.cache/yay/pamac-flatpak :: (1/2) Downloaded PKGBUILD: libpamac-flatpak :: (2/2) Downloaded PKGBUILD: pamac-flatpak 2 libpamac-flatpak (Build Files Exist) 1 pamac-flatpak (Build Files Exist) ==> Diffs to show? ==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4) ==> n :: (1/2) Parsing SRCINFO: libpamac-flatpak :: (2/2) Parsing SRCINFO: pamac-flatpak ==> Making package: pamac-flatpak 10.2.0-1 (Mi 26 Jän 2022 09:49:48) ==> Retrieving sources... -> Downloading pamac-10.2.0.tar.gz... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0==> Making package: libpamac-flatpak 11.1.0-1 (Mi 26 Jän 2022 09:49:49) ==> Retrieving sources... -> Downloading libpamac-11.1.0.tar.bz2... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 150k 100 150k 0 0 384k 0 --:--:-- --:--:-- --:--:-- 384k ==> Validating source files with sha256sums... pamac-10.2.0.tar.gz ... Passed 100 389k 100 389k 0 0 473k 0 --:--:-- --:--:-- --:--:-- 473k ==> Validating source files with sha256sums... libpamac-11.1.0.tar.bz2 ... Passed ==> Making package: libpamac-flatpak 11.1.0-1 (Mi 26 Jän 2022 09:49:52) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found libpamac-11.1.0.tar.bz2 ==> Validating source files with sha256sums... libpamac-11.1.0.tar.bz2 ... Passed ==> Removing existing $srcdir/ directory... ==> Extracting sources... -> Extracting libpamac-11.1.0.tar.bz2 with bsdtar ==> Sources are ready. ==> Making package: libpamac-flatpak 11.1.0-1 (Mi 26 Jän 2022 09:49:57) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> WARNING: Using existing $srcdir/ tree ==> Starting build()... The Meson build system Version: 0.61.1 Source dir: /home/home/.cache/yay/libpamac-flatpak/src/libpamac-11.1.0 Build dir: /home/home/.cache/yay/libpamac-flatpak/src/libpamac-11.1.0/builddir Build type: native build Project name: libpamac Project version: 11.1 C compiler for the host machine: cc (gcc 11.1.0 "cc (GCC) 11.1.0") C linker for the host machine: cc ld.bfd 2.36.1 Vala compiler for the host machine: valac (valac 0.54.6) Host machine cpu family: x86_64 Host machine cpu: x86_64 Found pkg-config: /usr/bin/pkg-config (1.8.0) Run-time dependency gobject-2.0 found: YES 2.70.2 Run-time dependency gio-2.0 found: YES 2.70.2 Run-time dependency gthread-2.0 found: YES 2.70.2 Run-time dependency libalpm found: YES 13.0.1 Run-time dependency json-glib-1.0 found: YES 1.6.6 Run-time dependency libsoup-2.4 found: YES 2.74.2 Run-time dependency polkit-gobject-1 found: YES 0.120 Run-time dependency appstream-glib found: YES 0.7.18 Run-time dependency gmodule-2.0 found: YES 2.70.2 Library posix found: YES Library m found: YES Run-time dependency flatpak found: YES 1.12.4 Program g-ir-compiler found: YES (/usr/bin/g-ir-compiler) WARNING: You should add the boolean check kwarg to the run_command call. It currently defaults to false, but it will default to true in future releases of meson. See also: https://github.com/mesonbuild/meson/issues/9300 Configuring org.manjaro.pamac.daemon.service using configuration Configuring pamac-daemon.service using configuration Configuring pamac-cleancache.service using configuration Program pacman-mirrors found: NO Build targets in project: 101
libpamac 11.1
User defined options buildtype : release prefix : /usr sysconfdir : /etc enable-flatpak: true
Found ninja-1.10.2 at /usr/bin/ninja [69/139] Compiling Vala source ../src/alpm_config.vala ../src/dependency_checker.vala ../src/alpm_config.vala:354.2-354.18: warning: Method `AlpmConfig.write' never used public void write (HashTable<string,Variant> new_conf) { ^^^^^^^^^^^^^^^^^ Compilation succeeded - 1 warning(s) [73/139] Compiling Vala source ../src/alpm_config.vala ../src/outdated_checker.vala ../src/alpm_config.vala:354.2-354.18: warning: Method `AlpmConfig.write' never used public void write (HashTable<string,Variant> new_conf) { ^^^^^^^^^^^^^^^^^ Compilation succeeded - 1 warning(s) [83/139] Compiling Vala source ../src/flatpak_interface.vala ../src/flatpak_plugin.vala ../src/package.vala ../src/flatpak_interface.vala:29.3-29.45: warning: Method `Pamac.FlatpakPlugin.refresh_appstream_data' never used public abstract bool refresh_appstream_data (); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/flatpak_interface.vala:30.3-30.42: warning: Method `Pamac.FlatpakPlugin.load_appstream_data' never used public abstract void load_appstream_data (); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/flatpak_interface.vala:31.3-31.40: warning: Method `Pamac.FlatpakPlugin.get_remotes_names' never used public abstract void get_remotes_names (ref GenericArray<unowned string> remotes_names); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/flatpak_interface.vala:32.3-32.38: warning: Method `Pamac.FlatpakPlugin.search_flatpaks' never used public abstract void search_flatpaks (string search_string, ref GenericArray<unowned FlatpakPackage> pkgs); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/flatpak_interface.vala:33.3-33.55: warning: Method `Pamac.FlatpakPlugin.search_uninstalled_flatpaks_sync' never used public abstract void search_uninstalled_flatpaks_sync (string[] search_terms, ref GenericArray<unowned FlatpakPackage> pkgs); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/flatpak_interface.vala:34.3-34.43: warning: Method `Pamac.FlatpakPlugin.is_installed_flatpak' never used public abstract bool is_installed_flatpak (string name); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/flatpak_interface.vala:35.3-35.63: warning: Method `Pamac.FlatpakPlugin.get_flatpak_by_app_id' never used public abstract unowned FlatpakPackage? get_flatpak_by_app_id (string app_id); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/flatpak_interface.vala:36.3-36.53: warning: Method `Pamac.FlatpakPlugin.get_flatpak' never used public abstract unowned FlatpakPackage? get_flatpak (string id); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/flatpak_interface.vala:37.3-37.45: warning: Method `Pamac.FlatpakPlugin.get_installed_flatpaks' never used public abstract void get_installed_flatpaks (ref GenericArray<unowned FlatpakPackage> pkgs); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/flatpak_interface.vala:38.3-38.44: warning: Method `Pamac.FlatpakPlugin.get_category_flatpaks' never used public abstract void get_category_flatpaks (string category, ref GenericArray<unowned FlatpakPackage> pkgs); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/flatpak_interface.vala:39.3-39.42: warning: Method `Pamac.FlatpakPlugin.get_flatpak_updates' never used public abstract void get_flatpak_updates (ref GenericArray<FlatpakPackage> pkgs); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/flatpak_interface.vala:40.3-40.32: warning: Method `Pamac.FlatpakPlugin.trans_run' never used public abstract bool trans_run (string sender, string[] to_install, string[] to_remove, string[] to_upgrade); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/flatpak_interface.vala:41.3-41.35: warning: Method `Pamac.FlatpakPlugin.trans_cancel' never used public abstract void trans_cancel (string sender); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/flatpak_interface.vala:42.3-42.30: warning: Method `Pamac.FlatpakPlugin.refresh' never used public abstract void refresh (); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Compilation succeeded - 14 warning(s) [105/139] Compiling Vala source ../src/version.vala ../src/package.vala ../src/alpm_pa...der.vala ../src/database.vala ../src/snap_interface.vala ../src/flatpak_interface.vala ../src/alpm_utils.vala:908.3-908.33: warning: Method `Pamac.AlpmUtils.trans_check_prepare' never used public bool trans_check_prepare (bool sysupgrade, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/database.vala:423.3-423.67: warning: Method `Pamac.Database.get_uninstalled_optdeps_async' never used internal async GenericArray<string> get_uninstalled_optdeps_async (string pkgname) { ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/database.vala:2557.3-2557.46: warning: Method `Pamac.Database.get_aur_updates_async' never used internal async Updates get_aur_updates_async (GenericSet<string?> ignorepkgs) { ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/snap_interface.vala:31.3-31.52: warning: Method `Pamac.SnapPlugin.search_uninstalled_snaps_sync' never used public abstract void search_uninstalled_snaps_sync (string search_string, ref GenericArray<unowned SnapPackage> pkgs); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/flatpak_interface.vala:33.3-33.55: warning: Method `Pamac.FlatpakPlugin.search_uninstalled_flatpaks_sync' never used public abstract void search_uninstalled_flatpaks_sync (string[] search_terms, ref GenericArray<unowned FlatpakPackage> pkgs); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Compilation succeeded - 5 warning(s) [110/139] Compiling Vala source ../src/package.vala ../src/alpm_package.vala ../src/pl...a ../src/snap_interface.vala ../src/flatpak_interface.vala ../src/updates_checker.vala ../src/alpm_config.vala:354.2-354.18: warning: Method `AlpmConfig.write' never used public void write (HashTable<string,Variant> new_conf) { ^^^^^^^^^^^^^^^^^ ../src/snap_interface.vala:31.3-31.52: warning: Method `Pamac.SnapPlugin.search_uninstalled_snaps_sync' never used public abstract void search_uninstalled_snaps_sync (string search_string, ref GenericArray<unowned SnapPackage> pkgs); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/snap_interface.vala:38.3-38.32: warning: Method `Pamac.SnapPlugin.trans_run' never used public abstract bool trans_run (string sender, string[] to_install, string[] to_remove); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/snap_interface.vala:39.3-39.37: warning: Method `Pamac.SnapPlugin.switch_channel' never used public abstract bool switch_channel (string sender, string name, string channel); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/snap_interface.vala:40.3-40.35: warning: Method `Pamac.SnapPlugin.trans_cancel' never used public abstract void trans_cancel (string sender); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/flatpak_interface.vala:33.3-33.55: warning: Method `Pamac.FlatpakPlugin.search_uninstalled_flatpaks_sync' never used public abstract void search_uninstalled_flatpaks_sync (string[] search_terms, ref GenericArray<unowned FlatpakPackage> pkgs); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/flatpak_interface.vala:40.3-40.32: warning: Method `Pamac.FlatpakPlugin.trans_run' never used public abstract bool trans_run (string sender, string[] to_install, string[] to_remove, string[] to_upgrade); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ../src/flatpak_interface.vala:41.3-41.35: warning: Method `Pamac.FlatpakPlugin.trans_cancel' never used public abstract void trans_cancel (string sender); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Compilation succeeded - 8 warning(s) [139/139] Generating src/pamac typelib with a custom command ==> Entering fakeroot environment... ==> Starting package()... [0/1] Installing files. Installing src/libpamac-flatpak.so.11.1 to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/lib Installing symlink pointing to libpamac-flatpak.so.11.1 to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/lib/libpamac-flatpak.so.11 Installing symlink pointing to libpamac-flatpak.so.11 to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/lib/libpamac-flatpak.so Installing src/pamac-flatpak.h to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/include Installing src/pamac-flatpak.vapi to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/vala/vapi Installing src/libpamac.so.11.1 to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/lib Installing symlink pointing to libpamac.so.11.1 to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/lib/libpamac.so.11 Installing symlink pointing to libpamac.so.11 to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/lib/libpamac.so Installing src/pamac.h to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/include Installing src/pamac.vapi to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/vala/vapi Installing src/Pamac-11.gir to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/gir-1.0 Installing src/Pamac-11.typelib to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/lib/girepository-1.0 Installing src/pamac-daemon to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/bin Installing src/dependency-checker to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/bin Installing src/outdated-checker to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/bin Installing po/af/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/af/LC_MESSAGES Installing po/ar/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/ar/LC_MESSAGES Installing po/ast/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/ast/LC_MESSAGES Installing po/az/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/az/LC_MESSAGES Installing po/az_AZ/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/az_AZ/LC_MESSAGES Installing po/be/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/be/LC_MESSAGES Installing po/bg/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/bg/LC_MESSAGES Installing po/bn/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/bn/LC_MESSAGES Installing po/bs/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/bs/LC_MESSAGES Installing po/ca/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/ca/LC_MESSAGES Installing po/ca@valencia/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/ca@valencia/LC_MESSAGES Installing po/cs/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/cs/LC_MESSAGES Installing po/cy/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/cy/LC_MESSAGES Installing po/da/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/da/LC_MESSAGES Installing po/de/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/de/LC_MESSAGES Installing po/de_CH/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/de_CH/LC_MESSAGES Installing po/de_DE/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/de_DE/LC_MESSAGES Installing po/el/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/el/LC_MESSAGES Installing po/el_GR/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/el_GR/LC_MESSAGES Installing po/en_GB/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/en_GB/LC_MESSAGES Installing po/eo/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/eo/LC_MESSAGES Installing po/es/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/es/LC_MESSAGES Installing po/es_419/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/es_419/LC_MESSAGES Installing po/es_AR/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/es_AR/LC_MESSAGES Installing po/es_ES/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/es_ES/LC_MESSAGES Installing po/es_MX/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/es_MX/LC_MESSAGES Installing po/es_SV/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/es_SV/LC_MESSAGES Installing po/et/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/et/LC_MESSAGES Installing po/eu/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/eu/LC_MESSAGES Installing po/fa/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/fa/LC_MESSAGES Installing po/fa_IR/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/fa_IR/LC_MESSAGES Installing po/fi/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/fi/LC_MESSAGES Installing po/fo/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/fo/LC_MESSAGES Installing po/fr/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/fr/LC_MESSAGES Installing po/gl/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/gl/LC_MESSAGES Installing po/gl_ES/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/gl_ES/LC_MESSAGES Installing po/gug_PY/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/gug_PY/LC_MESSAGES Installing po/he/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/he/LC_MESSAGES Installing po/he_IL/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/he_IL/LC_MESSAGES Installing po/hi/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/hi/LC_MESSAGES Installing po/hi_IN/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/hi_IN/LC_MESSAGES Installing po/hr/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/hr/LC_MESSAGES Installing po/hr_HR/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/hr_HR/LC_MESSAGES Installing po/hu/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/hu/LC_MESSAGES Installing po/id/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/id/LC_MESSAGES Installing po/ie/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/ie/LC_MESSAGES Installing po/is/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/is/LC_MESSAGES Installing po/is_IS/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/is_IS/LC_MESSAGES Installing po/it/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/it/LC_MESSAGES Installing po/ja/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/ja/LC_MESSAGES Installing po/ka/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/ka/LC_MESSAGES Installing po/kab/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/kab/LC_MESSAGES Installing po/kk/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/kk/LC_MESSAGES Installing po/ko/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/ko/LC_MESSAGES Installing po/lt/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/lt/LC_MESSAGES Installing po/ml/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/ml/LC_MESSAGES Installing po/ms/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/ms/LC_MESSAGES Installing po/nb/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/nb/LC_MESSAGES Installing po/ne/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/ne/LC_MESSAGES Installing po/nl/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/nl/LC_MESSAGES Installing po/nl_BE/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/nl_BE/LC_MESSAGES Installing po/nl_NL/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/nl_NL/LC_MESSAGES Installing po/nn/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/nn/LC_MESSAGES Installing po/or/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/or/LC_MESSAGES Installing po/pl/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/pl/LC_MESSAGES Installing po/pt/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/pt/LC_MESSAGES Installing po/pt_BR/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/pt_BR/LC_MESSAGES Installing po/pt_PT/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/pt_PT/LC_MESSAGES Installing po/ro/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/ro/LC_MESSAGES Installing po/ru/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/ru/LC_MESSAGES Installing po/si/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/si/LC_MESSAGES Installing po/sk/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/sk/LC_MESSAGES Installing po/sl/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/sl/LC_MESSAGES Installing po/sl_SI/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/sl_SI/LC_MESSAGES Installing po/sq/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/sq/LC_MESSAGES Installing po/sq_AL/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/sq_AL/LC_MESSAGES Installing po/sr/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/sr/LC_MESSAGES Installing po/sr@latin/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/sr@latin/LC_MESSAGES Installing po/sr_RS/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/sr_RS/LC_MESSAGES Installing po/sr_RS@latin/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/sr_RS@latin/LC_MESSAGES Installing po/sv/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/sv/LC_MESSAGES Installing po/sw/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/sw/LC_MESSAGES Installing po/ta/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/ta/LC_MESSAGES Installing po/tr/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/tr/LC_MESSAGES Installing po/uk/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/uk/LC_MESSAGES Installing po/ur_PK/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/ur_PK/LC_MESSAGES Installing po/uz/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/uz/LC_MESSAGES Installing po/vi/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/vi/LC_MESSAGES Installing po/zh/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/zh/LC_MESSAGES Installing po/zh_CN/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/zh_CN/LC_MESSAGES Installing po/zh_TW/LC_MESSAGES/pamac.mo to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/locale/zh_TW/LC_MESSAGES Installing data/polkit/org.manjaro.pamac.policy to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/polkit-1/actions Installing /home/home/.cache/yay/libpamac-flatpak/src/libpamac-11.1.0/builddir/meson-private/pamac.pc to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/lib/pkgconfig Installing /home/home/.cache/yay/libpamac-flatpak/src/libpamac-11.1.0/data/config/pamac.conf to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/etc Installing /home/home/.cache/yay/libpamac-flatpak/src/libpamac-11.1.0/builddir/data/dbus/org.manjaro.pamac.daemon.service to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/dbus-1/system-services Installing /home/home/.cache/yay/libpamac-flatpak/src/libpamac-11.1.0/data/dbus/org.manjaro.pamac.daemon.conf to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/etc/dbus-1/system.d Installing /home/home/.cache/yay/libpamac-flatpak/src/libpamac-11.1.0/data/mime/x-alpm-package.xml to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/share/mime/packages Installing /home/home/.cache/yay/libpamac-flatpak/src/libpamac-11.1.0/builddir/data/systemd/pamac-daemon.service to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/lib/systemd/system Installing /home/home/.cache/yay/libpamac-flatpak/src/libpamac-11.1.0/builddir/data/systemd/pamac-cleancache.service to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/lib/systemd/system Installing /home/home/.cache/yay/libpamac-flatpak/src/libpamac-11.1.0/data/systemd/pamac-cleancache.timer to /home/home/.cache/yay/libpamac-flatpak/pkg/libpamac-flatpak/usr/lib/systemd/system ==> Tidying install... -> Removing empty directories... -> Removing libtool files... -> Purging unwanted files... -> Removing static library files... -> Stripping unneeded symbols from binaries and libraries... -> Compressing man and info pages... ==> Checking for packaging issues... ==> Creating package "libpamac-flatpak"... -> Generating .PKGINFO file... -> Generating .BUILDINFO file... -> Generating .MTREE file... -> Compressing package... ==> Leaving fakeroot environment. ==> Finished making: libpamac-flatpak 11.1.0-1 (Mi 26 Jän 2022 09:50:07) ==> Cleaning up... -> libpamac-flatpak not satisfied, flushing install queue loading packages... resolving dependencies... looking for conflicting packages... :: libpamac-flatpak and libpamac are in conflict. Remove libpamac? [y/N] y error: failed to prepare transaction (could not satisfy dependencies) :: removing libpamac breaks dependency 'libpamac>=11.1' required by pamac-cli :: removing libpamac breaks dependency 'libpamac<11.2' required by pamac-cli :: removing libpamac breaks dependency 'libpamac>=11.1' required by pamac-gtk :: removing libpamac breaks dependency 'libpamac<11.2' required by pamac-gtk -> exit status 1
How do I resolve the last error messages in the console?
Title: Re: Flatpak extension in Pamac possible
Post by: conky60 on 26 January 2022, 13:02:22
You cannot install multiple versions of pamac. Install pamac-flatpak > answer yes to the questions pacman is asking and it will install the package you want > pamac-flatpak.
Best regards.
Title: Re: Flatpak extension in Pamac possible
Post by: Rainbow Sun on 26 January 2022, 13:43:18
Okay, i uninstalled Pamac and install only Pamac-flatpak with yay in the consol. I get a SystemD error, but its a Runit Init.
User:[root]:/home/home# yay -Syu pamac-flatpak -> Avoid running yay as root/sudo. :: Synchronizing package databases... system is up to date world is up to date galaxy is up to date lib32 is up to date universe is up to date omniverse is up to date extra is up to date community is up to date multilib is up to date :: Starting full system upgrade... warning: python-packaging: local (21.0-1) is newer than world (20.9-7) there is nothing to do :: Searching databases for updates... :: Searching AUR for updates... -> python-packaging: local (21.0-1) is newer than world (20.9-7) -> Flagged Out Of Date AUR Packages: jdownloader2 :: 1 Packages to upgrade. 1 aur/jack 0.125.0-9 -> 0.126.0-3 ==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name) ==> 1 :: Checking for conflicts... :: Checking for inner conflicts... [Aur:2] libpamac-flatpak-11.1.0-1 pamac-flatpak-10.2.0-1
:: (0/2) Downloaded PKGBUILD: pamac-flatpak :: (0/2) Downloaded PKGBUILD: libpamac-flatpak -> error fetching pamac-flatpak: context: exec: "systemd-run": executable file not found in $PATH
error fetching libpamac-flatpak: context: exec: "systemd-run": executable file not found in $PATH
Title: Re: Flatpak extension in Pamac possible
Post by: strajder on 26 January 2022, 13:49:30
pamac and flatpak are not needed at all. pacman with Artix repositories is sufficient to run Artix.
AUR is user-generated and not officially supported by Arch nor Artix.
flatpak and snap are what's wrong with today's GNU/Linux along with systemd.
Title: Re: Flatpak extension in Pamac possible
Post by: Rainbow Sun on 26 January 2022, 14:03:02
Okay, I need flatpak only for the user interface of Spotify and apparently also for the Nvidia driver. I thought I had installed the nvidia driver via pacmac. Do you have the command for the graphical user interface of Spotify. I see in the list other entries that have to do with downloading.
Title: Re: Flatpak extension in Pamac possible
Post by: strajder on 26 January 2022, 14:10:34
I don't use Spotify, as it is a proprietary service. I prefer my music offline. That said, Artix includes spotify daemon:
$ pacman -Ss spotify galaxy/spotifyd 0.3.3-1 Lightweight spotify streaming daemon with spotify connect support galaxy/spotifyd-dinit 20211102-2 (dinit-galaxy) dinit service scripts for spotifyd galaxy/spotifyd-openrc 20210505-1 (openrc-galaxy) OpenRC script for spotifyd galaxy/spotifyd-runit 20210407-2 (runit-galaxy) Runit service script for spotifyd galaxy/spotifyd-s6 20210919-1 (s6-galaxy) s6-rc service scripts for spotifyd galaxy/spotifyd-suite66 20210705-1 (suite66-galaxy) 66 script for spotifyd
This is its upstream URL: https://github.com/Spotifyd/spotifyd
Title: Re: Flatpak extension in Pamac possible
Post by: Rainbow Sun on 26 January 2022, 20:40:30
What are spotify daemon? I installed galaxy/spotifyd 0.3.3-1 and galaxy/spotifyd-runit 20210407-2 and i see no entries in start menu and can't start with the consol command. Daemons are just downloaders or taskbar popup views for the installed application, right? I have no idea how an upstream Spotify URL works.
Although I don't know much about Linux, my feeling says that something is wrong with SystemD. Your info that Flatpak also belongs to SystemD I did not know. Snap can be completely forgotten. If Flatpak and Snap are wrong in our GNU time, is an appimage better? Appimage is the parallel world to Windows Portable on the Linux world. correct?
Title: Re: Flatpak extension in Pamac possible
Post by: strajder on 26 January 2022, 20:47:13
daemons (https://wiki.archlinux.org/title/Daemons), or (very roughly said) services, must be activated and started to work. The exact procedure depends on your init.
For runit, see: https://wiki.artixlinux.org/Main/Runit
You will also have to configure spotifyd for your account. How to do that may also depend on your init.
Edit: Looking at spotifyd wiki, it has a configuration file /etc/spotifyd.conf: https://spotifyd.github.io/spotifyd/config/File.html
Help for CLI: https://spotifyd.github.io/spotifyd/config/Cli.html
Title: Re: Flatpak extension in Pamac possible
Post by: Rainbow Sun on 26 January 2022, 21:27:11
Quote
A daemon is a program that runs as a "background" process (without a terminal or user interface), commonly waiting for events to occur and offering services.
A Daemon background process are nothing for me. I want a graphical user interface of Spotify. Looks like I need flatpak.
Title: Re: Flatpak extension in Pamac possible
Post by: strajder on 27 January 2022, 09:51:51
A Daemon background process are nothing for me. I want a graphical user interface of Spotify. Looks like I need flatpak.
This particular daemon also doubles as a CLI to its another running instance. It is also fully functional.
There are spotify-related packages in AUR (https://aur.archlinux.org/packages/?O=0&K=spotify), but like I said above, those are user-produced and Artix has nothing to do with them. There are no guarantees nor support provided by Artix team about them. For any support or questions about those packages, refer to their pages on https://aur.archlinux.org/ instead.
Title: Re: Flatpak extension in Pamac possible
Post by: just on 27 January 2022, 13:00:45
A Daemon background process are nothing for me. I want a graphical user interface of Spotify. Looks like I need flatpak.
You should decide what do you want to do: - to run spotify in its flatpak version - to install pamac with flatpak support included
Judging from your screenshot (https://forum.artixlinux.org/index.php/topic,3579.msg23170.html#msg23170), you already have flatpak installed.
pamac, with or without flatpak support, is not needed at all to install and to run flatpak's version of spotify. Both actions are performed with native flatpak CLI commands.
flatpak doesn't add Spotify menu entry, and doesn't create any graphical element to start it up. If you want to see Spotify entry in GUI, you should create by hand a .desktop file, a script, a menu entry, a button, an icon, whatever you want with "flatpak run com.spotify.Client" command assigned to it.
On the other hand, if you want to have pamac with flatpak support, then:
1. Uninstall pamac-gtk with all its dependencies 2. Install any of: - aur/pamac-nosnap (https://aur.archlinux.org/packages/pamac-nosnap/) - aur/pamac-all (https://aur.archlinux.org/packages/pamac-all/) - aur/pamac-all-git (https://aur.archlinux.org/packages/pamac-all-git/) - aur/pamac-flatpak (https://aur.archlinux.org/packages/pamac-flatpak/) (outdated) Done.
Some of listed packages either won't install or won't work. Read comments by following the links.
Use AUR your own risk. No distribution provides a support for AUR packages.
Title: Re: Flatpak extension in Pamac possible
Post by: Rainbow Sun on 28 January 2022, 00:20:44
Installing Flatpak via the console I found out myself on the Flathub website and did it. It's not a secret. https://flatpak.org/setup/Arch https://www.flathub.org/apps/details/com.spotify.Client In this thread I asked how to get Flatpak with Pamac. The answer was. To get Flatpak in Pamac, you need an AUR helper (yaourt(ix) or yay). I chose yay because the 3 letters are easy to remember as a newbie. Now I installed yay via the pacman console and uninstalled the pamac I had preinstalled. On the Arch Aur website I first went for pamac-all 10.3.0-2 https://aur.archlinux.org/packages/pamac-all/ and today tried to install pamac-nosnap 10.3.0-2 https://aur.archlinux.org/packages/pamac-nosnap/ unsuccessfully with yay. Unfortunately I still get the error message that I can not fix. Spoiler (click to show/hide)
error fetching pamac-nosnap: context: exec: "systemd-run": executable file not found in $PATH
Of course I would like to have flatpak in pamac for later software that cannot be found in pacman. In Pamac GUI you can find more clearly the software you want and feels more comfortable as a beginner. Especially for users who do not know how to use the terminal or do not know the terminal language, e.g. my parents. I'm going to switch to Artix Xfce and try my luck again. Personally I find KDE a bit too cluttered and overloaded with features and uses for my taste too small visual icon buttons without text as settings that are well hidden. In neofetch it also needs 5Gb RAM and it feels slow too, although only my browser is active. Booting also takes a bit longer for me than I'm used to. Nice Fortunately, the Artix installation is ready in 10 minutes.
Of course I would like to have flatpak in pamac for later software that cannot be found in pacman. In Pamac GUI you can find more clearly the software you want and feels more comfortable as a beginner. Especially for users who do not know how to use the terminal or do not know the terminal language, e.g. my parents.
Kein Kommentar.
Title: Re: Flatpak extension in Pamac possible
Post by: just on 28 January 2022, 08:18:10
@Rainbow Sun pamac-gtk, pamac-all, pamac-all-git, pamac-nosnap, pamac-flatpak are all full, self-sufficient and mutualy exclusive packages. A package named "pamac" doesn't exist. There're no plugins or extensions for any of these "pamacs". pamac-flatpak is not an extension for pamac-gtk.
Only one package at a time may be installed. To install any pamac, a previous installation, if any, must be removed first. yay is very suitable for such remove-install operations.
I've added a warning (https://forum.artixlinux.org/index.php/topic,3579.msg23121.html#msg23121) to never run yay as root. Judging from your output (https://forum.artixlinux.org/index.php/topic,3579.msg23257.html#msg23257) - now removed with the edit, - it was ignored. Again: never run yay as root. Always run yay as a regular user.
I never use pamac, flatpaks, snaps, spotify, and don't have much experience with any of them. They were installed solely to illustrate the answer.
Can't reproduce here the errors you encounter. I installed pamac-nosnap without an issue with the command:
This is the result of installed pamac-nosnap interrogation. Note that -Q pacman's command queries only installed pkgs, i.e. pkgs on a user's computer. It doesn't look for anything in repos or elsewhere:
$ dt && pacman -Qii pamac-nosnap Current datetime: 2022-01-28 07:33:51
Name : pamac-nosnap Version : 10.3.0-2 Description : A Gtk3 frontend for libalpm (with AUR, flatpak, appindicator) Architecture : x86_64 URL : https://gitlab.manjaro.org/applications/pamac Licenses : GPL3 Groups : None Provides : pamac Depends On : libnotify libpamac-nosnap libhandy Optional Deps : polkit-gnome: needed for authentification in Cinnamon, Gnome [installed] Required By : None Optional For : None Conflicts With : pamac pamac-all pamac-gtk pamac-cli pamac-common pamac-aur pamac-aur-git pamac-flatpak pamac-flatpak-gnome Replaces : None Installed Size : 761.08 KiB Packager : Unknown Packager Build Date : Fri Jan 28 07:32:44 2022 Install Date : Fri Jan 28 07:33:03 2022 Install Reason : Explicitly installed Install Script : Yes Validated By : None Backup Files : (none)
$
"Install Reason : Explicitly installed" means that pamac-nosnap was manually installed by user (me).
Installed pamac-nosnap is shown as Add/Remove Software in menu. By default, AUR and Flatpak support are disabled in Pamac GUI. Lets enable them; close and open Pamac GUI again for changes to take in effect: (https://i.imgur.com/phlNpD9.png)
Now that Flatpak support is enabled in Pamac GUI, it is possible to search for and install flatpak stuff. For example, Spotify: (https://i.imgur.com/5ypZwIp.png)
To comfortably open Spotify from menu, I created a menu entry for it. This is Cinnamon. As already said (https://forum.artixlinux.org/index.php/topic,3579.msg23230.html#msg23230), the command assigned to Spotiry entry is:
Spotify window opens. As I never used Spotify in my life, I don't have Spotify account, and will never create it: (https://i.imgur.com/vMnrOSB.png)
Honestly, don't know what else can be added here. Everything is said and explained. A good will and dedication should be exercized to learn Artix (or Arch).
Edit: As said, I don't have any experience with pamac. Just found that Pamac automagically creates menu entries for software, installed from it. So I have two Spotify entries in Cinnamon menu now. One is created by Pamac and another is created by me. Ergo, when Spotify is installed from Pamac, there's no need to create a menu entry for it by hand. (https://i.imgur.com/d9yt3J5.png) Pamac creates more articulated command to launch Spotify from menu:
Of course I would like to have flatpak in pamac for later software that cannot be found in pacman. In Pamac GUI you can find more clearly the software you want and feels more comfortable as a beginner. Especially for users who do not know how to use the terminal or do not know the terminal language, e.g. my parents.
Package management is administration and is not a trivial task. Newbies should leave it to more skilled users, or learn it themselves.
Using GNU/Linux requires knowledge of "terminal", be it the one who's using it, or his more knowledgeable friend. It is just a question of "when" you will need it, not "if".
Title: Re: Flatpak extension in Pamac possible
Post by: Rainbow Sun on 28 January 2022, 14:12:24
The picture looks interesting. Is there more than pamac and Octopi?
As I said, I have now installed the xfce version. I have no idea why exactly this worked now with xfce. Probably my KDE desktop was broken. Now I have installed it correctly. At that time, about 6 months ago, I had installed pamac and then post-install the plugin. Now I tried to install the pamac-all 10.3.0-2 first with yay and got an error message. After that it worked with pamac-nosnap 10.3.0-2 to install the package. Yes, that you should not start yay with root rights was clear to me. But at that moment I already knew that I will reinstall my distro, because I had the feeling that kde was broken. Now I have learned here again a lot which I did not know before. Thanks to all who helped.
@Rainbow Sun pamac-gtk, pamac-all, pamac-all-git, pamac-nosnap, pamac-flatpak are all full, self-sufficient and mutualy exclusive packages. A package named "pamac" doesn't exist. There're no plugins or extensions for any of these "pamacs". pamac-flatpak is not an extension for pamac-gtk.
Only one package at a time may be installed. To install any pamac, a previous installation, if any, must be removed first. yay is very suitable for such remove-install operations.
I've added a warning (https://forum.artixlinux.org/index.php/topic,3579.msg23121.html#msg23121) to never run yay as root. Judging from your output (https://forum.artixlinux.org/index.php/topic,3579.msg23257.html#msg23257) - now removed with the edit, - it was ignored. Again: never run yay as root. Always run yay as a regular user.
I never use pamac, flatpaks, snaps, spotify, and don't have much experience with any of them. They were installed solely to illustrate the answer.
Can't reproduce here the errors you encounter. I installed pamac-nosnap without an issue with the command:
This is the result of installed pamac-nosnap interrogation. Note that -Q pacman's command queries only installed pkgs, i.e. pkgs on a user's computer. It doesn't look for anything in repos or elsewhere:
$ dt && pacman -Qii pamac-nosnap Current datetime: 2022-01-28 07:33:51
Name : pamac-nosnap Version : 10.3.0-2 Description : A Gtk3 frontend for libalpm (with AUR, flatpak, appindicator) Architecture : x86_64 URL : https://gitlab.manjaro.org/applications/pamac Licenses : GPL3 Groups : None Provides : pamac Depends On : libnotify libpamac-nosnap libhandy Optional Deps : polkit-gnome: needed for authentification in Cinnamon, Gnome [installed] Required By : None Optional For : None Conflicts With : pamac pamac-all pamac-gtk pamac-cli pamac-common pamac-aur pamac-aur-git pamac-flatpak pamac-flatpak-gnome Replaces : None Installed Size : 761.08 KiB Packager : Unknown Packager Build Date : Fri Jan 28 07:32:44 2022 Install Date : Fri Jan 28 07:33:03 2022 Install Reason : Explicitly installed Install Script : Yes Validated By : None Backup Files : (none)
$
"Install Reason : Explicitly installed" means that pamac-nosnap was manually installed by user (me).
Installed pamac-nosnap is shown as Add/Remove Software in menu. By default, AUR and Flatpak support are disabled in Pamac GUI. Lets enable them; close and open Pamac GUI again for changes to take in effect: (https://i.imgur.com/phlNpD9.png)
Now that Flatpak support is enabled in Pamac GUI, it is possible to search for and install flatpak stuff. For example, Spotify: (https://i.imgur.com/5ypZwIp.png)
To comfortably open Spotify from menu, I created a menu entry for it. This is Cinnamon. As already said (https://forum.artixlinux.org/index.php/topic,3579.msg23230.html#msg23230), the command assigned to Spotiry entry is:
Spotify window opens. As I never used Spotify in my life, I don't have Spotify account, and will never create it: (https://i.imgur.com/vMnrOSB.png)
Honestly, don't know what else can be added here. Everything is said and explained. A good will and dedication should be exercized to learn Artix (or Arch).
Edit: As said, I don't have any experience with pamac. Just found that Pamac automagically creates menu entries for software, installed from it. So I have two Spotify entries in Cinnamon menu now. One is created by Pamac and another is created by me. Ergo, when Spotify is installed from Pamac, there's no need to create a menu entry for it by hand. (https://i.imgur.com/d9yt3J5.png) Pamac creates more articulated command to launch Spotify from menu:
/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=spotify --file-forwarding com.spotify.Client @@u %U @@
@just, this has to be THE most comprehensive and easily understood answer to a question I may have ever read on a forum in a long time. Certainly as far from RTFM as one could ever expect.
Best regards.
Title: Re: Flatpak extension in Pamac possible
Post by: just on 29 January 2022, 14:13:12