Package Details: tikzit 2.1.6-1

Git Clone URL: https://aur.archlinux.org/tikzit.git (read-only, click to copy)
Package Base: tikzit
Description: Allows the creation and modification of TeX diagrams written using the pgf/TikZ macro library
Upstream URL: https://tikzit.github.io/
Licenses: GPL2
Submitter: alexmerry
Maintainer: hv15
Last Packager: haawda
Votes: 25
Popularity: 0.000000
First Submitted: 2010-05-10 21:27 (UTC)
Last Updated: 2020-08-19 17:20 (UTC)

Required by (0)

Sources (1)

Latest Comments

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

alexmerry commented on 2015-08-24 11:22 (UTC)

I just tried again with a clean working directory and up-to-date packages, and can't reproduce your issue. Could you try again after cleaning everything out of wherever you're creating the tikzit package?

alexmerry commented on 2015-07-23 07:39 (UTC)

Odd... I got that error before I changed how bison was called, but not in the released version. Could you paste the output of the following? pacman -Qo $(which bison)

alexmerry commented on 2015-07-22 21:35 (UTC)

The md5sum is correct. I suspect you're getting a 404 page or something from sourceforge, hence it not extracting. I've done a 1.1 release of tikzit from master on github (probably the last one that will ever happen), and I'm packaging that.

alexmerry commented on 2011-11-03 10:57 (UTC)

You'll need to rebuild tikzit - the libraries it depends on have been updated to incompatible versions. If tikzit were in a repo (like community), it would be rebuilt automatically, but because this is the AUR, you'll have to do it yourself.

<deleted-account> commented on 2011-11-03 05:51 (UTC)

Since the last system update, i got this error: $ tikzit tikzit: error while loading shared libraries: libgnustep-base.so.1.22: cannot open shared object file: No such file or directory $ tikzit tikzit: error while loading shared libraries: libpoppler-glib.so.6: cannot open shared object file: No such file or directory

alexmerry commented on 2010-12-03 12:58 (UTC)

I think I discovered what the issue was: the distribution package included the lex-generated .h files, but not the .m files. So there was probably a mismatch between the header and the source file. It should be fixed in 0.5.

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