Package Details: megazeux 2.93b-1

Git Clone URL: https://aur.archlinux.org/megazeux.git (read-only, click to copy)
Package Base: megazeux
Description: Game creation system
Upstream URL: https://www.digitalmzx.com/
Licenses: GPL
Groups: games
Submitter: CyberShadow
Maintainer: CyberShadow (insidious611)
Last Packager: insidious611
Votes: 3
Popularity: 0.21
First Submitted: 2017-07-27 08:36 (UTC)
Last Updated: 2024-09-11 22:40 (UTC)

Latest Comments

vikits commented on 2024-09-12 03:44 (UTC)

@insidious611 I found the issue. The issue was my Paru AUR helper cache directory was having the source archive of megazeux 2.93 (megazeux293.tar.xz). I uninstalled megazeux 2.93, removed the entire megazeux directory from /home/vxxxxxxx/.cache/paru/clone/ and tried installing again. This time it worked without any issues.

insidious611 commented on 2024-09-12 03:09 (UTC)

Yeah no, just tested again in my VM with the latest snapshot here and it built and installed megazeux 2.93b when I used makepkg -si.

Don't know what you mean by "check for updates" either? AUR is a manual process, there's no update checking involved, and MegaZeux's inbuilt updater is disabled on this version and not intended for use on Linux.

insidious611 commented on 2024-09-12 02:57 (UTC)

Vikits: I'm not sure how that's possible. I've tested this pkgbuild myself and it builds 2.93b.

vikits commented on 2024-09-11 22:42 (UTC)

Seems there is some issue with this package update. Though the check for update works fine, it downloads the source package of 2.93 not 2.93b and builds.

insidious611 commented on 2021-01-02 01:54 (UTC)

Jayman: Honestly, current maintainer here, I took over this pkgbuild a while back and left the DLAGENTS line as-is because I wasn't really clear as to whether it was needed.

If it's no longer needed and causing issues I'll get that fixed soon. I have to update this for the newest release of MegaZeux anyway.

Jayman commented on 2021-01-01 21:50 (UTC)

When I tried to build this package, I got: "ERROR: Unknown download protocol: https" I fixed this error by commenting out the DLAGENTS line for the PKGBUILD.

Why does this PKGBUILD specify its own DLAGENTS? Is a custom DLAGENTS still necessary?