It appears that adom doesn't play along with ncurses5-compat-libs after that package added symbol versioning with --with-versioned-syms. Hopefully we'll get a new ADOM build at some point (current ones target Debian 9 & Ubuntu 18.04), but until then, please build your ncurses5-compat-libs without versioned symbols. I'll probably need to add a fork of ncurses5-compat-libs to AUR, even though I really don't want to publish yet another ncurses-with-custom-configure-flag-subset package.
Search Criteria
Package Details: adom 1:3.3.3-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/adom.git (read-only, click to copy) |
|---|---|
| Package Base: | adom |
| Description: | A roguelike game with a quest-centric, plot driven structure |
| Upstream URL: | http://www.adom.de/ |
| Licenses: | custom: "adom" |
| Submitter: | DaNiMoTh |
| Maintainer: | luukko |
| Last Packager: | luukko |
| Votes: | 83 |
| Popularity: | 0.000000 |
| First Submitted: | 2007-12-15 12:36 (UTC) |
| Last Updated: | 2019-01-30 19:05 (UTC) |
luukko commented on 2021-12-05 09:08 (UTC)
luukko commented on 2018-06-17 20:05 (UTC)
@lietzu: it was actually the source URL that was changed -- the old download link resolved to a HTML page that, unsuprisingly, didn't pass the integrity check :)
lietzu commented on 2018-06-13 21:42 (UTC)
Looks like the upstream file has changed? The provided checksum fails to verify the integrity of the tar. Highly doubt I'm being targeted for something malicious, but I would like to hear if file integrity is broken for others.
chbinnc commented on 2015-10-10 01:41 (UTC) (edited on 2015-10-10 01:50 (UTC) by chbinnc)
@jdarch: I successfully run the game with:
# cd /usr/lib && ln -s libncursesw.so libncurses.so.5
According to the graphic version https://aur4.archlinux.org/packages/adom-noteye/, installing libtinfo from aur should also solves the problem https://aur4.archlinux.org/packages/libtinfo/
jdarch commented on 2015-10-06 20:58 (UTC)
The dependency is libncurses.so.5
luukko commented on 2015-09-13 05:43 (UTC)
@TrialnError: You are right, that makes no sense. It was just a copy-paste error from the adom-restricted PKGBUILD. Copy-paste rarely goes unpunished...
TrialnError commented on 2015-09-11 12:17 (UTC)
I didn't notice that change before. But why adding provides and conflicts to the PKGBUILD where it provides and conflicts its own pkgname?
I noticed this "enhancement" for various PKGBUILDS or requests to add those and argued against it.
Imo there is no much sense to use the logic, where package adom conflicts adom, just to provide adom...
luukko commented on 2015-08-18 07:26 (UTC)
@TrialnError: Thanks, I learned about this feature a while ago from your adom-noteye PKGBUILD :) I plan on implementing it for the next update.
TrialnError commented on 2015-08-17 12:39 (UTC)
Since pacman 4.2 it is possible to use architecture specific sources.
See for more information http://allanmcrae.com/2014/12/pacman-4-2-released/
Pinned Comments
luukko commented on 2021-12-05 09:08 (UTC)
It appears that adom doesn't play along with ncurses5-compat-libs after that package added symbol versioning with
--with-versioned-syms. Hopefully we'll get a new ADOM build at some point (current ones target Debian 9 & Ubuntu 18.04), but until then, please build your ncurses5-compat-libs without versioned symbols. I'll probably need to add a fork of ncurses5-compat-libs to AUR, even though I really don't want to publish yet another ncurses-with-custom-configure-flag-subset package.