tags 576620 + patch
thanks

On 2010-04-06 04:11 +0200, Clint Adams wrote:

> On Tue, Apr 06, 2010 at 10:36:12AM +1000, Ben Finney wrote:
>> Preparing to replace cpio 2.10-1 (using .../cpio_2.11-1_powerpc.deb) ...
>> Unpacking replacement cpio ...
>> dpkg: error processing /var/cache/apt/archives/cpio_2.11-1_powerpc.deb 
>> (--unpack):
>>  trying to overwrite '/usr/share/info/dir.gz', which is also in package 
>> ledger 0:2.6.2-2
>> =====
>> 
>> It seems unlikely these files are fungible. One or both of these files
>> needs to be renamed in the Debian package to allow for installing both
>> packages simultaneously.
>
> On Tue, Apr 06, 2010 at 11:36:10AM +1000, Matthew Palmer wrote:
>> Yeah, I'd say that's going to be ledger's fault -- or, at least, no less
>> than cpio's (or any other package).
>> 
>> I guess I'm about to learn a lot more about info pages than I ever wanted
>> to...
>
> No, neither package should ship that file.  Since this only occurs on certain
> architectures, there may be something funny going on with install-info on the
> buildds.

The condition for this bug to be triggered is that the install-info
package is installed in the build environment.  In that case,
"make install" will write to debian/tmp/usr/share/info/dir.
Here is a patch to remove the compressed file after that happens:

--8<---------------cut here---------------start------------->8---
--- debian/rules~       2010-03-11 14:04:02.000000000 +0100
+++ debian/rules        2010-04-06 11:34:09.847084344 +0200
@@ -125,6 +125,7 @@
        gzip -9v debian/tmp/usr/share/doc/$(package)/*
        gzip -9v debian/tmp/usr/share/man/*/*
        gzip -9v debian/tmp/usr/share/info/*
+       rm -f debian/tmp/usr/share/info/dir.gz
        install -m 644 debian/copyright debian/tmp/usr/share/doc/$(package)/.
 # Determine shared library dependencies
        dpkg-shlibdeps debian/tmp/bin/cpio debian/tmp/bin/mt-gnu
--8<---------------cut here---------------end--------------->8---

Sven



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to