My local Kannel 1.4.4 sources now have 18 patches in debian/patches/. I am managing them with "gbp pq". Unfortunately, "gbp pq import" in git-buildpackage 0.6.9 does not recognize the DEP-3 "Description" and "Author" headers, because it uses "git mailinfo". I have therefore reformatted the metadata of my patch in the following way, which I believe still complies with DEP-3. If you too can switch to this format, there is a small chance it might help me merge changes from Debian in the future. I'm not sure what to do about patch numbers in file names though -- they cannot match because 32_va-start-non-null.patch is neither applicable nor required in Kannel 1.4.4.
From: Kalle Niemitalo <kalle.niemit...@procomp.fi> Date: Tue, 9 Jun 2015 19:37:17 +0300 Subject: sqlite3: Use sqlite3_libversion, not sqlite3_version Using sqlite3_version[] causes a "has different size in shared object" warning at run time if the length of the version number has changed in the sqlite3 shared library. It is not clear whether anything worse will happen in addition to the warning, but we can avoid the problem altogether by calling sqlite_libversion() instead. Bug-Debian: http://bugs.debian.org/717728 Last-Update: 2015-06-09 --- gwlib/dbpool_sqlite3.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gwlib/dbpool_sqlite3.c b/gwlib/dbpool_sqlite3.c index 71e31f2..b735b08 100644 --- a/gwlib/dbpool_sqlite3.c +++ b/gwlib/dbpool_sqlite3.c @@ -86,7 +86,7 @@ static void *sqlite3_open_conn(const DBConf *db_conf) } info(0, "SQLite3: Opened or created database file `%s'.", octstr_get_cstr(conf->file)); - info(0, "SQLite3: library version %s.", sqlite3_version); + info(0, "SQLite3: library version %s.", sqlite3_libversion()); return db;
