Closed earwin closed 8 years ago
this is solid, @earwin thanks for separating the fairwaves configs into its own packaging and cleanup effort. looks good! last notes, are there any special installation instructions? how do we track the osmocom-fairwaves releases? also how has this been tested?
I'm not sure of the future of endaga-osmocom-fairwaves package. Releases? Will we even support it? If we're not using endaga ourselves, we don't exactly have any reason to. But that is solely my personal opinion reflecting what is known to me now. Your Kurtis should contact my Alexander and sort this out.
Fairwaves-specific software that we do support is available through vpn+repo that are visible from the bts. fwpkg update
does a selective apt-get update
on our repo.
I tested the installation, both on completely clean system and as upgrade, done as sudo apt-get install endaga-osmocom
(before the split). Remove/reinstall also work.
I did not test the split, as the current state of endaga-osmocom configs would work only on your hardware, which I have no access to.
Fairwaves-specific configs were tested in production on the station of the same model.
I did not do any extensive testing of your software itself.
okay, so noting really special for installation.
more details about the bts.type
issue? Can you execute the shell command endaga_db_get bts.type
?
Disregard this, these were old timestampless log records. gprsd still fails (with other message), but as I recon, it's still not fully adapted to osmocom, so it's legit.
Extracted fairwaves hardware-specific osmo configs into their separate tree and separate package.