10 Oct
2017
10 Oct
'17
3:36 a.m.
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 "UNNAMED PROJECT".
The branch, neels/subscr_vty has been updated
discards 1139b1a3ad54462aab9ee9fec728ca16bd58a550 (commit)
discards aec168e7b3ca472e08f8e949279425e4136b3379 (commit)
discards 3b30f04a517181315d644118f8513f977c7baebb (commit)
discards 66304c8ed487ac2a4b9f8e2263ab574e520e3fa2 (commit)
discards 67cbdfd935652532b812fd6933ac951634575c13 (commit)
discards 9a35f7f10601c9fc632cc6278088c651f4b4ced8 (commit)
discards 8c23f4f49ac485873423d9ad37459f3aab098dca (commit)
via 7a5d12ca717865de42f7be1942310956a1534871 (commit)
via 95101ce2c6330f7e16234906a5d30757e1ff122c (commit)
via 18db395475a9d21ce14ae3196d4c7c9fc1a554c1 (commit)
via 796f486dc976cbec82c5fbc09c6ec8c874469bba (commit)
via 4b9be928c238e88ceaa9c7093fd13f2bd4291a90 (commit)
via a8d831793a20e139be66660d3e4e3ea5dc734383 (commit)
via c31b4a341f4eb0f28c0121c240905ea1aac3e23a (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 (1139b1a3ad54462aab9ee9fec728ca16bd58a550)
\
N -- N -- N (7a5d12ca717865de42f7be1942310956a1534871)
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/osmo-hlr/commit/?id=7a5d12ca717865de42f7be194231095…
commit 7a5d12ca717865de42f7be1942310956a1534871
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Fri Oct 6 02:59:54 2017 +0200
implement subscriber vty, tests
Depends: libosmocore I1e94f5b0717b947d2a7a7d36bacdf04a75cb3522
Change-Id: I42b3b70a0439a8f2e4964d7cc31e593c1f0d7537
http://cgit.osmocom.org/osmo-hlr/commit/?id=95101ce2c6330f7e16234906a5d3075…
commit 95101ce2c6330f7e16234906a5d30757e1ff122c
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Fri Oct 6 18:24:56 2017 +0200
db_get_auth_data cosmetic TODO
Change-Id: I0dea71455025231a28205db663f4682bc7a4441e
http://cgit.osmocom.org/osmo-hlr/commit/?id=18db395475a9d21ce14ae3196d4c7c9…
commit 18db395475a9d21ce14ae3196d4c7c9fc1a554c1
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Mon Oct 9 23:12:57 2017 +0200
code undup: use db_bind_text() in db_get_auth_data()
To make the db_bind_text() error reporting mention "imsi", change the
DB_STMT_AUC_BY_IMSI to use a named parameter.
Change-Id: I49bd5eb78170cf4cdf8abb386c766d20d9f1cf73
http://cgit.osmocom.org/osmo-hlr/commit/?id=796f486dc976cbec82c5fbc09c6ec8c…
commit 796f486dc976cbec82c5fbc09c6ec8c874469bba
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Mon Oct 9 23:03:57 2017 +0200
fix db_update_sqn(): reset stmt in all error cases
Use the common db_bind_int64() so that the stmt bindings are cleared for any
errors and to get error logging for free.
On error with sqlite3_step(), log the SQL error message, and make sure the stmt
is cleared of bindings and reset.
After sqlite3_step(), verify that exactly one row was modifed, log and return
errors otherwise.
After this patch, the DB interaction closely matches the other (refactored) DB
functions.
Change-Id: I0d870d405e2e0a830360d9ad19f0a3f9e09d8cf2
http://cgit.osmocom.org/osmo-hlr/commit/?id=4b9be928c238e88ceaa9c7093fd13f2…
commit 4b9be928c238e88ceaa9c7093fd13f2bd4291a90
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Mon Oct 9 22:49:25 2017 +0200
code undup: use db_remove_reset() in db_auc.c
Change-Id: I32d728e2b8a9771421c097647aa0e060e29a601f
http://cgit.osmocom.org/osmo-hlr/commit/?id=a8d831793a20e139be66660d3e4e3ea…
commit a8d831793a20e139be66660d3e4e3ea5dc734383
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Mon Oct 9 17:51:13 2017 +0200
refactor db_get_auth_data return val
Adopt the error handling of the other db functions: return -ENOENT on unknown
subscriber and -EIO on SQL failure. Return 0 for no error, instead of the
number of rows modified.
Adjust the single caller: db_get_auc()
(and db_test.c).
Change-Id: I006f471962bdad95d00a3a4c41a28ebbc9740884
http://cgit.osmocom.org/osmo-hlr/commit/?id=c31b4a341f4eb0f28c0121c240905ea…
commit c31b4a341f4eb0f28c0121c240905ea1aac3e23a
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Tue Oct 10 02:25:00 2017 +0200
add db_subscr_update_aud_by_id(), complete db_subscr_delete_by_id()
Add ability to add and remove auc_2g and auc_3g table rows with
db_subscr_update_aud_by_id().
In db_subscr_delete_by_id(), make sure that when deleting a subscriber, also
all auth data associated with that user ID is removed as well. A newly created
subscriber must not obtain the same auth tokens just by getting the same id.
Depends: libosmocore Idf75946eb0a84e145adad13fc7c78bb7a267aa0a
Change-Id: Icb11b5e059fb920447a9aa414db1819a0c020529
-----------------------------------------------------------------------
Summary of changes:
hooks/post-receive
--
UNNAMED PROJECT