Your message dated Mon, 4 Feb 2008 10:55:07 -0600
with message-id <[EMAIL PROTECTED]>
and subject line Bug#464001: FTBFS: hardcodes architecture-specific path to
rep's rules.mk
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: sawfish
Version: 1:1.3.2-1
Severity: serious
Justification: no longer builds from source
>From
>http://buildd.debian.org/fetch.cgi?pkg=sawfish;ver=1%3A1.3.2-1;arch=amd64;stamp=1202040828
> :
[...]
> /usr/bin/fakeroot debian/rules clean
> dh_testdir
> dh_testroot
> rm -f build-stamp configure-stamp
> [ ! -f Makefile ] || /usr/bin/make distclean
> make[1]: Entering directory `/build/buildd/sawfish-1.3.2'
> Makedefs:85: /usr/lib/rep/i486-pc-linux-gnu/rules.mk: No such file or
> directory
> make[1]: *** No rule to make target
> `/usr/lib/rep/i486-pc-linux-gnu/rules.mk'. Stop.
> make[1]: Leaving directory `/build/buildd/sawfish-1.3.2'
> make: *** [clean] Error 2
> dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules clean gave error
> exit status 2
[...]
This appears to stem from a conjunction of sloppiness on upstream's
part (shipping platform-specific generated files) and increased
strictness on Debian's. AFAICT, you can work around it without having
to prepatch anything by specifying repexecdir via a command-line wildcard:
[ ! -f Makefile ] || /usr/bin/make distclean repexecdir=/usr/lib/rep/*-*
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.24.0 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
Version: 1:1.3.2+debian-1
> >From
> >http://buildd.debian.org/fetch.cgi?pkg=sawfish;ver=1%3A1.3.2-1;arch=amd64;stamp=1202040828
> > :
>
> [...]
> > /usr/bin/fakeroot debian/rules clean
> > dh_testdir
> > dh_testroot
> > rm -f build-stamp configure-stamp
> > [ ! -f Makefile ] || /usr/bin/make distclean
> > make[1]: Entering directory `/build/buildd/sawfish-1.3.2'
> > Makedefs:85: /usr/lib/rep/i486-pc-linux-gnu/rules.mk: No such file or
> > directory
> > make[1]: *** No rule to make target
> > `/usr/lib/rep/i486-pc-linux-gnu/rules.mk'. Stop.
> > make[1]: Leaving directory `/build/buildd/sawfish-1.3.2'
> > make: *** [clean] Error 2
> > dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules clean gave error
> > exit status 2
> [...]
>
> This appears to stem from a conjunction of sloppiness on upstream's
> part (shipping platform-specific generated files) and increased
> strictness on Debian's. AFAICT, you can work around it without having
> to prepatch anything by specifying repexecdir via a command-line wildcard:
>
> [ ! -f Makefile ] || /usr/bin/make distclean repexecdir=/usr/lib/rep/*-*
I didn't even try this. My "workaround" was to repack upstream's
tarball without the generated files. Already uploaded, as
1.3.2+debian-1
Thanks for the report.
signature.asc
Description: Digital signature
--- End Message ---
