Arch Linux User Repository

@Marek72 fixed by adding this patch, I opened a PR upstream for it.

error[E0433]: failed to resolve: could not find `os` in `fs`
  --> src/keys.rs:18:9
   |
18 | use fs::os::unix::fs::PermissionsExt;
   |         ^^ could not find `os` in `fs`

error[E0599]: no function or associated item named `from_mode` found for struct `Permissions` in the current scope
  --> src/keys.rs:56:56
   |
56 |         fs::set_permissions(pub_path, fs::Permissions::from_mode(0o644))?;
   |                                                        ^^^^^^^^^ function or associated item not found in `Permissions`
   |
   = help: items from traits can only be used if the trait is in scope
help: trait `PermissionsExt` which provides `from_mode` is implemented but not in scope; perhaps you want to import it
   |
 2 + use std::os::unix::fs::PermissionsExt;
   |

error[E0599]: no function or associated item named `from_mode` found for struct `Permissions` in the current scope
  --> src/keys.rs:71:59
   |
71 |         fs::set_permissions(secret_path, fs::Permissions::from_mode(0o600))?;
   |                                                           ^^^^^^^^^ function or associated item not found in `Permissions`
   |
   = help: items from traits can only be used if the trait is in scope
help: trait `PermissionsExt` which provides `from_mode` is implemented but not in scope; perhaps you want to import it
   |
 2 + use std::os::unix::fs::PermissionsExt;
   |

Some errors have detailed explanations: E0433, E0599.
For more information about an error, try `rustc --explain E0433`.
error: could not compile `purrcrypt` (lib) due to 3 previous errors

yeah, I followed up with that and got more context FYI: [PRQ#74091] Deletion Request for purrcrypt-git Rejected.

I've got a response from AUR moderator:

Request #74091 has been Rejected by bertptrs [1]:

purrcrypt-git is the correct name for this package, purrcrypt should be updated to not build from the latest VCS sources

[1] https://aur.archlinux.org/account/bertptrs/

@AlphaLynx I understood. Thanks for such a detailed explanation, you are absolutely right. I've sent a deletion request for purrcrypt-git.

@kochan Thank you for your response. I understand your reasoning, but I believe there's a misunderstanding about the application of the VCS naming guidelines in this specific case.

The purrcrypt package is bound to a specific version—the specific commit referenced in the PKGBUILD source URL fragment (purrcrypt PKGBUILD, line 14). While upstream lacks formal git tags or GitHub releases, this doesn't make it a -git VCS package. The package builds from a pinned commit (currently 116f168), not from the latest development state.

This pattern is well-established in Arch's official repositories, where numerous packages in extra use commit fragments in their source URLs to build specific versions from VCS repositories (examples: treeify, wlr-protocols, yubikey-full-disk-encryption, rapidcheck). These packages follow the guideline: "Packages that build from source using a specific version do not use a suffix" (AUR Rules of submission), and "Suffix pkgname with -bzr, -cvs, -darcs, -git, -hg, -svn, etc., unless the package fetches a specific release." (VCS Package naming)

The -git suffix is intended for packages that track ongoing development—providing access to features not yet available in stable releases. For example, polkit-git builds from the latest commits on main (polkit-git PKGBUILD, line 21) while polkit builds from the git tag via URL fragment (polkit PKGBUILD, line 32), allowing users to access newer features before the next stable release (126...main). Since purrcrypt's "stable release" is the latest commit on main, purrcrypt-git serves no distinct purpose from the existing purrcrypt package.

Additionally, the AUR guidelines emphasize checking for existing packages before submission (AUR Rules of submission). The purrcrypt package was submitted on 2025-03-16, predating purrcrypt-git by several weeks 2025-04-04.

Given that both packages deliver identical functionality and purrcrypt follows established patterns for VCS-sourced packages with specific versions, I believe purrcrypt-git should be removed to avoid duplication.

Hello! Recently, you've left a comment with a request to delete my purrcrypt-git package from AUR. I see, our PKGBUILDs are almost identical, but packages which upstream is VCS and which are not bound to specific version should have "-git" postfix in its name (source). Therefore, it's you who should delete the package to avoid misconceptions.