Search Criteria
Package Details: python-pathvalidate 3.2.1-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/python-pathvalidate.git (read-only, click to copy) |
---|---|
Package Base: | python-pathvalidate |
Description: | Sanitize/validate strings in filenames/file-paths/etc |
Upstream URL: | https://github.com/thombashi/pathvalidate |
Keywords: | sanitize validate |
Licenses: | MIT |
Submitter: | fl0w1 |
Maintainer: | fordprefect |
Last Packager: | fordprefect |
Votes: | 35 |
Popularity: | 4.18 |
First Submitted: | 2017-09-01 11:56 (UTC) |
Last Updated: | 2024-08-25 18:33 (UTC) |
Dependencies (6)
- python (python37AUR, python311AUR, python310AUR)
- python-click
- python-build (make)
- python-installer (python-installer-gitAUR) (make)
- python-setuptools-scm (make)
- python-wheel (make)
Latest Comments
1 2 3 4 Next › Last »
boennhoff commented on 2024-10-09 15:15 (UTC) (edited on 2024-10-09 15:17 (UTC) by boennhoff)
Using yay, I was stuck with the same (avoidable) checksum issue, which I could only solve by removing
~/.cache/yay/python-pathvalidate
.So, thanks for...
- the hint @foux
- a convenient AUR experience @yay ;-)
- maintaining the package at all @fordprefect
FabioLolix commented on 2024-09-08 10:49 (UTC)
@fordprefect I get you about the whining, yet all the checksum complaints could have been avoided by renaming the sources from
source=("$pkgname-$pkgver.tar.gz::
tosource=("$pkgname-$pkgver-2.tar.gz::
for a one time, and bumping the pkgrel too because the source is different isn't bad toovith commented on 2024-09-08 10:43 (UTC)
@fordprefect Looks like the
pkgrel
still hasn't been bumpedfordprefect commented on 2024-09-08 10:13 (UTC)
Folks! One last time: Please shut up about your bloody aur helpers, which produce nothing but trouble. Report here problems reproducible with makpkg only and whine about broken wrappers at the project upstream instead of pestering the wrong people for the problem. Thanks.
foux commented on 2024-09-08 10:09 (UTC)
@omnigenous : the ~/.cache/yay/python-pathvalidate folder. And then you're good
omnigenous commented on 2024-09-05 22:34 (UTC) (edited on 2024-09-05 22:36 (UTC) by omnigenous)
@chaos2theory
What folder are talking about? I've been stuck with this for days :-(.
Okay deleted
python-pathvalidate
andbottles
then installed bottles with cleanbuild all and it worked.nirnakinho commented on 2024-09-02 15:53 (UTC)
Maintainer, please update the pkgrel when you are making changing to the PKGBUILD. See https://wiki.archlinux.org/title/PKGBUILD#pkgrel for an explanation
chaos2theory commented on 2024-09-01 21:01 (UTC) (edited on 2024-09-01 21:11 (UTC) by chaos2theory)
Okay replacing this comment.
Package mantainer updated the sha without updating the version so everybody who updated between the version bump and before the sha was fixed is stuck unless you manually delete the entire folder. This is not a caching issue because all tools are seeing that the version was not updated.
This is a non-standard update that breaks configs for a reason, if there is no version bump there is no code to pull as per makepkg spec.
BiosElement commented on 2024-08-30 06:18 (UTC)
I can confirm it worked for me today with paru, but only after rm'ing .cache/paru/clone/
1 2 3 4 Next › Last »