Arch Linux User Repository

More detailed answer for wrong checksum:

Just run updpkgsums from pacman-contrib. pkgver gets extracted from the archive’s changelog (WhatsNew.txt), so version number should always be correct.

If the package version changes, drop me a note here, though I usually get notified about updates by the author.

If it does not change, don’t install it. That can mean something is wrong with the package, it’s a tiny fix that does not change the changelog or I fucked up the package in some way. In that case still drop me a note here.

When using openjdk, the jar command isn't available so I had to use unzip to make the package. I also updated the magick command as per the deprecation warnings. Here's the patch to use with git apply

From 54fd132206ac4cbeeadb99e321b915d15ceb92f8 Mon Sep 17 00:00:00 2001
From: maki <maki@hotmilk.space>
Date: Tue, 27 Jan 2026 21:13:10 -0500
Subject: [PATCH] Use unzip and updated magick

---
 .SRCINFO   | 1 +
 .gitignore | 2 ++
 PKGBUILD   | 8 ++++----
 3 files changed, 7 insertions(+), 4 deletions(-)

diff --git a/.SRCINFO b/.SRCINFO
index 3a2956c..e9792bc 100644
--- a/.SRCINFO
+++ b/.SRCINFO
@@ -10,6 +10,7 @@ pkgbase = emulicious-bin
    makedepends = gendesk
    makedepends = dos2unix
    makedepends = imagemagick
+   makedepends = unzip
    depends = java-environment
    depends = sh
    depends = hicolor-icon-theme
diff --git a/.gitignore b/.gitignore
index ea1bad4..8cf0888 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,2 +1,4 @@
 *.zip
 *.pkg.*
+/pkg
+/src
\ No newline at end of file
diff --git a/PKGBUILD b/PKGBUILD
index 488aeaf..a2837a8 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -13,7 +13,7 @@ license=('custom' 'BSD')
 provides=('emulicious')
 arch=('any')
 depends=('java-environment' 'sh' 'hicolor-icon-theme')
-makedepends=('java-environment-common' 'gendesk' 'dos2unix' 'imagemagick')
+makedepends=('java-environment-common' 'gendesk' 'dos2unix' 'imagemagick' 'unzip')
 source=("$pkgname-$pkgver-$pkgrel.zip::https://emulicious.net/download/emulicious/?wpdmdl=205" 'emulicious.sh')
 sha256sums=('53c9b3104b6938044d230b4f4e422e56cae687ceff1bb0bf9fc794fe62fb272e'
             '3f9442376a7a8ba93ff5490826bcd5b5b81c5c62b3a6ec48bcd586a0e42fca66')
@@ -23,9 +23,9 @@ prepare() {
   cd "${srcdir}/"
   # was zipped on windows
   dos2unix ./*.txt
-  jar xf Emulicious.jar Emulicious.png
+  unzip -o Emulicious.jar Emulicious.png
   # resize to a quadratic shape
-  magick convert Emulicious.png -background transparent -resize 256x256 -gravity center -extent 256x256 "${pkgname}_256x256.png"
+  magick Emulicious.png -background transparent -resize 256x256 -gravity center -extent 256x256 "${pkgname}_256x256.png"
 }

 # emulicious does not communicate any version numbers
@@ -46,6 +46,6 @@ package() {
   # generate all other icon sizes
   for i in 16 24 32 48 64 72 96 128;do
     install -d "${pkgdir}/usr/share//icons/hicolor/${i}x${i}/apps/"
-    magick convert "${srcdir}/${pkgname}_256x256.png" -resize ${i}x${i} "${pkgdir}/usr/share//icons/hicolor/${i}x${i}/apps/${provides[0]}.png"
+    magick "${srcdir}/${pkgname}_256x256.png" -resize ${i}x${i} "${pkgdir}/usr/share//icons/hicolor/${i}x${i}/apps/${provides[0]}.png"
   done
 }
-- 
2.52.0

Validity check failed due. Might want to update the package.

More detailed answer for wrong checksum:

Just run updpkgsums from pacman-contrib. pkgver gets extracted from the archive’s changelog (WhatsNew.txt), so version number should always be correct.

If the package version changes, drop me a note here, though I usually get notified about updates by the author.

If it does not change, don’t install it. That can mean something is wrong with the package, it’s a tiny fix that does not change the changelog or I fucked up the package in some way. In that case still drop me a note here.

That happens whenever emulicious gets an update. There is only the "current version", it's always the same URL, only the file changes.

The error pointed out by jpoppe is still happening.

The correct sha256sum for the package is 34eb29b68a0131e632c6c27302b7c7ff7553f42692792e08e8cfea54c209eded.

It seems the checksum of the upstream binary has changed:

==> ERROR: One or more files did not pass the validity check!