By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 1149

Summary:	Build issue: tdesvn FTBFS with "not a string literal error".
Product:	TDE	Reporter:	Francois Andriot <albator78>
Component:	non-core programs	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED FIXED
Severity:	major	CC:	bugwatch, darrella, slavek.banko
Priority:	P5
Version:	3.5.13 [Trinity]
Hardware:	All
OS:	Linux
Compiler Version:		TDE Version String:
Application Version:		Application Name:
Attachments:	Fix "not a string literal" errors in tdesvn Fix using ascii() in log messages

Description Francois Andriot 2012-08-05 06:01:51 CDT

Many error which look like:

/home/albator/rpmbuild/BUILD/BUILD.mga2.x86_64/applications/kdesvn/src/svnqt/cache/LogCache.cpp:190:83: erreur: le format n'est pas une chaîne littéral
e et pas d'argument de format [-Werror=format-security]

Comment 1 Francois Andriot 2012-08-05 06:02:34 CDT

Created attachment 759 [details]
Fix "not a string literal" errors in tdesvn

Comment 2 Slávek Banko 2014-01-06 11:40:24 CST

Created attachment 1841 [details]
Fix using ascii() in log messages

The patch has been pushed to GIT in hash 104a8598.

Just worries me now using method "ascii()". Especially in the cases: ".TOUTF8().data())).ascii()". Already several times use ascii() was the reason of problems.

Proposed patch attached.

Comment 3 Slávek Banko 2014-01-26 08:59:43 CST

Comment on attachment 759 [details]
Fix "not a string literal" errors in tdesvn

Already pushed to GIT in hash 104a8598.

Comment 4 Slávek Banko 2014-01-26 09:00:37 CST

Comment on attachment 1841 [details]
Fix using ascii() in log messages

Already pushed to GIT in hash 63892af8.