projects / platform / core / security / cert-svc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 500fe90) | patch
Fix sqlite2 DB operations during the build & small spellchek fix 22/305522/5 accepted/tizen_8.0_unified accepted/tizen_unified accepted/tizen_unified_toolchain accepted/tizen_unified_x tizen_8.0 accepted/tizen/8.0/unified/20240208.163159 accepted/tizen/unified/20240208.163947 accepted/tizen/unified/toolchain/20240311.065521 accepted/tizen/unified/x/20240214.051933
authorTomasz Swierczek <t.swierczek@samsung.com>
Thu, 1 Feb 2024 12:28:10 +0000 (13:28 +0100)
committerTomasz Swierczek <t.swierczek@samsung.com>
Mon, 5 Feb 2024 06:53:27 +0000 (07:53 +0100)
commit1eab389030ae0107cd5af56a32da3f77d0d90760
tree9acc58c0b0d16740451064820f0cd0f10927a543tree | snapshot
parent500fe90081562b02a94f2ac18cd2cccac62405ffcommit | diff
Fix sqlite2 DB operations during the build & small spellchek fix

Now, if inserting certificates into DB fails, the shell script
that manages their insertion will cause GBS build to fail too.

Without this change, on Tizen 7.0+ the certs databse of cert-svc
was emtpy, becasue sqlite3 couldn't parse the sql script adding
each certificate AND GBS didn't fail due to the way sh script was
written.

Change-Id: I6a0266936b317a119dbe08fd3817883ab1b2fcec
etc/db/CMakeLists.txt diff | blob | history
etc/db/initialize_store_db.sh diff | blob | history
Domain: Security / Authentication;