Your message dated Wed, 28 May 2008 12:47:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#483343: fixed in tagpy 0.94.5-1
has caused the Debian Bug report #483343,
regarding tagpy: FTBFS: invoke.hpp:88: error: no match for call to '(const
boost::python::detail::specify_a_return_value_policy_to_wrap_functio
ns_returning<TagLib::List<TagLib::StringList*>&>)
(TagLib::List<TagLib::StringList*>&)'
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.)
--
483343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483343
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: tagpy
Version: 0.93-5
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080527 qa-ftbfs
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in sid, your package failed to build on
i386.
Relevant part:
> gcc -pthread -fno-strict-aliasing -DNDEBUG -Wall -O3 -g -O2 -fPIC
> -I/usr/include/taglib -I/usr/include/python2.4 -c src/wrapper/basics.cpp -o
> build/temp.linux-i686-2.4/src/wrapper/basics.o
> /usr/include/boost/python/detail/invoke.hpp: In function 'PyObject*
> boost::python::detail::invoke(boost::python::detail::invoke_tag_<false,
> true>, const RC&, F&, TC&) [with RC =
> boost::python::detail::caller_arity<1u>::impl<F, Policies,
> Sig>::operator()(PyObject*, PyObject*) [with F =
> TagLib::List<TagLib::StringList*>& (TagLib::List<TagLib::StringList*>::*)(),
> Policies = boost::python::default_call_policies, Sig =
> boost::mpl::vector2<TagLib::List<TagLib::StringList*>&,
> TagLib::List<TagLib::StringList*>&>]::result_converter, F =
> TagLib::List<TagLib::StringList*>& (TagLib::List<TagLib::StringList*>::*)(),
> TC = boost::python::detail::caller_arity<1u>::impl<F, Policies,
> Sig>::operator()(PyObject*, PyObject*) [with F =
> TagLib::List<TagLib::StringList*>& (TagLib::List<TagLib::StringList*>::*)(),
> Policies = boost::python::default_call_policies, Sig =
> boost::mpl::vector2<TagLib::List<TagLib::StringList*>&,
> TagLib::List<TagLib::StringList*>&>]::c_t0]':
> /usr/include/boost/python/detail/caller.hpp:199: instantiated from
> 'PyObject* boost::python::detail::caller_arity<1u>::impl<F, Policies,
> Sig>::operator()(PyObject*, PyObject*) [with F =
> TagLib::List<TagLib::StringList*>& (TagLib::List<TagLib::StringList*>::*)(),
> Policies = boost::python::default_call_policies, Sig =
> boost::mpl::vector2<TagLib::List<TagLib::StringList*>&,
> TagLib::List<TagLib::StringList*>&>]'
> /usr/include/boost/python/object/py_function.hpp:38: instantiated from
> 'PyObject*
> boost::python::objects::caller_py_function_impl<Caller>::operator()(PyObject*,
> PyObject*) [with Caller =
> boost::python::detail::caller<TagLib::List<TagLib::StringList*>&
> (TagLib::List<TagLib::StringList*>::*)(),
> boost::python::default_call_policies,
> boost::mpl::vector2<TagLib::List<TagLib::StringList*>&,
> TagLib::List<TagLib::StringList*>&> >]'
> src/wrapper/basics.cpp:194: instantiated from here
> /usr/include/boost/python/detail/invoke.hpp:88: error: no match for call to
> '(const
> boost::python::detail::specify_a_return_value_policy_to_wrap_functions_returning<TagLib::List<TagLib::StringList*>&>)
> (TagLib::List<TagLib::StringList*>&)'
> error: command 'gcc' failed with exit status 1
> make: *** [build-stamp] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2008/05/27
This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3
is now the default on most architectures (even if it's not the case on
i386 yet). Consequently, many failures are caused by the switch to gcc
4.3.
If you determine that this failure is caused by gcc 4.3, feel free to
downgrade this bug to 'important' if your package is only built on i386,
and this bug is specific to gcc 4.3 (i.e the package builds fine with
gcc 4.2).
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment. Internet was not accessible from the build systems.
--
| Lucas Nussbaum
| [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
--- End Message ---
--- Begin Message ---
Source: tagpy
Source-Version: 0.94.5-1
We believe that the bug you reported is fixed in the latest version of
tagpy, which is due to be installed in the Debian FTP archive:
python-tagpy_0.94.5-1_i386.deb
to pool/main/t/tagpy/python-tagpy_0.94.5-1_i386.deb
tagpy_0.94.5-1.diff.gz
to pool/main/t/tagpy/tagpy_0.94.5-1.diff.gz
tagpy_0.94.5-1.dsc
to pool/main/t/tagpy/tagpy_0.94.5-1.dsc
tagpy_0.94.5.orig.tar.gz
to pool/main/t/tagpy/tagpy_0.94.5.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michal Čihař <[EMAIL PROTECTED]> (supplier of updated tagpy package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Wed, 28 May 2008 14:26:08 +0200
Source: tagpy
Binary: python-tagpy
Architecture: source i386
Version: 0.94.5-1
Distribution: unstable
Urgency: low
Maintainer: Michal Čihař <[EMAIL PROTECTED]>
Changed-By: Michal Čihař <[EMAIL PROTECTED]>
Description:
python-tagpy - Python module for manipulating tags in music files
Closes: 483343
Changes:
tagpy (0.94.5-1) unstable; urgency=low
.
* New upstream version.
- Build depend on python-setuptools.
- Fix configure params for new version.
- This version builds fine with GCC 4.3 (Closes: #483343).
* Use new homepage.
* Adjust watch file to use PyPi which is now official download site.
Checksums-Sha1:
33075bc23699a5ee8e6741bfeb0f93d038f7ec6f 1362 tagpy_0.94.5-1.dsc
24d15ba08c98312b305eb589faa4cec003ec8800 149641 tagpy_0.94.5.orig.tar.gz
7422374daf7f6bf35effb54c9c5c92e68be45446 2779 tagpy_0.94.5-1.diff.gz
4914f670e9f80e676b1d934fc147332c3a96f06a 605534 python-tagpy_0.94.5-1_i386.deb
Checksums-Sha256:
e5136571437a5349050836d220c2744fa04440cc59f2cd185cce8ff0e4383e07 1362
tagpy_0.94.5-1.dsc
11a1ecf07e4e23f29f128f47dcc337b6c11062ad0004a1168c4c679fe6c2e399 149641
tagpy_0.94.5.orig.tar.gz
a98a6d7e3b5cf086ec2eaca9c1bbd38bbfb63308633f79fc13ea58b62458a234 2779
tagpy_0.94.5-1.diff.gz
786599cee1be818d2af7da1c19d578d388a03ecad2752d2eadac71cc326351e9 605534
python-tagpy_0.94.5-1_i386.deb
Files:
56184c87604b58a9954e83a97394b1d2 1362 python extra tagpy_0.94.5-1.dsc
84d7862786ad7bab91d0d45ded15a875 149641 python extra tagpy_0.94.5.orig.tar.gz
7c5e7c1de604541d2cc4232432dfb51e 2779 python extra tagpy_0.94.5-1.diff.gz
55c1e6715f2235f1232a43ce5c53c4e2 605534 python extra
python-tagpy_0.94.5-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIPVB43DVS6DbnVgQRAsSwAJ4kvwVtC8BSZhcPrXWqXGzbd85C7wCggggq
iInqIsjoDxrci4j4459CA8U=
=0eSN
-----END PGP SIGNATURE-----
--- End Message ---
