On Sunday 18 November 2007 22:41, Hugo Mills wrote:
> On Sun, Nov 18, 2007 at 08:52:42PM +0000, hantslug@??? wrote:
> > On Sunday 18 November 2007 18:41, Hugo Mills wrote:
> > > 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#
> >
> > The list is hard to read, but rm mailcap.new was successful:
> > i.e. removed mailcap.new. But didn't work. :-( Sorry about that; I
> > ought to have used grep. The list was quite easy to read in its
> > original columns, and mailcap.new is no longer there. Repeating the
> > dpkg -i, however, still didn't work.
>
> Right. The problem is in the postrm script. Looking at that, it
> runs "mime-update". What happens if you run "mime-update" on its own
> as root?
Tux:/etc# mime-update
bash: mime-update: command not found
Tux:/etc#
Sorry, Hugo. I am presumably misunderstanding you. :-(
Lisi
