Your message dated Thu, 7 Sep 2006 14:12:48 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in NMU of dia-newcanvas 0.6.10-5.1
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: dia-newcanvas
Version: 0.6.10-5
Severity: serious
Justification: fails to build from source
>From my build log:
> Automatic build of dia-newcanvas_0.6.10-5 on testbuild by sbuild/i386 85
> Build started at 20060826-1602
> ******************************************************************************
> Checking available source versions...
> Fetching source files...
> Reading package lists...
> Building dependency tree...
> Need to get 605kB of source archives.
> Get:1 http://debian.aurel32.net sid/main dia-newcanvas 0.6.10-5 (dsc) [715B]
> Get:2 http://debian.aurel32.net sid/main dia-newcanvas 0.6.10-5 (tar) [328kB]
> Get:3 http://debian.aurel32.net sid/main dia-newcanvas 0.6.10-5 (diff) [276kB]
> Fetched 605kB in 0s (5909kB/s)
> Download complete and in download only mode
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>> 3.0.0), libgtk2.0-dev (>= 2.0.6), gettext,
> libglade2-dev (>= 2.0.0-2), python2.3-dev, python-gtk2-dev
...
> checking whether the i486-linux-gnu-g++ linker (/usr/bin/ld) supports shared
> libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> appending configuration tag "F77" to libtool
> checking for a Python interpreter with version >= 2.3... python
> checking for python... /usr/bin/python
> checking for python version... 2.4
> checking for python platform... linux2
> checking for python script directory... ${prefix}/lib/python2.4/site-packages
> checking for python extension module directory...
> ${exec_prefix}/lib/python2.4/site-packages
> checking for python >= 2.3... okay
> checking for headers required to compile python extensions... not found
> configure: error: could not find Python headers
> make: *** [config.status] Error 1
> ******************************************************************************
> Build finished at 20060826-1604
> FAILED [dpkg-buildpackage died]
> Purging chroot-unstable/build/buildd/dia-newcanvas-0.6.10
> ------------------------------------------------------------------------------
Build-depending on python-dev instead of python2.3-dev should fix the problem.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-amd64-k8-smp
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to fr_FR.UTF-8)
--- End Message ---
--- Begin Message ---
Version: 0.6.10-5.1
I've NMUed for this bug (fixing the bug to use versioning instead of the
"fixed" tag, to ease tracking through testing); here's the changelog:
> dia-newcanvas (0.6.10-5.1) unstable; urgency=medium
> .
> * Non-maintainer upload.
> * Build-depend on python-dev instead of python2.3-dev; fixes FTBFS now
> that python is python2.4. (Closes: #384818)
/* Steinar */
--
Homepage: http://www.sesse.net/
--- End Message ---
