Re: toulbar2: another try ?
Hi, lets see again
there is an extra space in VCS-fields, triggering a lintian warning
>> W: toulbar2-dbgsym: debug-file-with-no-debug-symbols usr/lib/debug/.build-id/63/769cbd8ba978f09766bcd677a4c0036429d701.debug
>Couldn't find a trace of this file.
you need to build with RelWithDebInfo to avoid that issue.
also please try to enable hardening
export DEB_BUILD_MAINT_OPTIONS = hardening=+all
http://debomatic-amd64.debian.net/distribution#unstable/toulbar2/0.9.8-1/lintian
update std-version to 3.9.8
regenerate doxygen documentation at build time
>> control: owner -1 !
>> control: tags -1 moreinfo
>
>Didn't get these two. I looked for owner and tags fields in
>debian/control and could not find any.
nothing, usually it means
"I'll take care of this package", but you didn't open a bug, so they didn't work :)
>I prefer to stick to Release mode. RelWithDebInfo compiles with -O2 -g
>and is roughly 2% slower than Release (-O3). Yes, it's not big but it's
>guaranteed. A debugging version is easy to compile for those who want.
ok, up to you then.
(You might try to build with -O3 -g, but I'm really not sure about what you will
have there!) feel free to experiment and report back.
>Explanation added. Basically, we do the tests before releasing and the
>tests (which may be long) include a timeout that will fail on slow
>machines (eg. on a 2GHz ARMv7 Cortex M15). Would need to change the
>testing logic to remove the timeout and I prefer not to.
you might want to exclude some test on some architectures, having a testsuite is good, because
it might fail on other debian derivatives (e.g. Ubuntu), where a different toolchain/flags
are used.
I'm not asking about a 10 hours testsuite, but a few tests are indeed something we like
>> copyright:
>Should be hopefully Ok now.
not completely
P: toulbar2 source: unversioned-copyright-format-uri http://dep.debian.net/deps/dep5
the url is not correct (please look at debomatic to find the correct link)
please add a watch file:
https://wiki.debian.org/debian/watch
(if possible)
let me know when you have a new package
(and please don't override the git history, if you want to have a clean history, you can recreate the git repo
once the package gets accepted if you want)
cheers,
G.
Reply to: