Your message dated Wed, 18 Apr 2012 08:05:18 +0800
with message-id
<CAMr=8w7pt6wu4wh0gvrgboohsd421+bctytzeunfhc9m7fr...@mail.gmail.com>
and subject line Re: [Pkg-ime-devel] Bug#669079: [libchewing] dbg package not
usable when --enable-debug gets removed during build
has caused the Debian Bug report #669079,
regarding [libchewing] dbg package not usable when --enable-debug gets removed
during build
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
669079: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libchewing
Version: 0.3.3-4
Severity: grave
Hi, I'm blocking 0.3.3-4's migration to testing, because the changes
of removing --enable-debug will make libchewing3-dbg package not
usable. dh_strip can strip out debugging symbols to -dbg package so
there is no risk of leaking private data if the library is written
properly. If the debug symbols cannot be stripped correctly, then
please either remove the -dbg package or build the source twice with
different flags.
--
Regards,
Aron Xu
--- End Message ---
--- Begin Message ---
On Tue, Apr 17, 2012 at 14:35, KanRu Chen <kos...@debian.org> wrote:
> Aron Xu <happyaron...@gmail.com> writes:
>
>> Package: src:libchewing
>> Version: 0.3.3-4
>> Severity: grave
>>
>> Hi, I'm blocking 0.3.3-4's migration to testing, because the changes
>> of removing --enable-debug will make libchewing3-dbg package not
>> usable. dh_strip can strip out debugging symbols to -dbg package so
>> there is no risk of leaking private data if the library is written
>> properly. If the debug symbols cannot be stripped correctly, then
>> please either remove the -dbg package or build the source twice with
>> different flags.
>
> Note that I've add an -g to CFLAGS so there will be correct debug
> information attached.
>
> --enable-debug, though it's name might be confusing, is really only for
> developer for debugging purpose. It will write logs to /tmp thus leaking
> private data and shouldn't be enabled by default.
>
> Please close this bug if you agree.
>
> Cheers,
> --
> Kanru
Thanks for clarifying! Closing.
--
Regards,
Aron Xu
--- End Message ---
