Your message dated Wed, 16 Sep 2015 13:42:46 +0000
with message-id <[email protected]>
and subject line Bug#799171: Removed package(s) from unstable
has caused the Debian Bug report #744647,
regarding pigment-python: run dh-autoreconf to update config.{sub,guess} and
{libtool,aclocal}.m4
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.)
--
744647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744647
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:pigment-python
Version: 0.3.12-2.1
User: [email protected]
Usertags: autoreconf
The package fails to build on ppc64el (powerpc64le-linux-gnu), because
the config.{guess,sub} files are out of date, and are not updated during
the build. If possible, please do not update these files directly,
but build-depend on autotools-dev instead, and use the tools provided
by autotools-dev to update these files.
- For dh, call dh --with autoreconf.
- For cdbs based build systems, include
/usr/share/cdbs/1/rules/autoreconf.mk
- For other rules files, call dh_autoreconf before calling
configure (in the build or configure target), and call
dh_autoreconf_clean before dh_clean in the clean target.
For combining autoreconf and autotools_dev, see bug #698765.
After the build on any architecture, and before a clean, a grep for
powerpc64le in the configure, aclocal.m4 and/or libtool.m4 file(s)
should print some lines. It is not enough to just update the
config.guess and config.sub files.
The full build log can be found at:
http://people.debian.org/~doko/logs/ppc64el-20140414/buildlog_ubuntu-trusty-ppc64el.pigment-python_0.3.12-2.1_FAILEDTOBUILD.txt
The last lines of the build log are at the end of this report.
Please note that these builds were done in an Ubuntu development,
environment there may be a few false positives in these bug reports.
See https://wiki.debian.org/qa.debian.org/FTBFS for a guide how to
address these.
[...]
make[4]: Entering directory `/build/buildd/pigment-python-0.3.12/win32/vs6'
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
make[4]: Leaving directory `/build/buildd/pigment-python-0.3.12/win32/vs6'
make[3]: Leaving directory `/build/buildd/pigment-python-0.3.12/win32/vs6'
Making install in vs9
make[3]: Entering directory `/build/buildd/pigment-python-0.3.12/win32/vs9'
make[4]: Entering directory `/build/buildd/pigment-python-0.3.12/win32/vs9'
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
make[4]: Leaving directory `/build/buildd/pigment-python-0.3.12/win32/vs9'
make[3]: Leaving directory `/build/buildd/pigment-python-0.3.12/win32/vs9'
make[3]: Entering directory `/build/buildd/pigment-python-0.3.12/win32'
make[4]: Entering directory `/build/buildd/pigment-python-0.3.12/win32'
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
make[4]: Leaving directory `/build/buildd/pigment-python-0.3.12/win32'
make[3]: Leaving directory `/build/buildd/pigment-python-0.3.12/win32'
make[2]: Leaving directory `/build/buildd/pigment-python-0.3.12/win32'
make[2]: Entering directory `/build/buildd/pigment-python-0.3.12'
make[3]: Entering directory `/build/buildd/pigment-python-0.3.12'
make[3]: Nothing to be done for `install-exec-am'.
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory `/build/buildd/pigment-python-0.3.12'
make[2]: Leaving directory `/build/buildd/pigment-python-0.3.12'
make[1]: Leaving directory `/build/buildd/pigment-python-0.3.12'
touch debian/stamp-makefile-install
Adding cdbs dependencies to debian/python-pgm.substvars
dh_installdirs -ppython-pgm
dh_installdocs -ppython-pgm ./README ./NEWS ./TODO ./AUTHORS
dh_installexamples -ppython-pgm
dh_installman -ppython-pgm
dh_installinfo -ppython-pgm
dh_installmenu -ppython-pgm
dh_installcron -ppython-pgm
dh_installinit -ppython-pgm
dh_installdebconf -ppython-pgm
dh_installemacsen -ppython-pgm
dh_installcatalogs -ppython-pgm
dh_installpam -ppython-pgm
dh_installlogrotate -ppython-pgm
dh_installlogcheck -ppython-pgm
dh_installchangelogs -ppython-pgm ./ChangeLog
dh_installudev -ppython-pgm
dh_lintian -ppython-pgm
dh_bugfiles -ppython-pgm
dh_install -ppython-pgm
dh_install: python-pgm missing files
(debian/tmp/usr/lib/python*/*-packages/*.so), aborting
make: *** [binary-install/python-pgm] Error 255
dpkg-buildpackage: error: /usr/bin/fakeroot debian/rules binary-arch gave error
exit status 2
--- End Message ---
--- Begin Message ---
Version: 0.3.12-2.1+rm
Dear submitter,
as the package pigment-python has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/799171
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
