Your message dated Sun, 09 Nov 2014 13:19:12 +0000 with message-id <e1xnsoe-0001sw...@franck.debian.org> and subject line Bug#768700: fixed in yafc 1.3.5-2 has caused the Debian Bug report #768700, regarding yafc: FTBFS in jessie: configure: error: cannot find install-sh, install.sh, or shtool in "." "./.." "./../.." 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.) -- 768700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768700 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: yafc Version: 1.3.5-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/«PKGBUILDDIR»' > dh_auto_configure -- \ > --without-readline \ > --with-bash-completion=/usr/share/bash-completion/completions > configure: WARNING: unrecognized options: --disable-maintainer-mode > configure: error: cannot find install-sh, install.sh, or shtool in "." "./.." > "./../.." The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/yafc_1.3.5-1_jessie.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: yafc Source-Version: 1.3.5-2 We believe that the bug you reported is fixed in the latest version of yafc, 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 768...@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 yafc 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, 09 Nov 2014 14:07:21 +0100 Source: yafc Binary: yafc Architecture: source Version: 1.3.5-2 Distribution: unstable Urgency: medium Maintainer: Sebastian Ramacher <sramac...@debian.org> Changed-By: Sebastian Ramacher <sramac...@debian.org> Description: yafc - yet another FTP client Closes: 768700 Changes: yafc (1.3.5-2) unstable; urgency=medium . * debian/patches/move-ac_config_aux_dir.patch: Move AC_CONFIG_AUX_DIR up a few lines so autofoo does not fail to find scripts in support. (Closes: #768700) Checksums-Sha1: 795d0b9b44e25be3f83606b4907394a450f2583f 1908 yafc_1.3.5-2.dsc 3b9c48fae46765c6e31e193f87583804f4db0255 18356 yafc_1.3.5-2.debian.tar.xz Checksums-Sha256: 4adb99c2ab2b85a8c6e256ef73274c3f0ef80937a1c1726d4da4b2c06ae7d93c 1908 yafc_1.3.5-2.dsc 43b968cefa4bb7d31aac508658cf30a5ffd0f629277d0c67cc065f0acc2b0430 18356 yafc_1.3.5-2.debian.tar.xz Files: aa197f2368618a0ba0734c81f3f77083 1908 net optional yafc_1.3.5-2.dsc e815c1ce28e5c14d89dd317f775056c8 18356 net optional yafc_1.3.5-2.debian.tar.xz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJUX2hZAAoJEGny/FFupxmTq4cQAMBmkrTVO7qV/mRVbPmrSySN pzBUcDJ2Ymu9S4SrvR0SebqMJA4vrhJf+uS2rEssSsDc2GDxuIgMDFjiQk/wZ4tx YdnTPDEK/ibsbiwwMwjyHtgXca9JJee3ZmT8JDIhfK0Rp6QL3wzDeCzaK7uklqQE vauMWgqzIgCflTsQlpuz/LVnaLJd9Pz6ERwSHrF0A4aY6OdST0Pf7NDgf7A8DmTx j/jszIjS5eDyv9Nl4hiSPdZ6kfJ2wm5x2sy8w5q846zBb7Chtxa+LsqYodfIT5a1 /pY0NhGHT+sslpao4T6hrh/Xa0S2dFrS/3HQ1vGZk8zLx8YxsnkXGBsAuZLnZrV5 rzEVOGjq6rFTCrAR5y3Sq3bF+ZKEFgsvCAd2ViOj8K8t9J+DzAxAYGdx6Ef2w+W/ NteVAwqgAW31N5Z7lU3btxAFFWuX9h/iYM0vG52T402FoPkCFlK1fgoZrfcp6uaY RI6qvh7L7PnSYS+XLfxKLQUyJuebs6HymOkyffkgRP9IyCEx3paP8HYJpwNz83s+ oONyuyn5zC61XReqLvCU+fajAbJVxXuRcK7NTBFg1TEDY8eQiLoRMijRM4JSsuPg ydertThWhsPNY41zY4Z3wQfmDv8rI4WBzL8URJGCBCzOPpb/wCIQ/gLfThlJqGNs 2M8Lk006S6jPn20g+mUL =0td3 -----END PGP SIGNATURE-----
--- End Message ---
