Arch Linux User Repository

thanks everyone for confirming that mepo does indeed compile against the Zig 0.11.0 version in the main arch repos. i'm also curious as to why some languages tend to lag behind in packaging on the main arch repos, but i'm glad everything is working now :)

let me know if you encounter any other issues

Can also confirm it is compiling and working now again

Thanks for the info, Zig has been updated to 0.11.0 in the main arch repos, compilation runs now without trouble :)

I'm also failing to install the latest version with the error,

==> Starting build()...
/dev/shm/aurydesty/mepo/src/mepo-1.2.0/build.zig:16:34: error: expected struct or union; found '[]const u8'
        .source_dir = .{ .path = "scripts" },
                                 ^~~~~~~~~
referenced by:
    runBuild: /usr/lib/zig/build_runner.zig:232:22
    usage__anon_5066: /usr/lib/zig/build_runner.zig:242:13
    remaining reference traces hidden; use '-freference-trace' to see all reference traces

==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: mepo-exit status 4

 -> Failed to install the following packages. Manual intervention is required:
mepo - exit status 4

To anyone who might be knowlageble in these "zig things"

....Zig 0.11.0, which is not available in the main arch repos for the time being. 

I'm somehow curious about this. Why are some languages so more "troublesome" than others, with regards to packaging for Arch ?

Why is this "zig" Arch official package always "late" ? Is it because it is difficult to maintain/build or package ? Does it mess/interfere with other things in Arch ? Is the language "zig" itself that makes things not so easy to compile and package things ? It reminds me of Pandoc and Haskell. Always a big beast to compile. At least compared to Go which makes it easy peasy to compile and package Go programs for Arch.

QuietApe: the latest mepo version is based on Zig 0.11.0, which is not available in the main arch repos for the time being. currently the workaround is to install zig-bin from the AUR, which is up to date. this will be fixed when Zig 0.11.0 is available in the main arch repos. The zig-bin package doesn't however satisfy the dependency check if it were to say zig>=0.11.0, so the dependency in the PKGBUILD still just says zig. i tried building on 0.10.1 and got the same error you did, so i assume this is the issue.

I tried to compile mepo but I end up with this error with makepkg :

==> Starting build()...
path/to/package/mepo/src/mepo-1.2.0/build.zig:16:34: error: expected struct or union; found '[]const u8'
        .source_dir = .{ .path = "scripts" },
                                 ^~~~~~~~~
referenced by:
    runBuild: /usr/lib/zig/build_runner.zig:232:22
    usage__anon_5129: /usr/lib/zig/build_runner.zig:242:13
    remaining reference traces hidden; use '-freference-trace' to see all reference traces

==> ERROR: A failure occurred in build().
    Aborting...

I guess the problem come from zig, but I don't get how to correct it ?

midv: The zig dependency version numbers have been temporarily removed, the build flag updated, and pkgrel bumped. I tested the updated pkgbuild on my system and it works as expected. Thanks for the heads up!

I managed to install 1.2.0 but it took a while to get there. I had to install zig-bin from AUR to satisfy the zig>=0.11 dependency. Then I had to change two things in PKGBUILD:

diff --git a/PKGBUILD b/PKGBUILD
index 96c3d1c..0a61a4e 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -8,8 +8,8 @@ arch=('i686' 'x86_64' 'arm' 'aarch64')
 url="https://git.sr.ht/~mil/mepo"
 license=('GPL3')
 depends=('jq' 'curl' 'zenity' 'xorg-xwininfo' 'geoclue' 'ncurses' 'findutils' 'sdl2_gfx' 'sdl2_image' 'sdl2_ttf')
-makedepends=('zig>=0.11' 'sdl2')
-checkdepends=('zig>=0.11')
+makedepends=('zig' 'sdl2')
+checkdepends=('zig')
 changelog=
 source=("$pkgname-$pkgver.tar.gz::$url/archive/$pkgver.tar.gz")
 sha512sums=('e01b19a578f9ffa340eac62e1db75495b424fe9bff98b9d25cf2c3cd6a402e8c756463582757bbd979aa927cd2e8c1ded2c25f6746851fb2a39a1257794fbbf3')
@@ -17,7 +17,7 @@ sha512sums=('e01b19a578f9ffa340eac62e1db75495b424fe9bff98b9d25cf2c3cd6a402e8c756
 build() {
   cd "$pkgname-$pkgver"

-  zig build -Drelease-safe=true
+  zig build -Doptimize=ReleaseSafe
   zig-out/bin/mepo -docman > mepo.1
 }

I had to temporarily remove the numbers because somehow zig-bin 0.11 couldn't satisfy version constraints in makepkg.

sayo: that would check out, considering i pushed a new pkgrel with updated checksums (i always run updpkgsums before pushing) on mar 22, then they changed again on april 1st. brycehenley reported the checksums changing back on the 3rd, so they shouldn't change now. i've validated this by building using the current pkgbuild and it passes the latest pushed checksums. a temporary fix would be to just skip the integrity check if this issue persists, but this wouldn't be ideal.

tl;dr the checksums shouldn't change again until the next package release

Regarding the checksum validation failures, it may be related to an issue SourceHut had with archive checksums between March 22nd and April 1st:

https://lists.sr.ht/~sircmpwn/sr.ht-announce/%3CCRM6OWV7GTWL.27CDG91BBXGW%40taiga%3E