Package Details: matterhorn 50200.12.0-1

Git Clone URL: https://aur.archlinux.org/matterhorn.git (read-only, click to copy)
Package Base: matterhorn
Description: A terminal-based chat client for MatterMost
Upstream URL: https://github.com/matterhorn-chat/matterhorn
Licenses: BSD
Submitter: amaloz
Maintainer: amaloz
Last Packager: amaloz
Votes: 9
Popularity: 0.32
First Submitted: 2017-05-31 16:55
Last Updated: 2021-02-05 23:12

Latest Comments

1 2 3 4 Next › Last »

VannTen commented on 2020-12-19 16:30

I was already doing this.

I think I found the root cause though : I build aur packages in a clean chroot, and the PKGBUILD built haskell-dependencies that are in the official repositories (like xdg-basedir), Since ghc is not determinist, the official version was not the same than the one built during matterhorn build, hence the error.

I fixed this using arch-hs to generate another PKGBUILD, which correctly list dependencies and generate PKGBUILD for those not present in the arch repos. The downside is that you have to build those in order, but it works great.

alerque commented on 2020-12-19 12:13

@VannTen First, update your base system so that all Haskell packages are fresh (they get rebuilds often daily). Then actually rebuild this, not just reinstall it. Don't rely on makepkg or yay to do it for you, force it (e.g. with makepkg -Cf or yay --aur --rebuild -S matterharn).

VannTen commented on 2020-12-10 16:10

I get matterhorn: error while loading shared libraries: libHSxdg-basedir-0.2.2-8ecb76da6be77d73b9461eff4f8ad8ead6925c6836da9fc507f05fc3db6963a5-ghc8.10.2.so: cannot open shared object file: No such file or directory when trying to launch matterhorn after building it in a clean chroot.

I thought it was a dependencies mismatch, so I tried to bump the version (latest is 50200.11.0) but I get another error : matterhorn: error while loading shared libraries: libHSmatterhorn-50200.11.0-inplace-ghc8.10.2.so: cannot open shared object file: No such file or directory Which seems like a internal lib. Do you see the same result, or is it my system ?

balrog4k commented on 2020-06-03 13:49

Hi, package is broken now?

Resolving dependencies...
cabal: Could not resolve dependencies:
[__0] trying: matterhorn-50200.8.0 (user goal)
[__1] next goal: brick (dependency of matterhorn)
[__1] rejecting: brick-0.54 (conflict: matterhorn => brick>=0.52.1 && <0.53)
[__1] skipping: brick-0.53 (has the same characteristics that caused the
previous version to fail: excluded by constraint '>=0.52.1 && <0.53' from
'matterhorn')
[__1] trying: brick-0.52.1
[__2] next goal: base (dependency of matterhorn)
[__2] rejecting: base-4.14.0.0/installed-4.14.0.0 (conflict: brick =>
base<=4.13.0.0)
[__2] skipping: base-4.14.0.0 (has the same characteristics that caused the
previous version to fail: excluded by constraint '<=4.13.0.0' from 'brick')
[__2] rejecting: base-4.13.0.0, base-4.12.0.0, base-4.11.1.0, base-4.11.0.0,
base-4.10.1.0, base-4.10.0.0, base-4.9.1.0, base-4.9.0.0, base-4.8.2.0,
base-4.8.1.0, base-4.8.0.0, base-4.7.0.2, base-4.7.0.1, base-4.7.0.0,
base-4.6.0.1, base-4.6.0.0, base-4.5.1.0, base-4.5.0.0, base-4.4.1.0,
base-4.4.0.0, base-4.3.1.0, base-4.3.0.0, base-4.2.0.2, base-4.2.0.1,
base-4.2.0.0, base-4.1.0.0, base-4.0.0.0, base-3.0.3.2, base-3.0.3.1
(constraint from non-upgradeable package requires installed instance)
[__2] fail (backjumping, conflict set: base, brick, matterhorn)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: brick, base, matterhorn

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

alerque commented on 2020-04-27 17:14

@sachaz That doesn't sound like an error after building, that sounds like an error after building, then updating your system's Haskell packages. You need to recompile this after any changes to it's dependencies.

sachaz commented on 2020-04-27 11:53

Arch 5.6.6-arch1-1 matterhorn 50200.8.0-3

After building when I'm launching matterhorn i got:

matterhorn: error while loading shared libraries: libHSzlib-0.6.2.1-CYgtdz0O92NHvS2vBB2HG4-ghc8.8.3.so: cannot open shared object file: No such file or directory

amaloz commented on 2020-04-02 18:03

ah, yes, I was too quick. Hopefully now...

alerque commented on 2020-04-02 17:33

Hey again ... your last commit message suggests you meant to fix the provides line, but it's still there ;-) It should be deleted entirely as it is just the pkgname.

alerque commented on 2020-04-02 09:13

You can drop all the conflicts/provides lines from this package. See the wiki guidelines but in short they ask you not to provide anything that is identical to the package name, and the conflicts are resolved from the other packages.

kerl commented on 2020-03-24 09:34

It worked thanks! I'll think about checking the version next time ^^