Re: [Hampshire] Is a faulty download to blame for my problem…

Top Page
Author: Hugo Mills
Date:  
To: Hampshire LUG Discussion List
Subject: Re: [Hampshire] Is a faulty download to blame for my problems?

Reply to this message
gpg: failed to create temporary file '/var/lib/lurker/.#lk0x56efc100.hantslug.org.uk.11201': Permission denied
gpg: keyblock resource '/var/lib/lurker/pubring.gpg': Permission denied
gpg: Signature made Sun Nov 18 18:41:20 2007 GMT
gpg: using DSA key 20ACB3BE515C238D
gpg: Can't check signature: No public key
On Sun, Nov 18, 2007 at 04:57:10PM +0000, hantslug@??? wrote:
> On Sunday 18 November 2007 16:28, Hugo Mills wrote:
> > On Sun, Nov 18, 2007 at 04:27:42PM +0000, hantslug@??? wrote:
> > > On Sunday 18 November 2007 16:08, Hugo Mills wrote:
> > > >  What do you get if you do:
> > > >
> > > > $ sudo dpkg -i
> > > > /var/cache/apt/archives/acroread-debian-files_0.0.11_all.deb
> > >
> > > Tux:/home/lisi#
> > > dpkg -i /var/cache/apt/archives/acroread-debian-files_0.0.11_all.deb
> > > (Reading database ... 137517 files and directories currently installed.)
> > > Preparing to replace acroread-debian-files 0.0.11
> > > (using .../acroread-debian-files_0.0.11_all.deb) ...
> > > Unpacking replacement acroread-debian-files ...
> > > Error: contents of '/etc/mailcap.new' do not match what was written --
> > > abort dpkg: warning - old post-removal script returned error exit status
> > > 255 dpkg - trying script from the new package instead ...
> > > Error: contents of '/etc/mailcap.new' do not match what was written --
> > > abort dpkg: error
> > > processing /var/cache/apt/archives/acroread-debian-files_0.0.11_all.deb
> > > (--install):
> > > subprocess new post-removal script returned error exit status 255
> > > Error: contents of '/etc/mailcap.new' do not match what was written --
> > > abort dpkg: error while cleaning up:
> > > subprocess post-removal script returned error exit status 255
> > > Errors were encountered while processing:
> > > /var/cache/apt/archives/acroread-debian-files_0.0.11_all.deb
> > > Tux:/home/lisi#
> >
> >    This starts to look more tractable by the minute.

>
> Oh, good. <sigh of relief>
>
> >    What does:

> >
> > $ ls -l /etc/mailcap*
> > say?
>
> [lisi@Tux:~]$  ls -l /etc/mailcap*
> -rw-r--r-- 1 root root 24420 2007-10-23 09:50 /etc/mailcap
> -rw-r--r-- 1 root root     0 2007-11-18 16:25 /etc/mailcap.new
> -rw-r--r-- 1 root root   449 2006-12-05 03:22 /etc/mailcap.order
> [lisi@Tux:~]$


Try removing /etc/mailcap.new and doing the above dpkg install
command again. That probably won't help, but it's worth a try.

Also, what happens if you (as root) do something like:

# echo Foo bar baz >/etc/mailcap.new

It looks like the package contains a new mailcap file, and for some
reason it can't write data to that file. The usual reason for this is
a full filesystem, but not always.

Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
         --- Always be sincere,  whether you mean it or not. ---