tag 402920 - unreproducible
clone 402920 -1
severity -1 serious
retitle -1 mplayer do not support nostrip/noopt and is in C [violates policy 
§10.1]
thanks

On Wed, Dec 13, 2006 at 05:46:12PM +0100, A Mennucc wrote:
> severity 402920 normal
> tag 402920 unreproducible
> thanks
> 
> Pierre Habouzit ha scritto:
> > Package: mplayer
> > Version: 1.0~rc1-2
> 
> your mplayer version is quite old; current one is 1.0~rc1-7

  read the damn report, I did the report from another machine. sorry I
did not fixed that.

> > Severity: serious
> 
> why? I checked into debian-policy 10.1 :
> http://www.debian.org/doc/debian-policy/ch-files.html
> > For this reason, it is recommended to support the 
> > standardized environment variable DEB_BUILD_OPTIONS.
> 
> DEB_BUILD_OPTIONS is a recommendation of policy, not a requirement.
> 
> I also found out that "debug" is not in the list of options.
> See http://bugs.debian.org/157131
> 
> I will update that to 'noopt'

  admitedly, but that's not wrt the name of the option, It's just that
thtis is the sole way to have a debug build of mplayer, that is more
than useful to generate useful backtraces and debug informations.

  you can feel free to consider this bug is not worth investigating, but
I may also consider that generating useful backtraces for you is not
worh the effort, and for the next bugs I'll just send stupid mails
"mplayer segfaults on foo" and let you deal with that alone.

  I do not care about the debug version a lot, I just wanted one with
debug symbols unstripped. But you're correct, you do not support
nostrip/noopt at all, and that's RC ! good catch.

> >   attach is the relevant build log part.
> >   the build was done on an x86 box (not the one I report the bug from).
> 
> I cannot rerpoduce this (and I tried on AMD64)

  maybe because, If you had read the bug report, you would have seen
that the machine I did the report from was not the machine I built the
package on. I did a build of the last package, with an x86 box. not an
amd64.

  givent that it's a register allocation failure it seems, that's no
wonder it works on amd64 that has plenty of'em available.

-- 
·O·  Pierre Habouzit
··O                                                [EMAIL PROTECTED]
OOO                                                http://www.madism.org

Attachment: pgpfpHpwS4hwC.pgp
Description: PGP signature

Reply via email to