Your message dated Wed, 19 Mar 2008 06:22:45 +1030
with message-id <[EMAIL PROTECTED]>
and subject line #329466 is not considered a bug upstream
has caused the Debian Bug report #329466,
regarding speex: should be able to read FLAC
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 [EMAIL PROTECTED]
immediately.)
--
329466: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=329466
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: speex
Version: 1.1.6-2
Severity: wishlist
I think it's a pity that the only file format the Speex encoder can read
is Microsoft's WAV, when FLAC is out there.
Would it be possible for the speexenc command to have (at least
optional) support for FLAC and Ogg FLAC files?
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-2-k7
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages speex depends on:
ii libc6 2.3.5-6 GNU C Library: Shared libraries an
ii libogg0 1.1.2-1 Ogg Bitstream Library
ii libspeex1 1.1.6-2 The Speex Speech Codec
speex recommends no packages.
-- no debconf information
--
[EMAIL PROTECTED]
OpenPGP 0xD9D50D8A
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Hi,
I doing some triage and preparing a new upload for speex.
Looking at this report, it is currently marked 'fixed-upstream',
which is a bit misleading, because upstream has stated that speex
should not have extra dependencies to support encapsulation formats.
That seems like the correct decision to me, speex is a codec, what
you wrap it in is up to the implementation. RIFF audio is as free
a format as the others you list, and if you could decode Ogg in half
a dozen lines of trivial code as well, perhaps it would have been
chosen for the trivial example instead. It seems totally appropriate
to expect more sophisticated transcoding to be done by higher level
applications.
That all happened over a year ago now, and there has been no further
discussion on this, so I'm closing this report too now in line with
the upstream resolution.
Sorry,
Ron
--- End Message ---
