Your message dated Sat, 03 Jun 2006 05:02:06 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#357355: fixed in packagesearch 2.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: packagesearch
Version: 2.0.6
Severity: serious

Hello,

There was an error while trying to autobuild your package:

> g++ -c -pipe -O2 `pkg-config --cflags libapt-front libtagcoll` -D_REENTRANT 
> -Wall -W  -DQT_NO_DEBUG -DQT_QT3SUPPORT_LIB -DQT3_SUPPORT -DQT_XML_LIB 
> -DQT_GUI_LIB -DQT_CORE_LIB -I/usr/share/qt4/mkspecs/linux-g++ -I. 
> -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtXml 
> -I/usr/include/qt4/Qt3Support -I/usr/include/qt4 -I. -I.moc -I.ui -o 
> .obj/instantiations.o instantiations.cpp
> instantiations.cpp:18: error: duplicate explicit instantiation of 'class 
> Tagcoll::OpSet<int>'
> make[2]: *** [.obj/instantiations.o] Error 1
> make[2]: Leaving directory `/build/buildd/packagesearch-2.0.6/src'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/build/buildd/packagesearch-2.0.6'
> make: *** [build-stamp] Error 2

A full build log can be found at:
http://buildd.debian.org/build.php?arch=amd64&pkg=packagesearch&ver=2.0.6

Best regards
Frederik Schueler


--- End Message ---
--- Begin Message ---
Source: packagesearch
Source-Version: 2.1

We believe that the bug you reported is fixed in the latest version of
packagesearch, which is due to be installed in the Debian FTP archive:

packagesearch_2.1.dsc
  to pool/main/p/packagesearch/packagesearch_2.1.dsc
packagesearch_2.1.tar.gz
  to pool/main/p/packagesearch/packagesearch_2.1.tar.gz
packagesearch_2.1_i386.deb
  to pool/main/p/packagesearch/packagesearch_2.1_i386.deb



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.
Benjamin Mesing <[EMAIL PROTECTED]> (supplier of updated packagesearch 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.7
Date: Mon, 1 June 2006 13:49:02 +0100
Source: packagesearch
Binary: packagesearch
Architecture: source i386
Version: 2.1
Distribution: unstable
Urgency: low
Maintainer: Benjamin Mesing <[EMAIL PROTECTED]>
Changed-By: Benjamin Mesing <[EMAIL PROTECTED]>
Description: 
 packagesearch - GUI for searching packages and viewing package information
Closes: 348493 355625 357355 364551 369424
Changes: 
 packagesearch (2.1) unstable; urgency=low
 .
   * New upstream release
      - removed obsolete instantiation.cpp file (Closes: #357355,
        already fixed before in NMU)
      - switched backend to use libapt-front in main program and
        relevant plugins (Closes: #364551, #348493)
      - prepared for gcc 4.1 (Closes: #369424)
      - checks for debtags availability before trying to open (Closes: #355625)
Files: 
 0c4d148f13ac069aba3955d63a62e562 614 admin optional packagesearch_2.1.dsc
 bc37a28f088373da45251144c28e2b7b 599913 admin optional packagesearch_2.1.tar.gz
 164f59617ecb94e0cb4f1c12ef6587e7 1060794 admin optional 
packagesearch_2.1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEgXVM9LSwzHl+v6sRAuqcAJ9UtVLElWwuUwRfSoC/BdHOuJmp0ACghidZ
15H0SfcA9QV4tWwwfjEfroM=
=88sx
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to