I bought a new computer a couple of months ago. I removed windows 8 and did a hard disk install of Navigatrix. I've been trying to install git in order to install RTL-SDR I think I may have accidentally changed some setting. I keep getting the following error.

ketos@SVKetos:~$ sudo apt-get install git
[sudo] password for ketos:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package git

Any suggestions?

Thanks,

Tim

Did you sudo apt-get update?

If the culprit is not the missing update mentioned in Moe's answer above, check what version of NX you have installed. If it is not the latest (based on Ubuntu version 14.04) but an earlier one (based on Ubuntu 13.04) you may have to change the software repository as described in this post: viewtopic.php?p=3663#p3663 (or install the latest version instead) .

Hi Guys,

I have Navigatrix 0.5 installed. I tried installing some software from the software center and got a warning that the files were not trusted. I decided to try to switch servers to be able to get the software from a different source. This is when things started not working. I think I may have screwed something up when changing servers. Not sure how to get back where I started.

Just for fun I tried: sudo sed -i -e 's/archive.ubuntu.com\|security.ubuntu.com/old-releases.ubuntu.com/g' /etc/apt/sources.list

Then: sudo apt-get update

This gave the following results:

ketos@SVKetos:~$ sudo apt-get update
Get:1 http://linux.ntuoss.org raring Release.gpg [7,086 B]
Hit http://dl.google.com stable Release.gpg
Get:2 http://linux.ntuoss.org raring-updates Release.gpg [7,094 B]
Hit http://dl.google.com stable Release
Hit http://archive.canonical.com raring Release.gpg
Get:3 http://ppa.launchpad.net raring Release.gpg [316 B]
Hit http://labs.picotech.com picoscope Release.gpg
Get:4 http://linux.ntuoss.org raring-backports Release.gpg [7,096 B]
Ign http://extras.ubuntu.com raring Release.gpg
Get:5 http://linux.ntuoss.org raring-security Release.gpg [7,095 B]
Hit http://labs.picotech.com picoscope Release
Hit http://archive.canonical.com raring Release
Ign http://extras.ubuntu.com raring Release
Get:6 http://linux.ntuoss.org raring Release [7,082 B]
Hit http://doc.hausser.ch ubuntu-dha Release.gpg
Hit http://dl.google.com stable/main i386 Packages
Ign http://extras.ubuntu.com raring/main i386 Packages/DiffIndex
Get:7 http://ppa.launchpad.net raring Release.gpg [316 B]
Get:8 http://linux.ntuoss.org raring-updates Release [7,090 B]
Ign http://linux.ntuoss.org raring Release
E: GPG error: http://linux.ntuoss.org raring Release: The following signatures were invalid: NODATA 1 NODATA 2

Then tried again to install git:

ketos@SVKetos:~$ sudo apt-get install git
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package git

Thanks again for the help.

Tim

Can you check what source/repository server you currently have configured? In the Manta Menu -> Preferences select Package Manager which will start the Synaptic Package Manager (a GUI front-end to apt-get). Go to the Package Manager's Settings menu and click on Repositories:

In the dialogue that pops up check if Download from is set to Main server:

If not re-set it to Main server.

Close the dialogue and click the Reload button under the menu bar (all the way to the left (same as apt-get update). Once it's done, search for git or exit and try

again.

I went into the package manager and selected Main. I did the update and still have the following.

ketos@SVKetos:~$ sudo apt-get install git
[sudo] password for ketos:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package git

Thanks again for all the help.

Tim

Tim, I think Markus hit the nail on the head. The 13.04 repositories are biting us in the butt.

Navigatrix does a rolling release. Minor bug fixes, and a 'little re-arranging' in the backroom, that do not change functionality, don't warrant a version number bump. The powers that be decreed there are 'subversions', nx0.5(june), nx0.5(july), nx0.5(august), or whatever they were called. I think there were 3 or 4 'updated' ISOs in a 10 week period.

This all works fine, it keeps the distribution current and fresh, but it also prevents the illusion that one should update when there is no material reason to update. No increase in functionality, no reason to update; no increase in security, no reason to update, and so on.

For example, if I have version 0.5, and version 0.51, or 0.53 just came out. There is the false impression that our copy, my copy won't work as well as the new version. It is outdated. We see this all the time. We are trained to think this way. The newer version will work better...except when it doesn't change how it functions for your use. It's like getting another hammer because the new one has a yellow handle, and maybe some fluting on the side. It makes no sense, particularly when the only way to get the new yellow fluted hammer is to download the entire 2.3 gigabyte workshop.

I fall for this all the time. It is generally a waste of time.

Now, appearing to contradict my "There is no need to update" rant, you should update.

Your looking for packages in the 'raring' repositories rather than the 'trusty' repositories.

Powers greater than anyone in the Navigatrix community have yanked the raring repositories into oblivion.

It might be possible to hand-hack the source list and change raring to trustyinstall the 14 packages that go along with git. It is reasonable to assume this will not break anything. You could live dangerously and leave 'trusty' there, or revert back to 'raring'. Making changes to the core of the system (rather than add-ons to the system, like git) you might not be as fortunate.

...then again, you could just update the whole thing.

If you have split your installation into a root partition and a home partition, it is relatively painless. My personal machine and my test machine are same. One or two times a month I do a fresh re-install having cluttered up my machine with various bits of crap, tests, and screwups.

If I've littered my home partition with too much garbage, I'll rename my /home/moe directory to something else, re-install without formatting /home and keep my name. Then, afterwards, I can move data as needed to the new /home. When I think I have done what I've needed...delete all the garbage in the old, re-named, directory.

Thanks Moe!

That did the trick. I now have RTL-SDR installed and running. Now for the next little problem...

When I try to install aisdecoder I get the following error.

ketos@SVKetos:~/aisdecoder/build$ cmake ..
-- Build configuration: Release
CMake Warning at CMakeLists.txt:68 (message):
You do not have the development files for pulseaudio (DISABLE).


-- Configuring done
-- Generating done
-- Build files have been written to: /home/ketos/aisdecoder/build
ketos@SVKetos:~/aisdecoder/build$

I did sudo apt-get install libasound-dev libpulse-dev

I previously installed aisdecoder on the thumb drive version of Navigatrix about a year ago and it installed fine. I was under the impression that libpulse-dev was what it is looking for but I'm probably mistaken. Where do I find the development files for pulseaudio?

Thanks again for all the help.

Tim

Is this looking for

Try:

cmake clean ..

if that spits up

delete the aisdecoder directory
and unpack the archive again...
tar zxvf aisdecoder.tar.gz
cd aisdecoder
mkdir build
cd build
cmake ..

It could be residual configuration....

Thanks again Moe. As always you were right on the money.

Tim

Cool.

When you've had a chance to test drive the new software, let us know what you think.

I contacted Sean by email because I was getting an error when I tried to activate the DVB-T dongle. He asked "Can you put aisdecoder into /usr/local/bin or somewhere in the path?"

I tried sudo cd /usr/local/bin and then tried to install it in this directory but it failed. Any idea how to install aisdecoder in the /usr/local/bin path?

Thanks,

Tim

On Sun, Dec 14, 2014 at 11:07 PM, Tim B <[email protected]> wrote:

Thank you for the work you've put into the development of the rtl-sdr plugin.

I'm currently trying to install your plugin on my laptop running Navigatrix. I have rtl-sdr and aisdecoder installed and working. About a year ago I install both programs and use the following commands to pipe the output to OpenCPN.

rtl_fm -f 161966899 -g 40 -s 48k -r 48k /tmp/aisdata

./aisdecoder/build/aisdecoder -h 127.0.0.1 -p 10110 -a file -c mono -d -l -f /tmp/aisdata

The file /tmp/aisdata is a fifo

This works but it is very tedious getting the frequency right.

I installed your plugin last week and have been trying to figure out what I'm doing wrong. The GUI comes up in OpenCPN but when I tr to enable it, I get the following error.

execvp(aisdecoder, -h, 127.0.0.1, -p, 10110, -a, file, -c, mono, -d, -f, /dev/stdin) failed with error 2!

I'm not a programmer and I'm learning as I go so any assistance would be greatly appreciated.

Thanks,

Tim

Tim, I don't find any instructions for sudo make install.

I can sudo make the binary (aisdecoder) and the library (libaisdecoder.so.0.1.1, plus 2 symbolic links), but I've no idea where the author wants them put (yeah, in the path).

You might be able to just manually move them to the 'right' place, and sudo ldconfig to cast a magic spell, but I have no idea where the lbrary w/should go.

I'm trying to install linrad which is a software defined radio program. I'm running into the same issues that I had when I tried to install the AIS plugin for OpenCPN. I tried switching to trusty on the server as in the previous posts with no luck. I'm getting the following errors with out these files.

Missing or not working libraries (non fatal.)
For information, type ./configure --with-help

Not present: libportaudio.so
Not present: libsoft66.so
Not present: libftdi.so (needed for Soft66 and Elektor)
Not present: libbladeRF.so
Not present: libmirisdr.so
Not present: libairspy.so
Not present: libfdms1.so.1.0
Not present: libudev.so and/or libudev.h (Funcube ProPlus, Afedri USB)
Not present: libwd_dask.so Neded for PCIe-9842
Not present: libperseus-sdr.so
Not present: libvga.so (and/or missing headers)
Not present: libX11.so (and/or missing headers)

To compile for Linux you need either libX11.so or libvga.so
Can also not compile for Windows due to missing mingw or libraries.

Not enough packages on this system to compile anything.
Type this command: ./configure --with-help
ketos@SVKetos:~/linrad/linrad-04.03$

Any suggestions would be greatly appreciated.

Thanks,

Tim

It's a trail of bread crumbs, Tim

run It spits out a long list of additional packages/libraries that need to be installed. Some are .deb files, some are source that need to be compiled, some offer a choice of the two.

Pick through it. It seems like 20 separate jobs, but isn't. I'd still use two terminals, one with the initial output from the ./configure --with-help, and the other to actually do what the long list says, and then work your way through it.

...it's long, just not complicated (one chunk at a time), if you can keep your eyes from crossing.

Thanks again Moe, it's up and running.