Package Details: awmtt 0.5-1

Git Clone URL: https://aur.archlinux.org/awmtt.git (read-only)
Package Base: awmtt
Description: Test and preview your AwesomeWM configuration with Xephyr
Upstream URL: https://github.com/mikar/awmtt
Licenses: MIT
Submitter: serialoverflow
Maintainer: serialoverflow
Last Packager: serialoverflow
Votes: 58
Popularity: 0.610024
First Submitted: 2011-06-17 09:15
Last Updated: 2017-02-22 13:50

Latest Comments

serialoverflow commented on 2017-02-14 05:14

thanks, i'll update the pkgbuild and repository to use tags in the next couple of days.

LxPvlv commented on 2017-02-12 21:21

==> Validating source files with sha256sums...
awmtt.sh ... FAILED
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build awmtt.

serialoverflow commented on 2015-01-12 20:29

Sorry about that, should have double checked.

ironborn commented on 2015-01-12 11:22

Checksums don't match after update to 0.4-2.

PKGBUILD: 56aca720eaec72709dca282116d6843cb24b765d528d61d55655648aa7f75c1b
$ sha256sum awmtt.sh: 146f68ac831ce6bc2f417472c7b46c121efce31a63b911c2324368bb83da103e

sergey_klay commented on 2014-02-07 14:55

Yes, skip checking resolves issue.

Thanks!

serialoverflow commented on 2014-02-07 09:39

Makepkg.conf only affects the building process. In fact, lots of pacman core/extra/community packages are built with sha256 checksums.
Additionally, i can build the package on a system with the default INTEGRITY_CHECK=(md5). I'm not sure where it goes wrong on your side but it's not makepkg.conf.

You can, however, always edit the PKGBUILD while installing to read {md5,sha256,...}sums=('SKIP') to avoid this issue.

serialoverflow commented on 2014-02-07 09:29

that information seems either outdated or wrong. i can build the package on a system with the default INTEGRITY_CHECK=(md5). I am not convinced that i am at fault here but i'll keep an eye on it.

You can, however, always edit the PKGBUILD while installing to read {md5,sha256,...}sums=('SKIP') to avoid this issue.

sergey_klay commented on 2014-02-07 09:11

Hi!

It seems if you use SHA-2 checksum (such a sha256sums) you need tell for users:

"To enable use of SHA-2 checksums, set up the INTEGRITY_CHECK option in /etc/makepkg.conf"

Or just use md5

serialoverflow commented on 2014-02-06 10:12

i just updated the source tarball again but yeah, the sha256sum stayed the same but maybe it does the trick for you as it did for elandx 2 months ago.

the checksum is f6e4bceed9becb28576474f336934369651c037997b4f18d4faf89dac0865915

sergey_klay commented on 2014-02-06 10:05

No, I couldn't update package. I went as follows - remove package, cleanup cache and tried to install it again. And again I got the same error - Validating source files with sha256sum. Now I don't have even old version. Though of course, I could just grab the source from Gist and use them. But your package .. you are confident. that it works not only at your pc? : )

All comments