Package Details: chocolate-doom 3.0.1-1

Git Clone URL: (read-only, click to copy)
Package Base: chocolate-doom
Description: Historically-accurate Doom, Heretic, Hexen, and Strife ports.
Upstream URL:
Licenses: GPL2
Conflicts: chocolate-common, chocolate-heretic, chocolate-hexen, chocolate-strife
Replaces: chocolate-common, chocolate-heretic, chocolate-hexen, chocolate-strife
Submitter: None
Maintainer: chungy
Last Packager: chungy
Votes: 52
Popularity: 0.095083
First Submitted: 2006-07-30 06:27 (UTC)
Last Updated: 2020-06-25 15:25 (UTC)

Pinned Comments

chungy commented on 2017-01-18 02:40 (UTC)

You'll either need to import fraggle's public key (available here: or, or run makepkg with --skippgpcheck

Latest Comments

chungy commented on 2020-11-16 10:10 (UTC)

Instead of being rude, maybe actually check what you're saying.

$ gpg --verify chocolate-doom-3.0.1.tar.gz.asc 
gpg: assuming signed data in 'chocolate-doom-3.0.1.tar.gz'
gpg: Signature made Wed 24 Jun 2020 08:22:20 PM PDT
gpg:                using RSA key 6D2C117E0310664497AA9546F6C2EE9C23354344
gpg: Good signature from "Simon Howard <>" [unknown]
gpg:                 aka "Simon Howard <>" [unknown]

in the PKGBUILD:


terrytuden114 commented on 2020-11-16 07:15 (UTC)

This doesn't work. Why can't you people just use a normal ass key? Jesus christ.

No, fraggle's public key DOESN'T work, and neither do any of the keys it tells me to import.

Stop posting trash to the aur maybe.

SpacingBat3 commented on 2020-05-28 11:47 (UTC)

I successfully built package with AARCH64 on Manjaro ARM (Raspberry Pi 4 model B), could you update PKGBUILD and add this arch so some package managers like pamac would recognise it as compatible?

chungy commented on 2020-01-20 06:42 (UTC)

You need to import the appropriate public key.

mreutman commented on 2020-01-20 05:34 (UTC)

Public key is still invalid as of January 2020.

==> Verifying source file signatures with gpg...
    chocolate-doom-3.0.0.tar.gz ... FAILED (unknown public key F6C2EE9C23354344)
==> ERROR: One or more PGP signatures could not be verified!

Morganamilo commented on 2018-10-25 19:57 (UTC)

PGP keys are still missing from the srcinfo though.

chungy commented on 2018-10-25 19:51 (UTC)

I don't seem to replicate the issue, it was probably just a temporary problem. Updating it to HTTPS anyway seems like a good idea though, thanks.

MagnusW commented on 2018-09-19 06:45 (UTC) (edited on 2018-09-19 06:48 (UTC) by MagnusW)

Got the following error when trying to build today:

curl: (22) The requested URL returned error: 404 Not Found
==> ERROR: Failure while downloading
Error downloading sources: chocolate-doom (chocolate-common chocolate-doom)

Seems that the source is not available via HTTP anymore. For example:

$ curl
This works however:

$ curl

Morganamilo commented on 2018-09-05 16:54 (UTC)

The pgp keys are not in the srcinfo. This is because you are using the defunct mksrcinfo over makepkg --printsrcinfo.

chungy commented on 2017-01-18 02:40 (UTC)

You'll either need to import fraggle's public key (available here: or, or run makepkg with --skippgpcheck

ahyeadude commented on 2017-01-18 01:25 (UTC)

Getting this error: chocolate-doom-2.3.0.tar.gz ... FAILED (unknown public key F6C2EE9C23354344)

chungy commented on 2016-12-30 02:16 (UTC)

Ahh, yes. I had forgotten about that. I made the change upstream myself :-) Thanks for the reminder.

Vaporeon commented on 2016-12-30 00:55 (UTC)

According to the changelog you don't have to change the binary dir anymore.

commented on 2016-09-23 04:50 (UTC)


commented on 2010-12-06 03:50 (UTC)

Your tarball has some issues. AUR guidelines suggest to not include binaries. Take for example: chocolate-doom/chocolate-doom.png chocolate-doom/chocolate-setup.png "Just an icon" you say, but I think you can do better. Thank you.

commented on 2010-11-09 22:35 (UTC)


commented on 2010-11-08 22:13 (UTC)

I have a compile error, concerning one of the manpages: