Your message dated Wed, 17 Mar 2010 22:09:34 +0100
with message-id <20100317210934.gf14...@density.luon.net>
and subject line Fix reapplied
has caused the Debian Bug report #526579,
regarding elisa: FTBFS: cannot touch
`/tmp/buildd/elisa-0.3.5/debian/tmp//usr/lib/python2.5/site-packages/elisa/__init__.py'
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.)
--
526579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elisa
Version: 0.3.5-3
Severity: serious
From my pbuilder build log:
...
running build_scripts
touch debian/python-module-stampdir/python-elisa
rm -f /tmp/buildd/elisa-0.3.5/debian/tmp//usr/lib/python2.5/site-packages/*.pth
touch
/tmp/buildd/elisa-0.3.5/debian/tmp//usr/lib/python2.5/site-packages/elisa/__init__.py
touch: cannot touch
`/tmp/buildd/elisa-0.3.5/debian/tmp//usr/lib/python2.5/site-packages/elisa/__init__.py':
No such file or directory
make: *** [common-install-indep] Error 1
dpkg-buildpackage: failure: fakeroot debian/rules binary gave error exit status
2
--
Daniel Schepler
--- End Message ---
--- Begin Message ---
Version: 1.0.7-1
The fix that got lost when the elisa 0.3.5-3.1 got removed from the
archive has already been reapplied to moovida 1.0.7-1.
Paul
--
PhD Student @ Eindhoven | email: pau...@debian.org
University of Technology, The Netherlands | JID: p...@luon.net
>>> Using the Power of Debian GNU/Linux <<< | GnuPG key ID: 0x50064181
--- End Message ---
