Search Criteria
Package Details: mepo 1.3.3-1
Package Actions
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.000222 |
First Submitted: | 2021-11-15 10:23 (UTC) |
Last Updated: | 2024-10-12 17:46 (UTC) |
Dependencies (13)
- curl (curl-quiche-gitAUR, curl-http3-ngtcp2AUR, curl-gitAUR, curl-c-aresAUR)
- findutils (findutils-gitAUR, busybox-coreutilsAUR, findutils-selinuxAUR)
- geoclue (geoclue_fake-gitAUR)
- jq (jq-gitAUR)
- ncurses (ncurses-gitAUR)
- sdl2_gfx
- sdl2_image
- sdl2_ttf
- xorg-xwininfo
- zenity (qarma-gitAUR, zenity-gtk3AUR, zenity-gitAUR)
- sdl2 (sdl2-gitAUR, sdl2-compat-gitAUR) (make)
- zig (zig-0.10-binAUR, zig-dev-binAUR, zig-gitAUR, zig-binAUR, zigup-binAUR, zig-nightly-binAUR) (make)
- zig (zig-0.10-binAUR, zig-dev-binAUR, zig-gitAUR, zig-binAUR, zigup-binAUR, zig-nightly-binAUR) (check)
Latest Comments
« First ‹ Previous 1 2 3 4 Next › Last »
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
: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!
midv commented on 2023-08-17 08:36 (UTC)
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:I had to temporarily remove the numbers because somehow zig-bin 0.11 couldn't satisfy version constraints in makepkg.
hamblingreen commented on 2023-04-08 21:31 (UTC)
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
sayo commented on 2023-04-08 14:48 (UTC)
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
flylightning commented on 2023-04-04 03:52 (UTC) (edited on 2023-04-04 04:13 (UTC) by flylightning)
The checksum of downloaded mepo archive keep changing somehow. About several weeks ago, my downloaded mepo archive doesn't pass checksum check of
sha512sums=('bc65abf5d6fc4433d8b6ce4d7efa78f09239f70cc2ef816706ad81d5748132bcf3fa9ba50147cd7e633a9fd306fdb00e886b31b6645444b1b1e5906bf28e4eb7')
. I waited about a week later and remove the old archive and re-downloaded it, somehow it passed. Then today I see the comments and find out the checksum of newer downloads changed again. This is very weird and I have no idea why.All those mepo archive file I talked about are the same version from the same source. Unfortunately I already removed old files, otherwise we can compare those and see what's wrong.
hamblingreen commented on 2023-04-03 16:58 (UTC) (edited on 2023-04-03 16:59 (UTC) by hamblingreen)
brycehenley: that's embarrassing, i've updated the package sums and tested it myself now, the validity check should pass now. let me know if it doesn't and i can do some deeper debugging.
brycehenley commented on 2023-04-03 16:07 (UTC) (edited on 2023-04-03 16:10 (UTC) by brycehenley)
Validating source files failed
hamblingreen commented on 2023-03-22 23:37 (UTC)
got it, thank you for your detail. i've added the other two sdl packages as dependencies
m040601 commented on 2023-03-22 09:38 (UTC) (edited on 2023-03-22 10:20 (UTC) by m040601)
It does break things. As I have said previously, you need not just one, but all 3 of them. I've tested this again, after your PKGBUILD update.
pacman -Qi mepo
pacman -Rns sdl2_gfx
Ok. We understand and already know that.
Now let's remove the other 2. It doesnt matter which one first.
And then let's try to start mepo
Right. Let's put it back and restart mepo.
Restart mepo. No problems
Let's try to remove the other one.
And then start mepo
Put it back. Start mepo. No problem.
Actually, even in this PKGBUILD, I notice they used to be "run" dependencies. It was only with, https://aur.archlinux.org/cgit/aur.git/commit/?h=mepo&id=1b1d6c2c643c645b39b030d14bae383f2f47aabd
That this situaton was changed from
to
Can you still remember why ?
Also, as I can see in the mepo code repo it self, https://git.sr.ht/~mil/mepo/tree/master/item/src/sdlshim.zig
There are these mentions of "ttf" and "image". I'm not a programmer. Have zero knowledge of Zig.
I cant help any further. Just report you that it doesnt run on my system without them.
So you might want to talk with the mepo developer himself. To clarify what is and what is not a dependency of mepo. Which one is a "make" dependency. And which one is a "run" dependency.
Actually he is not very explicit about that either, https://mepo.milesalan.com/installguide.html. It only says it is "written in Zig" and that it "renders on SDL". There is mention of different packages for different Linux distros. But as far as I can se there is no "INSTALL.md" or a file specifically aimed at packagers, not users. A fle or document detailing what is needed to compile and/or run.
« First ‹ Previous 1 2 3 4 Next › Last »