Package Details: tibia latest-1

Git Clone URL: (read-only, click to copy)
Package Base: tibia
Description: fast-paced free massively multiplayer online role-playing game
Upstream URL:
Keywords: cipsoft mmorpg
Licenses: custom
Submitter: Cameri
Maintainer: Cameri (TrialnError)
Last Packager: TrialnError
Votes: 13
Popularity: 0.000000
First Submitted: 2015-11-09 06:01
Last Updated: 2020-04-03 20:21

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

RaphaelCosta commented on 2018-02-06 12:08

I'll admit it wasn't as easy as I thought, but anyway do you want to merge this (minus the package name change, of course) or should I push the new package to the AUR?

EDIT: There's an issue with my patch regarding the generated .desktop icons if we rename the package to tibia-latest, in my clone I just reverted it to "tibia" with %s/_pkgname/pkgname/g.

Kuchiriel commented on 2018-01-31 16:02

@RaphaelCosta, exactly, besides the things you said, there are some points I would like to add.

Its easy to solve, just put in the pkgbuild the following things in the following order.

While on installation delete old non persistent data (saving map, configurations etc), if mkdir mkdir with -p flag for avoiding errors

If still want 775 and group do.

Execute usermod -a -G games $(id -u -n)

Or chmod -R 0777 /opt/Tibia to avoid permission issues

Problem solved

Please maintainer do it in the PKGBUILD.

RaphaelCosta commented on 2018-01-30 15:30

@Kuchiriel AND @TrialInError

Assuming there are no big changes, you delete the old souces (downloaded file from and run makepkg -s, it will fail because although the file from always has the same name, it extracts to a folder with a specific name (the tibia client's current version).

Unfortunately, tibia has some compatibility problems with Arch Linux (not sure about other distros) that require small patches to configuration files, the problem is that this PKGBUILD's .patch files include the exact path of the tarball as downloaded from and extracted with no additional flags, meaning we have to extract the tarball manually or run makepkg -s and wait as it fail every time in order to see the new name of the extracted file and edit the .patch files manually to refer to that new path so the package builds properly.

Resolving this issue is trivial, you just mv $extracted_path $static_path the tarball and use $static_Path in the patch files, it would require no maintenance whatsoever except that you would still need to pacaur/yaourt/other_helper -S tibia when the game fails to launch or if you were makepkg -s like the current maintainer likes to do: You would need to cd tibia && rm *tar && makepkg -s.

The BIG PROBLEM here is that Tibia is a game, I want to play, I play. The current PKGBUILD punishes me by saying I either need to go through several steps in order to play or I give up playing entirely until the maintainer "fixes" the package.

I've been trying to tell this to TrialInError for a few times now but I'm certain that this time my point got across, next time Tibia updates and requires manual intervention I'll push tibia-latest.

Kuchiriel commented on 2018-01-23 13:52

@TrialInError what is the exact path? We can patch manually? @RaphaelCosta There no automatic way to make this PKGBUILD? Or, how can we change PKBUILD to do what it is suposed to do without waiting for the maintainer?

RaphaelCosta commented on 2018-01-23 13:43

@karimi It's happening because we must wait several hours for TrialInError to update his package every time CIPSOFT releases a minor update. ;)

TrialnError commented on 2018-01-18 01:43

@Karimi: Happening because of new upstream release. Due to the hardcoded version number in patch files they will fail if the exact path cannot be resolved. The failing checksum is a similar indicator.

Karimi commented on 2018-01-17 23:24

I'm trying to install this package, but no matter what i do, the checksums don't match. and when i tell makepkg to skip checksums, instead i get some arcane prompt that i have no idea what to do. Any tips? Below are the lines i get for the situations mentioned.

==> Making package: tibia 11.54.6216-1 (Wed Jan 17 21:15:33 -02 2018) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found tibia-11.54.6216.tar.gz -> Found tibia-agreement.php -> Found 01_openssl102.patch -> Found 02_freetype.patch ==> Validating source files with sha256sums... tibia-11.54.6216.tar.gz ... FAILED tibia-agreement.php ... Passed 01_openssl102.patch ... Passed 02_freetype.patch ... Passed ==> ERROR: One or more files did not pass the validity check!

==> WARNING: Skipping verification of source file checksums. ==> Extracting sources... -> Extracting tibia-11.54.6216.tar.gz with bsdtar ==> Starting prepare()... [tibia] Generating desktop file... ok can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was:


|--- tibia-11.54.6216/ |+++ tibia-11.54.6216/


File to patch:

TrialnError commented on 2018-01-17 12:09

pacman's tool makepkg, which is the only supported tool for building packages from AUR, doesn't default to /tmp. Such behaviour is introduced by wrappers like pacaur or yaourt, but not pacman.

And as you're shaking your head about my working process in this case, I'm in the same position with yours. So not everyone's personal preference.

And again. Everyone can do with the PKGBUILD whatever they want (although such behaviour can be made more difficult if wrappers are used which download a snapshot everytime a package shall be built instead using a local PKGBUILD). This is only a recipe. If the update process is to slow (which it is sometimes), or bothering (like the issues you have with the current process), one can change the PKGBUILD to his liking. If someone thinks more people can benefit from it he is free to upload the PKGBUILD to the AUR. But by no means is the maintainer in a position such as the maintainer from the supported binary repos of Arch. No one needs to wait for him to update the PKGBUILD.

RaphaelCosta commented on 2018-01-17 09:49

Whereas a downloaded package named xyz.tar.gz, which wasn't deleted before (by mistake or whatnot (like using SRCDIR)) will get used again

So it won't install the new version if you have an older version downloaded? Well, both pacman and yaourt default to /tmp and at any pace deleting the old source is still a much better situation than the current one.

But yeah, that's entirely personal preference.

Everyone's personal preference is: I wake up, I want to play Tibia, I receive an annoying message saying "Your client is too old", I run "yaourt -S tibia or pacaur -S tibia" and Tibia magically updates.

I could see it as a bother for people if they download everytime a snapshot instead of cloning this repo

No, it's a bother for people when they need to go through several complicated steps in the morning to get their game to update. By the time you update this package several hours might have passed.

TrialnError commented on 2018-01-16 20:02

@RaphaelCosta: And disregarding the fact that -svn and -git packages work differently. Even if the cloned sources aren't deleted, you won't run into the problem with building an old version, as git fetch and the svn equivalent got invoked. Whereas a downloaded package named xyz.tar.gz, which wasn't deleted before (by mistake or whatnot (like using SRCDIR)) will get used again. There is no check involved, which compares with the upstream source.

And besides that, everyone can do with the PKGBUILD whatever they want. So if you think the idea is worth following you're free to do that. I told my point of view. The work involved on my side is minimal. I could see it as a bother for people if they download everytime a snapshot instead of cloning this repo and using git for fetching and applying changes. But yeah, that's entirely personal preference.

tl;dr: Introduce such a package if you want to. I have my doubts and therefor wouldn't maintain such a package.