This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Stuart Baggs stuart at bluewave.imThank you for all your help. I have managed to get OML sync now from a nanoBTS and the network is up. The problem now is that even though I have added my IMSI to the sqlite3 DB, it still give an auth REJECT. Not sure what database name openBSC used by default (or if sqlite even supports multiple databases). Does anyone know how I can get ths to auth based on the entries I have put into sqlite. Thanks, Stuart On 10 Apr 2010, at 14:09, Holger Freyther wrote: > On Saturday 10 April 2010 13:34:39 Stuart Baggs wrote: >> Ok I entered git reset --hard 0.9.0 but when I issue a fresh "git pull" I >> get this error: >> >> root at gateway:~/openbsc# git pull >> You are not currently on a branch, so I cannot use any >> 'branch.<branchname>.merge' in your configuration file. >> Please specify which branch you want to merge on the command >> line and try again (e.g. 'git pull <repository> <refspec>'). >> See git-pull(1) for details. >> >> Is there a tar.gz file of the 0.9.0 version of openbts? I am really keen to >> get involved in the project but I simply cannot understand how GIT works >> and no mattter how many tutorials I read it is still clear as mud. > > Hi Stuart, > > git can be hard to understand at first but with a basic cheat sheet and just > using a handful commands you should be just fine. > > What most likely happened for you is you typed some of the bisect commands I > wrote without actually knowing what they will do and what you will have to do. > What git bisect does is it go away from your default branch to a unnamed > temporary branch to jump in the history... > > Now when you type "git pull" it is first fetching objects from the default > remote (origin) and then tries to merge with the remote branch that you are > tracking... The problem is you are currently not on a branch (as the command > tells you) and so it refuses to merge. > > All you want to type is "git bisect reset" to go back to before you started > the bisect. which brings you back to the master branch.. > > >