Has anyone got this to work on any version of linux other than debian?
We dont use that outdated pos, I’ve have built from source, all deps are met, but the binary refuses to run, because it expects debian specific stuff like
~# piaware
01/16/2015 05:33:56 unable to run dpkg-query! can’t determine piaware package info
invalid command name “adept”
while executing
“adept send_log_message $text”
(procedure “logger” line 4)
invoked from within
“logger “unable to run dpkg-query! can’t determine $name package info””
(procedure “query_dpkg_name_and_version” line 5)
invoked from within
“query_dpkg_name_and_version piaware packageName packageVersion”
(procedure “load_piaware_config_and_stuff” line 5)
invoked from within
…snip…
I mean, like W T F ? who writes this stuff? It’s bad enough it wants TCL, but to require a specific distro??? and if its going to be so freaking anal, why did it not bail out at configure time…
Please FA, if you are going to support an operating system, support it, even if it means finding a programmer with a bloody clue.
I dont have the time or intent to butcher this thing just to make it run, if your programmer was competent he/she would have made it so in the first place.
It’s customized for Raspbian because that’s what FlightAware targets as their supported platform. It’s unreasonable to rant that it doesn’t work out of the box on a different platform. I’m sure that FlightAware would be happy to take specific, constructive bug reports for how it breaks on other platforms. (Your rant is neither).
What IS your target platform and architecture? You didn’t say!
Complaining about free software but not doing anything constructive to help is pretty bad form. The original source is here: github.com/mutability/piaware/t … an-package. While it is Debian-specific, much of the work I did there is work that you’ll want to do for packaging for other systems, e.g. putting logs in sensible places, reading config from /etc, not running as root.
FWIW based on your absolutely terrible bug report it actually just looks like a bug in how a lack of dpkg is handled; this is meant to log and continue anyway, but it’s broken because it tries to log before logging is properly set up. Probably unnoticed because it hasn’t been tested on an unsupported platform (who knew?!)
So if you’d like to put together a reasonable bug report that isn’t a ranty diatribe I’m sure I’d be able to work out a bugfix for you.
@ubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.10
Release: 14.10
Codename: utopic
@ubuntu:~$ uname -a
Linux ubuntu 3.16.0-25-generic #33-Ubuntu SMP Tue Nov 4 12:05:25 UTC 2014 i686 i686 i686 GNU/Linux
@ubuntu:~$ piaware -v
1.19-3
Is this proof enough that it works… There was even someone nice enough to document the steps needed to get it working http://pastebin.com/eKbm118F. I managed to get all this working within hours on an old Netbook after I found that my RasPi was having issues with its powersupply.
**OP: Do some serious research and, if you can still not get it working, ask a friendly question!! This choice of words and tone will not get you anywhere!!! **
I doubt our one-post-wonder will be back, but FWIW there’s a bugfix (specific to piaware-mutability, upstream will need a different fix) here: github.com/mutability/piaware/c … b90882e6d5
No idea if it works on the mystery target system for obvious reasons, but piaware works fine with that patch even after I disable dpkg temporarily.
Hi, new on this topic and very happy to be part of this group. I don’t if this discussion is still on going (seems to be sleeping sinc 2015) but I would need some help in order to perform the complet installation.
I changed the repository for dump1090 (the provided one is obsolete) and performed an almoust complet installation but finnaly faced an issue when launching: sudo piaware-config -user YOURFLIGHTAWAREUSERNAME -password.
Obviously I changed the username ;-).
The prompt is at that time: can’t find package Itcl …
Any idea about what I should do?
Regards.
