My first question is how much of the Documentation did you read before doing the install. What homework did you do that made you choose EndeavourOS and do you understand what a Rolling Release is?
If you are going to us PAMAC then I would HIGHLY recommend you do not use the AUR through PAMAC. This can cause issues. PAMAC is not and official software package for EndeavourOS for a reason we already offer pacman and yay. Being a terminal centric but more importantly a BUILD IT YOURSELF distro we believe you should take charge of the manangment and maintenance of your system.
Please take your time to understand the choice you have made and make sure its the best choice for you. PAMAC is not really a recommended way to handle packages many only use it to get the information but still use pacman and yay or other aur helper to install the packages. Being new if you want a graphical style package manager without all the fuss then I would recommend a TUI program called pacseek.
Well on the advice of this board, I will try to use the terminal to install everything when using EndeavourOS. But Pamac is very nice for browsing. Makes looking through all your options… very easy on the eyes. So I’ll probably use it mainly for that. I certainly wouldn’t want to cause more problems, I have enough of those without creating them myself.
I never knew Pamac would cause issues, then again someone did say that if you’re using it on Manjaro this problem may be smaller.
Have a look at pacseek as well, as @thefrog mentioned. As it’s an TUI application you can earn some terminal credibitility while showing off For my personal liking it’s just a bit cumbersome to switch between the search filed as well as the list of search results / packages to be installed.
I’ve also mentioned Octopi, which seems not to interfere that much with the AUR as pamac does. And you’ll get a notifier app for the system tray, in case you’re on Plasma. It’s more lightweight than pamac. And I only use it occasionally when I need to see which packages are being installed and to resolve dependency issues.
Additionally, if you’re a bit more into the distro and have mastered the basics, there are also some ways to get autocompletions to work, even for the AUR and don’t have to type out everything or use the search functions which are provided.
I would advice this especially being a newb. You need to understand what is going on when packages are installed so that if there are issues its easier for you to fix them. Its also better for that time when PAMAC will break and not work and then you have no clue how to use the appropriate tools to bypass the issue of the Package Manager.
So my best advice is to First learn the System you chosen so that it is easier when issue’s do arrive you will have a better chance of getting them fixed. I would suggest you as a newb start from these to threads on Managing your New EndeavourOS install as well as learning to Read the Wiki of both Arch and Endeavour.
If you look at its dependencies, libpamac, it is in turn dependent on pacman and libalpm (Archlinux Package Manager Library).
In other words, Pamac is a GUI frontend for pacman/libalpm.
In practice, since you have to install it from AUR, there may be sometimes a difference in time where pacman/libalpm (etc.) from Arch’s official repository get updated but the Pamac package from AUR is lagging behind and therefore leading to a broken Pamac. But this issue is transitory and is often resolved swiftly from the maintainers in AUR.
What you have to avoid is GUI package manager which uses packagekit as backend. However if you dont use them for installing and updating packages fro Arch’s repos, they are just fine for managing Flatpaks etc.
The issue here is that Manjaro does not follow the Arch way. This is why it is recommended not to be used. Its a Manjaro project and specific to THEIR needs and not the needs of Other OS’s. This is why people will always continue to have this issue with PAMAC and for new to Arch users who don’t really understand much how package management works its best for them to learn doing it manually first.
Using PAMAC for a Package Browser should be no issue if that is really what you want to use. At the end of the day its the OP’s machine so its the OP’s rules.
This is not about Manjaro and how they manage their repos.
Pamac is a piece of software, sure, developed by Manjaro but as I have explained, it is ultimately based on Pacman/libalpm.
Alright, one can say that it takes a detour via libpamac which as I understand it is a wrapper around libalpm and extends its functionality to be able to handle AUR for example. In the way of analogy, like yay is a pacman wrapper with AUR support.
There are other non-Manjaro, Arch-based distros that ships with Pamac. Arcolinux comes to mind. There might be others.
Sure, you can use Pamac and break your system but you can do that with pacman and yay as well.
Most of the breakages I have seen, it has been about pamac itself being broken on close to vanilla Arch-based systems, where users install it from AUR. And the breakage in this case is due to updates to pacman/libalpm from Arch’s repo while libpamac is lagging behind a bit in AUR. Something that is adressed by the AUR package maintainers of libpamac/pamac.
I’m not going to hijack the thread anymore to debate PAMAC. I just state I don’t think a new to Arch user should start out using that for package management. I believe they should learn to do it the correct way for when the Third party program doesn’t work.
Statements like this show the OP Understands little about Arch Package Management and should probably take some time to learn it before relying on third party programs to do it for them.
Again as I last stated before its ultimately up to the OP what they want to use. I just think they should be aware issues will arise from it at some point as with any update you can have on Arch. The difference is in knowing what to do vs not knowing.
What users should or should not do, will be doing or won’t be doing, doesn’t change the fact about PAMAC, being a GUI frontend, via LIBPAMAC, for PACMAN/LIBALPM. That is what I wanted to make clear.
When installing pacseek, I encountered this warning. Looks like it’s not a big deal since it did a sha256 comparison for me and they matched. Still makes you wonder why it would skip the pgp signatures. Maybe this functionality simply wasn’t offered by the developer/maintainer who put it on the AUR?
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with sha256sums…
pacseek-1.8.5.tar.gz … Passed
While it’s true I am still a newb to installing via the terminal having come from manjaro, the statement you’re referencing is (mostly) correct:
"In Linux, adding -git to the end of a package name (e.g., program-git) typically means that the package will install the latest development version of the software directly from its Git repository. This is useful for accessing cutting-edge features, bug fixes, or updates that are not yet included in stable releases.
Purpose of -git Packages
Latest Code:
These packages fetch and build the software from the most recent commits in the project’s Git repository, ensuring you get the absolute latest version.
Development Version:
-git packages are often used by developers or advanced users who need to test new features or contribute to ongoing development.
Unstable or Experimental:
Unlike stable versions, these versions may be less tested and could contain bugs or incomplete features.
When to Use -git Packages
You need features or fixes that are not available in the stable release.
You want to contribute to development or test experimental functionality.
You are troubleshooting a bug that has been fixed in the development version.
Example
If you want to install neovim-git instead of neovim, the neovim-git package will clone and build Neovim from its Git repository, providing you with the latest updates. On Arch Linux, this can be done using an AUR helper like yay.
Stability, yes. But I did say latest, I didn’t mention stability (even though I would have if I had realized it that may be considered undesirable by some people). But yeah that’s just splitting hairs at this point.
Anyway I got Pacseek installed, hopefully it has a somewhat better reputation on EdeavourOS than Pamac does. Seems really nice, I was able to get Librewolf installed with it, without issues.
Gave this a test and it seems to work fine. Now I won’t have the super annoying timeout in the event that I ever need to compile something large again.
Steps to Disable Timeout in Bash
Edit the Bash Configuration File:
Open your preferred bash configuration file in a text editor. You can use either ~/.bashrc (user-specific) or /etc/bash.bashrc (system-wide for all users).
For example, to edit ~/.bashrc:
bash
nano ~/.bashrc
Set the TMOUT Variable
Add the following line to disable the timeout completely:
bash
export TMOUT=0
This ensures that the shell session will not automatically log out due to inactivity
Save and Exit
Save the changes and exit the editor (e.g., in nano, press CTRL + O, then CTRL + X).
Apply the Changes:
Reload the configuration file to apply the changes immediately
Setting TMOUT=0 disables the timeout entirely.
If you modify /etc/bash.bashrc, you need root privileges, and it will affect all users on the system.
Ensure you only apply this change if you trust all users on your system, as disabling timeouts can pose a security risk.
I gave you a simple and safe command of preventing sudo to time out while yay is building your package.
I don’t know what the security implications of what you have done will be, but I do hope for the safety of your system that one of our forums more advanced users look into this and comment on it.
At the end of the day, it is your system and your machine, so do what you want with it.
So it didn’t install. But the thing you didn’t install looked like it was going to install onlyoffice.
I’m lost and I’m only on post 5. . .
It’s not. Just go straight to arch repos or AUR website. It’s far better/easier. You can also try pacseek. Pacseek is fantastic and will accomplish all of the things you want without the downside of pamac (which is all of it).
They aren’t. There’s been ample over the years.
Yes, but not always the most recent versions → thus where this whole thning goes wonky.
Possibly. They are a member here. If it’s an issue, we can ask them.
For my personal liking it’s just a bit cumbersome to switch between the search filed as well as the list of search results / packages to be installed.