|
Moritz, This problem was reported upstream and has been worked on. Additionally it IS NOT a Xastir problem; it is a "Jasper is not going to be available" problem. The SOLUTION is for people to learn how to pull Xastir from CVS and build on each platform that they use. Why? Because it is ALREADY FIXED in the CVS available source code. Also note that Xastir is a HAM RADIO OPERATOR USE ONLY program. The Xastir team has _many Wiki's_ and numerous people willing to help those that ask for it nicely. Moritz, whatever version you are using is no longer valid unless you pulled it from CVS since 1800 UTC today (01June2016). Yes, the development is that active. The developers DO NOT create any packages for any distributions at all; the packages in the distributions are done by those that volunteer time out of very busy schedules. My suggestion to you, provided you are a Licensed Ham Radio Operator is that you join the Xastir mailing list / reflector at http://xastir.org/mailman/listinfo/xastir and also read over the Wiki's available via Xastir.org. David Aitcheson - KB3EFS ------------------------------------------------------------------ Colin, Is a process available to "kill" this bug so that Non-Hams do not get all choked up about the issue? The issue was resolved in CVS with-in a week to two weeks after initial report and has been extensively tested in Debian and Ubuntu (and others via emulators) along with numerous derivatives of each on a multitude of platforms. Dave KB3EFS ------------------------------------------------------------------ On 06/01/2016 12:51 PM, Debian Bug
Tracking System wrote:
Processing commands for control@bugs.debian.org:severity 818217 graveBug #818217 [src:xastir] xastir: Jasper removal Severity set to 'grave' from 'important'thanksStopping processing here. Please contact me if you need assistance. |