Your message dated Sun, 22 Jul 2007 17:57:25 -0700
with message-id <[EMAIL PROTECTED]>
and subject line please binNMU pyvorbis (fixes #424441)
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: pyvorbis
Version: 1.3-1.2
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs

hi,

while doing an archive wide package rebuild your package failed to build from
source for the following reason:

 > package init file 'src/__init__.py' not found (or not a regular file)
 > running build_ext
 > building 'vorbis' extension
 > creating build
 > creating build/temp.linux-i686-2.4
 > creating build/temp.linux-i686-2.4/src
 > gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O2 -Wall -Wstrict-prototypes 
 > -fPIC -DVERSION="1.3" -I/usr/include -I/usr/include -I/usr/include/python2.4 
 > -c src/vorbismodule.c -o build/temp.linux-i686-2.4/src/vorbismodule.o
 > gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O2 -Wall -Wstrict-prototypes 
 > -fPIC -DVERSION="1.3" -I/usr/include -I/usr/include -I/usr/include/python2.4 
 > -c src/pyvorbisfile.c -o build/temp.linux-i686-2.4/src/pyvorbisfile.o
 > src/pyvorbisfile.c:266: warning: function declaration isn't a prototype
 > gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O2 -Wall -Wstrict-prototypes 
 > -fPIC -DVERSION="1.3" -I/usr/include -I/usr/include -I/usr/include/python2.4 
 > -c src/pyvorbiscodec.c -o build/temp.linux-i686-2.4/src/pyvorbiscodec.o
 > gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O2 -Wall -Wstrict-prototypes 
 > -fPIC -DVERSION="1.3" -I/usr/include -I/usr/include -I/usr/include/python2.4 
 > -c src/pyvorbisinfo.c -o build/temp.linux-i686-2.4/src/pyvorbisinfo.o
 > gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O2 -Wall -Wstrict-prototypes 
 > -fPIC -DVERSION="1.3" -I/usr/include -I/usr/include -I/usr/include/python2.4 
 > -c src/vcedit.c -o build/temp.linux-i686-2.4/src/vcedit.o
 > gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O2 -Wall -Wstrict-prototypes 
 > -fPIC -DVERSION="1.3" -I/usr/include -I/usr/include -I/usr/include/python2.4 
 > -c src/general.c -o build/temp.linux-i686-2.4/src/general.o
 > creating build/lib.linux-i686-2.4
 > creating build/lib.linux-i686-2.4/ogg
 > gcc -pthread -shared build/temp.linux-i686-2.4/src/vorbismodule.o 
 > build/temp.linux-i686-2.4/src/pyvorbisfile.o 
 > build/temp.linux-i686-2.4/src/pyvorbiscodec.o 
 > build/temp.linux-i686-2.4/src/pyvorbisinfo.o 
 > build/temp.linux-i686-2.4/src/vcedit.o 
 > build/temp.linux-i686-2.4/src/general.o -lvorbis -lvorbisfile -lvorbisenc -o 
 > build/lib.linux-i686-2.4/ogg/vorbis.so
 > Checking for Ogg ... success
 > Checking for Vorbis ... success
 > Wrote Setup file
 > You must have the Ogg Python bindings
 > installed in order to build and install
 > these bindings. Import of ogg._ogg failed.
 > make: *** [build-stamp] Error 1

The Full Build log is available and can be viewed at:

 http://people.debian.org/~lucas/logs/2007/05/15/00_Failed_1/
 
bye,
        - michael


--- End Message ---
--- Begin Message ---
On Wed, Jul 18, 2007 at 12:00:50PM +0200, Pierre Habouzit wrote:
>   I know I should provide a full binNMU list for python2.5 related
> packages, but at least this one is needed to fix the RC bug #424441.
> Probably other will follow.

Actually, the fix for #424441 is to binNMU pyogg rather than pyvorbis.  I've
scheduled pyogg, since I guess that was what you were really requesting here.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/

--- End Message ---

Reply via email to