Package Details: paru 2.0.4-1

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: 1017
Popularity: 15.59
First Submitted: 2020-10-19 00:43 (UTC)
Last Updated: 2024-09-20 18:50 (UTC)

Dependencies (6)

Sources (1)

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

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 25 Next › Last »

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.

MarsSeed commented on 2023-05-26 01:38 (UTC) (edited on 2023-05-26 01:39 (UTC) by MarsSeed)

TLDR: Paru can break itself if the paru package does not properly declare its direct dependencies like openssl (libssl.so).

Actually I did not directly remove openssl-1.1 today, I removed some benchmarking tools from AUR (basemark and unigine-superposition), and I used recursive removal.

That was when paru chose to remove my openssl-1.1 package automatically, thus breaking itself, because my instance of paru was built in Aug 2022.

A package manager tool like paru should absolutely try not to break itself, or at least warn the user and give them a choice about it. :)

MarsSeed commented on 2023-05-26 01:13 (UTC) (edited on 2023-05-26 01:14 (UTC) by MarsSeed)

@haxie I believe you do not properly understand how packaging works in Arch.

.SO dependency in a pacman package is dynamic: pacman looks up which packages provide the declared SO version.

Last August, the openssl package provided libssl.so.1.1.

Today, the openssl-1.1 package provides libssl.so.1.1.

SO versions mean API versions. You seem to confuse this topic.

If my local paru package has a depends=('libssl.so=3-64'), Arch can still update openssl to 3.0.x versions, maybe even 3.1.x versions, as long as any Arch package provides libssl.so=3-64', pacman/paru will be able to upgrade the system.

Don't try to make me seem stupid when it is you who do not understand what you are saying.

Paru has a direct depencency on openssl, not an indirect (transitive) dependency.

Therefore it should be declared in PKGBUILD.

My proposal (depends=('libssl.so')) is the most flexible and least disruptive way to do a versioned dependency declaration.

And it is the most helpful and graceful for users.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 25 Next › Last »