Your message dated Sat, 26 Apr 2008 18:45:45 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: john_1.7-2(alpha/experimental): FTBFS: install: cannot
stat `run/john'
has caused the Debian Bug report #410412,
regarding john_1.7-2(experimental/alpha/ds10): Doesn't build binary
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.)
--
410412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=410412
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: john
Version: 1.7-2
Severity: serious
Tags: experimental
Heya,
Building john failed here because the build system simply forgot to
actually build something:
Automatic build of john_1.7-2 on ds10 by sbuild/alpha 98-farm
Build started at 20070210-0644
******************************************************************************
[...]
dpkg-source: extracting john in john-1.7
dpkg-buildpackage: source package is john
dpkg-buildpackage: source version is 1.7-2
dpkg-buildpackage: host architecture alpha
dpkg-buildpackage: source version without epoch 1.7-2
/usr/bin/fakeroot debian/rules clean
test -x debian/rules
test "`id -u`" = 0
/usr/bin/make -f debian/rules reverse-config
make[1]: Entering directory `/build/buildd/john-1.7'
make[1]: Nothing to be done for `reverse-config'.
make[1]: Leaving directory `/build/buildd/john-1.7'
if [ "reverse-patches" = "reverse-patches" ]; then rm -f debian/stamp-patched;
fi
patches: debian/patches/faq.diff debian/patches/system-wide.diff
Patch debian/patches/system-wide.diff is not applied.
Patch debian/patches/faq.diff is not applied.
if [ "reverse-patches" != "reverse-patches" ]; then touch debian/stamp-patched;
fi
if [ "reverse-patches" != "reverse-patches" ] ; then \
/usr/bin/make -f debian/rules update-config ; \
fi
for dir in debian/patches ; do \
rm -f $dir/*.log ; \
done
dh_clean
rm -f run/john-* run/john
cd /build/buildd/john-1.7/src && /usr/bin/make clean
make[1]: Entering directory `/build/buildd/john-1.7/src'
rm -f ../run/john ../run/unshadow ../run/unafs ../run/unique ../run/john.bin
../run/john.com ../run/unshadow.com ../run/unafs.com ../run/unique.com
../run/john.exe ../run/unshadow.exe ../run/unafs.exe ../run/unique.exe
rm -f ../run/john.exe *.o *.bak core
rm -f detect bench generic.h arch.h sparc.h tmp.s
rm -f DES_bs_s.c DES_bs_n.c DES_bs_a.c
cp /dev/null Makefile.dep
make[1]: Leaving directory `/build/buildd/john-1.7/src'
rm -f build-john-stamp
debian/rules build
test -x debian/rules
mkdir -p "."
/usr/bin/make -f debian/rules reverse-config
make[1]: Entering directory `/build/buildd/john-1.7'
make[1]: Nothing to be done for `reverse-config'.
make[1]: Leaving directory `/build/buildd/john-1.7'
if [ "debian/stamp-patched" = "reverse-patches" ]; then rm -f
debian/stamp-patched; fi
patches: debian/patches/faq.diff debian/patches/system-wide.diff
Trying patch debian/patches/faq.diff at level 1 ... success.
Trying patch debian/patches/system-wide.diff at level 1 ... success.
if [ "debian/stamp-patched" != "reverse-patches" ]; then touch
debian/stamp-patched; fi
if [ "debian/stamp-patched" != "reverse-patches" ] ; then \
/usr/bin/make -f debian/rules update-config ; \
fi
make[1]: Entering directory `/build/buildd/john-1.7'
make[1]: Nothing to be done for `update-config'.
make[1]: Leaving directory `/build/buildd/john-1.7'
touch build-john-stamp
/usr/bin/fakeroot debian/rules binary-arch
test -x debian/rules
test "`id -u`" = 0
dh_clean -k
dh_installdirs -A
mkdir -p "."
dh_installdirs -pjohn
dh_installdocs -pjohn ./README
dh_installexamples -pjohn
dh_installman -pjohn
dh_installinfo -pjohn
dh_installmenu -pjohn
dh_installcron -pjohn
dh_installinit -pjohn
dh_installdebconf -pjohn
dh_installemacsen -pjohn
dh_installcatalogs -pjohn
dh_installpam -pjohn
dh_installlogrotate -pjohn
dh_installlogcheck -pjohn
dh_installmime -pjohn
dh_installchangelogs -pjohn
dh_installudev -pjohn
dh_install -pjohn
dh_link -pjohn
install -d /build/buildd/john-1.7/debian/john//var/run
install -d -m 0700 /build/buildd/john-1.7/debian/john//var/run/john
install -m 755 debian/extra/cronjob
/build/buildd/john-1.7/debian/john//usr/share/john
install -m 644 debian/extra/cron.d-john
/build/buildd/john-1.7/debian/john//etc/cron.d/john
install doc/CHANGES
/build/buildd/john-1.7/debian/john//usr/share/doc/john/changelog
install -m 644 run/john.conf
/build/buildd/john-1.7/debian/john//etc/john/john.conf
( cd /build/buildd/john-1.7/debian/john//usr/share/john && ln -s
/etc/john/john.conf john.conf )
install -s run/john /build/buildd/john-1.7/debian/john//usr/sbin/john
install: cannot stat `run/john': No such file or directory
make: *** [binary-install/john] Error 1
Marc
--
BOFH #340:
Well fix that in the next (upgrade, update, patch release, service
pack).
--- End Message ---
--- Begin Message ---
notfound 410412 1.7.2-1
notfound 447265 1.7.2-1
thanks
Hi all,
a new version of john landed into sid (1.7.2-1), and seems like it has been
built fine on all architectures (but armel). I believe I can close these bugs.
Please feel free to reopen them (well, one of) if you still experience any
problem.
Kindly,
David
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 ----|---- http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: PGP signature
--- End Message ---
