Re: [Xastir] upgrade

[Lee Bengston]

On Sun, May 6, 2018 at 9:52 AM, C.L. Hollahan  wrote:

> Right now I am running Ubuntu on a RasPi 2 with Xastir 2.0.6. What is the
> best way to update to the latest version, uninstall and get latest from
> Git, or is there an update script I can run?
>
> ​What version of Ubuntu?  Currently the Wiki as well as my build script
support Ubuntu 16.04 (and earlier), but not the current 18.04.​  If you're
on 18.04 I would follow the manual installation notes in the Xastir wiki to
install from Git in version 16.04 because chances are the prerequisite
package names haven't changed.  There's also a section of the installation
notes that discusses what Tom R. said about moving from a binary
installation to a source installation.

Lee - K5DAT
___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir

Re: [Xastir] upgrade

[Tom Russo]

On Sun, May 06, 2018 at 09:52:48AM -0500, we recorded a bogon-computron 
collision of the  flavor, containing:
> Right now I am running Ubuntu on a RasPi 2 with Xastir 2.0.6. What is the 
> best way to update to the latest version, uninstall and get latest from Git, 
> or is there an update script I can run?

If you've installed from a binary package from Ubuntu, yeah, the best you can
do is uninstall and recompile from Git.  There is no upgrade path
from binary installs to source installs --- they install to different places
(binary packages usually install to /usr, source usually installs to 
/usr/local).

You will also have to modify all your config files to make them point at
/usr/local instead of /usr.  There are tons of paths in the files
in .xastir/config that have paths to things like maps and setup files that
you'll need to update.  If you've got a lot of custom configuration and maps
already, you'll want to edit those config files.  If you DON'T have a lot of
configuration set up already, the easiest thing to do is just rename .xastir
to something else, and let your new xastir install create a new .xastir 
directory and start over with your set-up.

There's a script that can keep you up-to-date with git once you've got a source
install, but it really amounts to little more than:

  git pull
  ./bootstrap.sh
  mkdir -p build
  cd build
  ../configure
  make
  sudo make install

so it is not even flexible enough to deal with all versions of linux, so I
generally suggest that you just follow the system-specific install instructions
on the wiki.

-- 
Tom RussoKM5VY
Tijeras, NM  

 echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]

___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir

Re: [Xastir] Upgrade / Update 1.98 to 1.99 CVS

[Curt, WE7U]

On Fri, 10 Sep 2010, Dean Groe wrote:

I am puzzled as to why I would bother to make after configure already told me 
that it was old, that my src was not updating?


Yea.  Once configure tells you the version number and it's wrong
there's no need to go further.


FWIW, it appears that the problem was due to CVS not updating source.  I 
downloaded source and built in a different directory and it worked OK.


Of course, that is not how this is supposed to work ideally, but that is what 
was needed this time.


Probably becase you tried the STABLE or RELEASE tags and those
options are sticky, as Jerry mentioned.  Jerry wrote:


 Use 'cvs update -r HEAD'  instead of STABLE or RELEASE. The use of
 any tags in an update is sticky. You get what you asked for in
 this case.


So if you had issued that command against your original directory
you probably would have been able to then issue the cvs update
command and gotten the latest CVS HEAD sources.  Perhaps you still
have that directory around and can try it.

--
Curt, WE7U. http://www.eskimo.com/~archer
   APRS:  Where it's at!http://www.xastir.org
  Lotto:  A tax on people who are bad at math. - unknown
Windows:  Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me:  I picked the coordinate system!
___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

Re: [Xastir] Upgrade / Update 1.98 to 1.99 CVS

[Tom Russo]

On Tue, Sep 14, 2010 at 10:29:03AM -0700, we recorded a bogon-computron 
collision of the curt.w...@gmail.com flavor, containing:
 On Fri, 10 Sep 2010, Dean Groe wrote:
 
  I am puzzled as to why I would bother to make after configure already told 
  me 
  that it was old, that my src was not updating?
 
 Yea.  Once configure tells you the version number and it's wrong
 there's no need to go further.
 
 
  FWIW, it appears that the problem was due to CVS not updating source.  I 
  downloaded source and built in a different directory and it worked OK.
 
  Of course, that is not how this is supposed to work ideally, but that is 
  what 
  was needed this time.
 
 Probably becase you tried the STABLE or RELEASE tags and those
 options are sticky, as Jerry mentioned.  Jerry wrote:
 
   Use 'cvs update -r HEAD'  instead of STABLE or RELEASE. The use of
   any tags in an update is sticky. You get what you asked for in
   this case.
 
 So if you had issued that command against your original directory
 you probably would have been able to then issue the cvs update
 command and gotten the latest CVS HEAD sources.  Perhaps you still
 have that directory around and can try it.

What you want to do is use the -A option to CVS update.  According
to the documentation:

  Use the -A option  to  reset  any  sticky  tags,  dates,  or  -k
  options.  (If you get a working file using one of the -r, -D, or
  -k options, cvs remembers the corresponding tag, date, or  kflag
  and  continues  using it on future updates; use the -A option to
  make cvs forget these specifications, and retrieve the  ``head''
  version of the file).  Does not reset sticky -k options on modi-
  fied files.

So simply doing cvs update -A in the checkout directory will undo the
stickiness and retrieve the HEAD version -- no need to use -r HEAD.  From 
that point forward, all updates in that directory will continue to update to 
the latest.

As Jerry and Curt say, using -r at all makes the tag sticky, and all 
subsequent cvs updates merely update to the latest with that tag.  Since we 
only move RELEASE tags after the very rare releases, that means they'll usually 
do nothing.  We don't move STABLE tags all that often.

After clearing sticky tags with -A, watch for update lines that start with C 
--- these indicate a problem with the checkout (conflict) that usually result 
in a mangled file that will produce compilation errors.  Simply remove the 
mangled file that is listed with C and redo the update.  The latest, clean 
version of the file will be retrieved after a message that it was lost.
This is especially a problem if you've done any personal editing of source
files between updates.

-- 
Tom RussoKM5VY   SAR502   DM64ux  http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236http://kevan.org/brain.cgi?DDTNM
 The truth will set you free, but first it will piss you off.

___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

Re: [Xastir] Upgrade / Update 1.98 to 1.99 CVS

[Dean Groe]

 

  FWIW, it appears that the problem was due to CVS not updating source.  I 
  downloaded source and built in a different directory and it worked OK.
 
  Of course, that is not how this is supposed to work ideally, but that is 
  what 

  was needed this time.
 
 Probably becase you tried the STABLE or RELEASE tags and those
 options are sticky, as Jerry mentioned.  Jerry wrote:
 
   Use 'cvs update -r HEAD'  instead of STABLE or RELEASE. The use of
   any tags in an update is sticky. You get what you asked for in
   this case.
 
 So if you had issued that command against your original directory
 you probably would have been able to then issue the cvs update
 command and gotten the latest CVS HEAD sources.  Perhaps you still
 have that directory around and can try it.

Understood, and agreed.  
Going back down memory lane, the reason that I eventually threw my hands up and 
tried the STABLE and RELEASE tags, was because cvs update was not working on 
it's own.  The existing src was not being updated, thus configure indicating 
the 
older version.  


You get what you asked for in this case.
This does beg a question, and I realize that I am asking this without 
researching... So is 1.9.8 the current Stable release?  I assumed that it was 
1.9.9  .  


I do still have the original src directory, so if I can find some time, that 
would be an interesting experiment.  


Thanks 

Dean  KD4TWJ  


  

___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

Re: [Xastir] Upgrade / Update 1.98 to 1.99 CVS

[Dean Groe]

--
Hmm, the above would all happen as shown in the event that entering
'cvs update' effectively did nothing.

What happens if you do the following at the command line in a new
blank directory?

cvs -d:pserver:anonym...@xastir.cvs.sourceforge.net:/cvsroot/xastir login
(just hit enter when prompted for a password after the above command)

cvs -d:pserver:anonym...@xastir.cvs.sourceforge.net:/cvsroot/xastir co xastir

cd xastir

./bootstrap.sh

mkdir build

cd build

../configure


The above just downloads a fresh copy of 1.99 and runs with it.

Regards,

Lee - K5DAT
Murphy, TX

--

Yes, it appears that CVS update was not working against the previous 1.9.8 CVS 
based updated source.  As you may have seen in my previous messages, that is 
the 
suspicion that I have had.  


As expected, the new fresh src build in a different directory did work.  
Thankfully, 1.9.9 came up with my existing config options intact.  Of course, I 
did have the important files backed up. 


I was surprised to see that my existing Tiger 2008 shapefiles looked a little 
different.  The road layer(s) looked a little different.  I like it, it is 
looks 
better.  


I may have a chance to take it for a drive tomorrow, to confirm that everything 
else (interfaces) works OK.  


Maybe one day I will have a chance to play around with the OSM stuff.  

Thanks


Dean  KD4TWJ 


  

___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

Re: [Xastir] Upgrade / Update 1.98 to 1.99 CVS

[Jerry Stueve]

On Thu, Sep 9, 2010 at 9:19 PM, Dean Groe warpedspe...@yahoo.com wrote:

 And we are back.

 I finally had another chance to work on this tonight.  Summary - Same
 result.

 With cvs update I decided to try forcing the STABLE and then the RELEASE
 tags,
 but each time, no difference.

 Use 'cvs update -r HEAD'  instead of STABLE or RELEASE. The use of any tags
in an update is sticky. You get what you asked for in this case.


 Each time -
 bootstrap works fine.
7) Removing autom4te.cache directory...
6) Running aclocal...
5) Running autoheader...
4) Running autoconf...
3) Running automake...
2) Checking for 'mkinstalldirs'... Found!
1) Generating derived language files.
 Bootstrap complete.

 configure gives me this:
 checking for a BSD-compatible install... /usr/bin/install -c
 checking whether build environment is sane... yes
 checking for a thread-safe mkdir -p... /bin/mkdir -p
 checking for gawk... gawk
 checking whether make sets $(MAKE)... yes

 Configuring xastir 1.9.8

 ... etc

 And there we have it.  I cannot get this thing past 1.9.8 .

 Any ideas?  What have I missed?

 Thanks

 Dean  KD4TWJ




 ___
 Xastir mailing list
 Xastir@lists.xastir.org
 http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

Re: [Xastir] Upgrade / Update 1.98 to 1.99 CVS

[Curt, WE7U]

On Sun, 5 Sep 2010, Dean Groe wrote:


The make install seems to be working OK.  I get a new 1.98
/usr/local/bin/xastir with today's date each time I go through with the
process.

cvs update does not generate any errors and claims to be updating, although it
runs through pretty quick.  Should I see individual files being transferred? I
am not FWIW.


Two possible problems, one is that you're starting up the old
version still.

The second is that you need to run ./bootstrap.sh before
configure if you're updating from CVS.  That creates a brand-new
configure for you among other things, then configure builds
brand-new Makefiles for you.

To successfully run bootstrap.sh you'll need autoconf and automake
installed (developer tools, but not particularly large ones).

--
Curt, WE7U. http://www.eskimo.com/~archer
   APRS:  Where it's at!http://www.xastir.org
  Lotto:  A tax on people who are bad at math. - unknown
Windows:  Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me:  I picked the coordinate system!
___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

Re: [Xastir] Upgrade / Update 1.98 to 1.99 CVS

[F4EIR]

 Hello,

i'm new but i can try tu find a way.

Can you search a xastir executable anywhere on your mobile. delete them 
and try a new update.


73
Arnaud
F4EIR

Le 05/09/2010 18:44, Dean Groe a écrit :

All this recent traffic regarding upgrading old versions, plus about a half hour
of time this AM that no one was trying to get my attention, inspired me to try
the update from 1.98 to 1.99 on my mobile PC.


I am running Debian Lenny on that one.  Xastir was originally installed from
CVS, so I figured this should be a no brainer


Both README.CVS and Notes:CVS had me believing that I should just be able to
cvs update and su, then make install, and I should be at 1.99 .

Well, that did not work so well.  I still had 1.98 .

So then I took a look at the Debian Lenny HowTo, and decided that I should do
the full routine with the bootstrap, configure, and make steps too.

Still no joy, still 1.98 .

The make install seems to be working OK.  I get a new 1.98
/usr/local/bin/xastir with today's date each time I go through with the
process.


cvs update does not generate any errors and claims to be updating, although it
runs through pretty quick.  Should I see individual files being transferred? I
am not FWIW.


What am I missing?

Thanks

Dean  KD4TWJ




___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir





___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

Re: [Xastir] Upgrade / Update 1.98 to 1.99 CVS

[Bob Nielsen]

A make clean is probably also needed.  The update-xastir script will handle 
everything for you.

Bob, N7XY

On Sep 5, 2010, at 10:54 AM, Curt, WE7U wrote:

 On Sun, 5 Sep 2010, Dean Groe wrote:
 
 The make install seems to be working OK.  I get a new 1.98
 /usr/local/bin/xastir with today's date each time I go through with the
 process.
 
 cvs update does not generate any errors and claims to be updating, 
 although it
 runs through pretty quick.  Should I see individual files being transferred? 
 I
 am not FWIW.
 
 Two possible problems, one is that you're starting up the old
 version still.
 
 The second is that you need to run ./bootstrap.sh before
 configure if you're updating from CVS.  That creates a brand-new
 configure for you among other things, then configure builds
 brand-new Makefiles for you.
 
 To successfully run bootstrap.sh you'll need autoconf and automake
 installed (developer tools, but not particularly large ones).
 
 -- 
 Curt, WE7U. http://www.eskimo.com/~archer
   APRS:  Where it's at!http://www.xastir.org
  Lotto:  A tax on people who are bad at math. - unknown
 Windows:  Microsoft's tax on computer illiterates. - WE7U.
 The world DOES revolve around me:  I picked the coordinate system!
 ___
 Xastir mailing list
 Xastir@lists.xastir.org
 http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

Re: [Xastir] Upgrade / Update 1.98 to 1.99 CVS

[Curt, WE7U]

On Sun, 5 Sep 2010, Bob Nielsen wrote:


A make clean is probably also needed.  The update-xastir
script will handle everything for you.


Thanks for that.

Also, if you're running update-xastir or doing

cvs update;./bootstrap.sh;./configure

manually to keep your system up-to-date, make sure to install
automake and autoconf on your system.  Those are used by
bootstrap.sh to create the new configure script.  This becomes
important anytime we change the configure.ac or acinclude.m4 files.

--
Curt, WE7U. http://www.eskimo.com/~archer
   APRS:  Where it's at!http://www.xastir.org
  Lotto:  A tax on people who are bad at math. - unknown
Windows:  Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me:  I picked the coordinate system!
___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

Re: [Xastir] Upgrade / Update 1.98 to 1.99 CVS

[David Flood]

 after the cvs update, did you do ./bootstrap followed by 
./configure?  Those two command get the system ready for make...if 
that works then follow that by sudo make install


So the sequence should look a little like this:

cvs update
output of that command
./bootstrap
should get 5 or 6 lines
./configure
should get a lot of output followed by a chart of yes and no's
make
compiles the program
sudo make install
will prompt for root password and install things...


Dave
KD7MYC

On 9/5/2010 9:44 AM, Dean Groe wrote:

Both README.CVS and Notes:CVS had me believing that I should just be able to
cvs update and su, then make install, and I should be at 1.99 .

Well, that did not work so well.  I still had 1.98 .



___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

Re: [Xastir] Upgrade / Update 1.98 to 1.99 CVS

[Dean Groe]

--

Message: 4
Date: Sun, 5 Sep 2010 10:54:38 -0700 (PDT)
From: Curt, WE7U curt.w...@gmail.com
To: Xastir - APRS client software discussion xastir@lists.xastir.org
Subject: Re: [Xastir] Upgrade / Update 1.98 to 1.99 CVS
Message-ID: alpine.lnx.2.00.1009051052480.16...@wapiti.we7u.net
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

On Sun, 5 Sep 2010, Dean Groe wrote:

 The make install seems to be working OK.  I get a new 1.98
 /usr/local/bin/xastir with today's date each time I go through with the
 process.

 cvs update does not generate any errors and claims to be updating, although 
it
 runs through pretty quick.  Should I see individual files being transferred? I
 am not FWIW.

Two possible problems, one is that you're starting up the old
version still.

The second is that you need to run ./bootstrap.sh before
configure if you're updating from CVS.  That creates a brand-new
configure for you among other things, then configure builds
brand-new Makefiles for you.

To successfully run bootstrap.sh you'll need autoconf and automake
installed (developer tools, but not particularly large ones).

--

Thanks for the reply Curt.

As mentioned in my original message, with the second attempt, I did also 
perform 
the bootstrap, configure, and make routines.  I still ended up with a newer 
1.98 xastir executable. 


And that is the only xastir executable on the system under /usr/ .  I suspect 
that there is one under the ~xastir/src directories too, but I know that I am 
calling /usr/local/bin/xastir.  


Regarding the CVS update process.  I suspect that may be part of the problem.  
I 
did not see any files being transferred. 

I am guessing that ~xastir/src/CVS/Entries is the log of what happened with the 
CVS update?  If it is, I can tell you that there are no entries newer than 22 
March 2010.  

The date of both  the ~xastir/src/CVS/Entries and  ~xastir/src/CVS/Entries.Log 
files is today, but no updated information inside.  I know that there have been 
significant updates since 1.98, so that is why I am puzzled.  


Or, have I assumed FAR too much.  MUST I do a complete re-install to move up to 
1.99?  I have assumed that a CVS update and re-compile would get me there. 


Thanks

Dean 


  

___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

Re: [Xastir] Upgrade / Update 1.98 to 1.99 CVS

[David A Aitcheson]

Dave,

You are 99% spot on!  Except . . .

On 09/05/2010 01:16 PM, David Flood wrote:
  after the cvs update, did you do ./bootstrap followed by
 ./configure?  Those two command get the system ready for make...if
 that works then follow that by sudo make install

 So the sequence should look a little like this:

 cvs update
 output of that command
 ./bootstrap
 should get 5 or 6 lines
 ./configure
 should get a lot of output followed by a chart of yes and no's
 make
 compiles the program
 sudo make install
 will prompt for root password and install things...

This password (on most *nix operating systems) is the _users_ password. 
Not the root password.

 Dave
 KD7MYC

 On 9/5/2010 9:44 AM, Dean Groe wrote:
 Both README.CVS and Notes:CVS had me believing that I should just be
 able to
 cvs update and su, then make install, and I should be at 1.99 .

 Well, that did not work so well.  I still had 1.98 .
Dave
KB3EFS
___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

Re: [Xastir] Upgrade / Update 1.98 to 1.99 CVS

[Bob Nielsen]

One more step (as I posted earlier:

On Sep 5, 2010, at 3:03 PM, David A Aitcheson wrote:

 Dave,
 
 You are 99% spot on!  Except . . .
 
 On 09/05/2010 01:16 PM, David Flood wrote:
 after the cvs update, did you do ./bootstrap followed by
 ./configure?  Those two command get the system ready for make...if
 that works then follow that by sudo make install
 
 So the sequence should look a little like this:
 
 cvs update
 output of that command
 ./bootstrap
 should get 5 or 6 lines
 ./configure
 should get a lot of output followed by a chart of yes and no's

make clean

 make
 compiles the program
 sudo make install

This will remove the existing binary files and cause them to be rebuilt from 
the updated source code.  

Or just run ./xastir-update and let it do everything for you.

Bob, N7XY

___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir