Search Criteria
Package Details: xastir 2.2.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/xastir.git (read-only, click to copy) |
---|---|
Package Base: | xastir |
Description: | HAM RADIO - Full featured APRS Tracking/Information Reporting System |
Upstream URL: | http://www.xastir.org/ |
Keywords: | aprs gps ham radio |
Licenses: | GPL, LGPL |
Conflicts: | xastir-cvs |
Submitter: | Allan |
Maintainer: | not_anonymous |
Last Packager: | not_anonymous |
Votes: | 14 |
Popularity: | 0.000000 |
First Submitted: | 2008-12-19 03:45 (UTC) |
Last Updated: | 2023-12-03 15:26 (UTC) |
Dependencies (14)
- desktop-file-utils (desktop-file-utils-gitAUR)
- gdal (gdal-libkmlAUR, gdal-libkml-filegdbAUR, gdal-hdf4AUR, gdal-ecwAUR)
- graphicsmagick
- hamradio-menusAUR
- libax25AUR
- libxml2 (libxml2-gitAUR, libxml2-2.9AUR)
- libxpm (libxpm-gitAUR)
- openmotif
- perl (perl-gitAUR)
- python (python37AUR, python311AUR, python310AUR)
- shapelib
- autoconf (autoconf-gitAUR) (make)
- automake (automake-gitAUR) (make)
- festival (optional) – for speech systhesis
Latest Comments
1 2 3 4 Next › Last »
not_anonymous commented on 2022-02-14 22:11 (UTC)
Good catch....UPDATED
scres commented on 2022-02-13 07:48 (UTC) (edited on 2022-02-13 07:50 (UTC) by scres)
@minorsecond
makepkg -o, then comment out AM_INIT_AUTOMAKE in src/Xastir-Release-2.1.6/configure.ac, then makepkg -e
AM_INIT_AUTOMAKE is being invoked twice in there, no idea why. this is an upstream problem. I'll file it.
EDIT: Spoke too soon. this is fixed in the 2.1.8 release. https://github.com/Xastir/Xastir/pull/181
minorsecond commented on 2021-11-05 12:24 (UTC)
Xastir fails to build now. It dies after this error message:
configure.ac:35: error: AM_INIT_AUTOMAKE expanded multiple times
not_anonymous commented on 2020-05-19 22:55 (UTC)
Updated !
AxPU commented on 2018-02-22 21:40 (UTC)
Sorry for the long wait, I was and still am pretty swamped with work currently. Anyhow xastir does now build without issues here with the current xorgproto - No need for an update of the PKGBUILD. Can this be confirmed? Any issues left that need to be taken care of?
privong commented on 2018-02-21 14:14 (UTC)
There's now an updated xorgproto version which includes Print.h. I was able to successfully compile/install xastir after updating xorgproto.
not_anonymous commented on 2018-02-20 18:19 (UTC) (edited on 2018-02-20 18:19 (UTC) by not_anonymous)
Please see "xastir-fix" in the aur repo. It has the needed changes to "fix" the recent issues involved. This new package, xastir-fix, is meant to be a temporary replacement package. Hopefully the upstream issues with printproto/xorproto will be fixed and this package here (xastir) will be usable/useful again.
not_anonymous commented on 2018-02-15 22:55 (UTC)
1) Get the archlinux packager to remove printproto from the "conflicts" field of the xorgproto package BECAUSE the files from the older printproto package are NOT included in his package.
2) Get him, others or even yourself to package up the older printproto package so the missing files can be placed into the includes file-system-hierarchy.
( IF the archlinux packager does not "fix" the xorgproto package, YOU could consider creating your own with the change as outlined in no. 1 above.)
simona commented on 2018-02-15 13:22 (UTC) (edited on 2018-02-15 13:23 (UTC) by simona)
I might be able to recover "X11 / extensions / Print.h" from a previous version of arch (my oldest local backup) but even assuming that it works I still have to figure out what the software problem is with missing the Xorg side service. Although it may not work only something related to the printing.
not_anonymous commented on 2018-02-14 23:35 (UTC)
X11/extensions/Print.h (the missing file) was supplied by the "printproto" package. That has been removed from archlinux's binary repos and "replaced/provides" with the "xorgproto" package which does NOT contain that file.......sigh. (i.e. This will not compile and will give the error simona mentions herein; unless the host-system hasn't been updated recently....double sigh.)
AxPU ... perhaps you should "bitch-this" upstream ?
1 2 3 4 Next › Last »