Package Details: matterhorn 90000.0.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: alerque
Last Packager: alerque
Votes: 10
Popularity: 0.000000
First Submitted: 2017-05-31 16:55 (UTC)
Last Updated: 2024-03-28 00:29 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

alerque commented on 2020-04-27 17:14 (UTC)

@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 (UTC)

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 (UTC)

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

alerque commented on 2020-04-02 17:33 (UTC)

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 (UTC)

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 (UTC)

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

amaloz commented on 2020-03-23 20:52 (UTC)

Fixed. Thanks for the heads up!

clydedroid commented on 2020-03-23 20:39 (UTC)

kern, I had the same issue as you, and was able to resolve by updating the PKGBUILD to point at the newest version, 50200.7.0. Hope that helps!

kerl commented on 2020-03-23 17:06 (UTC)

Hi, I'm having some trouble building matterhorn. Cabal complains about not being able to resolve some dependencies:

==> Starting build()...
Config file path source is default config file.
Config file /home/martin/.cabal/config not found.
Writing default configuration to /home/martin/.cabal/config
Downloading the latest package list from hackage.haskell.org
Resolving dependencies...
cabal: Could not resolve dependencies:
[__0] next goal: matterhorn (user goal)
[__0] rejecting: matterhorn-50200.7.0 (constraint from user target requires
==50200.6.0)
[__0] trying: matterhorn-50200.6.0
[__1] next goal: time (dependency of matterhorn)
[__1] rejecting: time-1.9.3/installed-1.9..., time-1.10, time-1.9.3,
time-1.9.2, time-1.9.1, time-1.9 (conflict: matterhorn => time>=1.6 && <1.9)
[__1] trying: time-1.8.0.4
[__2] next goal: base (dependency of matterhorn)
[__2] rejecting: base-4.13.0.0/installed-4.1... (conflict: time => base>=4.7
&& <4.13)
[__2] rejecting: 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, matterhorn, time)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: matterhorn, base, time


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

I'm not sure I understand where this issue comes from. If that helps: I'm not using haskell myself and it seems that none of the AUR packages I have depend on haskell either so I guess the only haskell libraries I have on my system should be installed by pacman from the official repositories as dependencies for other packages. Am I the only one facing this issue? Is there something wrong with my haskell setup? Thanks!

amaloz commented on 2019-12-02 18:58 (UTC)

I integrated in your changes and pushed. Thanks!

I agree that it's still not perfect; for example, build still requires downloading packages.