Michael,

this is a Debian-specific problem, nothing you could solve (except
by removing hostname.7 again).

Michael Kerrisk wrote:
> On Mon, Jun 30, 2008 at 3:42 AM, Dario Minnucci (midget)
> <[EMAIL PROTECTED]> wrote:
> > Package: manpages
> > Version: 3.00-1
> > Severity: normal
> >
> > Cannot upgrade version 3.00-1 with 3.01-1.
> >
> > Here is the log
> >
> > [...]
> > Preparing to replace manpages 3.00-1 (using .../manpages_3.01-1_all.deb) ...
> > Unpacking replacement manpages ...
> > dpkg: error processing /var/cache/apt/archives/manpages_3.01-1_all.deb 
> > (--unpack):
> >  trying to overwrite `/usr/share/man/man7/hostname.7.gz', which is also in 
> > package bind
> > dpkg-deb: subprocess paste killed by signal (Broken pipe)
> > Processing triggers for man-db ...
> > Errors were encountered while processing:
> >  /var/cache/apt/archives/manpages_3.01-1_all.deb
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> Hi Dario,
> 
> I added hostname.7 in upstream man-pages-3.01.  What package does the
> other hostname.7 come from, do you know?

That's hidden in the message above:

> >  trying to overwrite `/usr/share/man/man7/hostname.7.gz', which is also in 
> > package bind
                                                                                
       ^^^^

However, that package shouldn't be installed on Dario's machine at
all as it has been superseded by 'bind9'.  Unfortunately it seems
to me that the's a transitional package missing that'll cause it
to be removed.

Thus, I believe the bug is in the package bind9/bind and not in
manpages.  However, I could fix this by conflicting/replacing
bind with manpages.  Before doing so I'll first see what LaMont
(bind9 maintainer) thinks about it.

Regards,

        Joey

-- 
GNU does not eliminate all the world's problems, only some of them.
                                                -- The GNU Manifesto

Please always Cc to me when replying to me on the lists.



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

Reply via email to