Bug#175978: sabre_0.2.4b-15(mipsel/unstable): fails to build with sudo

2003-03-30 Thread Colin Watson 
On Thu, Jan 09, 2003 at 03:40:04AM -0800, Ryan Murray wrote:
> Package: sabre
> Version: 0.2.4b-15
> Severity: serious
[...]
> > make[3]: Entering directory `/build/buildd/sabre-0.2.4b/lib/tzp'
> > rm -f Makefile 
> > rm -f config.cache config.log stamp-h stamp-h[0-9]*
> > make[3]: Leaving directory `/build/buildd/sabre-0.2.4b/lib/tzp'
> > make[2]: Leaving directory `/build/buildd/sabre-0.2.4b/lib'
> > rm -f config.status
> > make[1]: Leaving directory `/build/buildd/sabre-0.2.4b'
> > find -name Makefile -o -name Makefile.in | xargs -r rm -f
> > dh_clean
> >  debian/rules build
> > dh_testdir
> > automake && aclocal && autoconf
> > ./configure --prefix=/usr --bindir=/usr/games --without-svgalib
> > ./configure: line 903: config.log: Permission denied
> > make: *** [stamp-configure] Error 1
> 
> A full build log can be found at:
> http://buildd.debian.org/build.php?arch=mipsel&pkg=sabre&ver=0.2.4b-15
> 
> sabre fails to build from source with the following commands:
> apt-get source sabre
> cd sabre-0.2.4b
> dpkg-buildpackage -uc -us -B -rsudo
> 
> Running automake, aclocal, and autoconf in your clean target (with root
> privs), and then running them again in the build target (without root privs)
> causes the build to fail.  You need to clean up after everything generated
> in clean, or stop generating files in your clean target.

sabre's debian/rules does do this cleanup, though, so I'm confused. Look
further up in that build log:

make[1]: Entering directory `/build/buildd/sabre-0.2.4b'
cd . \
  && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status
config.status: creating Makefile
make[1]: Leaving directory `/build/buildd/sabre-0.2.4b'
make[1]: Entering directory `/build/buildd/sabre-0.2.4b'
Making distclean in .
make[2]: Entering directory `/build/buildd/sabre-0.2.4b'
rm -f TAGS ID
rm -f Makefile
rm -f config.cache config.log stamp-h stamp-h[0-9]*
make[2]: Leaving directory `/build/buildd/sabre-0.2.4b'

There's a fair bit of log after that, but none of it should touch
config.log, and building with -rsudo works fine for me on i386. However,
the mipsen do seem to be consistently failing. Since it doesn't appear
to be configure, can you shed any light on what's creating config.log?

Thanks,

-- 
Colin Watson  [EMAIL PROTECTED]

Bug#186884: jade: index.html doesn't reference the right copyright file

2003-03-30 Thread Andreas Pakulat 
Package: jade
Version: 1.2.1-28
Severity: minor

Hi,

the index.html file in the doc-dir references the copying.txt instead of
the copyright file that is used in Debian doc-dir's for the copyright
statement.

Andreas

-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux debian 2.4.20 #1 Don Mär 6 00:09:08 CET 2003 i686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8

Versions of packages jade depends on:
ii  libc6 2.3.1-14   GNU C Library: Shared libraries an
ii  libsp11.3.4-1.2.1-28 Runtime library for James Clark's 
ii  libstdc++2.10-glibc2.21:2.95.4-17The GNU stdc++ library
ii  sgml-base 1.17   utilities to maintain SGML catalog