Package Details: tinyfugue 5.0b8-5

Git Clone URL: https://aur.archlinux.org/tinyfugue.git (read-only, click to copy)
Package Base: tinyfugue
Description: a flexible, screen-oriented MUD client, for use with any type of MUD
Upstream URL: http://tinyfugue.sourceforge.net/
Keywords: mud
Licenses: GPL3
Conflicts: tinyfugue-git, tinyfugue-patched
Submitter: None
Maintainer: eigenfire
Last Packager: eigenfire
Votes: 15
Popularity: 0.66
First Submitted: 2008-07-29 23:11
Last Updated: 2020-07-26 03:14

Pinned Comments

eigenfire commented on 2020-07-25 18:45

I test PKGBUILDs in a clean chroot using `makepkg` ONLY.

If you encounter a build error using an AUR helper or anything other than `makepkg`, try to replicate the issue using `makepkg` only.

If the issue does not occur using only `makepkg`, then you've countered a bug in your helper that needs to be reported to that helper's developer.

I will not add per-helper edge case handling to a PKGBUILD, nor will I support helper-based issues.

Latest Comments

1 2 Next › Last »

eigenfire commented on 2020-07-26 03:14

This should resolve the build issue on Manjaro. :)

eigenfire commented on 2020-07-25 19:15

Hope that works out for you. Just understand that `tinyfugue-git` has been mangled pretty badly in the name of extra features, some of which aren't fully functional.

EvilBenFranklin commented on 2020-07-25 19:11

Got me, then. Must be some difference between "pure" Arch and the Manjaro spin on it.

FWIW, I was able to get tinyfugue-git to build and install without issues. Thanks for taking a look anyway.

eigenfire commented on 2020-07-25 19:06

And in fact I just built/installed it with `pamac-cli` on Arch, and it went just fine.

eigenfire commented on 2020-07-25 18:57

I just built/installed with `yay -Syyu` and it went without a hitch. ¯\_(ツ)_/¯

EvilBenFranklin commented on 2020-07-25 18:51

Thanks for the reply; I took pamac out of the equation and run it through yay -Syyu and got the same results, so I'm not sure what's going on here. I totally get that makepkg works, but if it won't build through AUR tools, that's going to be a headache for some.

Per the build errors, the step it seems to be failing on is creating the binary in the user's local cache; since the tools tend to run in fakeroot/sudo, perhaps this is part of the issue? I am unfortunately not great with code just yet, so this is admittedly an educated guess based on what I do know.

Build errors: https://pastebin.com/imHzx6x6


eigenfire commented on 2020-07-25 18:45

I test PKGBUILDs in a clean chroot using `makepkg` ONLY.

If you encounter a build error using an AUR helper or anything other than `makepkg`, try to replicate the issue using `makepkg` only.

If the issue does not occur using only `makepkg`, then you've countered a bug in your helper that needs to be reported to that helper's developer.

I will not add per-helper edge case handling to a PKGBUILD, nor will I support helper-based issues.

eigenfire commented on 2020-07-25 18:40

`makepkg` works, but `pamac` breaks on the same system and the same PKGBUILD. Thus, `pamac` seems to be doing something that breaks an otherwise functional build system. The issue is internal to `pamac`. As I am not a Manjaro user, I have little internal knowledge of `pamac`; I would suggest that you consult with the `pamac` devs to see what `pamac` is doing that `makepkg` is not.

EvilBenFranklin commented on 2020-07-24 20:33

I keep hitting a build error during the make install phase. Not sure what's going on here as it is actually creating directories as necessary, but keeps returning "no such file/directory" and "cannot create" file errors. Permissions maybe?

Error messages here: https://pastebin.com/EbM0PAtp


eigenfire commented on 2020-07-21 11:18

Thanks for keeping this running up until now!