Your message dated Tue, 30 Jul 2013 22:18:22 +0000
with message-id <e1v4ifk-0007cx...@franck.debian.org>
and subject line Bug#713194: fixed in libfm 0.1.17-2.2
has caused the Debian Bug report #713194,
regarding libfm: FTBFS: aclocal: warning: couldn't open directory 'm4': No such 
file or directory
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.)


-- 
713194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libfm
Version: 0.1.17-2.1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> autoreconf -i
> aclocal: warning: couldn't open directory 'm4': No such file or directory
> libtoolize: putting auxiliary files in `.'.
> libtoolize: copying file `./ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
> libtoolize: copying file `m4/libtool.m4'
> libtoolize: copying file `m4/ltoptions.m4'
> libtoolize: copying file `m4/ltsugar.m4'
> libtoolize: copying file `m4/ltversion.m4'
> libtoolize: copying file `m4/lt~obsolete.m4'
> libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> automake: warnings are treated as errors
> data/ui/Makefile.am:21: warning: '%'-style pattern rules are a GNU make 
> extension
> parallel-tests: installing './test-driver'
> /usr/share/automake-1.13/am/ltlibrary.am: warning: 'libfm-gtk.la': linking 
> libtool libraries using a non-POSIX
> /usr/share/automake-1.13/am/ltlibrary.am: archiver requires 'AM_PROG_AR' in 
> 'configure.ac'
> src/Makefile.am:205:   while processing Libtool library 'libfm-gtk.la'
> /usr/share/automake-1.13/am/ltlibrary.am: warning: 'libfm.la': linking 
> libtool libraries using a non-POSIX
> /usr/share/automake-1.13/am/ltlibrary.am: archiver requires 'AM_PROG_AR' in 
> 'configure.ac'
> src/Makefile.am:205:   while processing Libtool library 'libfm.la'
> /usr/share/automake-1.13/am/ltlibrary.am: warning: 'libgiofm.la': linking 
> libtool libraries using a non-POSIX
> /usr/share/automake-1.13/am/ltlibrary.am: archiver requires 'AM_PROG_AR' in 
> 'configure.ac'
> src/Makefile.am:312:   while processing Libtool library 'libgiofm.la'
> src/Makefile.am:21: warning: compiling 'glib-compat.c' with per-target flags 
> requires 'AM_PROG_CC_C_O' in 'configure.ac'
> autoreconf: automake failed with exit status: 1
> make[1]: *** [override_dh_auto_configure] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/libfm_0.1.17-2.1_unstable.log

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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

--- End Message ---
--- Begin Message ---
Source: libfm
Source-Version: 0.1.17-2.2

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

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 713...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Ramacher <sramac...@debian.org> (supplier of updated libfm 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sun, 28 Jul 2013 23:45:26 +0200
Source: libfm
Binary: libfm1 libfm-dev libfm1-dbg libfm-data libfm-gtk1 libfm-gtk-bin
Architecture: source amd64 all
Version: 0.1.17-2.2
Distribution: unstable
Urgency: low
Maintainer: Debian LXDE Maintainers <lxde-deb...@lists.lxde.org>
Changed-By: Sebastian Ramacher <sramac...@debian.org>
Description: 
 libfm-data - file management support (common data)
 libfm-dev  - file management support (development)
 libfm-gtk-bin - file management support (utilities)
 libfm-gtk1 - file management support (GTK+ GUI library)
 libfm1     - file management support (core library)
 libfm1-dbg - file management support (debug)
Closes: 713194
Changes: 
 libfm (0.1.17-2.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * debian/patches/03-automake1.12.patch: Apply patch from upstream to fix
     automake errors. (Closes: #713194)
Checksums-Sha1: 
 25cd009b664a8a2d2dc7a7adacbca425e5f8576c 2270 libfm_0.1.17-2.2.dsc
 bb31929cc0ae6327d2c8423a47acff46ddd618f4 10352 libfm_0.1.17-2.2.debian.tar.xz
 11d3c1a3aa14c5a23aa9096b95be7e0fd86b9717 61078 libfm1_0.1.17-2.2_amd64.deb
 dabda905a23772160dec7a47c12181eb6ef0419e 74840 libfm-dev_0.1.17-2.2_amd64.deb
 6fb8288920e3446b4bc785d65a14fd806f4d2c5b 628326 libfm1-dbg_0.1.17-2.2_amd64.deb
 25e3a1d85a052d77f7788cd51dcf4a561d1ccb1a 99982 libfm-data_0.1.17-2.2_all.deb
 2e09451095a78feb3e1606063ce445bb457b2dc5 98430 libfm-gtk1_0.1.17-2.2_amd64.deb
 7d27cf24b7fb28876b745ab187fdf5907fbfd6d0 15112 
libfm-gtk-bin_0.1.17-2.2_amd64.deb
Checksums-Sha256: 
 f93ffa3a8e63b818310b16f856f2e09e3bbfb02b5767ea6e98e2d07a384e76ef 2270 
libfm_0.1.17-2.2.dsc
 4f8e390c3a20f133902022b94827805f3d7e85f71f6716ca2cf4923d97e1f596 10352 
libfm_0.1.17-2.2.debian.tar.xz
 c404b49c078932169d9cc279a26c382cb4fd6c5c4c16738816959ca004072e90 61078 
libfm1_0.1.17-2.2_amd64.deb
 914dbd46c8e4150795b9046372265701e098e98dbdf77741d47538af89f787ba 74840 
libfm-dev_0.1.17-2.2_amd64.deb
 616b983180e86fea630d0076fdded47fe1f1ed10dc2651112736e51fc2f9c6d1 628326 
libfm1-dbg_0.1.17-2.2_amd64.deb
 f859b2824d1e4ad3b677ef8c015b3e7f7b4681cdf777ac2e0bc08d3152fe9bbe 99982 
libfm-data_0.1.17-2.2_all.deb
 69d6174022c70f8ac72f3bcc2339c68d14088236c10319e13af8891fcaeb421b 98430 
libfm-gtk1_0.1.17-2.2_amd64.deb
 2d90aaa0352e6c85362a882e62de34ee19beba9793f1bb396af8efb349eaa8b3 15112 
libfm-gtk-bin_0.1.17-2.2_amd64.deb
Files: 
 b86580751aa0db4f00487949267181e8 2270 libs extra libfm_0.1.17-2.2.dsc
 f4395ff89a2ab7a3d27be28c5a468434 10352 libs extra 
libfm_0.1.17-2.2.debian.tar.xz
 49e7cb09b37fb3b23ac4094d15adb0e3 61078 libs extra libfm1_0.1.17-2.2_amd64.deb
 818a605d223307d72084c22963333cc8 74840 libdevel extra 
libfm-dev_0.1.17-2.2_amd64.deb
 3e1e7f03e0a3677d8e70cd86633d0538 628326 debug extra 
libfm1-dbg_0.1.17-2.2_amd64.deb
 bea1a5816fc0aa699a00f2150894ef89 99982 misc extra libfm-data_0.1.17-2.2_all.deb
 60d7860a2b9a7a0d305378f37e99337e 98430 libs extra 
libfm-gtk1_0.1.17-2.2_amd64.deb
 68feebf4023c7622f295d20e9044f933 15112 misc extra 
libfm-gtk-bin_0.1.17-2.2_amd64.deb

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

iQIcBAEBCAAGBQJR9ZHqAAoJEGny/FFupxmTfvwP/R4M3tnyaMvwlI32kWtz35pZ
hWOoSkfmKB4curLza5wrtKGH8E9/xPaIEKB0WWEfm42GT8h826fQMBCCIGMKToX1
htamq2AATvXw+G0GrvkdYV7bYZTQ1WdKOExUiLciEGom46TzmxQZ9GU+mehcXW4t
8bCf2pqCMeCoBYhw7uuzrRARnUFCiIv0c5+EGYf+gESCNh7GHVNwbzbXHyLnSYPk
J4Mv5LoXCgROEAvKXHsJRFOTnsm8ZIvdrMTVPET2Qp+fqJxLte//8F8K/fTCA2Hz
RfCQ9FwVaTojtIrBbAP0seXk0bpwMuRiKmfhNuGSgjkpslXLS9BEO6VFW97nRNZd
W55v2ofOWL1RPWMaNXrxssh8hnZqp2x163le5z4z3P84znqnGquuGS51Ql8SNMxF
2+fXFsMdawiK+sm8az/Hns6yB+HNy3CsnCVilXkGPeyktREAC9TSKPPjknHLcM6W
/XsacljkSauX1uAZwIA4XbGoqQ3doDp7GhZQjVLfNg2J1LHyHcxmUypD1t3z8dIs
X4qmGl0nIpVLXEYSPTfktVTSBWWyMYjtfkBA9gKKkEpsi6KCll4jkBl7+ZgxmOhQ
yY77FzDOCQQbqhfUbp0cTO+5N9pt4aeEGwFX5290xvYbpjifJuojQdFa1Yax4GVx
2+EUrMetevgls8HM75Xu
=OdH4
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to