[Xastir-dev] Developer CVS
I'm having trouble with Developer CVS. I can do a cvs update from Anon CVS, but not Developer CVS. I can't do a cvs -n -q update from Devel-CVS either. I've been trying to do this for a couple of days. Perhaps they are either taking away resources from Devel-CVS or they are keeping it busy locally with migrations to SVN and others. $ cvs -n -q update cvs3.sourceforge.net: Connection refused cvs [update aborted]: end of file from server (consult above messages if any) $ cvs update cvs3.sourceforge.net: Connection refused cvs [update aborted]: end of file from server (consult above messages if any) -- Curt, WE7U.http://wetnet.net/~we7u APRS Wiki: http://info.aprs.net/ ___ Xastir-dev mailing list Xastir-dev@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir-dev
Re: [Xastir] GeoTiffs from mrsid files
This has worked First of all obtain the software to convert mrsid to geotiff from the Lizardtech site. follow the complete instructions here http://www.paulnorman.ca/blog/2011/03/converting-mrsid-to-geotiff/ (some commands are different if using Debian, particularly the PATH commands) With that Geotiff convert to appropriate datum (help required here from the expert) gdalwarp: gdal command to convert from one datum and projection to another -s_srs is source datum and projection using the EPSG codes. Code 28355 is GDA94, MGA zone 55 The maps are actually in WGS84, UTM Zone 55, but it's only a 2 or 3 metre difference and I knew where to find the GDA codes gdalwarp -s_srs EPSG:28355 -t_srs EPSG:4326 8130s.tif 8130s_lat.tif Then those files had 3 samples per pixel instead of 1 and this is attended to by rgb2pct.py 8130s_lat.tif /usr/share/xastir/maps/tif/8130s_lat.tif copying it into the xastir directory as I went. final result here http://www.flickr.com/photos/36563247@N07/8002767769/in/photostream ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Is there anyone left running Xorg server 1.7.5?
The bug in Xorg-server was fixed long ago, but the workaround remains in Xastir. Unfortunately, this is not a work-around that can be tested at configure time and disabled --- the bug is in the X server, not the client, and one cannot know at compile time whether Xastir will be used with an X server that has the bug. Thus we're all stuck with the workaround, even if we're not using an X server that has that bug. perhaps just add configure _option_ ? if someone is affected, he will just recompile with that option enabled (i.e. --with-broken-xorg ). given dynamics of xastir releases i assume such work-around will suffice for next 10 years ;) -- ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Is there anyone left running Xorg server 1.7.5?
On Wed, Sep 19, 2012 at 07:04:03PM +0200, we recorded a bogon-computron collision of the curi...@bwv190.internetdsl.tpnet.pl flavor, containing: The bug in Xorg-server was fixed long ago, but the workaround remains in Xastir. Unfortunately, this is not a work-around that can be tested at configure time and disabled --- the bug is in the X server, not the client, and one cannot know at compile time whether Xastir will be used with an X server that has the bug. Thus we're all stuck with the workaround, even if we're not using an X server that has that bug. perhaps just add configure _option_ ? if someone is affected, he will just recompile with that option enabled (i.e. --with-broken-xorg ). given dynamics of xastir releases i assume such work-around will suffice for next 10 years ;) :) Yes, a configure option is reasonable, and had occurred to me. It would be nice, however, to remove dead code rather than just #ifdef it. Xastir is a fairly unreadable mess due to the number of ifdefs that are peppered around it in an attempt to make it compatible with every single incompatible release of ImageMagick, various buggy versions of lesstif, and so on and so on. If there's even a single person who is actually using this one single buggy version of Xorg, then a configure-time option is reasonable, but my guess is that there aren't any more of these buggy servers out there. -- Tom RussoKM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236http://kevan.org/brain.cgi?DDTNM And, isn't sanity really just a one-trick pony anyway? I mean all you get is one trick, rational thinking, but when you're good and crazy, oooh, oooh, oooh, the sky is the limit! --- The Tick ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Is there anyone left running Xorg server 1.7.5?
Tom, What if in the bootstrap or configure script a test for Xorg==1.7.5 was done and if true an errorexit was generated with a message to upgrade xorg in order to continue? Else continue. I am running Xorg 1:7.6+12ubuntu1 here so I am in the clear. 73 Dave KB3EFS On 09/19/2012 12:42 PM, Tom Russo wrote: Is anyone here still running Xorg-server version 1.7.5, which was released in 2010? If not, it's time to remove a bad workaround in Xastir that was stuck in to deal with that single buggy version of X server. Back around the end of 2010, xorg-server version 1.7.5 got released and was adopted as the default in some distros. This version had a motif-crippling bug that caused Xastir (and all other Motif programs) to become unusable when the contextual menu was pulled up --- the cursor would become trapped in the Xastir window, and could only be released by killing Xastir from another screen (remote login or virtual terminal). Xastir was patched to deal with this, but there was an unpleasant side-effect: the contextual menus no longer stay up when you click the right button, you have to hold the right button down now. The bug in Xorg-server was fixed long ago, but the workaround remains in Xastir. Unfortunately, this is not a work-around that can be tested at configure time and disabled --- the bug is in the X server, not the client, and one cannot know at compile time whether Xastir will be used with an X server that has the bug. Thus we're all stuck with the workaround, even if we're not using an X server that has that bug. So, does anyone still have Xorg 1.7.5 installed on the systems they use for Xastir? This is the only version of X that ever had the problem, and if folks are no longer stuck with the broken server, we should unbreak Xastir so that contextual menus go back to working the way they did before xorg-server 1.7.5 was released. There's talk of having a 2.0.2 release soon (we haven't had a formal release since 2010), and this would be a good thing to fix before then. -- David A Aitcheson david.aitche...@gmail.com Go Green! Print this email only when necessary. ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
[Xastir] Welcome to our newest Admin
We've just added Tom Russo as Admin on the Xastir project, which makes three admins total: Chuck Byam Curt Mills Tom Russo Feel free to contact any of the three (with preference towards Curt or Tom due to availability) with any admin issues on the project that come up. -- Curt, WE7U.http://wetnet.net/~we7u APRS Client Capabilities: http://wetnet.net/~we7u/aprs_capabilities.html ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Is there anyone left running Xorg server 1.7.5?
On Wed, 19 Sep 2012, Tom Russo wrote: So, does anyone still have Xorg 1.7.5 installed on the systems they use for Xastir? I'm running xorg-x11-server-7.6_1.10.4 There's talk of having a 2.0.2 release soon (we haven't had a formal release since 2010), and this would be a good thing to fix before then. Yep. Real Soon Now to use one of my favorite Jerry Pournelle sayings. -- Curt, WE7U.http://wetnet.net/~we7u APRS Device Capabilities: http://wetnet.net/~we7u/aprs_device_capabilities.html ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
