Package Details: mepo 1.3.3-1

Git Clone URL: https://aur.archlinux.org/mepo.git (read-only, click to copy)
Package Base: mepo
Description: Fast, simple, and hackable OSM map viewer for Linux
Upstream URL: https://git.sr.ht/~mil/mepo
Licenses: GPL3
Submitter: renehsz
Maintainer: hamblingreen
Last Packager: hamblingreen
Votes: 9
Popularity: 0.000533
First Submitted: 2021-11-15 10:23 (UTC)
Last Updated: 2024-10-12 17:46 (UTC)

Latest Comments

1 2 3 4 Next › Last »

dkaparis commented on 2024-10-06 20:25 (UTC)

I have successfully built the current 1.3.3 release with some changes.

The updated PKGBUILD is available at https://git.kaparis.name/AUR/mepo.

dkaparis commented on 2024-09-26 08:12 (UTC)

The package does not build for me currently:

==> Extracting sources...
  -> Extracting mepo-1.2.1.tar.gz with bsdtar
==> Starting build()...
/xxx/build/mepo/src/mepo-1.2.1/build.zig:14:27: error: no field named 'path' in union 'Build.LazyPath' 
        .source_dir = .{ .path = "scripts" },
                          ^~~~
/usr/lib/zig/std/Build.zig:2171:22: note: union declared here
pub const LazyPath = union(enum) {
                     ^~~~~
referenced by:
    runBuild__anon_8819: /usr/lib/zig/std/Build.zig:2116:27
    main: /usr/lib/zig/compiler/build_runner.zig:301:29
    remaining reference traces hidden; use '-freference-trace' to see all reference traces
==> ERROR: A failure occurred in build().
    Aborting...

Current zig 0.13.0-1 is installed as a dependency, I can't seem to find a 0.11 zig version in repositories or aur.

m040601 commented on 2024-08-26 19:13 (UTC) (edited on 2024-08-26 19:31 (UTC) by m040601)

Big changes, https://git.sr.ht/~mil/mepo/refs says:

Codebase Updated to Build Against Zig 0.13.0

I also tested the PKGBUILD "mepo-git" https://aur.archlinux.org/packages/mepo-git and it currently fails.

@hamblinggreen

Maybe you want to adopt that "mepo-git" PKGBUILD ?

Its maintainer seems absent:

 Registration date:  2020-04-25 (UTC)
 Last Login:      2022-08-05 (UTC)

It would be nice if both maintainers of "mepo" and "mepo-git" would cooperate and share work. For consistency, to avoid reduplicating efforts, and have more eyeballs following this project.

hamblingreen commented on 2023-09-01 05:20 (UTC)

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

m040601 commented on 2023-09-01 01:54 (UTC)

Can also confirm it is compiling and working now again

QuietApe commented on 2023-08-29 20:55 (UTC)

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

m040601 commented on 2023-08-27 22:09 (UTC) (edited on 2023-08-27 22:20 (UTC) by m040601)

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.

hamblingreen commented on 2023-08-26 15:17 (UTC)

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.

QuietApe commented on 2023-08-26 13:08 (UTC) (edited on 2023-08-26 13:14 (UTC) by QuietApe)

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 ?

hamblingreen commented on 2023-08-17 17:09 (UTC)

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!