| Git Clone URL: | https://aur.archlinux.org/paru.git (read-only, click to copy) |
|---|---|
| Package Base: | paru |
| Description: | Feature packed AUR helper |
| Upstream URL: | https://github.com/morganamilo/paru |
| Keywords: | AUR helper pacman rust wrapper yay |
| Licenses: | GPL-3.0-or-later |
| Submitter: | Morganamilo |
| Maintainer: | Morganamilo |
| Last Packager: | Morganamilo |
| Votes: | 896 |
| Popularity: | 29.02 |
| First Submitted: | 2020-10-19 00:43 (UTC) |
| Last Updated: | 2024-03-26 04:28 (UTC) |
There is no actual diff between 1.11.1 and 1.11.2: https://github.com/Morganamilo/paru/compare/v1.11.1...v1.11.2
The reason why 1.11.2 was released was that the rebuilt binary compatible with the new version of OpenSSL had to be released on the GitHub repository. You don't need 1.11.2 even if paru says it cannot find openssl.so.1.1. Instead, you can just rebuild paru 1.11.1 with the latest version of OpenSSL installed.
Can you update to 1.11.2 your AUR package? Otherwise, make it an orphan package, and I'll maintain it. Or release 1.11.3 on both upstream and the AUR, so everyone agrees.
So far it looks like paru works just fine on the riscv64 platform, so it should be safe to add it to the supported arch list.
Thanks @johnnybash, I was asking about 1.11.1-1 which builds OK but doesn't find libssl.so.1.1 if openssl-1.1 is not installed
[user@arch1 ~]$ pacman -Qs openssl
local/libevent 2.1.12-4
Event notification library
local/openssl 3.0.7-4
The Open Source toolkit for Secure Sockets Layer and Transport Layer Security
local/perl-net-ssleay 1.92-2
Perl bindings for OpenSSL and LibreSSL
[user@arch1 ~]$ paru -Sua
paru: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
[user@arch1 ~]$
Does paru 1.11.1-1 need openssl-1.1 instead of openssl (currently 3.0.7-4)?
It's not out of date, 1.11.2 is just a rebuild for openssl 3.0
Not everyone uses the AUR the same way you do (I'm guessing you just fetch the PKGBUILD from the AUR and build it on local machine). I and many people have automated CI that automatically fetch packages from the AUR and build a private pacman repo, but it only build when it sees a different version.
@pedrogabriel if the latest is 1.11.2, it's out of date, IMHO.
It's not out of date, 1.11.2 is just a rebuild for openssl 3.0
Pinned Comments
haxie commented on 2023-05-26 17:45 (UTC)
you're better off contacting her via the github, this comments section is 90% "it's out of date" from people who didn't scroll down before posting