Package Details: awmtt 0.4-2

Git Clone URL: (read-only)
Package Base: awmtt
Description: Test and preview your AwesomeWM configuration with Xephyr
Upstream URL:
Licenses: MIT
Submitter: serialoverflow
Maintainer: serialoverflow
Last Packager: serialoverflow
Votes: 53
Popularity: 0.139686
First Submitted: 2011-06-17 09:15
Last Updated: 2015-06-11 14:25

Latest Comments

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 146f68ac831ce6bc2f417472c7b46c121efce31a63b911c2324368bb83da103e

sergey_klay commented on 2014-02-07 14:55

Yes, skip checking resolves issue.


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


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? : )

serialoverflow commented on 2014-02-06 00:23

Thanks for the feedback but please try to include the failing checksum next time.
You probably were unlucky and tried to install awmtt when i had just pushed the update to github and the AUR yesterday around 14:11. A good bet in those cases is to clear your cache (wherever your AUR helper built the package, typically /tmp) and try again a little bit later.
For what it's worth, i usually build the package on 2 seperate machines to make sure it builds and runs correctly. Since the sha256 matches, i'm going to assume it builds fine for everyone else.

sergey_klay commented on 2014-02-05 14:11

==> Software upgrade (new version) :
aur/awmtt 0.2-2 -> 0.3-1

==> Continue upgrade ? [Y/n]
==> [V]iew package detail [M]anually select packages
==> --------------------------------------------------
==> y

==> Continue building awmtt ? [Y/n]
==> -------------------------------
==> y
==> Building and installing package
==> Making package: awmtt 0.3-1 (Wed Feb 5 18:11:24 MSK 2014)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found awmtt
==> Validating source files with sha256sums...
awmtt ... FAILED
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build awmtt.
==> Restart building awmtt ? [y/N]
==> ------------------------------

All comments