Received: (at submit) by bugs.debian.org; 11 Feb 1997 09:35:09 +0000 Received: (qmail 11946 invoked from network); 11 Feb 1997 09:35:03 -0000 Received: from cartridge.i-connect.net (qmailr@206.190.143.12) by master.debian.org with SMTP; 11 Feb 1997 09:35:03 -0000 Received: (qmail 32274 invoked from network); 11 Feb 1997 09:19:16 -0000 Received: from greathan.apana.org.au (herbert@203.14.152.113) by cartridge.i-connect.net with SMTP; 11 Feb 1997 09:18:56 -0000 Received: (from herbert@localhost) by greathan.apana.org.au (8.8.5/8.8.5) id UAA27128 for submit@bugs.debian.org; Tue, 11 Feb 1997 20:12:44 +1100 From: Herbert Xu Message-Id: <199702110912.UAA27128@greathan.apana.org.au> Subject: Re: Anybody noticed odd dpkg-source -x behavior? (fwd) To: submit@bugs.debian.org Date: Tue, 11 Feb 1997 20:12:43 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Package: autoconf Version: 2.12-1 Galen Hazelwood wrote: > > The package seems to have extracted and patched okay, but is full of > backup (unpatched) files with a ~ extension. Did patch change it's > behavior? It's because the configure script in patch failed to detect support for long filenames. This is a bug in autoconf as it tries to write files to $prefix which in this case is set to /usr and may well be read-only. How autoconf should modified perhaps should be left to the GNU people. In the mean time, we can simply patch configure directly to avoid testing $prefix and its friends. -- Debian GNU/Linux 1.2 is out! { http://www.debian.org/ } Email: Herbert Xu ~{PmV>HI~} { http://greathan.apana.org.au/~herbert/ } PGP Key: pgp-public-keys@pgp.mit.edu or any other key sites