On Sat, Dec 08, 2007 at 09:24:35AM +0900, Osamu Aoki wrote:
> I think if we solve this broken dependency with the patch on the BTS, we
> may end up with undesirable situation.

Yep.  that's why I modified the patch.  See
git://git.debian.org/~lamont/postfix.git

> Solution1: (Pedantic)
> In addition to the patch proposed, postinst of postfix needs to check
> existence of postfix-doc package and if it exists, run postconf -e
> line as a part of postinst.

And that's what it does.

> Solution2: (I like this better for simplicity)
> A bit more sloppy but simple solution is just move this  postconf -e
> line to postinst of postfix package and run it even if postfix-doc does
> not exist.  Then add postfix-doc to the recommends for postfix so you
> have excuse if this minor feature does not work for installation without
> postfix-doc.

See https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/135851

> Comment:
> I do not understand why following still exist for postfix.
>  Replaces: ... postfix-doc (<< 1.1.7-0)
> Since postfix has postfix-doc package as I observe, why not just set
>  Conflicts: ... postfix-doc (<< 1.1.7-0)
> if the old postfix-doc (<< 1.1.7-0) causes problem?

It's there to allow partial upgrades.  OTOH, 1.1.7 is about 3 major
Debian releases ago, so it can certainly go at this point.

lamont



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

Reply via email to