From: gitosis@osmocom.org Precedence: list To: osmocom-commitlog@lists.osmocom.org Date: Fri, 25 Apr 2014 10:56:27 GMT Message-ID: <201404251056.s3PAuRUE096765@git.osmocom.org> Subject: openbsc.git branch zecke/features/sms-db-changes updated. 0.13.0-365-g219ad38 Message: 1 This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)". The branch, zecke/features/sms-db-changes has been updated discards f3916187ea58896ed163faf217e842d3032b00f2 (commit) discards a9778c06ec691263a739606a5140ad119fa3ac68 (commit) discards 634d2071056ae3a8b38c2a2d251746d49fe0287a (commit) discards 7b3b6630774ca76bfc6702b52182aa856e113b7d (commit) discards 584932428601bdbb1bc89e957d6c8d07aded3e66 (commit) via 219ad38bc41e9a1c27ba326806a48e388c7f522d (commit) via 541f3da88be2d388d6610512e3dc8fb9b596694c (commit) via d0cef632951c71443aa8ef35a4d51739cf76b723 (commit) via d410820f2af163e128e13727ec422c487ce72dae (commit) via 3bf6b7d2c9155695263091615a98b18b08395170 (commit) via e9faa6f3a411e4fc7ff7968ee4be279b28296eec (commit) via 86decfb53ca4efff2548980e4bee7fd246198d93 (commit) This update added new revisions after undoing existing revisions. That is to say, the old revision is not a strict subset of the new revision. This situation occurs when you --force push a change and generate a repository containing something like this: * -- * -- B -- O -- O -- O (f3916187ea58896ed163faf217e842d3032b00f2) \ N -- N -- N (219ad38bc41e9a1c27ba326806a48e388c7f522d) When this happens we assume that you've already had alert emails for all of the O revisions, and so we here report only the revisions in the N branch from the common base, B. Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://cgit.osmocom.org/openbsc/commit/?id=219ad38bc41e9a1c27ba326806a48e388c7f522d commit 219ad38bc41e9a1c27ba326806a48e388c7f522d Author: Holger Hans Peter Freyther Date: Sat Mar 8 16:41:37 2014 +0100 db: Add testcase for the db migration. http://cgit.osmocom.org/openbsc/commit/?id=541f3da88be2d388d6610512e3dc8fb9b596694c commit 541f3da88be2d388d6610512e3dc8fb9b596694c Author: Holger Hans Peter Freyther Date: Fri Mar 7 18:17:22 2014 +0100 sms: Add code to migrate the database to the new schema This is mostly based on Alexander's migration code. The code adds transaction handling and some sanity checks and cleanups to the code. We made the decision to fork the sms_from_result method and freeze it to that version. This way sms_from_result can move forward without having to deal with legacy. http://cgit.osmocom.org/openbsc/commit/?id=d0cef632951c71443aa8ef35a4d51739cf76b723 commit d0cef632951c71443aa8ef35a4d51739cf76b723 Author: Alexander Chemeris Date: Tue Oct 8 03:17:32 2013 +0200 sms: Do not store received id in the SMS database. That was a bad idea from the very beginning. A visible result of this is a wrong SMS routing when you change subscriber extensions, while having queued SMS. It's also a very wrong thing from the code layering perspective. I think the next logical step should be to remove "receiver" pointer from the gsm_sms structure into a structure, special for the internal SMS queue. http://cgit.osmocom.org/openbsc/commit/?id=d410820f2af163e128e13727ec422c487ce72dae commit d410820f2af163e128e13727ec422c487ce72dae Author: Holger Hans Peter Freyther Date: Fri Mar 7 19:08:03 2014 +0100 db: Add testcase for storing/loading/comparing a sms Use the already created subscriber, create a sms and read it back from the subscriber. http://cgit.osmocom.org/openbsc/commit/?id=3bf6b7d2c9155695263091615a98b18b08395170 commit 3bf6b7d2c9155695263091615a98b18b08395170 Author: Holger Hans Peter Freyther Date: Tue Oct 8 03:17:30 2013 +0200 sms: Kill the sms->sender and use addr/ton/npi throughout the code This is an incompatible database schema change. Store the type of the address in the database for both the sender and the receiver. Currently it is possible to use SMPP to store a SMS and the NPI and TON will be lost on the delivery of the SMS. The schema is changed to make the delivery always use the right NPI/TON. This patch is not ready for the master branch as there is no upgrade path for the HLR yet. ----------------------------------------------------------------------- Summary of changes: debian/osmocom-gbproxy.init | 6 +++--- openbsc/src/libmsc/gsm_04_11.c | 2 ++ openbsc/tests/ctrl_test_runner.py | 43 +++++++++++++++++++++++++++++++++++++++ 3 files changed, 48 insertions(+), 3 deletions(-) hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)