Your message dated Mon, 7 Dec 2009 22:18:21 +0300
with message-id <20091207221821.7c37a...@corner>
and subject line fixed in kflickr 0.9.1-2.2
has caused the Debian Bug report #554604,
regarding kflickr_0.9.1-2.1(ia64/unstable): FTBFS: confused about automake
versions?
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 ow...@bugs.debian.org
immediately.)
--
554604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kflickr
Version: 0.9.1-2.1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of kflickr_0.9.1-2.1 on mundy by sbuild/ia64 98
> Build started at 20091105-1553
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper, automake, libtool, kdelibs4-dev, autotools-dev
[...]
> cp -f /usr/share/aclocal/libtool.m4 admin/libtool.m4.in
> make -f Makefile.cvs
> make[1]: Entering directory `/build/buildd/kflickr-0.9.1'
> This Makefile is only for the CVS repository
> This will be deleted before making the distribution
>
> make[2]: Entering directory `/build/buildd/kflickr-0.9.1'
> *** YOU'RE USING automake (GNU automake) 1.11.
> *** KDE requires automake 1.6.1 or newer
> make[2]: *** [cvs] Error 1
> make[2]: Leaving directory `/build/buildd/kflickr-0.9.1'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/build/buildd/kflickr-0.9.1'
> make: *** [autotools-stamp] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
A full build log can be found at:
http://buildd.debian.org/build.php?arch=ia64&pkg=kflickr&ver=0.9.1-2.1
--- End Message ---
--- Begin Message ---
Version: 0.9.1-2.2
I believe this was fixed in a recent upload of version 0.9.1-2.2 (see #540669
for patch).
--
Ilya
--- End Message ---
