Source: cutter-testing-framework
Version: 1.2.2-2
Severity: serious
>From my pbuilder build log:
...
gtkdoc-mkdb --module=cutter \
--source-dir=./../../cutter \
--output-format=xml \
--expand-content-files="" \
--main-sgml-file=main.sgml \
--sgml-mode --source-dir="../../gcutter"
--source-dir="../../cppcutter" --source-dir="../../gdkcutter-pixbuf"
--source-dir="../../soupcutter" `test "../.." != "../.." && echo
--source-dir="../../cutter"`
../../cppcutter/cppcut-message.h:31: warning: Section cppcut-message is not
defined in the cutter-section.txt file.
../../cppcutter/cppcutter.h:155: warning: Parameter described in source code
comment block but does not exist. MACRO: cppcut_message Parameter: format.
./tmpl/cut-console-diff-writer.sgml:23: warning: Field descriptions for struct
CutConsoleDiffWriter are missing in source code comment block.
./tmpl/cut-console-diff-writer.sgml:30: warning: Field descriptions for struct
CutConsoleDiffWriterClass are missing in source code comment block.
./tmpl/cut-logger.sgml:67: warning: Value descriptions for CutEnumError are
missing in source code comment block.
./tmpl/cut-logger.sgml:75: warning: Value descriptions for CutFlagsError are
missing in source code comment block.
./tmpl/cut-logger.sgml:83: warning: Value descriptions for CutLogColorize are
missing in source code comment block.
./tmpl/cut-logger.sgml:92: warning: Value descriptions for CutLogItemFlags are
missing in source code comment block.
./tmpl/cut-logger.sgml:106: warning: Value descriptions for CutLogLevelFlags
are missing in source code comment block.
./tmpl/cut-logger.sgml:123: warning: Field descriptions for struct CutLogger
are missing in source code comment block.
./tmpl/cut-logger.sgml:130: warning: Field descriptions for struct
CutLoggerClass are missing in source code comment block.
./tmpl/cut-string-diff-writer.sgml:23: warning: Field descriptions for struct
CutStringDiffWriter are missing in source code comment block.
./tmpl/cut-string-diff-writer.sgml:30: warning: Field descriptions for struct
CutStringDiffWriterClass are missing in source code comment block.
./tmpl/gcut-egg.sgml:75: warning: Field descriptions for struct GCutEggClass
are missing in source code comment block.
./tmpl/gcut-event-loop.sgml:36: warning: Field descriptions for struct
GCutEventLoopClass are missing in source code comment block.
./tmpl/gcut-glib-event-loop.sgml:23: warning: Field descriptions for struct
GCutGLibEventLoop are missing in source code comment block.
./tmpl/gcut-glib-event-loop.sgml:30: warning: Field descriptions for struct
GCutGLibEventLoopClass are missing in source code comment block.
./tmpl/gcut-process.sgml:75: warning: Field descriptions for struct
GCutProcessClass are missing in source code comment block.
./tmpl/soupcut-client.sgml:34: warning: Field descriptions for struct
SoupCutClientClass are missing in source code comment block.
./cutter-unused.txt:1: warning: 1 unused declarations.They should be added to
cutter-sections.txt in the appropriate place.
touch sgml-build.stamp
LANG=ja_JP.UTF-8 /usr/bin/ruby -I ../../misc /usr/bin/rd2 -r rd2refentry-lib.rb
--name=CUTTER --po=./ja.po ../../doc/cutter.rd.ja > cutter.xml.ja
/usr/bin/rd2:209:in `===': invalid byte sequence in US-ASCII (ArgumentError)
from /usr/bin/rd2:209:in `block in <main>'
from /usr/bin/rd2:209:in `each'
from /usr/bin/rd2:209:in `find'
from /usr/bin/rd2:209:in `<main>'
make[4]: *** [cutter.xml.ja] Error 1
make[4]: Leaving directory
`/tmp/buildd/cutter-testing-framework-1.2.2/doc/reference'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/tmp/buildd/cutter-testing-framework-1.2.2/doc'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/buildd/cutter-testing-framework-1.2.2'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp/buildd/cutter-testing-framework-1.2.2'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--
Daniel Schepler
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
