But there is a packaging problem that needs to be addressed, as I mentioned in May 2023. It hasn't got any answer yet from maintainer.
Search Criteria
Package Details: paru 2.0.3-1
Package Actions
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) |
Dependencies (6)
- git (git-gitAUR)
- libalpm.so (pacman-pbAUR, pacman)
- pacman (pacman-pbAUR, pacman-fancy-progress-gitAUR, pacman-gitAUR)
- cargo (rust-nightly-binAUR, cargo-gitAUR, rustup-gitAUR, rust, rustup) (make)
- bat (bat-cat-gitAUR) (optional) – colored pkgbuild printing
- devtools (devtools32-gitAUR, devtools-gitAUR) (optional) – build in chroot and downloading pkgbuilds
Required by (27)
- aconfmgr-git (optional)
- arch-os-manager
- arch-update (optional)
- dec-bin
- dec-git
- fe
- fuzzy-pkg-finder (optional)
- fzpac-git (optional)
- iwant (optional)
- iwant-bin (optional)
- kdeplasma-arch-update-notifier-git (optional)
- kdeplasma5-arch-update-notifier-git (optional)
- lsparu
- meta-package-manager (optional)
- octopi (optional)
- octopi-dev (optional)
- packageprovides (optional)
- pacup-arch-git (optional)
- paru-static
- parui (optional)
- parui-git (optional)
- paruz (optional)
- paruz-git (optional)
- pkg-listn (optional)
- pkg-listn-git (optional)
- ppac-git (optional)
- upgrade
Sources (1)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 22 Next › Last »
MarsSeed commented on 2023-08-18 21:39 (UTC)
yochananmarqos commented on 2023-08-18 21:34 (UTC)
@Popolon: FYI, cargo
is provided by both rust
and rustup
. That way, users can use either. cargo-nightly
is provided by rustup
. That is why the dependencies are the way they are.
bjo commented on 2023-08-18 21:31 (UTC)
@Popolon: No need to change the release version, as it is not out of date.
As Morganamilo said:
Not out of date. Just people flag it as such.
Popolon commented on 2023-08-18 16:21 (UTC) (edited on 2023-08-18 16:21 (UTC) by Popolon)
Managed to upgrade it by:
* Changing the release version+sha256sump
* Replacing in makedepends, cargo by rust (now cargo binary is available in rust package)
* Adding openssl in libs dependencies.
haxie commented on 2023-06-14 15:33 (UTC)
@enihcam, you should either ask that on the GitHub, or Google the question, as it pertains to changing the default linker in rust, and is not necessarily paru-specific. Either way, it's not relevant here.
enihcam commented on 2023-06-14 14:39 (UTC)
how to link paru objects with mold?
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
MarsSeed commented on 2023-05-26 02:52 (UTC)
+1: From Arch package guidelines (heading 5):
"List all direct library dependencies."
MarsSeed commented on 2023-05-26 02:11 (UTC) (edited on 2023-07-31 17:12 (UTC) by MarsSeed)
@Morganamilo, please read my polite proposal, and kindly consider declaring openssl
or preferably libcrypto.so
and libssl.so
, which are direct link-level SO-versioned dependencies of paru, in your PKGBUILD.
Otherwise paru can automatically and silently break itself if it removes the legacy version of openssl (like 1.1), even as part of a recursive removal of some other package.
haxie commented on 2023-05-26 01:50 (UTC)
@MarsSeed TL;DR: You didn't follow the basic steps of packages on the AUR and were shocked when randomly removing packages somehow broke your setup.
Your proposal is the most disruptive for end users, and is also not the way packages are handled on the AUR generally.
I get the feeling that you may not have noticed who it is who packages this program? I'm pretty sure a TU knows the rules, the common practices, and the best way to handle this sort of "issue"
Please stop tagging me in your inane ramblings, if you want to get aggro at the packager for packaging it in a way that doesn't suit you, then IRC exists. This comments section is not the place to go off on some crusade.
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