On Sat, Jul 11, 2009 at 10:51:10AM +1000, Erik de Castro Lopo wrote:
> Hi all,
>
> I am the main upstream author of libsndfile and I am also a Debain
> Maintainer (ie not a DD).
>
> This bug is currently blocking the transition of libsndfile from
> unstable to testing.
This bug is indeed blocking the transition.
Version 1.0.20-1 was built succesfully, but the testsuite error
is now being ignored and the package built succesfully. It was
closed by the maintainer, but you asked to reopen it.
So the question is:
- Do you think it should migrate to testing as is or not?
Reason why you could think it should migrate:
- This bug affects the version in stable (1.0.17-4+lenny2) and/or
testing (1.0.18-2), and so is not a regression. If you
mark it as found in those version, it will migrate.
- It's not a release critical bug, it's only a minor functionaly
that's broken and it's mostly ussable even with this. You
could change the severity so it's not release critical.
Anyway, try to fix this bug, I see this in the various built logs:
mips:
Line 231: Actual SNR ( 57.4) > target SNR (-31.0).
arm:
Line 231: Actual SNR ( 0.0) > target SNR (-31.0).
hppa:
Line 231: Actual SNR ( 57.4) > target SNR (-31.0).
ia64:
Line 231: Actual SNR ( 58.7) > target SNR (-31.0).
mipsel:
Line 231: Actual SNR ( 57.4) > target SNR (-31.0).
powerpc:
Line 279: Actual SNR ( 59.3) > target SNR (-29.0).
alpha:
test_wrapper.sh: line 33: 20915 Floating point exception./floating_point_test
So this still looks like 2 bugs, and maybe it should get split in
2 bug reports.
If you want access to a certain arch, it's probably best
to mail the porter list for that arch. If you can make
a standalone test program for any of those issues I can
test them on the various arches for you, but it will
probably go faster if you can test things yourself.
Kurt
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
