Package Details: sync 0.9.4-1

Git Clone URL: https://aur.archlinux.org/sync.git (read-only, click to copy)
Package Base: sync
Description: Backup and synchronization service
Upstream URL: https://taler.net/
Licenses: AGPL
Groups: taler
Conflicts: sync-bin, sync-git
Submitter: grufo
Maintainer: grufo
Last Packager: grufo
Votes: 1
Popularity: 0.000001
First Submitted: 2021-08-27 02:07 (UTC)
Last Updated: 2024-03-29 16:17 (UTC)

Latest Comments

grufo commented on 2023-10-11 06:27 (UTC) (edited on 2023-10-11 06:28 (UTC) by grufo)

@FabioLolix

I see that you have flagged this package as non-up-to-date despite I updated it few hours ago. I guess then the problem is not that the package is not up-to-date, but this comment of yours from two years ago.

The answer is no. And the reason is that the package does conflict with sync-bin and sync-git. Even if these are not currently present in AUR, they could be uploaded in any moment, and Arch naming conventions reserve for these two packages a precise meaning, which is that of being the same package retrieved by different means (hence they are conflicting packages).

You had already posted a similar request under the cadet-gtk package, which was declined. I invite you to read this paragraph from the ArchWiki (see PKGBUILD § conflicts – emphasis mine):

When packages provide the same feature via the provides array, there is a difference between explicitly adding the alternative package to the conflicts array and not adding it. If the conflicts array is explicitly declared the two packages providing the same feature will be considered as alternative; if the conflicts array is missing the two packages providing the same feature will be considered as possibly cohabiting. Packagers should always ignore the content of the provides variable in deciding whether to declare a conflicts variable or not.

Please do not flag again packages that are up-to-date as non-up-to-date. Package owners are not obliged to agree to your requests, especially if they do not follow the guidelines, and marking a package as non-up-to-date for unrelated reasons damages the repository.

FabioLolix commented on 2021-08-27 15:10 (UTC)

No need to conflicts sync-bin, sync-git