Package Details: libpng15 1.5.30-1

Git Clone URL: (read-only)
Package Base: libpng15
Description: A collection of routines used to create PNG format graphics files (1.5 branch)
Upstream URL:
Licenses: custom
Conflicts: libpng<1.6
Submitter: eworm
Maintainer: eworm
Last Packager: eworm
Votes: 126
Popularity: 0.104502
First Submitted: 2013-05-02 14:58
Last Updated: 2019-07-01 20:30

Latest Comments

1 2 3 4 Next › Last »

archiebald commented on 2019-07-03 00:47

I am getting the warning below. I fetched the pgp keys again, but still getting the same warning. Any help is appreciated.

==> Validating source files with sha256sums... libpng-1.5.30.tar.xz ... Passed libpng-1.5.30.tar.xz.asc ... Skipped libpng-1.5.30-apng.patch.gz ... Passed ==> Verifying source file signatures with gpg... libpng-1.5.30.tar.xz ... Passed (WARNING: the key has expired.) ==> WARNING: Warnings have occurred while verifying the signatures. Please make sure you really trust them.

fuan_k commented on 2019-07-01 17:01

@maintainer: Please change the patch line to the following

gzip -d ../../libpng-${_apngver}-apng.patch.gz                                                                                               
patch -p1 -i ../../libpng-${_apngver}-apng.patch

gzip doesn't seem to like symbolic links very much apparently.

ssysmso commented on 2019-06-27 09:06

Error during build : patch: **** Can't open patch file ../libpng-1.5.27-apng.patch : No such file or directory

robrunner commented on 2017-10-26 14:06

Validating source files with sha512sums...
lltag-0.14.6.tar.gz ... Passed
lltag-0.14.6.tar.gz.asc ... Passed
==> Verifying source file signatures with gpg...
lltag-0.14.6.tar.gz ... FAILED
==> ERROR: One or more PGP signatures could not be verified!
==> ERROR: Makepkg was unable to build lltag.

vanadium50 commented on 2017-01-28 14:30

Last 3 comments on keys, same problems here. I just followed
@eworm from 2015-03-27. Worked OK.

gpg --recv-keys F54984BFA16C640F

rcrath commented on 2017-01-04 03:08

key URL gives message in Chrome:
This server could not prove that it is; its security certificate is not trusted by your computer's operating system. This may be caused by a misconfiguration or an attacker intercepting your connection.

wolttam commented on 2016-05-26 20:25

I had the same issue as asitdepends today,
Fixed by downloading key from:
gpg --import /path/to/key

asitdepends commented on 2015-07-21 15:06

Verifying source file signatures with gpg...
libpng-1.5.22.tar.xz ... FAILED (unknown public key F54984BFA16C640F)
ERROR: One or more PGP signatures could not be verified!

How can I fix this?

eworm commented on 2015-04-19 10:51

Just checked again... Everything is fine. Looks like your tarballs are broken. You could check with gpg, that should report an error. For me it gives:

% gpg --verify libpng-1.5.22.tar.xz.asc
gpg: assuming signed data in 'libpng-1.5.22.tar.xz'
gpg: Signature made Thu 26 Mar 2015 02:20:07 PM CET using RSA key ID A16C640F
gpg: Good signature from "Glenn Randers-Pehrson (mozilla) <>" [unknown]
gpg: aka "Glenn Randers-Pehrson (libpng) <>" [unknown]
gpg: aka "Glenn Randers-Pehrson (pngcrush) <>" [unknown]

OJaksch commented on 2015-04-16 16:12

...can't get it to work. The sha256 checksums are different since weeks at my site. Got
2c771f7106d684ca6129f099efd6ee5858abced1140ccb45a823f6af73728765 for libpng-1.5.22.tar.xz and
de4ecd049a0838c56a7e73cca8ed9f2ce99723b29b6d4da220a5e79db206e66c for libpng-1.5.22-apng.patch.gz.
Downloaded several times, always same checksums as called above. Strange.