Sorry, just flagged it and reload of the page and you fixed it.
Search Criteria
Package Details: fadein 4.1.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/fadein.git (read-only, click to copy) |
---|---|
Package Base: | fadein |
Description: | Professional screenwriting software (DEMO) |
Upstream URL: | http://www.fadeinpro.com/ |
Licenses: | custom |
Submitter: | gangelop |
Maintainer: | gangelop |
Last Packager: | gangelop |
Votes: | 2 |
Popularity: | 0.000001 |
First Submitted: | 2016-05-09 20:03 (UTC) |
Last Updated: | 2023-12-28 21:06 (UTC) |
Dependencies (1)
Required by (0)
Sources (1)
Latest Comments
« First ‹ Previous 1 2
jrichard326 commented on 2021-06-23 11:48 (UTC)
gangelop commented on 2021-02-28 18:54 (UTC) (edited on 2021-02-28 19:05 (UTC) by gangelop)
MageJon,
It took a while, but I finally fixed it. Better late than never I guess.
https://aur.archlinux.org/cgit/aur.git/commit/?h=fadein&id=0be365fab09a691e35c5cf68358810876c4e7b55
gangelop commented on 2017-01-12 00:55 (UTC)
Updated.
Thanks for checking MageJohn.
MageJohn commented on 2017-01-12 00:43 (UTC) (edited on 2017-01-12 00:53 (UTC) by MageJohn)
The integrity check is failing. Since the source isn't versioned, it's probably been updated. Perhaps hash checking should be switched off for this package?
EDIT: Yep, the latest tarball has a higher version in it then in the PKGBUILD. This also means the build still breaks if you disable integrity checks, because the folder name is different. Marked as out of date.
Pinned Comments
gangelop commented on 2023-12-28 11:30 (UTC) (edited on 2023-12-28 11:31 (UTC) by gangelop)
If you get the following error while installing fadein, please flag the package as "out of date" here on the AUR page, and I will fix it.
The reason this happens is because the software is distributed as
fadein-linux-amd64-demo.tar.gz
without a mention of version number in the filename. So the main way we know that a new version has been released is that this file changes and fails the validity check.If someone knows a more elegant way to handle updates for this package, please let me know!