Skip to main content
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: Paru not working (Read 4033 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Paru not working

Reply #15
@tony26102 , I use AUR myself. In fact, some drivers for my old laptop are only available in AUR. I use yay & makepkg to install AUR packages. Sure, yay and other alike helpers broke from time to time (the latest is due to interface change from AUR server side), but they got fixed pretty quickly. AUR is not a problem, some users of AUR are the problems. For example, excessively abusing AUR server by sending a request over each key strike and/or frequent query for updates, etc. AUR is a user repository, which means packages inside are NOT tested and certified by the Arch dev team. Packages are there for grab. It's uers' responsibility to carefully review & assert the usability of software posted there. So I think a disclaim like "AUR is not supported" from a distro is understandable. From my experience, if a package from either AUR or github is not functioning as advertised, file an issue report directly to the maintainer is more efficient than on a distro's forum.

Good luck & happy using Arch/Artix.

Re: Paru not working

Reply #16
Apparently, we should not use AUR, ok!
This is the wrong conclusion.

By all means, use AUR, but, as I said earlier, don't expect support for it from Arch or Artix team. Instead, ask for support from the maintainers of a specific AUR package.

Also, understand that using AUR is the user's responsibility. If the user doesn't read PKGBUILDs, then the user has no right to complain when something goes wrong.

Re: Paru not working

Reply #17
This is the wrong conclusion.

By all means, use AUR, but, as I said earlier, don't expect support for it from Arch or Artix team. Instead, ask for support from the maintainers of a specific AUR package.

Also, understand that using AUR is the user's responsibility. If the user doesn't read PKGBUILDs, then the user has no right to complain when something goes wrong.
Well, i don't understand and never read a PKGBUILDs.
Apparently the errors and hint are on all side, a normal user have no chance to make things right and the most user are not able and willing to spend time only to maintain OS running.

The people, you call 'user', must be expert and have many time to understand and apply the steps as you require.

You only try to elevate yourself above others and expect admiration, presenting a solution is not your intention or willingness, this is now to much of bad things. You don't know the meaning of life, and this contains only one simple rule.

I download paru from github and install it with makepkg -si, which topics from pkgbuild are to be observed?

Your arguments are unsustainable and i bet, yourself read almost never a  pkgbuild or only if something goes wrong, otherwise you should tell us now how many Artix users read a pkgbuild.

I ask for help or for knowledge transfer to understand where is the problem and tell you just in previous post that i cannot understand the maintainer and you repeat the same useless nonsense, are you sure you are a human?

Fact is: We cannot choose to use the AUR or not, we have to use it (see list below) and you, from whatever principles, get entangled in absurd excuses.
Do you want or can not help, then do not answer and do not try to convince me of your propagated nonsense.

Code: [Select]
pacman -Qm
auto-auto-complete 7.2-1
brother-hl3152cdw 1.1.4-4
c++utilities 5.13.0-1
ckb-next-git 1:0.4.4.r117.gd1183f27-1
crow-translate 2.9.1-2
cups-nosystemd 1:2.3.3op2-2
cups-ocr 0.1.2-4
downgrade 11.0.0-1
fakepkg 1.42.0-1
gconf 3.2.6+11+g07808097-10
kotatogram-desktop 1.4.8-2
kross-interpreters 21.08.3-1
libpamac-aur 11.2.0-7
masterpdfeditor-free 4.3.89-1
pamac-aur 10.3.0-5
paru 1.9.3-1
pocketsphinx 5prealpha-13
qtutilities 6.5.3-1
sphinxbase 5prealpha-13
subtitlecomposer 0.7.1-3
ttf-ms-fonts 2.0-12
yandex-browser-beta 22.1.3.856_1-1
Not all these packages are installed intentionally

I had no intention to blame someone but you force me to, than tell me why by automatic update of `cups` are the old entries in rc.conf deleted and the new not automatically enabled for all if the old entries were already present and enabled, why even after making the new entries the printers still not working and why additionally the network don't worked anymore and i was forced to use another device to find the solution and why the founded solution were not in Artix-Wiki nor Artix-Forum. The solution was on Ubuntu forum apparently have the same problem.

Stop pointing the finger always to others, we all are not perfect and make continuously mistakes, you are no exception in this.

Re: Paru not working

Reply #18
Paru works perfectly fine (also yay works perfectly fine) the only thing that you have to do is to press the `q` key in your keyboard when you are done reviewing the PKGBUILD (the thing that you pasted in your first post)

Code: [Select]
paru pamac
...
5 aur/pamac-aur 10.3.0-5 [+358 ~4.34] [Installed: 10.3.0-4]

:: Packages to install (eg: 1 2 3, 1-3):
:: 5
:: Resolving dependencies...
:: Calculating conflicts...
:: Calculating inner conflicts...

Aur (1) pamac-aur-10.3.0-5

:: Proceed to review? [Y/n]:

:: Downloading PKGBUILDs...
 PKGBUILDs up to date
/home/tony/.cache/paru/clone/pamac-aur/PKGBUILD
# Contributor: Zeph <[email protected]>
# Maintainer: Zeph <[email protected]>
# https://gitlab.manjaro.org/packages/extra/pamac
ENABLE_FAKE_GNOME_SOFTWARE=0

pkgname=pamac-aur
pkgver=10.3.0
pkgrel=5
_pkgfixver=$pkgver

_commit='fe5ebe918439c5ad247bf82226421bb2083431a0'
sha256sums=('610d631e8a0e4de408546af776fb7f2cbee4d4f6743b4698e7bea8313c2e1f81')

pkgdesc="A Gtk3 frontend, Package Manager based on libalpm with AUR and Appstream support"
arch=('i686' 'x86_64' 'arm' 'armv6h' 'armv7h' 'aarch64')
url="https://gitlab.manjaro.org/applications/pamac"
license=('GPL3')
depends=('glib2>=2.42' 'json-glib' 'libsoup' 'dbus-glib' 'polkit' 'vte3>=0.38' 'gtk3>=3.24'
         'libnotify' 'desktop-file-utils' 'libpamac-aur>=11.2' 'gnutls>=3.4' 'git'
         'appstream-glib>=0.7.18-1' 'archlinux-appstream-data' 'libhandy' 'git')

optdepends=('polkit-gnome: needed for authentification in Cinnamon, Gnome'
            'lxsession: needed for authentification in Xfce, LXDE etc.')
makedepends=('gettext' 'itstool' 'vala>=0.46' 'gtk3>=3.24' 'asciidoc' 'meson' 'ninja' 'gobject-introspection' 'libappindicator-gtk3' 'xorgproto')
conflicts=('pamac' 'pamac-tray-appindicator')
provides=("pamac=$pkgver-$pkgrel")
options=(!emptydirs !strip)
install=pamac.install
source=("pamac-$pkgver-$pkgrel.tar.gz::$url/-/archive/$_commit/pamac-$_commit.tar.gz")

define_meson=''
if [ "${ENABLE_FAKE_GNOME_SOFTWARE}" = 1 ]; then
  conflicts+=('pamac-gnome-integration' 'pamac-gnome-integration-dev' 'gnome-software')
  define_meson+=' -Denable-fake-gnome-software=true'
fi


prepare() {
  cd "$srcdir/pamac-$_commit"
:

HERE PRESS "q" IN YOUR KEYBOARD LIKE A CHAMPION

^^ scroll to the end of the code block above for instructions

Let me know if you need any further assistance

Re: Paru not working

Reply #19
@OP: Just to address some points:

  • AUR is far from "required" for normal operation of Artix. Official repositories are sufficient.
  • Recommended way to install Artix is installation from the base ISO. In base ISO installation, only packages which pacman is instructed to install, and their dependencies, are installed. paru and pamac-aur are not among the fundamental dependencies. Base ISO installation is how anyone who prefers to control what packages are installed, is installing Artix.
  • Software like pamac only conceals PKGBUILDs and pacman hook output from the user, which is a security hole, and  could lead to non-operational software if some user intervention, detailed in a pacman hook output, is required.
  • I don't "expect" anything, just inform you where you can find best help regarding unofficial packages, which packages from AUR are.
  • Everyone using software is its user, by definition, myself included.

That's all I have to say on the matter.

Re: Paru not working

Reply #20
... ,rather explain the solution for a problem.
The problem is yourself.


... a normal user have no chance to make things right and the most user are not able and willing to spend time ...
The people, you call 'user', must be expert and have many time to understand and apply the steps as you require.

You only try to elevate yourself above others and expect admiration, presenting a solution is not your intention or willingness, this is now to much of bad things. You don't know the meaning of life, and this contains only one simple rule.

Your arguments are unsustainable and i bet, yourself read almost never a  pkgbuild or only if something goes wrong, otherwise you should tell us now how many Artix users read a pkgbuild.

Stop pointing the finger always to others, we all are not perfect and make continuously mistakes, you are no exception in this.

For the garbage you have written here, I would kick you out of the forum immediately!
"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons} -gnome3 -kde -plasma -wayland "

Re: Paru not working

Reply #21
The people, you call 'user', must be expert and have many time to understand and apply the steps as you require.
Bonjour,
Did I make a mistake installing Artix and different AUR packages on multiple PCs?
Maybe not, because everything works fine, although I'm not a computer scientist.

Re: Paru not working

Reply #22
The problem is yourself.

For the garbage you have written here, I would kick you out of the forum immediately!

'Paru' in contrary to 'Yay' stop apparently by the installation of some apps.
It ask for password and confirmation with 'Y' (as 'yay') but sometimes appear just a blinking cursor and the user don't know what to do .

If the user, at this stage, press any key, the terminal will freeze. Sometime work "CTRL +C", sometime works even not.

The solution is, by just appearing of cursor, to press the "Q" key, better said the "q" (small Q) key.

Even the program developer on github mention to hit this key, but was too complicated to explain when to press it.

Conclusion-s:
1. Paru is bad programmed
2. Paru don't ask to press/hit the "q" key and the user don't know what and when to do
3. You and your "supporter" here neither know Paru nor ever used it or can help to solve the question.

Naturally, if you can, you would ban me from forum, but:
Remain the fact you can't or want't help at all, even in an apparently (for you) simple problem.

Finally, i found the solution by myself, even if i spend a lot of time on this, and give it away and that's normal (for me).

N.B.: Isn't a blaming if someone don't know something, but is one, if act as expert and always assign the user as guilty.

Maybe i can encourage you to ban me in suggesting you a new signature"

"Wer nichts kann und tut, macht niemals was falsches"

or

"Achtung! beleidigte Leberwurst"

or just "Q" like the required key

Re: Paru not working

Reply #23
Congratulations on finding the solution, and it was  morganamilo who first found the answer, until then nobody here had any idea including myself, credit where it is due!  ;D  What is happening with the "q" key is at that point you are not using "paru" but are temporarily within "less" to view a text file and you need to press "q" to exit less and continue. Well that is obvious now, but I am pretty sure from looking at the source on GitHub you could also configure what is used by editing this in paru.conf as documented in the man page
Code: [Select]
man paru.conf
Pager = Command
Command to use for paging
I haven't tried the alternatives, such as "bat" and "most" (you'll have to install these packages first if you don't already have them) but anyway if you really didn't like less in paru then that's one way to swap it for something else.

Re: Paru not working

Reply #24
Congratulations on finding the solution, and it was  morganamilo who first found the answer, until then nobody here had any idea including myself, credit where it is due!  ;D  What is happening with the "q" key is at that point you are not using "paru" but are temporarily within "less" to view a text file and you need to press "q" to exit less and continue. Well that is obvious now, but I am pretty sure from looking at the source on GitHub you could also configure what is used by editing this in paru.conf as documented in the man page
Code: [Select]
man paru.conf
Pager = Command
Command to use for paging
I haven't tried the alternatives, such as "bat" and "most" (you'll have to install these packages first if you don't already have them) but anyway if you really didn't like less in paru then that's one way to swap it for something else.

Thanks for your comforting words, but, to late, I had preferred the solution with explanation as I did after my first post.

The alternative you suggest is kind, but, you cannot provide evidence for functioning and is to complicated for me (as user) to apply.

Thanks anyway for your effort-s.

 

Re: Paru not working

Reply #25
what's so hard about navigating a text interface, exiting it with a key (q in less) then pressing enter to accept and execute the pkgbuild script?
that's why we are where we are...